The invention relates to the field of printing systems.
Businesses or other entities having a need for volume printing typically purchase a production printer. A production printer is a high-speed printer used for volume printing, such as 100 pages per minute or more. The production printers are typically continuous-form printers that print on paper or some other printable medium that is stored on large rolls.
A production printer typically includes a localized print controller that controls the overall operation of the printing system, a print engine (sometimes referred to as an “imaging engine” or as a “marking engine”), and a dryer. The print engine includes one or more printhead assemblies, with each assembly including a printhead controller and a printhead (or array of printheads). An individual printhead includes multiple tiny nozzles (e.g., 360 nozzles per printhead depending on resolution) that are operable to discharge ink as controlled by the printhead controller. The printhead array is formed from multiple printheads that are spaced in series along a particular width so that printing may occur across the width of the medium. The dryer is used to heat the medium and ink to dry the ink onto the medium.
For drop on demand print engines, drops of ink are ejected as needed to mark the medium with ink. During times of inactivity, ink within the nozzles of the print engine can begin to dry, which may clog or otherwise disturb the flow pattern when the nozzles resume ejecting ink drops. Thus, algorithms are designed to generate flush patterns to eject ink drops through the nozzles of the print engines to prevent this from occurring. This activity occurs during the actual job printing process, as nozzles may vary in activity during the printing process. The algorithms may utilize various criteria for generating flush patterns while printing the job, such as the amount of time one or more of the ink jet nozzles has been inactive, etc. The flush patterns may be printed onto non-used portions of the medium as a line or other pattern, or may be dispersed within portions of the medium that are marked based on print data for the job. However, it may not be desirable or possible to reserve blank portions of the medium for printing the flush patterns during printing of the job. Further, printing the flush pattern within the printed data for the job may reduce the quality of the printed output for the data.
Embodiments described herein provide for selectively removing flush drops from a plurality of ink drops ejected by a print engine when printing data for a print job. Flush patterns are merged with the print data for the job, and the merged data is utilized by the print engine during the printing process to eject ink drops towards a media. The flush drops that are the result of the flush pattern are then selectively removed from the ejected ink drops to prevent the flush drops from impinging or otherwise marking the medium during the printing process. The selective removal of the flush drops allows for a concurrent flush and print activity that eliminates the dispersal of flush drops within the printed data of the job. Further, the selective removal of the flush drops allows for a concurrent flush and print activity that eliminates the reservation of blank portions of the medium specifically for printing flush patterns. This improves the quality of the printed output for the job.
One embodiment is a control system of a printing system. The control system is operable to receive a flush pattern for flushing an ink jet print engine of the printing system. The control system is further operable to receive a sheetside bitmap for printing to a print medium, and to merge the flush pattern and the sheetside bitmap to generate a composite sheetside bitmap. The control system is further operable to direct the print engine to eject a plurality of ink drops toward the print medium based on the composite sheetside bitmap, and to identify a subset of the ink drops based on the flush pattern. The control system is further operable to direct a drop deflection system of the printing system to selectively prevent the subset of ink drops from impinging the print medium.
Another embodiment is a method for selectively removing flush drops from a plurality of ink drops ejected by a print engine when printing data for a print job. The method comprises receiving a flush pattern for flushing an ink jet print engine of a printing system, and receiving a sheetside bitmap for printing to a print medium. The method further comprises merging the flush pattern and the sheetside bitmap to generate a composite sheetside bitmap, and directing the print engine to eject a plurality of ink drops toward the print medium based on the composite sheetside bitmap. The method further comprises identifying a subset of the ink drops based on the flush pattern, and directing a drop deflection system of the printing system to selectively prevent the subset of ink drops from impinging the print medium.
Another embodiment is a non-transitory computer readable medium embodying programmed instructions executable by a processor of a printing system. The instructions direct the processor to receive a flush pattern for flushing an ink jet print engine of a printing system, and to receive a sheetside bitmap for printing to a print medium. The instructions further direct the processor to merge the flush pattern and the sheetside bitmap to generate a composite sheetside bitmap, and to direct the print engine to eject a plurality of ink drops toward the print medium based on the composite sheetside bitmap. The instructions further direct the processor to identify a subset of the ink drops based on the flush pattern, and to direct a drop deflection system of the printing system to selectively prevent the subset of ink drops from impinging the print medium.
Other exemplary embodiments may be described below.
Some embodiments of the present invention are now described, by way of example only, and with reference to the accompanying drawings. The same reference number represents the same element or the same type of element on all drawings.
The figures and the following description illustrate specific exemplary embodiments of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the invention and are included within the scope of the invention. Furthermore, any examples described herein are intended to aid in understanding the principles of the invention, and are to be construed as being without limitation to such specifically recited examples and conditions. As a result, the invention is not limited to the specific embodiments or examples described below, but by the claims and their equivalents.
One problem with prior printing systems, such as drop on demand printing systems, is that during times of inactivity the ink within the nozzles of the print engine can begin to dry. This may clog or otherwise disturb the flow pattern when the nozzles resume ejecting ink drops. In prior printing systems, flushing patterns are applied to a print engine to generate flush drops at the nozzles, which strike the print media either on non-printed portions of the print media or within areas of the printed portions of the media, neither of which is preferable.
In this embodiment, control system 102 has been enhanced to coordinate the selective removal of flush drops from a plurality of drops ejected during the process of printing data for a job. The flush drops in this embodiment are not ejected separately from the actual print data utilized in printing the job, but instead are merged within the print data for the job and are selectively removed as the merged print data is printed. Because the flush drops are prevented from striking the surface of media 114, the flush drops do not become part of the printed output of the print job, either as separate non-data regions that are reserved for the flush drops or as integrated within the print data for the job. This allows for a substantially concurrent flush and print process to occur, which improves the quality of the printed output for the job.
In general, control system 102 comprises any system, component, or device that is able to directly or indirectly prevent one or more ink drops 108-110 from impinging or otherwise marking media 114. Control system 102 may be included as part of a print controller (not shown) for printing system 110, as part of a printhead controller (also not shown) for print engine 104, or some combination thereof as a matter of design choice.
To coordinate the activity of removing the flush drops, control system 102 directs drop deflection system 112 to selectively deflect and/or prevent one or more of a plurality of ink drops 108-110 ejected by nozzles 106 from impinging media 114. In some embodiments, drop deflection system 112 may utilize air jets, vacuum, electrostatic fields, or some combination thereof to deflect one or more of ink drops 108-110 into a drop catcher (not shown), thus preventing the deflected drop from impinging or otherwise marking media 114. In other embodiments, drop deflection system 112 may utilize a high power laser to in effect, evaporate one or more of ink drops 108-110 thus preventing the evaporated drop(s) from impinging or otherwise marking media 114.
In general, drop deflection system 112 comprises any system, component, or device that is operable to prevent or more of ink drops 108-110 that have been ejected by nozzles 106 from impinging media 114.
Consider an example whereby a print operator is tasked with printing a job at printing system 100, which has been enhanced to selectively prevent flush drops that have been concurrently ejected along with data drops from impinging media 114. The print operator may specifically select printing system 100 based on the customer for the job and/or the specific characteristics of the job. For example, the customer may object to having flush patterns printed to regions on media 114 due to print quality concerns, or the job may be configured such that there are little or no non-printed regions that may be utilized for printing flush patterns. The print operator initiates printing of the job, which causes media 114 to traverse along the media path through printing system 100 in the direction indicated by the arrow in
In step 202, control system 102 receives a flush pattern for flushing print engine 104.
The flush pattern may be generated by a print controller, a print head controller, or some other system based on a flushing algorithm. The flushing algorithm may, for example, analyze the ink ejection activity of nozzles 106 of print engine 104, and generate a flushing pattern to flush ink drops from one or more nozzles 106. Generally, this flushing activity is performed while actively printing a job. Thus, it may not be sufficient to simply wait until the job is completely printed prior to flushing print engine 104.
In step 204, control system 102 receives sheetside bitmap for printing to media 114.
Generally, sheetside bitmaps are generated during the printing process for a print job. Sheetside bitmaps may include one or more logical pages, depending on the n-up configuration in the job. For example, in a 4-up printing configuration, logical pages for the job are rasterized (e.g., by a rasterizer or other system, not shown) and arranged 4 to a sheetside for printing to a printable medium. During the printing process, a plurality of sheetside bitmaps are assembled and provided to a marking engine, which marks the printable medium based on the sheetside bitmaps in order to print the job.
In step 206, control system 102 merges the flush pattern (e.g., flush pattern 302) and the sheetside bitmap (e.g., sheetside bitmap 402) to generate a composite sheetside bitmap.
In step 208, control system 102 directs print engine 104 to eject plurality of ink drops 108-110 towards media 114 based on the composite sheetside bitmap (e.g., composite sheetside bitmap 502). As discussed previously, ink for flush pattern data and ink for print data for a job are ejected substantially concurrently by print engine 104 during the flushing process for print engine 104. As the composite sheetside bitmap includes both the flush pattern and the sheetside bitmap data corresponding to a portion of print data for a job, ink drops 108-110 ejected by print engine 104 include both flush drops based on the flush pattern and ink drops based on the sheetside bitmap.
In step 210, control system 102 identifies a subset of ink drops 108-110 based on the flush pattern. Control system 102 may compare the flush pattern with the composite sheetside bitmap to in effect, identify which of ink drops 108-110 are flush drops. For example, control system 102 may identify drop 108 as a flush drop based on the flush pattern.
In step 210, control system 102 directs drop deflection system 112 to selectively prevent the subset of ink drops from impinging media 114. For instance, if control system 102 identifies drop 108 as a flush drop, then control system directs deflection system 112 to deflect, evaporate, etc., drop 108, thus preventing drop 108 from impinging or otherwise marking media 114. In some embodiments, control system 102 calculates a delay between directing print engine 104 to eject ink and a proximity of drops 108-110 to an active region of drop deflection system 112. For instance, drops 108-110 may be ejected at different velocities, etc., by print engine 104. Further, drop deflection system 112 may operate differently depending on the deflection methods. Laser ablation of one or more of ink drops 108-110 may be nearly instantaneous, while air, vacuum, or some other methods may be slower.
The invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In one embodiment, the invention is implemented in software, which includes but is not limited to firmware, resident software, microcode, etc.
Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium 706 providing program code for use by or in connection with a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium 706 can be any apparatus that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The medium 706 can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium 706 include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CD-ROM), compact disk-read/write (CD-R/W) and DVD.
A data processing system suitable for storing and/or executing program code will include one or more processors 702 coupled directly or indirectly to memory 708 through a system bus 710. The memory 708 can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code is retrieved from bulk storage during execution.
Input/output or I/O devices 704 (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers.
Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems, such a through host systems interfaces 712, or remote printers or storage devices through intervening private or public networks. Modems, cable modem and Ethernet cards are just a few of the currently available types of network adapters. Computing system 700 further includes print engine interfaces 714.
Although specific embodiments were described herein, the scope of the invention is not limited to those specific embodiments. The scope of the invention is defined by the following claims and any equivalents thereof.
Number | Name | Date | Kind |
---|---|---|---|
4175266 | Nakano et al. | Nov 1979 | A |
6808246 | Long | Oct 2004 | B2 |
7431420 | Inoue | Oct 2008 | B2 |
7543923 | McNestry | Jun 2009 | B2 |
7600852 | Brown et al. | Oct 2009 | B2 |
7621616 | Mitani et al. | Nov 2009 | B2 |
8070277 | Phillips et al. | Dec 2011 | B2 |
8128196 | Garbacz et al. | Mar 2012 | B2 |
8240813 | Lu et al. | Aug 2012 | B2 |
20060055747 | Steiner | Mar 2006 | A1 |
20100149238 | Garbacz et al. | Jun 2010 | A1 |
20120026225 | Mataki | Feb 2012 | A1 |
20120287196 | Boland et al. | Nov 2012 | A1 |
20120306971 | Kobashi et al. | Dec 2012 | A1 |
Entry |
---|
Brady, M.J., Kuhn, L., Lane, R. et al. (Sep. 1975). Self purging deflector gutter for ink jet arrays. IBM TDB. Retrieved from http://ip.com/IPCOM/000084148. |
Number | Date | Country | |
---|---|---|---|
20140240392 A1 | Aug 2014 | US |