The present invention relates to cash control safes, and more particularly to a method for cleaning components of a cash control safe.
Cash control safes include various components, such as for example, note acceptors (bill validators), coin hoppers (coin dispensing mechanisms), note dispensers, and coin sorting mechanisms that require periodic cleaning. A note acceptor includes sensors and drive wheels which accumulate dirt from paper dust, ink and dirt which adheres to the notes. This accumulation of dirt effects the proper operation of a note acceptor. Similarly, coin hoppers, note dispensers and coin sorters include sensors and other devices which fail when dirty.
A need has thus arisen for a method for cleaning components of a cash control safe to ensure reliable operation thereof.
In accordance with the present invention, a method for cleaning a cash interface device of a cash control safe is provided. A cash interface device cleaning frequency is established. The number of operations of the cash interface device is counted. Comparison between the counted number of operations of the device is made to the established cleaning frequency. A notice is provided to an operator when the counted number of operations of the device exceeds the established frequency indicating a need for a cleaning operation for the device.
For a more complete understanding of the present invention and for further advantages thereof, reference is now made to the following Description of the Preferred Embodiments taken in conjunction with the accompanying Drawings in which:
As used herein, the term “cash interface device” will include, but is not limited to, a note acceptor, bill validator, coin hopper, coin dispense mechanism, note dispenser or coin sorting mechanism. As used herein the term “operation” will refer to operation of a cash interface device, including, but not limited to, the acceptance of a note, dispensing of a coin, validating a bill, or sorting coins.
Referring to
The number of operations of cash interface devices 20 is counted and stored in a memory 22. Operators and users of safe 10 interface with central processing unit 12 utilizing, for example, a user interface 24 which may comprise, for example, a key pad or touch screen. User interface 24 also includes a display for displaying notices generated by central processing unit 12.
Central processing unit 12 in combination with memory 22, counts and stores the number of operations of a cash interface device associated with cash control safe 10.
Referring to
At step 32, a note counter is set to zero within memory 22. A user or operator logs onto cash control safe 10 at step 34. A note or bill is inserted into a note acceptor 14 of cash control safe 10 at step 36. The counter included within memory 22 is then incremented by one at step 38. A decision is then made at decision step 40 to determine if note insertion has been completed. If the decision is no, additional notes are inserted into note acceptor 14 at step 36 and the counter is incremented by one for each note inserted. At step 40, if the decision is yes, the flow returns to step 34.
After the note counter is set to zero, at step 32, the method waits for a manager or executive level log in at step 42. A decision is made at decision step 44 to determine if the note counter count of inserted notes is greater than the cleaning frequency count established at step 30. If the decision is not at decision step 44, the cash control safe 10 proceeds with other tasks at step 46.
If the note counter count exceeds the cleaning frequency, at decision step 44, a determination is made at decision step 48 to determine if the desired time interval since the last operator notification has been exceeded. If the decision at step 48 is no, the flow returns to step 46.
If the decision at decision step 48 is yes, a notification is generated by central processing unit 12 to notify the manager that the note acceptor 14 requires cleaning at step 50. This notification is provided to the manager via the display of interface 24.
At decision step 52, a decision is made by the manager whether to clean the note acceptor 14. If the decision is no, the flow returns to step 46. In this manner, the manager can defer cleaning the note acceptor until a later time. If the decision at decision step 52 is yes, the note acceptor 14 is enabled for cleaning at step 54. At step 54, instructions may be generated by central processing unit 12 and displayed to the manager via interface 24 as to the type of cleaning and the procedure for cleaning the note acceptor 14. At decision step 56, a decision is made as to whether the cleaning is complete. If the decision is no, the flow returns to step 54. If the decision is yes, the note counter within memory 22 is reset to zero at step 58 and the flow returns to step 46.
Other alterations and modifications of the invention will likewise become apparent to those of ordinary skill in the art upon reading the present disclosure, and it is intended that the scope of the invention disclosed herein be limited only by the broadest interpretation of the appended claims to which the inventors are legally entitled.
Number | Name | Date | Kind |
---|---|---|---|
4650980 | Mizutani | Mar 1987 | A |
5676456 | Sharp | Oct 1997 | A |
6736251 | Molbak | May 2004 | B2 |
6983880 | Graef et al. | Jan 2006 | B2 |
7131576 | Utz et al. | Nov 2006 | B2 |
7131580 | Molbak | Nov 2006 | B2 |
7140607 | Graef et al. | Nov 2006 | B2 |
7150392 | Utz et al. | Dec 2006 | B2 |
Number | Date | Country |
---|---|---|
02244296 | Sep 1990 | JP |