JPH0465260A - print control device - Google Patents

Abstract

PURPOSE:To perform process without an interruption of receiving printing data transmitted from external devices by a method wherein when printing process can not be executed because, for example, a printing data memory is full or printing paper is absent, the transmitted printing data are stored in memories. CONSTITUTION:The printing data transmitted from a host computer 201 are stored in a receiving buffer 101 of a printer, and then stored in a page buffer 102 in turn. Then, the printing data are read out from the page buffer 102 page by page by a printing data expansion device 103, and processed for printing. Even when printing process delays, the printing data are taken in the page buffer 101 until it becomes full, and after that, the printing data transmitted from the host computer 201 are taken in the receiving buffer 101 in the printer. Then, the printing data are stored in a printing data memory 106 of a secondary memory 203, and transferred from the secondary memory 203 to the page buffer 102 as soon as a region in the page buffer 102 becomes vacant.

Description

[Detailed description of the invention] [Industrial application field]

The present invention relates to a printing device that receives print data from an external device and prints the data.

[Conventional technology]

Conventional printers develop the contents of one page's worth of print data as a bitmap in the image memory based on the print data received from the host computer (character code, figure, image, designation of print position and size, etc.). , the result of development in the image memory is converted into a video signal and transferred to the printing mechanism section for printing. In such printers, when the memory for storing print data becomes full, data sent from the host computer is not accepted until the memory becomes free. This also applies when there is no paper or a paper jam occurs in the printer.

[Problem to be solved by the invention]

In such printers, when a large amount of print data is sent from the host computer, the print processing in the print mechanism cannot keep up with the data transfer speed from the host computer, and the memory that stores the print data becomes full. turn into. In such a case, the printer will not accept data sent from the host computer (
As a result, the waiting time of the host computer becomes long (resulting in a long wait time).Also, as mentioned above, when out of paper or paper jam occurs in the printer, the problem such as out of paper or paper jam can be detected by the operator. The printer will no longer accept data sent from the host computer until the printer is cleared. Therefore, if this situation occurs, the host computer will experience waiting time, which may even affect operator operations on the host computer. This also occurs when multiple host computers are connected to one printer.In other words, this printer
While printing data from a certain host computer is being processed, print processing from other host computers is not executed and is forced to wait. The present invention has been made in view of the above-mentioned conventional example, and when the printing process cannot be executed because the print data memory is full or there is no paper, for example, the transmitted print data is stored in the storage means. An object of the present invention is to provide a printing device that can perform processing without interrupting the transmission of print data from an external device. Another object of the present invention is to provide a printing device that can efficiently receive and print print data from a plurality of external devices.

[Means to solve the problem] In order to achieve the above object, the printing apparatus of the present invention has the following configuration. That is, A printing device that receives print data from an external device and prints it on a recording medium, the printer comprising: a developing unit that receives print data from the external device and develops it in a buffer; a determining means for determining whether or not the print data can be stored in the buffer; a storage means for storing the print data; and if the determining means determines that the print data cannot be stored, the received print data continues to be received from the external device; and control means for controlling data to be stored in the storage means. Still another invention is a printing device that is connected to a plurality of external devices, receives print data from the external devices, and prints, the printing device being provided corresponding to each of the plurality of external devices, and each of the external devices and a printing means that reads the print data from the storage means for each job and prints it. [Effect]

In the above configuration, it is determined whether the print data can be stored in the buffer based on the remaining capacity of the buffer for receiving print data from the external device, and if the print data cannot be stored, the data is received while continuing to receive the print data from the external device. The print data obtained is controlled to be stored in the storage means. According to another aspect of the invention, print data is stored for each job of each external device by a storage means provided corresponding to each of the plurality of external devices. The print data thus stored is read out and printed on a job-by-job basis.

【Example】

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. <Description of Printer (FIG. 1)> FIG. 1 is a block diagram showing a schematic functional configuration of the printer of this embodiment. In FIG. 1, 101 is a receiving buffer that receives print data (data such as character codes, figures, images, etc., data specifying print position, size, etc.) sent from the host computer, and - temporally... I remember. 10
A page buffer 2 is capable of storing at least one page of print data, for example, code information, and stores the print data until the print output is completed. A print data development unit 103 reads one page of print data from the print data stored in the page buffer 102 and develops it into bitmap information. Reference numeral 104 denotes an output unit which inputs the bitmap information from the print data development unit 103 and stores it on a recording medium such as a recording paper by the printing mechanism unit 204 (FIG. 2). Reference numeral 105 denotes a data writing unit that sequentially writes print data stored in the reception buffer 101 to a secondary storage device 203, which will be described later.
The print data is stored in the print data storage unit 106 (FIG. 2). 10
A print data storage unit 6 stores print data written by the data writing unit 105. 107 is a data reading unit that sequentially reads out the print data stored in the print data storage unit 106 and stores it in the page buffer 102; Next, FIG. 2 is a block diagram showing the general configuration of the printer of this embodiment and the connection with the host computer 201. In FIG. 2, 202, 203 and 204 represent the configuration of the printer in this embodiment, 202 represents a control unit of the printer, and 203 represents a secondary storage unit such as a hard disk built into this printer. Reference numeral 204 represents a printing mechanism unit for printing output that actually performs printing. A host computer 201 transfers various print data to this printer. FIG. 3 is a block diagram showing a schematic configuration of the printer control unit 202 shown in FIG. 2. As shown in FIG. 3014, a central processing unit (CP) that controls the entire printer.
In U), various controls are executed according to the control program stored in the program memory 302. A font memory 303 stores font information for developing character codes into bitmaps in correspondence with various character codes. A work memory 304 can temporarily store various data according to the operation of the CPU 301. Here, the reception buffer 101 shown in FIG. 1 is secured in this work memory 304. 305 represents a data input interface (I/F) circuit for connecting the host computer 201 and the control unit 202. 306 is a secondary storage unit 20 such as a hard disk, for example.
3 represents an interface (I/F) circuit for controlling. Reference numeral 308 denotes an image output memory which stores bitmap data for one page read out from the page buffer 102 and image data developed into a bitmap for output to the printing mechanism section 204. Reference numeral 309 denotes an output interface (I/F) circuit that connects the control section 202 and the printing mechanism section 204. 310 is an image signal generator, which is connected to the printing mechanism section 20.
In synchronization with the printing operation No. 4, data is read from the image output memory 308 and then a video signal for the printing mechanism unit 204 is generated. Further, 311 represents an internal bus that connects each memory or circuit to the central processing unit (CPU) 301. <Explanation of printer operation (Figures 4 to 6)> Next, the fourth
The outline of the operation of the printer of this embodiment will be explained with reference to FIGS. FIG. 4 is a conceptual diagram showing the operation of the printer of this embodiment in a normal state. That is, in a normal state, print data transmitted from the host computer 201 is taken into the reception buffer 101 of this printer and sequentially stored in the page buffer 102. Next, the print data development unit 103 reads one page of print data from the page buffer 102 and develops a bitmap in the image output memory 308 . 401 in FIG. 4 represents the concept of a bitmap developed in the image output memory 308 by the print data development section 103. The bitmap data developed in the image output memory 308 is transferred to the output unit 104 which actually performs printing output processing.
will be forwarded to. When the printing process for that page is thus completed, the data for the page that has been output is deleted from the page buffer 102. In the normal state, printing processing is performed by repeating this series of operations. Next, when there is no paper or a paper jam occurs during printing processing, print data is stored in the page buffer 102 until the page buffer 102 is full. Thereafter, as shown in FIG. 5, the print data sent from the host computer 201 is sent to the reception buffer 101 in the printer
Then, the data writing unit 105 stores the data in the print data storage unit 106 of the secondary storage unit 203. Furthermore, even in the normal state, the host computer 201
Even if the page buffer 102 becomes full, the data writing unit 105
The print data storage unit 10 in the secondary storage unit 203 is
Print data is stored in 6. Next, if the print output process is restarted from the above state by the operator's operation and the page buffer 102 becomes empty, the operation will be as shown in FIG. 6. In other words, if the page buffer 102 is full or the print mechanism unit 204 is unable to print, the print data stored in the secondary storage unit 203 is transferred to the secondary storage unit when these conditions are canceled. 203 and stored in the page buffer 102. Here, page buffer 10
One page worth of print data is taken out from No. 2 and developed into a bitmap in the image output memory 308. The image data developed in this way is the image data shown at 601 in FIG. The image data developed in the image output memory 308 is transferred to the output unit 104 as shown in FIG. The print data stored in the print data storage unit 106 of the secondary storage unit 203 is sequentially transferred from the secondary storage unit 203 to the page buffer 102 as soon as the page buffer 102 becomes empty.
will be forwarded to. At this time, the transferred print data in the secondary storage unit 203 is deleted from the print data storage unit 106. While print data exists in the print data storage unit 106 of the secondary storage unit 203, the print data transmitted from the host computer 201 is taken into the reception buffer 101 in this printer, and then converted into the data shown in FIG. Writing section 105
The print data storage unit 10 in the secondary storage unit 203 is
6. Next, all the print data in the secondary storage section 203 is transferred to the page buffer 102, and when the print data storage section 106 in the secondary storage section 203 becomes empty, the normal state shown in FIG. 4 is returned to. Here, using FIGS. 7 and 8, the secondary storage unit 203
This section explains how print data is stored in . FIG. 7 is a diagram for explaining the management of spool files of print data stored in the secondary storage unit 203. Here, the print data is stored in the print data storage unit 106 in the secondary storage unit 203 in print page units as shown at 704 . Hereinafter, such a file composed of a plurality of pages will be referred to as a spool file 703. In this way, the print data 704 for each page stored in the print data storage unit 106 is stored in the spool file management table 701.
Managed by. This spool file management table 701 itself is stored in the work memory 30 of the control unit 202.
It is placed at 4. Further, reference numeral 702 indicates a management record for the print data 704 for each member in the spool file management table 701. FIG. 8 shows the spool file management table 70 of FIG.
FIG. 1 is a diagram showing details of management in FIG. Here, FIG. 8 shows the spool file management table 70.
1 indicates that it is used cyclically, and to manage this, spool file management table 7 is used.
There is a registration pointer 801 that indicates which management record 702 of 01 has stored a spool file, and an output pointer 802 that indicates which management record 702's spool file 704 is to be output next. These two pointers 801 and 802 control the spool file management table 701 so that it can be used cyclically, and at the same time manage the spool file 703 based on each management record 702. Next, the present invention will be explained in detail according to the flowcharts of FIGS. 9 and 10. First, FIGS. 9A and 9B are flowcharts of printing processing in the normal state of the printer of this embodiment, which is the same processing as in the prior art. FIG. 9(A) shows the process of receiving print data from the host computer 201, in which the host computer 201 waits for the print data to be sent, receives the print data sent from the host computer 201, and then
The data is stored in the reception buffer 101 (step Sl). Next, the process advances to step S2, and in the page buffer 102,
Check whether there is enough space in the reception buffer 101 to store the received print data. If there is no space in the page buffer 102, wait in step S2 until there is space, and if there is space, proceed to step S3, and transfer the print data in the reception buffer 101 to page buffer]0.
Transfer within 2 days. Then, the next host computer 20
Step S1 to receive the transmitted print data from S1.
Return to FIG. 9(B) is a flowchart showing print output processing in this printer. First, in step S4, wait until one page's worth of print data is stored in the page buffer 102, and when it is stored, take out one page's worth of print data from the page buffer,
Using the print data expansion unit 103, the image output memory 3
Expand the bitmap in 08. Next, the process proceeds to step S5, where the output unit 10 performs actual printing output processing on the bitmap data developed in the image output memory 308.
Transfer to 4. Finally, in step S6, the print data that has been output is deleted from the page buffer 102, and the process returns to step S4 for processing the next page. <Control operation in the printer of this embodiment> Fig. 10 (A
)(B) is a flowchart showing control in the printer of this embodiment. FIG. 10(A) shows print data stored in a spool file 70.
FIG. 10B shows the operation of reading print data from the spool file 703 into the page buffer 102. In FIG. 10A, first, in step Sll, the CPU 20 waits for print data to be transmitted from the host computer 201, and stores the print data transmitted from the host computer 201 in the reception buffer 101. Next step S12
Proceed to spool file 703 in secondary storage unit 203
Check whether print data is already stored in . If print data is stored in the spool file 703 in the secondary storage unit 203, the process advances to step S15. On the other hand, the spool file 7 in the secondary storage unit 203
If print data is not stored in 03, step 3
13, it is checked whether the page buffer 102 has enough free space to store the print data received in the reception buffer 101. If there is no empty area, the process proceeds to step S15, but if there is an empty area in the page buffer 102, the process proceeds to step S14, and the print data in the reception buffer 101 is transferred into the page buffer 102. Then, the process returns to step Sll in order to receive the next transmitted print data from the host computer 201. On the other hand, in step S15, it is checked whether the spool file management table 701 is full or whether the spool file 703 itself in the secondary storage unit 203 is physically full. If it is full, the spool file management table 70
Data reception from the host computer 201 is stopped until there is space in 1 and the spool file 703 itself, and if the cause of the stop is the spool file management table is full, the spool file is physically full until there is space in the table. In this case, wait until the spool file becomes free. In this way, if an empty area is generated, the process proceeds to step 816, and the print data received by the reception buffer 101 is stored in the spool file 703 of the 72nd storage unit 203 using the data writing unit 105. At this time, if the currently stored print data includes a page encode command such as form feed, the spool file management table 701 is updated at that point. That is, the registration pointer 801 is advanced by one, and the management record 702 of the new spool file management table 701 is associated with the print data storage area 704 of the new page of the spool file 703. And the host computer 20
Step Sl to receive the next print data from 1
Return to l. FIG. 10(B) is a flowchart showing the operation of reading print data from the spool file 703 in the secondary storage unit 203 to the page buffer 102. First, in step S21, it is checked whether print data exists in the spool file 703 of the secondary storage unit 203. If no print data exists in the spool file 703 of the secondary storage unit 203, no particular processing is performed. If print data exists in the spool file 703 of the secondary storage unit 203, the process advances to step S22, and it is checked whether the page buffer 102 is empty. Here, if there is no empty area in the page buffer 102, the process waits until an empty area occurs. Note that the printing operation by the printing mechanism unit 204 is continued during this time. When an empty area is generated in the page buffer 102 in this way, the process advances to step S23, where the data reading unit 107 is used to
2 by the amount corresponding to the empty area of the page buffer 102.
Print data is read from the spool file 703 in the next storage unit 203 into the page buffer 102 . Next, the amount of print data transferred from the spool file 703 in the secondary storage unit 203 to the page buffer 102 is deleted from the spool file 703. At this time, if the print data transferred this time includes a page end code command such as form feed, the spool file management table 701 is updated at that point. That is, the output pointer 802 is advanced by one, and the management record 702 of the spool file management table 701 is made unused. Then, the process returns to step S21 for the next process. In this embodiment, the print data is stored (spooled) as it is in the secondary storage unit 203, but in addition to this, the print data may be converted into a secondary intermediate code and stored in the secondary storage. 203, or 1
Another possible method is to develop a page's worth of print data into a bitmap and then store the bitmap data in the secondary storage unit 203. Further, in this embodiment, a hard disk is used as the secondary storage unit 203, but it goes without saying that the present invention can be implemented using readable and writable disks such as floppy disks and magneto-optical disks. Furthermore, in this embodiment, print data is stored in the secondary storage unit 203 when there is no paper, there is a paper jam, or the page buffer is full, but even under conditions other than the above, some operation operation or printing Of course, the present invention can also be applied when printing processing is interrupted due to processing. As explained above, according to this embodiment, when there is no paper, a paper jam, a page buffer full, etc., the print data sent from the host computer is temporarily stored in the attached memory, etc., so that the print data can be printed. Print data sent from the host computer can be received regardless of interruptions in paper conveyance in the mechanical unit or delays in printing speed. <Other embodiments (Figs. 11 to 19)> Fig. 11 is a block diagram showing a schematic configuration of a printer according to another embodiment, and parts common to the printer of the first embodiment described above are designated by the same symbols. , and their explanation will be omitted. 1018 to 101c are reception buffers provided corresponding to host computers 201a to 201C, which will be described later, respectively. The print data stored in these reception buffers are stored in the print data storage section 106a of the secondary storage section 203, respectively. Further, 107 is a data reading unit that reads out print data stored in the print data storage unit 106a on a job-by-job basis and writes it into the page buffer 102. FIG. 12 is a diagram showing the connection between the host computers 201a to 201c and the printer 210 of the embodiment and the flow of print data. Each of 211 to 213 indicates an example of output for each job transmitted and printed from each host computer. FIG. 13 is a block diagram showing a schematic configuration of a printer according to another embodiment and a connection with a host computer. In the figure, 221 is a control unit for controlling the entire blink, and 203 is a secondary storage unit such as a hard disk built into this printer. FIG. 14 is a block diagram showing a schematic configuration of the control unit 221 of the printer of another embodiment, and parts common to the control unit 202 of the printer of the first embodiment shown in FIG. 3 are indicated by the same symbols. . 301 is a CPU for controlling the entire control section 221 according to a control program stored in the program memory 302a. Each of 305a to 305G is an input interface (I/F) circuit provided corresponding to each of the host computers 2018 to 201c. FIG. 15 is a diagram illustrating spooling (storage, management, and reading of print data) of print data received from a host computer. Print data received from each host computer is stored in the reception buffers 101a to 101c, and then written to the secondary storage unit 203 by the data writing unit 105. Here, print data for each host computer written to the secondary storage unit 203 is stored in a spool file 501 that corresponds one-to-one with each host computer, as shown by 501a to 501c. When a job end command is sent from the host computer 201 with the print data stored in the spool file 501 in this way, the data reading unit 107 reads out the corresponding print data from the spool file 501 in the secondary storage unit 203. be done. Reference numeral 502 represents a bitmap image read out in this manner and subjected to bitmap development by the print data development unit 103. In this case, when the process of reading print data from the spool file 501 corresponding to a certain host computer, developing it into a bitmap, and printing it starts, the print process of other spools is not executed until the printing of this job unit is completed. I have to. This guarantees print output for each job. FIG. 16 is a diagram showing an example of the format of print data transferred from each host computer to this printer. This print data is shown in the case of N pages of print data sandwiched between a job start command 601 and a job end command 603. These N par 2 print data are stored in a spool file corresponding to the host computer. When the job end command 603 is received, it is known that the transmission of print data for one job from the host computer has been completed. This will cause this printer to start printing this job and
Print processing for other spool files will not be executed until the printing processing for the previous spool file is completed. FIG. 17(A) is a diagram for explaining the management of spool files, and FIG. 17(B) is a diagram showing the data structure of management information 711. As shown in FIG. 17, all spool files 501a~
There is a management table 710 for managing 501c,
Management information 711a-711c is provided corresponding to each of the spool files 501a-501c. This management information 711 is composed of a receiving flag 721 and the number of stored jobs 722.Receiving flag 72
1 is a flag indicating that print data is being spooled for each job. Further, the number of stored jobs 722 is a counter indicating how many job units of print data are stored in the spool file corresponding to this management information. Therefore, the spool file 501 corresponding to the spool file management information 711 in which the value of the number of stored jobs 722 is not "O" becomes the output target file to be printed next. <Explanation of Operation of Printer of Other Embodiments> FIG. 18 is a flowchart showing a procedure for spooling (storing) print information transmitted from a host computer. A control program for executing this process is stored in the program memory 302a. ing. First, in step S31, in order to sequentially check the data from the plurality of connected host computers 201, a serial number is given to the host computer for convenience, and the number is set to "1".In step S32, the number Post computer corresponding to “l” (e.g. 201
Check whether there is a print data transmission request from a). If there is no transmission request from the host computer, the process proceeds to step S36, but if there is a transmission request, step S36 follows.
The process proceeds to step 33, where data reception processing from the host computer is performed and the received data is stored in the reception buffer (for example, 101a). Next, the process advances to step S34, where the data is written to the corresponding spool file (for example, 501a) in the secondary storage unit 203. Then, in step S35, the management information 711 of the management table 710 for this spool file is updated. This process will be described in detail later with reference to FIG. 18(B). In step S36, it is checked whether the check up to the final host computer has been completed. If not, the process advances to step S37, where the serial number for checking the host computer is incremented by 1, and the process returns to step S32. On the other hand, when the check up to the final host computer is completed, the process returns to step S31 again to check whether there is data from the host computer with number "1" and execute the above-mentioned processing. Next, with reference to FIG. 18(B), the updating process of the spool file management table 710 in step S35 of FIG. 18(A) will be described. First, in step S38, it is checked whether the print data written to the spool file 501 includes a job end command. If it is included, the process advances to step S39, and the file management table 710 corresponding to the spool file is
The number of stored jobs 722 in the management information 711 is increased by 1. Next, the process advances to step S40, and it is checked whether the print data in the reception buffer 101 written to the secondary storage unit 203 this time has ended prematurely. If the process ends halfway, the process advances to step S41, and the receiving flag 721 of the spool file management information 711 is turned on. This indicates that this spool file is in the middle of being stored. If the print data is not finished halfway, step S4
2, the receiving flag 721 is turned off, and the update process is ended. In this way, a spool file corresponding to each host computer is created in the secondary storage unit 203, and the management table 710 is updated at the same time. FIG. 9 is a flowchart showing a process for printing print data stored in the spool file 501, and a control program for executing this process is stored in the program memory 302a. First, in step S51, in the same manner as step S31 in FIG. It is checked whether the number of stored jobs 722 of the spool management information 711 corresponding to the number is 1 or more, that is, whether any job corresponding to that host computer is stored. If a job is stored, the process advances to step 353; That one job is read from the spool file, expanded into a bitmap by the print data expansion unit 103, and printed.When the printing process for one job is thus completed, the process advances to step S54, and the number of stored jobs 72 of the management information 711 is
Subtract 2 by 1. In step S55, it is checked whether the spool files for all connected host computers have been checked. If all the checks have not been completed, the process advances to step S56, where the host computer number is incremented by 1 and the process advances to step S52, where the next Proceed to process the spool file corresponding to the host computer. When the check of the spool file corresponding to the final host computer is completed, the process advances to step S51, returns to step S51 again, returns the host computer number to 1'', and executes the same process again. Now, step S52 to step S5
In the printing process in step 4, the jobs stored corresponding to each host computer are printed one by one. For example, when the number of jobs corresponding to the host computer 201a is "3", this host computer computer 2
After printing all three jobs in the spool file corresponding to 01a, print to the next host computer (for example, 201
The process may proceed to b). In addition, in this embodiment, any spool file 5
The number of stored jobs in the management information 711 corresponding to 01 is °'1
If the number of stored jobs 722 in the management information 711 for all spool files 501 is "0°°", then the receiving flag 7
It is also possible to search for a spool file 501 with 21 turned on and print the print data already stored in the spool file 501. This makes it possible to further increase the printing speed of print data received from the postcomputer. However, in this case, there is a problem in that printing processing for spooled files corresponding to other host computers cannot be executed until printing processing for that spooled file is completed. As explained above, according to this embodiment, by spooling (storing) print data sent from each host computer in the secondary storage unit etc. of each host computer, print data sent from a plurality of host computers can be stored. Print data can be efficiently printed. [Effects of the Invention] As explained above, according to the present invention, when the print process cannot be executed because the print data memory is full or there is no paper, for example, the print data can be efficiently printed. By storing the transmitted print data in the storage means, processing can be performed without interrupting the transmission of print data from external devices. This has the effect of efficiently receiving print data.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the general functional configuration of the printer of the first embodiment, FIG. 2 is a diagram showing the configuration of the printer of the first embodiment and its connection to a host computer, and FIG. 3 is a block diagram showing the schematic functional configuration of the printer of the first embodiment. 4, 5, and 6 are diagrams showing the flow of print data in the printer of the first embodiment. FIG. FIG. 8 is a diagram for explaining the management method of the spool file storing print data in the printer of the embodiment. FIG. 8 is a diagram for explaining the management of the spool file management table in FIG. 7. FIGS. 9 and 10 11 is a block diagram showing a schematic functional configuration of the printer of the second embodiment. FIG. A diagram for explaining the concept of print output corresponding to each host computer in the second embodiment, FIG. 13 is a diagram showing the configuration of the printer and the connection with the host computer in the second embodiment, and FIG. FIG. 15 is a block diagram showing the configuration of the control unit of the printer of the second embodiment; FIG. 15 is a diagram showing the flow of print data in the printer of the second embodiment; FIG. 16 is a diagram showing the flow of print data sent to the printer of the second embodiment. Figure 17 (A) is a diagram showing the structure of the spool management table and the relationship between the spool files, and Figure 17 (B) is the data structure of spool management information. FIG. 18 is a flow chart showing the storage process of print data from the host computer in the printer of the second embodiment, and FIG. 19 is a flow chart showing the print process in the printer of the second embodiment. In the figure, 101, 101a, 101b, 101c...reception buffer, 102...page buffer, 103...
・Print data development section, 104... Output section, 105...
- Data writing section, 106, 106a... Print data storage section, 107... Data reading section, 201, 201a,
201b, 201c... host computer, 202
...Control unit, 203...Secondary storage unit, 204...
Printing mechanism section, 301-CPU, 302, 302a...
・Program ROM, 308...Memory for image output,
501... Spool file, 701... Management table, 702... Management information, 710... Spool file management table, 711... Spool management information. Patent applicant Canon Co., Ltd. agent Patent attorney Yasunori Otsuka (and 1 other person) - Figure 2 Figure Figure Figure Figure (A) Figure (B) Figure 10 (B) Figure 12 Figure 16 Figure 15 Figure 17 (A) Figure 17 (B) Figure 18 (B)

Claims (3)

[Claims] (1) A printing device that receives print data from an external device and prints it on a recording medium, comprising: a developing unit that receives print data from the external device and develops it in a buffer; and based on the remaining amount of the buffer. a determining unit for determining whether the print data can be stored in the buffer; a storage unit for storing the print data; if the determining unit determines that the print data cannot be stored, continuing reception from the external device; A printing apparatus comprising: a control means for controlling the received print data to be stored in the storage means. (2) A printing device that receives print data from an external device and prints it on a recording medium, comprising: a determining unit that determines whether the print data can be printed; a storage unit that stores the print data; and the determining unit. A printing apparatus comprising: control means for controlling the printing data to continue receiving from the external device and storing the received print data in the storage means when it is determined by the means that the data cannot be stored. (3) A printing device that is connected to a plurality of external devices, receives print data from the external devices, and prints, and is provided corresponding to each of the plurality of external devices, and is provided for each job of each external device. A printing apparatus comprising: storage means for storing print data in the storage means; and printing means for reading print data for each job from the storage means and printing it.