Patent Grant
9822514
Automatic faucets and bathroom flushers have been used for many years. An automatic faucet typically includes an optical or other sensor that detects the presence of an object, and an automatic valve that turns water on and off, based on a signal from the sensor. An automatic faucet may include a mixing valve connected to a source of hot and cold water for providing a proper mixing ratio of the delivered hot and cold water after water actuation. The use of automatic faucets conserves water and promotes hand washing, and thus good hygiene. Similarly, automatic bathroom flushers include a sensor and a flush valve connected to a source of water for flushing a toilet or urinal after actuation. The use of automatic bathroom flushers generally improves cleanliness in public facilities.
In an automatic faucet, an optical or other sensor provides a control signal and a controller that, upon detection of an object located within a target region, provides a signal to open water flow. In an automatic bathroom flusher, an optical or other sensor provides a control signal to a controller after a user leaves the target region. Such systems work best if the object sensor is reasonably discriminating. An automatic faucet should respond to a user's hands, for instance, it should not respond to the sink at which the faucet is mounted, or to a paper towel thrown in the sink. Among the ways of making the system discriminate between the two it has been known to limit the target region in such a manner as to exclude the sink's location. However, a coat or another object can still provide a false trigger to the faucet. Similarly, this could happen to automatic flushers due to a movement of bathroom doors, or something similar.
An optical sensor includes a light source (usually an infra-red emitter) and a light detector sensitive to the IR wavelength of the light source. For faucets, the emitter and the detector (i.e., a receiver) can be mounted on the faucet spout near its outlet, or near the base of the spout. For flushers, the emitter and the detector may be mounted on the flusher body or on a bathroom wall. Alternatively, only optical lenses (instead of the emitter and the receiver) can be mounted on these elements. The lenses are coupled to one or several optical fibers for delivering light from the light source and to the light detector. The optical fiber delivers light to and from the emitter and the receiver mounted below the faucet.
In the optical sensor, the emitter power and/or the receiver sensitivity is limited to restrict the sensor's range to eliminate reflections from the sink, or from the bathroom walls or other installed objects. Specifically, the emitting beam should project on a valid target, normally clothing, or skin of human hands, and then a reflected beam is detected by the receiver. This kind of sensor relies on the reflectivity of a target's surface, and its emitting/receiving capabilities. Frequently, problems arise due to highly reflective doors and walls, mirrors, highly reflective sinks, the shape of different sinks, water in the sink, the colors and rough/shiny surfaces of fabrics, and moving users who are walking by but not using the facility. Mirrors, doors, walls, and sinks are not valid targets, although they may reflect more energy back to the receiver than rough surfaces at a right angle incidence. The reflection of valid targets such as various fabrics varies with their colors and the surface finish. Some kinds of fabrics absorb and scatter too much energy of the incident beam, so that less of a reflection is sent back to the receiver.
A large number of optical or other sensors are powered by a battery. Depending on the design, the emitter (or the receiver) may consume a large amount of power and thus deplete the battery over time (or require large batteries). The cost of battery replacement involves not only the cost of batteries, but more importantly the labor cost, which may be relatively high for skilled personnel.
There is still a need for an optical sensor for use with automatic faucets or automatic bathroom flushers that can operate for a long period of time without replacing the standard batteries. There is still a need for reliable sensors for use with automatic faucets or automatic bathroom flushers.
The present invention is directed to novel optical sensors and novel methods for sensing optical radiation. The novel optical sensors and the novel optical sensing methods are used, for example, for controlling the operation of automatic faucets and flushers. The novel sensors and flow controllers (including control electronics and valves) require only small amounts of electrical power for sensing users of bathroom facilities, and thus enable battery operation for many years. A passive optical sensor includes a light detector sensitive to ambient (room) light for controlling the operation of automatic faucets or automatic bathroom flushers.
According to one aspect, an optical sensor for controlling a valve of an electronic faucet or bathroom flusher includes an optical element located at an optical input port and arranged to partially define a detection field. The optical sensor also includes a light detector and a control circuit. The light detector is optically coupled to the optical element and the input port, wherein the light detector is constructed to detect ambient light. The control circuit is constructed for controlling opening and closing of a flow valve. The control circuit is also constructed to receive signal from the light detector corresponding to the detected light.
According to another aspect, a system for controlling a valve of an electronic faucet or bathroom flusher includes a first light detector, a second light detector, and a control circuit. The first light detector is optically coupled to a first input port and is constructed to detect ambient light arriving to the first detector from a first field of view (i.e., a first detection field). The second light detector is optically coupled to a second input port and constructed to detect ambient light arriving to the second detector from a second field of view (i.e., a second detection field). The control circuit controls opening and closing of a flow valve, wherein the control circuit is constructed to receive first data from the first light detector, corresponding to the detected ambient light from the first field of view, and to receive second data from the second light detector, corresponding to the detected ambient light from the second field of view. The control circuit is constructed to determine each the opening and closing of the flow valve based on a background level of the ambient light and a light level caused by a user.
Preferred embodiments of this aspect include one or more of the following:
The control circuit is further constructed to control the opening and closing by executing a detection algorithm employing detection of increase and decrease of the ambient light due to the presence of a user within at least one of the fields of view.
The detection algorithm processes detection of the increase of ambient light in the fields of view due to the presence of the user. The detection algorithm processes detection of the decrease of ambient light in the fields of view due to the presence of the user. The detection algorithm processes detection of the increase of ambient light in one of the fields of view and detection of the decrease of ambient light in the other of the fields of view due to the presence of the user.
The system further includes an optical element located at one of the input ports associated with one of the light detectors, wherein the optical element is arranged to partially define the field of view of the light detector. The system may include two optical elements located at the input ports associated with the light detectors, wherein the optical elements are arranged to partially define the field of view of the light detector. The optical element may include an optical fiber, a lens, a pinhole, a slit or a mirror.
According to this aspect, the system may control the flow valve included in an electronic faucet. Alternatively, the system may control the flow valve included in a bathroom flusher system.
The light detector may include a photodiode or a photoresistor. The optical element and the optical input port are constructed so that the light detector receives light in the range of 1 lux to 1000 lux.
According to yet another aspect, a system for controlling a valve of an electronic faucet or bathroom flusher includes a light detector and a control circuit. The light detector is optically coupled to an input port and is constructed to detect ambient light arriving to the detector from a field of view. The control circuit controls opening and closing of a flow valve, wherein the control circuit is constructed to receive signal from the light detector corresponding to the detected ambient light and to determine each the opening and closing of the flow valve based on detected levels of the ambient light measured over several time intervals. The control circuit is further constructed to control the opening and closing by executing a detection algorithm employing detection of increase and decrease of the ambient light due to the presence of a user within the field of view.
Preferred embodiments of this aspect include one or more of the following: The detection algorithm includes determining a transition from background data to target data. The determination is performed by differentiating optical data received from the light detector. The determination is performed using a stochastic algorithm on optical data from the light detector. The stochastic algorithm includes Kalman filter. Alternatively, the determination is performed using a predictive algorithm on optical data received from the light detector. The predictive algorithm includes Jacobi algorithm.
The control circuit is constructed to sample periodically the detector based on the amount of previously detected light. The control circuit is constructed to determine the opening and closing of the flow valve based on a background level of the ambient light and a present level of the ambient light, along with the stability of any light changes detected. The control circuit uses the changes in ambient light to detect arrival of a user and departure of the user, and the presence of a user based on the stability of the change. These parameters cause opening and closing of the valve. The passive optical sensor uses only a light detector that measures the increase or decrease or stability over short times, of primarily ambient light. The sensor's algorithm may execute several states described below. These are entered, for example, when the target is moving in; after the basically stationary target reached the sensor; and upon the departure of the target. From each of these states, the algorithm can enter the idle or a reset state if an error causes the prior state. Alternatively, the control circuit is constructed to open and close the flow valve based on detecting presence of a user, which it does similarly.
According to yet another aspect, an optical sensor for an electronic faucet includes an optical input port, an optical detector, and a control circuit. The optical input port is arranged to receive light. The optical detector is optically coupled to the input port and constructed to detect the received light. The control circuit controls opening and closing of a faucet valve, or a bathroom flusher valve.
Preferred embodiments of this aspect include one or more of the following features: The control circuit is constructed to sample periodically the detector based on the amount of light detected. The control circuit is constructed to adjust a sample period based on the detected amount of light after determining whether a facility is in use. The detector is optically coupled to the input port using an optical fiber. The input port may be located in an aerator of the electronic faucet. The system includes batteries for powering the electronic faucet.
Automatic faucet system 9 includes a faucet body 12 and an aerator 30, including a sensor port 34. Automatic faucet system 9 also includes a faucet base 14 and screws 16A and 16B for attaching the faucet to a deck 18. A cold water pipe 20A and a hot water pipe 20B are connected to a mixing valve 22 providing a mixing ratio of hot and cold water (which ratio can be changed depending on the desired water temperature). Water conduit 24 connects mixing valve 22 to a solenoid valve 38. A flow control valve 38 controls water flow between water conduit 24 and a water conduit 25. Water conduit 25 connects valve 38 to a water conduit 26 partially located inside faucet body 12, as shown. Water conduit 26 delivers water to aerator 30. Automatic faucet system 8 also includes a control module 50 for controlling a faucet sensor and solenoid valve 38, powered by batteries located in battery compartment 39.
Referring to
Alternatively, the distal end of fiberoptic cable 52 is polished and oriented to emit or to receive light directly (i.e., without the optical lens). Again, the distal end of fiberoptic cable 52 is arranged to have the field of view (for example, field of view A) directed toward sink 11, somewhat coaxial within the water stream discharged from aerator 30. Alternatively, sensor port 34 includes other optical elements, such as an array of pinholes or an array of slits having a selected size, geometry and orientation. The size, geometry and orientation of the array of pinholes or the array of slits is designed to provide a selected detection pattern (shown in
Referring still to
Preferably, the passive sensor 36 has a field of view somewhat coaxial within the water stream discharged from aerator 30, when the faucet is turned on. Passive sensor 70 has a field of view D that excludes sink 11 and extends beyond the sink to detect a user standing at the sink. The optical elements, such as an array of pinholes or an array of slits have a selected size, geometry and orientation. The size, geometry and orientation of the array of pinholes, or the array of slits are designed to provide a selected detection pattern (shown in
The optical sensors are passive optical sensors that detect a visible or infrared light detector optically coupled to sensor port 34. There is no light source (i.e., no light emitter) associated with the optical sensor. The visible or near infrared (NIR) light detectors detect light arriving at the corresponding sensor port. The detector provides the corresponding electrical signal to a controller located in control unit 50. The light detector (i.e., light receiver) may be a photodiode, or a photoresistor (or some other optical intensity element having an electrical output, whereby the sensory element will have the desired optical sensitivity). The optical sensor using a photo diode also includes an amplification circuitry. Preferably, the light detector detects light in the range from about 400-500 nanometers up to about 950-1000 nanometers. The light detector is primarily sensitive to ambient light and not very sensitive to body heat (e.g., infrared or far infrared light).
Dual flow valve 60 is constructed and arranged to simultaneously control water flow in both pipes 21A and 21B upon actuation by a single actuator 201. Specifically, valve 60 includes two flow valves arranged for controlling flow of hot and cold water in the respective water lines. The solenoid actuator 201 is coupled to a pilot mechanism for controlling two flow valves. The two flow valves are preferably diaphragm operated valves (but may also be piston valves, or large flow-rate “fram” valves). Dual flow valve 60 includes a pressure release mechanism constructed to change pressure in a diaphragm chamber of each diaphragm operated valve and thereby open or close each diaphragm valve for controlling water flow. Dual flow valve 60 is described in detail in PCT Application PCT/US01/43277, filed on Nov. 20, 2001, which is incorporated by reference.
Referring still to
Referring to
Passive sensor 70 has a field of view D (
Referring to
A sensor port 33 is coupled to faucet body 12 and is designed to have a field of view shown in
The design and operation of actuator 201 is described in detail in PCT Applications PCT/US02/38757; PCT/US02/38758; and PCT/US02/41576, all of which are incorporated by reference as if fully provided herein.
Referring to
Passive sensors 80 and 90 may include one or several optical elements designed to provide the field of view shown in
A user standing in front of a faucet will affect the amount of ambient (room) light arriving at the sink and thus will affect the amount of light arriving at the optical detector. On the other hand, a person just moving in the room will not affect significantly the amount of detected light. A user having his hands under the faucet will alter the amount of ambient light being detected by the optical detector even more. Thus, the passive optical sensor can detect the user's hands and provide the corresponding control signal. Here, the detected light does not depend significantly on the reflectivity of the target surface (unlike for optical sensors that use both a light emitter and a receiver). After hand washing, the user removing his hands from under the faucet will again alter the amount of ambient light detected by the optical detector. Then, the passive optical sensor provides the corresponding control signal to the controller (explained in connection with
In the algorithm, detector 33 has to first detect the user, and after detector 34 detects the user's hands the water flow is initiated. During the water flow, both passive sensors detect the user, while sensor 34 may experience an increased data noise due to the hand movements of the user washing his hands. After passive sensor 34 no longer detects the user, the water flow may be closed upon some change detected by passive sensor 33, presumably due to the user removing his or her hands from under the faucet and perhaps stepping away from the sink. This detection pattern also eliminates errors due to, for example, a paper towel or other objects left in the sink (being detected by sensor 34) since passive sensor 33 will no longer detect the user.
Using appropriate selection of the optical elements described in connection with
Field of view E may also be achieved using two passive optical sensors 80 and 90 as shown in
Bathroom flushers 100 and 100A may have a modular design, wherein their cover can be partially opened to replace the batteries or the electronic module. Bathroom flushers with such a modular design are described in U.S. Patent Application 60/448,995, filed on Feb. 20, 2003, which is incorporated by reference for all purposes.
In general, the field of view of a passive optical sensor can be formed using optical elements such as beam forming tubes, lenses, light pipes, reflectors, arrays of pinholes and arrays of slots having selected geometries. These optical elements can provide a down-looking field of view that eliminates invalid targets such as mirrors, doors, and walls. Various ratios of the vertical field of view to horizontal field of view provide different options for target detection. For example, the horizontal field of view may be 1.2 wider than the vertical field of view or vice versa. A properly selected field of view can eliminate unwanted signals from an adjacent faucet or urinal. The detection algorithm includes a calibration routine that accounts for a selected field of view including the field's size and orientation.
Optical data graphs 180 and 190 exhibit two transition regions for the user entering the field of view. The first transition region (region 184 or 194) is quite steep, while the second transition region (region 185 or 195) is less steep, enabling a better detection. Further improvement of detection is achieved by the combination of the measured optical data patterns 150, 170, 180 and 190, using several passive sensors as described above.
Referring to
We note that, as shown in
If the clear and target have similar light levels then there will be a symmetric transition pattern with a target delay in between. (Target situation 2.) There is a requirement for a minimum and maximum target delay time (i.e., 0<t0 and it is unlikely that a target will stay longer than t1, for valid time t, t0<t<t1.) The background and noise levels can be superimposed to transition target and clear levels at any time. The noise levels may or may not mask signal levels (transition target clear).
The algorithm measures light level at the preset intervals and can use filter measurement to reduce measurement and background noise. Then, the algorithm takes the derivative of detected optical signal. The algorithm may executes the following:
Assume transition started add level to energy of current transition
Mark time of start of transition
Change sampling time if necessary
Add level to energy of current transition
Check if time scale of transition is in range. If yes, push transition time and energy onto software stack. Else no transition erase energy, time associated reset sampling time
Check stack for any transitions longer than t1 in stack and erase.
Other detection algorithms can use various numerical algorithms such as stochastic algorithms (e.g., Kalman filter) or various predictive algorithms (e.g., Jacobi algorithm) to detect the transitions from background level to target level, from a background level to an intermediate level, or from a target level from an intermediate level or a new background level. The use of the stochastic algorithm and the predictive algorithm is particularly useful when the passive sensors are used to control a faucet, where the decision time is limited. That is, a user expects to receive water within a second from the time he or she places his or her hands under the faucet. If there is a delay in water delivery, the user will think that the faucet is out of order. On the other hand, when using passive sensors with the bathroom flushers a time delay is acceptable because a user cannot usually exit the field of view and a new user cannot enter the field of view in a second. Therefore, the delay in flush initiation is acceptable.
“No battery” detector generates pulses to microcontroller 254 in form of “No Battery” signals to notify microcontroller 254. Low Battery detector is coupled to the battery/power regulation through the 6.0V power. When power drops below 4.2V, the detector generates a pulse to the microcontroller (i.e., low battery signal). When the “low battery” signal is received, microcontroller will flash indicator 280 (e.g., an LED) with a frequency of 1 Hz, or may provide a sound alarm. After flushing 2000 times under low battery conditions, microcontroller will stop flushing, but still flash the LED.
As described in connection with
A manual button switch may be formed by a reed switch, and a magnet. When the button is pushed down by a user, the circuitry sends out a signal to the clock/reset unit through manual signal IRQ, then forces the clock/reset unit to generate a reset signal. At the same time, the level of the manual signal level is changed to acknowledge to microcontroller 254 that it is a valid manual flush signal.
Referring still to
Microcontroller 254 can receive an input signal from an external input element (e.g., a push button) that is designed for manual actuation or control input for actuator 260. Specifically, microcontroller 254 provides control signals 256A and 256B to power driver 258, which drives the solenoid of actuator 260. Power driver 258 receives DC power from battery and voltage regulator 272 regulates the battery power to provide a substantially constant voltage to power driver 258. An actuator sensor 262 registers or monitors the armature position of actuator 260 and provides a control signal 265 to signal conditioner 273. A low battery detection unit 275 detects battery power and can provide an interrupt signal to microcontroller 254.
Actuator sensor 262 provides data to microcontroller 254 (via signal conditioner 273) about the motion or position of the actuator's armature and this data is used for controlling power driver 258. The actuator sensor 262 may be an electromagnetic sensor (e.g., a pick up coil) a capacitive sensor, a Hall effect sensor, an optical sensor, a pressure transducer, or any other type of a sensor.
Preferably, microcontroller 254 is an 8-bit CMOS microcontroller TMP86P807M made by Toshiba. The microcontroller has a program memory of 8 Kbytes and a data memory of 256 bytes. Programming is done using a Toshiba adapter socket with a general-purpose PROM programmer. The microcontroller operates at 3 frequencies (fc=16 MHz, fc=8 MHz and fs=332.768 kHz), wherein the first two clock frequencies are used in a normal mode and the third frequency is used in a low power mode (i.e., a sleep mode). Microcontroller 254 operates in the sleep mode between various actuations. To save battery power, microcontroller 254 periodically samples optical sensor unit 252 for an input signal, and then triggers power consumption controller 268. Power consumption controller 268 powers up signal conditioner 273 and other elements. Otherwise, optical sensor unit 252, voltage regulator 272 (or voltage boost 272) and signal conditioner 273 are not powered to save battery power. During operation, microcontroller 254 also provides indication data to indicator 280. Control electronics 250 may receive a signal from the passive optical sensor or the active optical sensor described above. The passive optical sensor includes only a light detector providing a detection signal to microcontroller 254.
Low battery detection unit 275 may be the low battery detector model no. TC54VN4202EMB, available from Microchip Technology. Voltage regulator 272 may be the voltage regulator part no. TC55RP3502EMB, also available from Microchip Technology (http://www.microchip.com). Microcontroller 254 may alternatively be a microcontroller part no. MCU COP8SAB728M9, available from National Semiconductor.
To open a fluid passage, microcontroller 254 sends OPEN signal 256B to power driver 258, which provides a drive current to the drive coil of actuator 261 in the direction that will retract the armature. At the same time, coils 263A and 263B provide induced signal to the conditioning feedback loop, which includes the preamplifier and the low-pass filter. If the output of a differentiator 269 indicates less than a selected threshold calibrated for the retracted armature (i.e., the armature did not reach a selected position), microcontroller 254 maintains OPEN signal 256B asserted. If no movement of the solenoid armature is detected, microcontroller 254 can apply a different (higher) level of OPEN signal 256B to increase the drive current (up to several times the normal drive current) provided by power driver 258. This way, the system can move the armature, which is stuck due to mineral deposits or other problems.
Microcontroller 254 can detect the armature displacement (or even monitor armature movement) using induced signals in coils 263A and 263B provided to the conditioning feedback loop. As the output from differentiator 269 changes in response to the armature displacement, microcontroller 254 can apply a different (lower) level of OPEN signal 256B, or can turn off OPEN signal 256B, which in turn directs power driver 258 to apply a different level of drive current. The result usually is that the drive current has been reduced, or the duration of the drive current has been much shorter than the time required to open the fluid passage under worst-case conditions (that has to be used without using an armature sensor). Therefore, the control system saves considerable energy and thus extends the life of battery 270.
Advantageously, the arrangement of coil sensors 263A and 263B can detect latching and unlatching movement of the actuator armature with great precision. (However, a single coil sensor, or multiple coil sensors, or capacitive sensors may also be used to detect movement of the armature.) Microcontroller 254 can direct a selected profile of the drive current applied by power driver 258. Various profiles may be stored in microcontroller 254, and may be actuated based on the fluid type, the fluid pressure (water pressure), the fluid temperature (water temperature), if the time actuator 261 has been in operation since installation or last maintenance, a battery level, input from an external sensor (e.g., a movement sensor or a presence sensor), or other factors. Based on the water pressure and the known sizes of the orifices, the automatic flush valve can deliver a known amount of flush water.
The detection circuit 252, used by the passive sensor enables a significant reduction in energy consumption, and includes a detection element D (e.g., a photodiode or a photoresistor), two comparators (U1A and U1B) connected to provide a read-out from the detection element upon receipt of a high pulse. Preferably, the detection element is a photoresistor. The voltage VCC is +5 V (or +3V) received from the power source. Resistors R2 and R3 are voltage dividers between VCC and the ground. Diode D1 is connected between the pulse input and output line to enable the readout of the capacitance at capacitor C1 charged during the light detection.
Preferably, the photoresistor is designed to receive light of intensity in the range of 1 lux to 1000 lux, by appropriate design of optical lens 54 or the optical elements shown in
Referring still to
By virtue of the elimination of the need to employ an energy-consuming IR light source used in the active optical sensor, the system can be configured so as to achieve a longer battery life (usually many years of operation without changing the batteries). Furthermore, the passive sensor enables a more accurate means of determining presence of a user, the user motion, and the direction of user's motion.
The preferred embodiment as it relates to which type of optical sensing element is to be used is dependent upon the following factors: The response time of a photoresistor is on the order or 20-50 milliseconds, whereby a photodiode is on the order of several microseconds, therefore the use of a photoresistor will require a significantly longer time form which impacts overall energy use.
Furthermore, the passive optical sensor can be used to determine light or dark in a facility and in turn alter the sensing frequency (as implemented in the faucet detection algorithm). That is, in a dark facility the sensing rate is reduced under the presumption that in such a modality the faucet or flusher will not be used. The reduction of sensing frequency further reduces the overall energy consumption, and thus this extends the battery life.
The microcontroller reads out optical data as follows: First, all charge pins are set to Hi-Z (just like no Vcc, no current goes to capacitor). Then, the input/discharge pin is set as output, and is set “low” so that capacitor C1 discharges from this pin. Next, the discharge pin is charged as input. At this moment, the logic of this pin is “low”. Then, the charge pin is set to “Hi.” The microcontroller selects charge 0, or charge 0+charge X (X=1, 2, 3). Thus, the current goes from charge 0+chargeX to the capacitor, and at the same time the timer is started. The capacitor voltage will increase, when it reaches ⅔ Vcc (which is the microcontroller power supply, and it's also I/O output voltage). At this point the logic in input/discharge pin will turn from “low” to “high” and the timed is stopped. The timer value corresponded to the charge time, which is depend on charge current (that goes through photodetector D, and through one or several parallel resistors). By selecting different parallel resistors and charge together with photocell, the timer resolution can be adjusted and the maximum charge time can be limited.
Algorithm 300 (shown in
When a target moves closer, the target blocks the ambient light, especially if wearing dark, light-absorbent clothes, so that the passive sensor will detect less light while the target comes into the field of view. At this time, pulse width measurements will go up. More light will be detected as the target leaves the facility, so pulse width will go down. On the other hand, if the target wears a specific-kind of reflective clothes the passive sensor will detect more light while the target comes into the field of view. The microcontroller measures a smaller pulse width (i.e., more light) as the target enters the field of view, and a longer pulse width (less light) as the target moves away. Both possibilities are covered in the presented algorithms.
The algorithm has a preferred (working) light range for a photoresistor or a photodiode, where it best detects a target's presence. In the present embodiment, the photoresistor has a working light range from approximately 100 counts to 27,000 counts. Below this range, there is BrightMode, where background light is too bright to detect a target properly (i.e., the pulse width is below 100 counts). Above this range, there is DarkMode, where background light is too dark to detect a target (i.e., the pulse width is above 27,000 counts). Within the preferred light range, algorithm 300 has two options: NotTargetMode and TargetMode. In the NotTargetMode, no target has been detected, but the system checks for an approaching target. In the TargetMode, a target has already been detected, and the system looks for changes from one stage to another to determine if water flow should be initiated. These stages include: TargetIn, TargetStav, TargetOut, and TargetLeave.
In the TargetIn stage, light changes show the target is moving towards the sensor. In the TargetStay stage, stable light levels show the target is staying in front of the sensor for a particular period of time. In the TargetOut stage, the target is moving, and changes in light indicate that the light conditions are returning to those measured previously (or other background conditions). Finally, in the TargetLeave stage, light conditions are stable and have basically returned to those previous to the target being detected (or other background conditions).
The microcontroller constantly cycles through the algorithm, where it wakes up every 250 milliseconds (step 302, or another preset time), determines the mode it was last in (based on a previously set flag), and evaluates what mode it should go to based on the measured pulse width (p), similarly to algorithm 600 in
Referring to
In regular use the microcontroller wakes up and scans the photoresistor at step 306. It checks the current light level, as well as its previous status, set based on light levels, to make a decision as to what action to take next. The system generally works best in usual ambient light, so it has been set up with predefined thresholds for its working light range. In algorithm 540, these are preferably approximately 44 lux for a high (Level_Hi), and 33,000 lux for a low level (Level_Lo). If the light range is between 44 to 33,000 lux, and had not been darker or brighter in the previous cycle, the system remains in one of two modes: TargetMode or NotTargetMode, with this last one being the default. Therefore, if within the working light range, the microcontroller will go directly through steps 308 and 310. In steps 312 and 314 it finds out whether it had previously been in darker (DarkMode) or brighter (BrightMode) conditions than those in its working range. If this is not the case, and no targets have been detected, it will go into NotTargetMode at steps 316 to 332 (
Changes in light that cause the microcontroller to be outside its working light range also play a role in this system. Referring to
In Normal to Bright mode,
In Normal to Dark mode,
If the light had been outside the working range in previous cycles but now is within it, however, the system moves through steps 308 and 310 in
If the unit had been in BrightMode and now is within the working light range (314 to 330 and
If the conditions in step 368 are not the case, the microcontroller checks whether the DayModeCounter has been counting for longer than 4 sec. (369). If not, it exits to begin cycling anew. If it did count for over 4 sec., it will take the maximum value of light detected in the last 4 seconds as the background (step 372), set NotTargetMode in step 374, exit and start cycling anew.
If the unit had been in DarkMode and is now within the working light range (312 to 330 and
Referring to
Still referring to
However, a similar scenario can take place if a target, instead of blocking light when coming in, reflects it due to the clothes being worn. In that case, p would be less than the previous background (398), and the system would go through similar steps as described above (406 and 408) to determine that the Deriv. is greater than the threshold value. If that is the case, it is likely that the greater amount of light is due to a user coming in and reflecting light, so the microcontroller sets the mode as TargetMode at a stage of TargetInLo (414), saves TempBackground (416) and also exits. If no light change large enough to be a likely target is sensed in NotTargetMode, the system exits to continue cycling without changing the mode, and will continue scanning for a target as long as it remains within the working light range set.
Once the stage of TargetInHi or TargetInLo is set, and the microcontroller cycles once more, it will go to TargetMode (
Referring still to
If the potential target reflects light and was set as TargetInLo, the microcontroller will be at step 484 in
If p is not lower than the background since first detecting the potential target (step 490), the StandByCounter begins to count here as well (492) to make sure that the change detected previously was not merely a change in light. If p is higher than the background for more than 4 sec. (step 494), the previously detected change was likely also a temporary change in background light, and the microcontroller sets NotTargetMode (step 502) and exits.
Referring to
If p is not greater than the threshold set in 516 (step 518), the microcontroller sets threshold (step 520), calculates Delta in this case as the current background minus the current value of p (step 522), and checks whether this Delta is greater than the threshold (step 524). If this is the case, it sets TargetInLo (step 530), since it is likely that the changes being perceived are due to the target still coming in, and then it exits. If not (step 524), and none of the above conditions are met, it exits and begins anew. Once the system has set the stage as TargetOutHi (464,
For the parallel condition TargetOutLo (532,
Referring to
In each of the algorithms, there are three light conditions on which activity depends: bright, dark, and ambient light. As a general rule, the algorithms function best in ambient (or customary) light conditions, when changes in light due to users being nearby are most evident. Therefore, most activity occurs in ambient light conditions. In this case, when lower light levels are detected starting from ambient light, a user is likely blocking it, and is using the facility. When somewhat higher light levels are evident, a user is likely reflecting it, and is once again, likely using the facility.
As previously stated, the system functions using the principle that, not only will a user in front of the unit being used change the light level being detected, but that a user will have to remain stably in front of a unit in use. Therefore stability of the light conditions also plays a role in determining whether or not a user is nearby. Changes in light levels would be stable if a user is truly making use of the unit in question. Referring to
Algorithm 600 has three light modes: a Bright Mode (Mode 1), a Dark Mode (Mode 3), and a Normal Mode (Mode 2). The Bright Mode (Mode 1) is set as the microcontroller mode when resistance is less than 2 kΩ (Pb), corresponding to large amounts of light detected (
The microcontroller is constantly cycling through algorithm 600, where it will wake up (for example) every 1 second, determine which mode it was last in (due to the amount of light it detected in the prior cycle). From the current mode, the microcontroller will evaluate what mode it should go to based on the current pulse width (p) measurement, which corresponds to the resistance value of the photoresistor.
The microcontroller goes through 6 states in Mode 2. The following are the states required to initiate the flush: An Idle status in which no background changes in light occur, presumably because there are no users present, and in which the microcontroller calibrates the ambient light; a TargetIn status, in which a target moves into the field of the sensor; an In8Seconds status, during which the target is in the field of the sensor, and the pulse width measured is stable for 8 seconds (if the target leaves after 8 seconds, there is no flush); n After8Seconds status, in which the target is in the sensor's field, and the pulse width is stable for more than 8 seconds, meaning the target has remained in front of the sensor for that time (and after which, if the target leaves, there is a cautionary flush); a TargetOut status, in which the target is moving away, out of the field of the sensor; an In2 Seconds status, in which the background is stable after the target leaves. After this last status, the microcontroller flushes, and goes back to the Idle status.
As previously stated, the system functions using the principle that, not only will a user in front of the unit being used change the light levels being detected, but that a user will have to remain in front of a unit to use it. Therefore stability of the light conditions also plays a role in determining whether or not a user is nearby. Changes in light levels would be stable if a user is truly making use of the unit in question. The flusher, for example, uses that principle in the following manner (
If then there is a progressive change (that is, unstable light levels) towards background light levels once more, the person is now once again moving in front of the unit, and is likely moving away from it (“TargetOut”). Once that light level, now closer to background is stable, the user is likely to have left once more (“In2 Sec”), and the unit prepares to flush in a specific period of time.
When the target moves closer to the sensor, the target can block the light, particularly when wearing dark, light-absorbent clothes. Thus, the sensor will detect less light during the TargetIn status, so that resistance will go up (causing what will later be termed a TargetInUp status), while the microcontroller will detect more light during the TargetOut status, so that resistance will go down (later termed a TargetOutUp status). However, if the target wears light, reflective clothes, the microcontroller will detect more light as the target gets closer to it, in the TargetIn status (causing what will later be described as a TargetInDown status), and less during the TargetOut status (later termed a TargetOutDown status). Two seconds after the target leaves the toilet, the microcontroller will cause the toilet to flush, and the microcontroller will return to the Idle status.
To test whether there is a target present, the microcontroller checks the Stability of the pulse width, or how variable the p values have been in a specific period, and whether the pulse width is more variable than a constant, selected background level, or a provided threshold value of the pulse width variance (Unstable). The system uses two other constant, pre-selected values in algorithm 600, when checking the Stability of the p values to set the states in Mode 2. One of these two pre-selected values is Stable1, which is a constant threshold value of the pulse width variance. A value below means that there is no activity in front of unit, due to the p values not changing in that period being measured. The second pre-selected value used to determine Stability of the p values is Stable2, another constant threshold value of the pulse width variance. In this case a value below means that a user has been motionless in front of the microcontroller in the period being measured.
The microcontroller also calculates a Target value, or average pulse width in the After8Sec status, and then checks whether the Target value is above (in the case of TargetInUp) or below (in the case of TargetInDown) a particular level above the background light intensity: BACKGROUND×(1+PERCENTAGEIN) for TargetInUp, and BACKGROUND×(1−PERCENTAGEIN) for TargetInDown. To check for TargetOutUp and TargetOutDown, the microcontroller uses a second set of values: BACKGROUND×(1+PERCENTAGEOUT) and BACKGROUND×(1−PERCENTAGEOUT).
Referring to
Referring to
If the microcontroller was previously in Mode 1, but the value of p is now greater than 2 kΩ but less than 2 MΩ (622), for greater than 60 seconds (634) based on the timer 1 count (632), all Mode 1 timers will be reset (644), the microcontroller will set Mode 2 (646) as the system mode, so that the microcontroller will start in Mode 2 in the next cycle 600, and the microcontroller will go to sleep (612). However, if p changes while timer 1 counts for 60 seconds (134 to 148), Mode 1 will remain the microcontroller mode and the microcontroller will go to sleep (612) until the next cycle 600 starts.
If the microcontroller was previously in Mode 1, and p is now greater than or equal to 2 MΩ (624) while timer 2 counts (636) for greater than 8 seconds (638), all Mode 1 timers will be reset (650), the microcontroller will set Mode 3 (652) as the new system mode, and the microcontroller will go to sleep (612) until the next cycle 600 starts. However, if p changes while timer 2 counts for 8 seconds, the microcontroller will go to sleep (steps 638 to 612), and Mode 1 will continue to be set as the microcontroller mode until the start of the next cycle 600.
Referring to
If the microcontroller was previously in Mode 3 based on the value of p having been greater than or equal to 2 MΩ, and the value of p is still greater than or equal to 2 MΩ (820), the microcontroller will reset timers 3 and 4 (822), the microcontroller will go to sleep (612), and Mode 3 will continue to be set as the microcontroller mode until the start of the next cycle 600.
If the microcontroller was previously in Mode 3, but p is now between 2 kΩ and 2 MΩ (824), for a period measured by timer 4 (826) as longer than 2 seconds (828), timers 3 and 4 will be reset (830), Mode 2 will be set as the mode (832) until the next cycle 600 starts, and the microcontroller will go to sleep (612). However, if p changes while timer 4 counts for longer than 2 seconds, Mode 3 will remain the microcontroller mode, and the microcontroller will go from step 828 to step 612, going to sleep until the next cycle 600 starts. If an abnormal value of p occurs, the microcontroller will go to sleep (612) until a new cycle starts.
Referring to
However, if now p is greater than or equal to 2 MΩ (658) for a period measured by timer 6 (668) as longer than 8 seconds (670), the toilet is not in Idle status (i.e., there are background changes, 680), and p remains greater than or equal to 2 MΩ while timer 6 counts for over 5 minutes (688), the system will flush (690). After flushing, timers 5 and 6 will be reset (692), Mode 3 will be set as the microcontroller mode (694), and the microcontroller will go to sleep (612). Otherwise, if p changes while timer 6 counts for longer than 5 minutes, the system will go from step 688 to 612, and go to sleep.
If the microcontroller mode was previously set as Mode 2, now p is greater than or equal to 2 MΩ (658) for a period measured by timer 6 (668) as more than 8 seconds (670), but the toilet is in Idle status (680), timers 5 and 6 will be reset (682), Mode 3 will be set as microcontroller mode (684), and the microcontroller will go to sleep at step 612.
If p is greater or equal to 2 MΩ, but changes while timer 6 counts (668) to greater than 8 seconds (670), the microcontroller will go to sleep (612), and Mode 2 will remain as the microcontroller mode. If p is within a different value, the microcontroller will go to step 660 (shown in
Referring to
At this point, when the status of the microcontroller is found to be Idle (672), the microcontroller goes on to step 675. In step 675, if the Stability is found to be greater than the constant Unstable value, meaning that there is a user present in front of the unit, and the Target value is larger than the Background×(1+PercentageIn) value, meaning that the light detected by the microcontroller has decreased, this leads to step 680 and a TargetInUp status (i.e., since a user came in, towards the unit, resistance increased because light was blocked or absorbed), and the microcontroller will go to sleep (612), with Mode 2 TargetInUp as the microcontroller mode and status.
When the conditions set in step 675 are not true, the microcontroller will check if those in 677 are. In step 677, if the Stability is found to be greater than the constant Unstable value, due to a user in front of the unit, but the Target value is less than the Background×(1−PercentageIn) value, due to the light detected increasing, this leads to a “TargetInDown” status in step 681, (i.e., since a user came in, resistance decreased because light off of his clothes is reflected), and the microcontroller will go to sleep (612), with Mode 2 TargetInDown as the microcontroller mode and status. However, if the microcontroller status is not Idle (672), the microcontroller will go to step 673 (shown in
Referring to
If the TargetInDown status (686) had been set in the previous cycle, the system will check whether Stability is less than Stable2 and Target is less than Background×(1−PercentageIn) at the same time in step 693. If this is so, which would mean that there is a user motionless in front of the unit, with more light being detected, the microcontroller will advance status to In8SecDown (701), and will then go to sleep (612).
If the two requirements in step 693 are not met, the microcontroller will check if Stability is less than Stable1 while at the same time Target is greater than Background×(1−PercentageIn) in step 698. If both are true, the status will be set as Mode 2 Idle (703), due to these conditions signaling that there is no activity in front of the unit, and that there is a large amount of light being detected by the unit, and it will go to sleep (612). If Stability and Target do not meet either set of requirements from steps 693 or 698, the microcontroller will go to sleep (612), and Mode 2 will continue to be the microcontroller status. If status is not Idle, TargetInUp or TargetInDown, the microcontroller will continue as in step 695 (shown in
Referring to
Referring to
If the timer does not count for longer than 8 seconds while Stability and Target remain at those ranges, the microcontroller will not advance the status, and will go to sleep (612). If the requirements of step 718 are not met by the Stability and Target values, the In8SecTimer will be reset (720), and the microcontroller status will be set to TargetInDown (722), where the microcontroller will continue to step 673 (
Referring to
If Stability was not less than Stable1, the microcontroller checks whether it is greater than Unstable, and whether Target is greater than Background×(1+PercentageOut) (738). If both simultaneously meet these criteria, meaning that there is a user moving in front of the unit, but there is more light being detected because they are moving away, the microcontroller advances to Mode 2 TargetOutUp as the microcontroller status (740), and the microcontroller goes to sleep (612). If Stability and Target do not meet the two criteria in step 738, the microcontroller goes to sleep (612).
If the microcontroller was in After8SecDown (750), it will check whether the Stability is less than Stable1 at step 752. If so, timer 7 will begin to count (754), and if it counts for greater than 15 minutes (756), the microcontroller will flush (758), Idle status will be set (760), and the microcontroller will go to sleep (612). If Stability does not remain less than Stable1 until timer 7 counts to greater than 15 minutes, the microcontroller will go to sleep (612) until the next cycle.
If the Stability is not found to be less than Stable1 at step 752, the microcontroller will check whether Stability is greater than Unstable, while at the same time Target is less than Background×(1−PercentageOut) at step 762. If so, this means that there is a user in front of the unit, and that it detects less light because they are moving away, so that it will advance the status to TargetOutDown at step 764, and will go to sleep (612). Otherwise, if both conditions in step 762 are not met, the microcontroller will go to sleep (612). If the Mode 2 state is none of those covered in
Referring to
If the microcontroller is in TargetOutDown status (782), it will check whether Stability is less than Stable1, and Target greater than Background×(1−PercentageOut) simultaneously (783). If so, it would mean that there is no activity in front of the unit, and that there is less light reaching the unit, so that it will advance status to In2Sec (784), and go to sleep (612). However, if Stability and Target do not meet both criteria of step 783, the microcontroller will check whether Stability is greater than Unstable, and Target is less than Background×(1−PercentageOut) simultaneously in step 785. If so, the microcontroller will set status as After8SecDown (788), and go to step 732 where it will continue (See
Referring to
If Stability and Target values do not meet the two criteria set in step 792, the In2Sec timer is reset (802), the status is changed back to either TargetOutUp or TargetOutDown in step 804, and the microcontroller goes to step 770 (
In Mode 2 (algorithm 1000), the photoresistor inside the water stream also uses the above variables, but takes an additional factor into consideration: running water can also reflect light, so that the sensor may not be able to completely verify the user having left the faucet. In this case, the algorithm also uses a timer to turn the water off, while then actively checking whether the user is still there. Modes 1 or 2 may be selectable, for example, by a dipswitch.
Referring to
Referring to
If SL is smaller than 25% of the previously established BLTH, this would mean that the light in the room has suddenly dramatically increased (direct sunlight, for example). The scan counter starts counting to see if this change is stable (928) as the microcontroller cycles through steps 924, 925, 926, 928 and 929, until it reaches five cycles (929). Once it does reach the five cycles under the same conditions, it will establish a new BLTH in step 930 for the now brightly lit room, and begin a cycle anew at step 922 using this new BLTH.
If, however, the SL is between 25% greater than or equal to, but no greater than 85% of the BLTH (at steps 926 and 927), light is not at an extreme range, but regular ambient light, and the microcontroller will set the scan counter to zero at step 932, measure SL once more to check for a user (934), and assess whether the SL is between greater than 20% BLTH or less than 25% BLTH (20% BLTH<SL<25% BLTH) at step 936. If not, this would mean that there is a user in front of the unit sensor, as the light is lower than regular ambient light, causing the microcontroller to move on to step 944, where it will turn the water on for the user. Once the water is on, the microcontroller will set the scan counter to zero (946), scan for the target every ⅛ of a second (948), and continue to check for a high SL, that is, for low light, in step 950 by checking whether the SL is less than 20% of the BLTH. When SL decreases to less than 20% of BLTH (950), meaning that the light detected increased, the microcontroller will move on to step 952, turning on a scan counter. The scan counter will cause the microcontroller to continue scanning every ⅛ of a second and checking that SL is still less than 20% of BLTH until over 5 cycles through 948, 950, 952 and 954 have passed (954), which would mean that there now has been an increase in light which has lasted for more than 5 of these cycles, and that the user is no longer present. At this point the microcontroller will turn the water off (956). Once the water is turned off, the whole cycle is repeated from the beginning.
Referring to
If the SL is between greater than or equal to 25% or less than 85% of the BLTH, the microcontroller will continue through step 1015, and setting the scan counter to zero. It will measure the SL at step 1016, and assess if it is greater than 20% BLTH, but smaller than 25% BLTH (20% BLTH<SL<25% BLTH), at step 1017. If it is not, meaning there is something blocking light to the sensor, the microcontroller will turn water on (1024); this also turns on a Water Off timer, or WOFF (1026). Then, the microcontroller will continue to scan for a target every ⅛ of a second (1028). The new SL is checked against the BLTH, and if the value of SL is not between less than 25% BLTH, but greater than 20% BLTH (20% BLTH<SL<25% BLTH), the microcontroller will loop back to step 1028 and continue to scan for the target while the water runs. If the SL is within this range (1030), the WOFF timer now starts to count (1032), looping back to the cycle at step 1028. The timer's function is simply to allow some time to pass between when the user is no longer detected and when the water is turned off, since, for example, the user could be moving the hands, or getting soap, and not be in the field of the sensor for some time. The time given (2 seconds) could be set differently depending upon the use of the unit. Once 2 seconds have gone by, the microcontroller will turn the water off at step 1036, and it will cycle back to 1002, where it will repeat the entire cycle.
However, if at step 1017 SL is greater than 20% BLTH, but smaller than 25% BLTH (20% BLTH<SL<25% BLTH), the scan counter will begin to count the number of times the microcontroller cycles through steps 1016, 1017, 1018 and 1020, until more than five cycles are reached. Then, it will go to step 1022, where a new BLTH will be established for the light in the room, and the microcontroller will cycle back to step 1002, where a new cycle through algorithm 1000 will occur, using the new BLTH value.
At step 1332, if a target is found, the algorithm starts a target timer (1334). If the target timer counts for less than 8 seconds, the algorithm returns to step 1330, and continues scanning for a target. If the target's timer counts for longer than 8 seconds, the algorithm performs another scan for a target in step 1338. In step 1340, if the target is lost, the algorithm checks for the value of the time counted by the idle timer minus the target timer (1356). If the difference between the times counted by the two timers is less than 15 seconds, the algorithm activates the valve on every third target detected, providing a water amount equivalent to a half flush (1348). After providing a half flush (1348), the algorithm resets the idle timer (1370), resets the target timer (1372), and starts the idle timer once more to begin the cycle anew at step 1322.
If the difference between the times counted by the idle timer and the target timer is greater than 15 but less than 30 seconds (1358), the flusher executes a half-flush after one second at step 1360. It will then restart the algorithm, resetting the idle and target timers (1370 and 1372), and starting the idle timer (1322).
If the difference in times counted by the idle timer and the target timer is also greater than 30 seconds (1358), then the algorithm executes a full flush after one second (1365). After flushing the toilet or urinal, the idle timer and target timers are reset (1370 and 1372), and the system restarts the idle timer in step 1322. At this time, the entire Mode A is repeated.
If a target is not found at step 1332, the algorithm executes a detect blackout routine (1350), where light in the bathroom is measured. If there is light in the bathroom, i.e., there is no “blackout,” the algorithm continues scanning for a target at step 1330. If there is a blackout (1352), the algorithm enters the blackout mode (1354), in which the flusher enters a “sleep mode” to save battery power. This subroutine detects no use, for example, at night or on weekends.
If the sentinel timer counts for less than 24 hours before the toilet is flushed, a target timer is started (1406) and the system scans for a target at step 1408. If a target is found, the target timer is started (1412). When the target timer does not count for longer than 8 seconds at step 1414, if the target is lost (1416), the flush valve will be activated at step 1435, and the target timer will be reset (1440), so the algorithm can begin anew. If the target is not lost at step 1416, a new target scan will take place at step 1418.
If a sentinel flag is not set at step 1402, a dry-trap timer is started at step 1424. If at step 1426 this timer has counted for less than 12 hours before the urinal is flushed, the algorithm will next resume at step 1406, where the target timer will begin to count. However, if the dry-trap timer has counted for longer than 12 hours without the urinal being flushed, the timer is reset (1428), the flush valve is activated (1435), and the target timer is reset (1440), so the algorithm can begin once more.
If a target is not found at step 1410, the algorithm executes a detect blackout routine (1442). If there is no blackout, the algorithm continues to step 1408, to scan for a target. If a blackout is detected, the algorithm enters the blackout mode (1446).
The last two modes, the men's and women's closet modes, illustrated in FIGS. 14C1-14DII, have patterns that also use both stability and light changes to detect whether a user has been in the facility. Both modes have an intermittent target detection feature and a target out timer, with which a lost target is checked for instability in detection before being discarded as invalid. In this case, the stability and length of time of the light change also determine the type of flush that follows use.
However, if after intermittent target detection the target is still not found at step 1483, the microcontroller checks whether the target-out timer has counted for greater than 5 seconds. It will check for a target (i.e., cycle from step 1486 through 1483) until the target-out timer counts for longer than 5 seconds. At this point the algorithm begins anew, because if a target was detected for less than three seconds, and then lost for over 5, it is highly likely that what was detected was not a user.
If the target timer counted for over three seconds in step 1469, the microcontroller checks whether the target timer has counted for longer than 8 seconds (1470) while the target was lost. If so, it will check whether the period of time counted by the target timer was less than 90 seconds: that is, how long the user was in the facility. If use was for longer than 90 seconds, it will cause a full flush to occur (1490). If the timer counted for less than 90 seconds, it will activate the flush valve and cause a half flush (1474). Once either flush has occurred, the target timer will be reset at step 1475, and the algorithm will begin once more.
If the sentinel timer counts for longer than 24 hours before flushing occurs (1456), it is reset at step 1458, and a full flush is initiated at step 1490. The target timer is reset at step 1475, and the cycle begins once more.
If the sentinel flag is not set at step 1452, the dry-trap timer will start (1459), and if it counts for a short period of time before detecting use, it will begin to scan for a target at step 1462. However, once the timer counts for over one month (1460), it will be reset at step 1488, the flush valve will be activated, causing a full flush (1490), and the target timer will be reset at step 1475. At that point the algorithm will start once more.
If no target is found at step 1463, the microcontroller will check for a blackout (1476 and 1478). If none is detected at step 1478 it will go back to scanning for a target (1462). However, if one is detected, the algorithm will go to blackout mode (1480).
If the target timer has counted for longer than three seconds at step 1530, it will move on to step 1532, where it will determine if it has counted for greater than 8 seconds. If it has yet to count for more than 8 seconds, the algorithm will go back to step 1518 and scan. However, once the target timer has counted for longer than 8 seconds, the microcontroller will go to step 1534, to determine if any time has passed since it activated the target-out timer at step 1525. If the target-out timer has counted at all, the flush preparation timer will start (1536). The algorithm will cause the preparation timer to count for over 30 seconds (1538 and 1540), at which point the microcontroller will determine whether the target timer has counted for less than 120 seconds (i.e., a user has been in the unit for less than two minutes). If so, the flush valve will be activated, and a half flush will occur (1546), after which the target timer and preparation timers will be reset (1548 and 1550), and the algorithm will begin once more.
However, if the target timer has counted for longer than 120 seconds (i.e., a user has been detected for longer than 2 minutes) while the preparation timer was counting, the flush valve will be activated, and a full flush will occur at step 1544, after which the target and preparation timers will be reset in steps 1548 and 1550, and the algorithm will begin anew.
If the sentinel flag is not set at step 1502, the dry-trap timer will start (1503). If the dry-trap timer counts for a short period of time (1510), if will begin to scan for a target at step 1512. However, once the timer counts for over one month (1510), it will be reset at step 1507 or 1508; the flush valve will be activated, causing a full flush (step 1544); and the target and preparation timers will be reset at steps 1548 and 1550, so that the algorithm can start once more.
If no target is found at step 1514, the microcontroller will check for a blackout (1572 and 1574). If none is detected at step 1574 it will go back to scanning for a target (1512). However, if a blackout is detected, the algorithm will go to blackout mode (1576).
Having described various embodiments and implementations of the present invention, it should be apparent to those skilled in the relevant art that the foregoing is illustrative only and not limiting, having been presented by way of example only. There are other embodiments or elements suitable for the above-described embodiments, described in the above-listed publications, all of which are incorporated by reference as if fully reproduced herein. The functions of any one element may be carried out in various ways in alternative embodiments. Also, the functions of several elements may, in alternative embodiments, be carried out by fewer, or a single, element.
This application is a divisional of U.S. application Ser. No. 11/446,506, filed on Jun. 2, 2006, now U.S. Pat. No. 7,921,480, which is a continuation of PCT Appl. PCT/US04/040887, filed on Dec. 6, 2004, which is a continuation-in-part of PCT Appl. PCT/US03/38730, entitled “Passive Sensors for Automatic Faucets and Bathroom Flushers,” filed on Dec. 4, 2003; and which is a continuation-in-part of PCT Appl. PCT/US03/41303, entitled “Optical Sensors and Algorithms for Controlling Bathroom Flushers and Faucets,” filed on Dec. 26, 2003. The PCT/US04/040887 is also a continuation-in-part of U.S. application Ser. No. 10/860,938, entitled “Electronic Faucets for Long Term Operation,” filed on Jun. 3, 2004, which is a continuation of PCT Application PCT/US02/38757, entitled “Electronic Faucets for Long Term Operation,” filed on Dec. 4, 2002, and which is a continuation-in-part of U.S. application Ser. No. 10/859,750, entitled “Automatic Bathroom Flushers” filed on Jun. 3, 2004, which is a continuation of PCT Application PCT/US02/38758, entitled “Automatic Bathroom Flushers” filed on Dec. 4, 2002; wherein all of the above-mentioned applications are incorporated by reference. The U.S. application Ser. No. 11/446,506 is also a continuation-in-part of U.S. application Ser. No. 11/098,574, filed on Apr. 4, 2005, which is a continuation of U.S. application Ser. No. 10/440,997, filed on May 19, 2003, now U.S. Pat. No. 6,874,535, which is a continuation PCT Application PCT/US01/43277, filed on Nov. 20, 2001. The present invention is directed to novel optical sensors. The present invention is, more specifically, directed to novel optical sensors for controlling operation of automatic faucets and bathroom flushers, and in particular, to novel flow control sensors for providing control signals to electronics used in such faucets and flushers.
| Number | Name | Date | Kind |
|---|---|---|---|
| 207482 | Blessing | Aug 1878 | A |
| 1501331 | Gulick | Jul 1924 | A |
| 1518942 | Spear | Dec 1924 | A |
| 2471328 | Jones | May 1949 | A |
| 2619122 | Hunter | Nov 1952 | A |
| 2619986 | Goepfrich et al. | Dec 1952 | A |
| 2685301 | Dreier | Aug 1954 | A |
| 2827073 | Owens | Mar 1958 | A |
| 2842400 | Booth et al. | Jul 1958 | A |
| 2877791 | Rich | Mar 1959 | A |
| 2923314 | Badger, Jr. et al. | Feb 1960 | A |
| 2986155 | Doyle | May 1961 | A |
| 2999191 | Muradian et al. | Sep 1961 | A |
| 3019453 | Radcliffe | Feb 1962 | A |
| 3034151 | Filliung | May 1962 | A |
| 3056143 | Foster | Oct 1962 | A |
| 3058485 | McQueen | Oct 1962 | A |
| 3098635 | Delaporte et al. | Jul 1963 | A |
| 3166291 | Specht | Jan 1965 | A |
| 3242940 | Sirotek | Mar 1966 | A |
| 3254664 | Delaney et al. | Jun 1966 | A |
| 3285261 | Chaney | Nov 1966 | A |
| 3318565 | Cutler | May 1967 | A |
| 3369205 | Hamrick | Feb 1968 | A |
| 3373449 | Rusnok | Mar 1968 | A |
| 3386462 | Walters | Jun 1968 | A |
| 3400731 | McCormack | Sep 1968 | A |
| 3495803 | Schoepe et al. | Feb 1970 | A |
| 3495804 | Muller et al. | Feb 1970 | A |
| 3559675 | Schoepe et al. | Feb 1971 | A |
| 3586017 | Walters | Jun 1971 | A |
| 3606241 | Bornholdt | Sep 1971 | A |
| 3693649 | Gordon et al. | Sep 1972 | A |
| 3740019 | Kessell et al. | Jun 1973 | A |
| 3763881 | Jones | Oct 1973 | A |
| 3778023 | Billeter | Dec 1973 | A |
| 3791619 | Perr | Feb 1974 | A |
| 3802462 | Trösch | Apr 1974 | A |
| 3812398 | Kozel et al. | May 1974 | A |
| 3821967 | Sturman | Jul 1974 | A |
| 3842857 | McCornack | Oct 1974 | A |
| 3864567 | Bez | Feb 1975 | A |
| 3895645 | Johnson | Jul 1975 | A |
| 4010769 | De Lorenzo et al. | Mar 1977 | A |
| 4011553 | Barri | Mar 1977 | A |
| 4065095 | Johnson | Dec 1977 | A |
| 4097786 | Lund | Jun 1978 | A |
| 4105186 | Eby | Aug 1978 | A |
| 4114647 | Sturman et al. | Sep 1978 | A |
| 4135696 | Saarem et al. | Jan 1979 | A |
| 4141091 | Pulvari | Feb 1979 | A |
| 4206901 | Williams | Jun 1980 | A |
| 4231287 | Smiley | Nov 1980 | A |
| 4257437 | Pearson | Mar 1981 | A |
| 4272052 | Gidner | Jun 1981 | A |
| 4280680 | Payne | Jul 1981 | A |
| 4295485 | Waterfield | Oct 1981 | A |
| 4295631 | Allen | Oct 1981 | A |
| 4295653 | Coles | Oct 1981 | A |
| 4304391 | Yamaguchi | Dec 1981 | A |
| 4309781 | Lissau | Jan 1982 | A |
| 4383234 | Yatsushiro et al. | May 1983 | A |
| 4505451 | Jonas | Mar 1985 | A |
| 4570272 | Kawaguchi et al. | Feb 1986 | A |
| 4604735 | Parsons | Aug 1986 | A |
| 4609178 | Baumann | Sep 1986 | A |
| 4611356 | Lin | Sep 1986 | A |
| 4671485 | Saarem | Jun 1987 | A |
| 4672206 | Suzuki et al. | Jun 1987 | A |
| 4681141 | Wang | Jul 1987 | A |
| 4709427 | Laverty, Jr. | Dec 1987 | A |
| 4729342 | Loctin | Mar 1988 | A |
| 4756031 | Barrett | Jul 1988 | A |
| 4767922 | Stauffer | Aug 1988 | A |
| 4775949 | Kalata | Oct 1988 | A |
| 4787411 | Moldenhauer | Nov 1988 | A |
| 4793588 | Laverty, Jr. | Dec 1988 | A |
| 4795908 | Morimoto et al. | Jan 1989 | A |
| 4796658 | Caple | Jan 1989 | A |
| 4796662 | Hoffmann et al. | Jan 1989 | A |
| 4805247 | Laverty, Jr. | Feb 1989 | A |
| 4823414 | Piersimoni et al. | Apr 1989 | A |
| 4823825 | Buchl | Apr 1989 | A |
| 4826129 | Fong et al. | May 1989 | A |
| 4826132 | Moldenhauer | May 1989 | A |
| 4832263 | Poynor | May 1989 | A |
| 4832582 | Buffet | May 1989 | A |
| 4839039 | Parsons et al. | Jun 1989 | A |
| 4887032 | Hetrick | Dec 1989 | A |
| 4891864 | Laverty, Jr. | Jan 1990 | A |
| 4893645 | Augustinas et al. | Jan 1990 | A |
| 4894698 | Hijikigawa et al. | Jan 1990 | A |
| 4894874 | Wilson | Jan 1990 | A |
| 4910487 | Kleinhappl | Mar 1990 | A |
| 4911401 | Holcomb et al. | Mar 1990 | A |
| 4921208 | LaMarca | May 1990 | A |
| 4921211 | Novak et al. | May 1990 | A |
| 4932430 | Fernstrom | Jun 1990 | A |
| 4941215 | Liu | Jul 1990 | A |
| 4941219 | Van Marcke | Jul 1990 | A |
| 4944487 | Holtermann | Jul 1990 | A |
| 4977929 | Chinnock et al. | Dec 1990 | A |
| 4988074 | Najmolhoda | Jan 1991 | A |
| 4989277 | Tsutsui et al. | Feb 1991 | A |
| 4998673 | Pilolla | Mar 1991 | A |
| 5025516 | Wilson | Jun 1991 | A |
| 5027850 | Peterson et al. | Jul 1991 | A |
| 5032812 | Banick et al. | Jul 1991 | A |
| 5036553 | Sanderson | Aug 1991 | A |
| 5074520 | Lee et al. | Dec 1991 | A |
| 5086526 | Van Marcke | Feb 1992 | A |
| 5101639 | Wruck | Apr 1992 | A |
| 5109885 | Tauscher | May 1992 | A |
| 5115391 | Puthenpura et al. | May 1992 | A |
| 5125621 | Parsons et al. | Jun 1992 | A |
| 5127625 | Kleinhappl | Jul 1992 | A |
| 5133987 | Spence et al. | Jul 1992 | A |
| 5169118 | Whiteside | Dec 1992 | A |
| 5188337 | Mertens et al. | Feb 1993 | A |
| 5195720 | Nortier et al. | Mar 1993 | A |
| 5213303 | Walker | May 1993 | A |
| 5213305 | Whiteside et al. | May 1993 | A |
| 5224685 | Chiang et al. | Jul 1993 | A |
| 5232194 | Saadi et al. | Aug 1993 | A |
| 5244179 | Wilson | Sep 1993 | A |
| 5245024 | Scarpa et al. | Sep 1993 | A |
| 5251188 | Parsons et al. | Oct 1993 | A |
| 5265594 | Olsson et al. | Nov 1993 | A |
| 5265843 | Kleinhappl | Nov 1993 | A |
| 5281808 | Kunkel | Jan 1994 | A |
| 5293652 | Furr | Mar 1994 | A |
| 5295655 | Wilson et al. | Mar 1994 | A |
| 5313673 | Saadi et al. | May 1994 | A |
| 5315719 | Tsutsui et al. | May 1994 | A |
| 5335694 | Whiteside | Aug 1994 | A |
| 5375811 | Reinicke | Dec 1994 | A |
| D354113 | Nortier et al. | Jan 1995 | S |
| D355478 | Allen et al. | Feb 1995 | S |
| 5408369 | Miura et al. | Apr 1995 | A |
| D357976 | Allen et al. | May 1995 | S |
| 5412816 | Paterson et al. | May 1995 | A |
| 5431008 | Ross et al. | Jul 1995 | A |
| 5431181 | Saadi et al. | Jul 1995 | A |
| 5433245 | Prather et al. | Jul 1995 | A |
| 5456279 | Parsons et al. | Oct 1995 | A |
| 5474303 | Coles | Dec 1995 | A |
| 5481187 | Marcott et al. | Jan 1996 | A |
| 5508510 | Laverty et al. | Apr 1996 | A |
| 5539198 | McMichael et al. | Jul 1996 | A |
| 5548119 | Nortier | Aug 1996 | A |
| 5555912 | Saadi et al. | Sep 1996 | A |
| 5566702 | Philipp | Oct 1996 | A |
| 5574617 | Shimanuki et al. | Nov 1996 | A |
| 5583434 | Moyers et al. | Dec 1996 | A |
| 5584465 | Ochsenreiter | Dec 1996 | A |
| 5586746 | Humpert et al. | Dec 1996 | A |
| 5600237 | Nippert | Feb 1997 | A |
| 5603127 | Veal | Feb 1997 | A |
| 5636601 | Moriya et al. | Jun 1997 | A |
| 5647388 | Butler | Jul 1997 | A |
| 5651384 | Rudrich | Jul 1997 | A |
| 5668366 | Mauerhofer | Sep 1997 | A |
| 5680879 | Sheih et al. | Oct 1997 | A |
| 5708355 | Schrey | Jan 1998 | A |
| 5709245 | Miller | Jan 1998 | A |
| 5716038 | Scarffe | Feb 1998 | A |
| 5730165 | Philipp | Mar 1998 | A |
| D393898 | Gottwald | Apr 1998 | S |
| 5747684 | Pace et al. | May 1998 | A |
| 5749521 | Lattery | May 1998 | A |
| D396090 | Marcichow et al. | Jul 1998 | S |
| 5780854 | Lin | Jul 1998 | A |
| 5785955 | Fischer | Jul 1998 | A |
| 5787915 | Byers et al. | Aug 1998 | A |
| 5787924 | Cewers et al. | Aug 1998 | A |
| 5797360 | Pischinger et al. | Aug 1998 | A |
| 5804962 | Kather et al. | Sep 1998 | A |
| 5815362 | Kahr et al. | Sep 1998 | A |
| 5819336 | Gilliam et al. | Oct 1998 | A |
| 5829467 | Spicher | Nov 1998 | A |
| 5855356 | Fait | Jan 1999 | A |
| 5881993 | Wilson et al. | Mar 1999 | A |
| 5887848 | Wilson | Mar 1999 | A |
| 5889204 | Scherer et al. | Mar 1999 | A |
| 5900201 | Chatterjee et al. | May 1999 | A |
| 5901384 | Sim | May 1999 | A |
| 5905625 | Schebitz | May 1999 | A |
| D411609 | Stoltenberg et al. | Jun 1999 | S |
| 5915417 | Diaz et al. | Jun 1999 | A |
| 5918855 | Hamanaka et al. | Jul 1999 | A |
| 5927603 | McNabb | Jul 1999 | A |
| 5941505 | Nagel | Aug 1999 | A |
| 5943712 | Van Marcke | Aug 1999 | A |
| 5950983 | Jahrling | Sep 1999 | A |
| 5961095 | Schrott | Oct 1999 | A |
| 5964192 | Ishii | Oct 1999 | A |
| 5966076 | Cantrell | Oct 1999 | A |
| 5967182 | Wilson | Oct 1999 | A |
| 5979500 | Jahrling et al. | Nov 1999 | A |
| 5984262 | Parsons et al. | Nov 1999 | A |
| 5996965 | Eichholz et al. | Dec 1999 | A |
| 6000674 | Cheng | Dec 1999 | A |
| 6003170 | Humpert et al. | Dec 1999 | A |
| 6019343 | Tsai | Feb 2000 | A |
| 6024059 | Kamimaru et al. | Feb 2000 | A |
| 6044814 | Fuwa | Apr 2000 | A |
| 6056261 | Aparicio et al. | May 2000 | A |
| 6065735 | Clark | May 2000 | A |
| 6073904 | Diller et al. | Jun 2000 | A |
| 6082407 | Paterson et al. | Jul 2000 | A |
| 6118521 | Jung | Sep 2000 | A |
| 6127671 | Parsons et al. | Oct 2000 | A |
| 6155231 | Adachi et al. | Dec 2000 | A |
| 6158715 | Kirschbaum | Dec 2000 | A |
| 6161726 | Parsons et al. | Dec 2000 | A |
| 6182689 | Lauer et al. | Feb 2001 | B1 |
| 6202980 | Vincent | Mar 2001 | B1 |
| 6212697 | Parsons et al. | Apr 2001 | B1 |
| 6216730 | Hall | Apr 2001 | B1 |
| 6227219 | Pino | May 2001 | B1 |
| 6239423 | Hama et al. | May 2001 | B1 |
| 6243885 | Lopez-Torres, Jr. | Jun 2001 | B1 |
| 6250601 | Kolar et al. | Jun 2001 | B1 |
| 6260576 | Allen | Jul 2001 | B1 |
| 6273394 | Vincent et al. | Aug 2001 | B1 |
| 6293516 | Parsons et al. | Sep 2001 | B1 |
| 6299127 | Wilson | Oct 2001 | B1 |
| 6305602 | Grabowski et al. | Oct 2001 | B1 |
| 6305662 | Parsons et al. | Oct 2001 | B1 |
| D452898 | Johnson | Jan 2002 | S |
| 6340032 | Zosimadis | Jan 2002 | B1 |
| 6353942 | Pondelick et al. | Mar 2002 | B1 |
| 6367096 | Quintana | Apr 2002 | B1 |
| 6382586 | Wilson et al. | May 2002 | B1 |
| 6450478 | Parsons et al. | Sep 2002 | B2 |
| 6499152 | Johnson | Dec 2002 | B2 |
| 6560790 | Saar et al. | May 2003 | B2 |
| 6609698 | Parsons et al. | Aug 2003 | B1 |
| 6619614 | Parsons et al. | Sep 2003 | B2 |
| D480450 | Saadi et al. | Oct 2003 | S |
| 6639517 | Chapman et al. | Oct 2003 | B1 |
| 6643853 | Wilson et al. | Nov 2003 | B2 |
| 6659420 | Hwang | Dec 2003 | B2 |
| 6685158 | Parsons | Feb 2004 | B2 |
| 6871835 | Parsons | Mar 2005 | B2 |
| 7069941 | Parsons et al. | Jul 2006 | B2 |
| D531696 | Lopez | Nov 2006 | S |
| 7188822 | Marcichow | Mar 2007 | B2 |
| 7325781 | Parsons | Feb 2008 | B2 |
| D569947 | Johnson | May 2008 | S |
| 7396000 | Parsons et al. | Jul 2008 | B2 |
| 7690623 | Parsons et al. | Apr 2010 | B2 |
| 7731154 | Parsons et al. | Jun 2010 | B2 |
| 7921480 | Parsons et al. | Apr 2011 | B2 |
| 8042202 | Parsons et al. | Oct 2011 | B2 |
| 8276878 | Parsons et al. | Oct 2012 | B2 |
| 20030058118 | Wilson | Mar 2003 | A1 |
| 20030122059 | Su | Jul 2003 | A1 |
| 20050076425 | Contadini | Apr 2005 | A1 |
| Number | Date | Country |
|---|---|---|
| 29717352 | Feb 1998 | DE |
| 10054863 | May 2002 | DE |
| 0337367 | Oct 1989 | EP |
| 1314632 | Apr 1973 | GB |
| WO8505648 | Dec 1985 | WO |
| WO 03087641 | Oct 2003 | WO |
| Entry |
|---|
| International Search Report issued in PCT Application PCT/US 03/41303 dated May 4, 2004 (5 pages). |
| International Search Report issued in PCT Application PCT/US 03/38730 dated May 12, 2004 (6 pages). |
| International Search Report issued in PCT Application PCT/US 03/20117 dated Dec. 18, 2003. |
| International Preliminary Report on Patentability issued in PCT Application PCT/US 04/040887 dated Apr. 10, 2006 (11 pages). |
| International Search Report issued in PCT Application PCT/US 04/040887 dated May 25, 2005 (6 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20110302708 A1 | Dec 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11446506 | Jun 2006 | US |
| Child | 13066349 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US2004/040887 | Dec 2004 | US |
| Child | 11446506 | US | |
| Parent | PCT/US02/38757 | Dec 2002 | US |
| Child | 10860938 | US | |
| Parent | PCT/US02/38758 | Dec 2002 | US |
| Child | 10859750 | US | |
| Parent | 13066349 | US | |
| Child | 10859750 | US | |
| Parent | 10440997 | May 2003 | US |
| Child | 11098574 | US | |
| Parent | PCT/US01/43277 | Nov 2001 | US |
| Child | 10440997 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/US03/38730 | Dec 2003 | US |
| Child | PCT/US2004/040887 | US | |
| Parent | PCT/US03/41303 | Dec 2003 | US |
| Child | 11446506 | US | |
| Parent | 10860938 | Jun 2004 | US |
| Child | PCT/US2004/040887 | US | |
| Parent | 10859750 | Jun 2004 | US |
| Child | 11446506 | US | |
| Parent | 11098574 | Apr 2005 | US |
| Child | 13066349 | US |
