The present invention relates to communications systems and methods for automated irrigation systems, which provide central and local control of delivered amounts of water.
There are various sprinkler devices for watering gardens, yards, or for agricultural uses. These devices may have a controller installed at a source of pressurized water and a remotely located sprinkler. The sprinklers include a rotatable water guide with a water nozzle. When water is ejected from the nozzle, it flows initially through the water guide piece that rotates over a full circle or over a semicircular pattern. The spraying speed is frequently determined by the water flow speed. That is, the water speed governs the rotation of the water guide piece and thus the irrigation pattern.
Many irrigation controllers are time based. The water delivery is activated over a selected period of time regardless of the temperature, air humidity, soil moisture or other vegetation growth factors. Furthermore, the water delivery may vary with the water source pressure and other factors.
Therefore, there is still a need for reliable water delivery systems and control methods capable of delivering selected or known amounts of water. There is still also a need for automated water delivery systems and methods that enable a local loop feedback control and/or can detect local malfunctions.
The present invention relates to communication systems and methods for automated irrigation systems installed in-ground or above-ground. The automated irrigation systems control and meter the amounts of water delivered from one or several irrigation zones.
One type of the communication system is used for selectively controlling multiple zones and delivering a selectable water amount (or irrigating different amounts of water from the individual zones) according to the local irrigation needs. A multizone irrigation system includes a central control unit having a central controller interfaced with a central valve and a central communication unit. The central valve regulates water flow for irrigation from a water source. The central communication unit is constructed to transmit or receive communication signals providing irrigation information. Each zone includes a sprinkler control unit including a sprinkler connected to a water pipe for irrigation of a land area. The sprinkler control unit includes a local controller interfaced with a local valve for controlling water flow to the sprinkler. The sprinkler control unit also includes a local communication unit constructed to receive communication signals from the central communication unit and provide received irrigation information to the local controller. In a bi-directional system, one or several local communication units are constructed to transmit communication signals to the central communication unit which provide received information to the central controller. The central controller thus can store specific irrigation cycles including the water amounts delivered by each sprinkler or each zone. The local controller controls operation of the local valve based on the irrigation information received from the central controller and information provided by the individual local sensors.
According to one embodiment, a communication system used in an irrigation system includes a central controller interfaced with a central valve and a central communication unit, and a number of sprinkler units each unit including a local controller interfaced with a local valve for controlling water flow to a sprinkler, and a local communication unit. The central valve regulates water flow for irrigation from a water source. The central communication unit is constructed to transmit communication signals providing irrigation information. The sprinkler units are constructed to irrigate a land area. The local communication unit is constructed to receive communication signals from the central communication unit and provide received irrigation information to the local controller. The local controller is constructed to control operation of the local valve based on the irrigation information.
The central communication unit is constructed to receive the communication signals, and the local communication unit is constructed to transmit communication signals.
The central communication unit and the local communication unit are coupled to water conduits connected to the water source and are constructed to generate pressure waves transmitted through water in the conduits. The central communication unit and the local communication unit include a pressure sensor arranged to detect the pressure waves.
The central communication unit and the local communication unit are coupled to water conduits connected to the water source and are constructed to generate pressure pulses or ultrasound waves transmitted through water in the conduits.
Furthermore, the automated systems and methods enable water delivery based on a local loop feedback control and/or control of a delivered amount of water at different water pressures. These systems can be used for watering lawns, gardens, yards, golf courses, or for agricultural uses.
According to yet another embodiment, a remotely located irrigation system includes a controller connected to receive data from a sensor, and a valve device including an actuator. The system has a water input port constructed to be coupled to a water conduit receiving water from a remotely located water source. The controller is located near the water input port and provides control signals to the actuator. The actuator initiates the on and off states of the valve device located near, and connected to, the water input port for providing water to a water delivery device such as a sprinkler or a drip irrigation device.
According to yet another aspect, an irrigation system includes a water input port constructed receiving water from a remotely located water source, and a controller located near the water input port and connected to at least one sensor. The system also includes a valve device including an actuator located near and connected to the water input port, wherein the valve device is constructed to receive control signals from the controller for providing water to a sprinkler.
Preferred embodiments may include one or more of the following features: The controller may be battery operated. The actuator is a latching actuator (as described in U.S. Pat. No. 6,293,516, which is incorporated by reference), a non-latching actuator (as described in U.S. Pat. No. 6,305,662, which is incorporated by reference), or an isolated operator (as described in PCT Application PCT/US01/51098, which is incorporated by reference).
The sensor may be a precipitation sensor, humidity sensor, a soil moisture sensor, or a temperature sensor.
The remotely located irrigation system may include an indicator associated with the controller. The remotely located irrigation system may include a wireless communication unit connected to the controller for receiving data or sending data. The remotely located irrigation system may include manual data input associated with the controller.
The controller may be constructed to provide control signals to at least two actuators, each associated with one valve device and located near and connected to the water input port, wherein the valve device is constructed to receive control signals from the controller for providing water to a water delivery unit.
The controller may be constructed as a time based controller, or as a non-time based controller.
The irrigation system may be constructed to be removably located at a selected location. The irrigation system may be constructed to be mounted on a mobile irrigation platform. The mobile irrigation platform may be self-propelled.
The described irrigation systems use different types of communication systems for irrigation providing controlled amounts of water or providing metered amounts of water delivered from one or several irrigation zones. The irrigation systems are either above-ground or in-ground and use different control systems, valves and sensors, as described below.
A single zone irrigation system 10 or 40 includes a remotely located controller connected to receive data from at least one local sensor, and includes a valve device actuated by an actuator. The irrigation system has a water input port constructed to be coupled to a water conduit receiving water from a remotely located water source. The controller is located near the water input port and provides control signals to the actuator. The actuator initiates the on and off states of the valve device for providing water to a sprinkler or a drip irrigation device.
A multizone irrigation system 230A includes a central control unit having a central controller interfaced with a central communication unit. There may be a central valve that regulates water flow for irrigation from a water source. The central communication unit is constructed to transmit or receive communication signals providing irrigation information, as shown in Tables 1 and 2. Each zone includes an irrigation control unit (e.g., a sprinkler control unit) constructed to control irrigation from a sprinkler, a drip irrigation device, or similar. The sprinkler control unit includes a local controller interfaced with a local valve for controlling water flow to the sprinkler. The sprinkler control unit also includes a local communication unit constructed to receive communication signals from the central communication unit and provide received irrigation information to the local controller.
In a bi-directional communication system, one or several local communication units (associated with irrigation control units) are constructed to transmit communication signals to the central communication unit, which provides the received information to the central controller. The central controller thus can store specific irrigation cycles including the water amount delivered by each sprinkler or each zone. The local controller controls operation of the local valve based on the irrigation information received from the central controller and information provided by the individual local sensors.
Sprinkler 24 is controlled by a control system and an actuator, all described below in connection with
Water delivery unit 10 is an automated system controlled by a microprocessor that executes various modes of operation. Preferably, the entire water delivery unit 10 is battery operated. Water delivery unit 10 can provide a pre-programmed water delivery without measuring the “local conditions” or by measuring the “local conditions” using one or several sensors. The sensor date may be used to override a pre-selected algorithm (such as skip one watering course after detecting rain). Alternatively, water delivery unit 10 can provide water delivery based on a local loop feedback control by measuring local conditions such as precipitation, humidity, soil moisture, temperature and/or light and using the measured data to deliver a selected amount of water at varying water pressures.
Water delivery unit 10 includes a water pressure sensor (e.g., a sensor system described in connection with
The present systems and methods are also highly suitable for watering large areas such as parks, golf courses, or agricultural fields using water delivery unit 10, where the “local” conditions vary due to an uneven terrain (e.g., small hills with dry soil or valleys where water has accumulated), and due to different soil, or different vegetation. The present systems and methods are also highly suitable for fields or orchards where different agricultural products are grown. In each case, the local controller receives data from at least one sensor and calculates the desired water amount using stored algorithms. Based on the local water pressure, water delivery unit 10 delivers the calculated water amount over the irrigated area. The design of water delivery unit 10 is also highly suitable for using “gray water” pumped or delivered from canals or water reservoirs. The present design of valves and actuators (described in connection with
Mobile irrigation platform 40 also includes two rear wheels 50 and 52, both of which are independently propelled by water pressure from a water supply (not shown in
To achieve a straight-line motion with both valves to both wheels 50 and 52 open, irrigation platform 40 uses a proportional flow valve arrangement that provides a desired rate of the water supply to the propelled wheels. The proportional flow valve arrangement is placed at a location having equal distance to each wheel so as to insure equal rate of the wheel rotation. Furthermore, each wheel 50 or 52 is mounted onto frame 42 using a spring-loaded independent suspension arrangement (not shown in
Front wheel 54 is spinning free (i.e., is not self-propelling as wheels 50 and 52), but is equipped with two rotation encoders. The first rotation encoder determines the forward or reverse motion. The second rotation encoder is located inside an enclosure 55. The second rotation encoder determines the wheel's clockwise or counterclockwise rotation with respect to frame 42. That is, the second encoder measures the left or right side turns by monitoring the rotational axis of a fork 53, which secures wheel 54 to frame 42. Detailed description of the rotation encoders is provided in U.S. Provisional Application No. 60/337,112, filed on Dec. 4, 2001, entitled “Cart Management System,” published as US 2003/0102969, on Jun. 5, 2003, which is incorporated by reference.
Sprinklers 44 and 46 have their spray nozzles directed at a selected angle (for example, downward with a slight outward angle so as to obtain a spray coverage to the left, right, front and rear of the frame's outline). Each sprinkler 44 or 46 is controlled by the control system and the actuator described below. The control system controls the spray pattern and the water amount. The sprinklers may be located at a selected height or may even be telescopically elevated at actuation to provide a longer trajectory and to enable watering of areas that the platform cannot access. Each sprinkler 44 and 46 may include a solenoid controlled, proportional flow valve that enables turning on/off of each individual sprinkler (or sprayer) and enables control of the spray distance and trajectory.
Mobile irrigation platform 40 includes a water inlet port (not shown) connectable to a garden hose. The water inlet port enables 360° rotation with respect to the water supply hose with further means of insuring that the platform will not override the hose by virtue of a rotating right angle rigid arm, which will extend and retain the hose beyond the platform traversing path.
Control system 60 may be connected to other external controllers, sensors, or a central operation unit using standard wires. Alternatively, control system 60 may communicate with other external units using a device described in U.S. patent application Ser. No. 09/596,251, filed on Jun. 16, 2000, and PCT Application PCT/US01/40913, entitled “Method and Apparatus for Combined Conduit/Electrical Conductor Junction Installation,” which is incorporated by reference.
Alternatively, control system 60 uses a wireless communication unit 76 for sending data to or receiving data from a central communication unit, for downloading software or input data into the memory of controller 62, or for receiving remote sensor data. Controller 62 may also include one or several displays and a manual data input 74. Depending on a control algorithm and the data received from one or several sensors 64 through 72, controller 62 provides ON and OFF signals to valve actuator 80, which opens or closes water delivery. Preferably, valve actuator 80 actuates a valve device 250 described in connection with
Referring to
The entire control and indicator system is packaged in a robust, outdoor sealed container capable of withstanding humid and hot or cold environment and also capable of withstanding mechanical shocks due to rough handling. For example, the photo-sensor is located behind a clear window, and the temperature sensor is located inside a temperature conductive conduit protecting the temperature sensor and providing good thermal coupling. Rain sensor 64 includes opening 32 covered by a removable screen and wire mesh, as described below in connection with
Still referring to
The rain sensor detects the amount of natural precipitation and provides the corresponding signal to the microcontroller. The microcontroller may delay a watering cycle based on the amount of precipitation. The late watering cycle is displayed to a user by rain delay indicator 122. Rain delay indicator 122 includes a single color visible LED, or another indicating element. A user can manually select the vegetation type using vegetation type selector 112. The selected type of vegetation is then indicated by one of four single color visible LEDs. (Alternatively, a single multi-color or two dual color light indicators may be used.)
For example, in the embodiment where controls 30 are constructed and arranged as a hose-end controller (as shown in
The ground moisture sensor is filled with liquid through liquid refill port 158. Float 164 is located near or at the liquid surface, depending on its construction. Due to the hygroscopic force (F) directed from inside of rigid containment chamber 152 toward soil 149, water migrates from inside of chamber 154. As the liquid seeps out through semi-permeable membrane 154, water level drops, which changes the location (the relative height) of float 164. Reed sensor 162 detects location of magnets 166 or 168 and provides a signal to the microcontroller regarding the water level inside rigid containment chamber 152. Based on this electrical signal the ground moisture content is determined using a calibration curve. Thus the microcontroller receives information about the ground moisture from the ground moisture sensor 150 or 150A. There may be several ground moisture sensors located around the water territory and these may be hardwired to the microcontroller or may provide information using RF or other wireless coupling.
Another embodiment of soil moisture sensor 64 includes two electrodes located on a stake and insertable in the ground. The two electrodes are separated by a predetermined distance. The resistance or ion migration between the two electrodes varies depending on the ground moisture. The electrodes may be made of metals providing a different potential and thus causing migration of ions there between. A measurement circuit connected to the two electrodes measures the corresponding potential. Alternatively, the two electrodes may be made of an identical, non-corrosive metal (e.g., stainless steel 300 series) connected to an electrical circuit. The electrical circuit provides a two-point or a four-point measurement of electrical conductivity between the electrodes, which conductivity corresponds to the soil moisture. The measured conductivity data is provided to a microcontroller 62, which then determines the moisture content of the soil and determines the irrigation cycle according to a selected algorithm. Alternatively, at least one of the electrodes may include conductive and isolating regions located at different depths in the ground. Based on the conductivity value measured at different levels, the moisture sensor measures the moisture profile at different depths in the ground. Again, microcontroller 62 uses the depth moisture profile for calculating an appropriate irrigation cycle.
Alternatively, the ground moisture sensor may be a capacitive sensor having a porous dielectric. The dielectric material is in contact with the ground and water migrates between the capacitive plates by the capillary effect from the ground. Depending on the ground moisture, the dielectric constant of the capacitor varies. Thus, the capacitance value corresponds to measured moisture content of the ground.
According to another embodiment, the ground moisture sensor (i.e., the soil moisture sensor) includes a gypsum board coated with a water pearmeable film and two electrodes located inside the gypsum board and separated by a predetermined distance. The moisture sensor measures the resistance between the two electrodes, which corresponds to the ground moisture migrating into the gypsum material.
Referring to
The present design may be used with various embodiments of in ground pop-up (riser) sprinklers described in U.S. Pat. Nos. 4,781,327; 4,913,351; 5,611,488; 6,050,502; 5,711,486; and US Patent Publications 2001/0032890; 2002/0092924; 2002/0153432, all of which are incorporated by reference
Each valve 250 and the associated sprinkler 236 may include one control system 60 (which in this embodiment is a local control system) located inside enclosure 238 and communicating with a central control or interface system via antenna 246. Local control system 60 (shown in
In general, a multizone irrigation system (e.g., irrigation system 230A shown in
According to another embodiment, the communication system is a wireless communication system, wherein the central communication unit includes an RF transmitter and the local communication units include an RF receiver. Alternatively, both the central communication unit and the local communication units each include an RF transceiver. The wireless communication system uses the rising antenna described above.
According to another embodiment, the communication system is a hard-wired communication system, wherein the communication wire is located along the water pipes. This embodiment is described U.S. patent application Ser. No. 09/596,251, now U.S. Pat. No. 6,748,968, and PCT Application PCT/US01/40913, entitled “Method and Apparatus for Combined Conduit/Electrical Conductor Junction Installation,” both of which are incorporated by reference.
According to yet another embodiment, the communication system uses water medium in the irrigation pipes for transmitting communication messages. The messages between the central communication unit and the local communication units are transmitted using pressure waves. The communication system utilizes ultrasound waves generated by a piezoelectric elements commonly used in ultrasound systems. The central communication unit and each local communication unit include ultrasound transducers (or transducer arrays) for emitting and detecting ultrasound waves. The ultrasound transducer design, spacing and location are arranged to optimal transmission in water pipes depending on the pipe layout.
According to yet another embodiments, the communication system utilizes an acoustic/vibratory driver (electro magnetic or magnostrictive) at the central control unit. The acoustic/vibratory driver is coupled to the waterline and each local control system includes an acoustic/vibratory receiver. The acoustic/vibratory driver generates waves in the water column within the irrigation pipes and/or the piping walls. The waves carry coded information transmitted from the central controller to the local controller. For bi-directional communication, each local control system includes a driver next to the zone valve.
According to yet another embodiments, the communication system utilizes oscillating pressure waves propagating in the water conduits, which waves vary in rate, pulse width, and possibly in pulse magnitude. The pressure oscillations are attained by an oscillating pump, a two-way solenoid or another means residing at central controller unit 300. The pressure waves are detected by pressure sensors 239 (or pressure switches) associated with the sprinkler control units.
According to yet another embodiments, the communication system utilizes pressure waves generated by opening and closing a valve and propagating in the water conduits. This communication system is described in detail in connection with
All N sprinkler control units 231N include similar element elements though variation in the units is possible depending on the irrigation needs. The sprinkler control units have a modular design enabling field modification of the unit. That is, a technician installing or servicing the units can add or remove various sensors. For example, some local control systems 235 may include no soil or no humidity sensors, or other may include no sensors at all, but all include a central controller (i.e., a processor, memory and communication interface). According to one preferred embodiment, each sprinkler control unit 231 includes a self-contained power supply unit for recharging the batteries. The power supply unit includes a solar element utilizing the photovoltaic effect to provide power to the batteries. Alternatively, the power supply unit includes a miniature water turbine utilizing the water flow energy for generating and providing electrical power to the batteries.
Central control system 60 communicates with the sprinkler units 2311-231N, utilizing changes in the water pressure as the signaling means. Central valve 302 is constructed to allow water to exit water pipe 232 via a port 301 and thus lower water pressure in pipes 234. Sprinkler units 231 include local controllers 235 that control valves 250 for sprinkling or for sending pressure signals by opening and closing and thus lowering and restoring water pressure in pipes 234. Pressure sensors 239 detect the changes in water pressure that constitute the communication signals and provide the corresponding electrical signal to local control systems 235.
Generally, each pressure sensor (transducer) 239 is made from high-strength, watertight, non-corrosive material such as stainless steel. The input pressure range is, for example, between 0-414 kPa (or 0-60 psi). The electrical output signal, between 4-20 mA, is then sent to the controller, which interprets the signal and uses it to determine the next action in the irrigation system, including determining amount of watering, and sending back signals by changing the water pressure. The pressure gauge should have good repeatability, and be able to reproduce an identical signal each time the same pressure is applied to it under the same conditions. It should also have a short response time, or length of time required for an output signal to be produced when the pressure is sensed.
The programmable controller of each sprinkler unit 231 has interfaces for receiving signals from pressure sensor 239, and for opening and closing sprinkler valves 250 for pressure signaling (i.e., data communication) and sprinkling. Each local controller can be programmed to both receive input from the pressure gauge (corresponding to communication signals from central control unit 300) and to send signals to central control unit 300, at particular time slots. The schedule for signals receiving and transmitting of communication at particular times is selected and designated for each sprinkler unit 231 to avoid crosstalk or communication errors.
The communication system uses a stipulated code of pressure changes, sending and decoding messages conveyed by each coded signal. Central control system 60 transmits messages to the sprinkler units utilizing pressure changes to convey amounts of irrigation based on the variables measured by the central system's sensors and/or preset values entered by a user using the system's controls. For example, central control system provides a set length of watering time one morning as based on rain the night before, and given the vegetation the sprinklers were set to water, etc. Each sprinkler unit also detects variables such as the wetness of the soil at the sprinkler's location. Based on these measurements, each sprinkler varies the amount of watering further refining the sensitivity of the system. If one sprinkler unit senses a higher amount of soil moisture than the general system, it could water 20% more than the instruction from the control system. If a sprinkler measures precipitation due to someone having watered the specific location with a hose, without having watered the entire property irrigated by the in ground watering system, the sprinkler unit's controller can also then reduce the amount it waters by a specific percentage. The magnitude of these changes is preset for each measurement involved.
Referring still to
Referring to Tables 1 and 2, each communication starts with a header (“LSLS”), so that any random change in water pressure is not read as a message by the pressure sensor. Each message transmission also ends with a footer, so that the system could ascertain end of transmission. In this example, a 5 sec. lowering of pressure (i.e., “LLLLL”), where the valve is open, allowing for water to exit the system, functions as a footer. (However, the unit interval may be shorter than 1 sec. And depends on the pressure recovery from “low” pressure to “standard” pressure.) Pressure detector 239n detects changes in the water pressure and controller 235n “translates” the messages, and determines what messages to transmit. Controller 235n directs opening and closing of valve 250, therefore lowering or raising the water pressure and sending the communication signal. The communication message may include the following header, first coded term, spacer, second coded term, and footer (i.e., end of transmission string): LSLS/LSL/SSSSS/LSSL/LLLLL.
The code for each part of the message is selected depending on the amount of information being communicated, and how it is being communicated. For example, if only one type of information is being transmitted, the code can be simpler, and the spacer may not be necessary. If more information is being communicated, the code can be more complex, having more changes in pressure for each term. The same terms can also have more than one meaning depending on their location in the entire message. The controller and control unit can be made to distinguish each meaning as dependent upon the location of the term within the message.
Each sprinkler unit 231 may transmit a signal back to central control unit 300 at a predetermined time to prevent cross-talk, as shown in Tables 1 and 2. Local control system 2351 can transmit a signal including the header, the code for the amount the watering varied from the amount required by control system 60 (“0-20% less”), the spacer between the two signals, and the code giving the reason for the length of the watering period (“humidity level”). Then control system 60 transmits a message of its own to the sprinkler at the predetermined time. The reply message may include the header, and the code meaning “message received.” Controller 2351 receives the signal via readings from pressure detector 239n, and does not attempt to send the signal once more.
This pattern continues for each sprinkler unit. In the example shown, other sprinklers in the system have watered different amounts, and for different reasons. For example, sprinkler 2363 has watered 40-60% less than required due to the type light levels measured in its area. Sprinkler 2364 has not varied the amount of watering required by control unit 60 because of precipitation levels at its location. In this last case, the control system did not receive the message, so that sprinkler 2364's controller 2354 have to resend its message to the control system. It do so right away, within the two minutes allotted to the control unit to communicate with sprinkler 2364 to communicate, to make sure the message was received before the next sprinkler unit sent its message, and so that the control unit not confuse two sprinkler units' messages. This system has been used as an example only, and is by no means exclusive of embodiments, which can include new codes, meanings, times for communication, or message structures.
The value of having the standard pressure (S0) calculated every time the system commences communication is twofold: any variances in water pressure are offset, and leaks can be detected. Once standard pressure is calculated, central control system 60 communicates to local control systems 235n the amount of watering necessary for each sprinkler in the system (step 906), based on central control system 60's sensors and controls.
At the allocated time, central control system 60 sends pressure-based messages to each local control 235n regarding the amount of watering necessary for the territory being irrigated (step 906). Once the message is received, the sprinkler unit confirms the receipt of the message in the time allotted for central control system-sprinkler unit communication (step 907).
Central control system 60 causes the sprinkler units to adjust their irrigation amounts by its messages according to the desires of the user, and the central control system's sensors (step 910). Each local control system 235n executes irrigation based on two types of input: (A) the irrigation data received from central control system 60, and (B) readings from their local sensors 64, 66, 68, 70, and 72. Specifically, the input from local sensors 64, 66, 68, 70, and 72 is used to adjust the irrigation data received from central control system 60 at step 906.
As described in
If central control system 60 does not receive the sprinkler unit confirmation (step 908), and the control system 60 has not sent the message twice (step 944), it resends the message to the sprinkler unit in question (step 906). If central control system 60 transmits the irrigation message twice without return confirmation (step 944), it enters an error message for that sprinkler unit (step 948). If a message has not been sent to all sprinkler units, central control system 60 (step 912) initiates transmission of the irrigation message to the next sprinkler at the pre-selected time slot (step 908).
Table 1 (
The time allocation for communicating with the local control systems is pre-selected depending on the number of sprinkler units and complexity of the irrigation instructions. For example, central control system 60 transmits the irrigation instructions to local control system 2351 ten minute after 6 AM for a pre-selected period of ten minutes. This is a reserved time slot for local control system 2351, which system “wakes up” and “listens” for irrigation instructions, while the other local control systems 2352 through 235n are inactive. Time slots of other lengths can be selected.
As an example, if the preset timing for the start of the communication algorithm is 2:00 AM, pressure will be calibrated at 2:00-2:01 AM. Central control unit 60 has a time allotted for communication with each sprinkler unit: in this case, the central control system 60 has allotted 7 minutes for transmitting the irrigation message to sprinkler unit 1, and is ready at 2:10 AM to send the message. Similarly, sprinkler unit 1's controller “listens” for the message at 2:10 AM. Central control unit 60's irrigation message to sprinkler unit 1 consists of a header (“LSLS”), instructions for the irrigation time (“LLS”), and a footer (“LLLLL”), indicating the end of the message. The meaning of the message is to water for one hour. Each message to the sprinkler units follows a similar format.
Sprinkler unit 1 transmits its confirmation message at 2:18, sprinkler unit 2 at 2:28, etc. Similarly, the central control unit is ready to receive these messages at these same times. The message follows the same format as above: a header (“LSLL”), a message received/not received signal (“LSLL” or “LLS”), and a footer (“LLLLL”).
Referring again to
Referring now to
If the pressure is set for signaling, the sprinkler units send central control system 60 the confirmation messages (step 920). The central control system sends back a confirmation to the sprinkler units at step 921. If the sprinkler units do not receive confirmation (step 922), and the sprinkler units have not sent the message twice already (step 928), the message is resent (step 920). However, if the message had already been sent (step 930), the central control unit sets an error message for future servicing (step 930).
These steps are further described in
Central control system 60 then confirms the messages by each sprinkler unit. Again, there is a preset time that central control system 60 transmits, and that the sprinkler units receive: for sprinkler unit 1, that is 6:18-6:22 AM. For sprinkler unit 2, 6:28-6:32 AM, etc. The messages consist of a header, a received or not received message, and a footer (i.e., end of communication string).
At this point, if the central control system sent messages to all the sprinkler units (step 924), it shuts the system down until the next scheduled communication. The system will then turn on, recalibrate, and communicate in the same manner as that described above.
The parameters described can be changed, and are not inclusive: the time for communication, the number of times the message can be resent, the number of components (both for the sprinkler units and the central control system), and the nature of the messages, for example, can all be modified.
According to another embodiment, an ultrasonic communication system provides communication between the central control unit and the sprinkler units. While water is an ideal medium for transmitting mechanical sound waves, the irrigation pipes may “complicate” the propagation and detection of the signal. The system is similar to the system shown in
In the ultrasonic communication system, the generated longitudinal sound waves travel through the water in the water pipes. However, the communication system is sensitive to changes in the generated waves. Therefore, the ultrasonic communication system is designed with smooth pipes generally free of blemishes and discontinuities, which cause energy reflections. The reflection sensitivity can, however, be used to provide orientation and distance which can be used to identify the transmitter. That is, once the control unit received a signal, the nature of the signal could be used to ascertain which sprinkler unit had sent it. This is a desirable quality when setting up communication codes, particularly in simpler irrigation systems. In the ultrasound communication system, the central control system communicates with the local control system using algorithms similar to flow diagram 900. However, since the ultrasound system enables a higher data transmission rate, the communication code may be much more elaborate that the code examples provided in Tables 1 and 2.
Depending on the size and materials of the irrigation system, the scattering of the signals and their absorption could become a concern, and it may be necessary to have some of the sprinkler units relay signals so they can more easily and clearly reach more remote parts of the system. Controllers at certain points along the system is programmed to resend signals to the control unit from sprinkler units further away, and vice-versa. The necessity for this relay could be reduced not only by optimizing the shape and size of the system, but also by generally using relay transmitters and strategic locations of ultrasonic transducers or selection of suitable arrays.
The above described communications systems increase their reliability by optionally using an error control algorithm. The system can use either a forward error correction strategy (FEC) or an automatic repeat request strategy (ARR). The FEC algorithm, such as the Hamming code) provides for error correction where a transmission error is detected. The ARQ algorithm initiates automatically re-transmission if a communication error or corrupted data are detected. The FEC protocol is generally not preferred for the irrigation communication system of
Metallic input coupler 260 is rotatably attached to input port 290 using a C-clamp 262 that slides into a slit 264 inside input coupler 260 and also a slit 292 inside the body of input port 290. Metallic output coupler 280 is rotatably attached to output port 294 using a C-clamp 282 that slides into a slit 284 inside output coupler 280 and also a slit 296 inside the body of output port 294. When servicing delivery unit 10 (or in ground unit 236), this rotatable arrangement prevents tightening the water line connection to any of the two valve couplers unless attaching the wrench to the surface of couplers 260 and 280. (That is, a service person cannot tighten the water input and output lines by gripping on the valve body 256.) This protects the relatively softer plastic body 256 of automatic valve device 250. However, body 256 can be made of a metal in which case the above-described rotatable coupling is not needed. A sealing O-ring 266 seals input coupler 260 to input port 290, and a sealing O-ring 288 seals output coupler 280 to input port 294.
Referring to
Referring still to
Automatic valve device 250 also includes a service loop 390 (or a service rod) designed to pull the entire valve assembly, including attached actuator 80, out of body 256, after removing of plug 366. The removal of the entire valve assembly also removes the attached actuator 80 and piloting button 705 (shown in
There are various embodiments of electronics 500, which can provide a DC measurement, an AC measurement including eliminating noise using a lock-in amplifier (as known in the art). Alternatively, electronics 500 may include a bridge or another measurement circuit for a precise measurement of the resistivity. Electronic circuit 500 provides the resistivity value to microcontroller 62 and thus indicates when valve device 250 is in the open state. Furthermore, leak sensor 78 indicates when there is an undesired water leak between input coupler 260 and output coupler 280. The entire valve 250 is located in an isolating enclosure (e.g., enclosure 26 in
Automatic valve device 250 may include a standard diaphragm valve, a standard piston valve, or a novel “fram” piston valve 320 explained in detail in connection with
The present invention envisions valve device 326 having various sizes. For example, the “full” size embodiment has the pin diameter A=0.070″, the spring diameter B=0.360″, the pliable member diameter C=0.730″, the overall fram and seal's diameter D=0.812″, the pin length E=0.450″, the body height F=0.380″, the pilot chamber height G=0.280″, the fram member size H=0.160″, and the fram excursion I=0.100″. The overall height of the valve is about 1.39″ and diameter is about 1.178″.
The “half size” embodiment of the “fram piston” valve has the following dimensions provided with the same reference letters. In the “half size” valve A=0.070″, B=0.30, C=0.560″, D=0.650″, E=0.38″, F=0.310″, G=0.215″, H=0.125″, and I=0.60″. The overall length of the ½ embodiment is about 1.350″ and the diameter is about 0.855″. Different embodiments of the “fram piston” valve device may have various larger or smaller sizes.
Referring to
When the plunger of actuator 80 seals control passages 344A and 344B, pressure builds up in pilot chamber 342 due to the fluid flow from input port 318 through “bleed” groove 338. The increased pressure in pilot chamber 342 together with the force of spring 340 displace linearly, in a sliding motion over guide pin 336, fram piston 326 toward sealing lip 325. When there is sufficient pressure in pilot chamber 342, diaphragm-like pliable member 328 seals input port chamber 318 at lip seal 325. The soft member 328 includes an inner opening that is designed with guiding pin 336 to clean groove 338 during the sliding motion. That is, groove 338 of guiding pin 336 is periodically cleaned. Therefore, fram piston 326 is uniquely designed for controlling flow of “unclean” water (“gray water”) for irrigation.
The embodiment of
Fram member 426 defines a pilot chamber 442 arranged in fluid communication with actuator cavity 450 via control passages 444A and 444B. Actuator cavity 450 is in fluid communication with output port 421 via a control passage 446. Groove 438 (or grooves 438 and 438A) provides a communication passage between input port 419 and pilot chamber 442. Distal body 404 includes an annular lip seal 425 co-operatively arranged with pliable member 428 to provide a seal between input port 419 and output port 421. Distal body 404 also includes flow channel 417 providing communication (in the open state) between input port 419 and output port 421 for a large amount of fluid flow. Pliable member 428 also includes sliding seal lips 429A and 429B (or one sided sealing member depending on the pressure conditions) arranged to provide a sliding seal with respect to valve body 422, between pilot chamber 442 and input port 419. (Of course, groove 438 enables a controlled flow of fluid from input port 419 to pilot chamber 442, as described above.) The entire operation of valve device 400 is controlled by a single solenoid actuator, such as the isolated actuator, 81.
Isolated actuator 81 also includes a resilient diaphragm membrane 764 that may have various embodiments shown and described in connection with
Referring to still to
Isolated actuator 81 may be constructed either as a latching actuator (shown in
In the non-latching embodiment, there is no permanent magnet (i.e., no magnet 723). Thus, to keep armature 740 in the open state, a drive current must continue to flow in windings 728 to provide the necessary magnetic field. Armature 740 moves to the closed state under the force of spring 748 if there is no drive current. On the other hand, in the latching embodiment, a drive current is applied to windings 728 in opposite directions to move armature 740 between the open and closed states, but no drive current is necessary to maintain either state.
Referring still to
For example, the armature liquid may be water mixed with a corrosion inhibitor, e.g., a 20% mixture of polypropylene glycol and potassium phosphate. Alternatively, the armature fluid may include silicon-based fluid, polypropylene polyethylene glycol or another fluid having a large molecule. The armature liquid may in general be any substantially non-compressible liquid having low viscosity and preferably non-corrosive properties with respect to the armature. Alternatively, the armature liquid may be Fomblin or other liquid having low vapor pressure (but preferably high molecular size to prevent diffusion).
If there is anticorrosive protection, the armature material can be a low-carbon steel, iron or any soft magnetic material; corrosion resistance is not as important a factor as it would otherwise be. Other embodiments may employ armature materials such as the 420 or 430 series stainless steels. It is only necessary that the armature consist essentially of a ferromagnetic material, i.e., a material that the solenoid and magnet can attract. Even so, it may include parts, such as a flexible or other tip, that is not ferromagnetic.
Resilient diaphragm membrane 764 encloses armature fluid located in a fluid-tight armature chamber in communication with armature port 752 or 790 formed by the armature body. Furthermore, resilient diaphragm membrane 764 is exposed to the pressure of regulated fluid in the main valve and may therefore be subject to considerable external force. However, armature 740 and spring 748 do not have to overcome this force, because the conduit's pressure is transmitted through resilient diaphragm membrane 764 to the incompressible armature fluid within the armature chamber. The force that results from the pressure within the chamber therefore approximately balances the force that the conduit pressure exerts.
Referring still to
In the latching embodiment shown in
To return the armature to the illustrated, retracted position and thereby permit fluid flow, current is driven through the solenoid in the direction that causes the resultant magnetic field to reinforce that of the magnet. As was explained above, the force that magnet 723 exerts on the armature in the retracted position is great enough to keep it there against the spring force. However, in the non-latching embodiment that doesn't include magnet 723, armature 740 remains in the retracted position only so long as the solenoid conducts enough current for the resultant magnetic force to exceed the spring force of spring 748.
Advantageously, resilient diaphragm membrane 764 protects armature 740 and creates a cavity that is filled with a sufficiently non-corrosive liquid, which in turn enables actuator designers to make more favorable choices between materials with high corrosion resistance and high magnetic permeability. Furthermore, diaphragm membrane 764 provides a barrier to metal ions and other debris that would tend to migrate into the cavity.
Resilient diaphragm membrane 764 includes a distal sealing surface 766, which is related to the seat opening area, both of which can be increased or decreased. The distal sealing surface 766 and the seat surface of piloting button 705 can be optimized for a pressure range at which the valve actuator is designed to operate. Reducing distal sealing surface 766 (and the corresponding tip of armature 740) reduces the plunger area involved in squeezing the membrane, and this in turn reduces the spring force required for a given upstream fluid-conduit pressure. On the other hand, making the plunger tip area too small tends to damage resilient diaphragm membrane 764 during valve closing over time. Preferable range of tip-contact area to seat-opening area is between 1.4 and 12.3. The present actuator is suitable for a variety of pressures of the controlled fluid including pressures of about 150 psi. Without any substantial modification, the valve actuator may be used in the range of about 30psi to 80 psi, or even water pressures of about 125 psi.
Referring still to
The assembly of operator 81 (or 81A, or 81B) and piloting button 705 is usually put together in a factory and is permanently connected thereby holding resilient diaphragm membrane 764 and the pressure loaded armature fluid (at pressures comparable to the pressure of the controlled fluid). Piloting button 705 is coupled to the narrow end of actuator base 716 using complementary threads or a sliding mechanism, both of which assure reproducible fixed distance between distal end 766 of diaphragm membrane 764 and the sealing surface of piloting button 705. The coupling of operator 80 and piloting button 705 can be made permanent (or rigid) using glue, a set screw or pin. Alternatively, one member may include an extending region that is used to crimp the two members together after screwing or sliding on piloting button 705.
It is possible to install solenoid actuator 81 (or 81A or 81B) without piloting button 705, but this process is somewhat more cumbersome. Without piloting button 705, the installation process requires first positioning the pilot-valve body with respect to the main valve and then securing the actuator assembly onto the main valve as to hold the pilot-valve body in place. If proper care is not taken, there is some variability in the position of the pilot body due to various piece-part tolerances and possible deformation. This variability creates variability in the pilot-valve member's stroke. In a low-power pilot valve, even relatively small variations can affect timing or possibly sealing force adversely and even prevent the pilot valve from opening or closing at all. Thus, it is important to reduce this variability during installation, field maintenance, or replacement. On the other hand, when assembling solenoid actuator 81 (81A or 81B) with piloting button 705, this variability is eliminated or substantially reduced during the manufacturing process, and thus there is no need to take particular care during field maintenance or replacement. In automatic valve 250, piloting button 705 is co-operatively constructed and arranged with the design of cavity 350 and sealing surface 348 to enable a novel way of assembling a pilot-valve-operated valve 250.
Referring to
Preferably, resilient diaphragm membrane 764 has high elasticity and low compression (which is relatively difficult to achieve). Diaphragm membrane 764 may have some parts made of a low durometer material (i.e., parts 767 and 768) and other parts of high durometer material (front surface 766). The low compression of resilient diaphragm membrane 764 is important to minimize changes in the armature stroke over a long period of operation. Thus, contact part 766 is made of high durometer material. The high elasticity is needed for easy flexing of resilient diaphragm membrane 764 in regions 768. Furthermore, resilient membrane part 768 is relatively thin so that the diaphragm can deflect, and the plunger can move with very little force. This is important for long-term battery operation.
Referring to
Resilient diaphragm membrane 764 can be made by a two stage molding process whereby the outer portion is molded of a softer material and the inner portion that is in contact with the pilot seat is molded of a harder elastomer or thermo-plastic material using an over molding process. The forward facing insert 774 can be made of a hard injection molded plastic, such as acceptable co-polymer or a formed metal disc of a non-corrosive non-magnetic material such as 300 series stainless steel. In this arrangement, pilot seat 709 is further modified such that it contains geometry to retain pilot seat geometry made of a relatively high durometer elastomer such as EPDM 0 durometer. By employing this design that transfers the sealing surface compliant member onto the valve seat of piloting button 705 (rather than diaphragm member 764), several key benefits are derived. There are substantial improvements in the process related concerns of maintaining proper pilot seat geometry having no flow marks (that is a common phenomenon requiring careful process controls and continual quality control vigilance). This design enables the use of an elastomeric member with a hardness that is optimized for the application.
However, automatic valve device 250 may be used with other solenoid valves such as the bistable solenoid model no. AXB724 available from Arichell Technologies Inc., West Newton, Mass. Alternatively, actuator 80 may include a latching actuator (as described in U.S. Pat. No. 6,293,516, which is incorporated by reference), a non-latching actuator (as described in U.S. Pat. No. 6,305,662, which is incorporated by reference), or an isolated operator 81 as shown in
Microcontroller 814 is again designed for efficient power operation. Between actuations, microcontroller 814 goes automatically into a low frequency sleep mode and all other electronic elements (e.g., input element or sensor 818, power driver 820, voltage regulator or voltage boost 826) are powered down. Upon receiving an input signal from, for example, a motion sensor, microcontroller 814 turns on a power consumption controller 819. Power consumption controller 819 powers up signal conditioner that provides power to microcontroller 814.
Also referring to
To open the fluid passage, microcontroller 814 provides an OPEN control signal 815B (i.e., latch signal) to solenoid driver 820. The OPEN control signal 815B initiates in solenoid driver 820 a drive voltage having a polarity such that the resultant magnetic flux opposes the force provided by bias spring 748. The resultant magnetic flux reinforces the flux provided by permanent magnet 723 and overcomes the force of spring 748. Permanent magnet 723 provides a force that is great enough to hold armature 740 in the open position, against the force of return spring 748, without any required magnetic force generated by coil 728.
Referring to
To open the fluid passage, microcontroller 814 sends OPEN signal 815B to power driver 820, which provides a drive current to coil 842 in the direction that will retract armature 740. At the same time, coils 843A and 843B provide induced signals to the conditioning feedback loop, which includes a preamplifier and a low-pass filter. If the output of a differentiator 849 indicates less than a selected threshold calibrated for armature 740 reaching a selected position (e.g., half distance between the extended and retracted positions, or fully retracted position, or another position), microcontroller 814 maintains OPEN signal 815B asserted. If no movement of armature 740 is detected, microcontroller 814 can apply a different level of OPEN signal 815B to increase the drive current (up to several times the normal drive current) provided by power driver 820. This way, the system can move armature 740, which is stuck due to mineral deposits or other problems.
Microcontroller 814 can detect armature displacement (or even monitor armature movement) using induced signals in coils 843A and 843B provided to the conditioning feedback loop. As the output from differentiator 849 changes in response to the displacement of armature 740, microcontroller 814 can apply a different level of OPEN signal 815B, or can turn off OPEN signal 815B, which in turn directs power driver 820 to apply a different level of drive current. The result usually is that the drive current is reduced, or the duration of the drive current is much shorter than the time required to open the fluid passage under worst-case conditions (that has to be used without an armature sensor). Therefore, the system of
Advantageously, the arrangement of coil sensors 843A and 843B can detect latching and unlatching movements of armature 740 with great precision. (However, a single coil sensor, or multiple coil sensors, or capacitive sensors may also be used to detect movement of armature 740.) Microcontroller 814 can direct a selected profile of the drive current applied by power driver 820. Various profiles may be stored in microcontroller 814 and may be actuated based on the fluid type, fluid pressure, fluid temperature, the time actuator 840 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.
Optionally, microcontroller 814 may include a communication interface for data transfer, for example, a serial port, a parallel port, a USB port, or a wireless communication interface (e.g., an RF interface). The communication interface is used for downloading data to microcontroller 814 (e.g., drive curve profiles, calibration data) or for reprogramming microcontroller 814 to control a different type of actuation or calculation.
Referring to
Also referring to
Similarly, as described in connection with
While the invention has been described with reference to the above embodiments, the present invention is by no means limited to the particular constructions described and/or shown in the drawings. In any additional equivalent embodiment, any one of the above-described elements may be replaced by one or more equivalent elements, or similarly any two or more of the above-described elements may be replaced by one equivalent element. The present invention also comprises any modifications or equivalents within the scope of the following claims.
This is a continuation application of PCT application PCT/US2004/020504, filed on Jun. 24, 2004, entitled “Communication System for Multizone Irrigation,” which is a continuation-in-part of PCT application PCT/US2003/020117, filed on Jun. 24, 2003, entitled “Automatic Water Delivery Systems with Feedback Control,” which claims priority from U.S. Provisional Applications Nos. 60/391,282 and 60/391,284 both filed on Jun. 24, 2002, all of which are incorporated by reference. The PCT application PCT/US2004/020504 is also continuation-in part of PCT Application PCT/US2002/38757, filed on Dec. 4, 2002, and is a continuation-in-part of PCT/US02/38758, both filed on Dec. 4, 2002, which are incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
207482 | Blessing | Aug 1878 | A |
1501331 | Gulick | Jul 1924 | A |
2438207 | Derby | Mar 1948 | A |
2471328 | Jones | May 1949 | A |
2507966 | Filliung | May 1950 | A |
2603794 | Bokser | Jul 1952 | 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 |
3022450 | Chase, Jr. | 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 |
3151340 | Teshima | Oct 1964 | A |
3242940 | Sirotek | Mar 1966 | A |
3254664 | Delaney et al. | Jun 1966 | A |
3285261 | Chaney | Nov 1966 | A |
3314081 | Atkins et al. | Apr 1967 | A |
3318565 | Cutler | May 1967 | A |
3369205 | Hamrick | Feb 1968 | A |
3373449 | Rusnok | Mar 1968 | A |
3379214 | Weinberg | Apr 1968 | A |
3386462 | Walters | Jun 1968 | A |
3400731 | McCormack | Sep 1968 | A |
3406941 | Ichimori et al. | Oct 1968 | A |
3429333 | Schoepe et al. | Feb 1969 | A |
3480787 | Johansen | Nov 1969 | A |
3487477 | Classen | Jan 1970 | A |
3495803 | Schoepe et al. | Feb 1970 | A |
3495804 | Muller et al. | Feb 1970 | A |
3559675 | Schoepe et al. | Feb 1971 | A |
3575640 | Ishikawa | Apr 1971 | A |
3576277 | Blackmon | Apr 1971 | A |
3586017 | Walters | Jun 1971 | A |
3606241 | Bornholdt | Sep 1971 | A |
3638680 | Kopp | Feb 1972 | A |
3639920 | Griffin et al. | Feb 1972 | A |
3670167 | Forbes | Jun 1972 | A |
3693649 | Gordon et al. | Sep 1972 | A |
3724001 | Ichimori et al. | Apr 1973 | A |
3740019 | Kessell et al. | Jun 1973 | A |
D228782 | Taiani | Oct 1973 | S |
3763881 | Jones | Oct 1973 | A |
3778023 | Billeter | Dec 1973 | A |
3791619 | Pett | Feb 1974 | A |
3799198 | Kijimoto | Mar 1974 | A |
3802462 | Trösch | Apr 1974 | A |
3812398 | Kozel et al. | May 1974 | A |
3814376 | Reinicke | Jun 1974 | A |
3821967 | Sturman et al. | Jul 1974 | A |
3842857 | McCornack | Oct 1974 | A |
3863196 | Hilles | Jan 1975 | A |
3895645 | Johnson | Jul 1975 | A |
3951098 | Meyers | Apr 1976 | A |
4010769 | De Lorenzo et al. | Mar 1977 | A |
4065095 | Johnson | Dec 1977 | A |
4097786 | Lund | Jun 1978 | A |
4105186 | Eby | Aug 1978 | A |
4107046 | Corder | Aug 1978 | A |
4114647 | Sturman et al. | Sep 1978 | A |
4116377 | Andersson et al. | Sep 1978 | A |
4135696 | Saarem et al. | Jan 1979 | A |
4141091 | Pulvari | Feb 1979 | A |
4179691 | Keller | Dec 1979 | A |
4184445 | Burrows | Jan 1980 | A |
4206901 | Williams | Jun 1980 | A |
4207466 | Drage et al. | Jun 1980 | A |
4223698 | Reinicke | Sep 1980 | A |
4225111 | Stahle | Sep 1980 | A |
4229811 | Salem | Oct 1980 | A |
4231287 | Smiley | Nov 1980 | A |
4241759 | Billeter | Dec 1980 | A |
4272052 | Gidner | Jun 1981 | A |
4280680 | Payne | Jul 1981 | A |
4282430 | Hatten et al. | Aug 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 |
4396149 | Hirsch | Aug 1983 | A |
4402095 | Pepper | Sep 1983 | A |
4408745 | Swiers et al. | Oct 1983 | A |
4457452 | Symmons | Jul 1984 | A |
4488702 | Lapeyre | Dec 1984 | A |
4505450 | Saarem | Mar 1985 | A |
4505451 | Jonas | Mar 1985 | A |
4520516 | Parsons | Jun 1985 | A |
4539474 | Takahata | Sep 1985 | A |
4543991 | Fuchs | Oct 1985 | A |
4570272 | Kawaguchi et al. | Feb 1986 | A |
4570899 | Kingham | Feb 1986 | A |
4597895 | Bartlett | Jul 1986 | A |
4604735 | Parsons | Aug 1986 | A |
4606085 | Davies | Aug 1986 | A |
4609178 | Baumann | Sep 1986 | A |
4611356 | Lin | Sep 1986 | A |
4613764 | Lobato | Sep 1986 | A |
4645094 | Acklin et al. | Feb 1987 | A |
4651777 | Hardman | Mar 1987 | A |
4653534 | Chung-Shan | Mar 1987 | A |
4662563 | Wolfe, Jr. | May 1987 | A |
4669653 | Avelov | Jun 1987 | A |
4681141 | Wang | Jul 1987 | A |
4684920 | Reiter | Aug 1987 | A |
4693419 | Weintraub et al. | Sep 1987 | A |
4709427 | Laverty, Jr. | Dec 1987 | A |
4709728 | Ying-Chung | Dec 1987 | A |
4717237 | Austin | Jan 1988 | A |
4729342 | Loctin | Mar 1988 | A |
4756031 | Barrett | Jul 1988 | A |
4767922 | Stauffer | Aug 1988 | A |
4787411 | Moldenhauer | Nov 1988 | A |
4793588 | Laverty, Jr. | Dec 1988 | A |
4796654 | Simpson | 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 |
4836641 | Priaroggia | Jun 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 |
4901750 | Nicklas et al. | Feb 1990 | A |
4902887 | Everett, Jr. | Feb 1990 | A |
4910487 | Kleinhappl | Mar 1990 | A |
4911401 | Holcomb et al. | Mar 1990 | A |
4915347 | Iqbal et al. | Apr 1990 | A |
4919165 | Lloyd | Apr 1990 | A |
4921208 | LaMarca | May 1990 | A |
4921211 | Novak et al. | May 1990 | A |
4922433 | Mark | May 1990 | A |
4932430 | Fernstrom | Jun 1990 | A |
4934400 | Cuming | Jun 1990 | A |
4938384 | Pilolla et al. | Jul 1990 | A |
4941215 | Liu | Jul 1990 | A |
4941219 | Van Marcke | Jul 1990 | A |
4944487 | Holtermann | Jul 1990 | A |
4953141 | Novak et al. | Aug 1990 | A |
4953236 | Lee et al. | Sep 1990 | A |
4962790 | Chou et al. | Oct 1990 | A |
4972070 | Laverty, Jr. | Nov 1990 | A |
4977929 | Chinnock et al. | Dec 1990 | A |
4988074 | Najmolhoda | Jan 1991 | A |
4991819 | Laube | 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 |
5060859 | Bancroft | Oct 1991 | A |
5062164 | Lee et al. | Nov 1991 | A |
5062453 | Saadi et al. | Nov 1991 | A |
5074520 | Lee et al. | Dec 1991 | A |
5092560 | Chen | Mar 1992 | A |
5095944 | Hochstrasser | Mar 1992 | A |
5109885 | Tauscher | May 1992 | A |
5109886 | Takata et al. | May 1992 | A |
5111846 | Hochstrasser et al. | May 1992 | A |
5125621 | Parsons et al. | Jun 1992 | A |
5127625 | Kleinhappl | Jul 1992 | A |
5148826 | Bakhshaei | Sep 1992 | A |
5148985 | Bancroft | Sep 1992 | A |
5169118 | Whiteside | Dec 1992 | A |
5172193 | Payne et al. | Dec 1992 | A |
5181538 | Manganaro | Jan 1993 | A |
5188337 | Mertens et al. | Feb 1993 | A |
5195720 | Nortier et al. | Mar 1993 | A |
5202666 | Knippscheer | Apr 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 |
5255398 | Flynn et al. | Oct 1993 | A |
5265594 | Olsson et al. | Nov 1993 | A |
5265843 | Kleinhappl | Nov 1993 | A |
5295654 | Laube | Mar 1994 | A |
5295655 | Wilson et al. | Mar 1994 | A |
5299592 | Swanson | Apr 1994 | A |
5313673 | Saadi et al. | May 1994 | A |
5315719 | Tsutsui et al. | May 1994 | A |
5329965 | Gordon | Jul 1994 | A |
5335694 | Whiteside | Aug 1994 | A |
5339859 | Bowman | Aug 1994 | A |
5375811 | Reinicke | Dec 1994 | A |
D354113 | Wortier 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 |
5427351 | Korfgen et al. | Jun 1995 | A |
5431181 | Saadi et al. | Jul 1995 | A |
5433245 | Prather et al. | Jul 1995 | A |
5455971 | Sakakibara et al. | Oct 1995 | A |
5456279 | Parsons et al. | Oct 1995 | A |
5456448 | Chou | Oct 1995 | A |
5464041 | Reinicke | Nov 1995 | A |
5467799 | Buccicone et al. | Nov 1995 | A |
5473723 | Stockman et al. | Dec 1995 | A |
5474303 | Coles | Dec 1995 | A |
5481187 | Marcott et al. | Jan 1996 | A |
5508510 | Laverty et al. | Apr 1996 | A |
5511579 | Price | Apr 1996 | A |
5535781 | Paterson et al. | Jul 1996 | A |
5539198 | McMichael et al. | Jul 1996 | A |
5548119 | Nortier | Aug 1996 | A |
5555912 | Saadi et al. | Sep 1996 | A |
5564462 | Storch | Oct 1996 | A |
5566702 | Philipp | Oct 1996 | A |
5570869 | Diaz et al. | Nov 1996 | A |
5574617 | Shimanuki et al. | Nov 1996 | A |
5583434 | Moyers et al. | Dec 1996 | A |
5584465 | Ochsenreiter | Dec 1996 | A |
5595216 | Pilolla | Jan 1997 | A |
5599003 | Seemann et al. | Feb 1997 | A |
5600237 | Nippert | Feb 1997 | A |
5636601 | Moriya et al. | Jun 1997 | A |
D381008 | Parsons et al. | Jul 1997 | S |
5655747 | Pasut | Aug 1997 | A |
5655748 | Regelbrugge et al. | Aug 1997 | A |
5668366 | Mauerhofer | Sep 1997 | A |
5680879 | Sheih et al. | Oct 1997 | A |
5708355 | Schrey | Jan 1998 | A |
5716038 | Scarffe | Feb 1998 | A |
5747684 | Pace et al. | May 1998 | A |
5749521 | Lattery | May 1998 | A |
5758688 | Hamanaka et al. | Jun 1998 | A |
D396090 | Marcichow et al. | Jul 1998 | S |
5775372 | Houlihan | 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 |
5836339 | Klever et al. | Nov 1998 | A |
5839660 | Morgenstern et al. | Nov 1998 | A |
5881993 | Wilson et al. | Mar 1999 | A |
5883557 | Pawlak et al. | Mar 1999 | A |
5887848 | Wilson | Mar 1999 | A |
5900201 | Chatterjee et al. | May 1999 | A |
5901384 | Sim | May 1999 | A |
5905625 | Schebitz | May 1999 | A |
5918855 | Hamanaka et al. | Jul 1999 | A |
5927328 | Nelson et al. | Jul 1999 | A |
5927603 | McNabb | Jul 1999 | A |
5941505 | Nagel | Aug 1999 | A |
5950983 | Jahrling | Sep 1999 | A |
5964192 | Ishii | 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 |
6024059 | Kamimaru et al. | Feb 2000 | A |
6039067 | Houlihan | Mar 2000 | A |
6044699 | Greenblatt et al. | Apr 2000 | A |
6044814 | Fuwa | Apr 2000 | A |
6056261 | Aparicio et al. | May 2000 | A |
6058647 | Emalfarb | May 2000 | A |
6073904 | Diller et al. | Jun 2000 | A |
6085790 | Humpert et al. | Jul 2000 | A |
6123839 | Sussman | 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 |
6198398 | Velasquez | Mar 2001 | B1 |
6212697 | Parsons et al. | Apr 2001 | B1 |
6216730 | Hall | Apr 2001 | B1 |
6227219 | Pino | May 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 |
6298872 | Keller | Oct 2001 | B1 |
6299127 | Wilson | Oct 2001 | B1 |
6305662 | Parsons et al. | Oct 2001 | B1 |
6340032 | Zosimadis | Jan 2002 | B1 |
6342295 | Kobayashi | Jan 2002 | B1 |
6353942 | Pondelick et al. | Mar 2002 | B1 |
6367096 | Quintana | Apr 2002 | B1 |
6382586 | Wilson et al. | May 2002 | B1 |
6393634 | Kodaira et al. | May 2002 | B1 |
6401530 | Roman | Jun 2002 | B1 |
6408881 | Lorenzelli et al. | Jun 2002 | B2 |
6425415 | Lorenzelli et al. | Jul 2002 | B2 |
6445565 | Toyoda et al. | Sep 2002 | B1 |
6450478 | Parsons et al. | Sep 2002 | B2 |
6507200 | Brandelik et al. | Jan 2003 | B2 |
6532803 | Hutchinson et al. | Mar 2003 | B2 |
6609698 | Parsons et al. | Aug 2003 | B1 |
6619320 | Parsons et al. | Sep 2003 | B2 |
6619614 | Parsons et al. | Sep 2003 | B2 |
6643853 | Wilson et al. | Nov 2003 | B2 |
6662632 | Parker et al. | Dec 2003 | B1 |
6685158 | Parsons | Feb 2004 | B2 |
6763703 | Krieger et al. | Jul 2004 | B2 |
7032435 | Hassenflug | Apr 2006 | B2 |
20070051166 | Baker et al. | Mar 2007 | A1 |
Number | Date | Country | |
---|---|---|---|
20060202051 A1 | Sep 2006 | US |
Number | Date | Country | |
---|---|---|---|
60391284 | Jun 2002 | US | |
60391282 | Jun 2002 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2004/020504 | Jun 2004 | US |
Child | 11318254 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US03/20117 | Jun 2003 | US |
Child | PCT/US2004/020504 | US | |
Parent | PCT/US02/38758 | Dec 2002 | US |
Child | PCT/US03/20117 | US | |
Parent | PCT/US02/38757 | Dec 2002 | US |
Child | PCT/US02/38758 | US |