Printing may be performed using a printhead with nozzles through which printing liquid is emitted onto a substrate or medium. Nozzles may fail to operate, for example to due to clogging.
Example implementations are described below with reference to the accompanying drawings, in which;
Certain printing methods involve ejecting printing liquid from a series of nozzles onto a substrate to print an image/design.
Some printing applications involve printing on large amounts of material, in some cases in a short amount of time. Such printing operations may benefit from unattended printing wherein printing can take place without human oversight or intervention of the printing process. For example, in dye-sublimation printing, a single print job/run may involve printing on around 1000 linear metres of substrate. In such examples the user may wish to run the printer non-stop, ideally without supervision, while the print run takes place.
To improve print quality and reliability of running a print job; and reduce any need for user intervention or monitoring during printing, in particular for long print runs (e.g. several hours), systems and workflows may be used to improve media/substrate control, printing liquid//ink delivery control, carriage moment, and others. However, systems to monitor printhead heath are engaged outside printing time. For example, a drop detection routine, whereby nozzles of the printhead are tested to check whether they are emitting printing fluid correctly, or whether they are misfiring or blocked/clogged, may take place either before a print job/run (prior to any of the image being printed) or after a print job/run (after printing is completed and the whole image has been printed). As such, any nozzle failures which may affect print quality may be detected after a print run has finished. However, if the failure occurs during the print run, it may undesirably result in a visible print defect in the printed item.
Such drop detection routines (or other methods for checking nozzle operation) may be performed for all nozzles of a printhead, which takes an amount of time which is too long to feasibly allow such a drop detection (or similar) routine to be performed during a print run. For example, it may take around 80 seconds for a drop detection routine for all nozzles of a printhead, and adding this time to the print run time makes the overall time for the print run to complete impractically long. Further, drop detection routines may check nozzles and categorise each nozzle as either operational (firing, on) or not operational (missing, off) without any further or intermediate categorisation of the nozzles.
It may be desirable to monitor the health/operation of nozzles of a print head during a print run so that action may be taken to correct any errors in nozzle operation during the print run.
It may be desirable to perform such nozzle monitoring, and any subsequent error correction, in a way which does not take additional time over the time to perform the print run. It may be desirable to categorise nozzles in further categories to “on” or “off”, for example to allow for different ways of managing nozzle operation to achieve acceptable print quality.
Examples disclosed herein may allow for nozzle operation to be monitored during a print run without introducing delay. Examples disclosed herein may allow for nozzle operation to be categorised to allow for a reduction on the number of nozzles to be evaluated to ensure sufficient monitoring during a print run. Certain examples disclosed herein combine a grading algorithm (using a categorisation of nozzle health, to select a number of nozzles for monitoring less than the total number), and a control function to enable rapid nozzle monitoring during printing without introducing delays to the print flow. Nozzle monitoring may be performed, for example, by drop detection, or based on light emitting and light receiving components detecting the emission of printing fluid from the nozzle. Nozzle monitoring may also be done using other methods, such as using image patterns or determine whether nozzles are functioning.
The term “vulnerable nozzle” may be taken to mean a nozzle which is operational, i.e. is ejecting/performing the deposition of printing fluid to a satisfactory standard, i.e. it deposits printing fluid in a way which at least meets a printing quality threshold. However, the vulnerable nozzle also at least meets a threshold for expected printing error, i.e. it meets a failure likelihood criterion. Thus, if a vulnerable nozzle were to stop operating and become a non-functional nozzle, e.g. due to clogging of that nozzle, then the resulting print quality of the printed item would not meet an acceptable printing quality threshold. This may be because, for example, the vulnerable nozzle is immediately adjacent to a non-functioning nozzle—while the one non-functioning nozzle can be compensated for so the resulting printed item meets a quality criterion, if the vulnerable nozzle were also to fail, then the resulting printed item would be of lower print quality and thus not meet the quality criterion.
Since it is functional, but vulnerable nozzles, which are monitored by the online monitoring process disclosed herein, the nozzle map of vulnerable nozzles indicates nozzles that are printing properly, but which, if they fail, may cause an unacceptable print quality deterioration (e.g. such as a region of the substrate which should have printing liquid deposited thereon/therein, but which does not as the nozzles which should deposit printing liquid in that region are not operational nor compensated for by other operational nozzles). Other methods of checking print operation of printing nozzles may instead focus on nozzles which are “out”/non-functioning, which are weak (not enough printing liquid is being dispensed by the nozzle) or which are misdirected nozzles (the printing liquid emitted is not deposited in the desired region of the substrate)—that is, nozzles which are not operating satisfactorily.
Based on the vulnerable nozzle map, and during a print job and between successive print passes of the printhead, the method comprises checking operation of the one or more operational nozzles indicated on the vulnerable nozzle map 104. Checking operation of the vulnerable nozzles may comprise, for example, performing drop detection of the one or more operational nozzles indicated in the vulnerable nozzle map, and/or any suitable method for verifying that the vulnerable nozzles are satisfactorily operational.
Because the number of vulnerable nozzles may be less (in some examples, much less, e.g. less than 10%, or 5%, of all the nozzles) than the total number of nozzles of the printhead, it is possible to check the operation of those operational nozzles indicated on the vulnerable nozzle map during a print job and between successive print passes of the printhead without introducing delays in the print process compared to performing the same print job without any nozzle checks. That is, performing the print job including checking the operation of the one or more operational nozzles indicated on the vulnerable nozzle map takes substantially the same time as performing an equivalent print job performed without checking the operation of one or more operational nozzles. In other words, a print job to print a printed image which includes checking the operation of the nozzles indicated on the vulnerable nozzle map, between print passes of the print head during the print run, may take substantially the same time to complete as an equivalent print job producing an equivalent printed image performed without checking the operation of the one or more operational nozzles indicated on the vulnerable nozzle map as claimed.
In some examples, the method may comprise, following checking the operation of the one or more operational nozzles 104, identifying one or more further operational nozzles of the printhead which meet the failure likelihood criterion 106, and adding the further operational nozzles to the vulnerable nozzle map 106. That is, after a check of the vulnerable nozzles, one or more further nozzles may be identified as vulnerable and thus may be added to the vulnerable nozzle map to update the map (or in some examples create a new vulnerable nozzle map). One or more nozzles may be identified as vulnerable by, for example, identifying one or more nozzles indicated as vulnerable on the vulnerable nozzle map as non-functioning nozzles, and re-determining which nozzles of the printhead now qualify as meeting the failure likelihood criterion and are thus vulnerable, based on the newly identified, previously vulnerable yet operational, but now non-functioning, nozzles.
In some examples, the method may comprise re-determining an error-hiding algorithm based on the vulnerable nozzle map including the added further operational (but now vulnerable) nozzles 110. The error-hiding algorithm is to select nozzles, e.g. for use in printing, and/or for omission from use in printing, to provide a reduction of printing errors due to non-functional nozzles. For example, an error-hiding algorithm may replace a non-functional nozzle with a functional one by identifying that a functional nozzle passes over the empty space of the substrate which has been left by the non-functioning nozzle. A secondary printhead of the same colorant located in a different position of the carriage may then be instructed to fire (emit printing fluid) using its functional nozzle which overlaps with the space left by the non-functional nozzle. This may be either in the same print pass or a secondary print pass. This may be achieved by shifting the firing region of the printhead from one non-functional nozzle to another functional one, for example.
In
In this example, vulnerable nozzles 304 are those which, if they were to fail, may result in a visible fault to be present in a printed image (e.g. a space or gap in the printed image). In this example also; the vulnerable nozzles 304 are those which are immediately neighbouring a threshold number (in this example, two) of non-functional nozzles 306. That is, it may be said that the vulnerable nozzles 304 in this example are those operational nozzles which at least meet the failure likelihood criterion of 1) if the nozzle were to become non-operational, it would cause a visible fault in a printed image, and 2) the nozzle is immediately neighbouring a threshold number (two) of non-functional nozzles.
Such a nozzle map may be used to determine whether a nozzle is failing to operate at a rate above a threshold nozzle operation rate. If, for example, a nozzle fails more than a predetermined number of times in a row (e.g. three times in a row), and/or a predetermined number of times out of a set number of attempts (e.g. four failures from ten attempts), then that nozzle may be marked as vulnerable.
In some examples in which the printhead region varies for different vulnerable nozzle checks, checking the operational nozzles of one of the nozzle regions may comprise calculating a carriage stop position for the nozzle region at which the nozzle region is positioned to be checked. For example, the carriage stop position to check a magenta trench by e.g. drop detection by a drop detector sensor at one side of the substrate may be different to the carriage stop position to check a yellow, cyan or black trench by that drop detector sensor. Calculating the carriage stop position may comprise calculating the stop position of the carriage such that the nozzle region to be checked is aligned for operation with (e.g. on top of) the drop detector (or other detection element), and then executing the drop detection routine (or other testing routine) on that nozzle region.
In some examples, the number of nozzles which can be checked in-between immediately successive print passes 608 may not be the same as the number of vulnerable nozzles which are indicated in the vulnerable nozzle map 612. Thus in some examples, as shown in
If, on the other hand, the number of vulnerable nozzles 612 to be checked is less than the number per print pass of vulnerable nozzles 608 which can be checked, the method may check 708 a second number of one or more operational nozzles of the printhead identified as meeting a further failure likelihood criterion, which is lower than the failure likelihood criterion. For example, the first set of vulnerable nozzles may be categorised as vulnerable because they are operational but immediately neighbouring two non-functional nozzles. The second set of vulnerable nozzles which may be checked may then meet the lower failure likelihood criterion of neighbouring one non-functional nozzle. As another example, the first set of vulnerable nozzles may be categorised as vulnerable because they are operational but fewer than six out of ten times. The second set of vulnerable nozzles which may be checked may then meet the lower failure likelihood criterion of being operational but fewer than eight out of ten times. In this way, use is made of time available in-between two consecutive print passes to check nozzle operations by checking not only those nozzles identified as vulnerable 612 but also checking one or more other nozzles fulfilling a (different) vulnerability criterion.
The method 800 of
Checking operation of the nozzles of the printhead 802 may comprise, for example; determining one or more drop parameters for each checked nozzle. A drop parameter indicates a level of operability of the nozzle. The drop parameter may comprise, for example, one or more of: drop velocity (the velocity of the ink drop after being fired by the nozzle); fly time (which is a consequence of the drop velocity; and is the time between a nozzle firing a drop and the drop being detected on the drop detector); drop weight (the quantity of ink that forms the drop); drop size/drop volume (this parameter is relative to the drop weight, and may be evaluated by the signal interference that the drop generates on the drop detector signal); and drop trajectory (the direction in which ink is emitted; to check if a nozzle is misdirected or not).
The operation of the one or more operational nozzles indicated on the vulnerable nozzle map may be checked using a drop detection apparatus when the printhead is at a carriage stop position at a side of a print zone. This may be the case for the initial generation of the vulnerable nozzle map, a subsequent amendment of the vulnerable nozzle map, and/or between successive print passes when checking the vulnerable nozzles.
The state of the printing process is checked 910. If the process is prior to the print run, following generation of the initial vulnerable nozzle map/list 906, the useable delay between successive print runs may be calculated and the number of nozzles which may be checked in that time may be extracted 920, as discussed in relation to
If the process is during the print run, the operation of the one or more vulnerable nozzles identified in the vulnerable nozzle map/list is monitored 912, as described above e.g. through drop detection between successive print runs. If no (further) nozzles are identified as being non-functional/missing, then no changes are applied 914 and the process continues by monitoring the vulnerable nozzles 912. If a vulnerable nozzle is identified as being non-functional/missing/out, then in this example an error hiding algorithm is executed 916 to compensate for the non-functional nozzle to ensure an acceptable print quality is still achieved. A new nozzle ranking 918 is obtained, to specify which nozzles are to be operated and which nozzles are now considered to be vulnerable and are to be monitored 912, following execution of the error hiding algorithm 916. The process continues by checking the state 910 of the print run.
Also disclosed herein is an apparatus (e.g. the apparatus 1000 of
In some examples, as illustrated, the vulnerable nozzle map 1010 may be stored remotely from the controller 1012 (and/or apparatus 1000) and accessed by the controller 1012, for example over wired or wireless connection. In some examples, the apparatus 1000 comprises a storage medium 1004 on which the vulnerable nozzle map is stored. In either arrangement, the controller 1012 may, following the print pass and check of the operation of the one or more operational nozzles indicated on the vulnerable nozzle map 1010, identify one or more further operational nozzles which meet the failure likelihood criterion; update the vulnerable nozzle map 1010 to include the one or more identified further operational nozzles. The controller may store the updated vulnerable nozzle map on the storage medium 1012 (either which is part of the apparatus 1000 or in communication with and external to the apparatus 1000).
In some examples, when executed by a processor, the instructions stored on the medium 1100 are to cause the processor to 1012, during a print job, to provide a vulnerable nozzle map 1010 indicating one or more operational nozzles of a printhead identified as meeting a failure likelihood criterion; and between successive print passes of the print job, control a drop detection process to check operation of the one or more operational nozzles indicated on the vulnerable nozzle map.
The non-transitory computer readable storage medium may, in some examples, have executable instructions stored thereon which, when executed by a processor, cause the processor to: update the vulnerable nozzle map based on a change in operation of the one or more operational nozzles indicated on the vulnerable nozzle map; and re-determining an error-hiding algorithm based on the updated vulnerable nozzle map, the error-hiding algorithm to select printing nozzles to provide a reduction of printing errors due to non-functional nozzles.
In discussing “checking” the operation of nozzles in successive print passes, in some examples this may mean that checks are performed between immediately successive print passes (i.e. the printhead performs one print pass, then a check of the operation of vulnerable nozzles is performed, then the printhead performs a further print pass, and then a further check of the operation of (the same, or different) vulnerable nozzles is performed. In some examples this may mean that checks are performed between successive print passes but not as frequently as between every print pass. For example, the printhead may perform one print pass, then a second print pass, and then a check of the operation of vulnerable nozzles is performed, followed by a third and a fourth print pass, and then a further check of the operation of (the same, or different) vulnerable nozzles is performed (i.e. in this example a check of vulnerable nozzles is performed between each two immediately successive print passes). In other examples there may be a different number of print passes between vulnerable nozzle checks.
In some examples, the number of print passes between successive checks of the vulnerable nozzles may vary as the print job progresses; for example, as the print job progresses, the number of print passes between successive vulnerable nozzle checks may decrease (in other examples the number of print passes may increase, or may otherwise vary). In some examples, the frequency with which vulnerable nozzle checks are performed (i.e. the number of print passes taking place before a vulnerable nozzle check is performed) may vary depending on a printing factor, such as a quality of the image being printed (e.g. amount of ink to print a region of the image, saturation of the ink to be used in a region of the image) and/or an indication obtained from the vulnerable nozzle checks (for example, if the vulnerable nozzle checks identify an increasing number of vulnerable nozzles as the print job progresses, the frequency with which vulnerable nozzle checks are performed may also increase). Of course other variations on the frequency of vulnerable nozzle checks are possible.
Because the vulnerable nozzle monitoring is being executed during printing, with no throughput impact, the process can be done using a reduced amount of drop detection actions compared to monitoring routines which take place offline.
Throughout the description and claims of this specification, the words “comprise” and “contain” and variations of them mean “including but not limited to”, and they are not intended to (and do not) exclude other components, integers or elements, Throughout the description and claims of this specification, the singular encompasses the plural unless the context suggests otherwise. In particular, where the indefinite article is used, the specification is to be understood as contemplating plurality as well as singularity, unless the context suggests otherwise.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2020/041909 | 7/14/2020 | WO |