Various embodiments described herein relate generally to automated methods and systems for distributing a desired amount or dose of particles from a storage container.
It may be desirable to provide automated systems and methods for distributing a desired amount or dose of particles from a storage container; the present invention provides such systems and methods.
In an automatic system that includes a particle storage container coupled to a particle distribution mechanism that distributes particles from the storage container, it is desirable to distribute a known quantity or amount of the particles 5. In an embodiment, the desired distributed amount is based on the weight of the particles distributed from a storage container. In an embodiment, the desired particle 5 weight (termed dose) may vary as a function of the next use of the particles 5. In an embodiment, the storage container ideally may hold many doses of particles, about 5 to 200 doses in an embodiment.
In an embodiment, the particles may be coffee beans (roasted or green) and the storage container (termed a hopper in an embodiment) may hold the coffee beans. To create a brewed espresso weighting about 30 g (grams), 20 g of coffee beans may be ideally consumed-used (ratio of about 1.5 espresso to coffee beans). For regular coffee, however the ideal ratio may be about 1.18. Accordingly, in an automated system and method for distributing particles (such as coffee beans) from a storage container (such as coffee bean hopper), the desired dose (weight) of particles in a dose (coffee beans) may vary as a function of the next usage of the particles (to produce an espresso, cup of coffee, for example).
A controller 10A may be coupled to the scale or weight module 50A and receive either an analog or digital signal that indicates the weight of the combination of the PSC 20A, PDM 30A, and any particles 5 therein. The controller 10A may also know the weight of the combination of the PSC 20A, PDM 30A alone (no particles)—i.e., the tare weight. Based on the tare weight, the controller 10A may be able to determine the weight of any particles 5 in the combination of PSC 20A, PDM 30A based on the weight module signal 50A.
In an embodiment, the combination of the PSC 20A and PDM 30A may have a tare weight of about 100 to 2000 grams and be able to store from 100 to 1000 grams of particles 5. The weight module 50A may be able to affect or provide a signal indicating weights from 10 to 3000 grams with an accuracy of 0.1 to 0.8 grams in an embodiment. In an embodiment, the weight module 50A may include a load cell, strain gauge, or other devices capable of providing the required degree of accuracy as a function of the particle 5 weight and dose weight. The controller 10A may also be coupled to the PDM 30A to control and vary the distribution rate of particles 5 such as 1 to 50 particles for a predetermined time interval (such as per second . . . ) if so desired in an embodiment. For example, in an embodiment, the PDM 30A may include a motor 35D coupled to a distribution device such as blades, rotating window sized to permit particles to pass therethrough, auger 33D, or another device.
In operation, controller 10A may employ the algorithm 200A shown in
In an embodiment based on the requested dose, the controller 10A may activate the PDM for a first predetermined time interval 30A (activity 204A). The predetermined time interval may be based on preprogrammed ratios of time to dose. Such ratios may be based on calibration of the PSC/PDM for certain particles 5. The User may be able to specify the particles 5 in the PSC/PDM so the activation time may be adjusted accordingly. In an embodiment, the first predetermined time interval may be selected to provide slightly less than the desired weight or dose to prevent over distribution of particles 5 (activity 206A). For example, where 20 grams of particles are desired (dose weight of 20 grams), the PDM 30A may be activated to distribute a certain percentage less (from 5 to 20% less) and then weight the PSC/PDM-particles 5 remaining combination (activity 208A).
Based on the combined weight of the PSC/PDM-particles 5 prior to PDM 30A activation, the dose of particles 5 distributed may be determined. When the dose weight is within a tolerance (within the weight mechanism accuracy) or a percentage of the dose weight in an embodiment (0.5 to 5% in an embodiment), the distribution process may be complete. For example where the desired dose weight is 20 g, the desired accuracy may be 0.2 g or about one particle (coffee bean). Otherwise, the differential between the required weight or dose and that distributed thus far may be determined and used to determine a differential dose that is distributed using algorithm activities 204A-212A until the desired total dose is distributed within tolerance. Such a process may eliminate weighting errors versus continuously weighting the combination of PSC/PDM-remaining particles 5 while the PDM 30A actively distributing particles 5.
In another embodiment, the controller 10A may continuously weight-receive an indication of weight from the weight mechanism 50A of the combination of PSC/PDM-remaining particles 5 while the PDM 30A is actively distributing particles 5. The controller 10A may continue to direct the PDM 30A to operate until the desired dose weight (loss of weight of combination of PSC/PDM-particles 5 equals the desired particle 5 weight dose) is achieved within tolerances. In particular, in an embodiment, a controller 10A may employ the algorithm 200D shown in
As shown in
While the controller 10A is directing a PDM 30A to operate it may determine whether the dose weight (particles 5 distributed weight) continues to increase (activity 206D). The controller 10A via a scale 20D may be able to determine the overall weight to the PDM 30A, PSC 20A and any particles 5 located therein is not changing over time and thus particles 5 are not being distributed. The controller 10A via the known tare weight of the PDM 30A and PSC 20A and the current measured weight via the scale 50A (activity 224D) may be able to determine and report that a system 100A-D is out of particles 5 (activity 226D). Otherwise, when flow of particles 5 has stopped but the tare weight has not been detected, the controller 10A may report that the remaining particles 228D are not flowing in the system 100D. In an embodiment, the controller 10A may engage a vibration module coupled to the PSC 20A or PDM 30A to attempt to enable particles to flow when they are determined not to be flowing. In such an embodiment, the weight of the vibration module may be known and included in the overall weight of the PDM 30A, PSC 20A and any particles 5 located therein. For example, the particles 5 may be coffee beans and may stick together or a wall in a PSC 20A.
When the dose weight continues to increase (at a desired rate in an embodiment), the controller 10A may direct the PDM 30A to continue to distribute particles 5 at the first rate until the desired does weight (of distributed particles 5) is achieved. In an embodiment, once the controller 10A determines a predetermined percentage (lower than 100%) of dose weight is achieved (activity 208D) such as about 80% to 95% or about 90% in an embodiment, the controller 10A may reduce the distribution rate of a PDM 30A to a second, lower rate (activity 212D). For example, the controller 10A may lower the distribution rate to 1 particle (coffee bean) per second for the second rate in an embodiment. The controller 10A may continue to ensure that particles are being distributed by monitoring overall weight (activity 214D) and continue to operate the PDM 30A at the second, lower rate until the desired dose (weight) is achieved (activity 216D) within tolerances (e.g., within 0.2 g for a 20 g dose). Depending on the system 100A-D other activities may be performed once the dose weight is achieved including activating a particle processing mechanism 70A such a grinder 70C and another system to use the processed particles, such as a brew unit 80C.
In an embodiment, the PPM 70A may be directed to process particles in its holding area 72A when the required dose of particles 5 has been distributed therein by the PSC/PDM per activities 204B-212B (activity 214B). The results of the PPM 70A processing may be collected in the processed particle collection bin 40B. For example, in an embodiment the particles 5 may be coffee beans and the PPM 70A may be a grinder.
As shown in
In an embodiment, the controller 10A may direct the PDM 30C to distribute a dose of coffee beans 5 to the coffee holding area 72C (activities 204C-212C) when either the grinder 70C or the brew unit 80C have completed their cycles (activities 214C, 216C) in an embodiment. Once a dose of coffee beans 72C has been distributed into the coffee bean holding area 72C, the controller 10A may activate the grinder 70C for a predetermined time sufficient to process all beans in the holding area 70C (activity 214C). In an embodiment, the output of the grinder (coffee grounds) may be directed in the brew unit 80C for processing. Once the grinder 70C has been activated for the predetermined time interval, the controller 10A may direct the brew unit 80C to process the received grounds (activity 216C). The brew unit 80C may generate coffee-espresso via the spout 84C into container 90C and send spent grounds into the ground collection bin 40C (activity 216C).
As shown in
The user input device 272 may comprise an input device such as a keypad, touch screen, track ball or other similar input device that allows the user to navigate through menus, displays in order to operate systems 100A-D. The display 268 may be an output device such as a CRT, LCD, touch screen, or other similar screen display that enables the user to read, view, or hear received messages, displays, or pages from the system 100A-D.
The modem/transceiver 244 may couple, in a well-known manner, the device 230 to a user device to enable communication with the CPU 232. In an embodiment, the modem/transceiver 244 may be a wireless modem or other communication device that may enable communication with a user device. The CPU 232 via the server 254 or application 252 resident on a user device may direct communication between modem 244 and a user device.
The ROM 236 may store program instructions to be executed by the CPU 232, server 254, or application module 252. The RAM 234 may be used to store temporary program information, queues, databases, and overhead information. The storage device 238 may comprise any convenient form of data storage and may be used to store temporary program information, queues, databases, and overhead information.
Such embodiments of the inventive subject matter may be referred to herein individually or collectively by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept, if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In the foregoing Detailed Description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted to require more features than are expressly recited in each claim. Rather, inventive subject matter may be found in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
Number | Date | Country | |
---|---|---|---|
63087314 | Oct 2020 | US |