The present disclosure relates to systems and methods for event monitoring and detection in liquid level monitoring systems. Various embodiments disclosed herein improve the battery life of liquid level monitoring systems and will improve the reliability and efficiency of systems using consumable liquids (e.g., liquid propane) that are manually replenished.
The present embodiments will become more fully apparent from the following description and appended claims, taken in conjunction with the accompanying drawings. Understanding that the accompanying drawings depict only typical embodiments, and are, therefore, not to be considered to be limiting, the embodiments will be described and explained with specificity and detail in reference to the accompanying drawings, in which:
It will be readily understood that the components of the embodiments, as generally described and illustrated in the Figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of various embodiments, as represented in the Figures, is not intended to limit the scope of the present disclosure, as claimed, but is merely representative of various embodiments. While the various aspects of the embodiments are presented in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The phrases “connected to,” “coupled to” and “in communication with” refer to any form of interaction between two or more entities, including mechanical, electrical, magnetic, and electromagnetic interaction. Two components may be coupled to each other, even though they are not in direct contact with each other.
Systems for monitoring a liquid level may be used in a variety of circumstances and applications involving systems that utilize a consumable liquid. Such systems may require periodic manual replenishment. For example, a liquid propane tank may be used as a fuel source for a wide variety of systems. The level of liquid propane tank may be monitored so that manual replenishment occurs as needed.
Inefficiencies may result by simply replenishing tanks on a fixed schedule, particularly in instances where demand for the consumable liquid is variable. For instance, if demand for the consumable liquid is low during a specific period, it may be unnecessary to replenish the consumable liquid, according to the fixed schedule. By contrast, if demand for the consumable liquid is high during a specific period, the supply of the consumable liquids stored in the tank may be exhausted before the next scheduled replenishment. Therefore, suppliers may be faced with “No Fill Needed” or “Out of Fuel” events, which are inefficient and costly.
A liquid level monitoring system may be utilized in order to determine a liquid level in the storage tank. Various embodiments of such systems are disclosed in U.S. Pat. No. 7,287,425 (the “425 Patent”), in U.S. Pat. No. 7,905,143 (the “143 Patent”), and U.S. patent application Ser. No. 12/411,242 (the “242 Application”) now U.S. Pat. No. 8,104,341. The entirety of the 425 Patent, the 143 Patent, and the 242 Application are incorporated by reference.
Various embodiments of liquid level monitoring systems disclosed in the 425 Patent, the 143 Patent, and the 242 Application rely on battery power. Reducing power consumption in such systems may allow the systems to operate more reliably, for longer periods of time, and less expensively. While the cost of the batteries may be relatively low, according to various embodiments, an operator may need to be dispatched to a remote location in order to simply replace batteries. Various embodiments disclosed herein, and in connection with the 425 Patent, the 143 Patent, and the 242 Application, utilize satellite communication for the transmission of various measurements. In addition to consuming power, satellite transmissions may also have an associated cost. Accordingly, reducing the number of transmissions may both decrease power consumption and decrease expenses associated with data transmission. Further, by moving to an event driven schedule for transmission, fuel outages and unnecessary refueling trips may be more effectively avoided.
According to various embodiments disclosed herein, battery power may be conserved by reducing the number of transmissions made by a liquid level monitoring system. Certain embodiments may be configured, according to a schedule for making measurements. The measurement may then be compared against one or more thresholds to determine whether to transmit the measurements. A variety of thresholds may be specified and utilized to determine when it is appropriate to transmit the measurements. For example, a threshold may relate to a liquid level in a tank or to a temperature at a location of the liquid level monitoring system. Further, various embodiments may be configured to detect a change in a monitored condition (e.g., use of a liquid stored in a tank, a temperature at a location of the liquid level monitoring system, etc.). Upon the detection of a change in the monitored condition, a measurement may be made and compared to a threshold. Such embodiments may further conserve battery power by reducing the number of measurements to be made and by reducing the number of measurements transmitted.
Sensing of a liquid level in a tank may be performed utilizing sonic or ultrasonic measurement techniques. An externally mounted ultrasonic emitter may generate an ultrasonic beam and receive an echo of the ultrasonic beam off a liquid surface inside the tank. The amount of time that passes between generating the beam and receiving the echo may be determined and may be referred to as a time-of-flight. If a liquid level and density are known and the geometry of a tank is known, then the liquid volume in the tank can be calculated, based upon the measured time-of-flight.
Referring to
According to the embodiment illustrated in
According to the system illustrated in
The battery box 112 may be located in a position that allows for easy access within communications unit 110. Operators of the system 100 may be required to access the battery box within communications unit 110 in order to replace a battery. As shown in
System 200 also includes a communication unit 224 that is in electrical communication with the transducer unit 202. According to the illustrated embodiment, a battery 218 is contained within communications unit 224. The battery 218 is in electrical communication with all components in the ultrasonic liquid level monitoring system 200 requiring electrical power. An electrical cable 234 may connect the transducer unit 202 to the communications unit 224.
The communications unit 224 may also contain a local data link 228 and a wireless transceiver 230. The local data link 228 and the wireless transceiver 230 may be in communication with a processor 220 and/or a machine-readable storage medium by way of a data connection 226. According to one embodiment, local data link 228 may be embodied as an RS-232 port. In alternate embodiments, local data link 228 may be embodied as an Ethernet port, universal serial bus (USB) port, IEEE 1394 port, and the like. Local data link 228 may be connected to a wireless transceiver 230. Wireless transceiver 230 may be a Bluetooth wireless module, or may operate using other wireless technologies including IEEE 802.11 (a/b/g/n), wireless USB, ultrawide band, and the like. The local data link 228 and the wireless transceiver 230 may be deactivated or put into a low-power state during periods of inactivity to conserve battery power.
The communication unit 224 may comprise the processor 220. The processor 220 is powered by the battery power supply 218. Instructions executable by processor 220 may be stored on machine-readable storage medium 238. As used herein, a software module or component may include any type of computer instruction or computer executable code located within a memory device that is operable in conjunction with appropriate hardware to implement the programmed instructions. A software module or component may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that performs one or more tasks or implements particular abstract data types. In certain embodiments, a particular software module or component may comprise disparate instructions stored in different locations of a memory device, which together implement the described functionality of the module. Machine-readable storage medium 238 may be the repository of various modules configured to perform any of the features described herein. According to alternative embodiments, the processor 220 may further include memory and/or firmware.
According to the illustrated embodiment, machine-readable storage medium 238 comprises a time-of-flight module 240, a threshold module 242, a tank parameters module 244, a monitored condition module 246, and a communications module 248. Time-of-flight module 240 may be configured to interpret data received from emitter 206 and perform calculations in order to determine a time-of-flight. As described above, with a known tank geometry, the time-of-flight may be used to determine the volume of a liquid stored in the tank. Threshold module 242 may be configured to compare the determined time-of-flight or the volume of liquid stored in the tank to a specified threshold. Further, threshold module 242 may also store and compare other thresholds related to monitored conditions detected by system 200 (e.g., battery level, temperature, etc.). Tank parameters module 244 may be configured to store information regarding a monitored tank. For example, tank parameters module 244 may store information regarding a tank geometry, a tank volume, etc. Further, tank parameters module 244 may be configured to determine a volume of liquid stored in a tank based upon a determined time-of-flight. Monitored condition module 246 may be configured to detect a change in a monitored condition (e.g., use of a liquid stored in a tank, of the liquid level monitoring system, etc.). System 200 may receive input from one or more sensors (e.g., temperature sensor 208) configured to detect changes in a monitored condition. According to other embodiments, a sensor may be used to determine when liquid is being removed from the tank. Communications module 248 may be configured to selectively transmit an indication of the volume of the liquid in the tank either via a satellite radio, the local data link 228, or the local wireless transceiver 230.
The processor 220 may also be in electrical communication with the satellite radio 214 by way of the data link 236. The data connection 226 and the electrical cable 234 may be embodied within a single cable. The satellite radio 214 is in communication with an antenna 216 and the battery power supply 218. To minimize size and cost, the satellite radio 214 may be a simplex radio capable of transmitting but not receiving. Alternatively, a two way radio capable of sending and receiving commands can be utilized.
According to one embodiment, the processor 220 may measure the liquid level in a tank according to a schedule. When scheduled measurements occur, information about the time-of-flight, the temperature of the liquid, and the battery level may all be collected and transmitted in a single transmission using satellite radio 214 and antenna 216. According to an alternative embodiment, one or more sensor components may provide input to the system 200 when a change in a monitored condition is detected.
Once a measurement has been made, the measurement may be compared against one or more thresholds to determine whether the measurement should be classified as a reportable event and transmitted. For example, if a measurement of a liquid fuel level indicates that the tank is nearly full, the system 200 may be configured to not transmit that measurement. The thresholds may be variable or fixed, depending on a particular application. For example, in certain applications it may be important that the tank is never completely depleted. Accordingly, in this application, system 200 may be configured to transmit more regularly (e.g., weekly) or at a higher fill level threshold (e.g., below 40% of capacity). Further, system 200 may also be used in some applications where use of the liquid is sporadic, such as a cabin. During periods of occupancy, the liquid fuel may be used at a relatively rapid rate in order to provide heat, electricity, fuel for cooking, and the like. In this application, it may be desirable to know relative changes in the level of a liquid fuel, since such changes may warrant closer monitoring during a period of activity, and less frequent monitoring during a period of inactivity. In another example, an appropriate schedule for making measurements may be based upon seasonality or a time of year. For example, in certain agricultural applications, a liquid fuel (e.g., propane) may be used more heavily in the winter than in the summer. Accordingly, in the summer, the system may be configured to report a liquid level once per month. In the winter, the system may be configured to report the liquid level once per week.
Referring to
Earth station 308 or portable electronic device 318 receives the data input and, together with previously stored information on tank geometry or dimensions and suitable computer readable instructions, processes the received data to calculate the volume of the liquid in the tank 310. The calculated measurement may also be stored in the storage medium and may be read out, and displayed by Earth station 308 or portable electronic device 318. Earth station 308 or portable electronic device 318 may be in electrical communication with a network 312, such as a LAN, WAN, or the Internet. Through network 312, the calculated measurement may be read out, displayed or stored on a second computer 314. Portable electronic device 318 may be connected to network 312 using mobile data communications link 320. In alternative embodiments, portable electronic device 318 may lack a mobile data communications link, but may later be synchronized with a computer system and may, at that time, transfer information about the volume of the liquid in the tank 310.
Portable electronic device 318 may be embodied as a wide variety of commercially available portable electronic devices. For example, portable electronic device 318 may be a portable computer (e.g., a laptop computer, or a tablet computer, such as an iPad), a personal digital assistant (PDA), or a “smart” cellular telephone. Many commercially available portable electronic devices include the ability to communicate using wireless data protocols, such as Bluetooth, IEEE 802.11, or include wired communication ports, such as Ethernet, RS-232, USB, or IEEE 1394. Further, many commercially available portable electronic devices are capable of performing calculations and running software applications that may be required in order to determine a liquid level or to interface with the communications unit 322. A local data link configured to communicate with a portable electronic device is advantageous in minimizing the installation and servicing costs associated with a liquid level monitoring system.
If a measurement is determined to be a reportable event that is to be transmitted, the measurement may be transmitted at 408. According to multiple embodiments, following the completion of transmission of the measurement, multiple notifications may be generated based on established conditions. For example, where unavailability of a liquid fuel may be costly, multiple notifications regarding a fuel measurement below a specified threshold may be generated. E-mail messages, text messages, automated telephone recordings, and other such notification mechanisms may be employed.
Screen shot 530 illustrates a screen that may be utilized to establish one or more alarms that may be associated with a monitored criteria. According to the illustrated embodiment, the monitored criteria include a minimum fill level 532 and a minimum battery level 534. Depending upon the application for which the particular storage tank is used, thresholds 532 and 534 may be adjusted. For example, certain applications may require high reliability, and thus a minimum fill level alarm 532 may be set at an appropriately high level in order to ensure that the tank is not depleted. According to alternative embodiments, additional monitored criteria may be included and thresholds associated with such criteria may be specified.
Screen shot 540 illustrates a first calibration screen. Using current fill level 542 a user may input a fill level based on an on-site gauge connected to the tank. The manual input may be based on the on-site gauge mounted to the tank. Alternatively, a user may make a measurement using the ultrasonic fuel level measurement system by pressing button 544. Using calibration button 546 on screen 540, a user may open a calibration screen 550. Calibration screen shot 550 may show a current fill level 552. The calibration process may be used to optimize a transducer for use with a specific tank. One portion of the calibration process may include identification of a gain and an optimized frequency to be used at 556. The optimized frequency value may be stored for future usage by the system. The calibration process may also provide a user with an indication of a current fill level, both in relative terms (e.g., 35% of capacity) or as a measurement of the number of gallons/liters stored in the tank 554. Additional details regarding the selection of an optimized frequency are provided in the 425 Patent. Screen shot 560 illustrates a message that may be displayed upon the successful commissioning of the unit.
It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the disclosure. The scope of the present disclosure should, therefore, be determined only by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
2570218 | Draganjac | Oct 1951 | A |
2600341 | Thompson | Jun 1952 | A |
2775748 | Rod et al. | Dec 1956 | A |
3100885 | Welkowitz et al. | Aug 1963 | A |
3687219 | Langlois | Aug 1972 | A |
3985030 | Charlton | Oct 1976 | A |
4320659 | Lynworth et al. | Mar 1982 | A |
4440025 | Hayakawa et al. | Apr 1984 | A |
4602344 | Ferretti et al. | Jul 1986 | A |
4736329 | Ferretti et al. | Apr 1988 | A |
4788648 | Ferretti et al. | Nov 1988 | A |
4815323 | Ellinger et al. | Mar 1989 | A |
4853694 | Tomecek | Aug 1989 | A |
4868797 | Soltz | Sep 1989 | A |
4901245 | Olson et al. | Feb 1990 | A |
5131271 | Haynes et al. | Jul 1992 | A |
5150334 | Crosby | Sep 1992 | A |
5195058 | Simon | Mar 1993 | A |
5235553 | Garlick et al. | Aug 1993 | A |
5261274 | Nemirow | Nov 1993 | A |
5303585 | Lichte | Apr 1994 | A |
5319973 | Crayton et al. | Jun 1994 | A |
5335545 | Leszczynski | Aug 1994 | A |
5425523 | Madey et al. | Jun 1995 | A |
5511041 | Michalski | Apr 1996 | A |
5563478 | Suganuma | Oct 1996 | A |
5568449 | Rountree et al. | Oct 1996 | A |
5586085 | Lichte | Dec 1996 | A |
5644299 | Cruickshank | Jul 1997 | A |
5697248 | Brown | Dec 1997 | A |
5755136 | Getman et al. | May 1998 | A |
5778726 | Muller et al. | Jul 1998 | A |
5866815 | Schwald et al. | Feb 1999 | A |
5991234 | Sejalon et al. | Nov 1999 | A |
6053041 | Sinha | Apr 2000 | A |
6317029 | Fleeter | Nov 2001 | B1 |
6396819 | Fleeter et al. | May 2002 | B1 |
6397656 | Yamaguchi et al. | Jun 2002 | B1 |
6412344 | Danicich et al. | Jul 2002 | B1 |
6481627 | Guerreri | Nov 2002 | B1 |
6536275 | Durkee et al. | Mar 2003 | B1 |
7245059 | Lagergren et al. | Jul 2007 | B2 |
7287425 | Lagergren | Oct 2007 | B2 |
7905143 | Lagergren | Mar 2011 | B2 |
8104341 | Lagergren et al. | Jan 2012 | B2 |
20040016442 | Cawlfield | Jan 2004 | A1 |
20040173021 | Lizon et al. | Sep 2004 | A1 |
20050192727 | Shostak et al. | Sep 2005 | A1 |
20050284218 | Lagergren | Dec 2005 | A1 |
20050289021 | Lagergren | Dec 2005 | A1 |
20060144139 | Miyagawa | Jul 2006 | A1 |
20060169056 | Dockendorff et al. | Aug 2006 | A1 |
20060236766 | Quirch et al. | Oct 2006 | A1 |
20070016069 | Grunwald et al. | Jan 2007 | A1 |
20070080609 | Johnson et al. | Apr 2007 | A1 |
20070084283 | Carlson et al. | Apr 2007 | A1 |
20070261487 | Sintes et al. | Nov 2007 | A1 |
20080208060 | Murkin | Aug 2008 | A1 |
20080319688 | Kim | Dec 2008 | A1 |
20090025474 | Lagergren | Jan 2009 | A1 |
20090303059 | Von Lintzgy et al. | Dec 2009 | A1 |
20100242593 | Lagergren et al. | Sep 2010 | A1 |
Number | Date | Country |
---|---|---|
0151753 | Aug 1985 | EP |
08-211883 | Aug 1996 | JP |
WO2009014790 | Jan 2009 | WO |
WO 2010111450 | Sep 2010 | WO |
Entry |
---|
Response to Office Action dated Nov. 17, 2006 for U.S. Appl. No. 11/131,435. |
Response to Restriction Requirement dated May 28, 2009 for U.S. Appl. No. 11/880,671. |
International Search Report dated Mar. 25, 2010 for PCT/US2010/028586. |
Notice of Allowance dated Jan. 20, 2011 for U.S. Appl. No. 11/880,671. |
Office Action dated Jul. 28, 2010 for U.S. Appl. No. 11/880,671. |
Office Action dated Apr. 14, 2010 U.S. Appl. No. 11/880,671. |
Office Action dated Oct. 2, 2009 for U.S. Appl. No. 11/880,671. |
Office Action dated Nov. 17, 2006 for U.S. Appl. No. 11/131,434. |
Office Action dated Nov. 21, 2006 for U.S. Appl. No. 11/131,435. |
International Search Report and Written Opinion dated Aug. 7, 2008 for PCT/US08/62603. |
Restriction Requirement dated May 28, 2009 for U.S. Appl. No. 11/880,671. |
Notice of Allowance dated May 3, 2007 for U.S. Appl. No. 11/131,434. |
Notice of Allowance dated May 22, 2007 for U.S. Appl. No. 11/131,435. |
International Search Report and Written Opinion for PCT/US2012/027199 filed Mar. 1, 2012, and mailed Sep. 3, 2012, 8 pgs. |
International Preliminary Report on Patentability and Written Opinion mailed Oct. 28, 2010 for PCT/US2010/028586. |
Office Action mailed Sep. 7, 2011 for U.S. Appl. No. 12/411,242. |
Number | Date | Country | |
---|---|---|---|
20120259560 A1 | Oct 2012 | US |