Ultraviolet (UV) light emission device employing visible light for target distance guidance, and related methods of use, particularly suited for decontamination

Description

FIELD OF THE DISCLOSURE

The technology of the disclosure relates to light-emitting devices, and more particularly to devices that emit ultraviolet (UV) light, particularly for use in inactivating and/or killing microorganisms, such as bacteria, viruses, spores, and other pathogens.

BACKGROUND

Pathogens, such as bacteria and viruses, are microorganisms that are present in everyday society. Pathogens are present in areas that humans encounter daily, such as bathrooms, living areas, door handles, public areas, etc. Some airborne pathogens are present in the air that humans breathe. Human beings can become infected with pathogens when they enter the human body as a host. The pathogens begin to multiply, which can result in bacterial infections and diseases that the human body must then fight off as part of its immune defense system response. Thus, it is important for humans to try to limit their exposure to these pathogens. Chemical disinfectants such as bleach, for example, can be used to inactivate or destroy microorganisms. For example, it may be important in hospital settings, in particular, to disinfect all surfaces in a patient's room or area so that the patient's risk of becoming infected with pathogens that are bacterial or viral is reduced. Chemical disinfectants commonly take the form of wipes that are infused with a chemical agent to apply the chemical disinfectant to inert surfaces. Chemical disinfectants can also be applied as a spray or mist in the air and on inert surfaces. However, it is not generally feasible to use chemical disinfectants to disinfect every possible surface that a human may come into contact with.

It is known that ultraviolet (UV) light can also damage the DNA of a microorganism, such as bacteria, viruses, and spores. For example, natural UV light from solar radiation can damage the DNA of a microorganism on surfaces, thus inactivating or killing the microorganism. However, UV light emitted by the sun is weak at the Earth's surface as the ozone layer of the atmosphere blocks most of the UV light. Thus, UV light emission devices that include a UV light source that emits UV light that can be directed to an intended area to inactivate or kill the microorganism present in the area have been designed as a disinfectant method. The UV light source of such UV light emission devices is designed to emit a desired wavelength or range of wavelengths of UV light to be able to expose microorganisms to such light to inactivate or kill the microorganisms. These UV light emission devices need to be designed to emit UV light with enough intensity (i.e., power transferred per unit area) that the UV light that reaches the ultimate surface or area to be disinfected is of sufficient intensity to be effective in inactivating or killing microorganisms of interest. The intensity of the UV light also affects how quickly an exposed microorganism is inactivated or killed. It may be important for business and other practical reasons to disinfect an area quickly, i.e., within minutes or seconds, for example.

For this reason, large UV light emission devices with high-powered UV light sources can be deployed in areas to be disinfected. However, such UV light sources may not be safe for human exposure due to the high intensity of UV emitted light. Thus, these UV light emission devices may have to be used in areas that are closed off from humans until the disinfectant process is complete to avoid human exposure. Handheld UV light emission devices have also been designed as a convenient form factor to be used by humans to disinfect surfaces and other areas. However, handheld UV light emission devices can expose the human user to the UV light in an unsafe manner, especially if the intensity of the UV light source is sufficient to be effective in inactivating or killing microorganisms of interest quickly.

SUMMARY OF THE DISCLOSURE

Aspects disclosed herein include ultraviolet (UV) light emission devices and related methods of use. The UV light emission devices disclosed herein are particularly suited for use in disinfecting surfaces and air. The UV light emission devices disclosed herein can be provided in the form factor of a handheld device that is easily held and manipulated by a human user. The human user can manipulate the handheld UV light emission device to decontaminate surfaces, air, and other areas by orienting the handheld UV light emission device so that the UV light emitted from its light source is directed to the area of interest to be decontaminated.

In one exemplary aspect, a handheld light emission device is disclosed. The handheld light emission device comprises a UV light source comprising a light source housing comprising one or more UV lights each configured to emit UV light in a direction towards a target of interest, and one or more visible lights each configured to emit a respective visible light beam in the direction of the UV light emitted by the one or more UV lights at a given visible light beam spread on the target of interest-based on the distance between the one or more visible lights in the light source housing and the target of interest. The light emission device also comprises an electrical control system comprising one or more light driver circuits, each configured to couple power to the one or more UV lights to cause the one or more UV lights to emit UV light towards the target of interest. The electrical control system is further configured to couple power to the one or more visible lights to cause the one or more visible lights to emit a respective visible light beam towards the target of interest.

In another exemplary aspect, a method of emitting UV light to a target of interest is disclosed. The method comprises directing a UV light source comprising one or more UV lights and one or more visible lights in a light source housing in a direction towards a target of interest. The method also comprises emitting UV light from one or more UV lights of the UV light source in the direction towards the target of interest. The method also comprises emitting a visible light from each of the one or more visible lights in the direction of the UV light emitted by the one or more UV lights to the target of interest in a respective visible light beam spread based on the distance between the one or more visible lights in the light source housing and the target of interest.

In another exemplary aspect, a handheld light emission device is disclosed. The handheld light emission device comprises a UV light source comprising a light source housing comprising one or more UV lights each configured to emit UV light in a direction towards a target of interest, and one or more visible lights each configured to emit a respective visible light beam in the direction of the UV light emitted by the one or more UV lights at a given visible light beam spread on the target of interest-based on the distance between the one or more visible lights in the light source housing and the target of interest. The light emission device also comprises an electrical control system comprising one or more light driver circuits, each configured to couple power to the one or more UV lights to cause the one or more UV lights to emit UV light towards the target of interest. The electrical control system is further configured to couple power to the one or more visible lights to cause the one or more visible lights to emit a respective visible light beam towards the target of interest. The one or more visible lights are each configured to increase its respective visible light beam spread on the target of interest as the distance between the one or more visible lights, and the target of interest is increased. The distance between the one or more UV lights and the one or more visible lights, both to the target of interest, varies as a function of the distance between the light source housing and the target of interest. The one or more visible lights are each configured to vary the visible light beam spread of its visible light beam on the target of interest further based on the orientation of the light source housing to the target of interest. The one or more visible lights comprises a plurality of visible lights. The distance between the respective visible light beam spread of the visible light beam emitted by each the one or more visible lights is a function of the distance between the light source housing and the target of interest. The one or more UV lights are disposed in the light source housing to be configured to emit UV light inside a pattern of visible light emitted on the target of interest.

In another exemplary aspect, a handheld light emission device is disclosed. The handheld light emission device comprises a UV light source comprising a light source housing comprising one or more UV lights each configured to emit UV light in a direction towards a target of interest, and one or more visible lights each configured to emit a respective visible light beam in the direction of the UV light emitted by the one or more UV lights at a given visible light beam spread on the target of interest-based on the distance between the one or more visible lights in the light source housing and the target of interest. The light emission device also comprises an electrical control system comprising one or more light driver circuits, each configured to couple power to the one or more UV lights to cause the one or more UV lights to emit UV light towards the target of interest. The electrical control system is further configured to couple power to the one or more visible lights to cause the one or more visible lights to emit a respective visible light beam towards the target of interest. The handheld light emission device also comprises a mask disposed on the light source housing, the mask containing one or more patterned sections each disposed adjacent to a visible light among the one or more visible lights such that the visible light emitted by the one or more visible lights is emitted through a patterned section among the more or more patterned sections. The one or more patterned sections are each configured to block a portion of the visible light emitted from the one or more visible lights. The electrical control system is configured to couple power to the one or more visible lights to emit visible light towards the target of interest, in response to the one or more light driver circuits providing power from the received power signal to the one or more UV lights.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A is a front perspective view of an exemplary ultraviolet (UV) light emission device that includes a UV light source for UV light emission, wherein the UV light emission device is configured to be manipulated by a human user to be activated and oriented so that UV light emission from the UV light source can be directed to a surface or area of interest for decontamination;

FIG. 1B is a perspective view of a UV light emission system that includes the UV light emission device in FIG. 1A and a power source to provide power to the UV light emission device for operation;

FIG. 1C is a close-up, rear perspective view of the UV light emission device in FIGS. 1A and 1B;

FIG. 2 is a bottom view of the UV light source of the UV light emission device in FIGS. 1A-1C;

FIG. 3A is a first side view of the UV light emission device in FIGS. 1A-1C;

FIG. 3B is a second side view of the UV light emission device in FIGS. 1A-1C;

FIG. 3C is a bottom view of the UV light emission device in FIGS. 1A-1C;

FIG. 3D is a top view of the UV light emission device in FIGS. 1A-1C;

FIG. 3E is a front view of the UV light emission device in FIGS. 1A-1C;

FIG. 3F is a rear view of the UV light emission device in FIGS. 1A-1C;

FIG. 4A is a side, cross-sectional view of the UV light emission device in FIGS. 1A-1C;

FIG. 4B is a close-up, side, cross-sectional view of a UV light source package area of the UV light emission device in FIGS. 1A-1C;

FIG. 4C is a side, exploded view of the UV light source package area of the UV light emission device in FIGS. 1A-1C;

FIG. 5 is a schematic diagram of an exemplary electrical control system that can be included in the UV light emission device in FIGS. 1A-1C;

FIG. 6 is a diagram illustrating operational control of the UV light source in the UV light emission device in FIGS. 1A-1C based on orientation of the UV light emission device;

FIG. 7 is an electrical diagram of light-emitting devices of the UV light source of the UV light emission device in FIGS. 1A-1C;

FIG. 8 is a schematic diagram of another exemplary electrical control system that can be included in the UV light emission device in FIGS. 1A-1C;

FIG. 9 is a diagram of operational states according to execution of a state machine in the UV light emission device in FIGS. 1A-1C that can be executed by the controller circuit in the electrical control system in FIG. 5 or 8, for example;

FIG. 10 is a diagram of light patterns and colors controlled to be emitted by the visual status indicator of the UV light emission device in FIGS. 1A-1C based on the operating states and errors of the UV light emission device according to the operational states in FIG. 9;

FIG. 11 is a diagram illustrating the IMU circuit operation in the UV light emission device in the electronic control systems in FIGS. 5 and 8;

FIG. 12 is a hardware diagram of the haptic feedback device in electronic control systems in FIGS. 5 and 8 of the UV light emission device;

FIG. 13A is a graph illustrating an exemplary degradation in output power of a UV LED over time;

FIGS. 13B and 13C are diagrams of the light source derate operation in the UV light emission device in the electronic control systems in FIGS. 5 and 8;

FIG. 14 is a flowchart illustrating an exemplary overall control process for the UV emission device 100 in FIGS. 1A-1C as controlled by the controller circuit in FIGS. 5 and 8;

FIG. 15 is a flowchart illustrating an exemplary process for power-on and power-on self-test (POST) states in the overall control process in FIG. 14;

FIGS. 16A and 16B is a flowchart illustrating an exemplary process for error detection in the power-up self-test (POST) state of the UV light emission device;

FIG. 17 is a flowchart illustrating an exemplary process performed by the UV light emission device while waiting for the secondary switch of the UV light emission device activated by the user to start light emission operation;

FIG. 18 is a flowchart illustrating an exemplary process for an operational state of the UV light emission device in response to the secondary switch of the UV light emission device being activated;

FIG. 19 is a flowchart illustrating an exemplary process in response to a tilt detection of the UV light emission device;

FIG. 20 is a flowchart illustrating an exemplary process of waiting for the secondary switch of the UV light emission device to be released after tilt detection;

FIG. 21 is a flowchart illustrating an exemplary process of handling error detection in the UV light emission device;

FIG. 22A-22C is a diagram of an exemplary status register that can be programmed and accessed in the UV light emission device to detect programming and record history information for the UV light emission device;

FIG. 23 is a diagram of an alternative UV light source in the form of an excimer UV lamp that can be employed in the UV light emission device in FIGS. 1A-1C;

FIG. 24 is a schematic diagram of an alternative electrical control system that can be employed in the UV light emission device in FIGS. 1A-1C employing the excimer UV lamp in FIG. 23;

FIGS. 25A and 25B are schematic diagrams of an alternative UV light emission device similar to the UV light emission device in FIGS. 1A-1C, but with an alternative UV light source housing that allows air to be drawn into the UV light source housing and across the UV light source to expose the drawn-in air to the UV light emission;

FIG. 26 is a schematic diagram of an alternative UV light emission system that includes the UV light emission device and a power charging station configured to receive the UV light emission system and charge an integrated battery and/or to provide a wired interface connectivity for exchange of telemetry information stored in the UV light emission device;

FIGS. 27A and 27B illustrate exemplary depths of focus of UV light emitted from the UV light source of the UV light emission device in FIGS. 1A-1C as a function of distance from the UV light source;

FIG. 28 is a graph illustrating an exemplary relationship between mean irradiance of UV light emitted from the UV light source of the UV light emission device in FIGS. 1A-1C on a surface of interest and distance of the surface from the UV light source;

FIGS. 29A and 29B illustrate exemplary spotlights formed on a surface as a result of orienting the UV light source of the UV light emission device in FIGS. 1A-1C towards a surface at different distances and the visible UV lights of the UV light source emitting visible light onto the surface;

FIGS. 30A-30C illustrate exemplary spotlights patterns on a surface as a result of orienting the UV light source of the UV light emission device in FIGS. 1A-1C towards a surface at different distances, and the visible UV lights of the UV light source emitting visible light onto the surface;

FIG. 31 is a diagram of exemplary, alternative patterned spotlights on a surface as a result of providing a mask on the UV light source with patterned openings adjacent to the visible lights and orienting the UV light source of the UV light emission device in FIGS. 1A-1C towards a surface at different distances, and the visible UV lights of the UV light source emitting visible light on the surface;

FIG. 32 is a diagram of the UV light emission device in FIGS. 1A-1C with a mask disposed on the light source adjacent to the visible lights in the UV light source;

FIG. 33 is a diagram of a mask placed on the UV light source to cause visible light emitted from the visible light indicator on the surface to be patterned as shown in FIG. 31;

FIGS. 34A-34F are exemplary heat maps of UV light emitted by the UV light source of the UV light emission device in FIGS. 1A-1C as a function of distance from center and distance of the UV light source from a surface of interest;

FIG. 35 is a graph illustrating an exemplary reflectance versus wavelength of different common metals;

FIG. 36 is a graph illustrating an exemplary reflectance versus wavelength of different coatings on parabolic reflectors of the UV light source in the UV light emission device in FIGS. 1A-1C;

FIGS. 37A-37D illustrate an alternative UV light emission device similar to FIGS. 1A-1C, but with a power connector and a mounting structure on the base;

FIGS. 38A-38C are respective perspective, front and side views, respectively, of belt clip that is configured to receive the mounting structure on the base of the UV light emission device in FIGS. 37A-37C to mount the UV light emission device to a user's belt; and

FIG. 39 is a schematic diagram of a representation of an exemplary computer system, wherein the exemplary computer system is configured to control the operation of a UV light emission device, including but not limited to the UV light emission devices disclosed herein.

DETAILED DESCRIPTION

With reference now to the drawing figures, several exemplary aspects of the present disclosure are described. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

FIG. 1A is a front, perspective view of an exemplary ultraviolet (UV) light emission device 100 that includes a UV light source 102 that emits UV light 104. The UV light emission device 100 in FIG. 1A in this example is a handheld device that is configured to be manipulated by a human user to be activated and oriented so that emission of UV light 104 from the UV light source 102 can be directed to a surface or area of interest for decontamination. Certain wavelengths of UV light have been found effective in damaging the DNA of pathogens and, as a result, inactivating or killing such pathogens. As will be discussed in more detail below, the UV light emission device 100 in FIG. 1A includes a light source head 106 that is a housing that supports the UV light source 102 and provides supporting components to control emission of the UV light 104 from the UV light source 102. For example, the light source head 106 in this example could include an optional light source shield 108 that is disposed in front of an array of UV LEDs 110 configured to emit the UV light 104 as part of the UV light source 102. The UV LEDs 110 will each have a viewing angle that affects the angle of UV light emission from a normal plane, which in this example is the plane of the light source shield 108. The light source head 106 is designed to support the insertion and retention of the light source shield 108. The light source shield 108 is provided for safety reasons to avoid contact, including human contact, with the UV LEDs 110, to avoid skin burns due to the heat emanating from the UV LEDs 110, and/or to avoid damaging the UV LEDs 110. It may be important that the light source shield 108 be designed to allow at least a portion of the UV light 104 generated by the UV light source 102 to pass therethrough so that the UV light 104 can reach a desired surface or area of interest when the UV light emission device 100 is in use. For example, the light source shield 108 could be made of fused silica, quartz glass, or other UV translucent material, such as PCTFE (Polychlorotrifluoroethylene). The light source shield 108 may be manufactured to be shatter-proof.

The light source shield 108 can be a solid member or could have openings. As another example, the light source shield 108 could include a patterned mesh, such as from a mesh metal or plastic material that has either openings or translucent sections to allow UV light 104 to pass through, but also reduces or prevents the ability for direct contact and/or damage to the UV LEDs 110. The mesh may be made from a metal material or alloys, such as stainless steel or aluminum material, as examples. An optional diffuser could be installed on or serve as the light source shield 108 to diffuse the UV light 104 emitted from the UV light source 102, but as the UV light 104 is not visible, a diffuser may not be desired or necessary. A filter coating 109 could also be disposed on the light source shield 108 to filter out certain wavelengths of the UV light 104 if desired. The light source shield 108 can include a first surface 111 disposed adjacent to and behind the UV light source 102 and a second surface 113 opposite the first surface 111. The filter coating 109 could be disposed on the first and/or second surfaces 111, 113 of the light source shield 108.

In addition, or in the alternative to employing the light source shield 108 to protect the UV LEDs 110 from contact for safety or other reasons, the UV LEDs 110 could be housed in reflectors that are sized to prevent direct human contact. This is discussed in more detail below with regard to FIGS. 4A and 4B. The openings of the reflectors 424 could be sized small enough to prevent a human finger from being able to be inserted therein and come in contact with the UV LEDs 110.

The UV light emission device 100 has been found to be effective at killing bacteria, viruses, and spores at a rate of 99.9% or higher. The UV light source 102 in the UV light emission device 100 is selected to be at a desired UV wavelength or range of wavelengths to damage or kill pathogens as a decontamination tool. For example, the UV light source 102 can be selected to emit UV light at a single or multiple UV wavelengths in the 200-399 nanometer (nm) wavelength range. For example, the UV light source 102 may be selected to emit UV light at a wavelength(s) between 260-270 nm. For example, the UV LEDs 110 may be the Klaran WD Series UVC LEDs, as a non-limiting example, that emits light at a wavelength(s) between 250-270 nm at an optical output power of either 60 milliWatts (mW) (Part No. KL265-50 W-SM-WD), 70 mW (Part No. KL265-50V-SM-WD), or 80 mW (Part No. KL265-50U-SM-WD). As another example, the UV light source 102 may be selected to emit UV light at peak wavelengths at 254 nm and/or 265 nm. As another example, the UV light source 102 may be selected to emit UV light at a wavelength(s) between 200-230 nm as Far-UVC light. For example, a Far-UV wavelength of 222 nm has been found to be effective in inactivating or killing pathogens and also be safe to human tissue. Thus, it may be possible to operate the UV light emission device 100 without the need to provide protection, such as masks, goggles, gloves, and/or other personal protective equipment (PPE) for a human user or human in the field of the UV light 104. As another example, the UV light source 102 may be selected to emit UV light at a wavelength of 207 nm.

The UV light emission device 100 could also be configured to change (e.g., upconvert) the wavelength frequency of UV light 104 emitted by the UV light source 102 to a higher energy/intensity level. For example, the UV light source 102, whether frequency-converted or not, may be configured to emit UV light 104 with an intensity of 5-100 milliWatts (mW) per square centimeter (cm2) (mW/cm2). For example, the UV light source 102 may be selected and configured to emit UV light 104 with an intensity of 10-60 mW/cm2. As another example, the UV light source 102 may be selected and configured to emit the UV light 104 with an intensity of 20 mW/cm2 for periods of up to one (1) second (sec.). For example, with the UV light 104 at an intensity of 20 mW/cm2, the UV light emission device 100 could be swept over an area of interest that is at a height of five (5) cm above the surface and a rate of two (2) cm in length per second to expose the area of interest to the desired intensity and duration of the UV light 104 for decontamination. The UV light emission device 100 could be configured to emit the UV light 104 from the UV light source 102 for any amount of time desired by the user or for defined periods of time and to a desired intensity. For example, such defined periods of time could be 1-10 seconds and a time period specifically of one (1) second or less. The UV light emission device 100 could be configured to control the UV light source 102 to emit the UV light 104 as a steady-state light or to pulse the UV light source 102 to emit pulses of the UV light 104, such as at a pulse rate between 10-100 KiloHertz (kHz), for example. Controlling the pulse rate of the UV light 104 is another way to control the intensity of the UV light 104. The UV light emission device 100 could be configured to control the activation and deactivation of the UV light source 102 to control the pulse rate of the UV light 104 through a pulse-width modulated (PWM) signal to control the enabling and disabling of a light driver circuit, as an example.

With continuing reference to FIG. 1A, as will be discussed in more detail below, the UV LEDs 110 are mounted on a printed circuit board (PCB) 112 that is installed inside the light source head 106. The light source head 106 also includes vent openings 114 on one or more of its sides 116 and rear 117, also shown in the rear perspective view of the UV light emission device 100 in FIG. 2A, to allow for the escape of heat generated inside the light source head 106 due to the heat generated from the UV LEDs 110 when activated (i.e., turned on). As will also be discussed in more detail below, the light source head 106 can support other components to support the operation of the UV light source 102, including a fan and heat sink for dissipation of heat generated by the UV LEDs 110, as an example. The light source head 106 can also be designed to support a PCB as part of the light source head 106 to support the UV LEDs 110 and other components, such as temperature sensors supporting operation and control functions. The light source head 106 in the UV light emission device 100 in FIGS. 1A-1C is square-shaped, but the light source head 106 could also be provided in other shapes, including circular-shaped, oval-shaped, or elliptical-shaped.

With continuing reference to FIG. 1A, the UV light emission device 100 also includes a handle 118 that is attached to the light source head 106. The handle 118 may be a separate component that is attached to the light source head 106 or formed as an integrated component with the light source head 106, such as that produced with a mold. The handle 118 supports a surface to allow a human user to engage the handle 118 with their hand to control and manipulate the orientation of the UV light 104 emitted from the UV light source 102. The user can lift the UV light emission device 100 by the handle 118 and manipulate the UV light source 102 through manipulation of the handle 118 to direct the UV light 104 emitted from the UV light source 102 to the surface or area desired to decontaminate such surface or area. For example, the UV light emission device 100 may be lightweight (e.g., 1.5 lbs. without integration of a battery or 3 lbs. with integration of a battery) to be easily handled and maneuvered by a human user. In this example, as shown in FIG. 1A, and as will be discussed in more detail below, the handle 118 includes a secondary switch 120 that is disposed on the underneath side 121 of the handle 118. The UV light emission device 100 is designed so that the UV light source 102 will not activate the UV LEDs 110 to emit UV light 104 unless the secondary switch 120 is depressed and activated to a closed state as a safety mechanism. FIG. 1A shows the secondary switch 120 is a non-activated state as not being depressed. The secondary switch 120 in this example is a momentary switch that acts as a trigger switch and returns to a non-depressed, non-activated, or open-state when a force is no longer applied to the secondary switch 120. In this manner, a user who grabs the handle 118 of the UV light emission device 100 to control it can squeeze the handle 118 to depress the secondary switch 120 to activate the secondary switch 120 such that it provides a trigger signal to activate the UV light source 102 to emit UV light 104. The secondary switch 120 could be a mechanical switch, or alternatively, a capacitive touch sensor switch, as an example. However, a capacitive touch sensor switch may not be desired if the UV light emission device 100 will be used by persons wearing gloves, for example, where the capacitance of the person does not transfer to the switch. When the user disengages the handle 118, the secondary switch 120 becomes non-depressed and thus non-activated such that it does not provide a trigger signal.

Thus, by providing the secondary switch 120 as a momentary switch, the UV light source 102 is only active when the secondary switch 120 is being actively depressed, such as by a user holding the handle 118 and depressing the secondary switch 120. When a user is no longer depressing the secondary switch 120, the secondary switch 120 becomes non-depressed and thus non-activated such that it does not provide a trigger signal to activate the UV light source 102. Thus, the secondary switch 120 can act as a safety measure to ensure that the UV light source 102 is not active when the secondary switch 120 is not being engaged. For example, if the user of the UV light emission device 100 lays the device down and releases the handle 118 such that the secondary switch 120 is not activated, the UV light source 102 will be deactivated. The secondary switch 120 as a momentary switch allows the user to control the ultimate on and off time of the UV LEDs 110.

Further, although not limiting and the UV light source 120 not being limited to the use of UV LEDs, the deployment of the secondary switch 120 as a momentary switch can also make more feasible the use of LEDs in the UV light source 120. LEDs are a semiconductor device. As soon as current flows to the LED, electrons flow through its P-N junction of a LED, and energy is released in the form of photons to emit light. The UV LEDs 110 of the UV light source 120 are able to essentially instantaneously emit UV light when current starts to flows under control of the secondary switch 120 when activated without having to wait for more significant elapsed time (e.g., 10-15 minutes) for a gas inside a bulb to “warm-up” to produce a fuller intensity light. The use of LEDs as the UV light source 102 allows a more instantaneous off and on of UV light emission, as controlled by the secondary switch 120 in this example, without having to employ other techniques for off and on employed by bulbs, such as pulse-width modulation (PWM). Also, in this example, the UV light emission device 100 includes a primary switch 122 that must be activated to a closed position for the UV light emission device 100 to be activated regardless of the state of the secondary switch 120. In this regard, a user cannot accidentally activate the UV light source 102 to emit the UV light 104 without depressing the secondary switch 120 on the handle 118 even if the primary switch 122 is activated. As will be discussed in more detail below, the primary switch 122 being activated couples a power source to an electronic control system and the UV light source 102 for operations. Thus, deactivating the primary switch 122 decouples power from the electronic control system and the UV light source 102 as a hard kill switch, such that the UV light emission device 100 will be completely non-operational regardless of the state of the secondary switch 120. The secondary switch 120 only controls activation and deactivation of the UV light source 102 as a secondary control mechanism.

With continuing reference to FIG. 1A, the UV light emission device 100 in this example also includes a base 124 that includes a base housing 126 that is attached to an end 128 of the handle 118 opposite an end 130 of the handle 118 attached to the light source head 106. The base 124, the handle 118, and the light source head 106 may all be made of hardened plastic material, as an example. The base housing 126 can be a separate component that is attached to the handle 118 or formed as an integrated component with the handle 118, such as that produced with a mold. As will be discussed in more detail below, in this example of the UV light emission device 100, the base housing 126 supports PCBs of the electronic control system and light source driver circuits (i.e., current drivers) to drive power to the UV LEDs 110 in the UV light source 102 for operation to emit the UV light 104. As discussed below, the electronic control system and light source driver circuits are located in the base 124 to separate them from the UV light source 102 that generates substantial heat. In this example, the base housing 126 is spatially separated from the light source head 106 by at least eight (8) inches through the intermediate handle 118 to spatially isolate the electronic control system from the UV light source 102. The base housing 126 can also be configured to support other components as desired, including sensors that may be employed to detect environmental and other conditions that are detected to affect the control and operation of the UV light emission device 100. The handle 118 can include an interior portion (not shown in FIG. 1A) that supports a wiring harness coupled between light source driver circuits in the base housing 126 and the UV light source 102. The wiring harness is connected to a PCB as part of the UV light source 102 in the light source head 106 to couple power and control signals from the light source driver circuits to the UV light source 102. The primary switch 122 is also supported in the base housing 126 and mounted on the bottom surface 132 of the base housing 126 for convenience.

As also shown in FIGS. 1A and 1B, a grommet 134 is also supported by the base housing 126 in this example and mounted on the bottom surface 132 of the base housing 126 to support an electrical cable 136 attached to the base housing 126 and extending into the base housing 126 for carrying power from an external power source to the light source driver circuits and electrical control system components in the base housing 126 for operation. FIG. 1B illustrates a UV light emission system 138 that includes the UV light emission device 100 and a power source 140 in the form of a battery 142 to provide power to the UV light emission device 100. The battery 142 is provided remote from the UV light emission device 100 in this example. Alternatively, the power source 140 could include an alternating current (AC) power interface and AC-DC power converter circuitry so that the power source could be power received directly through an AC power outlet without the need for a battery. As another example, the power source 140 could include both alternating current (AC) power interface and AC-DC power converter circuitry to charge the battery 142, and the UV light emission device 100 be portably used from power from the battery 142. As another example, the battery 142 could be integrated into the base 124 to avoid the need for attachment of the UV light emission device 100 through the electrical cable 136.

FIG. 1C is a close-up rear perspective view of the UV light emission device 100 in FIGS. 1A and 1B to illustrate additional detail. As shown in FIG. 1C, the base 124 is formed by the base housing 126 and a base attachment member 200 that is secured to the base housing 126 through fasteners 139, such as screws, that are received into respective orifices 141 in the base housing 126 and engage with internal female bosses/receivers in the base attachment member 200. The orifices 141 may be threaded to receive the fasteners 139, which may be self-tapping fasteners 139, for example. An interior chamber is formed in the base 124 between the base housing 126 and base attachment member 200. In this manner, the base housing 126 can be easily removed to access components, including the electrical control system and light source driver circuits, inside the base housing 126, such as for repair or troubleshooting. Also, as shown in FIG. 1C, the light source head 106 includes a light source housing 202 that is attached to a light source housing cover 204 to secure the UV light source 102. For example, the light source housing 202 and the light source housing cover 204 may be an approximately 4″×4″ dimension to provide a large area for the embedded UV light source 102. An interior chamber is formed in the light source head 106 between the light source housing 202 and the light source housing cover 204. As discussed in more detail below, the components of the UV light source 102, including the UV LEDs 110, a PCB 112 in which the UV LEDs 110 are mounted, a fan, and heat sink are mounted inside the light source housing 202. The light source housing cover 204 may be made or surrounded on its outside from a softer material than the light source housing cover 204, such as rubber, silicone, polycarbonate, polyethylene material, a thermoplastic elastomer, and a thermoplastic urethane as examples, as a bumper to protect the light source shield 108, especially if the light source shield 108 is made from a delicate material, such as glass. In this manner, if the UV light emission device 100 is dropped, the light source housing cover 204 can absorb some of the impact from the collision.

With continuing reference to FIG. 1C, a visual status indicator 143, which is an LED 144 in this example, is mounted on the rear 117 of the light source housing 202 to provide a visual status of the UV light emission device 100 to a user. As will be discussed in more detail below, the light color and/or the emission pattern of the visual status indicator 143 can be controlled by the electronic control system of the UV light emission device 100 to provide information on operational and error modes of the UV light emission device 100 visually to the user. For example, the visual status indicator 143 can be controlled to emit different colors, such as red, green, and yellow, as well as emit light in different blink patterns. The visual status indicator 143 is preferentially mounted on the rear 117 of the light source housing 202 so that the visual status indicator 143 is in line of sight of a user as the user holds the handle 118 and directs the UV light 104 emitted from the UV light source 102 through the light source shield 108 away from the user towards a surface or area of interest.

With continuing reference to FIG. 1C, the UV light 104 emitted by the UV LEDs 110 is at a UV wavelength(s) that is not visible to the human eye. Thus, there is not a way for a user to detect that the UV light source 102 is operational and the UV LEDs 110 are emitting light by seeing the UV light 104 emanating from the UV light source 102. This could cause an unsafe condition if the user were to look in at the UV LEDs 110 wherein the UV light 104 reached the surface of the user's skin and/or cornea of their eyes, depending on the wavelength(s) of the UV light 104, the intensity of the UV light 104, and the duration of exposure. Thus, in this example, the light source head 106 also includes an additional visual status indicator 146 in the form of a visible light ring 148. The visible light ring 148 is made of a translucent material shaped in the form of a ring that fits and is retained between the light source housing 202 and the light source housing cover 204 when the light source housing cover 204 is secured to the light source housing 202. Visible light indicators or visible lights in the form of visible light LEDs (not shown) are located on a PCB that also supports the UV LEDs 110 in this example. The visible light LEDs are placed so that the light emitted from the visible light LEDs is directed towards the visible light ring 148 automatically when the UV light source 102 is operational. The visible light ring 148 acts as a light pipe, such that the visible light emitted by the visible light LEDs through the visible light ring 148 appear to light up or glow. In this example, the visible light indicators are electrically coupled to a light source driver circuit that receives power from the same main light power rail as the UV light source 102. Thus, if power is interrupted to the main light power rail as a safety condition, for example, the visible light ring 148 will not glow to indicate that the UV light source 102 is also non-operational. However, if power is coupled to the main light power rail, the visible light ring 148 will glow to indicate that the UV light source 102 is also receiving power and may be operational.

Alternatively or in addition, an optional mesh material installed over the light source shield 108 or providing the light source shield 108 could be coated with a phosphorous material that exhibits luminescence and illuminates when contacted by the UV light 104 for a period of time according to its decay rate. Thus, the light source shield 108 could also serve as a visual indicator to a user that the UV light source 102 is operational. This method may also be employed as a way to avoid further internal visible-light LEDs in the light source housing 202 to illuminate through the visible light ring 148, acting as a light pipe, and/or to eliminate the visible light ring 148.

FIG. 2 is a bottom view of the light source head 106 of the UV light emission device 100 in FIGS. 1A-1C to illustrate additional exemplary details of the UV light source 102 and the light source shield 108. As shown in FIG. 2, the UV light source 102 includes the UV LEDs 110 in this example, as previously discussed. The UV LEDs 110 are grouped in light strings that consist of either one LED or multiple LEDs electrically coupled together serially. In this example, there are six (6) light strings 206(1)-206(6) in the UV light source 102. A light string is defined as a circuit that can contain one light (e.g., a LED) or multiple lights (i.e., multiple LEDs) connected in series to each other. The grouping of a number of LEDs on a light string is a design choice and is dependent on the light source driver circuit selected and the amount of current needed to drive the LEDs according to their specifications to emit light of the desired intensity. The grouping of LEDs in light strings may also be desired to allow each light string 206(1)-206(6) to operate independently of the other light strings 206(1)-206(6) in case there is a failure in an LED in a given light string 206(1)-206(6) and/or its light source driver circuit.

With reference to FIG. 2, the UV light emission device 100 in this example also includes one or more visible lights in the light strings 206(1)-206(6) that are configured to emit light in the visible spectrum and at one or more wavelengths in the visible light spectrum (i.e., between 400-700 nanometers (nm)), which is safe to humans. For example, light strings 206(1) and 206(6) could each include two (2) visible lights 208(1)-208(2), and 208(3)-204(4), which can be in the form of visible light LEDs as an example. In this manner, when the light strings 206(1), 206(6) of the UV light source 102 are operational, current driving these light strings 206(1), 206(6) also automatically drives the visible lights 208(1)-208(4) in these light strings 206(1), 206(6) to emanate visible light. By automatic, it is meant that the UV light emission device 100 is configured to drive power to the visible lights 208(1)-208(4) to cause them to emit visible light when power is driven to the light strings 206(1), 206(6) to cause UV LEDs 110 to emit UV light in this example without further separate user activation or control. In this manner, the visible light emitted by the visible lights 208(1)-208(4) is visually perceptible to a user when the UV LEDs 110 are emitting UV light for the user's safety and to provide visual feedback to the user as discussed in more detail below. In other words, the user will know the UV LEDs 110 are emitting UV light that is not otherwise visible to the user when the visible lights 208(1)-208(4) are emitting visible light. For example, the visible lights 208(1)-208(4) may be configured to emit white light. For convenience, the visible lights 208(1)-208(4) can replace respective UV LEDs 110 that would otherwise be present in the UV light source 102. Thus, a user that is operating the UV light emission device 100 has indicators that are visibly perceptible in the form of the visible light emitted from the visible lights 208(1)-208(4) to also know that the UV light 104 is being emitted by the UV light source 102. In this example, as a non-limiting example, the visible lights 208(1)-208(4) are mounted in the UV light source 102 in the interior chamber of the light source housing 202 adjacent to the outside corners of the light source head 106 so that the visible light emitted from the UV light source 102 provides an approximate light border of where the UV light 104 may be emanating from the UV LEDs 110 when the UV light source 102 is activated. The visible light is emitted by visible lights 208(1)-208(4) in the direction of the UV light 104 emitted by the UV LEDs 110. The visible light emitted by the visible lights 208(1)-208(4) can intersect the UV light 104 emitted by the UV LEDs 110. In this manner, the user can determine by viewing the visible light emitted by the visible lights 208(1)-208(4), the direction and general area in which the UV light 104 is emitted by the UV LEDs 110. Alternatively, another visible light source other than the visible lights 208(1)-208(4) as LEDs may be employed, including but not limited to a laser that emits one or more laser beams, as an example. Alternatively, a single visible light could be mounted in the UV light source 102 in the center or center area of the light source head 106 so that the visible light emitted from the UV light source 102 is centered to the UV light 104 emanating from the UV LEDs 110 when the UV light source 102 is activated.

Also, in this example, a benefit of placing the visible lights 208(1)-208(4) in the series of light strings 206(1), 206(6) that also include UV LEDs 110 is to provide a safety mechanism. Current that reaches the UV LEDs 110 in the light strings 206(1), 206(6) will also reach the visible lights 208(1)-208(4) so that the visible lights 208(1)-208(4) will emit visible light when the UV light source 102 is emitting UV light 104. Also, as will be discussed in more detail below, the UV light emission device 100 is designed so that power can be decoupled from the UV light source 102 independent of power provided to the electronic control system that drives the visual status indicator 143 shown in FIG. 1C. Thus, the emission of light by the visual status indicator 143 in and of itself is not an absolute indicator of the presence or lack of presence of the UV light 104 emitted by the UV light source 102. However, as discussed above and in more detail below, the color and light pattern of the visual status indicator 143 can be controlled to indicate different operational modes and statuses to a user, which can include an operational status of the UV light source 102. In this instance, the visible lights 208(1)-208(4) are a secondary method of visually conveying to a user if the UV light source 102 is operational and emitting the UV light 104. The visual status indicator 143 can be a bi-color LED that is configured to emit different colors (e.g., green, red, and yellow colors) of light depending on a controlled operational mode.

With continuing reference to FIG. 2, the light source housing cover 204 includes female bosses/receivers (not shown) that are configured to receive fasteners 210(1)-210(4) to secure the light source shield 108 to the light source housing cover 204. The light source shield 108 includes openings 212(1)-212(4) that are configured to align with the female receivers internal to the light source housing cover 204 when the light source shield 108 is placed inside the light source housing cover 204. The light source housing cover 204 is designed to have an internal diameter D1 that is slightly larger than the outer diameter D2 of the light source shield 108 so that the light source shield 108 can fit inside the outer edges of the light source housing cover 204. Fasteners 210(1)-210(4) are inserted into the openings 212(1)-212(4) to secure the light source shield 108 to the light source head 106.

FIG. 3A is a first side view of the UV light emission device 100 in FIGS. 1A-1C with common elements discussed above labeled with common element numbers. As shown in FIG. 3A, the UV light emission device 100 is designed so that the plane P1 of the opening # normal to the light source housing cover 204 and the UV light source 102 therein is at angle Φ1 with respect to the tangential plane P2 to the apex A1 of the handle 118. The apex A1 of the handle 118 may be located at half the distance DA between ends 128, 130 of the handle 118 as an example. In this manner, when a user is handling the UV light emission device 100 by the handle 118, the light source housing 202 and UV light source 102 will naturally be oriented in a parallel plane to plane P1 with respect to the ground. Then angle Φ1 between the first plane P1 and the tangential plane P2 can be between 1 and 45 degrees. FIG. 3B is a second side view of the UV light emission device in FIGS. 1A-1C with common elements discussed above labeled with common element numbers. FIG. 3C is a bottom view of the UV light emission device 100 in FIGS. 1A-1C with common elements discussed above labeled with common element numbers. FIG. 3D is a top view of the UV light emission device 100 in FIGS. 1A-1C with common elements discussed above labeled with common element numbers. FIG. 3E is a front view of the UV light emission device 100 in FIGS. 1A-1C with common elements discussed above labeled with common element numbers. FIG. 3F is a rear view of the UV light emission device 100 in FIGS. 1A-1C with common elements discussed above labeled with common element numbers.

To illustrate more exemplary detail of the UV light emission device 100 in FIGS. 1A-1C, FIGS. 4A-4D are provided. FIG. 4A is an overall side, cross-sectional view of the UV light emission device 100 in FIGS. 1A-1C. FIG. 4B is a close-up, side, cross-sectional view of the light source head 106 of the UV light emission device 100. FIG. 4C is a side perspective exploded cross-sectional view of the light source head 106 of the UV light emission device 100. FIG. 4D is an overall side, exploded view of the UV light emission device 100.

With reference to FIG. 4A, six (6) light driver circuits 400(1)-400(6) are installed in the base housing 126 of the base 124 to drive power to the UV light source 102 in the light source head 106. In this example, the light driver circuits 400(1)-400(6) are LED driver circuits to drive the UV LEDs 110 in the UV light source 102. In this example, the light driver circuits 400(1)-400(3) are mounted to a first light driver PCB 402 inside the base housing 126, and the light driver circuits 400(4)-400(6) are mounted to a second light driver PCB 403 opposite the first light driver PCB 402. As previously discussed, input power provided to the light driver circuits 400(1)-400(6) is sourced from the electrical cable 136 (see FIG. 1C). There are six (6) light driver circuits 400(1)-400(6) in this example because each light driver circuits 400(1)-400(6) drives power to one (1) light string 206(1)-206(6) among the six (6) light strings 206(1)-206(2) provided in the UV light source 102 (see FIG. 2). As will also be discussed in more detail below, current and voltage sensors (not shown) are also provided for the light driver circuits 400(1)-400(6) to sense current drawn from the light driver circuits 400(1)-400(6) and/or voltage across the driver circuits 400(1)-400(6) as a failure detection mechanism to determine if any of the light driver circuits 400(1)-400(6) have failed. The light driver circuits 400(1)-400(6) may not only be located in the base 124 apart from the UV light source 102 in the light source head 106 for packaging convenience but also to manage heat. This also creates balance by placing the electronic control system 404 and the light driver circuits 400(1)-400(6) in this example in the base 124 circuitry opposite the light source head 106. The center of gravity of the UV light emission device 100 is very close to the secondary switch 120, reducing wrist strain. The light driver circuits 400(1)-400(6) are configured to supply a large amount of current and generate heat. The UV light source 102 also generates heat. So, providing the light driver circuits 400(1)-400(6) in the base 124 apart from the light source head 106 may serve to improve heat dissipation rates and to more easily manage the temperature in the UV light source 102.

With continuing reference to FIG. 4A, an electrical control system 404 on an electrical control PCB 406 is also supported in the base housing 126. The electrical control system 404 is an electrical circuit. As will be discussed in more detail below, the electrical control system 404 includes a microprocessor that is configured to receive inputs from a number of sensors and other sources, including the secondary switch 120 on the handle 118, and control the activation of the light driver circuits 400(1)-400(6) to activate and deactivate the UV light source 102. As also shown in FIG. 4A, wiring connectors 408, 410 are provided inside the base 124 and extend inside the handle 118 to provide a wiring harness between the light driver circuits 400(1)-400(6), the electrical control system 404, and the UV light source 102. The wiring harness may include, for example, a ribbon cable 412 that is coupled to the wiring connector 410 and to another wiring connector 414 on the opposite end of the handle 118 adjacent to the light source head 106 that is connected to writing connector 416 coupled to the UV light source 102 to distribute power and other communications signals between the light driver circuits 400(1)-400(6) electrical control system 404.

With continuing reference to FIG. 4A, the secondary switch 120 is shown installed inside the handle 118 with a trigger 418 of the secondary switch 120 exposed from an opening in the body of the handle 118. The trigger 418 is attached to a spring-loaded hinge 420 that biases the trigger 418 outward to an open position. The trigger 418 of the secondary switch 120 is in electrical contact with the electrical control system 404. As will be discussed in more detail below, when the trigger 418 is not engaged such that the secondary switch 120 remains open such that a trigger signal cannot be provided, the electrical control system 404 disables the distribution of power from the power source received over the electrical cable 136 to the light driver circuits 400(1)-400(6) as a safety mechanism. When the trigger 418 is moved inward and engaged to close the secondary switch 120, the secondary switch 120 can provide a trigger signal in the electrical control system 404 that enables the distribution of power from the power source received over the electrical cable 136 to the light driver circuits 400(1)-400(6). For example, the secondary switch 120 may be the Omron D2MQ series Omron SS series (e.g., SS-01GL13) subminiature basic switch.

As discussed previously, by providing the secondary switch 120 as a momentary switch, the light driver circuits 400(1)-400(6) of the UV light source 102 are only active to generate current when the secondary switch 120 is being actively depressed, such as by a user holding the handle 118 and depressing the secondary switch 120. When a user is no longer depressing the secondary switch 120, the secondary switch 120 becomes non-depressed and thus non-activated such that it does not provide a trigger signal to activate the light driver circuits 400(1)-400(6). Thus, the secondary switch 120 can act as a safety measure to ensure that the UV light source 102 is not active when the secondary switch 120 is not being engaged. For example, if the user of the UV light emission device 100 lays the device down and releases the handle 118 such that the secondary switch 120 is not activated, the light driver circuits 400(1)-400(6) will be deactivated. The secondary switch 120 as a momentary switch allows the user to control the ultimate on and off time of the UV LEDs 110.

Further, although not limiting and the UV light source 102 not being limited to use of UV LEDs, the deployment of the secondary switch 120 as a momentary switch can also make more feasible the use of LEDs in the UV light source 102. LEDs are a semiconductor device. As soon as current flows to the LED, electrons flow through its P-N junction of a LED, and energy is released in the form of photons to emit light. The UV LEDs 110 of the UV light source 102 are able to essentially instantaneously emit UV light when current starts to flows under control of the secondary switch 120 when activated without having to wait for more significant elapsed time (e.g., 10-15 minutes) for a gas inside a bulb to “warm-up” to produce a fuller intensity light. The use of LEDs as the UV light source 102 allows a more instantaneous off and on of UV light emission, as controlled by the secondary switch 120 in this example, without having to employ other techniques for off and on employed by bulbs, such as pulse-width modulation (PWM).

With continuing reference to FIG. 4A, a cross-sectional view of the light source head 106 of the UV light emission device 100 is shown. FIG. 4B illustrates a close-up, cross-sectional view of the light source head 106 of the UV light emission device 100 shown in FIG. 4A to provide additional detail. FIG. 4C illustrates a side perspective exploded cross-sectional view of the light source head 106 of the UV light emission device 100 shown in FIGS. 4A and 4B. As shown in FIGS. 4A-4C, the UV light source 102 installed in the light source head 106 includes a light source PCB 422 in which the UV LEDs 110 and visible lights 208(1)-208(4) are mounted, as previously discussed in FIG. 2 above. Visible light indicators 423 (i.e., visible lights), which may be LEDs, are also mounted on the perimeter of the light source PCB 422 adjacent to the visible light ring 148 and driven by a light driver circuit 400(1)-400(6) to emit light to the visible light ring 148 that is then propagated through the visible light ring 148 when the UV light source 102 has activated an additional indicator of such. Thus, in this example, because the visible light indicators 423 are driven by a light driver circuit 400(1)-400(6) that also drives the UV LEDs 110 in the UV light source 102, the visible light indicators 423 are activated automatically in response to the light driver circuits 400(1)-400(6) driving the UV LEDs 110 in the UV light source 102. In this manner, the visible light emitted by the visual light indicators 143 to the visible light ring 148 is visually perceptible to a user when the UV LEDs 110 are emitting UV light for the user's safety. In other words, the user will know the UV LEDs 110 are emitting UV light that is not otherwise visible to the user when the visible light ring 148 is illuminated by visible light from the visual light indicators 143. The UV LEDs 110 and visible lights 208(1)-208(4) are mounted in parabolic reflectors 424 that may be reflectors of a metal material, and that reflect and direct their emitted light in a ten (10) degree cone in this example.

A heat sink 426 is mounted on the backside of the light source PCB 422 for the UV light source 102 to dissipate heat generated from operation. A fan 428 is mounted inside the light source head 106 above the heat sink 426 to draw heat away from the heat sink 426 and the light source PCB 422 for the UV light source 102 and to direct such heat through the vent openings 114 in the rear 117 of the light source housing 202 for heat dissipation. Alternatively, the fan 428 could be controlled to draw air through the openings 114 in the rear 117 of the light source housing 202 and exhausting it through the openings 114 in the side(s) 116 of the light source housing 202 for heat dissipation. As discussed in more detail below, the fan 428 is electronically controlled by the electrical control system 404 to variably control the speed of the fan 428 based on sensed temperature in the UV light source 102 to provide sufficient heat dissipation. In another embodiment, the fan 428 can be eliminated using passive heat dissipation. This may be possible when UV light source 102 is efficient enough to not need additional airflow for heat dissipation.

In addition, since visible LEDs such as the visible light indicators 423 and UV LEDs, such as UV LEDs 110, have different optical efficiencies, where visible LEDs are generally more optically efficient, the circuit could be modified to shunt some of the currents around the white LED to reduce its brightness with a resistor. The brightness of the visible LED could also be reduced with a simple filter inserted in the individual reflector cells.

A fan 428 is mounted inside the light source head 106 above the heat sink 426 to draw heat away from the heat sink 426 and the light source PCB 422 for the UV light source 102 and to direct such heat through the vent openings 114 in the rear 117 of the light source housing 202 for heat dissipation. Alternatively, as discussed above, the fan 428 mounted inside the light source head 106 above the heat sink 426 could pull air through the openings 114 in the rear 117 of the light source head 106. Pulled air could be exhausted through the openings 114 in the side 116 to carry heat generated from the light source PCB 422 in the UV light source 102 away from the UV light source 102. As discussed in more detail below, the fan 428 is electronically controlled by the electrical control system 404 to variably control the speed of the fan 428 based on sense temperature in the UV light source 102 to provide sufficient heat dissipation. The fan 428 is mounted inside the light source housing 202 through fasteners 425 that are extended through openings 427 in the rear 117 of the light source housing 202. The interior chamber 429 created by the light source housing 202 also provides additional spaces that can further facilitate the dissipation of heat. Note that the interface area 430 between the handle 118 and the light source housing 202 is a closed-off space by the presence of the light source PCB 422 and internal walls 432, 434 of the light source housing 202 and light source housing cover 204.

Also, as shown in FIG. 4A, the UV light emission device 100 includes a haptic feedback device 435 in the handle 118 that is coupled to the electrical control system 404. As discussed in more detail below, the electrical control system 404 is configured to activate the haptic feedback device 435 to apply a vibratory force to the handle 118 under certain conditions and operational modes of the UV light emission device 100. The vibratory force will be felt by a human user who is holding the handle 118 to control and manipulate the UV light emission device 100 in its normal, operational use. For example, the haptic feedback device 435 can be configured to be controlled by a haptic motor driver (shown in FIG. 5 below) in the electrical control system 404 to spin to cause the haptic feedback device 435 to exert a vibratory force to the handle 118. The electrical control system 404 could cause activate the haptic feedback device 435 to create different sequences of vibratory force as different indicators or instructions to a human user of the UV light emission device 100, such as various error conditions.

FIG. 4B also shows the raised outer edges 436, 438 of the light source housing cover 204 that then create an internal compartment for the light source shield 108 to be inserted and fit inside to be mounted to the light source housing cover 204 in front of the direction of emission of light from the UV light source 102. An optional screen 439 (e.g., metal screen) can also be provided and fit between the light source shield 108 and the light source housing cover 204 to further protect the UV light source 102 and/or to provide a sacrificial surface. The optional screen 439 includes openings 441 that align with the UV LEDs 110 in the UV light source 102. An adhesive or tape (e.g., a double-sided tape) can be used to secure the light source shield 108 to the optional screen 439. Thus, for example, if the light source shield 108 is made of glass and it breaks, the glass shield will remain in place and attached to the optional screen 439 for safety reasons.

Also, as discussed earlier, in addition, or alternatively to providing the light source shield 108, the parabolic reflectors 424 could be provided to have an opening or aperture 441 of diameter D3(1) as shown in FIG. 4B. The light from the respective UV LEDs 110 and visible light 208(1)-208(4) is emitted towards the respective aperture 441 of the parabolic reflectors 424. The diameter D3 of the apertures 441 of the parabolic reflectors 424 can be sized to be smaller than the diameter of a typical, smaller-sized human finger. For example, the diameter D3 of the aperture 441 could be 0.5 inches or smaller. This would prevent a human from being able to put their finger or other appendages inside the opening 441 of the parabolic reflectors 424 in direct contact with the UV LEDs 110 and/or the visible light 208(1)-208(4) for safety reasons. This may allow a separate light shield, like light source shield 108, to not be used or required to provide the desired safety of preventing direct human contact with the UV LEDs 110 and visible light 208(1)-208(4).

Note that the diameter of the parabolic reflectors 424 decreases from the aperture 441 back to where the actual position of the UV LEDs 110 or visible light 208(1)-208(4) is disposed within the parabolic reflectors 424. Thus, even if the diameter D3(1) of the aperture 441 has a large enough opening to receive a human finger or other parts, the reducing internal diameter of the parabolic reflectors 424 may still prevent a human finger or other parts from reaching and contacting the UV LEDs 110 or visible light 208(1)-208(4) within the parabolic reflectors 424. For example, as shown in FIG. 4B, the diameter D3(2) of the parabolic reflectors 424 is less than the diameter D3 of their apertures 441. The diameter D3(2) of the parabolic reflectors 424 still located a distance away from the UV LEDs 110 or visible light 208(1)-208(4) is disposed within the parabolic reflectors 424 may also be small enough to prevent human finger or other parts from reaching and contacting the surface of the UV LEDs 110 or visible light 208(1)-208(4).

As further shown in FIG. 4C, the handle 118 is comprised of two handle members 440, 442 that come together in clamshell-like fashion and are fitted together by fasteners 444 through openings in the handle member 442 to be secured to the handle member 440. As previously discussed, the two handle members 440, 442 have internal openings such that an interior chamber is formed inside the handle 118 when assembled for the ribbon cable 412 (see FIG. 4A) of the wiring harness and secondary switch 120. Similarly, as shown in FIG. 4C, the light source housing cover 204 is secured to the light source housing 202 through fasteners 448 that are inserted into openings in the light source housing cover 204. The fasteners 448 can be extended through openings 450 in the visible light ring 148 and openings 452 in the light source PCB 422 and into openings in the light source housing 202 to secure the light source housing cover 204 to the light source housing 202.

As discussed above, the UV light emission device 100 includes an electrical control system 404 that is on one or more PCBs and housed in the base housing 126 to provide the overall electronic control of the UV light emission device 100. In this regard, FIG. 5 is a schematic diagram of the exemplary electrical control system 404 in the UV light emission device 100 in FIGS. 1A-1C. As will be discussed below, the electrical control system 404 includes safety circuits, power distribution circuits for controlling the distribution of power to the light driver circuits 400(1)-400(6) and the UV light source 102, and other general circuits. As shown in FIG. 5, the electrical control system 404 includes an external power interface 500 that is configured to be coupled to the electrical cable 136 that is electrically coupled to a battery 142 as a power source (e.g., 44.4 Volts (V)). As previously discussed, the battery 142 may be external to the UV light emission device 100 or alternatively integrated within the UV light emission device 100. A power signal 504 generated by the battery 142 is electrically received by an input power rail 506 controlled by inline primary switch 122 (see FIGS. 1A-1C) into three (3) DC-DC regulator circuits 508(1)-508(3) to provide different voltage levels to different voltage rails 510(1)-510(3) since different circuits in the electrical control system are specified for different operation voltages, which in this example are 15V, 12V, and 3.3V, respectively. For example, the battery 142 may be a rechargeable Lithium-Ion battery rated at 44.4V, 6.4 Ah manufactured by LiTech. As another example, the battery 142 may be a 14.4 VDC nominal 143 W/hr. battery manufactured by IDX. The electrical control system 404 may also have battery overload and reserve battery protection circuits. The input power rail 506 is also coupled to a safety switch 512, which may be a field-effect-transistor (FET). The safety switch 512 is configured to pass the power signal 504 to a power enable circuit 530 (e.g., a power switch) in response to a power safety signal 516 generated by a safety circuit 518, indicating either a power safe or power unsafe state independent of any software-controlled device, such as a microprocessor controller circuit as discussed below, as a failsafe mechanism. The safety circuit 518 is configured to receive a power signal 520 indicating an enable or disable state from a detect latch 522 that is controlled by a controller circuit 524, which is a microcontroller in this example, to latch a latch reset signal 526 as either a power safe or power unsafe state. As will be discussed below, the controller circuit 524 is configured to set the detect latch 522 to a power safe state when it is determined that it is safe to distribute power in the UV light emission device 100 to the light driver circuits 400(1)-400(6) to distribute power to the UV light source 102. When it is desired to discontinue power distribution to the light driver circuits 400(1)-400(6), the controller circuit 524 is configured to generate the latch reset signal 526 to a latch reset state as a power unsafe state. The detect latch 522 is configured to default to a power unsafe state on power-up of the electrical control system 404.

As also shown in FIG. 5, the safety switch 512 is also controlled based on a power regulator circuit 528 that is configured to pull the power safety signal 516 to ground or a power rail voltage to indicate either the power safe or power unsafe state to control the safety switch 512. Thus, if there are any voltage irregularities on the input power rail 506 or from the DC-DC regulator circuits 508(1)-508(3), the power regulator circuit 528 is configured to generate the power safety signal 516 in a power unsafe state to disable the safety switch 512 and interrupt power distribution from the input power rail 506 to a power enable circuit 530 as a safety measure. Note that the safety circuit 518 and the power regulator circuit 528 are configured to generate the power safety signal 516 irrespective of whether the controller circuit 524 is operational as a safety measure and in case the controller circuit 524 discontinues to operate properly. This is because it is desired in this example to detect fault conditions with regard to any voltage irregularities on the input power rail 506 or from the DC-DC regulator circuits 508(1)-508(3) when power is first turned on to the UV light emission device 100, and before the controller circuit 524 starts up and becomes operational as a hardware circuit-only safety feature.

The safety circuit 518 in this example also receives an analog over-temperature signal 531 and a watchdog reset signal 539 as additional mechanisms to cause the safety circuit 518 to generate the power safety signal 516 in a power unsafe state to disable the safety switch 512 from distributing the power signal 504, even if the controller circuit 524 is not operational. For example, the controller circuit 524 includes a watchdog timer circuit 532 that is configured to be updated periodically by the controller circuit 524 from an output signal 541, and if it is not, the watchdog timer circuit 532 times out and generates a watchdog reset signal 539 to restart the controller circuit 524. The watchdog reset signal 539 is also provided to the safety circuit 518 to cause the safety circuit 518 to generate the power safety signal 516 in a power unsafe state to disable the safety switch 512 from distributing the power signal 504 when the controller circuit 524 becomes or is non-operational, and until the controller circuit 524 is successfully rebooted and operational. The safety circuit 518 is also configured to generate the power safety signal 516 in a power unsafe state to disable the safety switch 512 from distributing the power signal 504 when an overall temperature condition at the UV light source 102 is detected via the analog over-temperature signal 531 generated by the temperature sensor circuit 536 described below.

It is also desired for the controller circuit 524 to also be able to control enabling and disabling of power distribution of the power signal 504. For example, the controller circuit 524 includes a trigger signal 535 from the secondary switch 120 that indicates a power enable state (e.g., a logic ‘1’ value) when the secondary switch 120 is engaged and a power disable state (e.g., a logic ‘0’ value) when the secondary switch 120 is not engaged. As discussed above, the secondary switch 120 is configured to be engaged by a user when using the UV light emission device 100 to control when the UV light source 102 is activated or de-activated. In this regard, the power enable switch 530 is provided, which may be a FET. The power enable switch 530 is coupled between the safety switch 512 and the light driver circuits 400(1)-400(6) to control power distribution to the light driver circuits 400(1)-400(6). The power enable switch 530 is under the sole control of the controller circuit 524 to provide another mechanism to control power distribution of the power signal 504 to the light driver circuits 400(1)-400(6) driving the UV light source 102. In this manner, as discussed in more detail below, a software algorithm executed in software or firmware by the controller circuit 524 can control the enabling and disabling of power distribution of the power signal 504 to the light driver circuits 400(1)-400(6) based on a number of conditions detected by input signals. In this regard, the controller circuit 524 is configured to generate a power enable signal 533 to the power enable switch 530 of a power enable or power disable state. For example, the controller circuit 524 is configured to receive power input signals 534(1)-534(3) that can be coupled to the voltage rails 510(1)-510(3) to detect if the DC-DC regulator circuits 508(1)-508(2) are distributing their expected voltages in addition to the power regulator circuit 528 that does not involve the controller circuit 524. In response to the power enable signal 533 being a power enable state, the power enable switch 530 is configured to distribute the received power signal 504 to the light driver circuits 400(1)-400(6).

With continuing reference to FIG. 5, a driver enable circuit 537 is also provided that controls a driver enable signal 538 in either a driver enable state or driver disable state. The driver enable signal 538 is coupled to the light driver circuits 400(1)-400(4) to control the activation or deactivation of the light driver circuits 400(1)-400(4). If the driver enable signal 538 is in a power disable state, the light driver circuits 400(1)-400(4) will be disabled and not drive power to the UV light source 102 regardless of whether or not the power enable switch 530 distributes the power signal 504 to the light driver circuits 400(1)-400(4). The driver enable circuit 537 is coupled to a light enable signal 543 generated by the controller circuit 524 and a trigger signal 535, which must both indicate a power enable state for the driver enable circuit 537 to generate the driver enable signal 538 (DRIVER ENABLE) of a power enable state to enable the light driver circuits 400(1)-400(4).

With continuing reference to FIG. 5, the controller circuit 524 is also configured to generate a visual feedback signal 540 to the visual status indicator 143 (see FIG. 1C) to control the operational mode, color, and pulse pattern of light emitted by the visual status indicator 143. The controller circuit 524 is also configured to generate a fan control signal 542 to a fan control switch 544 to control operation of the fan 428 in the UV light source 102 to dissipate heat generated by the UV light source 102. The controller circuit 524 can pulse-width-modulate the fan control signal 542 provided to the fan control switch 544 to control the speed of the fan 428. The electrical control system 404 also includes an inertial measurement unit (IMU) circuit 546 that includes an accelerometer circuit. The IMU is configured to generate an accelerometer or orientation signal 548 to the detect latch 522 and the controller circuit 524. For example, the IMU circuit 546 may be the MMA84511Q digital accelerometer by NXP Semiconductors. The IMU circuit 546 may be programmed over a communication bus 549 (e.g., an I2C communications bus) to generate the accelerometer or orientation signal 548 based on the UV light emission device 100 exceeding a given acceleration and/or angle or orientation as a safety feature. For example, the accelerometer or orientation signal 548 may indicate an initialize state, a test ok state indicating a current is sensed in a test state, an ok state indicating current is sensed in an operational state or an error state. For example, the accelerometer or orientation signal 548 may be in an error state if the UV light emission device 100 is dropped or rotated by a user beyond a programmed allowable angle based on acceleration or orientation of the UV light emission device 100. If the accelerometer or orientation signal 548 is in an error state, this causes the detect latch 522 to register the error condition to cause the controller circuit 524 to disable the power enable switch 530 to discontinue distribution of the power signal 504 to the light driver circuits 400(1)-400(4).

The IMU circuit 546 can also be configured to generate an acceleration (or force) signal 548 to indicate the amount of g-force imposed on the UV light emission device 100 as a drop detect safety feature, for example. If the g-force on the UV light emission device 100 is detected by the electronic control system 404 to exceed a defined force threshold level, the detect latch 522 can be activated to register this error condition and inform the controller circuit 524. The controller circuit 524 can disable the UV light emission device 100 if desired, for example. This detected error condition in the detect latch 522 could cause the controller circuit 524 to disable the power enable switch 530 to discontinue distribution of the power signal 504 to the light driver circuits 400(1)-400(4) so that light is not emitted from the UV light source 102. In one example, the IMU circuit 546 is configured to generate the force signal 547 to cause the detect latch 522 to register the drop detection error if the g-force measured exceeds 7G. 7G of force was found to be the equivalent of an approximate two (2) foot drop of the UV light emission device 100. For example, FIG. 6 is a diagram illustrating control of operation of the UV light emission device 100 in FIGS. 1A-1C based on orientation of the UV light emission device 100 detected by the IMU circuit 546 in the electrical control system 404 in FIG. 5. As shown in FIG. 6, the UV light emission device 100 is shown moving in an X-Z plane, where Z is a height direction from the ground and X is a horizontal direction parallel to the ground. In this example, the IMU circuit 546 detects the angular orientation, which is shown as the light source head 106 between 0 and 90 degrees. In this example, the controller circuit 524 is configured to continue to generate the power enable signal 533 in a power enable state if the IMU circuit 546 detects the angular orientation, which is shown as the light source head 106 between 0 and 90 degrees. When the controller circuit 524 detects that the angular orientation of the UV light emission device 100 is more than five (5) degrees beyond its permitted angular range of 0 to 90 degrees (or 95 degrees from the Z plane parallel to ground), in this example, the controller circuit 524 is configured to generate the power enable signal 533 in a power disable state to disable the power enable switch 530 to disable power distribution of the power signal 504 to the light driver circuits 400(1)-400(4), as shown in FIG. 5.

With reference back to FIG. 5, the electrical control system 404 also includes the light driver circuits 400(1)-400(6). As previously discussed, in this example, the light driver circuits 400(1)-400(3) are provided on a first light driver PCB 402, and the light driver circuits 400(4)-400(6) are provided on a second light driver PCB 403 (see also, FIG. 2). The light driver circuits 400(1)-400(6) are configured to generate current signals 550(1)-550(6) on current outputs 551(1)-551(6) to respective light strings 206(1)-206(6) and a driver circuit 552(1)-552(6) that drives the visible light indicators 423 configured to emit light to the visible light ring 148. In this example, the respective light strings 206(1)-206(6) and visible light indicators 423 are coupled to the same node that is coupled to the respective current outputs 551(1)-551(6) so that it is guaranteed that the visible light indicators 423 will receive current 553 if the respective light strings 206(1)-206(6) receive current 553 for safety reasons. For example, the visible status indicator 143 may be the SunLED right angle SMD chip LED, Part XZFBB56 W-1. In this manner, the user will be able to visibly detect light emanating from the visible light ring 148 when the light strings 206(1)-206(6) are emitting the UV light 104. As a safety mechanism, a current sense circuit 554(1)-554(6) is provided for each light driver circuit 400(1)-400(6) to sense the current signals 550(1)-550(6) generated on the current outputs 551(1)-551(6) by the light driver circuits 400(1)-400(6). The current sense circuits 554(1)-554(6) are each configured to generate current sense signals 556(1)-556(6) on the communication bus 549 to be received by the controller circuit 524 to determine if the light driver circuits 400(1)-400(6) are operational as a diagnostic feature. For example, if a LED in the light string 206(1)-206(6) has failed, causing an open circuit, this can be detected by the lack of current in the current sense signals 550(1)-550(6). This will cause the overall current in the current signal 550(1)-550(6) to change. For example, the current sense signals 556(1)-556(2) may indicate an initialize state, a test ok state indicating a current is sensed in a test state, an ok state indicating current is sensed in an operational state or an error state. For example, the controller circuit 524 can be configured to determine if the current signal 550(1)-550(6) changed in current based on the received the current sense signals 556(1)-556(6) on the communication bus 549. The controller circuit 524 can be configured to detect an open circuit if the current drops by more than a defined threshold amount of current.

In certain embodiments, the controller circuit 524 is configured to cause a respective LED driver circuit 400(1)-400(6) to automatically compensate for an open circuit in the UV LEDs 110 and visible lights 208(1)-208(4) in a respective light string 206(1)-206(6) of the UV light source 102. As discussed above with regard to FIG. 7, each light string 206(1)-206(6) has three (3) LEDs, which either all UV LEDs 100 or a combination of the UV LEDs 110 and visible light indicator 208, connected in series with another series-connected three (3) LEDs 110, 208 of all UV LEDs 100 or a combination of the UV LEDs 110. The light strings 206(1)-206(6) are connected in parallel. If UV LEDs 100 or a visible light indicator 208 in a three (3) LED, series-connected string incurs an open circuit, the controller circuit 524 can detect this condition by the current drop as discussed above. The current/voltage sense ICs 854(1)-854(6) and/or the controller circuit 524 can be configured to automatically compensates for the loss of a three (3) LED series-connected string that has an open circuit light string 206(1)-206(6) by increasing (e.g., doubling) the current signals 550(1)-550(6) the parallel three (3) series connected LED string in the same light string 206(1)-206(6) to maintain the same output energy in a given light string 206(1)-206(6). Each parallel LED string in the light string 206(1)-206(6) has a constant current source. Thus, normally, 50% of the current in current signals 550(1)-550(6) will flow in each parallel LED string. If one of parallel LED strings becomes open circuited, then 100% of the current of a respective current signal 550(1)-550(6) from a respective LED driver circuit 400(1)-406(6) will flow in the other remaining parallel LED strings in a given light string 206(1)-206(6). The optical output power emitted by a parallel LED string is directly proportional to current in the respective current signal 550(1)-550(6) so the optical output of the remaining parallel LED string in a given light string 206(1)-206(6) will compensate for the open-circuited parallel LED string. If parallel LED strings in a given light string 206(1)-206(6) have an open circuit, an error condition would be generated by the controller circuit 524.

Temperature sensor circuits 558(1)-558(6) are also provided in the UV light source 102 and are associated with each light string 206(1)-206(6) to detect temperature of the light strings 206(1)-206(6) based on their emitted light as driven by the current signals 550(1)-550(6) from the light driver circuits 400(1)-400(6). The temperature sensor circuits 558(1)-558(6) are configured to generate temperature detect signals 560(1)-560(6) on the communication bus 549 to be received by the controller circuit 524 to detect over-temperature conditions in the UV light source 102. For example, the temperature detect signals 560(1)-560(6) may indicate an initialize state, a test ok state indicating a current and voltage is sensed in a test state, an ok state indicating current and voltage is sensed in an operational state, or an error state. The controller circuit 524 is configured to control the power enable switch 530 to discontinue power distribution to the light driver circuits 400(1)-400(6) in response to detecting an over-temperature condition. Also, the temperature detect signals 560(1)-560(6) may be provided to the safety circuit 518 to allow the safety circuit 518 to disable the safety switch 512 to disable power distribution independent of the controller circuit 524 being operational. The temperature sensor circuits 536(1) may be configured for the temperature threshold to be set or programmed.

It is also noted that memory may be provided in the electrical control system 404 in FIG. 5 to record conditions present. For example, the memory may be a non-volatile memory (NVM). For example, the controller circuit 524 may include an NVM 562 on-chip that can be used to record data that can later be accessed. For example, a USB port 564 may be provided in the electrical control system 404 that can be interfaced with the controller circuit 524 to access the data in the NVM 562. The electrical control system 404 could also include a Wi-Fi or Bluetooth interface for transfer of data. An Ethernet port could also be provided in addition or in lieu of the USB port 564. This is discussed in more detail below.

FIG. 7 is an electrical diagram of the light strings 206(1)-206(6) in the UV light source 102 in the UV light emission device 100 in FIGS. 1A-1C compatible with the mechanical diagram of the UV light source 102 in FIG. 2. As shown in FIG. 6, each light string 206(1)-206(6) in this example has six (6) LEDs. Light string 206(1) and 206(6) include four UV LEDs 110 and the two (2) visible lights 208(1)-208(2), 208(3)-208(4), respectively, as previously described in FIG. 2. Each light string 206(1)-206(6) is driven by its respective light driver circuit 400(1)-400(6), as previously discussed. As also previously discussed, the light strings 206(1) and 206(6) that include visible lights 208(1)-208(2), 208(3)-208(4) are coupled together in series so that if the UV LEDs 110 in such light strings 206(1), 206(6) receive power to emit light, the visible lights 208(1)-208(2), 208(3)-208(4) will also receive current to emit light as an indicator to the user of the UV light emission device 100 as a safety feature.

FIG. 8 is a schematic diagram of another exemplary electrical control system 804 that can be included in the UV light emission device 100 in FIGS. 1A-1C. Shared common components between the electrical control system 804 in FIG. 8 and the electrical control system 404 in FIG. 4 are shown with common element numbers between FIGS. 4 and 8. These common components will not be re-described in FIG. 8.

With reference to FIG. 8, in this example, the electrical control system 804 includes the haptic motor driver 870. A haptic motor driver 870 is coupled to the communication bus 549. As discussed in more detail below, the controller circuit 524 is configured to issue a haptic enable signal 871 to the haptic motor driver 870 to activate the haptic motor driver 870 and to control the spin of the haptic motor driver 870 as desired. The haptic motor driver 870 is coupled to the haptic feedback device 435 outside of the electronic control system 804 and disposed in the UV light emission device 100, as shown in FIG. 4A.

With continuing reference to FIG. 8, in this example, the electronic control system 804 also includes the ability of the controller circuit 524 to control a timer circuit 841, The controller circuit 524 can initiate a timer circuit 841 to increment a counter based on a clock signal. The timer circuit 841 can issue a timer signal 843 to provide a count value of the timer to the controller circuit 524 to maintain one or more counters. For example, the controller circuit 524 can be configured to use the timer signal 843 from the timer circuit 841 to accumulate a total time (e.g., hours) of usage of the UV light source 102 is activated to track its operational age. The total accumulated time representing the operational age of the UV light source 102 can be stored in FRAM NVM 872 and/or NVM 562. The controller circuit 524 could be configured to deactivate the LED driver circuits 406(1)-406(6) and not allow the UV light emission device 100 to be reactivated after the operational age of the UV light source 102 exceeds a defined threshold. An error condition can be generated in this instance by the controller circuit 524 and recorded in a status register in the FRAM NVM 872 and/or the NVM 562. The controller circuit 524 can also use the timer circuit 841 to maintain other counters that can be used for tracking time of tasks and for timeout purposes.

With continuing reference to FIG. 8, in this example, the electronic control system 804 also includes a FRAM NVM 872. The FRAM NVM 872 is located off-chip from the controller circuit 524. The FRAM NVM 872 is coupled to the controller circuit 524 via an interface bus 874. As discussed in more detail below, the FRAM NVM 872 is provided to store data for the UV light emission device 100, such as its serial number, date of last service, usage time, and error codes, etc. This serial number and date of last service can be stored in the FRAM NVM 872 at manufacture or service. The controller circuit 524 is configured to store usage time and error codes in the FRAM NVM 872 at run time. The data in the FRAM NVM 872 can be accessed remotely through the USB port 564, for example.

With continuing reference to FIG. 8, in this example, the fan 428 of the electronic control system 804 can include the ability to generate a tachometer feedback signal 873 that can be provided to the controller circuit 524. The controller circuit 524 can detect the speed of the fan 428 based on the information in the tachometer feedback signal 873 to verify and variably control the fan 428 speed in a closed-loop manner.

With continuing reference to FIG. 8, in this example, the electronic control system 804 includes an LED array PCB 822 that has differences from the LED array PCB 422 in the electronic control system 404 in FIG. 5. In this regard, the LED array PCB 822 also includes a temperature failsafe circuit 876 that is configured to generate a signal to the safety circuit 518 if the detected temperature is outside a desired temperature range. This is because it may be desired to disable the UV light source 102 and/or UV light emission device 100 if its temperature exceeds a temperature outside a designated temperature range for safety reasons. The safety circuit 518 can disable the safety FET 512 in response to a detected temperature by the temperature failsafe circuit 876 outside the desired temperature range.

With continuing reference to FIG. 8, in this example, the LED array PCB 822 of the electronic control system 804 includes the driver circuits 552(1)-552(6) to drive the light strings 206(1)-206(6) as in the electronic control system 404 in FIG. 5. However, in this example, two of the light strings 206(5), 206(6) each include two additional current sources 878(1), 878(2) coupled in parallel to respective visible light indicator 208(1)-208(4), which were previously described. The additional current sources 878(1), 878(2) draw some of the current driven from the respective driver circuits 552(5), 552(6) to the visible light indicator 208(1)-208(4) in the light strings 206(5), 206(6) to regulate or limit their brightness. This is done because, in this example, the current driven to the UV LEDs 110 is also driven to the visible light indicator 208(1)-208(4) as being coupled in series. However, the amount of current desired to be driven to the UV LEDs 110 may be more current than desired to be driven to the visible light indicator 208(1)-208(4). For example, it may be desired to drive more current to the UV LEDs 110 for effective decontamination, whereas that same current level may cause the visible brightness of the visible lights 208(1)-208(4) to be greater than desired. For example, the additional current sources 878(1), 878(2) could be resistors.

With continuing reference to FIG. 8, in this example, the light driver PCBs 402, 403 in the electronic control system 804 are also configured with current/voltage sense circuits 854(1)-854(6) for each respective light string 206(1)-206(6). This is opposed to only including current sense circuits 554(1)-554(6) like in the electronic controls system 404 in FIG. 5. In this manner, as discussed in more detail below, the current/voltage sense circuits 854(1)-854(6) can also detect voltage driven to the respective light strings 206(1)-206(6) to detect a short circuit in the light strings 206(1)-206(6). A current sense resistor 856 is provided between the current/voltage sense circuits 854(1)-854(6) and the light strings 206(1)-206(6). If, for example, a UV LED 110 fails in its light string 206(1)-206(6), creating a short circuit in its respective light string 206(1)-206(6), this failure may not be detectable by the human eye, because the UV LED 110 emits UV light in the non-visible UV spectrum. Current sensing is not used to detect a short circuit in the light strings 206(1)-206(6) because the current signals 550(1)-550(6) driven by the LED driver circuits 400(1)-406(2) to the light strings 206(1)-206(6) does not change. However, a short circuit in a UV LED 110 or visible light indicator 208(1)-208(4) will cause a voltage drop in its light string 206(1)-206(6) that can be detected by sensing voltage. This is because the same voltage is applied in parallel to each of the light strings 206(1)-206(6). Thus, a short circuit in one of the light strings 206(1)-206(6) will present a different resistance in that light string 206(1)-206(6) versus the other light strings 206(1)-206(6), thus cause a different voltage divide across its UV LED 110 and/or visible light indicator 208(1)-208(4).

As discussed above, the electronic control systems 404, 804 in FIGS. 5 and 8 are configured to detect a short circuit in a LED 110, 208 in a light string 206(1)-206(6) of the UV light source 102. The current/voltage sense circuits 854(1)-854(6) are configured to detect a sensed voltage signal 860(1)-860(6) in its respective light string 206(1)-206(6) to detect a short circuit in a light string 206(1)-206(6). This is because a short circuit in a UV LED 110 or visible light indicator 208(1)-208(4) in a given light string 206(1)-206(6) will cause a voltage drop in its respective light string 206(1)-206(6) that can be detected by sensing voltage. This is because the same voltage is applied in parallel to each of the light strings 206(1)-206(6). Thus, a short circuit in one of the light strings 206(1)-206(6) will present a different resistance in that light string 206(1)-206(6) versus the other light strings 206(1)-206(6). However, process and temperature variations can cause the normal voltage drop across the UV LEDs 110 and/or visible light indicator 208(1)-208(4) in a given light string 206(1)-206(6) to vary without a short circuit. Thus, when a current/voltage sense circuit 854(1)-854(6) detects a voltage at a given light string 206(1)-206(6), it is difficult to determine if the change in voltage in a given light string 206(1)-206(6) is normal or the result of a short circuit in the respective light string 206(1)-206(6).

In this regard, in examples disclosed herein, to compensate for a variation in voltage drop across UV LED 110 and/or visible light indicator 208(1)-208(4) in a given light string 206(1)-206(6) due to process and/or temperature variations, the controller circuit 524 in the electronic control system 404, 804 in FIGS. 5 and 8 can be configured to compensate for variability in voltage drop across UV LED 110 and/or visible light indicator 208(1)-208(4) in a given light string 206(1)-206(6) for detecting a short circuit. In this regard, the current/voltage sense circuits 854(1)-854(6) can be configured to measure the voltage at each light string 206(1)-206(6) at manufacture time as a baseline voltage. The measured baseline voltages for each light string 206(1)-206(6) can be stored in a voltage limit table in the NVM 562 and/or FRAM NVM 872. During operation, the controller circuit 524 can then read in the measured baseline voltages from the voltage limit table for each light string 206(1)-206(6) from NVM 562 and/or FRAM NVM 872 and set a threshold voltage value as a percentage change of such measured baseline voltages for detecting a short circuit. Thus, during normal operation of the UV light emission device 100, if the controller circuit 524 determines based on the sensed voltages for the light strings 206(1)-206(6) by the respective current/voltage sense circuits 854(1)-854(6) that the sense voltages deviate beyond the threshold voltage levels calibrated for the respective light strings 206(1)-206(6), the controller circuit 524 can generate a short circuit error and inform the user through an error state as shown in FIG. 9 for example and/or through the haptic feedback device 435.

Now that the exemplary mechanical, electrical, and optical features and components of the exemplary UV light emission device 100 in FIGS. 1A-1C have been discussed, exemplary operational aspects of the UV light emission device 100 are now discussed in more detail with regard to FIG. 9. FIG. 9 is a diagram of the state machine that can be executed by the controller circuit 524 in the electrical control system 404 in FIG. 5 and/or the electrical control system 804 in FIG. 8 and implemented by other components that are not controlled by the controller circuit 524 to control the operation of the UV light emission device 100. In FIG. 9, states are indicated under the “State” column and include “Power On,” “Power-On Self-Test (POST),” “MONITOR,” “RECOVERABLE ERROR,” “BATTERY LOW,” and “LATCHED ERROR” states. The “Power On,” “POST,” “MONITOR,” “RECOVERABLE ERROR,” and “BATTERY LOW” states also have sub-states. The conditions of the communication bus 549 inputs, the failsafe inputs, and the controller circuit 524 outputs are shown with their respective signal names and labels in reference to FIGS. 5 and 8 (for features that are provided by the additional components in FIG. 8). A ‘0’ indicates an error condition present for an input or a disable state for an output. A “1’ indicates no error condition for an input or an enable state for an output. An ‘X’ indicates a don't care (i.e., no concern) condition. An “OK” condition indicates an ok status where no error condition is present. An “INIT” condition indicates that the device for the stated input is in an initialization phase. A “Control” condition for the fan 428 indicates that the controller circuit 524 is controlling the speed of the fan 428 through the fan control signal 542 according to the temperature from the temperature detect signals 560(1)-560(6). Note that for signals that are replicated for different light strings 206(1)-206(6) and light driver circuits 400(1)-400(6), any error in any of these signals is indicated as a ‘0’ condition in the state machine.

With reference to FIG. 9, when the primary switch 122 (FIG. 1A-1C) of the UV light emission device 100 is activated by a user, the UV light emission device 100 is in a “Power On” state as indicated in the “State” column. The state of the trigger signal 535 of the secondary switch 120 (Trigger) is a don't care condition (X). The power enable signal 533, the light enable signal 543, and fan control signal 542 are in a disable state automatically upon initialization as indicated by a ‘0’ in the “Power On” state to disable the UV light source 102 and since the controller circuit 524 is not yet operational in the “Power On” state. The current sense signals 556(1)-556(2), the temperature detect signals 560(1)-560(6), and the accelerometer or orientation signal 548 are in an initialization (INIT) state for testing. The fail-safe inputs of power input signals 534(1)-534(3), the analog over-temperature signal 531, the watchdog reset signal 537, the force signal 547, and the timeout signal 843 are treated as don't care situations (X) in the “Power On” state, because the latch reset signal 526 is initially set to a power unsafe state (logic state ‘1’) to disable the safety switch 512 from distributing the power signal 504 as shown in FIGS. 5 and 8. The power enable signal 533 is set to a power disable state (logic ‘0’) to prevent distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state. The visual status indicator 143 will be pulsed between red, yellow, and green colors to indicate the “Power On” state visually to the user. The trigger signal 535 of the secondary switch 120 indicates a ‘1’ value in the +Trigger substate of the “Power On” state when the secondary switch 120 is engaged.

The controller circuit 524 will next transition to the “POST” state if the current sense signals 556(1)-556(2), the temperature sensor circuits 558(1)-558(6), and accelerometer or orientation signal 548 indicate a TEST_OK status meaning that their respective current sense circuits 554(1)-554(6), temperature detection circuits, and the IMU circuit 546 are detected as operational. The fan control signal 542 is controlled as indicated by the “Control” state to activate the fan 428 after the “Power On” state.

With continuing reference to FIG. 9, in the “POST” state, the controller circuit 524 determines if the UV light emission device 100 has any errors or failures on the voltage rails 510(1)-510(3) or if the temperature exceeds a designed threshold temperature in the UV light source 102. The controller circuit 524 receives and analyzes the power input signals 534(1)-534(3) and the analog over-temperature signal 531. If the controller circuit 524 determines if the power input signals 534(1)-534(3) indicate the voltage rails 510(1)-510(3) have their expected voltages from the DC-DC regulator circuits 508(1)-508(2) as indicated by a logic ‘1’ state and if the analog over-temperature signal 531 generated by the temperature sensor circuit 536 indicates a temperature below the preset temperature threshold as indicated by the logic ‘1’ state, the controller circuit 524 enters a “Post-OK” sub-state of the “POST” state. The latch reset signal 526 is set to a power save condition (logic ‘0’) to allow the power enable switch 530 to enable distribution of the power signal 504 to the light driver circuits 400(1)-400(6). However, the power enable signal 533 is set to a power disable state (logic ‘0’) to prevent distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state. In the “Post-OK” sub-state, the visual status indicator 143 will be solid green in colors to indicate the “Post-OK” sub-state visually to the user that no errors have yet been detected, and the controller circuit 524 will enter the “MONITOR” state for normal operation. The controller circuit 524 activates the haptic motor driver 870 to activate the haptic feedback device 435 to the user if the user engages the secondary switch 120.

However, if the controller circuit 524 determines if the power input signals 534(2)-534(3) indicate the voltage rails 510(2)-510(3) have their expected voltages from the DC-DC regulator circuits 508(2)-508(3) as indicated by a logic ‘1’ state, and if the analog over-temperature signal 531 generated by the temperature sensor circuit 536 determines the power input signal 534(1) for voltage rail 510(1) is lower than expected in the “POST” state, this is an indication of the battery 142 having a low charge. In response, the controller circuit 524 enters the “Battery Low” sub-state of the “POST” state. In the “Battery low” sub-state of the “POST” state, the visual status indicator 143 will pulse in a pattern of off-red-red states to indicate the “Post OK” sub-state visually, thus indicating the low battery condition to the user. The latch reset signal 526 is still set to a power safe condition (logic ‘0’) to allow the power enable switch 530 to enable distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation. However, the power enable signal 533 is set to a power disable state (logic ‘0’) to prevent distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state. The controller circuit 524 then enters the “BATTERY LOW” state and remains in this state until the UV light emission device 100 is powered down by switching off the primary switch 122 and repowering the UV light emission device 100 to start up in the “Power On” state. If the battery 142 is not changed or recharged, the UV light emission device 100 will enter the “BATTERY LOW” state again after power-up.

If in the “Post-OK” sub-state of the “POST” state, the controller circuit 524 determines that a power input signal 534(2)-534(3) indicates its voltage rail 510(2)-510(3) does not have the expected voltages from the DC-DC regulator circuits 508(2)-508(3), or the analog over-temperature signal 531 generated by the temperature sensor circuit 536 is above its defined threshold limit, as indicated by the “ERROR” condition in the “Post error” rows in FIG. 9, this is an indication of a failsafe error condition in which the UV light source 102 of the UV light emission device 100 should not be allowed to operate. In response, the power enable signal 533 is set to a power disable state (logic ‘0’) to prevent distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state, and the controller circuit 524 enters a “LATCHED ERROR” state. The controller circuit 524 activates the haptic motor driver 870 to activate the haptic feedback device 435 to the user to indicate the error condition if the secondary switch 120 is engaged by the user as shown in the “error+trig” substate of the “POST” state. In the “LATCHED ERROR” state, the visual status indicator 143 will pulse in pattern of red-off-red states to indicate the “LATCHED ERROR” state. The controller circuit 524 remains in the “LATCHED ERROR” state until the UV light emission device 100 is powered down by switching off the primary switch 122 and repowering the UV light emission device 100 to start up in the “Power On” state.

In the “MONITOR” state, the UV light emission device 100 is ready to be operational to distribute power to the UV light source 102 to emit the UV light 104. This is shown in the “Monitor (ready)” sub-state in FIG. 8, where all signals indicate no error conditions, except that the trigger signal 535 of the secondary switch 120 (Trigger) indicates that the secondary switch 120 is not engaged by a user. Thus, the controller circuit 524 still sets the power enable signal 533 to a power disable state (logic ‘0’) to prevent distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state. The latch reset signal 526 was previously latched in a power safe condition (logic ‘0’) to allow the power enable switch 530 to enable distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation once the power enable signal 533 is set to a power enable state (logic ‘1’). In the “Monitor (ready)” sub-state of the “MONITOR” state, the visual status indicator 143 will be generated in a pattern of solid green in color to indicate the “ready” sub-state visually to the user.

Once the trigger signal 535 of the secondary switch 120 (Trigger) indicates that the secondary switch 120 is engaged by a user, the controller circuit 524 enters the “Monitor (trigger+OK)” sub-state of the “MONITOR” state. The power enable signal 533 is set to a power enable state (logic ‘1’) to enable the safety switch 512 to distribute the power signal 504 to the light driver circuits 400(1)-400(6) for operation. The light enable signal 543 is also set to a power enable state (logic ‘1’) to allow the power enable switch 530 to distribute the power signal 504 to the light driver circuits 400(1)-400(6) for operation in this state. In the “Monitor (trigger+OK)” sub-state of the “MONITOR” state, the visual status indicator 143 will be generated in a pattern of solid green in color to visually indicate the operation “ok” status to the user. The UV light emission device 100 will remain in the “MONITOR” state in the “Monitor (trigger+OK)” sub-state or the “Monitor (ready”) sub-state until an error occurs or until the UV light emission device 100 is turned off by the primary switch 122.

The UV light emission device 100 will go into the “MONITOR” state in the “Monitor (trigger+OK+timeout)” sub-state if the UV light emission device 100 has been activated by the secondary switch 120 for too long such that a time out has occurred. In the “Battery low” sub-state of the “POST” state, the visual status indicator 143 will pulse in a pattern of yellow, yellow, off states in this example to indicate to the user to release the secondary switch 120. The controller circuit 524 activates the haptic motor driver 870 to activate the haptic feedback device 435 to the user if the user engages the secondary switch 120.

In the “MONITOR” state, if the controller circuit 524 detects through a timer circuit 841 that the secondary switch 120 has been engaged continuously for more than a defined period of time (e.g., 5 minutes), the controller circuit 524 will enter the “Monitor (trigger+OK+ON-Time)” sub-state. For example, this may be an indication that the secondary switch 120 is being engaged accidentally without an intent by a user to engage, or it may be desired to only allow emission of UV light 104 for a defined period of time without a further disengagement and reengagement of the secondary switch 120 to prevent battery run down. The power enable signal 533 is set to a power disable state (logic ‘1’) to disable the safety switch 512 to halt distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation. The light enable signal 543 is also set to a power disable state (logic ‘1’) to disable the power enable switch 530 distributing the power signal 504 to the light driver circuits 400(1)-400(6). The controller circuit 524 will go to the “MONITOR (ready)” sub-state, which will then require a release of the secondary switch 120 and a reengagement of the secondary switch 120 to enter into the “RECOVERABLE ERROR” state to be able to recover once the secondary switch 120 is released and activated again to reactivate the UV light source 102.

In the “MONITOR” state, if the accelerometer or orientation signal 548 generated by the IMU circuit 546 indicates an acceleration or tilt condition that is outside the programmed operational range of the UV light emission device 100, the controller circuit 524 will enter the “Monitor (trigger+tilt)” sub-state. The power enable signal 533 is set to a power disable state (logic ‘1’) to disable the safety switch 512 to halt distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation. The light enable signal 543 is also set to a power disable state (logic ‘1’) to disable the power enable switch 530 distributing the power signal 504 to the light driver circuits 400(1)-400(6). The visual status indicator 143 will be generated in a pattern of green-off-green color to indicate the operation “ok” status, but tilt orientation visually to indicate to the user. The controller circuit 524 then goes into the “RECOVERABLE ERROR” state either in the “RECOVERABLE ERROR (trigger)” sub-state (if the secondary switch 120 is engaged) or “RECOVERABLE ERROR (trigger released)” sub-state (when the secondary switch 120 is released). The controller circuit 524 will go to the “RECOVERABLE ERROR (trigger released)” sub-state once the secondary switch 120 is released and no other errors are present. The visual status indicator 143 is also caused to emit a mostly yellow color state followed by a short off state in this example to signify the recoverable error to the user in the “RECOVERABLE ERROR” state. The controller circuit 524 will go to the “MONITOR (ready)” sub-state thereafter if no other errors are present to allow the user to reengage the secondary switch 120 to cause the UV light 104 to be emitted as discussed for this sub-state as discussed above.

Also, while in the “MONITOR” state, if the controller circuit 524 determines that the power input signal 534(1) for voltage rail 510(1) is lower than expected in the “POST” state, this is an indication of the battery 142 having a low charge. In response, the controller circuit 524 enters the “Monitor (battery low+OK)” sub-state of the “MONITOR” state. The power enable signal 533 is set to a power disable state (logic ‘1’) to disable the safety switch 512 to halt distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation. The light enable signal 543 is also set to a power disable state (logic ‘1’) to disable the power enable switch 530 distributing the power signal 504 to the light driver circuits 400(1)-400(6). The visual status indicator 143 will be generated in a pattern of off-off-red in color to indicate to the user that the battery is low. The controller circuit 524 activates the haptic motor driver 870 to activate the haptic feedback device 435 to the user if the user is engaging the secondary switch 120 in the “battery low+OK+Trig” substate of the “MONITOR” state. The controller circuit 524 then goes into the “BATTERY LOW” state and will remain in the “BATTERY LOW” state until the UV light emission device 100 is turned off by primary switch 122 and repowered to go back into the “Power On” state. If the battery 142 is not changed, the UV light emission device 100 will enter the “BATTERY LOW” state again after powering up. The visual status indicator 143 is also caused to emit a mostly off state followed by a short red color emission in this example to signify the battery low error to the user in the “BATTERY LOW” state.

Also, while in the “MONITOR” state, if the controller circuit 524 determines that any other error has occurred based on the failsafe inputs or the communication bus 549 inputs as previously described in regard to FIG. 5 or 8, the controller circuit 524 enters the “Monitor (error or Dropped)” sub-state of the “MONITOR” state. The power enable signal 533 is set to a power disable state (logic ‘1’) to disable the safety switch 512 to halt distribution of the power signal 504 to the light driver circuits 400(1)-400(6) for operation. The light enable signal 543 is also set to a power disable state (logic ‘1’) to disable the power enable switch 530 distributing the power signal 504 to the light driver circuits 400(1)-400(6). The visual status indicator 143 will be generated in a pattern of red-off-red in color to indicate the operation “ok” status to indicate to the user that the battery is low. The controller circuit 524 activates the haptic motor driver 870 to activate the haptic feedback device 435 to the user if the user is engaging the secondary switch 120 in the “error or Dropped+Trig” substate of the “MONITOR” state.

The controller circuit 524 will go into the “LATCHED ERROR” state and will remain in the “LATCHED ERROR” state until the UV light emission device 100 is turned off by primary switch 122 and repowered to go back into the “Power On” state. A power cycle is required in this example to reset the UV light emission device 100 for the UV light source 102 to be able to be operational again. The visual status indicator 143 is also caused to emit three (3) rapid red color states followed by three (3) slow flashing red color states in this example to signify the latched error to the user in the “LATCHED ERROR” state.

FIG. 10 illustrates the illumination modes of the visual status indicator 143 by the controller circuit 524 in FIGS. 4 and 8 for normal operating states of “POWER ON,” “POST,” and “MONITOR” in FIG. 9. FIG. 10 also illustrates the illumination modes of the visual status indicator 143 by the controller circuit 524 in FIGS. 5 and 8 for error operating states of “TILT ERROR, “BATTERY LOW,” and “LATCHED ERROR” in FIG. 9. FIG. 10 illustrates the illumination modes of the visual status indicator 143 by the controller circuit 524 in FIGS. 4 and 8 to be able to indicate the software revision number of the software executed by the controller circuit 524.

As discussed above, the electrical control system 404 in FIGS. 5 and 8 may include memory accessible to the controller circuit 524 to record conditions and history of events for the UV light emission device 100. For example, the controller circuit 524 may include the NVM 562 on-chip and FRAM NVM 872 (FIG. 8) that can be used to record data that can later be accessed. As shown in FIG. 8, in this example, the controller circuit 524 is configured to update counters in the NVM 562 for a defined number of events. These events are a drop of the UV light emission device 100 as indicated by the acceleration signal 547, tilt of the UV light emission device 100 as indicated by the accelerometer or orientation signal 548, current sense errors as indicated by the current sense circuits 554(1)-554(6), power supply errors as indicated by the power input signals 534(1)-534(3), communication bus 549 errors, power enable errors, as indicated by the power, enable signal 533 being generated in a power disable state, temperature errors as indicated by the temperature detect signals 560(1)-560(6), the recoverable errors as indicated by the accelerometer or orientation signal 548, and total accumulated minutes of use. FIG. 8 shows this data that can be recorded by the controller circuit 524 in the NVM 562 and the byte format of such. This recorded data can be accessed through a communication port provided to the controller circuit 524 and can be accessed by an external device via a coupling to the communication port. The NVM 562 can also include a circular buffer that is used to record error codes that are generated by the controller circuit 524 based on detected errors.

Now that exemplary components and states of the UV light emission device 100 have been described, exemplary hardware circuits and processes for the operation of the UV light emission device 100 that can include the electronic control system 404 in FIG. 5 or the electronic control system 804 in FIG. 8, for example, will now be described below.

FIG. 11 is a diagram illustrating the IMU circuit 546 operation in the UV light emission device in the electronic control systems 404, 804 in FIGS. 5 and 8. An IMU integrated circuit (IC) 1100 in the IMU circuit 546 is initialized by the controller circuit 524 through an IMU interface module 1102 coupled to the communications bus 549 with programming in the power-on state with the threshold force to be detected for drop detection of the UV light emission device 100. The IMU IC 1100 is configured to issue an interrupt 1104 in response to detecting a g-force exceeding the threshold force. In response to the interrupt 1104, the detect latch 522 is enabled to disable the light emission from the UV light source 102 of the UV light emission device 100 as previously described.

The interrupt 1104 is also communicated to the controller circuit 524 through an IMU interface module 1102 coupled to the communication bus 549. The controller circuit 524 can react in response to the interrupt 1200 based on the operational state in FIG. 9.

FIG. 12 is a diagram illustrating the haptic motor driver 870 and haptic feedback device 435 in the UV light emission device 100 in the electronic control systems in FIGS. 5 and 8. A haptic integrated circuit (IC) 1200 in the haptic motor driver 870 controls the haptic feedback device 435. The haptic IC 1200 is coupled to a haptic interface module 1202 to communicate commands from the controller circuit 524 to the haptic motor driver 870 to control the haptic feedback device 435. As discussed in the operational state in FIG. 9, the controller circuit 524 is configured to activate the haptic motor driver 870 in response to tilt detection or another error state.

The controller circuit 524 in the electronic control systems 404, 804 in FIG. 5 and FIG. 8 can also be configured to dynamically adjust the power in the current signals 550(1)-550(6) overtime to compensate for the loss in optical performance of the UV LEDs 110 in the light strings 206(1)-206( ) in the UV light source. For example, FIG. 13A illustrates a graph that shows an exemplary power output of UV LEDs 110 from an initial time t0 to a designated time tX (e.g., 5000 hours of operation) for a given fixed amount of current in current signals 550(1)-550(6). As shown in the curve 1300 in FIG. 13A, the power output of UV LEDs 110 degrades over time even though the current level in current signals 550(1)-550(6) remains the same. For example, the output power of a UV LED 110 at time t0 for a given current level may be 14.5 mW/m2, but the output power of a UV LED 110 may degrade to 12 mW/m2 at time tx. It may be desired for the output power of the UV LEDs 110 to not degrade over time.

Thus, in an example, the controller circuit 524 may be configured to cause the LED driver circuits 400(1)-406(6) in the UV light source 102 to increasing generate a higher level of current in current signals 550(1)-550(2) over time as the output power of the UV LEDs 110 is known to degrade. In this regard, FIG. 13B illustrates a diagram of the controller circuit 524 operation to compensate for the degradation in output power of the UV LEDs 110 over time. In this regard, at power-on of the UV light emission device 100 and as part of the boot-up operation of the controller circuit 524, the controller circuit 524 executes a LED derate engine 1302 that loads in a LED derate table circuit 1304 from NVM 562 and/or the FRAM NVM 872. The values in LED derate table circuit 1304 can be checked for a parity error checking function 1306. The LED derate table 1304 defines values to allow the controller circuit 524 to predict the light intensity degradation of the UV LEDs 110 over an accumulated usage time. For example, the LED derate table circuit 1304 can be based on empirical data programmed into a look-up table as LED derate values or a formula representing a function for calculated expected light intensity as a function of accumulated usage time. The LED derate table circuit 1304 is used by the controller circuit 524 to set the current level for the LED driver circuits 406(1)-406(6) to generate in the current signals 550(1)-550(6). When the controller circuit 524 enters into a state 1308, as shown in FIG. 13C, in response to the activation of the secondary switch 120 such that the LED driver circuits 406(1)-406(6) are enabled to cause the UV LEDs 110 to emit UV light 104, the controller circuit 524 can consult the LED derate table circuit 1304 to obtain LED derate values based on the accumulated UV LED 110 usage to set the current level for the LED driver circuits 406(1)-406(6) to generate in the current signals 550(1)-550(6).

In one example, the current level of the current signals 550(1)-550(6) can be monitored and controlled based on the sensed current signals 556(1)-556(6) by the current-voltage sense circuits 854(1)-854(6). In another example, the controller circuit 524 can configure the LED driver circuits 406(1)-406(6) to adjust the average current of the current signals 550(1)-550(6) in an open-loop control based on controlling the duty cycle of pulse-width modulated (PWM) of the current signals 550(1)-550(6). If a digital current potentiometer is used to control the current levels of the current signals 550(1)-550(6), the digital current potentiometer can be adjusted for the new current level according to the LED derate table circuit 1304. If PWM is used to control the average current of the current signals 550(1)-550(6), the LED driver circuits 406(1)-406(1) can be controlled to generate the desired average current of current signals 550(1)-550(6), by the controller circuit 524 enabling and disabling the power signal 504 as a PWM signal 1312 according to the determined duty cycle based on the LED derate table circuit 1304.

FIG. 14 is a flowchart illustrating an exemplary overall control process 1400 for controlling the overall operation of the UV emission device 100 in FIGS. 1A-1C as controlled by the controller circuit 524 in FIGS. 5 and 8. The process 1400 in FIG. 14 is executed by the controller circuit 524 when powered up/on and booted up in response to the primary switch 122 being activated. As shown in FIG. 14, the controller circuit 524 executes a system start-up process for the power-on and POST states in the operational state in FIG. 9. The exemplary system start-up process 1500 is shown in FIG. 15 and described below. After the system start-up process 1500, the controller circuit 524 executes a process 1600 in FIG. 16, described below, to wait for the secondary switch 120 to be activated by the user before entering an output active process 1700 in FIG. 17, described below in the MONITOR state discussed in FIG. 9. The controller circuit 524 remains ready and/or in an operational state in the MONITOR state with the UV light source 102 activated subject to activation of the secondary switch 120, until an error occurs or the UV light emission device 100 is powered down by deactivation of the primary switch 122. If an error is detected in the processes 1500-1800, the controller circuit 524 enters into an error state 1402 as discussed in the operational state in FIG. 9 and then waits until the UV light emission device 100 is reactivated according to the error state. The controller circuit 524 is configured to perform a tilt reaction process 1800 in FIG. 18, discussed below, in response to detection of a tilt beyond a tilt threshold or force beyond a force threshold of the UV light emission device 100 from the MONITOR state in process 1700. If tilt or force error occurs, the UV light source 102 is disabled the controller circuit 524 waits for the secondary switch 120 to be released in process 1900 in FIG. 19, discussed below. The UV light source 102 is reactivated by the controller circuit 524 in response to the secondary switch 120 being reactivated.

FIG. 15 is a flowchart illustrating an exemplary process 1500 for power-on and power-on self-test (POST) states in the overall control process in FIG. 14.

FIG. 16A is a flowchart illustrating an exemplary process 1600 for a power-on and POST of the UV light emission device 100 in FIGS. 1A-1C that can be performed by the controller circuit 524 in FIGS. 5 and 8. When the primary switch 122 is turned on, power is applied to the electronic control system 404, 804, and its controller circuit 524 in the power-on state, as previously discussed in FIG. 9. The controller circuit 404, 804 then goes to the POST state, as discussed in FIG. 9, to initialize the UV light emission device 100. In the power-on state, the communication bus 549, the controller circuit 524, the fan controller 544, and light driver PCB 402, 403 are powered on (block 1602 in FIG. 16A). The controller circuit 404, 804 programs and checks the haptic motor driver 870 via the communication bus 549 (block 1604 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the haptic motor driver 870 in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational state in FIG. 9 (block 1606 in FIG. 16A). The controller circuit 404, 804 checks the current sense signals 556(1)-556(2) to determine if current is flowing to the light driver PCB 402, 403 (block 1608 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the current sense in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational state in FIG. 9 (block 1606 in FIG. 16A). The controller circuit 404, 804 checks the analog over-temperature signal 531 for the temperature sensor 536 (block 1610 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the temperature sense in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational state in FIG. 9 (block 1606 in FIG. 16A). The controller circuit 404, 804 checks the FRAM 872 to determine if it is operational by writing and reading a bit to the FRAM 872 and verifying (block 1612 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the FRAM 872 in the NVM 562 and handles the error condition according to the operational state in FIG. 9 (block 1606 in FIG. 16A). The controller circuit 404, 804 checks the IMU circuit 546 to determine if it is operational (block 1614 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the IMU circuit 546 in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational states in FIG. 9 (block 1606 in FIG. 16A). The controller circuit 404, 804 loads the LED derate table circuit (described in more detail below) into the NVM 562 and/or FRAM 872 (block 1616 in FIG. 16A). If an error occurs, the controller circuit 404, 804 sets an error state in a status bit designated for the LED derate table circuit in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational states in FIG. 9 (block 1606 in FIG. 16A).

Thereafter, the controller circuit 404, 804 determines if the user has depressed the secondary switch 120 (block 1618 in FIG. 16B). The controller circuit 404, 804 is configured to display the software revision number through a sequence of the visual status indicator 143, as shown in FIG. 10 in this example, if the user depressed the secondary switch 120 at power-on (block 1620 in FIG. 16B). If the user has not depressed the secondary switch 120, the controller circuit 404, 804 initiates a LED sequence test for the UV LEDs 160 and visible light indicator 208(1)-208(4) (block 1622 in FIG. 16B). The controller circuit 404, 804 then does a fan 428 self-test by turning on and off the fan 428 via the fan controller 544 (block 1624 in FIG. 16B). The controller circuit 404, 804 then enters a loop (block 1626 in FIG. 16B) where it is determined if a timer for the fan-self test has expired based on whether the tachometer feedback signal 873 indicates rotation of the fan 428 within the timeout period (block 1628 in FIG. 16B). If the fan 428 is operational, the controller circuit 404, 804 turns off the fan 428 and verifies the revolutions per minute (RPM) of the fan 428 according to the RPM setting to the fan controller 544 and the RPMs detected from the tachometer feedback signal 873 (block 1630 in FIG. 16B). If an error is detected, the controller circuit 404, 804 sets an error state in a status bit designated for the fan 428 in the NVM 562 and/or FRAM 872 and handles the error condition according to the operational state in FIG. 9 (block 1606 in FIG. 16A). Otherwise, the controller circuit 404, 804 proceeds to the MONITOR state in FIG. 9 for normal operation (block 1632 in FIG. 16B).

FIG. 17 is a flowchart illustrating an exemplary process 1700 for operation of the UV light emission device 100 while waiting for the secondary switch 120 of the UV light emission device 100 to be activated by the user to start operation. In this regard, while the secondary switch 120 of the UV light emission device 100 is not activated (block 1702 in FIG. 17), the controller circuit 524 performs a series of checks and evaluations. The controller circuit 524 determines if the battery 142 voltage is above a defined voltage threshold (block 1704 in FIG. 7). The controller circuit 524 determines if the fan controller 544 is operational to control the fan 428 (block 1706 in FIG. 7). The controller circuit 524 determines if the UV light emission device 100 has been tilted beyond the programmed tilt orientation based on the accelerometer or orientation signal 548 or if it has been dropped according to the force signal 547 (block 1708 in FIG. 7). The controller circuit 524 writes any errors detected to a status register in the NVM 562 or FRAM NVM 872 to log the error (block 1710 in FIG. 7). If any errors were detected (block 1712 in FIG. 7), the controller circuit 524 enters into an error state and performs the process 2100 in FIG. 21, discussed below. If not, the controller circuit 524 continues to perform the checks in blocks 1704-1712 until the secondary switch 120 is activated. If no errors are detected, and the secondary switch 120 is activated (block 1702 in FIG. 17), the controller circuit 524 executes a process 1800 for an operational state in FIG. 18. In this example, if the controller circuit 524 detects that the secondary switch 120 was activated twice, the tilt detection feature is disabled in the controller circuit 524 (block 1714 in FIG. 7).

FIG. 18 is a flowchart illustrating an exemplary process 1800 for an operational state of the UV light emission device 100 in response to the secondary switch 120 of the UV light emission device 100 being activated in the process 1700 in FIG. 17 (block 1802 in FIG. 18). In response to detection of activation of the secondary switch 120, the controller circuit 524 performs a series of evaluations (block 1805 in FIG. 18) to check for errors according to the operational states in FIG. 9. If an error is detected (block 1806 in FIG. 8), the controller circuit 524 enters into an error state and performs the process 2100 in FIG. 21, discussed below. If an error is not detected and a tilt outside a threshold tilt range is not detected (block 1808 in FIG. 8), the controller circuit 524 increments a runtime counter (block 1810 in FIG. 8) and determines if the secondary switch 120 has been engaged for more than a predetermined amount of time (e.g., 5 minutes) (block 1812 in FIG. 8). If so, the controller circuit 524 disables the LED driver circuits 406(1)-406(6) (block 1814 in FIG. 8) and goes back to block 1802 to check to wait for reactivation of the secondary switch 120. This is to ensure that the LED driver circuits 406(1)-406(6) are not continuously activated for more than a defined period of time. If the secondary switch 120 has not been engaged for more than a predetermined amount of time (block 1812 in FIG. 18), the controller circuit 524 looks up a LED derate value in the LED derate table circuit 1304 to controlling the current of the current signals 550(1)-550(6) generated by the LED driver circuits 406(1)-406(6) to the light strings 206(1)-206(6) of the UV light source (block 1814 in FIG. 18). The controller circuit 524 activates the fan controller 544 to activate the fan 428 (block 1816 in FIG. 18). The controller circuit 524 then activates the LED driver circuits 406(1)-406(6) to cause the current signals 550(1)-550(6) to be generated by the LED driver circuits 406(1)-406(6) to the light strings 206(1)-206(6) at a current level controlled based on the read LED derate value from the LED derate table circuit 1304 in block 1816. The controller circuit 524 then determines if the secondary switch 120 will continue to be activated, and if not, disables the LED driver circuits 406(1)-406(6) until the secondary switch 120 is reactivated (block 1802 in FIG. 18).

FIG. 19 is a flowchart illustrating an exemplary tilt reaction process 1900 in response to a detected tilt of the UV light emission device 100. The process 1900 in FIG. 19 can be executed in response to a tilt detection in the overall operation process 1400 in FIG. 14. With reference to FIG. 19, in response to the controller circuit 524 detecting a tilt, the controller circuit 524 deactivates the LED driver circuits 406(1)-406(6) of the UV light source 102 (block 1902 in FIG. 19). The controller circuit 524 then sets the visual status indicator 143 to a fast flashing green color state as also set forth in the operational state in FIG. 9 (block 1904 in FIG. 19). The controller circuit 524 then activates the haptic feedback device 435 to signify the error condition through physical feedback to the user (block 1906 in FIG. 19). The controller circuit 524 then saves the error condition to the status register in the NVM 562 and/or the FRAM NVM 872 (block 1906 in FIG. 19) and waits for secondary switch 120 release and re-activation process 200 in FIG. 20. This is because for a tilt error, the controller circuit 524 is configured to allow the LED light drivers 406(1)-406(6) 100 to be reactivated to activate the light strings 206(1)-206(6) when the secondary switch 120 release and re-activated.

FIG. 20 is a flowchart illustrating an exemplary process 2000 of waiting for the secondary switch 120 of the UV light emission device 100 to be released. The process 200 includes the controller circuit 524 detecting when the secondary switch 120 has been deactivated (block 2002 in FIG. 20). When the controller circuit 524 detects the secondary switch 120 has been deactivated, the controller circuit 524 sets the visual status indicator 143 to a sold, steady green color state as shown in the state diagram in FIG. 19 (block 2004 in FIG. 20), and goes back to the wait for secondary switch 120 to be activated process 1700 in FIG. 17.

FIG. 21 is a flowchart illustrating an exemplary process 2100 of handling error detection in the UV light emission device 100. When an error is detected, the controller circuit 524 disables the LED driver circuits 406(1)-406(6) so that light is not emitted from the UV LEDs 110 and visible lights 208(1)-208(4) in the UV light source 102 (block 2102 in FIG. 21). The controller circuit 524 then determines if the error detected is a battery 142 low error (block 2104 in FIG. 21). If so, the controller circuit 524 enters the BATTERY LOW state as discussed in FIG. 9 (block 2106 in FIG. 19) and sets the visual status indicator 143 to a slow red flashing state (block 2108 in FIG. 19). The controller circuit 524 then logs the battery 142 low error in the status register in the NVM 562 and/or the FRAM NVM 872 (block 2110 in FIG. 19). The controller circuit 524 then activates the haptic feedback device 435 (block 2112 in FIG. 19). If the error is other than a battery 142 low error (block 2112 in FIG. 19), the controller circuit 524 sets the visual status indicator 143 to a three (3) short and three (3) long red flashing state (block 2114 in FIG. 19), then logs the error in the status register in the NVM 562 and/or the FRAM NVM 872 (block 2110). The controller circuit 524 then waits until the UV light emission device 100 is reactivated to recover from the error, which may require the secondary switch 120 to be reactivated and/or a power cycle by deactivating and reactivating the primary switch 122.

FIG. 22A-22C is a diagram of an exemplary status register 2200 that can be programmed and access in the NVM 562 and/or the FRAM NVM 872 to detect programming and register history information, including errors, for the UV light emission device 100. The status register 2200 is indexable by an address 2202, as shown in FIGS. 22A-22C. At each address 2202, the status register 2200 contains a block (e.g., a byte, word, etc.) of memory space to allow a status to be written. The memory space at each address 2202 is dedicated to a specific type of data, as shown in the written description column 2204 in FIGS. 22A-22C.

UV light sources other than the UV LEDs 110 described above can also be employed in the UV light emission device 100 in FIGS. 1A-1C to emit the UV light 104. In this regard, FIG. 23 is a diagram of an alternative UV light source in the form of a planar excimer UV lamp 2300 that can be employed in the UV light emission device 100 in FIGS. 1A-1C. For example, the excimer UV lamp 2300 could be a Krypton-containing or Krypton-Chlorine (KrCl) light source with a peak emission at 222 nm wavelength as an example. For example, the excimer UV lamp 2300 could be the high-power ultraviolet (UV) and vacuum ultraviolet (VUV) lamps with micro-cavity plasma arrays disclosed in U.S. Patent Application No. 2019/0214244 A1 incorporated herein by references in its entirety. FIG. 10 is a schematic diagram of an alternative electrical control system 2404 that can be employed in the UV light emission device in FIGS. 1A-1C employing the excimer UV lamp 2300 in FIG. 23. Common elements between the electrical control system 404 in FIG. 10 and the electrical control system 404 in FIG. 5 are shown with common element numbers between FIGS. 5 and 24 and will not be re-described.

As shown in FIG. 24, the power signal 504 distributed by the power enable switch 530 is coupled to a ballast 2400. The ballast 2400 is configured to generate a voltage signal 2450(1) to power the excimer UV lamp 900. The ballast 2400 is mounted to PCB 2401. The ballast 2400 also includes a LED light driver 2402 to generate a current signal 2410 to the visible light indicators 423 that emit light into the visible light ring 148. The ballast 2400 also includes a LED light driver 2412 to generate a current signal 2414 to the visible lights 208(1)-208(4) that provide a visible light source indicating when the UV light 244 is being emitted from the excimer UV lamp 900. A current sense circuit 2454 is also provided on the PCB 2401 and is configured to sense the current signals 2410, 2414 and voltage signals 2450(1)-2450(3) generated by the ballast 2400 and its LED light drivers 2402, 242412 to detect error conditions similar to the detection of the current signals 550(1)-550(6) in the electrical control system 404 in FIG. 5. The current sense circuit 2454 is configured to generate a current sense signal 2456 on the communication bus 549 to indicate to the controller circuit 524 if an error condition is present in the current signals 2410, 2414 and respective voltage signals 2450(1)-2450(3) such that the ballast 2400 or the LED light drivers 2402, 2412 are malfunctioning or not operating properly. Note that the electronic control system 804 in FIG. 8 could also include the planar excimer UV lamp 2300.

FIGS. 25A and 25B are schematic diagrams of an alternative UV light emission device 2500 similar to the UV light emission device 100 in FIGS. 1A-1C, but that allows air to be drawn into the light source housing 202 and across the UV light source 102 to expose the drawn-in air to the UV light emission. FIG. 25A is a close-up, side, cross-sectional view of the light source head 106 of the UV light emission device 2500. FIG. 25B is a bottom view of the UV light source 102 of the UV light emission device 2500 in FIG. 25A. Common elements between the UV light emission device 2500 in FIGS. 25A and 25B and the UV light emission device 100 in FIGS. 4B and 2, respectively, are shown with common element numbers and not re-described.

With reference to FIG. 25A, the UV light emission device 2500 includes a light source head 106 that includes a light source housing 202 that is attached to the light source housing cover 204 to secure the UV light source 102. The fan 428 is mounted inside the light source head 106 to draw heat away from the light source PCB 422 for the UV light source 102 and to direct such heat through the vent openings 114 in the rear 117 of the light source housing 202 for heat dissipation. However, as shown in FIG. 25B, the light source shield 108 includes openings 2502. The heat sink 426 is removed or rearranged so that there is fluid communication between the fan 428 and the openings 2502. Thus, when the fan 428 draws air from the UV light source 102, the suction generated by the fan 428 also draws air through the openings 2502 and past the UV light source 102 to decontaminate the drawn-in air. The air is then exposed on the opposite side of the fan 428 through the vent openings 114 in the rear 117 of the light source housing 202. The vent openings 114 on the sides of the light source housing 202 may be present or may be removed fully or partially to cause the drawn-in air to pass across the UV light source 102. Alternatively, as discussed above, the fan 428 mounted inside the light source head 106 above the heat sink 426 could pull air through the openings 114 in the rear 117 of the light source head 106, exhausting such air through the openings 114 in the side 116 to carry heat generated from the light source PCB 422 for the UV light source 102 away from the UV light source 102.

FIG. 25B also illustrates an alternative light source housing 202 that has UV LEDs 110 in different sized parabolic reflectors 424(1), 424(2). These larger and smaller parabolic reflectors 424(1), 424(2) cause the UV light emitted by the UV LEDs 110 to be reflected and shaped differently to provide narrower and broader UV beam angles, respectively. Providing the smaller parabolic reflectors 424(2) to provide a broader UV beam angle of UV light emitted by the UV LEDs 110 may provide a more uniform UV light emission on a target of interest. Providing the larger parabolic reflectors 424(1) to provide a narrower UV beam angle of UV light to be emitted by the UV LEDs 110 may contain the emitted UV light within a desired target area on a target of interest, such as the 4″×4″ target surface.

FIG. 26 is a schematic diagram of an alternative UV light emission system 2600 that includes the UV light emission device 100 in FIGS. 1A-1C but provides the battery 142 as integrated with the base 124 to allow more portability. The UV light emission system 2600 can still be connected to a power source as an AC-to-DC converter 2602 for wall outlet power and for battery 142 charging. Also, the electrical leads 2604 are exposed from the base housing 126 to allow the UV light emission device 100 to be placed in a docking station or cradle for charging, data transmission, and/or secure storage. The electrical leads 2604 include leads for power and ground, but also include leads that can be electrically coupled to the USB port 264, the communication bus 549 or other interface of the electrical control systems 404, 804 in FIGS. 5 and 8, for example, to communicate with the UV light emission device 100 and to extract the data stored in the NVM 262. Alternatively, the battery 142 could be inductively charged through the base housing 126 without the need for electrical leads 2604.

Other light sources for generating UV light not described above could also be employed in the UV light emission device 100, including a microplasma UV lamp, a laser UV light source, an OLED UV light source, and a chemiluminescence UV light source, as non-limiting examples. The circuit boards discussed herein may be clad with a metal such as aluminum for further heat dissipation.

The UV light emission device 100 can be configured so that the base housing 126 is compatible with a battery 142 is a v-mount battery in this example to standardize the mounting system, electrical connectors, and voltage output. This type of battery 142 can be found in power photography and videography equipment. The battery 142 provides a 14.4 VDC nominal output and comes in a variety of capacities. Using a standard battery offers many benefits. For example, the battery 142 may be the IDX Duo-C150 (143 Wh battery).

The depth of focus of the light emitted by the UV LEDs 110 in the UV light source 102 of the UV light emission device 100 determines the output power as a function of emission range. It may be desired to control depth of focus of the light emitted by the UV LEDs 110 to control the output power as a function of emission range so that a user could direct the UV light source 102 towards a given surface to expose that surface to the UV light 104 without the UV light source 102 actually having to come into contact with such surface. For example, FIG. 27A is a diagram of depth of focus 2700 of UV light 2702 emitted from the UV LEDs 110 of the UV light source 102 of the UV light emission device 100 as a function of distance from the UV light source 102. As shown therein, as the UV light 2702 travels a further distance in the X-axis direction, the UV light spreads out a further distance in the Z-axis, thus causes a loss of intensity of the UV light 2702. For example, the depth of focus of the UV light 2702 is shown at distance D4, which is one (1) inch in this example, distance D5, which in three (3) inches in this example, and distance D6, which is twelve (12) inches in this example. Thus, the intensity of the UV light 2702 emitted from the UV LED 110 on a surface of distance D6 away from the UV light source 102 will be less than the intensity of the UV light 2702 emitted from the UV LED 110 on a surface of distance D5 away from the UV light source 102. The intensity of the UV light 2702 emitted from the UV LED 110 on a surface of distance D5 away from the UV light source 102 will be less than the intensity of the UV light 2702 emitted from the UV LED 110 on a surface of distance D4 away from the UV light source 102. FIG. 27B is a diagram that illustrates the depth of focus 2704 of the UV light 2702 emitted from the UV LEDs 110 of the UV light source 102 up to a much further distance D7, which may be 72 inches. FIG. 28 illustrates a graph 2800 illustrating mean irradiance 2802 of the UV light source 102 in mW/cm2 as a function of distance in inches (in). As shown therein, the irradiance 2802 reduces substantially linearly to distance from 2 inches to 32 inches as an example. Thus, controlling the power of the UV lights 110 in the UV light source 102 is a way to control the irradiance to achieve the desired optical output power at a given distance of the UV light source 102 from a surface.

It was found that the visible light emitted from the visible lights 208(1)-208(4) in the UV light source 102 can provide a visual feedback to a user directing the UV light source 102 toward a surface to emit UV light from the UV LEDs 110 towards that surface. The visible light from the visible lights 208(1)-208(4) appears on the surface that the UV light from the UV LEDs 110 is emitted, as shown in FIGS. 29A and 29B. As shown in FIGS. 29A and 29B, the UV light source 102 is placed above a surface 2900 at a greater distance in FIG. 29B than in FIG. 29A. Thus, the spotlights 2902(1)-2902(4) formed on the surface 2900 from visible light emission from the visible lights 208(1)-208(4) in FIG. 29A have a smaller visible light beam spread of smaller diameter D8 than the visible light beam spread (diameter) of spotlights 2904(1)-2904(4) formed on the surface 2900 from visible light emission from the visible lights 208(1)-208(4) in FIG. 29B. Thus, if a correlation can be found between the visible light beam spread diameter and/or orientation of spotlights on a surface 2900 resulting from visible light being emitted by the visible lights 208(1)-208(4) of the UV light source 102 and the desired power of the UV light at the surface for decontamination, the spotlights on a surface 2900 resulting from visible light being emitted by the visible lights 208(1)-208(4) of the UV light source 102 can be used as a visual indicator to a user of the UV light emission device 100 on the recommended distance to hold the UV light source 102 away from a surface to be decontaminated.

It was found by an example experimentation that for a distance of one (1) inch between the UV light source 102 of the UV light emission device 100 and the surface 2900, the power of the UV light at the surface 2900 was 16.78 mW/cm2. FIG. 30A shows the visible light beam spread diameter of the spotlights 3000(1)-3000(4) on a surface from the visible light emitted by the visible lights 208(1)-208(4) of the UV light source 102 when placed one (1) inch away from the surface. As shown in FIG. 30A, at a distance of one (1) inch, the spotlights 3000(1)-3000(4) have a visible light beam spread diameter of D10 and are located a distance D11 from each other. The distance D11 is greater than 0, meaning there is a gap distance between adjacent spotlights 3000(1)-3000(4). It was also found by experimentation that for a distance of 2.5 inches between the UV light source 102 and the surface 2900, the power of the UV light at the surface 2900 was 15.8 mW/cm2. FIG. 30B shows the visible light beam spread diameter of the spotlights 3002(1)-3002(4) on a surface from the visible light emitted by the visible lights 208(1)-208(4) of the UV light source 102 when placed 2.5 inches away from the surface. As shown in FIG. 30B, at a distance of 2.5 inches, the spotlights 3000(1)-3000(4) have a visible light beam spread diameter of D12 and are located a distance D13 from each other of zero (0), meaning there is no gap distance and the spotlights 3002(1)-3002(4) either barely touch, are extremely close, and touch each other or almost touch each other to the human visual eye. It was also found by experimentation that for a distance of 3.5 inches between the UV light source 102 and the surface 2900, the power of the UV light at the surface 2900 was 16.6 mW/cm2. As shown in FIG. 30C, at a distance of 3.5 inches, the spotlights 3004(1)-3004(4) have a visible light beam spread diameter of D14 and are located a distance D15 from each in an overlapping manner, or a negative distance as compared to the spotlights 3000(1)-300(4) in FIG. 30A.

The visual feedback from spotlights formed on a surface as a result of the visible light emitted from the visible lights 208(1)-208(4) not only provides an indication to the user that the UV light source 102 is activated and operational but also allows the user to instantly determine that they are holding the UV light source 102 of the UV light emission device 100 at the prescribed distance from the surface to achieve the desired light power of the UV light 104 emitted from the UV LEDs 110 on the surface. For instance, if the user is instructed to hold the UV light emission device 100 so that the spotlights formed on a surface as a result of the visible light emitted from the visible lights 208(1)-208(4) are just touching each other as shown in FIG. 30B, this can be used as an indirect instruction for the user to hold the UV light source 102 2.5 inches from a surface of interest to achieve the desired UV light power and intensity at the surface of interest. As shown in FIGS. 29A and 29B, the visible light beam spread size (i.e., diameter) of the spotlights formed on a surface as a result of directing the UV light source of the UV light emission device 100 towards the surface and the visible lights 208(1)-208(4) emitting visible light may not be consistent. Variables such as ambient light and the angle of orientation of the UV light source 102 with respect to a surface of interest, and the topography of the surface, affect the formation of the spotlights on the surface of interest. Thus, this may cause a user to hold the UV light source 102 at a distance from a surface of interest that is not desired or ideal for the desired light power and intensity according to the depth of focus of the UV LEDs 110. In this regard, as shown in FIG. 31, the spotlights 3100(1)-3100(4) emitted by the visible lights 208(1)-208(4) of the UV light source 102 can be manipulated to a desired pattern to provide a more easily discernable spotlight to a user. The pattern shown in FIG. 31 is a rectangular-shaped pattern (e.g., a square-shaped pattern) that forms a rectangle when drawing imaginary lines between the center areas of the light beams on the target of interest from the visible light emitted by the visible lights 208(1)-208(4). The pattern can be any shape pattern depending on the number of visible lights 208 and the orientation of the visible lights 208 in the light source housing 202. In this example, the pattern shown in FIG. 31 is polygonal-shaped (e.g., with four (4) sides). The pattern could be circular-shaped. Only one visible light 208 could be included with the circular-shaped cone of light on the target of interest from the visible light emitted by the visible light 208 is circular shaped. The distance between the visible light 208 and the target of interest affects the shape and diameter of the cone of light. In this example, the UV LEDs 110 are arranged in the light source housing 202 such that their emitted UV light is contained within the shaped pattern formed by drawing imaginary lines between the beams of light on the target of interest emitted by the visible lights 208(1)-208(4) depending on the type of visible lights 208(1)-208(4), their distance from the target of interest, and the type and shape of their reflectors 424.

FIG. 32 is a diagram of the mask 3200 placed on the UV light source 102 that includes patterned sections 3202(1)-3202(4) to cause visible light emitted from the visible lights 208(1)-208(4) on a surface to be patterned as shown in FIG. 31. The visible light emitted from the visible lights 208(1)-208(4) is emitted through the respective patterned sections 3202(1)-3202(4) of the mask 3200. This may control the visible light beam spread of the visible light to be of a higher resolution to be more easily visible by a user and for a user to more easily visibly detect the perimeter of the visible light beam spread of the visible lights 208(1)-208(4). FIG. 33 illustrates the mask 3200 in a closer view. For example, the mask 3200 can be formed from a laser cut think stainless steel sheet 3204 to be able to fit over the top the UV light source shield 108 as an example.

The use of the mask 3200 also affects the brightness of the visible light emitted by the visible lights 208(1)-208(4). The patterned sections 3202(1)-3202(4) can be designed to control the desired brightness of the visible light emitted by the visible lights 208(1)-208(4). This may be important to achieve a desired light intensity of UV light 104 emitted by the UV light source 102, that is not visible to the human eye, without causing the visible lights 208(1)-208(4) to emit visible light at a brightness that is deemed too bright and/or undesirable for a user. As discussed above, certain light driver circuits 400(1)-400(6) are configured to drive a current in the same light string 206(1)-206(6) that has both UV LEDs 100 and a visible light 208(1)-208(4). Thus, the same amount of current drive to the UV LEDs 100 in such a light string 206(1)-206(6) is also driven to the visible light 208(1)-208(4) in the same light string 206(1)-206(6). It may not be possible or desired to drive less current to the visible light 208(1)-208(4), especially if LEDs, without affecting and/or shutting off the operation of the visible light 208(1)-208(4). There may be a threshold current (e.g., 250 mA) necessary to achieve an on state with visible LEDs. Thus, in this example, to drive the desired amount of current to the UV LEDs 110 to achieve the desired light intensity for efficacy, this amount of current driven to the visible light(s) 208(1)-208(4) in the same light string 206(1)-206(6) may be too bright. The visible lights 208(1)-208(4) may be more efficient than the UV LEDs 110 in terms of conversion of current to light power. Thus, by placing the patterned sections 3202(1)-3202(4) of the mask 3200 in the light path of the visible light(s) 208(1)-208(4), the visible light emitted from the visible light(s) 208(1)-208(4) is attenuated or blocked. The patterned sections 3202(1)-3202(4) of the mask 3200 may be arranged to block the center area of the light path of the visible light(s) 208(1)-208(4) to block the more light intense areas of the visible light emitted by the visible light(s) 208(1)-208(4). Visible light emitted by the visible light(s) 208(1)-208(4) may leak around the solid portions of the patterned sections 3202(1)-3202(4). Alternatively, a filter could be placed on the light source housing 202 to filter all light emitted from the visible lights 208(1)-208(4), but this attenuates the entire cone of light emitted from the visible lights 208(1)-208(4). The patterned sections 3202(1)-3202(4) of the mask 3200 allow the selective filtering of visible light emitted by the visible lights 208(1)-208(4). It may also be desired to purposefully control the uniformity of the UV light emitted from the UV LEDs 110 to provide a uniform intensity of UV light 104 on a surface of interest from the UV light emission device 100. The design of the parabolic reflectors 424 of the UV light source 102, as shown in FIGS. 4A and 4B, affects the uniformity of the UV light 104 emitted from the UV LEDs 110 of the UV light source 102. In this regard, experiments were conducted to explore the uniformity of the intensity of UV light 104 at various distances from the parabolic reflectors 424 on a surface of interest. FIGS. 34A-34F illustrate various heat maps 3400A-3400F that show two-dimensional power distribution (distance in mm from center vs. W/m2) of UV light 104 emitted by the UV light source 102 across a 4″×4″ area at varying distances from the parabolic reflectors 424 at distances of 1 inch, 2 inches, 3 inches, 4 inches, 6 inches, and 12 inches, respectively. Light from a point source decreases as the square of the distance. A doubling of distance would cause the light power of the UV light 104 to decrease by a factor of 4. The parabolic reflectors 424 collimate the UV light 1 in the nearfield, which extends the range of usable distance. If the UV light 104 were not collimated, the output power of the UV light 104 at 2″ would be 25% of the output power of UV light 104 at 1″. The average power of the UV light 104 in the heat map 3400A in FIG. 34A was 143.58 W/m2. The average power of the UV light 104 in the heat map 3400B in FIG. 34B was 139.41 W/m2. The average power of the UV light 104 in the heat map 3400C in FIG. 34C was 129.56 W/m2. The average power of the UV light 104 in the heat map 3400D in FIG. 34D was 117.75 W/m2. The average power of the UV light 104 in the heat map 3400E in FIG. 34E was 99.08 W/m2. The average power of the UV light 104 in the heat map 3400F in FIG. 34F was 56.46 W/m2.

The reflectivity of light off of various materials has long been characterized. Aluminum is known to have a high reflectivity compare to other metals, for example. For example, as shown in the graph 3500 in FIG. 35, it is shown that not all metallic reflectors respond the same as the short wavelengths. The graph in FIG. 35 plots reflectance vs. wavelength in nm for aluminum (Al), silver (Ag), gold (Au), and copper (Cu). Note that silver, gold, and copper have very low reflectance as the wavelength drops below 600 nm. At a UV light of 270 nm emitted from the UV light source 102 as an example, note that graph 3500 shows that only aluminum exhibits decent reflectivity at >90% at this wavelength. For this reason, reflectors made for lower wavelengths (220-300 nm) are often made from aluminum. Unfortunately, aluminum may also oxidize and quickly corrodes such that it will lose its reflective properties unless protected.

In this regard, in an example, the parabolic reflectors 424 in the UV light source 102 of the UV light emission device 100 may be coated with a thick protective coasting by adding a thin coat of SiO2 (glass) to the surface of parabolic reflectors 424. The parabolic reflectors 424 use a planetary system and crucible to deposit aluminum onto a plastic substrate and then apply a thin coat of SiO2 (glass). In this fashion, reflectivity measurement of >70% at a UV light wavelength of 270 nm has been observed. For example, the protective coating could be formed on the parabolic reflectors 424 by electron beam deposition process (E-Beam). Source materials in the coating chamber can either be vaporized using heating or electron-beam bombardment of powder or granular dielectric or metallic substances. The subsequent vapor condenses upon the optical surfaces, and via precision computer control of heating, vacuum levels, substrate location, and rotation during the deposition process result in conformal optical coatings of pre-specified optical thicknesses.

FIG. 36 is a graph 3600 that shows percentage reflectance of the SiO2 (glass) 3602 as compared to other coatings 3604, 3606, 3608, 3610, 3612. Curve 3610 illustrates the reflectance of the plastic parabolic reflector 424 with no coating. Curve 3608 illustrates the reflectance of the parabolic reflector 424 coated with aluminum. Curves 3606, 3604 illustrate reflectances of the parabolic reflector 424 of other sample coatings. Curve 3602 illustrates the reflectance of the plastic parabolic reflector 424 with SiO2 (glass).

FIGS. 37A-37D illustrate an alternative UV light emission device 3700 similar to FIGS. 1A-1C but with a power connector 3702 and a mounting structure 3706 on the base housing 124. Common elements between the UV light emission device 3700 in FIGS. 37A-37D and the UV light emission device 100 in FIGS. 1A-1C are shown with common element numbers. The previous description of the UV light emission device 100 in FIGS. 1A-36 is applicable to the UV light emission device 3700. The power connector 3702 is a male connector used to connect the UV light emission device 3700 to a battery. A cable 132 is fitted with a female cable connector 3704 that can be secured to connector 3702. The power connector 3702 is connector made by Hirose Electric Co., part no. LF10WBP-4s(31), and the cable connector 3704 is also made by Hirose Electric Co., part LF10WBR-4P. FIGS. 37A-37D also illustrate a mounting structure 3706 that is fitted to the base housing 124. The mounting structure 3706 is a circular metal member that is configured to be received in a receiver in a belt clip 3800 shown in FIGS. 38A-38C to hold the support the base member 124 of the UV light emission device 3700 on a user's belt clip.

In this regard, FIG. 38A-38C are respective perspective, front and side views, respectively, of belt clip 3800 that is configured to receive the mounting structure 3706 on the base housing 124 of the UV light emission device 3700 in FIGS. 37A-37C to mount the UV light emission device 3700 to a user's belt. As shown in FIG. 38A-38C, the mounting structure 3706 includes a V-shaped receiver 3804 that is configured to receive and secure the mounting structure 3706. As shown in the side view of the belt clip 3800 in FIG. 38C, the belt clip 3800 includes a front member 3808 and a back member 3806 attached to each other and disposed in substantially parallel planes with a slot 3110 formed therebetween to be able to receive a user's belt. In this manner, the belt clip 3800 can be secured to a user's belt. The mounting structure 3706 on the base housing 124 of the UV light emission device 3700 in FIGS. 37A-37C is received in the receiver 3804 wherein the handle 118 and light source housing 106 can rotate and swivel downward due to gravity such that the UV light emission device 3700 hangs down from the belt clip 3800 by the base member 124 and its mounting structure 3706 secured in the receiver 3804. The mounting structure 3706 being circular in shape allows it to easily rotate within the receiver 3804. The belt clip 3800 can also include orifices 3812 to be able to mount the belt clip 3800 to a wall or other surface to support the UV light emission device 3700 in different manners than on a user's belt.

The UV light emission devices and charging bases disclosed herein can include a computer system 3900, such as shown in FIG. 39, to control the operation of a UV light emission device, including but not limited to the UV light emission devices disclosed herein. For example, the computer system 3900 may be the controller circuit 524 in the electrical control systems 404, 804, 1004 in FIGS. 5, 8, and 10. With reference to FIG. 39, the computer system 3900 includes a set of instructions for causing the multi-operator radio node component(s) to provide its designed functionality and their circuits discussed above. The multi-operator radio node component(s) may be connected (e.g., networked) to other machines in a LAN, an intranet, an extranet, or the Internet. The multi-operator radio node component(s) may operate in a client-server network environment or as a peer machine in a peer-to-peer (or distributed) network environment. While only a single device is illustrated, the term “device” shall also be taken to include any collection of devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. The multi-operator radio node component(s) may be a circuit or circuits included in an electronic board card, such as a printed circuit board (PCB) as an example, a server, a personal computer, a desktop computer, a laptop computer, a personal digital assistant (PDA), a computing pad, a mobile device, or any other device, and may represent, for example, a server, edge computer, or a user's computer. The exemplary computer system 3900 in this embodiment includes a processing circuit or processing device 3902, a main memory 3904 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM), etc.), and a static memory 3906 (e.g., flash memory, static random access memory (SRAM), etc.), which may communicate with each other via a data bus 3908. Alternatively, the processing device 3902 may be connected to the main memory 3904 and/or static memory 3906 directly or via some other means of connectivity. The processing device 3902 may be a controller, and the main memory 3904 or static memory 3906 may be any type of memory.

The processing device 3902 represents one or more general-purpose processing circuits such as a microprocessor, central processing unit, or the like. More particularly, the processing device 3902 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 3902 is configured to execute processing logic in instructions 3916 for performing the operations and steps discussed herein.

The computer system 3900 may further include a network interface device 3910. The computer system 3900 also may or may not include an input 3912 to receive input and selections to be communicated to the computer system 3900 when executing instructions. The computer system 3900 also may or may not include an output 3914, including but not limited to a display, a video display unit (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device (e.g., a keyboard), and/or a cursor control device (e.g., a mouse).

The computer system 3900 may or may not include a data storage device that includes instructions 3916 stored in a computer-readable medium 3918. The instructions 3916 may also reside, completely or at least partially, within the main memory 3904 and/or within the processing device 3902 during execution thereof by the computer system 3900, the main memory 3904, and the processing device 3902 also constituting computer-readable medium. The instructions 3916 may further be transmitted or received over a network 3920 via the network interface device 3910.

While the computer-readable medium 3918 is shown in an exemplary embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the processing circuit and that cause the processing circuit to perform any one or more of the methodologies of the embodiments disclosed herein. The term “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic medium, and carrier wave signals.

The embodiments disclosed herein include various steps. The steps of the embodiments disclosed herein may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware and software.

The embodiments disclosed herein may be provided as a computer program product or software, that may include a machine-readable medium (or a computer-readable medium) having stored thereon instructions, which may be used to program a computer system (or other electronic devices) to perform a process according to the embodiments disclosed herein. A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium includes a machine-readable storage medium (e.g., read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage medium, optical storage medium, flash memory devices, etc.).

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A controller may be a processor. A processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The embodiments disclosed herein may be embodied in hardware and in instructions that are stored in hardware and may reside, for example, in Random Access Memory (RAM), flash memory, Read-Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a remote station. In the alternative, the processor and the storage medium may reside as discrete components in a remote station, base station, or server.

Unless otherwise expressly stated, it is in no way intended that any method set forth herein be construed as requiring that its steps be performed in a specific order. Accordingly, where a method claim does not actually recite an order to be followed by its steps, or it is not otherwise specifically stated in the claims or descriptions that the steps are to be limited to a specific order, it is in no way intended that any particular order be inferred. It will be apparent to those skilled in the art that various modifications and variations can be made without departing from the spirit or scope of the invention. Since modifications combinations, sub-combinations, and variations of the disclosed embodiments incorporating the spirit and substance of the invention may occur to persons skilled in the art, the invention should be construed to include everything within the scope of the appended claims and their equivalents.

It is also noted that the operational steps described in any of the exemplary aspects herein are described to provide examples and discussion. The operations described may be performed in numerous different sequences other than the illustrated sequences. Furthermore, operations described in a single operational step may actually be performed in a number of different steps. Additionally, one or more operational steps discussed in the exemplary aspects may be combined. It is to be understood that the operational steps illustrated in the flowchart diagrams may be subject to numerous different modifications as will be readily apparent to one of skill in the art. Those of skill in the art will also understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of emitting ultraviolet (UV) light to a target of interest, comprising: directing a UV light source comprising one or more UV lights and a plurality of visible lights in a light source housing, in a direction towards a target of interest;emitting visible light from each of the plurality of visible lights in the direction towards the target of interest to project a plurality of visible light beams from the respective plurality of visible lights toward the target of interest to form an interior beam area on the target of interest in an area between the plurality of visible light beams on the target of interest; andemitting UV light from each of the one or more UV lights in the direction towards the target of interest to project one or more UV light beams from the respective one or more UV lights towards the target of interest to create one or more UV light beams contained in the interior beam area on the target of interest.
2. The method of claim 1, wherein emitting the visible light further comprises projecting the plurality of visible light beams of a respective plurality of visible light beam spreads on the target of interest.
3. The method of claim 2, further comprising manipulating a distance of the light source housing from the target of interest to vary the areas of the respective plurality of visible light beam spreads on the target of interest.
4. The method of claim 2, further comprising increasing a distance between the between the one or more visible lights in the light source housing and the target of interest to increase the respective plurality of visible light beams of visible light emitted by the one or more visible lights on the target of interest.
5. The method of claim 4, further comprising varying orientation of the light source housing to vary the areas of the respective plurality of visible light beam spreads on the target of interest.
6. The method of claim 1, wherein emitting the UV light from each of the one or more UV lights further comprises emitting the UV light from each of the one or more UV lights to project the one or more UV light beams of at least 12 mW/cm2 on the target of interest when a distance between the one or more UV lights and the target of interest is one (1) inch.
7. The method of claim 1, wherein emitting the UV light from each of the one or more UV lights further comprises emitting the UV light from each of the one or more UV lights to project the one or more UV light beams of at least 12 mW/cm2 on the target of interest when a distance between the one or more UV lights and the target of interest is 2.5 inches.
8. The method of claim 1, wherein emitting the UV light from each of the one or more UV lights further comprises emitting the UV light from each of the one or more UV lights to project the one or more UV light beams of at least 12 mw/cm2 on the target of interest when a distance between the one or more UV lights and the target of interest is 3.5 inches.
9. The method of claim 1, wherein emitting the visible light from each of the plurality of visible lights comprises emitting the visible light from each of the plurality of visible lights to project the plurality of visible light beams on the target of interest in a pattern forming the interior beam area on the target of interest.
10. The method of claim 9, wherein the pattern comprises a polygonal-shaped pattern.
11. The method of claim 1, further comprising masking the visible light emitted from each of the plurality of visible lights through a respective patterned section in a mask among a plurality of patterned sections in the mask.
12. The method of claim 11, wherein masking the visible light comprises blocking a portion of the visible light emitted from each of the plurality of visible lights through the respective patterned section in the mask among the plurality of patterned sections in the mask.
13. The method of claim 11, wherein masking the visible light comprises masking the visible light emitted from each of the plurality of visible lights through the respective patterned section in a mask among the plurality of patterned sections in the mask to equalize the light intensity of the visible light emitted by the plurality of visible lights and the UV light emitted by the plurality of UV lights.
14. The method of claim 1, further comprising coupling power to the plurality of visible lights to emit the plurality of visible light beams towards the target of interest, in response to providing power from a received power signal to the one or more UV lights.

PRIORITY APPLICATIONS

The present application is a divisional application of and claims priority to U.S. patent application Ser. No. 17/139,537 entitled, “ULTRAVIOLET (UV) LIGHT EMISSION DEVICE EMPLOYING VISIBLE LIGHT FOR TARGET DISTANCE GUIDANCE, AND RELATED METHODS OF USE, PARTICULARLY SUITED FOR DECONTAMINATION,” filed on Dec. 31, 2020, which claims priority to U.S. Provisional Patent Application Ser. No. 63/019,231 entitled, “ULTRAVIOLET (UV) LIGHT EMISSION DEVICE, AND RELATED METHODS OF USE, PARTICULARLY SUITED FOR DECONTAMINATION,” filed May 1, 2020, and U.S. Provisional Patent Application Ser. No. 63/079,193 entitled “ULTRAVIOLET (UV) LIGHT EMISSION DEVICE, AND RELATED METHODS OF USE, PARTICULARLY SUITED FOR DECONTAMINATION,” filed on Sep. 16, 2020, all of which are incorporated hereby by reference in their entireties.

US Referenced Citations (1234)

Number	Name	Date	Kind
1118006	Henri et al.	Nov 1914	A
1132265	Henri et al.	Mar 1915	A
1145140	Henri et al.	Jul 1915	A
1151267	Henri et al.	Aug 1915	A
1266803	Henri et al.	May 1918	A
2058826	Reece	Oct 1936	A
2201548	Treinis	May 1940	A
2253251	Selig	Aug 1941	A
2298124	Hartman	Oct 1942	A
2553711	Jackson	May 1951	A
2732501	Blaeker	Jan 1956	A
2935611	Myers	May 1960	A
2977647	Vassiliades et al.	Apr 1961	A
3185839	Glasson et al.	May 1965	A
3433946	Harwick	Mar 1969	A
3683638	Devon	Aug 1972	A
4008045	Free	Feb 1977	A
4063890	Baron	Dec 1977	A
4141686	Lewis	Feb 1979	A
4255663	Lewis	Mar 1981	A
4469835	Laurin	Sep 1984	A
4535247	Kurtz	Aug 1985	A
4786812	Humphreys	Nov 1988	A
4806770	Hylton et al.	Feb 1989	A
4816145	Goudy, Jr.	Mar 1989	A
4910942	Dunn et al.	Mar 1990	A
4952369	Belilos	Aug 1990	A
4963750	Wilson	Oct 1990	A
4973847	Lackey et al.	Nov 1990	A
5053033	Clarke	Oct 1991	A
5133932	Gunn et al.	Jul 1992	A
5150705	Stinson	Sep 1992	A
5213759	Castberg et al.	May 1993	A
5326542	Sizer et al.	Jul 1994	A
5372781	Hallett et al.	Dec 1994	A
5433920	Sizer et al.	Jul 1995	A
5503559	Vari	Apr 1996	A
5587069	Downey, Jr.	Dec 1996	A
5624573	Wiesmann	Apr 1997	A
5626768	Ressler et al.	May 1997	A
5637877	Sinofsky	Jun 1997	A
5707594	Austin	Jan 1998	A
5742063	Scroggins et al.	Apr 1998	A
5744094	Castberg et al.	Apr 1998	A
5780860	Gadgil et al.	Jul 1998	A
5817276	Fencl et al.	Oct 1998	A
5852879	Schumaier	Dec 1998	A
5874741	Matschke	Feb 1999	A
5920075	Whitehead	Jul 1999	A
5928607	Frisk	Jul 1999	A
5935431	Korin	Aug 1999	A
5961920	Soremark	Oct 1999	A
5997812	Burnham et al.	Dec 1999	A
6006659	Rosenthal	Dec 1999	A
6030578	McDonald	Feb 2000	A
6039928	Roberts	Mar 2000	A
6087764	Matei	Jul 2000	A
6162406	Michael	Dec 2000	A
6200307	Kasinkas et al.	Mar 2001	B1
6231820	Wedekamp	May 2001	B1
6245293	Fencl et al.	Jun 2001	B1
6254625	Rosenthal et al.	Jul 2001	B1
6258370	Behrends et al.	Jul 2001	B1
6258736	Massholder	Jul 2001	B1
6267924	Fencl et al.	Jul 2001	B1
6269680	Prieve et al.	Aug 2001	B1
6280615	Phillips et al.	Aug 2001	B1
6283986	Johnson	Sep 2001	B1
6301359	Roberts	Oct 2001	B1
6313470	Fencl et al.	Nov 2001	B1
6344176	Metzger	Feb 2002	B1
6365113	Roberts	Apr 2002	B1
6398970	Justel et al.	Jun 2002	B1
6403030	Horton, III	Jun 2002	B1
6447720	Horton, III et al.	Sep 2002	B1
6447721	Horton, III et al.	Sep 2002	B1
6458331	Roberts	Oct 2002	B1
6468433	Tribelski	Oct 2002	B1
6469308	Reed	Oct 2002	B1
6475433	McGeorge et al.	Nov 2002	B2
6490351	Roberts	Dec 2002	B1
6500267	Fencl et al.	Dec 2002	B1
6524529	Horton, III	Feb 2003	B1
6565803	Bolton et al.	May 2003	B1
6627000	Fencl et al.	Sep 2003	B2
6655577	Mihaylov et al.	Dec 2003	B2
6656424	Deal	Dec 2003	B1
6660227	Lopez Ordaz	Dec 2003	B2
6669838	Baarman	Dec 2003	B1
6707254	Moisan et al.	Mar 2004	B1
6730113	Eckhardt et al.	May 2004	B2
6730265	Horton, III	May 2004	B2
6737020	Horton, III et al.	May 2004	B1
6753537	Woo	Jun 2004	B2
6766097	Horton, III	Jul 2004	B2
6773584	Saccomanno	Aug 2004	B2
6776824	Wen	Aug 2004	B2
6784440	Fink et al.	Aug 2004	B2
6803587	Gadgil et al.	Oct 2004	B2
6861658	Fiset	Mar 2005	B2
6911177	Deal	Jun 2005	B2
6911657	Waluszko	Jun 2005	B2
6916452	Rix et al.	Jul 2005	B1
6924495	Brickley	Aug 2005	B1
6953940	Leighley et al.	Oct 2005	B2
6974958	Gadgil et al.	Dec 2005	B2
7002161	Greene	Feb 2006	B2
7084389	Spector	Aug 2006	B2
7169311	Saccomanno	Jan 2007	B2
7173255	Snowball	Feb 2007	B2
7175806	Deal et al.	Feb 2007	B2
7175807	Jones	Feb 2007	B1
7201767	Bhullar	Apr 2007	B2
7211813	Jensen	May 2007	B2
7217933	Gadgil et al.	May 2007	B2
7234586	Newman	Jun 2007	B1
7316200	Bosma et al.	Jan 2008	B2
7319230	Skaggs	Jan 2008	B2
7323065	Fencl et al.	Jan 2008	B2
7326387	Arts et al.	Feb 2008	B2
7372044	Ross	May 2008	B2
7416588	Burrows et al.	Aug 2008	B2
7445441	West et al.	Nov 2008	B2
7465942	Holden	Dec 2008	B2
7476885	Garcia et al.	Jan 2009	B2
7476888	Fiset	Jan 2009	B2
7498004	Saccomanno	Mar 2009	B2
7507980	Garcia et al.	Mar 2009	B2
7511283	Chor	Mar 2009	B2
7560706	Castelluccio	Jul 2009	B1
7598501	Jones	Oct 2009	B2
7642522	Egberts	Jan 2010	B2
7646000	Shih	Jan 2010	B2
7665181	Gebhard et al.	Feb 2010	B2
7683344	Tribelsky et al.	Mar 2010	B2
7691343	Ueberall	Apr 2010	B2
7692159	Lane et al.	Apr 2010	B2
7695673	Moisan et al.	Apr 2010	B2
7695675	Kaiser et al.	Apr 2010	B2
7791044	Taylor et al.	Sep 2010	B1
7829016	Deal et al.	Nov 2010	B2
7836548	Cho	Nov 2010	B2
7884336	Gibson	Feb 2011	B2
7888656	Freedgood	Feb 2011	B2
7982199	Deshays	Jul 2011	B2
7989779	Ray et al.	Aug 2011	B1
7994489	Fiset	Aug 2011	B2
8029739	Field et al.	Oct 2011	B2
8058629	Long	Nov 2011	B2
8067750	Deal	Nov 2011	B2
8083512	Adriansens	Dec 2011	B2
8084752	Ranta et al.	Dec 2011	B2
8101135	Lee et al.	Jan 2012	B2
8105532	Harmon et al.	Jan 2012	B2
8110819	Boyarsky et al.	Feb 2012	B2
8114346	Hyde et al.	Feb 2012	B2
8125333	Ressler et al.	Feb 2012	B2
8142713	Gordon	Mar 2012	B2
8143596	Yerby	Mar 2012	B2
8161596	Cheung et al.	Apr 2012	B2
8164073	Mohr	Apr 2012	B2
RE43332	Tribelsky et al.	May 2012	E
8168963	Ratcliffe	May 2012	B2
8173066	Mohr et al.	May 2012	B2
8203124	Havens et al.	Jun 2012	B2
8236239	Bernstein	Aug 2012	B2
8246839	Ueberall	Aug 2012	B2
8252099	Worrilow	Aug 2012	B2
8252100	Worrilow	Aug 2012	B2
8269190	Dornblaser et al.	Sep 2012	B2
8278628	Hamilton	Oct 2012	B2
8283639	Lane et al.	Oct 2012	B2
8296493	Engelhardt et al.	Oct 2012	B1
8297435	Lathem	Oct 2012	B2
8318090	Gordon	Nov 2012	B2
8330121	Douglas	Dec 2012	B2
8337770	Wind	Dec 2012	B2
8357330	Erdlen et al.	Jan 2013	B1
8357914	Caldwell	Jan 2013	B1
8366654	Iranitalab	Feb 2013	B2
8378324	Gardner, III	Feb 2013	B2
8381728	Rao et al.	Feb 2013	B2
8399853	Roiniotis	Mar 2013	B2
8399854	Crawford	Mar 2013	B1
8404273	Baumgart et al.	Mar 2013	B2
8421032	Dornseifer	Apr 2013	B2
8431075	Davis	Apr 2013	B2
8431910	Perry	Apr 2013	B1
8458922	Parisi et al.	Jun 2013	B2
8460353	Beran et al.	Jun 2013	B2
8466433	Ullman	Jun 2013	B2
8470239	Kerr	Jun 2013	B1
8481985	Neister	Jul 2013	B2
8506897	Davis	Aug 2013	B2
8512631	Kerr	Aug 2013	B2
8518017	Caluori	Aug 2013	B2
8519356	Boyle	Aug 2013	B2
8525126	Lee et al.	Sep 2013	B2
8525128	Mohr	Sep 2013	B2
8536541	Taylor et al.	Sep 2013	B2
8557188	Lo	Oct 2013	B2
8569715	Tantillo	Oct 2013	B1
8575567	Lyslo et al.	Nov 2013	B2
8372128	Reuben	Dec 2013	B2
8597569	Gruen et al.	Dec 2013	B2
8606981	Engelhardt et al.	Dec 2013	B2
8614425	Conradt et al.	Dec 2013	B2
8617464	Kerr	Dec 2013	B2
8624202	Gil	Jan 2014	B2
8631533	Gulian et al.	Jan 2014	B1
8633454	Durkin	Jan 2014	B2
8653481	Packman et al.	Feb 2014	B2
8662705	Roberts	Mar 2014	B2
8685318	Collard et al.	Apr 2014	B2
8698100	Schumacher	Apr 2014	B2
8710460	Dayton	Apr 2014	B2
8742366	Snowball	Jun 2014	B2
8747764	Burchman et al.	Jun 2014	B1
8747770	Davis	Jun 2014	B2
8753575	Neister	Jun 2014	B2
8754385	Gutman	Jun 2014	B1
8757160	Rao et al.	Jun 2014	B2
8779385	Noori	Jul 2014	B2
8791441	Lichtblau	Jul 2014	B1
8809807	Nelson et al.	Aug 2014	B2
8834788	Fogg et al.	Sep 2014	B2
8845928	Bernstein	Sep 2014	B2
8845961	Bernstein	Sep 2014	B2
8847174	Domenig et al.	Sep 2014	B2
8859994	Deal	Oct 2014	B2
8877124	Bergman	Nov 2014	B2
8890087	Ben-David et al.	Nov 2014	B2
8895938	Ullman	Nov 2014	B2
8895939	Lyslo et al.	Nov 2014	B2
8895940	Moskowitz et al.	Nov 2014	B2
8907304	Kreitenberg	Dec 2014	B2
8911664	Cavanaugh	Dec 2014	B1
8911677	Gerstner et al.	Dec 2014	B2
8921813	Palmer et al.	Dec 2014	B2
8928234	Kim et al.	Jan 2015	B2
8941078	Tantillo	Jan 2015	B2
8951468	Perry	Feb 2015	B1
8961872	Fehr et al.	Feb 2015	B2
8975605	Neister	Mar 2015	B2
8977796	Engelhardt et al.	Mar 2015	B2
8999237	Tumanov	Apr 2015	B2
8999238	Kreitenberg	Apr 2015	B2
9006683	Wen	Apr 2015	B2
9023274	Garner et al.	May 2015	B2
9024277	Domenig et al.	May 2015	B2
9034251	Gutman	May 2015	B1
9034254	Kim et al.	May 2015	B2
9044521	Farren	Jun 2015	B2
9045358	Greuel	Jun 2015	B2
9056147	Ma	Jun 2015	B2
9095633	Dayton	Aug 2015	B1
9101260	Desu-Kalyanam	Aug 2015	B2
9114183	Campagna	Aug 2015	B2
9114184	Messina et al.	Aug 2015	B2
9144618	Kreitenberg	Sep 2015	B2
9149548	Davis	Oct 2015	B2
9149549	Kreitenberg	Oct 2015	B2
9162000	Ullman	Oct 2015	B2
9168321	Oestergaard et al.	Oct 2015	B2
9186802	Parisi et al.	Nov 2015	B2
9198990	Fletcher	Dec 2015	B2
9205162	Deal et al.	Dec 2015	B2
9211352	Kassel et al.	Dec 2015	B2
9226985	Dam	Jan 2016	B2
9233182	Arlemark	Jan 2016	B2
9254342	Engelhardt et al.	Feb 2016	B2
9265174	Shostak et al.	Feb 2016	B2
9265849	Kerr	Feb 2016	B2
9265850	Davis et al.	Feb 2016	B2
9272058	Montgomery	Mar 2016	B1
9272059	Lyslo et al.	Mar 2016	B2
9289523	Lee	Mar 2016	B2
9289527	Lichtblau	Mar 2016	B1
9295286	Shin	Mar 2016	B2
9295741	Yerby	Mar 2016	B2
9295742	Rasooly et al.	Mar 2016	B2
9320818	Vardiel et al.	Apr 2016	B2
9345796	Stewart	May 2016	B2
9345798	Trapani	May 2016	B2
9352469	Stewart	May 2016	B2
9358313	Deal	Jun 2016	B2
9364573	Deshays et al.	Jun 2016	B2
9381265	Hamilton	Jul 2016	B2
9387268	Farren	Jul 2016	B2
9402985	Caluori	Aug 2016	B2
9408929	Ma	Aug 2016	B2
9415125	Chen et al.	Aug 2016	B2
9415126	Dobrinsky et al.	Aug 2016	B2
9439996	Gross	Sep 2016	B2
9463258	Kassel et al.	Oct 2016	B2
9468695	Liao et al.	Oct 2016	B2
9486548	Aurongzeb et al.	Nov 2016	B2
9492574	Rasooly et al.	Nov 2016	B2
9492577	Dayton	Nov 2016	B1
9498550	Kneissl et al.	Nov 2016	B2
9498551	Yanke	Nov 2016	B2
9511159	Kreiner et al.	Dec 2016	B2
9511163	Larsen	Dec 2016	B2
9522200	Boisvert	Dec 2016	B2
9526387	Li et al.	Dec 2016	B1
9550006	Boodaghians et al.	Jan 2017	B2
9555144	Garner et al.	Jan 2017	B2
9592312	Lyslo et al.	Mar 2017	B2
9597420	Maxik et al.	Mar 2017	B2
9603956	Newham	Mar 2017	B2
9603960	Dobrinsky et al.	Mar 2017	B2
9623130	Tumanov	Apr 2017	B2
9623131	Taboada et al.	Apr 2017	B2
9623133	Childress et al.	Apr 2017	B2
9623138	Pagan et al.	Apr 2017	B2
9630859	Chen	Apr 2017	B2
9662410	Mackin	May 2017	B2
9666424	Veloz et al.	May 2017	B1
9675720	Romo et al.	Jun 2017	B2
9676008	Huang	Jun 2017	B1
9682161	Farren et al.	Jun 2017	B2
9687575	Farren	Jun 2017	B2
9687577	Dobrinsky et al.	Jun 2017	B2
9687646	Sobue et al.	Jun 2017	B2
9700642	Neister	Jul 2017	B2
9707306	Farren	Jul 2017	B2
9717325	Mongan et al.	Aug 2017	B2
9718302	Young et al.	Aug 2017	B2
9724441	Shur et al.	Aug 2017	B2
9724442	Munn	Aug 2017	B1
9750831	Barreau et al.	Sep 2017	B2
9764050	Almeida et al.	Sep 2017	B1
9770522	Taskinen et al.	Sep 2017	B2
9782505	Lyslo et al.	Oct 2017	B2
9787113	Kim et al.	Oct 2017	B2
9789215	Collins et al.	Oct 2017	B1
9795701	Dayton	Oct 2017	B2
9801966	Garrett	Oct 2017	B2
9802019	Arcilla et al.	Oct 2017	B2
9803909	Son et al.	Oct 2017	B2
9814794	Dayton	Nov 2017	B2
9827339	Nunn et al.	Nov 2017	B2
9827340	Cheng et al.	Nov 2017	B2
9833525	Schumacher	Dec 2017	B2
9834456	Collins et al.	Dec 2017	B2
9839210	Stewart	Dec 2017	B2
9839707	Won	Dec 2017	B2
9855350	Dahlquist	Jan 2018	B1
9855351	Kim	Jan 2018	B2
9855353	Stacy	Jan 2018	B1
9856152	Bokermann et al.	Jan 2018	B2
9868651	Matlack et al.	Jan 2018	B2
9889217	Franc	Feb 2018	B2
9889219	Dayton	Feb 2018	B2
9901652	Cole et al.	Feb 2018	B2
9907870	Boodaghians et al.	Mar 2018	B2
9907871	Kreiner et al.	Mar 2018	B2
9912790	Kim et al.	Mar 2018	B2
9919067	Nevin	Mar 2018	B2
9925390	Yehezkel	Mar 2018	B2
9943617	Burchman et al.	Apr 2018	B1
9943618	Liao et al.	Apr 2018	B2
9950088	Garner et al.	Apr 2018	B2
9956307	Burapachaisri et al.	May 2018	B2
9968697	Phillips	May 2018	B1
9974873	Cole	May 2018	B2
9974875	Davis	May 2018	B2
10010633	Trapani	Jul 2018	B2
10010635	Jeong et al.	Jul 2018	B2
10022467	Chang	Jul 2018	B2
10024559	Gwak et al.	Jul 2018	B2
10029926	Lichi et al.	Jul 2018	B2
10039853	Munn	Aug 2018	B1
10046073	Farren et al.	Aug 2018	B2
10046076	Collins et al.	Aug 2018	B1
10046175	Gerber	Aug 2018	B2
10053251	Clusserath	Aug 2018	B2
10064966	Kassel et al.	Sep 2018	B2
10064968	Statham et al.	Sep 2018	B2
10071262	Randers-Pehrson et al.	Sep 2018	B2
10076582	Liao et al.	Sep 2018	B1
10086097	Dayton	Oct 2018	B2
10092664	Dayton	Oct 2018	B2
10092665	Lyslo et al.	Oct 2018	B2
10092669	Marshall	Oct 2018	B2
10117958	Dombrowsky et al.	Nov 2018	B2
10130726	Pujol et al.	Nov 2018	B2
10137213	St. Louis et al.	Nov 2018	B2
10139305	Salg	Nov 2018	B2
10151084	Koll et al.	Dec 2018	B2
10159761	Kreitenberg	Dec 2018	B2
10166308	Engelhardt et al.	Jan 2019	B2
10166309	Liao et al.	Jan 2019	B2
10183084	Cahan et al.	Jan 2019	B2
10183085	Dobrinsky et al.	Jan 2019	B2
10183086	Ullman	Jan 2019	B2
10186884	Kim et al.	Jan 2019	B2
10195298	Kreitenberg	Feb 2019	B2
10195299	Baker et al.	Feb 2019	B2
10201626	Rapp	Feb 2019	B1
10206548	Hall et al.	Feb 2019	B1
10207015	Dayton	Feb 2019	B2
10220106	Kim et al.	Mar 2019	B2
10226541	Trapani	Mar 2019	B2
10226542	Messina et al.	Mar 2019	B2
10228622	Kimsey-Lin	Mar 2019	B2
10232067	Kim et al.	Mar 2019	B2
10238763	Kreiner et al.	Mar 2019	B2
10245339	Shin et al.	Apr 2019	B2
10245340	Stibich et al.	Apr 2019	B2
10245341	Stibich et al.	Apr 2019	B2
10255466	Jinadatha	Apr 2019	B2
10258706	Henniges et al.	Apr 2019	B2
10265428	Gross et al.	Apr 2019	B1
10265429	Kreiner et al.	Apr 2019	B2
10265430	Liao et al.	Apr 2019	B2
10265432	Paranhos et al.	Apr 2019	B2
10265540	Yehezkel	Apr 2019	B2
10271932	Caluori	Apr 2019	B2
10272166	Mackin	Apr 2019	B2
10272167	Starkweather et al.	Apr 2019	B2
10272168	Shur et al.	Apr 2019	B2
10279057	Ma	May 2019	B2
10279059	Bettles et al.	May 2019	B2
10286094	Dobrinsky et al.	May 2019	B2
10293066	Dayton	May 2019	B2
10301806	Childress et al.	May 2019	B2
10307495	Mori et al.	Jun 2019	B2
10307501	Dayton	Jun 2019	B2
10307504	Munn	Jun 2019	B2
10314928	Dobrinsky et al.	Jun 2019	B2
10328166	Georgeson	Jun 2019	B2
10328168	Veloz et al.	Jun 2019	B1
10335505	Gil et al.	Jul 2019	B2
10342884	Bettles et al.	Jul 2019	B2
10351443	Bokermann et al.	Jul 2019	B2
10354857	Chen et al.	Jul 2019	B2
10363327	Liao et al.	Jul 2019	B2
10363328	Yanke	Jul 2019	B2
10363329	Childress et al.	Jul 2019	B2
10363330	Bettles et al.	Jul 2019	B2
10369243	Dayton	Aug 2019	B2
10369379	Randers-Pehrson et al.	Aug 2019	B2
10376604	Romo et al.	Aug 2019	B2
10383963	Toita et al.	Aug 2019	B2
10383964	Shatalov et al.	Aug 2019	B2
10383965	Dombrowsky	Aug 2019	B2
10391189	Stibich et al.	Aug 2019	B2
10401012	Owen et al.	Sep 2019	B2
10406253	Kreitenberg	Sep 2019	B2
10406254	Garner et al.	Sep 2019	B2
10413622	Mackin	Sep 2019	B2
10426852	Dobrinsky et al.	Oct 2019	B2
10426973	Williamson et al.	Oct 2019	B2
10427954	Vardiel et al.	Oct 2019	B2
10429014	Jenks	Oct 2019	B2
10439408	Bastiyali	Oct 2019	B1
10441670	Shur et al.	Oct 2019	B2
10441671	Sobhy et al.	Oct 2019	B2
10449263	Joshi	Oct 2019	B2
10451298	Matschke et al.	Oct 2019	B2
10456489	Dayton	Oct 2019	B2
10456496	Munn	Oct 2019	B2
10463759	Munn	Nov 2019	B2
10478515	Shur et al.	Nov 2019	B2
10485887	Ramanand et al.	Nov 2019	B2
10493176	McCormick et al.	Dec 2019	B2
10494273	Vardiel et al.	Dec 2019	B2
10500294	Paul et al.	Dec 2019	B2
10500296	Kreitenberg	Dec 2019	B2
10507311	Quisenberry	Dec 2019	B2
10512703	Dayton	Dec 2019	B2
10512704	Dytioco et al.	Dec 2019	B2
10517976	Shur et al.	Dec 2019	B2
10525153	Kim et al.	Jan 2020	B2
10525155	Lee et al.	Jan 2020	B2
10532119	Dombrowsky et al.	Jan 2020	B2
10543289	Taboada et al.	Jan 2020	B2
10549000	Yellen et al.	Feb 2020	B2
10550011	Jung et al.	Feb 2020	B2
10556025	Ufkes	Feb 2020	B2
10556026	Bilenko et al.	Feb 2020	B2
10556027	Kreiner et al.	Feb 2020	B2
10561750	Mintie et al.	Feb 2020	B2
10568981	Lyslo et al.	Feb 2020	B2
10576174	Shur et al.	Mar 2020	B2
10583212	Ufkes	Mar 2020	B2
10583213	Stibich et al.	Mar 2020	B2
10585218	Ufkes et al.	Mar 2020	B2
10588993	Quilici	Mar 2020	B2
10596280	Henderson et al.	Mar 2020	B1
10596281	Tchon et al.	Mar 2020	B1
10596282	Gil et al.	Mar 2020	B2
10596288	Bettles et al.	Mar 2020	B2
10597311	Mayrand	Mar 2020	B2
10603391	Mishkin et al.	Mar 2020	B2
10603394	Farren et al.	Mar 2020	B2
11006493	Meir et al.	May 2021	B1
11007292	Grenon et al.	May 2021	B1
11020498	Rosen et al.	Jun 2021	B2
11020501	Rosen et al.	Jun 2021	B1
11020502	Medendorp, Jr. et al.	Jun 2021	B1
11116858	Grenon et al.	Sep 2021	B1
20010042842	Leighley et al.	Nov 2001	A1
20010048891	McGeorge et al.	Dec 2001	A1
20020043504	Chen et al.	Apr 2002	A1
20020045848	Jaafar et al.	Apr 2002	A1
20020063954	Horton, III	May 2002	A1
20020083535	Fraden	Jul 2002	A1
20020085947	Deal	Jul 2002	A1
20020098109	Nelson et al.	Jul 2002	A1
20020117631	Gadgil et al.	Aug 2002	A1
20020146343	Jenkins et al.	Oct 2002	A1
20020162969	Reed	Nov 2002	A1
20020162970	Sasges	Nov 2002	A1
20030019505	Scheir et al.	Jan 2003	A1
20030021723	Lopez Ordaz	Jan 2003	A1
20030034459	Bonin	Feb 2003	A1
20030086817	Horton, III	May 2003	A1
20030086818	Holley, Jr. et al.	May 2003	A1
20030086831	Horton, III	May 2003	A1
20030086848	Saccomanno	May 2003	A1
20030089670	Saccomanno	May 2003	A1
20030103866	Wang et al.	Jun 2003	A1
20030127506	Braun, Jr.	Jul 2003	A1
20030168507	Mihaylov et al.	Sep 2003	A1
20030223904	Lakhdar Bacha	Dec 2003	A1
20040009091	Deal et al.	Jan 2004	A1
20040013777	Hallstadius	Jan 2004	A1
20040016887	Fink et al.	Jan 2004	A1
20040045806	Neff et al.	Mar 2004	A1
20040047776	Thomsen	Mar 2004	A1
20040055620	Fencl et al.	Mar 2004	A1
20040056201	Fink et al.	Mar 2004	A1
20040084630	Waluszko	May 2004	A1
20040089815	Woo	May 2004	A1
20040120844	Tribelsky et al.	Jun 2004	A1
20040120850	Kaiser	Jun 2004	A1
20040129894	Coulombe et al.	Jul 2004	A1
20040140347	Mihaylov et al.	Jul 2004	A1
20040146426	Biering et al.	Jul 2004	A1
20040146437	Arts et al.	Jul 2004	A1
20040158302	Chornenky et al.	Aug 2004	A1
20040175288	Horton, III	Sep 2004	A1
20040183461	Robert et al.	Sep 2004	A1
20040219056	Tribelsky et al.	Nov 2004	A1
20040222163	Saccomanno	Nov 2004	A1
20040232359	Fiset	Nov 2004	A1
20050013729	Brown-Skrobot et al.	Jan 2005	A1
20050022844	Field et al.	Feb 2005	A1
20050061241	West et al.	Mar 2005	A1
20050061743	Buttner	Mar 2005	A1
20050077482	Poppi et al.	Apr 2005	A1
20050092931	Gadgil et al.	May 2005	A1
20050101854	Larson et al.	May 2005	A1
20050156119	Greene	Jul 2005	A1
20050158206	Moisan et al.	Jul 2005	A1
20050163648	Liang	Jul 2005	A1
20050163652	Metzger et al.	Jul 2005	A1
20050163653	Crawford et al.	Jul 2005	A1
20050163668	Crawford et al.	Jul 2005	A1
20050175512	Yuen	Aug 2005	A1
20050178984	Brickley	Aug 2005	A1
20050187596	Fiset	Aug 2005	A1
20050220665	Ding	Oct 2005	A1
20050223998	Bosma et al.	Oct 2005	A1
20050230320	Evans	Oct 2005	A1
20050230638	Ancona et al.	Oct 2005	A1
20050230639	Ancona et al.	Oct 2005	A1
20050253086	Snowball	Nov 2005	A1
20050256553	Strisower	Nov 2005	A1
20060011556	Ueberall	Jan 2006	A1
20060011856	Skaggs	Jan 2006	A1
20060017025	Jensen	Jan 2006	A1
20060079948	Dawson	Apr 2006	A1
20060104859	Tribelsky	May 2006	A1
20060151715	Greene	Jul 2006	A1
20060185116	Lee et al.	Aug 2006	A1
20060186358	Couvillion	Aug 2006	A1
20060188389	Levy	Aug 2006	A1
20060192136	Gadgil et al.	Aug 2006	A1
20060213791	Holden	Sep 2006	A1
20060216193	Johnson et al.	Sep 2006	A1
20060255291	Harris	Nov 2006	A1
20060263275	Lobach	Nov 2006	A1
20070009377	Goodrich et al.	Jan 2007	A1
20070012340	Jones et al.	Jan 2007	A1
20070023710	Tom et al.	Feb 2007	A1
20070031281	Stevens	Feb 2007	A1
20070057197	Chor	Mar 2007	A1
20070075268	Harris	Apr 2007	A1
20070145292	Jones	Jun 2007	A1
20070164232	Rolleri et al.	Jul 2007	A1
20070164233	Mohr	Jul 2007	A1
20070194255	Garcia et al.	Aug 2007	A1
20070258851	Fogg et al.	Nov 2007	A1
20070260231	Rose et al.	Nov 2007	A1
20070272877	Tribelsky et al.	Nov 2007	A1
20070274879	Millikin	Nov 2007	A1
20070276455	Fiset	Nov 2007	A1
20080035864	Fiset	Feb 2008	A1
20080048541	Sumrall et al.	Feb 2008	A1
20080052872	Cho	Mar 2008	A1
20080056933	Moore et al.	Mar 2008	A1
20080061252	Garcia et al.	Mar 2008	A1
20080065175	Redmond et al.	Mar 2008	A1
20080067417	Lane et al.	Mar 2008	A1
20080067418	Ross	Mar 2008	A1
20080067419	Shih	Mar 2008	A1
20080073287	Kolber et al.	Mar 2008	A1
20080073595	Thiruppathi	Mar 2008	A1
20080075629	Deal et al.	Mar 2008	A1
20080077122	Boyden et al.	Mar 2008	A1
20080077123	Boyden et al.	Mar 2008	A1
20080077145	Boyden et al.	Mar 2008	A1
20080093210	Edwards	Apr 2008	A1
20080131329	Lin et al.	Jun 2008	A1
20080131330	Lyon et al.	Jun 2008	A1
20080159908	Redmond	Jul 2008	A1
20080199353	Mlodzinski et al.	Aug 2008	A1
20080199354	Gordon	Aug 2008	A1
20080203891	Gaertner et al.	Aug 2008	A1
20080210884	Egberts	Sep 2008	A1
20080213128	Rudy et al.	Sep 2008	A1
20080213129	van der Pol et al.	Sep 2008	A1
20080219883	Thur et al.	Sep 2008	A1
20080224066	Nolen et al.	Sep 2008	A1
20080253941	Wichers et al.	Oct 2008	A1
20080257355	Rao et al.	Oct 2008	A1
20080265179	Havens et al.	Oct 2008	A1
20080271282	Gebhard et al.	Nov 2008	A1
20080283769	Deshays	Nov 2008	A1
20080286145	Ratcliffe	Nov 2008	A1
20080286146	Schroll et al.	Nov 2008	A1
20080289649	Woytkiw	Nov 2008	A1
20080295271	Perunicic	Dec 2008	A1
20080306454	Sikora	Dec 2008	A1
20080308748	Burrows	Dec 2008	A1
20090000639	Tribelsky et al.	Jan 2009	A1
20090004050	Lee et al.	Feb 2009	A1
20090032527	Lee et al.	Feb 2009	A1
20090056044	Rizoiu et al.	Mar 2009	A1
20090068071	Hamilton	Mar 2009	A1
20090112297	Fiset	Apr 2009	A1
20090117001	Hyde et al.	May 2009	A1
20090123331	Ross	May 2009	A1
20090126145	D'Agostino et al.	May 2009	A1
20090130169	Bernstein	May 2009	A1
20090148358	Wind	Jun 2009	A1
20090155121	Mohr et al.	Jun 2009	A1
20090169425	Park et al.	Jul 2009	A1
20090169442	Levy et al.	Jul 2009	A1
20090179547	Auday et al.	Jul 2009	A1
20090184268	Garcia et al.	Jul 2009	A1
20090191100	Deal	Jul 2009	A1
20090196802	Streppel	Aug 2009	A1
20090205664	Lyon	Aug 2009	A1
20090218512	Ranta et al.	Sep 2009	A1
20090242075	Busick et al.	Oct 2009	A1
20090252646	Holden et al.	Oct 2009	A1
20090256085	Thiruppathi	Oct 2009	A1
20090257910	Segal	Oct 2009	A1
20090257912	Lane et al.	Oct 2009	A1
20090274576	Ressler	Nov 2009	A1
20090280028	Muggli et al.	Nov 2009	A1
20090285727	Levy	Nov 2009	A1
20090289015	Levy	Nov 2009	A1
20090294692	Bourke, Jr. et al.	Dec 2009	A1
20090304553	Gordon	Dec 2009	A1
20090311149	Freedgood	Dec 2009	A1
20090314956	Long	Dec 2009	A1
20090317309	Lee et al.	Dec 2009	A1
20090317506	Adriansens	Dec 2009	A1
20100003175	Gibson	Jan 2010	A1
20100007492	Ressler et al.	Jan 2010	A1
20100012147	Lu	Jan 2010	A1
20100028201	Neister	Feb 2010	A1
20100072399	Street et al.	Mar 2010	A1
20100076531	Beran et al.	Mar 2010	A1
20100104471	Harmon et al.	Apr 2010	A1
20100127189	Boyarsky et al.	May 2010	A1
20100143188	Roiniotis	Jun 2010	A1
20100168823	Strisower	Jul 2010	A1
20100186187	Cheung et al.	Jul 2010	A1
20100187437	Ueberall	Jul 2010	A1
20100193709	Dalton	Aug 2010	A1
20100212335	Lukitobudi	Aug 2010	A1
20100222852	Vasily et al.	Sep 2010	A1
20100237254	Mason et al.	Sep 2010	A1
20100253207	Joulaud et al.	Oct 2010	A1
20100266445	Campagna	Oct 2010	A1
20100314553	Yerby	Dec 2010	A1
20100320405	Gardner, III	Dec 2010	A1
20100326484	Wu	Dec 2010	A1
20110008205	Mangiardi	Jan 2011	A1
20110020175	Collard et al.	Jan 2011	A1
20110040236	Isaacs et al.	Feb 2011	A1
20110044848	Wright	Feb 2011	A1
20110054574	Felix	Mar 2011	A1
20110060272	Iranitalab	Mar 2011	A1
20110076196	Chittka et al.	Mar 2011	A1
20110081274	Packman et al.	Apr 2011	A1
20110099831	Parisi et al.	May 2011	A1
20110100865	Brink et al.	May 2011	A1
20110104004	Bobbitt	May 2011	A1
20110108143	Caluori	May 2011	A1
20110112232	Krishna et al.	May 2011	A1
20110138905	Kim et al.	Jun 2011	A1
20110139999	Clark et al.	Jun 2011	A1
20110158862	Kim et al.	Jun 2011	A1
20110162155	Wai	Jul 2011	A1
20110171080	Lo	Jul 2011	A1
20110213339	Bak	Sep 2011	A1
20110215261	Lyslo et al.	Sep 2011	A1
20110240883	Ullman	Oct 2011	A1
20110243789	Roberts	Oct 2011	A1
20110256019	Gruen et al.	Oct 2011	A1
20110272595	Neister	Nov 2011	A1
20110274581	Davis	Nov 2011	A1
20110274582	Davis	Nov 2011	A1
20110286882	Wu	Nov 2011	A1
20110291995	Shr et al.	Dec 2011	A1
20110305597	Farren	Dec 2011	A1
20110308917	Lathem	Dec 2011	A1
20120006995	Greuel	Jan 2012	A1
20120012136	Nguyen et al.	Jan 2012	A1
20120022619	Fiset	Jan 2012	A1
20120045363	Gil	Feb 2012	A1
20120061592	Dornblaser et al.	Mar 2012	A1
20120068088	Durkin	Mar 2012	A1
20120074334	Milligan	Mar 2012	A1
20120085926	Ingram et al.	Apr 2012	A1
20120093684	Martin et al.	Apr 2012	A1
20120097862	Snowball	Apr 2012	A1
20120107184	Asiyanbola et al.	May 2012	A1
20120116294	Boenig et al.	May 2012	A1
20120121457	Farren	May 2012	A1
20120126134	Deal et al.	May 2012	A1
20120134879	Tarifi	May 2012	A1
20120141322	Fogg	Jun 2012	A1
20120161031	NeCamp	Jun 2012	A1
20120165716	Reuben	Jun 2012	A1
20120168647	Davis	Jul 2012	A1
20120181447	Yerby	Jul 2012	A1
20120196011	Felix	Aug 2012	A1
20120227586	Chan et al.	Sep 2012	A1
20120227745	Arcilla et al.	Sep 2012	A1
20120228517	Mohr	Sep 2012	A1
20120230867	Kerr	Sep 2012	A1
20120240968	Schumacher	Sep 2012	A1
20120241644	Ben-David et al.	Sep 2012	A1
20120246863	Douglas	Oct 2012	A1
20120261590	Boyle	Oct 2012	A1
20120261593	Noori	Oct 2012	A1
20120156094	Gordon	Nov 2012	A1
20120280147	Douglas	Nov 2012	A1
20120282135	Trapani	Nov 2012	A1
20120305787	Henson	Dec 2012	A1
20120305804	Goldman	Dec 2012	A1
20120313006	Chiu	Dec 2012	A1
20120315186	Davis	Dec 2012	A1
20120319311	Nutter et al.	Dec 2012	A1
20120328474	Campagna	Dec 2012	A1
20130001435	Engelhardt et al.	Jan 2013	A1
20130002157	van de Ven et al.	Jan 2013	A1
20130004367	Roberts	Jan 2013	A1
20130015753	Son et al.	Jan 2013	A1
20130022495	Allen, IV et al.	Jan 2013	A1
20130026389	Lee et al.	Jan 2013	A1
20130037047	Saiger	Feb 2013	A1
20130045132	Tumanov	Feb 2013	A1
20130048876	Crawford	Feb 2013	A1
20130052079	Bernstein	Feb 2013	A1
20130062534	Cole	Mar 2013	A1
20130064733	Gerstner et al.	Mar 2013	A1
20130078142	Gordon	Mar 2013	A1
20130115146	Hamilton	May 2013	A1
20130126760	Klein et al.	May 2013	A1
20130129567	Gray	May 2013	A1
20130152921	Rao et al.	Jun 2013	A1
20130167854	Shin	Jul 2013	A1
20130175458	Kerr	Jul 2013	A1
20130175460	Farren	Jul 2013	A1
20130177474	Kerr	Jul 2013	A1
20130181141	Brueck et al.	Jul 2013	A1
20130195716	Fehr et al.	Aug 2013	A1
20130207002	Greuel et al.	Aug 2013	A1
20130214174	Domenig et al.	Aug 2013	A1
20130224071	Bernstein	Aug 2013	A1
20130234041	Deal	Sep 2013	A1
20130243646	Kearns et al.	Sep 2013	A1
20130243647	Garner et al.	Sep 2013	A1
20130259742	Kerr	Oct 2013	A1
20130269206	Parisi et al.	Oct 2013	A1
20130277574	Dayton	Oct 2013	A1
20130280125	Kim et al.	Oct 2013	A1
20130281921	Sobue et al.	Oct 2013	A1
20130294969	Chen et al.	Nov 2013	A1
20130299019	Caluori	Nov 2013	A1
20130299032	Caluori	Nov 2013	A1
20130303877	Strisower	Nov 2013	A1
20130303996	Rasooly et al.	Nov 2013	A1
20130323119	Alwan	Dec 2013	A1
20130323120	Ma	Dec 2013	A1
20130340460	Andros et al.	Dec 2013	A1
20140001109	Lee et al.	Jan 2014	A1
20140001374	Ullman	Jan 2014	A1
20140014228	Kolber et al.	Jan 2014	A1
20140034849	Lyslo et al.	Feb 2014	A1
20140044590	Trapani	Feb 2014	A1
20140050612	Kneissl et al.	Feb 2014	A1
20140056757	Chen et al.	Feb 2014	A1
20140059796	Boodaghians et al.	Mar 2014	A1
20140084185	Palmer et al.	Mar 2014	A1
20140091236	Jhawar et al.	Apr 2014	A1
20140107409	Bailey et al.	Apr 2014	A1
20140116961	Bokermann et al.	May 2014	A1
20140117250	Vardiel et al.	May 2014	A1
20140127077	Rock	May 2014	A1
20140140888	Neister	May 2014	A1
20140140893	Kohler	May 2014	A1
20140158909	Hamilton	Jun 2014	A1
20140158910	Fletcher	Jun 2014	A1
20140161663	Farren et al.	Jun 2014	A1
20140166900	Nelson et al.	Jun 2014	A1
20140175280	Tantillo	Jun 2014	A1
20140203188	Yerby	Jul 2014	A1
20140207215	Fiset	Jul 2014	A1
20140212332	Bergman	Jul 2014	A1
20140217306	Ferran et al.	Aug 2014	A1
20140217307	Messina et al.	Aug 2014	A1
20140222120	Fiset	Aug 2014	A1
20140227132	Neister	Aug 2014	A1
20140241941	Kreitenberg	Aug 2014	A1
20140245866	Hadlock et al.	Sep 2014	A1
20140248179	Engelhardt et al.	Sep 2014	A1
20140252247	Moskowitz et al.	Sep 2014	A1
20140263091	Carter, III et al.	Sep 2014	A1
20140271348	Deal et al.	Sep 2014	A1
20140271352	Stewart	Sep 2014	A1
20140271353	Oestergaard et al.	Sep 2014	A1
20140284499	Schumacher	Sep 2014	A1
20140291552	Schumacher	Oct 2014	A1
20140300581	Aurongzeb et al.	Oct 2014	A1
20140328985	Snowball	Nov 2014	A1
20140330452	Stewart	Nov 2014	A1
20140334974	Rasooly et al.	Nov 2014	A1
20140341777	Deshays et al.	Nov 2014	A1
20140346370	Dobrinsky et al.	Nov 2014	A1
20140356229	Farren	Dec 2014	A1
20140363335	Dam	Dec 2014	A1
20140368103	Son et al.	Dec 2014	A1
20140371710	Williamson	Dec 2014	A1
20140378792	Krimsky et al.	Dec 2014	A1
20150004056	Fogg et al.	Jan 2015	A1
20150008336	Rubinchikov et al.	Jan 2015	A1
20150017059	Arlemark	Jan 2015	A1
20150017061	Robison	Jan 2015	A1
20150028228	Almasy et al.	Jan 2015	A1
20150041679	Deal	Feb 2015	A1
20150056096	Hoover	Feb 2015	A1
20150057650	Grosser	Feb 2015	A1
20150064064	Kim et al.	Mar 2015	A1
20150064065	Kreitenberg	Mar 2015	A1
20150069263	Moyal	Mar 2015	A1
20150069266	Domenig et al.	Mar 2015	A1
20150069269	Lyslo et al.	Mar 2015	A1
20150069270	Shur et al.	Mar 2015	A1
20150073396	Randers-Pehrson et al.	Mar 2015	A1
20150076363	Wen	Mar 2015	A1
20150076369	Ullman	Mar 2015	A1
20150086420	Trapani	Mar 2015	A1
20150090903	Cole	Apr 2015	A1
20150090904	Cole	Apr 2015	A1
20150102235	Lee	Apr 2015	A1
20150114911	Helmore	Apr 2015	A1
20150115170	Shostak et al.	Apr 2015	A1
20150137762	Kim et al.	May 2015	A1
20150148734	Fewkes et al.	May 2015	A1
20150148776	Sobue et al.	May 2015	A1
20150151016	Boisvert	Jun 2015	A1
20150165078	Nevin	Jun 2015	A1
20150174276	Tumanov	Jun 2015	A1
20150182648	Engelhardt et al.	Jul 2015	A1
20150190537	Kerr	Jul 2015	A1
20150190538	Olvera et al.	Jul 2015	A1
20150196674	Newham	Jul 2015	A1
20150199487	Grauds et al.	Jul 2015	A1
20150209457	Bonutti et al.	Jul 2015	A1
20150209458	Kreitenberg	Jul 2015	A1
20150209459	Kreitenberg	Jul 2015	A1
20150209460	Kreitenberg	Jul 2015	A1
20150217012	Garner et al.	Aug 2015	A1
20150231288	Campagna	Aug 2015	A1
20150246152	Gross	Sep 2015	A1
20150251921	Sobanksi et al.	Sep 2015	A1
20150258234	Larsen	Sep 2015	A1
20150265346	Randers-Pehrson et al.	Sep 2015	A9
20150265735	Ma	Sep 2015	A1
20150290346	Kassel et al.	Oct 2015	A1
20150297766	Cole	Oct 2015	A9
20150306263	Yanke	Oct 2015	A1
20150306341	Hoefler	Oct 2015	A1
20150313354	Mongan et al.	Nov 2015	A1
20150328348	Colayco	Nov 2015	A1
20150338336	Dobrinsky et al.	Nov 2015	A1
20150343102	Romo et al.	Dec 2015	A1
20150343104	Maxik et al.	Dec 2015	A1
20150352348	Murphy-Shutorian et al.	Dec 2015	A1
20150359915	Farren et al.	Dec 2015	A1
20150367008	Romo et al.	Dec 2015	A1
20160000950	Won	Jan 2016	A1
20160000951	Kreiner et al.	Jan 2016	A1
20160008498	Boysset et al.	Jan 2016	A1
20160074547	Kreiner et al.	Jan 2016	A1
20160030612	Kim et al.	Feb 2016	A1
20160030613	Paul et al.	Feb 2016	A1
20160036952	Kim et al.	Feb 2016	A1
20160045633	Pagan et al.	Feb 2016	A1
20160074545	Kim	Mar 2016	A1
20160074546	Rizzone	Mar 2016	A1
20160082138	Kermode et al.	Mar 2016	A1
20160082281	Gerber et al.	Mar 2016	A1
20160083271	Chen	Mar 2016	A1
20160083272	Rajagopalan et al.	Mar 2016	A1
20160089206	Lee et al.	Mar 2016	A1
20160089459	Boodaghians et al.	Mar 2016	A1
20160089460	Jeong et al.	Mar 2016	A1
20160089461	Kassel et al.	Mar 2016	A1
20160101201	Franc et al.	Apr 2016	A1
20160101202	Gil et al.	Apr 2016	A1
20160106872	Martinez	Apr 2016	A1
20160107000	Randers-Pehrson et al.	Apr 2016	A1
20160114067	Dobrinsky et al.	Apr 2016	A1
20160121007	Dayton	May 2016	A1
20160121008	Taboada et al.	May 2016	A1
20160129141	Barreau et al.	May 2016	A1
20160136312	Park et al.	May 2016	A1
20160136314	Kreitenberg	May 2016	A1
20160151524	Lyslo et al.	Jun 2016	A1
20160151645	Williamson	Jun 2016	A1
20160158395	Hughes et al.	Jun 2016	A1
20160175896	Montgomery	Jun 2016	A1
20160176727	Younis	Jun 2016	A1
20160184467	Cheng et al.	Jun 2016	A1
20160206766	Yerby	Jul 2016	A1
20160220716	Childress et al.	Aug 2016	A1
20160228591	Engelhardt et al.	Aug 2016	A1
20160249436	Inskeep	Aug 2016	A1
20160250362	Mackin	Sep 2016	A1
20160251238	Matlack et al.	Sep 2016	A1
20160262369	Stewart	Sep 2016	A1
20160263261	Trapani	Sep 2016	A1
20160271280	Liao et al.	Sep 2016	A1
20160271282	Trapani	Sep 2016	A1
20160271803	Stewart	Sep 2016	A1
20160278895	Caluori	Sep 2016	A1
20160289272	Otterlei et al.	Oct 2016	A1
20160296649	Ramanand et al.	Oct 2016	A1
20160296650	Liao et al.	Oct 2016	A1
20160303265	Coles	Oct 2016	A1
20160317268	Dietzel et al.	Nov 2016	A1
20160317685	Pujol et al.	Nov 2016	A1
20160317686	Dayton	Nov 2016	A1
20160317687	Dayton	Nov 2016	A1
20160339127	Ma	Nov 2016	A1
20160339133	Lichtblau	Nov 2016	A1
20160339138	Nagao et al.	Nov 2016	A1
20160339262	Fiset	Nov 2016	A1
20160375165	Cole et al.	Dec 2016	A1
20160375166	Kreitenberg	Dec 2016	A1
20160376046	Clusserath	Dec 2016	A1
20170007215	Podoly	Jan 2017	A1
20170014537	Nunn et al.	Jan 2017	A1
20170028088	Maxik et al.	Feb 2017	A9
20170029292	Rajagopalan et al.	Feb 2017	A1
20170035918	Kassel et al.	Feb 2017	A1
20170035920	Boodaghians et al.	Feb 2017	A1
20170035923	Yanke	Feb 2017	A1
20170056540	Dayton	Mar 2017	A1
20170072077	Baker et al.	Mar 2017	A1
20170080116	Kreiner et al.	Mar 2017	A1
20170080251	Yehezkel	Mar 2017	A1
20170086560	Pires et al.	Mar 2017	A1
20170087262	Toita et al.	Mar 2017	A1
20170100498	Sobhy et al.	Apr 2017	A1
20170100500	Garner et al.	Apr 2017	A1
20170112953	Dayton	Apr 2017	A1
20170112954	Dayton	Apr 2017	A1
20170136136	Li et al.	May 2017	A1
20170143859	Lyslo et al.	May 2017	A1
20170157276	Dobrinsky et al.	Jun 2017	A1
20170157279	Dayton	Jun 2017	A1
20170174536	Robison et al.	Jun 2017	A1
20170182194	Shin et al.	Jun 2017	A1
20170182305	Kermode et al.	Jun 2017	A1
20170182332	Fiset	Jun 2017	A1
20170190397	Salters et al.	Jul 2017	A1
20170197002	Dobrinksky et al.	Jul 2017	A1
20170197493	Paranhos et al.	Jul 2017	A1
20170202988	Clark	Jul 2017	A1
20170209607	Safraoui	Jul 2017	A1
20170209608	Cameron	Jul 2017	A1
20170216466	Dujowich et al.	Aug 2017	A1
20170216468	Romo et al.	Aug 2017	A1
20170224853	Jay	Aug 2017	A1
20170224854	Mackin	Aug 2017	A1
20170224855	Mackin	Aug 2017	A1
20170224858	Stibich	Aug 2017	A1
20170232123	Burapachaisri et al.	Aug 2017	A1
20170246332	Marshall	Aug 2017	A1
20170253497	Mayrand	Sep 2017	A1
20170274223	Reidenberg et al.	Sep 2017	A1
20170284011	Jeong et al.	Oct 2017	A1
20170290932	Mori et al.	Oct 2017	A1
20170290933	Collins et al.	Oct 2017	A1
20170290935	Boodaghians et al.	Oct 2017	A1
20170290937	Dobrinsky et al.	Oct 2017	A1
20170296686	Cole	Oct 2017	A1
20170299289	Brais et al.	Oct 2017	A1
20170304472	Neister et al.	Oct 2017	A1
20170304473	Farren et al.	Oct 2017	A1
20170307234	Matschke et al.	Oct 2017	A1
20170314243	Koll et al.	Nov 2017	A1
20170333170	Caluori	Nov 2017	A1
20170333580	Cahan et al.	Nov 2017	A1
20170333582	Davis	Nov 2017	A1
20170333583	Shur et al.	Nov 2017	A1
20170333618	Krohn et al.	Nov 2017	A1
20170340153	Wise-Jarvis	Nov 2017	A1
20170340760	Starkweather et al.	Nov 2017	A1
20170340762	Ullman	Nov 2017	A1
20170348446	Golden, Sr.	Dec 2017	A1
20170360977	Stibich et al.	Dec 2017	A1
20170368213	Mintie et al.	Dec 2017	A1
20170368216	Regalado et al.	Dec 2017	A1
20170368220	Joshi	Dec 2017	A1
20170373516	Kim et al.	Dec 2017	A1
20180008735	Almeida	Jan 2018	A1
20180008736	Lyslo et al.	Jan 2018	A1
20180043043	Spector	Feb 2018	A1
20180044204	Lichi et al.	Feb 2018	A1
20180051447	Hills et al.	Feb 2018	A1
20180055959	Lin et al.	Mar 2018	A1
20180055960	Reiber et al.	Mar 2018	A1
20180055961	Noad	Mar 2018	A1
20180055964	Dayton	Mar 2018	A1
20180064833	Childress et al.	Mar 2018	A1
20180071414	Dujowich et al.	Mar 2018	A1
20180071417	Taboada et al.	Mar 2018	A1
20180085481	Schumacher	Mar 2018	A1
20180093001	Georgeson	Apr 2018	A1
20180110893	Chang	Apr 2018	A1
20180117194	Dobrinksky et al.	May 2018	A1
20180134351	Salters et al.	May 2018	A1
20180134584	Kolch et al.	May 2018	A1
20180140727	Romo et al.	May 2018	A1
20180154028	Offutt et al.	Jun 2018	A1
20180154029	Shr et al.	Jun 2018	A1
20180154032	Dombrowsky et al.	Jun 2018	A1
20180161468	Dayton	Jun 2018	A1
20180161594	Yehezkel	Jun 2018	A1
20180169279	Randers-Pehrson et al.	Jun 2018	A1
20180182607	Chen et al.	Jun 2018	A1
20180370821	Kishi et al.	Jun 2018	A1
20180185534	Dombrowsky et al.	Jul 2018	A1
20180185535	Dombrowsky et al.	Jul 2018	A1
20180193500	Safavi et al.	Jul 2018	A1
20180193501	Ufkes	Jul 2018	A1
20180193502	Ufkes	Jul 2018	A1
20180193504	Kreiner et al.	Jul 2018	A1
20180200396	Messina et al.	Jul 2018	A1
20180207302	Vasilenko	Jul 2018	A1
20180209613	Callahan	Jul 2018	A1
20180214585	Piper	Aug 2018	A1
20180214592	Garner et al.	Aug 2018	A1
20180214595	Munn	Aug 2018	A1
20180215634	Jung et al.	Aug 2018	A1
20180221519	Nguyen	Aug 2018	A1
20180221521	Shur et al.	Aug 2018	A1
20180224584	Shur et al.	Aug 2018	A1
20180236113	Gross et al.	Aug 2018	A1
20180236114	Davis	Aug 2018	A1
20180236116	Burapachaisri et al.	Aug 2018	A1
20180243582	Kaneda et al.	Aug 2018	A1
20180250428	Canfield	Sep 2018	A1
20180250429	Rock	Sep 2018	A1
20180250723	Schomer	Sep 2018	A1
20180256764	Kreitenberg	Sep 2018	A1
20180259256	Kim et al.	Sep 2018	A1
20180264150	Shur et al.	Sep 2018	A1
20180264151	Shur et al.	Sep 2018	A1
20180265382	Schuentz	Sep 2018	A1
20180272014	Dombrowsky	Sep 2018	A1
20180272016	Hunt	Sep 2018	A1
20180272017	Stibich et al.	Sep 2018	A1
20180289845	Chan	Oct 2018	A1
20180289847	McCormick et al.	Oct 2018	A1
20180289940	Spotnitz et al.	Oct 2018	A1
20180296709	Mishkin et al.	Oct 2018	A1
20180304225	Bourke, Jr.	Oct 2018	A1
20180326105	Crosby	Nov 2018	A1
20180333510	Lee et al.	Nov 2018	A1
20180339075	Kennedy et al.	Nov 2018	A1
20180343847	Ervin	Dec 2018	A1
20180343898	Alzeer et al.	Dec 2018	A1
20180353017	Miranda et al.	Dec 2018	A1
20180353629	Neister et al.	Dec 2018	A9
20180353631	Grinstead et al.	Dec 2018	A1
20180361001	Liao et al.	Dec 2018	A1
20180361008	Munn	Dec 2018	A1
20180369435	Dhiman et al.	Dec 2018	A1
20180369439	Brockschmidt et al.	Dec 2018	A1
20180369440	Dytioco et al.	Dec 2018	A1
20180373157	Kimsey-Lin	Dec 2018	A1
20190001007	Lyslo et al.	Jan 2019	A1
20190016610	Hoehne	Jan 2019	A1
20190022260	Cole	Jan 2019	A1
20190022261	Dayton	Jan 2019	A1
20190022263	Quilici	Jan 2019	A1
20190030195	Hatti et al.	Jan 2019	A1
20190031536	Vardiel et al.	Jan 2019	A1
20190038914	Igarashi et al.	Feb 2019	A1
20190046676	Dayton	Feb 2019	A1
20190053674	Hall et al.	Feb 2019	A1
20190054201	Zhang et al.	Feb 2019	A1
20190060495	Gil et al.	Feb 2019	A1
20190060496	Tillotson	Feb 2019	A1
20190070325	Preminger et al.	Mar 2019	A1
20190076558	Zhang-Miske et al.	Mar 2019	A1
20190076569	Peterson	Mar 2019	A1
20190083672	Munn	Mar 2019	A1
20190083673	Munn	Mar 2019	A1
20190091358	Liao et al.	Mar 2019	A1
20190091738	Chen	Mar 2019	A1
20190099507	Garrett	Apr 2019	A1
20190099508	Garrett	Apr 2019	A1
20190099613	Estes et al.	Apr 2019	A1
20190105415	Gross et al.	Apr 2019	A1
20190110746	Dau et al.	Apr 2019	A1
20190111168	Baumler et al.	Apr 2019	A1
20190111169	Flaherty et al.	Apr 2019	A1
20190117802	Hishinuma et al.	Apr 2019	A1
20190117806	Cahan et al.	Apr 2019	A1
20190117813	Dayton	Apr 2019	A9
20190126058	McCarthy	May 2019	A1
20190134242	Bonutti et al.	May 2019	A1
20190134249	Taboada et al.	May 2019	A1
20190134595	Bourke, Jr. et al.	May 2019	A1
20190142981	Kim et al.	May 2019	A1
20190142986	Zhang et al.	May 2019	A1
20190160190	Kreitenberg	May 2019	A1
20190160192	Fudakowski	May 2019	A1
20190160305	Randers-Pehrson et al.	May 2019	A1
20190162471	Stewart	May 2019	A1
20190167230	Cho et al.	Jun 2019	A1
20190167792	Sowemimo-Coker et al.	Jun 2019	A1
20190167827	Gaska et al.	Jun 2019	A1
20190171111	Kimsey-Lin	Jun 2019	A1
20190172336	Haidegger et al.	Jun 2019	A1
20190175780	Munn	Jun 2019	A1
20190184044	Yellen et al.	Jun 2019	A1
20190192708	Igarashi	Jun 2019	A1
20190192709	Igarashi	Jun 2019	A1
20190192844	Wegener et al.	Jun 2019	A1
20190201563	Swaney et al.	Jul 2019	A1
20190201570	Dobrinsky et al.	Jul 2019	A1
20190209722	Stibich et al.	Jul 2019	A1
20190214244	Park et al.	Jul 2019	A1
20190216958	Kreitenberg et al.	Jul 2019	A1
20190216964	Kreiner et al.	Jul 2019	A1
20190219506	Gould et al.	Jul 2019	A1
20190223585	Wigand et al.	Jul 2019	A1
20190224352	Rasooly et al.	Jul 2019	A1
20190231912	Dobrinsky	Aug 2019	A1
20190240363	Kreiner et al.	Aug 2019	A1
20190240365	Dombrowsky et al.	Aug 2019	A1
20190254903	Hag	Aug 2019	A1
20190255201	Rosen et al.	Aug 2019	A1
20190262484	Georgeson	Aug 2019	A1
20190262485	Ramanand et al.	Aug 2019	A1
20190262487	Gil et al.	Aug 2019	A1
20190262489	Yanai et al.	Aug 2019	A1
20190262493	Collins et al.	Aug 2019	A1
20190269810	Brehm	Sep 2019	A1
20190270630	Dahan et al.	Sep 2019	A1
20190274421	Cosolito	Sep 2019	A1
20190282718	Cole	Sep 2019	A1
20190290791	Baker et al.	Sep 2019	A1
20190290794	Brockschmidt	Sep 2019	A1
20190298869	Poulsen	Oct 2019	A1
20190298871	Dobrinsky	Oct 2019	A1
20190298875	Childress et al.	Oct 2019	A1
20190309248	Alibek et al.	Oct 2019	A1
20190313785	Jimenez et al.	Oct 2019	A1
20190321503	Warnell	Oct 2019	A1
20190321504	Dayton	Oct 2019	A1
20190321506	Zhang et al.	Oct 2019	A1
20190328915	Paul et al.	Oct 2019	A1
20190328919	Saad et al.	Oct 2019	A1
20190328920	Stibich et al.	Oct 2019	A1
20190336627	Lucio	Nov 2019	A1
20190336628	Dombrowsky	Nov 2019	A1
20190336632	Dombrowsky et al.	Nov 2019	A1
20190336714	Vazales et al.	Nov 2019	A1
20190345701	Koll et al.	Nov 2019	A1
20190351084	Garner et al.	Nov 2019	A1
20190351085	Dayton	Nov 2019	A1
20190351086	Dayton	Nov 2019	A1
20190365938	Romo et al.	Dec 2019	A1
20190374075	Barnett et al.	Dec 2019	A1
20190374664	Kay et al.	Dec 2019	A1
20190374665	Jo et al.	Dec 2019	A1
20190381336	Randers-Pehrson et al.	Dec 2019	A1
20190382597	Gross	Dec 2019	A1
20190388572	Cole et al.	Dec 2019	A1
20190388706	Randers-Pehrson et al.	Dec 2019	A1
20200030469	Neister et al.	Jan 2020	A1
20200030472	Kim et al.	Jan 2020	A1
20200054893	Yoon et al.	Feb 2020	A1
20200061223	Hallack	Feb 2020	A1
20200070214	Mangiardi	Mar 2020	A1
20200073199	Lin et al.	Mar 2020	A1
20200075972	Jorgenson et al.	Mar 2020	A1
20200078480	Starkweather et al.	Mar 2020	A1
20200078483	Eidman	Mar 2020	A1
20200085983	Ramanand et al.	Mar 2020	A1
20200093945	Jeong	Mar 2020	A1
20200215210	Rosen et al.	Jul 2020	A1
20200215214	Rosen et al.	Jul 2020	A1
20200215215	Randers-Pehrson et al.	Jul 2020	A1
20200246632	Naito	Aug 2020	A1
20200360554	Sakaguchi et al.	Nov 2020	A1
20200384144	Sakaguchi et al.	Dec 2020	A1

Foreign Referenced Citations (118)

Number	Date	Country
201481833	May 2010	CN
102772812	Nov 2012	CN
202961251	Jun 2013	CN
204972697	Jan 2016	CN
205011421	Feb 2016	CN
205181844	Apr 2016	CN
207304076	May 2018	CN
209490289	Oct 2019	CN
70087	Jan 1986	EP
582739	Feb 1994	EP
552189	Mar 1995	EP
1027082	Aug 2000	EP
1042006	Aug 2001	EP
919246	Apr 2002	EP
818206	Oct 2002	EP
916937	Jan 2005	EP
1453375	May 2005	EP
1721684	Jul 2008	EP
2127684	Dec 2009	EP
1962905	Feb 2010	EP
2303338	Apr 2011	EP
2198886	Jun 2011	EP
2303338	Aug 2011	EP
2391421	Dec 2011	EP
2288578	Feb 2012	EP
2391421	Jun 2012	EP
1523341	Sep 2012	EP
2175892	Sep 2012	EP
1866627	Sep 2013	EP
2683442	Jan 2014	EP
2729175	May 2014	EP
2683442	Aug 2014	EP
2780043	Sep 2014	EP
2953655	Dec 2015	EP
2968633	Jan 2016	EP
2996727	Mar 2016	EP
2999553	Mar 2016	EP
3003986	Apr 2016	EP
3016607	May 2016	EP
3129069	Feb 2017	EP
1887297	Apr 2017	EP
3148594	Apr 2017	EP
3150562	Apr 2017	EP
3160661	May 2017	EP
3162327	May 2017	EP
3164160	May 2017	EP
3162327	Jul 2017	EP
3195900	Jul 2017	EP
3206721	Aug 2017	EP
3234653	Oct 2017	EP
2709958	Dec 2017	EP
3256172	Dec 2017	EP
3302328	Apr 2018	EP
3328444	Jun 2018	EP
3335573	Jun 2018	EP
3338812	Jun 2018	EP
3373973	Sep 2018	EP
3421053	Jan 2019	EP
3436394	Feb 2019	EP
3442313	Feb 2019	EP
3466451	Apr 2019	EP
3473150	Apr 2019	EP
2654806	May 2019	EP
3082919	May 2019	EP
3495325	Jun 2019	EP
3111961	Jul 2019	EP
3111962	Jul 2019	EP
3326693	Aug 2019	EP
2582401	Sep 2019	EP
3253453	Sep 2019	EP
3520912	Sep 2019	EP
3560067	Oct 2019	EP
3003375	Nov 2019	EP
3193634	Nov 2019	EP
3316915	Nov 2019	EP
3562435	Nov 2019	EP
3581624	Dec 2019	EP
2997108	Feb 2020	EP
3578207	Mar 2020	EP
3623446	Mar 2020	EP
3560066	Apr 2020	EP
3411086	Jul 2020	EP
3073971	Jan 2021	EP
H03218764	Sep 1991	JP
H11128325	May 1999	JP
H11230899	Aug 1999	JP
2001332216	Nov 2001	JP
2003159570	Jun 2003	JP
2004128331	Apr 2004	JP
2005216647	Aug 2005	JP
2005218850	Aug 2005	JP
2005323654	Nov 2005	JP
2007220549	Aug 2007	JP
2007289641	Nov 2007	JP
2017059321	Mar 2017	JP
2017213263	Dec 2017	JP
2018019670	Feb 2018	JP
2018114197	Jul 2018	JP
2018114209	Jul 2018	JP
2018146413	Sep 2018	JP
2018177055	Nov 2018	JP
6490318	Mar 2019	JP
2019072411	May 2019	JP
2019116991	Jul 2019	JP
6558376	Aug 2019	JP
6561881	Aug 2019	JP
2019188127	Oct 2019	JP
6607623	Nov 2019	JP
2020000285	Jan 2020	JP
6660861	Mar 2020	JP
M512405	Nov 2015	TW
9607451	Mar 1996	WO
0191810	Dec 2001	WO
0242164	May 2002	WO
02092138	Nov 2002	WO
2019079976	May 2019	WO
2019079983	May 2019	WO
2019164810	Aug 2019	WO

Non-Patent Literature Citations (43)

Entry
Boeing, “Boeing Licenses Ultraviolet Wand to Healthe, Inc. to Counter COVID-19,” PRNewswire, Seattle, Sep. 22, 2020, https://investors.boeing.com/investors/investor-news/press-release-details/2020/Boeing-Licenses-Ultraviolet-Wand-to-Healthe-Inc.-to-Counter-COVID-19/default.aspx, 2 pages.
Healthe, “Healthe® Wand Pro,” Specification Sheet 111620, Version 7, Nov. 2020, available at https://healtheinc.com/app/media/2020/11/Healthe_WandPro_SpecSheet_v7.pdf, 2 pages.
U.S. Appl. No. 62/694,482.
U.S. Appl. No. 62/632,716.
U.S. Appl. No. 62/963,682.
U.S. Appl. No. 17/119,440.
International Patent Application No. PCT/US2020/066056.
Alphawire, “EcoCable® Mini,” Lit. No. EcoC-Mini-1409, 2014, 13 pages.
Apem, “Q8 Series: ∅8 mm panel mount LED indicators,” IND-Q8-2001, 2001, 7 pages.
Avago Technologies,“HSMF-C113 and HSMF-C115 Right Angle Tricolor Surface Mount ChipLEDs Data Sheet,” Document No. AV02-0611EN, Apr. 9, 2010, 8 pages.
Cui Devices, “CFM-80 Series DC Axial Fan,” Revision 1.05, Feb. 10, 2020, 7 pages.
Cypress Semiconductor, “CY8CKIT-059: PSoC® 5LP Prototyping Kit,” Document No. 630-60242-01, Revision 6, Jun. 16, 2015, 3 pages.
Cypress Semiconductor, “CY8CKIT-059: PSoC® 5LP Prototyping Kit Guide,” Document No. 001-96498, Revision G, Mar. 12, 2018, 48 pages.
Hirose Electric Co., Ltd, “LF10WBP-4S(31) Specification Sheet,” Jun. 14, 2019, 1 page.
Hirose Electric Co., Ltd, “LF10WBR-4P Specification Sheet,” Sep. 10, 2016, 1 page.
IDX, “DUO-C150 Compact 143Wh Li-ion V-Mount Battery Data Sheet,” Jan. 2019, https://cdn.shopify.com/s/files/1/0282/9559/4123/files/DUO-C150_Datasheet_2.pdf, 2 pages.
Klaran, “Klaran® WD Series UVC LEDs Data Sheet,” 2018, www.klaran.com, Crystal IS, Inc., 8 pages.
Linear Technology, “LT6118 Current Sense Amplifier, Reference and Comparator with POR,” Document No. 6118f, 2014, www.linear.com/LT6118, 24 pages.
LiTech, “LiTech-180W Series Specification of Lithium Battery,” Apr. 15, 2020, 7 pages.
LiTech, “Specification of LiTech Power Li-ion 12S2P 44.4V 6.4Ah Battery Pack,” Model No. LP12S2P8A8AL01, Document No. DSE-A-1214-01, Version 0, approved Mar. 30, 2020, LiTech Power Co.,Ltd., 6 pages.
LiTech, “Specification of LiTech Power Li-ion 12S2P 44.4V 6.4Ah Battery Pack,” Model No. LP12S2P8A8AL01, Document No. DSE-A-1214-01, Version 1, approved Mar. 30, 2020, LiTech Power Co.,Ltd., 6 pages.
Maxim Integrated, “MAX9611/MAX9612: High-Side, Current-Sense Amplifiers with12-Bit ADC and Op Amp/Comparator,” Dcoument No. 19-5543, Revision 5, Dec. 2019, 20 pages.
Molex, “Micro Fit (3.0) Right Angle SMT Clips Single Row / Tape and Reel,” Document No. SD-43650-004, Revision E1, Apr. 27, 2018, 1 page.
Molex, “Milligrid 2mm Pitch, SMT Vertical Shrouded Header,” Document No. SD-87832-0001, Revision A12, Jul. 23, 2019, 13 pages.
Molex, “Picoblade 1.25 Header Assy Dip VT Tin Plating Type,” Document No. 530470000-SD, Revision A, Oct. 15, 2019, 1 page.
Molex, “Pico-Lock1.5 Hdrassy SGLRW R/A ETP H=2 for Circuit Size 4-8, 10,12,” Document No. 5040500000-SD, Revision A, Feb. 18, 2019, 6 pages.
NXP Semiconductors, “MMA8451Q, 3-axis, 14-bit/8-bit digital accelerometer,” Document No. MMA8451Q, Revision 10.3, Feb. 2017, 59 pages.
Omron Corporation, “D2MQSubminiature Basic Switch,” available as early as Mar. 24, 2020 from https://omronfs.omron.com/en_US/ecb/products/pdf/en-d2mq.pdf, 4 pages.
Recom, “RCD-48 Series: Constant Current Buck LED Driver,” Feb. 2017, www.recom-power.com, 4 pages.
Sunled, “3. 0mmx1.0 Right Angle SMD Chip LED Lamp,” Part No. XZFBB56W-1, Document No. XDsB4251, Version3-Z, Mar. 28, 2016, 4 pages.
Texas Instruments, “LM75A Digital Temperature Sensor and Thermal Watchdog With Two-Wire Interface,” Document No. SNOS808P, Jan. 2000, revised Dec. 2014, 30 pages.
Wurth Elektronik, “3.00 MM Male Single Row Vertical Header,” WERI Part No. 662 0xx 111 22, Sep. 10, 2014, 3 pages.
XP Power, “LED Driver LDU Series,” Aug. 21, 2014, xppower.com, 4 pages.
Non-Final Office Action for U.S. Appl. No. 17/139,342, dated Mar. 1, 2021, 6 pages.
Notice of Allowance for U.S. Appl. No. 17/139,342, dated Apr. 8, 2021, 9 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/030260, dated May 25, 2021, 7 pages.
Non-Final Office Action for U.S. Appl. No. 17/139,448, dated May 11, 2021, 14 pages.
Invitation to Pay Additional Fees for International Patent Application No. PCT/US2021/030269, dated Jul. 7, 2021, 3 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/030269, dated Sep. 16, 2021, 19 pages.
Non-Final Office Action for U.S. Appl. No. 17/139,537, dated Apr. 21, 2021, 12 pages.
Notice of Allowance for U.S. Appl. No. 17/139,537, dated Jul. 12, 2021, 8 pages.
Non-Final Office Action for U.S. Appl. No. 17/139,578, dated Feb. 22, 2021, 9 pages.
Notice of Allowance for U.S. Appl. No. 17/139,578, dated Mar. 24, 2021, 11 pages.

Related Publications (1)

	Number	Date	Country
	20210379224 A1	Dec 2021	US

Provisional Applications (2)

	Number	Date	Country
	63079193	Sep 2020	US
	63019231	May 2020	US

Divisions (1)

	Number	Date	Country
Parent	17139537	Dec 2020	US
Child	17409403		US

Ultraviolet (UV) light emission device employing visible light for target distance guidance, and related methods of use, particularly suited for decontamination

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Abstract