In one embodiment there is a wireless reader 30 that can be carried by a person servicing a population of printers. The wireless reader 30 has at least two essential capabilities: to read machine-readable code (typically a bar-code, but any kind is possible) and wirelessly transmit data related to a code. The basic hardware platform of such a reader 30 can be a wireless bar-code scanner or a cell phone, such as with digital-camera hardware. In use, the code-reading portion of the device reads a machine-readable code associated with a quantity of media, such as on the packaging of a stack of paper 32. Data identifying the type of quantity of media is then transmitted to a central database, such as retained for a population of printers in server 18, in one of a number of ways. One way is for the reader 30 to contact server 18 through cell-phone channels; another is for the reader 30 to transmit the data through very short range radio signals to a receiver 34 on board the printer 12; the received data is then sent through network channels from printer 12 through network 14 to server 18. Other ways of getting data from reader 30 to server 18 will be apparent.
When a machine-readable code associated with a quantity of media 32 is loaded into a tray of a printer 12, the quantity of media 32 must in turn be associated in the database with a specific tray such as 16a, 16b, 16c. There are a number of possible approaches to accomplish this. In one method, incidental to transmitting data relating to the quantity of media 32, the reader 30 transmits data relating to the tray 16a, 16b, or 16c intended to receive the media. Each tray can have a machine-readable code 17a, 17b, or 17c, visible when the tray is open, that identifies the tray and the printer 12. When opening a tray such as 16a for loading, the user of reader 30 reads the code on media 32 and the code on tray 16a within a predetermined time-window, and then transmits data relating both codes to each other to server 18. Software associated with server 18 then identifies the media 32 with the tray 16a. (As shown in the Figure, two readers 30, one reading the stack of paper 32 and one reading the code 17a, are shown for clarity; in a practical embodiment, one reader 30 is used for both functions.)
Alternately, a user opens a particular tray such as 16a, thus activating sensor 20, which in turn indicates to a control system governing printer 12 that tray 16a is open. While the tray is open, the user uses reader 30 to read the code associated with media 32. A signal that tray 16a is open is sent to server 18 through network 14, and within a predetermined time window, the code for media 32 is sent to server 18 through whatever channel. Software associated with server 18 then identifies the media 32 with the tray 16a. There may also be ancillary data associated with the loading of the media in the tray, such as a date-time stamp and the identity of the person (identified as the holder of a particular reader 30, the reader 30 identifying itself to the database with each transmission of data) doing the loading: this ancillary data is also accumulated in the database.
Instead of using a wireless device such as 30, there may be provided, in effect “on-board” a printer 12, a code reader 36. In loading the printer 12, a user opens the desired tray such as 16a, indicating through sensor 20 that the tray is open, and then holds the code on media 32 to the code reader 36. Software associated with printer 12 and/or server 18 then identifies the media 32 with the tray 16a. In such a case, information about the date and time of the loading, as well the identity of the person doing the loading, can be entered via the UI 13 of the printer, or by other means.
Further according to this embodiment, once a quantity of media 32 is associated with a particular tray such as 16a in a particular printer 12 in the database in server 18, a service is provided to ensure that a “usual” type of media 32 is loaded in the tray. In practical use of large fleets of printers serviced by specialized personnel, the placement of the “wrong” type of media in a particular tray is a significant customer dissatisfier. The present disclosure thus provides an automatic check that correct or “usual” media has been loaded in a particular tray.
Within a database serving a population of printers, such as retained within a server 18, each tray of each printer is associated with at least one type of “usual” media. As used herein, “usual” means that the media has characteristics (brand, vendor, color, size, weight, finish, pre-printing, etc.) that are to some extent consistent with types of media that have been loaded into that particular tray in the recent past. The identity of types of media that have been loaded into the tray in the recent past is also retained in the database. The database may also include a table that associates each specific code, such as an SKU, as would possibly be read by reader 30 or code reader 36 with a set of characteristics. By associating each SKU with a set of characteristics, rules can be set up allowing substitutions of SKU's.
Since the database in server 18 keeps some kind of record of what type of media is “usual” for a given tray in a given printer, an algorithm is provided for deeming a media 32 proposed for loading into a particular tray to be “unusual.” “Unusual” can be defined in various ways, and an algorithm will reflect the definition; e.g., if the SKU of the proposed media is at all different from the previous media loaded into the tray; if the proposed media comes from a different vendor; if the proposed media is of different color; if the proposed media is of different size; if the proposed media is of different weight; or if the proposed media is of different finish, etc.
If the algorithm determines that a media 32 proposed for loading into the tray is “unusual,” a feedback of some kind to the user at the printer, or to a systems administrator associated with server 18, is initiated. Different types of feedback are possible depending on customer desires. Most simply, an “Are you sure?” pop-up can appear at the UI 13 associated with the printer 12, sending a message to the human user. A message can be sent wirelessly, from whatever source, to the reader 30, and the reader 30 could let out a sound and show a message to the user. Alternatively or in addition, the use of “unusual” media can be indicated to the systems administrator governing the population of printers, and approval from the systems administrator may be required (under penalty of, for instance, disabling the printer).
Information about media loaded into each tray in each printer over time can be retained in server 18 for statistical analysis, such as correlating with malfunctions, or flagging situations in which a particular printer 12 is overused (such as by noting a large number of reloads of a tray within a period of time). The database in server 18 can be used for re-ordering media from a vendor, facilitating asking the vendor to send more media (in proportions of sheet sizes, etc., as determined by past use) to the physical address of the particular printer.
In another embodiment, there is compiled via server 18 a master list of the descriptions of the contents of all trays in all machines accessible to any user on network 14. For various possible reasons, the “history” of what types of media have been loaded in any particular tray 16 in any printer 12 on the network in the past may be made available to any user associated with network 14.
The claims, as originally presented and as they may be amended, encompass variations, alternatives, modifications, improvements, equivalents, and substantial equivalents of the embodiments and teachings disclosed herein, including those that are presently unforeseen or unappreciated, and that, for example, may arise from applicants/patentees and others.
The following U.S. Patent is incorporated by reference in its entirety for the teachings therein: U.S. Pat. No. 6,647,222 B1.