JP2023050596A - printer - Google Patents

Abstract

To provide a technique to increase the likelihood that a printer capable of collate printing can continue processing without making a memory become full even when performing collate printing of image data having a large number of pages.SOLUTION: A printer 1 memorizes obtained raster data in raster areas 40 of a memory 12, and after printing, erases the raster data when not performing collate printing, and does not erase the raster data when performing collate printing. The printer 1, when there are no vacancies in the raster areas 40 at the time of memorizing the raster data subjected to collate printing, erases data corresponding to at least one page of the raster data memorized in the raster areas 40, and memorizes the raster data subjected to collate printing in an external memory 50. When printing an image of the raster data erased from the raster areas 40, the printer 1 reads out the raster data memorized in the external memory 50, memorizes the data in the raster area 40 and utilizes the data in printing.SELECTED DRAWING: Figure 8

Description

The technical field disclosed in this specification relates to a printer capable of collating printing based on image data for multiple pages.

2. Description of the Related Art Conventionally, printers capable of collating printing (or sorting printing or collating printing), which is collation printing based on image data of a plurality of pages, have been put into practical use. For example, in Japanese Patent Laid-Open No. 2002-100002, a printer capable of collate printing performs collate printing based on the intermediate data stored up to that point when the memory becomes full while developing intermediate data and storing it in the memory. After that, the printed intermediate data is erased from the memory, the remaining intermediate data is stored in the memory, and the processing is continued, thereby making it as close to collate printing as possible.

JP-A-11-170631

As disclosed in Japanese Patent Application Laid-Open No. 2002-200011, in the case of collate printing, the printer needs to store image data for a plurality of pages in a memory. In Japanese Patent Application Laid-Open No. 2004-100001, printing is started at the stage when the memory becomes full, thereby releasing the memory and continuing the process. does not become Therefore, there is room for improvement in processing for continuing collate printing.

This specification discloses a technique for a printer capable of collate printing, which increases the possibility of continuing processing without memory full even when performing collate printing for image data with a large number of pages. .

A printer designed to solve this problem is a printer having an internal memory, the printer acquires raster data representing an image to be printed, and stores the acquired raster data in an empty raster area. The raster data is data in raster format, the raster area is an area secured in the internal memory prior to storing the raster data, and the image to be printed may have a plurality of pages. Further, the printer reads the raster data stored in the raster area, prints an image indicated by the read raster data, and the printer is designated to print in collated units. If the raster data is not printed, it is deleted from the raster area after printing is completed. is used for printing the second and subsequent copies, and after printing of the designated number of copies is completed, the raster data is erased from the raster area, and the printer erases the raster data for which collation printing is specified. is stored, if there is no space in the raster area, at least one page of the raster data stored in the raster area is erased from the raster area, and the printer erases the acquired When the raster data specifies collation printing, the acquired raster data is stored in an external memory connected to the printer, and the printer prints the specified number of copies before printing is completed. When printing an image indicated by the raster data erased from the raster area, the raster data to be printed is read from the external memory and stored in the raster area, and the raster data read from the external memory is stored in the raster area. It is characterized by using data for printing.

The printer disclosed in this specification stores at least one page of raster data stored in the raster area if there is no space in the raster area when storing acquired raster data in collated printing. Clear to free up raster space. As a result, the raster data can be stored, and as a result, the printing process can be continued. Furthermore, in printing by collation, the printer stores the acquired raster data in the external memory, and reads out the raster data that has been erased from the raster area before the printing of the specified number of copies is completed, from the external memory. Use for printing. Therefore, it is possible to print even the image indicated by the erased raster data, increasing the possibility of completing the collation printing process.

A control method, a computer program, and a computer-readable storage medium storing the computer program for realizing the functions of the printer are also novel and useful.

According to the technology disclosed in this specification, even when a printer capable of collate printing performs collate printing for image data with a large number of pages, it is possible to continue processing without memory becoming full. technology that enhances performance.

1 is a block diagram showing a schematic configuration of a printer of this embodiment; FIG. FIG. 4 is an explanatory diagram showing an example of a print job; 4 is an explanatory diagram showing each part of the printer; FIG. 4 is a flowchart showing the procedure of data reception processing; 4 is a flowchart showing the procedure of normal print processing; 4 is a flowchart showing the procedure of engine control processing; 4 is a flow chart showing the procedure of print processing for the first copy. 7 is a flow chart showing a procedure of internal storage processing; FIG. 10 is an explanatory diagram showing an example of memory utilization when printing the first copy in collate printing; FIG. 10 is a flow chart showing the procedure of print processing for the second and subsequent copies; FIG. FIG. 10 is an explanatory diagram showing an example of memory utilization when printing the second and subsequent copies in collate printing; FIG. 10 is an explanatory diagram showing an example of memory utilization when printing the final copy in collate printing;

A printer according to the present embodiment will be described in detail below with reference to the accompanying drawings. This embodiment discloses a printer capable of collate printing.

The printer 1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12, as shown in FIG. The printer 1 also includes a user interface (hereinafter referred to as “user IF”) 13 , a communication interface (hereinafter referred to as “communication IF”) 14 , and a print engine 15 . properly connected.

The CPU 11 executes various processes according to programs read from the memory 12 and based on user's operations. Note that the controller 10 in FIG. 1 is a collective term for hardware and software used to control the printer 1 , and does not necessarily represent a single piece of hardware that actually exists in the printer 1 .

Various programs and various data are stored in the memory 12 of the printer 1 of this embodiment. In the memory 12, for example, when the printer 1 is activated, a raster area 40 and a reception buffer 60 are secured as shown in FIG. The memory 12 of this embodiment is a ROM, RAM, HDD, etc. built in the printer 1, and is an example of an internal memory. The memory 12 is also used as a work area when various processes are executed. A buffer provided in the CPU 11 is also an example of an internal memory. Details of programs and data stored in the memory 12, and buffers or areas for storing the data will be described later.

The user IF 13 is, for example, a touch panel, and includes hardware that displays a screen for informing the user of information and hardware that accepts user operations. The user IF 13 may be a combination of a display and operation buttons.

The communication IF 14 includes hardware for communicating with an external device such as a personal computer (hereinafter referred to as “PC”) 3 . The communication standard of the communication IF 14 is Ethernet (registered trademark), Wi-Fi (registered trademark), USB, or the like. The printer 1 may include multiple communication IFs 14 that support multiple communication standards.

The print engine 15 includes configuration for printing images on print media such as sheets. The image forming method of the print engine 15 is, for example, an electrophotographic method. The printer 1 of this embodiment may be capable of color printing, or may be configured to perform only monochrome printing.

A detachable external memory 50 is attached to the printer 1 of this embodiment. The external memory 50 is, for example, a storage medium such as a USB memory that is readable and writable by the CPU 11 . A computer-readable storage medium is a non-transitory medium. In addition to the above examples, non-transitory media include recording media such as CD-ROMs and DVD-ROMs. A non-transitory medium is also a tangible medium. On the other hand, an electrical signal that carries a program downloaded from a server on the Internet is a computer-readable signal medium, which is a kind of computer-readable medium, but is a non-transitory computer-readable storage. Not included in media.

For example, as shown in FIG. 1, the printer 1 of this embodiment is connected to the PC 3 and receives data such as print jobs from the PC 3 . PC3 is an example of an external device. The PC 3 has, for example, a printer driver 31 corresponding to the printer 1, as shown in FIG. The printer driver 31 is a program that generates a print job for causing the printer 1 to print based on a user's instruction. The PC 3 also has an application program for causing the printer 1 to print using the functions of the printer driver 31 .

For example, as shown in FIG. 2, a print job 200 generated by the printer driver 31 of the PC 3 and transferred to the printer 1 includes PJL data 201 and 203 indicating parameters related to printing, and print target data indicating an image to be printed. 202 and. Data to be printed by the printer 1 is not limited to a print job transmitted from the PC 3 or the like, and may be data obtained from a scanner, a cloud server, a USB memory, or the like.

The print target data 202 is, for example, GDI data. The GDI data is data in raster format, and can be used for printing by the print engine 15 as it is. The print target data 202 may be PDL data. PDL data is data in formats such as PCLXL and PDF, for example. PDL data is an example of image data. PDL data is data that is not in raster format. When receiving PDL data, the printer 1 rasterizes the PDL data to generate raster data so that the print engine 15 can use it for printing.

Next, operation of the printer 1 will be described. It should be noted that the following processing basically shows the processing of the CPU 11 according to the instructions described in the program. That is, the processes such as "judgment", "extraction", "selection", "calculation", "determination", "specification", "acquisition", "acceptance", "control", etc. in the following description are performed by the CPU 11. represent. Processing by the CPU also includes hardware control using the API of the OS. In this specification, the description of the OS is omitted and the operation of each program will be described. That is, in the following description, the description to the effect that "the program B controls the hardware C" may refer to "the program B controls the hardware C using the API of the OS". Also, the processing of the CPU 11 according to the instructions written in the program may be described with abbreviated words. For example, it may be described as "performed by the CPU 11". In addition, the processing of the CPU 11 according to the instructions described in the program may be described by abbreviating the CPU, such as "performed by the program A."

Note that "acquisition" is used as a concept that does not require a request. That is, the process of receiving data without the CPU 11 requesting it is also included in the concept of "the CPU acquires data." Also, "data" in this specification is represented by a computer-readable bit string. Data having substantially the same meaning and content but different formats are treated as the same data. The same applies to "information" in this specification. Further, "request" and "instruct" are concepts indicating outputting information indicating requesting or instructing to the other party. Also, information indicating a request or information indicating an instruction is simply referred to as a "request" or an "instruction."

Also, the process of judging by the CPU 11 whether or not the information A indicates that the matter B is conceptually described as "judging whether or not the information A is the matter B". There is The processing by the CPU 11 to determine whether information A indicates matter B or matter C is referred to as "judging whether information A is matter B or matter C". It may be described conceptually as

As shown in FIG. 3, the printer 1 of this embodiment has a plurality of components including a reception buffer control section 21, a rasterization section 22, a system memory management section 23, and an engine control section 24. FIG. The receive buffer control unit 21 controls the receive buffer 60 . The rasterization unit 22 executes rasterization processing. A system memory management unit 23 manages the memory 12 built in the printer 1 . The engine control section 24 controls the print engine 15 . Each configuration shown in FIG. 3 may be configured by software, may be configured by hardware, or may be configured by a combination of software and hardware. The processing of the CPU 11 described in each flowchart such as FIG. 4 to be described later includes processing by the plurality of configurations described above.

In the printer 1, a process of securing a predetermined memory area in the memory 12, a process of releasing the secured memory area, a process of writing data to the memory 12, a process of erasing data from the memory 12, and a process of reading data from the memory 12. is executed by making a request to the system memory management unit 23 . Note that the process of writing data to the memory 12 includes the process of overwriting the data in the memory 12 .

In response to the memory area reservation request, the system memory management unit 23 registers the requested size of memory as an area reserved for the requesting program. When the system memory management unit 23 registers the area as a reserved area and receives a data write request or a data erase request from the requesting program that requested the area to be reserved, the system memory management unit 23 responds to the request. It performs the processing according to the request, and does not execute the processing according to the request even if it receives a request from another program. Further, even if the system memory management unit 23 receives a request to secure a memory area, it does not further secure the already secured area as a secured area.

Further, when the requesting program that requested the allocation requests release of the memory area, the system memory management unit 23 releases the secured memory area. After releasing the memory area, the system memory management unit 23 uses the released area for writing data and securing the memory area.

When receiving a data write request, the system memory management unit 23 basically does not write data to an area in which other data has already been written. After erasing the written data, the system memory management unit 23 uses the area in which the erased data was stored for data writing. That is, the concept of data erasing processing by the system memory management unit 23 is to enable the area in which the data is stored to be used for writing other data. Note that when receiving a data overwrite request, the system memory management unit 23 writes the requested data even in an area in which data has already been written.

The procedure of data reception processing in the printer 1 of this embodiment will be described with reference to the flowchart of FIG. The data reception process is executed by the CPU 11 of the printer 1 when the printer 1 receives data from the PC 3 or the like via the communication IF 14 . The printer 1 temporarily stores the received data in the reception buffer 60 . The reception buffer 60 is an area of a predetermined size, and is reserved in the memory 12 when the printer 1 is activated.

In the printer 1 of this embodiment, the reception buffer control unit 21 stores the data received by the communication IF 14 in the reception buffer 60 . The CPU 11 acquires and analyzes data from the reception buffer 60 (S101), and determines whether or not it is a print job (S102). When determining that the received data is not a print job (S102: NO), the CPU 11 executes various processes based on the received data (S103), and ends the data reception process. Received data other than the print job includes, for example, data including an update command for updating the firmware of the printer 1 and a setting command for changing the settings of the printer 1 .

The CPU 11 manages how far the data in the reception buffer 60 has been read using a pointer (not shown). Therefore, the CPU 11 does not read the data once read from the reception buffer 60 again.

When determining that it is a print job (S102: YES), the CPU 11 generates a job ID (S111), associates it with the generated job ID, and registers the received print job in the job list.

Further, the CPU 11 determines whether the received print job is a collate print job (S112). Collate printing is a method of outputting by collation when forming a plurality of copies of a printed matter of a plurality of pages. For example, in the print job 200 shown in FIG. 2, the PJL data 201 includes a "SET QTY=3" command 210 indicating an instruction to print three copies of collate printing. A command 210 is an example of a command indicating collated printing.

If the CPU 11 determines that it is not collate printing (S112: NO), the CPU 11 executes normal printing processing (S121). A print job that is not collate printing is a job that prints one or more copies of each page to be printed in the order in which the data is received. The procedure of normal print processing will be described with reference to the flowchart of FIG.

In normal print processing, the CPU 11 acquires received data from the reception buffer 60 (S201), and determines whether or not the acquired data indicates the end of the data (S202). When determining that the end of the data is not reached (S202: NO), the CPU 11 generates a page ID (S211). A retention flag is associated with the page ID, and the CPU 11 sets off the retention flag associated with the generated page ID (S212).

The retention flag is information indicating whether or not to erase the raster data used for printing the page corresponding to the associated page ID after the printing is completed. If the hold flag is off, the printer 1 releases the raster area 40 storing the raster data for which printing has been completed in S306 of the engine control process, which will be described later. By releasing the raster area 40 after printing is complete, the printer 1 effectively erases the raster data stored in that raster area 40 . Since the raster data of the printed page is unnecessary in the normal print process, the printer 1 turns off the retention flag in S212.

After S212, the CPU 11 determines whether the acquired data is PDL data or GDI data (S214). When determining that the acquired data is GDI data (S214: GDI), the CPU 11 attempts to secure the raster area 40, and determines whether or not the raster area 40 has been successfully secured (S216). For example, the CPU 11 requests the system memory management unit 23 to secure a memory area for the raster area 40, and determines whether or not the system memory management unit 23 has notified that the request was successful. The raster area 40 is an area for storing acquired raster data.

If it is determined that the raster area 40 has not been successfully secured (S216: NO), the CPU 11 repeats the trial of securing the raster area 40 and the determination of whether the securing has succeeded. In normal print processing, since the raster area 40 is released after printing, the CPU 11 can secure the raster area 40 as the printing progresses. If the raster area 40 is successfully secured (S216: YES), the CPU 11 stores the acquired raster data in the secured raster area 40 (S218).

On the other hand, when determining that the acquired data is PDL data (S214: PDL), the CPU 11 rasterizes the PDL data (S215) to generate raster data. In S<b>215 , the CPU 11 performs rasterization by passing the PDL data to the rasterization unit 22 , for example. When the PDL data is acquired, the CPU 11 executes S216 to S218 with the raster data generated in S215 as data to be stored, and stores the generated raster data in the secured raster area 40 . Note that hereinafter, acquisition of raster data generated by rasterizing PDL data is simply described as acquisition of raster data.

Further, the CPU 11 stores the information of the raster area 40 storing the raster data and the ID of the page being processed in association with the job ID (S219). Then, the CPU 11 determines whether or not one page of raster data has been stored (S221). If one page is not stored (S221: NO), the CPU 11 returns to S214, continues to acquire raster data, and stores the acquired raster data. Note that the printer 1 acquires raster data in units of blocks of a predetermined size, for example, and secures and stores the raster area 40 in units of blocks. In this case, raster data for one page may consist of raster data for a plurality of blocks.

Note that the printer 1 may be configured to secure a predetermined number of raster areas 40 at the time of startup or the like. In this case, the CPU 11 may first determine in S216 whether or not there is a raster area 40 in which raster data is not yet stored. If there is a raster area 40 in which raster data is not yet stored, the CPU 11 proceeds to S218 and stores the acquired raster data in that raster area 40 . If the CPU 11 determines that there is no raster area 40 in which raster data is not yet stored, in S216, the CPU 11 may try to secure the raster area 40 and determine whether the allocation was successful. good.

After one page of raster data has been stored (S221: YES), the CPU 11 designates the page ID and notifies the engine control unit 24 that the raster data has been stored (S222). Note that the CPU 11 may notify the engine control unit 24 every time one block of raster data is stored, without being limited to the configuration in which the notification is made to the engine control unit 24 after one page of raster data is stored. .

Note that in the case of a print job for simply printing a plurality of copies instead of collate printing, the CPU 11 notifies S222 of normal print processing multiple times, and prints using the same raster data multiple times. In this case, the CPU 11 turns on the hold flag for the page until printing of the copy before the final copy is completed, and turns off the hold flag for the page after printing the copy before the final copy is completed.

Then, the CPU 11 returns to S201, further acquires the received data, and if the acquired data indicates the end of the data (S202: YES), ends the normal print processing and returns to the data reception processing. .

The engine control unit 24 executes the engine control process upon receiving the notification of the page ID in S222 or the like of the normal print process. The procedure of engine control processing will be described with reference to the flowchart of FIG. The engine control process is executed by the CPU 11 of the printer 1 .

In the engine control process, the CPU 11 reads raster data based on the notified page ID, and causes the engine control unit 24 to cause the print engine 15 to execute printing (S301). The CPU 11 waits until printing of the page is completed (S302: NO), that is, until a print completion notification is received from the print engine 15. FIG. The timing at which it is determined that printing of the page is completed is the timing at which the print engine 15 finishes using the raster data. The timing at which it is determined that printing is completed may be, for example, the timing at which the printed sheet is discharged from the printer 1 . The timing at which it is determined that printing is completed may be, for example, the timing at which the sheet is fed and the printing of that page is started.

When printing of the page is completed (S302: YES), the CPU 11 determines whether or not the retention flag for that page is off (S305). For example, in a print job that is not collate printing, the hold flag for each page is turned off in S212 of the normal print processing described above.

If the hold flag of the page to be printed is off (S305: YES), the CPU 11 releases the raster area 40 storing the raster data of the printed page (S306), and ends the engine control process. . Specifically, the engine control unit 24 requests the system memory management unit 23 to release the raster area 40 in which the corresponding raster data is stored. By releasing the raster area 40 , it becomes possible to write other data in the area used as the raster area 40 . That is, in effect, the raster data stored in the raster area 40 is erased. Erasure of data in this specification is a concept including de facto erasure of data by releasing a memory area in which data is stored.

If the retention flag of the page to be printed is ON (S305: NO), the CPU 11 does not release the raster area 40 and leaves the raster data in the memory 12, and terminates the engine control process.

Returning to the description of the data reception process in FIG. After the normal print process of S121, the CPU 11 erases the information of the finished print job from the job list (S141), and ends the data reception process.

On the other hand, when determining that the received print job is a print job for collate printing (S112: YES), the CPU 11 executes the printing process for the first copy (S131). The first copy print processing is processing for printing the first copy from the first page to the last page in the case of collate printing. Also, a print job to be processed in the first copy print process of the present embodiment is a print job including a command indicating collate printing, like the print job 200 shown in FIG.

The procedure for printing the first copy will be described with reference to the flowchart of FIG. In the description of the printing process for the first set and in FIG. 7, the same steps as in the normal printing process of FIG. 5 are given the same reference numerals to simplify the description.

In the first copy printing process, the CPU 11 sets the storage destination information to information indicating the memory 12, which is a memory built into the printer 1 (S401). The CPU 11 acquires the received data from the reception buffer 60 (S201), and determines whether or not the acquired data indicates the end of the data (S202). If it is not the end of the data (S202: NO), the CPU 11 generates a page ID (S211).

The CPU 11 determines whether the received data is PDL data or GDI data (S412). When determining that the received data is GDI data (S412: GDI), the CPU 11 determines whether or not one page of raster data has been acquired (S414). For example, when a page break command is received, the CPU 11 determines that one page of raster data has been obtained. When determining that one page of raster data has not been acquired (S414: NO), the CPU 11 returns to S412 and acquires further data.

On the other hand, when determining that the received data is PDL data (S412: PDL), the CPU 11 rasterizes the received PDL data (S413) to obtain raster data.

If it is determined that one page of raster data has been acquired (S414: YES), the CPU 11 determines that the save destination information is information indicating the memory 12 built into the printer 1 or information indicating the external memory 50. or (S421). When determining that the storage destination information is information indicating the memory 12 (S421: internal), the CPU 11 executes internal storage processing (S422).

The procedure of internal storage processing will be described with reference to the flowchart of FIG. In the description of the internal storage process and FIG. 8, the same steps as in the normal print process of FIG. 5 are given the same reference numerals to simplify the description.

In the internal storage process, the CPU 11 attempts to secure the raster area 40 capable of storing one page of raster data using the system memory management unit 23, and determines whether or not the raster area 40 has been successfully secured (S216). . Note that if there is a print job being executed before this print job, the raster area 40 used by the previous print job is released by completing the printing of the previous print job, and the raster area 40 is newly created. It may be possible to secure If the raster area 40 cannot be secured and the print job to be processed is not at the top of the job list, the CPU 11 may wait until it becomes the top.

If the raster area 40 has been successfully secured (S216: YES), the CPU 11 sets ON the retention flag associated with the generated page ID (S502). In collate printing, after printing all the pages of the first copy, the printer 1 prints the second and subsequent copies based on the raster data used for printing the first copy. Since the printer 1 does not read the data read from the reception buffer 60 again, the raster data used for printing the first copy is stored in the raster area 40 and reused. Therefore, in collate printing, the CPU 11 turns on the hold flag of each page so that the raster area 40 is not released by the engine control unit 24, that is, so that S306 of the engine control process is skipped.

Then, the CPU 11 stores the obtained raster data in the secured raster area 40 (S218). Further, the CPU 11 stores information such as the address and size of the raster area 40 storing the raster data and the ID of the page being processed in association with the job ID (S219). Further, the CPU 11 notifies the engine control unit 24 of the page ID of the page storing the raster data (S222), ends the internal storage process, and returns to the first copy printing process.

The engine control unit 24 receives the notification of the page ID and executes the engine control process shown in FIG. In the case of collate printing, since the hold flag of each page is turned on in S502, the engine control unit 24 does not release the raster area 40 even after printing is completed. That is, the raster data stored in the raster area 40 remains in the memory 12 even after the printing of the first copy is completed, and is reused for the printing of the second copy and thereafter.

Since the raster data remains in the memory 12 in collate printing, the secured raster area 40 gradually increases, and it is possible that the raster area 40 for storing newly acquired raster data cannot be secured. have a nature. When determining that the raster area 40 for storing the raster data could not be secured (S216: NO), the CPU 11 determines whether or not there is an empty area of a predetermined size in the external memory 50 (S511).

If the external memory 50 is not attached to the printer 1, or if it is determined that the attached external memory 50 does not have a sufficient size of free space (S511: NO), the CPU 11 notifies an error ( S512), the internal storage process is ended, and the process returns to the printing process for the first copy.

Raster data tends to be large in size, and storing a plurality of pages in the memory 12 tends to cause memory shortage. On the other hand, if the external memory 50, which has a larger capacity than the built-in memory 12, is attached, it is easy to hold raster data for a plurality of pages until printing of the specified number of copies is completed. In this specification, a case where an external memory 50 having a larger capacity than the memory 12 built into the printer 1 is installed will be described.

When determining that the external memory 50 has a free space (S511: YES), the CPU 11 changes the save destination information to information indicating the external memory 50 (S521). Furthermore, the CPU 11 copies all the raster data of this print job, which has been stored in the raster area 40 so far, to the external memory 50 (S522).

The printer 1 of this embodiment stores the raster data in the external memory 50 when the raster data for all pages cannot be stored in the raster area 40 . If raster data for all pages can be stored in the raster area 40 of the memory 12, collate printing is possible without using the external memory 50. FIG. In that case, the printer 1 omits storing raster data in the external memory 50, thereby reducing the control load. Note that the raster data stored until S216 of the internal storage process determines NO is all the raster data of the page for which the hold flag is turned on, and is stored in the raster area 40 without being erased. .

The CPU 11 then erases one page of raster data from the raster area 40 of the memory 12 (S523). For example, among the raster data stored in the memory 12, the CPU 11 selects the raster data of at least one page and the oldest stored raster data to be erased. Specifically, in S523, the CPU 11 requests the system memory management unit 23 to release the raster area 40 storing the raster data to be erased. That is, the CPU 11 tries to practically erase the raster data by releasing the raster area 40 .

Then, the CPU 11 attempts to secure the raster area 40 by the system memory management unit 23, and determines whether or not the raster area 40 has been successfully secured (S524). Specifically, the CPU 11 requests the system memory management unit 23 to secure a new raster area 40 in S524. If the CPU 11 determines that the raster area 40 has not been successfully secured (S524: NO), the CPU 11 further deletes one page of raster data. The CPU 11 repeats S523 and S524 until it succeeds in securing the raster area 40 having a size capable of storing the raster data of the page being processed.

In S<b>523 , for example, when page IDs having values that increase in the order of generation are generated, the CPU 11 deletes the raster data linked to the page ID with the smallest value. Alternatively, the raster area 40 may be provided with information indicating the time of storage, in which case the CPU 11 can identify the oldest raster data based on the provided information.

Note that the raster data to be erased in S523 is not limited to the oldest raster data, and may be any raster data for which printing of the first set has been completed. However, even with collate printing, printing is executed each time one page of raster data is stored. highly sexual. Therefore, if the oldest raster data is to be erased, there is a high possibility that the printing of the first copy can be properly completed.

When determining that the raster area 40 has been secured (S524: YES), the CPU 11 turns off the holding flag of the page being processed (S525). By turning off the hold flag, the raster area 40 is released in S306 of the engine control process after printing, as described above. Furthermore, the CPU 11 stores the obtained raster data in the secured raster area 40 and the external memory 50 (S526).

In S523 and S526, the CPU 11 may delete the raster data of the oldest stored article from the raster area 40, and store the newly acquired raster data in the raster area 40 where the raster data has been deleted. . Specifically, the raster area 40 in which the raster data to be erased is stored may be specified, and newly obtained raster data may be overwritten. For example, by requesting the system memory management unit 23, the raster area 40 storing the raster data to be erased may be overwritten with new raster data.

The printer 1 of this embodiment stores the received raster data in the raster area 40 and in the external memory 50 in parallel. As a result, after the raster data is stored in the external memory 50, it is possible to start storing the raster data in the raster area 40 earlier than when the raster data in the external memory 50 is stored in the raster area 40. . Therefore, it is more likely that processing of the print job can be completed early.

After storing the raster data, the CPU 11 proceeds to S219 and stores the page ID of the page in process, which is the page whose raster data is stored in the raster area 40, in association with the job ID (S219). Further, the CPU 11 notifies the engine control unit 24 of the page ID of the page being processed (S222), ends the internal storage process, and returns to the first copy print process. Since the retention flag is turned off, the engine control unit 24 releases the raster area 40 storing the raster data of this page after printing of this page is completed. As a result, a newly securable raster area 40 is created, and even if there is a next page in the print job being processed, the CPU 11 is highly likely to be able to secure the raster area 40 for the next page.

Returning to the description of the printing process for the first set in FIG. After the internal storage process of S422, the CPU 11 determines whether or not an error was reported in S512 of the internal storage process (S423). If it is determined that an error has been notified (S423: YES), that is, if there is no free space in either the memory 12 built into the printer 1 or the external memory 50, the CPU 11 cannot continue processing, so it cancels the print job. Cancel, end the printing process for the first set, and return to the data receiving process shown in FIG. In the data reception process, when the print job is canceled, the CPU 11 ends the process without performing subsequent processes.

If it is determined that an error has not been reported (S423: NO), the CPU 11 returns to S201 and further acquires data from the reception buffer 60. FIG.

On the other hand, when determining that the storage destination information has already become information indicating the external memory 50 (S421: external), the CPU 11 determines whether or not there is an empty area in the external memory 50 (S431). In S431, the CPU 11 determines whether or not the external memory 50 has a free area sufficient to store raster data for one page. If it is determined that there is not enough free space in the external memory 50 (S431: NO), the CPU 11 notifies an error indicating that the memory is full (S432), cancels the print job, and ends the printing process for the first copy. .

When determining that there is sufficient free space in the external memory 50 (S431: YES), the CPU 11 erases one page of raster data from the raster area 40 (S441). The CPU 11 uses the system memory management unit 23 to try to secure a raster area 40 having a size capable of storing the newly acquired raster data, and determines whether or not the securing has succeeded (S442). If it is determined that the reservation has not been successful (S442: NO), the CPU 11 sets another page of raster data to be erased. If it is determined that the raster area 40 has been secured (S442: YES), the CPU 11 turns off the holding flag of the page being processed (S212), and stores the acquired raster data in the raster area 40 and the external memory 50 ( S444). In S441 and S442, the CPU 11 attempts to release and secure the raster area 40 in the same manner as in S523 and S524 of the internal storage process described above.

Further, the CPU 11 stores the information of the raster area 40 storing the raster data and the page ID of the page being processed in association with the job ID (S219), and notifies the engine control unit 24 (S222). Since the retention flag is turned off, the engine control unit 24 releases the raster area 40 storing the raster data of this page after printing of this page is completed.

After S<b>222 , the CPU 11 returns to S<b>201 and further acquires data from the reception buffer 60 . Then, when it is determined that the acquired data is the end of the data (S202: YES), the CPU 11 ends the printing process for the first copy and returns to the data receiving process.

Next, a specific example of how the memory 12 and the external memory 50 are used when printing the first copy when a print job including GDI data specifying collate printing is received will be described with reference to FIG. . When the printer 1 receives a print job including GDI data, the printer 1 reads the GDI data stored in the reception buffer 60 to perform the process of acquiring the raster data in the flowchart described above. In the description of FIG. 9 and similar figures to be described later, the process described as "obtaining" in the flowchart will be described as "receiving".

9 and similar figures to be described later, it is assumed that the raster area 40 secured in the memory 12 is an area capable of storing raster data for 8 pages, and that the job to be processed is a 9-page job. do. It is also assumed that the external memory 50 has sufficient free space. Note that the numbers in each figure indicate the page of the raster data.

When the printer 1 analyzes the data received in the reception buffer 60 and determines that the print job is for collate printing (YES in S112 of the data reception process), the raster area 40 is displayed as shown in FIG. 9A. is secured, and the received raster data is stored in order from the first page in the secured raster area 40 . Further, the printer 1 turns on the retention flag of each page storing raster data (S502 and S218 of internal storage processing). Since the raster data is stored in the raster area 40, the printer 1 can print the first page (S222 of the internal storage process). In this example, raster data up to the eighth page can be stored in the raster area 40, so the printer 1 can print up to the eighth page.

When the printer 1 receives the raster data of the ninth page, as shown in FIG. 9B, the raster area 40 is in a state of no space (NO in S216 of the internal storage process). Therefore, as shown in FIG. 9C, the printer 1 first copies the raster data from the first page to the eighth page stored in the raster area 40 of the memory 12 to the external memory 50 (internal S522 of the saving process).

The printer 1 erases the raster data of the first page from the raster area 40 (S523 of the internal storage process), and stores the raster data of the ninth page in the raster area 40 that can be secured (S523 of the internal storage process). S526). The physical location of the raster area 40 that stores the raster data of the 9th page may be the same as or different from the location where the raster data of the 1st page was stored. Also, the printer 1 turns off the hold flag for the ninth page (S525 of the internal storage process). Further, the printer 1 also stores the raster data of the ninth page in the external memory 50 (S526 of internal storage processing).

As a result, as shown in FIG. 9D, the raster data of all pages are stored in the external memory 50, and the raster data of the 2nd to 8th pages and the raster data of the 9th page are stored in the raster area 40. It will be in a state where After printing the ninth page, the printer 1 releases the raster area 40 storing the raster data of the ninth page (S306 of the engine control process). This completes the printing of all pages of the first copy.

Returning to the description of the data reception process in FIG. After printing the first copy in S131, the CPU 11 decrements the number of copies specified by the collate printing instruction by 1 (S132), and executes the printing processing for the second and subsequent copies (S133). Information on the number of copies specified in the print job is stored in the memory 12 when it is determined that the received data is the print job. In S<b>132 , the CPU 11 updates the number of copies information stored in the memory 12 .

The printing process for the second and subsequent copies is a process for printing from the second copy up to the specified number of copies in the case of collate printing. The procedure of print processing for the second and subsequent copies will be described with reference to the flowchart of FIG. In the explanation of the printing process for the second copy and in FIG. 10, the same steps as in the normal printing process of FIG. 5 are given the same reference numerals to simplify the explanation.

In the printing process for the second and subsequent copies, the CPU 11 acquires the total number of pages of the current print job to be processed (S601). Since printing of all pages has been completed in the printing process for the first copy, the CPU 11 counts all the page IDs linked to the job ID, for example. Get the number of pages. Alternatively, the CPU 11 counts the number of pages each time a page ID is generated in S211 of the printing process for the first copy, and if YES is determined in S202, the counted number of pages is associated with the page ID. You can remember. Then, the CPU 11 determines whether or not the raster data of the target page is stored in the memory 12 in order from the first page (S602).

As described in the first copy printing process, in collate printing, when the raster area 40 is secured, the CPU 11 turns on the hold flag for that page so that the raster data is not erased. When it is determined that the raster data of the page to be processed is stored in the memory 12 (S602: YES), the CPU 11 notifies the page ID of the page to the engine control section 24 and causes printing to be executed (S222). The engine control unit 24 reads raster data from the raster area 40 based on the specified page ID, and causes the print engine 15 to print it.

On the other hand, if the raster area 40 cannot be secured in the printing process of the first copy, there is a possibility that the raster data of the page to be printed is not stored in the memory 12 . When determining that raster data is not stored (S602: NO), the CPU 11 newly generates a page ID (S211), and associates the generated page ID with the job ID of the print job to be processed. Further, the CPU 11 sets off the retention flag associated with the generated page ID (S212).

If the external memory 50 is installed, the external memory 50 stores raster data even for pages for which raster data is not stored in the memory 12 built into the printer 1 . In the printing process for the second and subsequent copies, a case where raster data is stored in the external memory 50 will be described. If the external memory 50 is not installed, or raster data is not stored in the installed external memory 50, and the CPU 11 determines NO in S602, an error occurs. Note that if there is a method for continuing printing without using the external memory 50, the CPU 11 does not have to make an error.

In order to use the raster data stored in the external memory 50, the CPU 11 attempts to secure the raster area 40 by the system memory management unit 23, and determines whether or not the raster area 40 has been successfully secured (S216). ).

In collate printing, since the holding flag of each page is turned on in S502 of the internal storage processing, even if the printing of the first copy is completed, the raster area 40 storing the raster data of each page is not released. . However, for the raster data newly stored in S526, the holding flag of the corresponding page is turned off in S525. That is, the raster area 40 for storing newly stored raster data is released in S306 of the engine control process when printing is completed. Therefore, in S216 of the printing process for the second and subsequent copies, the system memory management unit 23 attempts to secure the raster area 40 again, and there is a possibility that the released area can be secured as a new raster area 40. FIG.

If the raster area 40 has been successfully secured (S216: YES), the CPU 11 acquires the raster data of the target page from the external memory 50 and copies it to the secured raster area 40 (S618). Further, the CPU 11 stores the information of the raster area 40 storing the raster data and the ID of the page being processed in association with the job ID (S219). Raster data that has not been stored at the start of the printing process for the second and subsequent copies is data that is once stored in the memory 12 in the printing process for the first copy, and is erased after being used for printing. The CPU 11 notifies the page ID to the engine control unit 24 and causes printing to be executed (S222).

After S222, the CPU 11 determines whether printing of all pages of the second set has been completed (S631). For example, the CPU 11 counts the number of notifications to the engine control unit 24 in S222, and determines whether or not the number of notifications reaches the number of pages acquired in S601. If unprinted pages remain (S631: NO), the CPU 11 returns to S602 and causes the print engine 15 to print based on the stored raster data or the raster data copied from the external memory 50. .

When all pages of the second set have been printed (S631: YES), the CPU 11 subtracts 1 from the number of copies stored in the memory 12 (S632), and determines whether or not the remaining number of copies is 1. (S633). When determining that the number of remaining copies is not 1 (S633: NO), the CPU 11 determines whether or not the number of remaining copies is 0 (S634). If the number of remaining copies is neither 1 nor 0 (S634: NO), the CPU 11 returns to S602 and executes printing of the next copy in the same manner as the second copy.

When determining that the number of remaining copies is 1 (S633: YES), the CPU 11 turns off the retention flags of all pages linked to the job ID to be processed (S635), returns to S602, and finally to print one copy of As a result, after the printing of the last copy is completed, the engine control unit 24 releases the raster area 40 in which the raster data of each printed page is stored in S306 of the engine control process. .

When determining that the number of remaining copies is 0 (S634: YES), the CPU 11 ends the print processing for the second and subsequent copies, and returns to the data reception processing.

For example, after the printing of the first copy of the print job shown in FIG. 9 is completed, the printer 1 executes processing based on the printing process for the second and subsequent copies. Referring to FIG. 11, the usage status of the memory 12 when printing from the second copy to the last copy before the final copy in the printer 1 will be described.

At the start of the printing process for the second and subsequent copies, as shown in FIG. is stored in the external memory 50 .

In the printing process for the second and subsequent copies, the CPU 11 determines that the raster data for the first page is not stored in the memory 12 (NO in S602), and therefore executes S211 to S219. As shown in FIG. 11B, the printer 1 reads out the raster data of the first page from the external memory 50 and stores it in the raster area 40 (S618 for printing the second and subsequent copies). The printer 1 executes the printing of the first page (S222 of the printing process for the second and subsequent copies), and since the hold flag for the first page is off (S212 of the printing process of the second and subsequent copies), The raster area 40 storing the raster data of the first page is released (S306 of the engine control process).

Since the raster data of the 2nd to 8th pages have already been stored in the raster area 40 (YES in S602 of the printing process for the second and subsequent copies), the printer 1 performs the raster area 2 to 8 pages are printed based on the raster data stored in 40 (S222 of print processing for the second and subsequent copies). The hold flags of these pages are ON, and the printer 1 does not release the raster area 40 storing the raster data of the 2nd to 8th pages.

Since the raster data of the ninth page is not stored in the raster area 40, the printer 1 reads the raster data of the ninth page from the external memory 50 and stores it in the raster area 40 as shown in FIG. 11(D). (S618 if NO in S602 of print processing for the second and subsequent copies). The hold flag for the ninth page is off (S212 of the printing process for the second and subsequent copies). The printer 1 executes printing of the ninth page, and releases the raster area 40 storing the raster data of the ninth page when the printing is completed (S306 of the engine control process). state.

FIG. 11(E) is the same state as FIG. 11(A). Although omitted in FIGS. 11B to 11E, the raster data stored in the external memory 50 has not changed from the state shown in FIG. 11A. Then, the printer 1 repeats the processes of FIGS. 11A to 11E from the second set to the one set before the final set.

Next, the usage state of the memory 12 when printing the final copy of collate printing in the printer 1 will be described with reference to FIG. Before the final copy is printed, the hold flag of each page is turned off by S635 of the printing process for the second and subsequent copies.

When printing the final copy, the printer 1 reads out the raster data of the first page from the external memory 50 and stores it in the raster area 40 (S618 of the printing process for the second and subsequent copies) in the same way as the previous copy. Print the first page. Further, the printer 1 prints the 2nd to 8th pages based on the raster data of the 2nd to 8th pages stored in the raster area 40 . When printing the last copy, since the hold flags for pages 2 to 8 are turned off (S635 of the printing process for the second and subsequent copies), the printer 1, after printing each page of the last copy, The raster area 40 storing the raster data of that page is released (S306 of the engine control process).

Further, as shown in FIG. 12B, the printer 1 reads out the raster data of the ninth page from the external memory 50, stores it in the raster area 40, and executes printing (from S618 of the printing process for the second and subsequent copies). S222). The hold flag for the ninth page is off (S212 of the printing process for the second and subsequent copies), and the printer 1 releases the raster area 40 storing the raster data for the ninth page after printing the ninth page. (S306 of engine control processing).

Returning to the description of the data reception process in FIG. After the printing process for the second and subsequent copies in S133, the CPU 11 erases the raster data stored in the external memory 50 (S134). After printing the designated number of copies, the printer 1 erases all pages of raster data stored in the external memory 50 . As a result, as shown in FIG. 12C, neither the raster area 40 nor the external memory 50 stores raster data. The CPU 11 erases the information of the finished print job from the job list (S141), and finishes the data reception process.

As described in detail above, in collate printing, when the acquired raster data is stored in the printer 1 of the present embodiment, if the raster area 40 has no free space, at least one data stored in the raster area 40 is stored. Since the raster area 40 for storing raster data for a page is released and the raster area 40 is vacated, the raster data can be stored, and as a result, the printing process can be continued. Further, the printer 1 of this embodiment stores the acquired raster data in the external memory 50, and reads out from the external memory 50 the raster data that has been erased from the raster area 40 before printing of the specified number of copies is completed. used for printing. As a result, it is highly likely that the image indicated by the erased raster data can also be printed and the collate printing process can be completed.

Further, when the raster data stored in the raster area 40 is erased for collate printing, the printer 1 of the present embodiment has a hold flag for the page corresponding to the raster data stored in the raster area 40 that has been cleared by the erasure. turn off. If the raster area 40 is secured by erasing raster data, there is a high possibility that the raster area 40 will remain empty after that. Since the printer 1 of the present embodiment erases the raster data stored in the raster area 40 secured by erasing after printing is completed, the subsequent raster data can also be stored in the raster area 40 at an early stage.

Furthermore, when erasing the raster data stored in the raster area 40, the printer 1 of the present embodiment erases only one page first, and if it is still insufficient, erases another page. If a large amount of raster data is erased at once, the processing load for acquiring the erased raster data from the external memory 50 increases. Data can be reduced, and an increase in processing load is suppressed.

It should be noted that the present embodiment is merely an example, and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can naturally be improved and modified in various ways without departing from the gist thereof. For example, the printer 1 is not limited to a printer having a single printing function, and can be applied to any printer having a printing function such as a multifunction machine, a copier, a FAX machine, and the like. Also, the device that transmits the print job to the printer 1 is not limited to the PC 3, and may be a smart phone, a tablet computer, or a server computer. Also, the printer 1 may be connected to a plurality of PCs or the like.

Further, in this embodiment, when it is determined that raster data cannot be stored in the raster area 40 of the memory 12 built into the printer 1, the use of the external memory 50 is started, but the present invention is not limited to this. For example, if it is determined that the print job is for collate printing, the raster data of all pages are acquired and stored in the external memory 50 first, and then the raster data in the external memory 50 are sequentially read out and used for printing. good too. However, when the raster area 40 in the memory 12 built into the printer 1 runs out, the use of the external memory 50 is started, and thereafter the raster data in the reception buffer 60 is transferred to the raster data in the memory 12 built into the printer 1. Storing and printing in the area 40 and the external memory 50 increases the number of pages that can be printed without using the external memory 50, increasing the possibility of early completion of print job processing.

Further, in this embodiment, the print job including the command 210 is illustrated as the print job for collate printing, but the print job may be a print job including only raster data that does not include the PJL data 201 and 203 . For example, the printer 1 may be able to receive an instruction for the number of copies to be printed and an instruction for collate printing via the user IF 13 .

Also, in this embodiment, when the raster area 40 runs out, the raster data is erased one page at a time, and the raster area 40 vacated by erasing the raster data is reused in the processing of subsequent pages. , but not limited to this. For example, when the raster area 40 runs out, the number of remaining pages may be acquired from subsequent raster data, and the raster area 40 may be made available for the remaining number of pages.

Further, in any flowchart disclosed in the embodiments, multiple processes in any multiple steps can be arbitrarily changed in execution order or executed in parallel as long as there is no contradiction in the processing contents.

Also, the processing disclosed in the embodiments may be performed by a single CPU, multiple CPUs, hardware such as an ASIC, or a combination thereof. Further, the processes disclosed in the embodiments can be realized in various forms such as a recording medium recording a program for executing the processes, a method, and the like.

1 Printer 3 PC
12 memory 14 communication IF
50 external memory

Claims (11)

A printer comprising an internal memory,
The printer is
Obtaining raster data representing an image to be printed, storing the obtained raster data in an empty raster area, wherein the raster data is data in raster format, and the raster area stores the raster data. is an area secured in the internal memory prior to , and the image to be printed may have multiple pages,
Further, the printer
reading the raster data stored in the raster area, printing an image indicated by the read raster data;
Further, the printer
deleting the raster data for which collation printing is not specified from the raster area after printing is completed;
The raster data for which collation printing is specified is not deleted from the raster area even after the printing of the first copy is completed. After printing is completed, erase from the raster area,
Further, the printer
If there is no space in the raster area when storing the raster data for which collation printing is designated, at least one page of the raster data stored in the raster area is stored in the raster area. erase from
Further, the printer
storing the acquired raster data in an external memory connected to the printer, if collated printing is specified for the acquired raster data;
Further, the printer
reading the raster data to be printed from the external memory and storing it in the raster area when printing an image indicated by the raster data erased from the raster area before printing of a specified number of copies is completed; using the raster data read from the external memory for printing;
A printer characterized by: The printer of claim 1, wherein
The printer is
If a command indicating collation printing is given to the acquired raster data, collation printing is specified.
A printer characterized by: In the printer according to claim 1 or claim 2,
The printer is
At least one page of the raster data stored in the raster area is erased from the raster area when the raster area is full when the raster data for which collation printing is specified is stored. in this case, the raster data stored in the raster area due to the erasure is erased from the raster area after printing is completed;
A printer characterized by: In the printer according to any one of claims 1 to 3,
The printer is
when the raster data read from the external memory is used for printing, the read raster data is erased from the raster area after printing is completed;
A printer characterized by: In the printer according to any one of claims 1 to 4,
The printer is
If there is no space in the raster area when storing the raster data for which collation printing is designated, the timing of storing the raster data in the raster area among the raster data stored in the raster area. erases the oldest raster data from the raster area,
A printer characterized by: In the printer according to any one of claims 1 to 5,
The printer is
If there is no space in the raster area when storing the raster data for which collation printing is specified, one page of the raster data stored in the raster area is removed from the raster area. After that, if there is space for storing the raster data in the raster area, the raster data is stored in the raster area, and if there is no space for storing the raster data in the raster area, the raster area is stored. erasing from the raster area one page of the raster data stored in
A printer characterized by: In the printer according to any one of claims 1 to 6,
Equipped with a communication interface,
The printer is
obtaining the raster data by receiving the raster data transmitted from an external device via the communication interface;
A printer characterized by: A printer according to claim 7, wherein
The printer is
storing the received raster data in a reception buffer secured in the internal memory, storing the raster data from the reception buffer in the raster area;
Further, the printer
when collation printing is specified, storing the raster data stored in the reception buffer in the external memory in parallel with storing the raster data in the raster area;
A printer characterized by: In the printer according to any one of claims 1 to 6,
Equipped with a communication interface,
The printer is
receiving image data representing an image to be printed via the communication interface, and obtaining the raster data generated by rasterizing the received image data;
A printer characterized by: In the printer according to any one of claims 1 to 9,
The printer is
When the obtained raster data specifies printing in units of copies, if the raster data for all pages can be stored in the raster area, the raster data is not stored in the external memory, and all the raster data are stored in the external memory. if the raster data for a page cannot be stored in the raster area, storing the raster data for all pages in the external memory;
A printer characterized by: 11. The printer of claim 10, wherein
The printer is
if collation printing is designated for the obtained raster data, the raster data is not stored in the external memory while there is space for storing the raster data to be printed in the raster area; When the space for storing the raster data to be printed runs out in the raster area, the raster data to be printed and the raster data acquired earlier than the raster data to be printed are stored in the external memory. and further storing the raster data acquired after the raster data to be printed in the external memory.
A printer characterized by:

Images