System and methods for reducing component wear in an imaging device

An imaging device having a controller, a print engine and a raster image processor including methods for reducing wear in one or more components of the imaging device, the raster image processor including instructions for receiving a print job, determining whether one or more function features in the imaging device is disabled prior processing the print job, adjusting a default printing performance of the imaging device upon a determination that the one or more function features in the imaging device is disabled, generating a rasterized image for each page of the print job following the adjusting, and sending each rasterized image to the print engine of the imaging device for printing, wherein the adjusting the printing performance of the imaging device reduces the component wear in the imaging device and extends an allowable life of the one or more imaging components.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is related to the U.S. patent application Ser. Nos. 15/825,659 and 15/825,210, both entitled “System and Methods for Reducing Component Wear in an Imaging Device,” and which are filed contemporaneously herewith and assigned to the assignee of the present application.

REFERENCE TO SEQUENTIAL LISTING, ETC.

BACKGROUND

1. Technical Field

The present invention relates to a system and methods for reducing component wear in imaging devices and, more particularly, to a system and methods for reducing component wear in an imaging device by adjusting the printing performance of the imaging device.

2. Description of the Related Art

Upon the completion of printing a print job, a print engine of an imaging device typically shuts down, stopping all motors and turning off high voltage supplies. When another print job is in the print queue after printing a print job, the print engine is restarted. The imaging device may be configured to start the print engine following the receipt of a print job in the imaging device. In addition, the print engine may be prevented from shutting down following the completion of a print job while another print job is being processed into a printable format by a raster image processor (RIP).

Since it is possible for the RIP to take time in generating a printable image for the print engine, the print engine may wait for a relatively long time for an image to be available prior to starting printing. There may be various reasons for the delay, such as, but not limited to, job complexity, job size, poor network quality or host communication, and/or formatting problems. In other scenarios, print data may be lacking or lost as the print job is transmitted over a network such that the print job will not be printed. As a consequence of the print engine operating while images are being generated by the RIP, excessive churn may be incurred in the imaging device, which wears out printing components and uses up supplies within the device faster. Technical support is often requested to change settings in the imaging device until a minimal amount of churn remains.

Accordingly, it is desirable to have a system and methods for reducing component wear in an imaging device. There also exists a need for automatically adjusting functions in the imaging device based on the detected churn and reducing the component wear.

SUMMARY

An imaging device and methods for reducing wear in one or more components of the imaging device are disclosed. The disclosed imaging device includes a controller having an associated memory, a raster image processor and a print engine.

In one example embodiment, the method includes receiving a print job, determining whether one or more function features in the imaging device is disabled prior processing the print job, adjusting a default printing performance of the imaging device upon a determination that the one or more function features in the imaging device is disabled, generating a rasterized image for each page of the print job following the adjusting, and sending each rasterized image to a print engine of the imaging device for printing, wherein the adjusting the printing performance of the imaging device reduces the component wear in the imaging device.

In another example embodiment, the method includes receiving a print job, determining whether a default printing performance of the imaging device needs to be adjusted based on a previous print job following receipt of the print job and upon a positive determination, disabling at least one of a set of functions performed in the imaging device for achieving the default printing performance, and sending a rasterized image corresponding to each page of the print job to a print engine of the imaging device for printing, wherein the disabling the at least one of the set of functions reduces the default printing performance of the imaging device and reducing the default printing performance results in a reduction of the wear on the one or more imaging components in the imaging device thus increasing an allowable life of the one or more imaging components.

The abovementioned methods may be performed by a raster image processor of the imaging device. Other embodiments, objects, features and advantages of the disclosure will become apparent to those skilled in the art from the detailed description, the accompanying drawings and the appended claims.

DETAILED DESCRIPTION OF THE DRAWINGS

It is to be understood that the disclosure is not limited to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The disclosure is capable of other example embodiments and of being practiced or of being carried out in various ways. For example, other example embodiments may incorporate structural, chronological, process, and other changes. Examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some example embodiments may be included or substituted for those of others. The scope of the disclosure encompasses the appended claims and all available equivalents. The following description is therefore, not to be taken in a limited sense, and the scope of the present disclosure is defined by the appended claims.

Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use herein of “including”, “comprising”, or “having” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Further, the use of the terms “a” and “an” herein do not denote a limitation of quantity but rather denote the presence of at least one of the referenced item.

In addition, it should be understood that example embodiments of the disclosure include both hardware and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware.

It will be further understood that each block of the diagrams, and combinations of blocks in the diagrams, respectively, may be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other data processing apparatus may create means for implementing the functionality of each block or combinations of blocks in the diagrams discussed in detail in the description below.

Accordingly, blocks of the diagrams support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the diagrams, and combinations of blocks in the diagrams, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

Disclosed is a system and different methods for reducing component wear in an imaging device. Since component wear is hastened by excess churn in the imaging device, methods for reducing component wear include methods for reducing excess churn in the imaging device. For purposes of the present disclosure, churn refers to the state of operating the imaging device with the motors running while utilizing imaging supplies having toner. An imaging supply (e.g., toner cartridge, imaging unit containing photoconductive members and toner development rollers) that is exposed to excessive churn may not meet an expected life goal due to print quality problems that occur because of the churn. In one example scenario, toner may be pressed through a nip and generate a charge. However, when toner is not transferred to a media sheet, it is recycled through the imaging supply and charged again. Following many cycles through the imaging supply, toner may heat up, deform, and may not charge properly, causing print quality problems. To reduce churn in the imaging device, a preset printing performance, which refers to a time-to first-print and a number of throughputs that the imaging device is capable of achieving, is thus reduced.

FIG. 1shows an imaging system100according to one example embodiment. Imaging system100includes a client device105and an imaging device110communicatively connected to each other through a network115. Client device105includes an imaging driver120and a memory125for storing a print job130having one or more pages130a-130n. Imaging device110includes a controller135having an associated memory140, a raster image processor (RIP)145, and a print engine150.

Client device105includes imaging driver120for allowing communications between client device105and imaging device110. Imaging driver120may be a printer/scanner driver software program for imaging device110. Client device105may be any computing device capable of generating a print job and may be, but is not limited to, a computer, smartphone, tablet, smartwatch, etc. One or more print jobs130may be created and stored in client device105. Each print job130may include one or more pages130a-130n, such as pages130a,130b,130c,130nas shown inFIG. 1, where n represents the total number of pages in the print job. It will also be appreciated by those skilled in the art that while one client device105and one imaging device110are shown inFIG. 1, multiple client devices105and/or multiple imaging devices110may be present in imaging system100and communicatively coupled via network115.

Imaging device110may be a single function printer or a multifunction machine (sometimes referred to as an all-in-one device) capable of printing, scanning, making copies, e-mailing and/or other functions. Imaging device110may be communicatively connected to client device105via a communications link such as network115. Network115may refer to any structure that facilitates electronic communication between multiple components and may operate using wired or wireless technology. Network115may include communications over the Internet. The communications link may be a standard communication protocol, such as, for example, universal serial bus (USB), Ethernet or IEEE 802.xx.

RIP145may be housed within imaging device110(seeFIG. 1). RIP145may be any raster image processor available or known at the time of filing the present application, for converting each print job page130ato130nof print job130to a rasterized image or other printable format. The conversion of each page130ato130nof print job130by RIP145results in generating a rasterized set of images160. Rasterized images160ato160n(shown as160a,160b,160cand160ninFIG. 1) correspond to individual pages130a,130b,130cand130n, respectively, of print job130. In some example embodiments, the resulting rasterized set of images160may be stored in memory140for later retrieval by controller104. In other example embodiments, rasterized images160a-160nmay each be directly sent to print engine150for printing without storing. While RIP145is depicted inFIG. 1as being part of imaging device110, RIP145may be a component of client device105in other example embodiments. In still other example embodiments, RIP145may be a component separate from client device105and imaging device110but communicatively connected to both client device105and imaging device110via network115.

Print engine150receives rasterized images160a-160nassociated with print job130from RIP145. As is known in the art, print engine150may include a motor, gears, and imaging supplies controlled by controller135and utilized for printing an image onto a media sheet passed through imaging device110.

In one example embodiment of processing print jobs, pages130a-130nof print job130may be transmitted from client device105to imaging device110through network115via imaging driver120. Additional information, such as, for example, the user's printing preferences or metadata relating to print job130may also be sent to imaging device110. RIP145then converts pages130a,130b, and130cto corresponding rasterized images160a,160b, and160c, respectively, and may store these images in memory140. For purposes of the present disclosure, a print command may be at least an instruction from RIP145to print engine150for print engine150to start printing. The print command indicates that at least one of rasterized images160a-160nis generated and ready for printing. The additional information indicated by a user of client device105or imaging device110as well as limitations relating to an imaging capability of imaging device110known to controller135are considered by controller135when printing images160a-160n.

In the present disclosure, imaging device110includes an Advanced Start (AS) function and a Smart Run-Out (SRO) function which, when both enabled, improves a printing performance of imaging device110. In one example embodiment, the AS and SRO functions are enabled to set a default printing performance of imaging device110. It is to be understood that while the AS and SRO functions are depicted inFIG. 1as blocks of instructions stored in memory140, the AS and/or SRO functions may be instructions stored in a storage medium remotely located from imaging device110and communicatively connected to imaging device110via controller135.

The AS function includes one or more instructions for sending a start command to print engine150upon receipt of a print job in RIP145. In doing so, print engine150is ready to print the images associated with the print job in time for the generation of images in RIP145to be complete. When enabled, the AS function pre-starts print engine150as RIP145generates images for each page of the received print job. In having print engine150fully powered on or before RIP145completely generates an image of the received print job, a printing performance of imaging device110is improved by specifically decreasing the amount of time it takes to produce a printed copy or the time to first print.

The SRO function may include a sequence of instructions for preventing print engine150from shutting down or turning off while a print job is still being processed by RIP106or upon determining that a new print job is received by RIP145. In some example embodiments, print engine150may include instructions for sending a request to RIP145for a status thereof (e.g., an SRO request) in order to determine whether or not RIP145is busy or not in processing print job130. When enabled, the SRO function helps improve the printing performance of imaging device110by increasing a throughput of print engine150.

Raster image processors in current image forming devices typically wait for one or more problems to be resolved prior to completing the printing operation which may contribute to the excessive churn. For example, RIP145may wait for print job130to be transmitted from client device105to imaging device110no matter the quality or condition of network115. In another example embodiment, RIP145may continue to generate images for each job page no matter how problematic the page is or the length of time spent on the image generation. Print engine150may also be warmed up longer while waiting for an image to be received from RIP145. Any of these aforementioned scenarios may not only cause the churn but also eventually contribute to causing wear and reducing the life of imaging components and/or supplies.

FIG. 2is a flowchart of one example method200of adjusting the printing performance of imaging device110ofFIG. 1based on a presence of excess churn. Example method200includes powering imaging device110to a full printing performance, detecting a slow image generation causing the excess churn, reducing the printing performance by disabling the AS and SRO functions, and enabling the AS and SRO functions when it has been determined that imaging device110has recovered from the slow image generation.

In one example embodiment, imaging device110may be powered on initially or from being not in use for over a period of time (also known as a “power on reset”). In other example embodiments, imaging device110may be in an idle state where imaging device110is waiting to receive a print job from client device105(also known as a “sleep” or “standby” mode).

At block205, following power on reset of imaging device110or receipt of a print job (in the context where imaging device110is in idle state), controller135may set the performance of imaging device110to full printing performance. In a full printing performance, both the AS and SRO functions are enabled in imaging device110in order to decrease the time to first print and to increase throughput of imaging device110.

At block210, either RIP145or print engine150may detect excess churn generally caused by slow image generation. Slow image generation may be caused by at least one of the following scenarios: (1) when RIP145detects problems in network115; (2) when RIP145processes a problematic print job and/or job page(s); and/or (3) when print engine150waits for a print job page image from RIP145(i.e., a job page image is not ready for printing onto a media sheet when print engine150is available and ready to print it). Problems of network115may include, but are not limited to, a low bandwidth or extreme traffic along the communication path, such as collisions, lost packets, etc. A problematic print job and/or job page(s) may refer to print jobs that are in a format which cannot be processed by RIP145or pages that may be too complex for RIP145to process. Print engine150may detect slow image generation when a job page image from RIP145associated with a print job is not ready in time for printing onto a media sheet by print engine150.

At block215, controller104reduces the printing performance of imaging device110to address the churn detected at block210. Reducing the printing performance of imaging device110includes disabling at least one of the AS and SRO functions in imaging device110. In one example embodiment, print engine150may not respond to (i.e., it may ignore) the AS command from RIP145. Alternatively or in addition, print engine150may not send the SRO request to RIP145. In a second example embodiment, RIP145may not send an AS command to print engine150. Alternatively or in addition, RIP145may indicate to print engine150of its “not busy” status or ignore an SRO request from print engine150.

As a result of disabling the AS function, imaging device110may incur a relatively slower time to first print than when print engine150automatically prints a print job once completed in RIP145. As a result of disabling the SRO function, the throughput of print engine150is also relatively less than when the SRO function is enabled because print engine150would be stopped and restarted every time following a print job.

At block220, RIP145or print engine150may then detect recovery of imaging device110from the churn detected at block210while imaging device110is operated at the reduced printing performance. Detecting recovery may include determining whether or not the churn detected from block210still exists following a predetermined number of print jobs or images being processed. Detecting recovery may further include determining whether or not adequate bandwidth is available in the communication path.

In one example embodiment where the churn is detected in RIP145, RIP145may include instructions to detect whether the communications link between imaging device110and network115is being utilized at full bandwidth and to determine whether problematic jobs still exist following the processing of a predetermined number of print job pages. In another example embodiment where the churn is detected in print engine150, print engine150may include instructions to determine whether or not, following the printing of a predetermined number of print job images, the print job images are received by print engine150from RIP145just in time, i.e., as soon as print engine150is ready for printing.

FIGS. 3A and 3Bshow a first example method300of the present disclosure where print engine150manages the excess churn.FIGS. 4A and 4Bshow a second example method400of the present disclosure where RIP145manages the excess churn. As is known in the art, processes performed by RIP145and by print engine150are separate complementary processes such that example methods300and400are each split into two parts:FIGS. 3A and 4Ainclude actions that are performed by RIP145whileFIGS. 3B and 4Binclude actions that are performed by print engine150in conjunction with the actions inFIGS. 3A and 4A, respectively. It will be appreciated that in the present disclosure the actions performed inFIG. 3Amay be performed simultaneously with the actions inFIG. 3Band that the actions performed inFIG. 4Amay be performed simultaneously with the actions inFIG. 4B.

Reference will now be made with respect to first example method300inFIGS. 3A and 3B. Example method300may include print engine150receiving the images from RIP145, detecting slow image generation causing the churn, and based on the slow image generation, disabling the AS function by not responding to or ignoring an AS command from RIP145(between blocks334and356ofFIG. 3B), disabling both AS and SRO functions when an image is not received within a predetermined timeout (block352,FIG. 4B), and disabling the SRO function by not sending an SRO request to RIP145(between blocks360and362,FIG. 3B). It will be noted thatFIG. 3Aincludes actions that are known in the field of generating images for print job pages.

Referring toFIG. 3A, imaging device110may initially be set in an idle state. In response to receipt by RIP145of a print job from client device105(block302), RIP145may send an AS command to print engine150at block304(print engine150may receive the same AS command at block332inFIG. 3B). At block306, RIP145sets a status thereof to “busy” as a consequence to receiving the print job. At block308, RIP145may generate an image corresponding to a first page of the print job. Then, at block310, RIP145may send the generated image to print engine150along with a print command. Print engine150then determines whether this same generated image is received from RIP145at block340inFIG. 3B.

Referring back toFIG. 3A, RIP145may then determine (at block312) whether or not the image generated at block308corresponds to a last page of the print job. At block314, if the image generated from block308does correspond to the last page of the print job, RIP145then clears its status and indicates to print engine150that RIP145is not busy processing any print job pages (the status being indicated as a response to an SRO request of print engine150at block336inFIG. 3B). Imaging device110may then return to idle state where RIP145is in standby mode for another print job. In the event that RIP145determines that the print job includes a subsequent page, RIP145generates an image corresponding to the subsequent page of the print job (returning to block308) and sends the generated image to print engine150(block310). Actions in blocks308and310are repeated for all other subsequent pages of the print job. When repeating actions in blocks308and310, the RIP state of RIP145is maintained as busy.

FIG. 3Bincludes blocks330-366that are performed by print engine150in conjunction with blocks302-314inFIG. 3Adescribed above. At block330, following a POR of imaging device110, print engine150may enable the AS and SRO functions. At block332, print engine150may receive an AS command from RIP145which is sent by RIP145at block304inFIG. 3A.

At block334, print engine150may determine whether or not the AS function is enabled in imaging device110. In one aspect, determining whether or not the AS function is enabled may depend on whether or not the AS function has been disabled while processing a previous print job prior to the transition of imaging device110to an idle state. At block336, upon a determination that the AS function is enabled, print engine150is powered up and, in particular, starts operating (i.e., transitions to a printing state). Then, at block338, print engine150waits for a job page image or any print-job related information from RIP145. Block338may be performed within a predetermined timeout such as, for example, 5 seconds. At block340, print engine150may determine whether or not a job page image is received from RIP145, as sent by RIP145at block310inFIG. 3A.

Still referring toFIG. 3B, upon receipt of an image from RIP145, print engine150may print the received job page image onto a corresponding media sheet at block348. At block350, print engine150then determines whether or not other job page images for printing exist and, if so, print engine150again performs block348where print engine150prints each of the other images received from RIP145onto corresponding media sheets, per blocks308and310inFIG. 3A.

Referring back to block334, upon a determination by print engine150that the AS function is not enabled, print engine150may not respond to the AS command sent by RIP145(per block304,FIG. 3A). Instead print engine150may proceed to block356where print engine150waits for a print command prior to starting up. In waiting for the print command, printing is held off and, with the printing time being dependent upon receipt of a print command, a time to first print in imaging device110may be increased.

At block340, in an example context where print engine150did not receive any job page image from RIP145following the predetermined timeout period, print engine150may disable the AS and SRO functions (block352). At block354, print engine150may be stopped following the processing of a first print job and imaging device110may be returned to the idle state. At block356, print engine150may wait for a print command prior to starting up (block358). When a job page image is in queue for printing, print engine150prints the job page image (block348) and determines whether or not all other images associated with the print job have been printed (block350). If other print job images have not been printed, print engine150prints each of the other images received from RIP145per blocks308and310inFIG. 3Aprior proceeding to block360inFIG. 3B.

At block360, when all the images that are queued for printing by print engine150have been printed, print engine150may then determine whether or not the SRO function is enabled in imaging device110. At block362, when the SRO function is determined to be disabled, print engine150may be stopped prior to setting imaging device110to an idle state, and an SRO request may not be sent from print engine150to RIP145. At block364, when the SRO function is determined to be enabled, print engine150may send an SRO request to RIP145to determine whether or not it should shut down following printing the print job. At block366, print engine150then determines whether or not RIP145is busy based upon a status set by RIP145at time when the SRO request is sent. Upon a determination that RIP145is busy processing images of the same print job or images of a new print job (based on blocks306to312inFIG. 3A), print engine150again performs blocks338to360. If, at block366, print engine150determines that RIP145is not busy or that a status thereof is clear (based on block314inFIG. 3A), then print engine150may inform controller135to set imaging device110to an idle state.

In one example embodiment, a counter value may be used as a basis is determining whether or not the AS and SRO functions are to be enabled following a period where a normal printing operation is observed while the AS and SRO functions are disabled. The counter value may be set to a first value (e.g., zero) following POR and to a second value every time the AS and SRO functions are disabled. The counter value may be regularly updated following every instance that an image is being processed by print engine150without any delay or drawback. In one example embodiment of the present disclosure, a counter value is set to the second value (i.e., predetermined MAX count) upon the detection of churn and is updated every time that an image is processed without any problems until the second value equals the first value.

In particular, and with reference to block352ofFIG. 3B, where the AS and SRO functions are disabled based upon the image being not received from RIP145within the predetermined timeout, print engine150may accordingly set the counter value to the second predetermined maximum value prior to stopping print engine150. At block342, the counter value may be decremented every time an image is received within the timeout until the second value is determined to reach its initial value (zero) following POR (see block330). At block344, print engine150may then determine whether or not the counter value reached the initial value following POR, and if so, at block346, print engine150re-enables the AS and SRO functions prior to printing the image (block348). Other alternative methods for tracking a number of times that an image is generated and/or received on time may be apparent to those skilled in the art.

Reference will now be made with respect to second example method400inFIGS. 4A and 4B. Example method400may include RIP145receiving a print job from client device105, detecting slow image generation causing the churn, and based on the slow image generation, disabling the AS function by not sending an AS command to print engine150(between blocks406and410ofFIG. 4A) and disabling the SRO function by indicating to print engine150that no jobs are being processed or ignoring an SRO request from print engine150(between blocks410and414ofFIG. 4A).

At block402, following a POR of imaging device110, RIP145may enable the AS and SRO functions. At block404, where imaging device110is powered on after being idle, RIP145may receive a print job from client device105. At block406, RIP145may determine whether or not the AS function is enabled based upon a presence of churn or a previous status of the function on imaging device110. At block408, upon a determination that the AS function is enabled, RIP145may send an AS command to print engine150for preparing print engine150for printing. (The same AS command is received by print engine150at block440ofFIG. 4B). Otherwise, upon a determination that the AS function is disabled, no AS command may be sent from RIP145to print engine150, and RIP145may proceed to performing block410following block406.

Continuing withFIG. 4A, following blocks406and408, RIP145may determine whether or not the SRO function is enabled at block410. At block412, if the SRO function is enabled, RIP145may set the status thereof as “busy” for print engine150to refer to when an SRO request is received by RIP145from print engine150(block460inFIG. 4B). Otherwise, when the SRO function is disabled, RIP145may either indicate in response to the SRO request of print engine150(block460ofFIG. 4B) that it is not busy processing any print jobs or ignore any SRO request from print engine150(also block460ofFIG. 4B) so as to cause print engine150to shut down following processing of the print job.

Referring back toFIG. 4A, following blocks410and412, at block414, RIP145generates an image corresponding to the first page of the print job. At block416, RIP145may determine whether the image is generated past a set time limit. If the image is generated past a set limit, RIP may disable the AS and SRO functions at block418. Additionally, at block418, RIP145may clear a status thereof and indicate this change in status when an SRO request is received from print engine150(also block460ofFIG. 4B). At block420, RIP145then sends the generated image to print engine150along with a print command for starting up.

Similar to at least blocks340,342, and344inFIG. 3B, a counter value may be used as a basis in determining whether or not to maintain the AS and SRO functions as disabled or have them enabled. Referring back to block416inFIG. 4A, upon a determination that the image is generated within the time limit, RIP145may decrement the counter value for tracking the instance when the image is generated within the time limit (block422). At block424, RIP145may determine whether or not the counter value reached the initial value (e.g., zero) set following POR. At block426, upon a determination that the counter value has reached the initial set value, RIP145may enable the AS and SRO functions and set a status thereof as busy for reference by print engine150when print engine150sends an SRO request (see block460ofFIG. 4B). Upon a determination that the counter value did not reach the initial value or following block426, RIP145may send the image generated from block414to print engine150along with a print command for printing the image (block420). This same image is received by print engine150in block448ofFIG. 4B.

Continuing withFIG. 4A, RIP145may determine (block428) whether or not the image generated at block414corresponds to a last page of the print job. If the image corresponds to the last page of the print job, RIP145may clear a status thereof prior returning imaging device110to an idle state at block430. This updated status of RIP150may be indicated to print engine150when an SRO request (per block460,FIG. 4B) is made. Otherwise, upon a determination that the print job includes additional pages, RIP145again performs blocks414to420until a last page of the print job is determined.

Reference is now made to blocks440-464inFIG. 4B, which are performed in conjunction with blocks402-430inFIG. 4A. It will be noted thatFIG. 4Bincludes actions that are known in the field of printing job page images.

At block440, where imaging device110is either initially powered on or powered on after being idle, print engine150may receive a print command or an AS command from RIP145. The AS command and the print command may be sent by RIP145at blocks408and420inFIG. 4A, respectively. At block442ofFIG. 4B, print engine150may then determine whether or not an AS command is received. At block444, upon a determination that an AS command is received, print engine150may start operating at a printing state. At block446, print engine150waits for an image generated by RIP145at block420inFIG. 4A. Similar to block338inFIG. 3B, block446inFIG. 4Bmay be performed within a predetermined timeout period. At block448, print engine150may determine whether or not a job page image is received and if so, prints the job page image (block450). Upon a determination at block448that the image is not received on time or that no image is received within the timeout period from RIP145, print engine150may be stopped (block454) and imaging device110may be set to an idle state. At block456, print engine150may be configured to wait for a print command (which may be from block420inFIG. 4A) prior to starting up (block458).

Following block450, at block452, print engine150may then determine whether the print queue is empty or whether more job page images are to be printed. At block460, upon a determination that the print queue is empty, print engine150may send an SRO request to RIP145. At block462, print engine150may determine whether or not RIP145is busy based on information received from the request sent at block460. Such information on the status of RIP145may be based on the actions in blocks412or430. When RIP145is busy processing other print job pages, print engine150may repeat the actions in blocks446to460. At block464, upon a determination that RIP145is not busy based on a status of RIP145when the SRO request is sent (block412or430inFIG. 4A), print engine150may be stopped, and imaging device110may be returned to idle state.

It will be appreciated that the actions described and shown in the example flowcharts may be carried out or performed in any suitable order. It will also be appreciated that not all of the actions described inFIGS. 2, 3A-3B, and 4A-4Bneed to be performed in accordance with the example embodiments and/or additional actions may be performed in accordance with other example embodiments of the disclosure.