JPH01171948A - Printer control apparatus - Google Patents

Abstract

PURPOSE:To prevent trouble in host equipment, by prohibiting the output of data into the host equipment when the data are analyzed again when a format mode is changed. CONSTITUTION:The data from a data processing device 1 are once stored in an external buffer 2 and outputted into a printer system 10. The printer system 10 comprises a video-map type data processing device 3, a printing engine 4, an external paper feeding unit 5, a sorter 6 and the like. In the data processing device 3, protocols for these devices are analyzed in addition to printing data. Instructions for the control of formats, paper feeding to the printing engine 4 as required, change in optional modes and the like are outputted. In the printing engine 4, control of an electronic photograph system associated with record control, timing control of recording paper and processing synchronized with the paper feeding in other optional modes are performed in addition to the record control. The output of the response data when the data are analyzed again is prohibited, and troubles in a host computer is prevented.

Description

DETAILED DESCRIPTION OF THE INVENTION (Field of Industrial Application) The present invention relates to a printer control device that prints data sent from a data processing device such as a host computer.

(Prior Art) Generally, data sent from a host computer or the like to a printer consists of print data indicating an actual print pattern and control data for controlling a printing method and mode of a print engine. A printer control device (hereinafter simply referred to as a controller) processes this data, converts it into a dot image to be actually printed, and supplies it to a print engine that performs printing.

(Problems to be solved by the invention) Conventionally, in printers that apply electrophotographic technology such as copiers and laser printers, troubles such as paper jams occur during printing operations, and problems such as paper jams or Some methods aim to improve throughput by re-analyzing the data received from the host when the direction (direction, etc.) is changed, but in this case, the data includes a protocol to output response data to the host. When re-analyzing, the response data is output to the host,
There was a problem that a problem occurred on the host side.

SUMMARY OF THE INVENTION An object of the present invention is to provide a printer control device that prevents data from being output to the host when reanalyzing data when the format mode is changed, thereby eliminating trouble on the host side.

(Means for Solving the Problems) A printer control device according to the present invention includes at least an input means for inputting print data and control data, a storage means for storing the input data from the input means, and an input means for storing the input data from the input means. an analysis means for analyzing data; a response output means for outputting response data according to the analysis result of the analysis means; a reanalysis means for reanalyzing the analyzed input data stored in the storage means; The present invention is characterized by comprising an output blocking means for blocking the output of the response outputting means while the reanalysis means is in operation.

(Function) Prohibits output of response data when reanalyzing data to prevent problems with the host computer.

(Example) Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

(a) Configuration of electrophotographic printer First, the general configuration of the printer and controller will be described.

FIG. 1 shows a printer system lO which is an embodiment of the present invention.
The configuration of the processing system is shown below.

In order to improve the throughput of the data processing device 1, data from the general-purpose data processing device 1 is temporarily stored in an external 7-aisle buffer 2, and then transferred to the printer system 1O.
is output to.

The printer system 10 includes a bitmap type data processing device 3, a print engine 4 using an electrophotographic process and a laser, and accessory devices such as an external paper feed unit 5 and a sorter 6.

FIG. 2 shows the appearance of the printer system IO. The print engine 4 incorporates the bitmap type data processing device 3, and can be connected to an external paper feed unit 5 and a sorter 6 as accessories. In addition, on the upper front side of the print engine 4, there is an operation panel 4 with a display showing the system status and keys for performing simple operations.
4 is installed.

FIG. 3 shows details of the operation panel 44. Here, 901 to 903 are input keys, and 910 to 91
8 is a display element. A key 901 is a PAUSE key for temporarily stopping the printing operation. key 903
is the TEST key for starting TEST print. Key 903 is a shift key, and by pressing it at the same time as key 902, you can select CANCEL to interrupt printing.
It becomes the key. The reason why the keys 902 and 903 are pressed at the same time to function is to prevent interruptions due to careless operations.

FIG. 4 is a central sectional view showing the paper passing path of the printing system, showing three removable paper feed cassettes (51, 52,
Paper is selectively fed from 53). After the toner is removed by the cleaner 406 in the print engine 4, the charger 404 and the eraser lamp 405
As a result, the photosensitive drum 401 is uniformly charged and receives image exposure from the optical system 409. And the developing device 402
A toner image is formed on the photoreceptor drum 401, transferred onto the paper fed by the transfer charger 403, conveyed to the paper fixing device 408 by the conveyor belt 407, and subjected to the fixing process by the fixing device 408. After that, it is stored in the sorter 6.

FIG. 5 is a schematic block diagram of printer system 10.

The bitmap type data processing device 3 includes a bitmap control unit (BMC) 30 and a bitmap R for bitmaps.
It consists of an AM (BM-RAM) 32, a bitmap writing section (BMW) 31 (see FIG. 7) which performs drawing on this BM-RAM 32, and a font section 33. Connection with the print engine 4 is made through a bus B3 for control data (number of sheets, accessory control, etc.) and a bus B4 for image data. The print engine 4 is mainly composed of three controllers. First, the interface control section (IF
C) 40 processes control data from the bitmap control section 30, controls the operation panel, and controls the overall timing of the print engine 4 via the internal bus B5. The electrophotographic control section 41 controls the electrophotographic processing section 45 in accordance with data sent from the interface control section 40 through the internal bus B5.

The print head control unit (PHC) 42 uses an internal bus B4.
In order to write the image data sent from the bitmap writing section 31 through the internal bus B5 onto the photoreceptor drum 401, the semiconductor laser of the print head section 43 emit light and the polygon Controls the rotation of a motor (not shown).

In addition, the external paper feed unit 5 and the sorter 6 are also connected to the internal bus B5.
It is controlled by the interface control section 40 through the interface control section 40.

The printer system IO described above is a bitmap type laser printer. The print data (mostly represented by a code) sent from the data processing device 1 is stored in the BM-RAM of the bitmap processing device 3.
32 as an actual print image, and output to the print engine 4. The print engine 4 modulates the laser beam according to the data from the bitmap data processing device 3, records the data on the photoreceptor, and further transfers it onto recording paper.

The data sent from the data processing device 1 includes not only print data but also codes for format control and engine mode setting.

The bitmap type data processing device 3 analyzes these protocols in addition to the print data, controls the format, and issues instructions for feeding paper to the print engine 4, changing the optional mode, etc. as necessary.

In addition to the recording control described above, the print engine 4 performs associated electrophotographic control, recording paper timing control, and processing synchronized with paper feeding to other options.

Control of the print engine 4 is similar to that of an electrophotographic copying machine except for the scanning system.

(b) Bitmap Control Section FIG. 6 is a block diagram of the bitmap control section 30. The bitmap control section 3o is composed of several blocks connected by an internal bus B30. BM-CPU3
01 is a central control unit of the bitmap type data processing device 3, and a data processing device interface 30.
8, it communicates with the data processing device l and external file buffer 2, converts print data, controls the bitmap writing unit 31 through the bitmap writing unit interface 306, and controls the print engine 4 through the print engine interface 307. Control. SMS-ROM 302 stores programs for BM-CPU 301. The SYS-RAM 303 is a working storage area of the BM-CPU 301 including an MCB buffer area to be described later, and is used to store stacks and basic flags.

The R-buffer 304 is a buffer for communication with the outside (data processing device 1 and 7-aisle 772), and
The purpose is to enable communication between the processing program of the PU 301 and the data processing device 1 to be processed even asynchronously.

The bucket buffer (hereinafter abbreviated as P-buffer) is an intermediate code (hereinafter abbreviated as P-buffer) that converts the data from the data processing device l from the 7-ont attribute and that is easy to draw on the BM-RAM 32.
(hereinafter abbreviated as packet).

The actual drawing of the font is performed by the bitmap writing section 3I, but as information to the bitmap writing section 31, it is necessary to calculate parameters such as the font pattern built-in address and the drawing address to the BM-RAM 32. .

This takes a certain amount of time. Therefore, BM-RAM3
By pre-processing the data for the next page while printing the second page data, processing speed is increased.

Therefore, the movement of data in the P-buffer 305 is F
IFO (first in, first out).

The print engine interface 307 is an interface with the print engine 4, and exchanges JOB control commands such as print commands with the print engine 4 interface via the bus B3.

FIG. 7 is a configuration diagram of the bitmap writing section 31. The functions of the bitmap writing section 31 can be roughly divided into BM-RA
Drawing function to M32 and BM-RAM3 when printing
2 and a function of outputting data to the print engine 4.

The drawing function to the BM-RAM 32 is further divided into two parts: drawing of lines and circles performed by the graphic image writing unit 316, and font drawing performed by the font image writing unit 311. Both are logic units that operate on packets sent from the bitmap control unit 30 through the bitmap control unit interface 317, but most of the processing in the graphic image writing unit 316 is performed by analyzing parameters within the packet and transmitting them to the BM-RA.
M32, most of the processing of the font image writing unit 311 is performed by writing the font image to the font unit 3 via the font unit interface 314 according to the data in the packet.
The font image read from 3 is drawn on the BM-RAM 32.

On the other hand, the function of outputting data during printing is performed by the print head control unit interface 315. That is, from the bitmap control unit 30 to the interface 31
When the print start code sent via the bus B4 is received, the BM
- Outputting the data in the RAM 32 to the print head control unit 42.

(C) Flow of Bitmap Control The operation of this system will now be explained with reference to flowcharts.

1O to 24 are charts 70 showing the processing of the bitmap control section 30. In FIG. 10, first, when the power is turned on (Step #11 and subsequent steps are omitted), internal initialization is performed (#2), and the BM-RA
M32, after clearing P-buffer 3O5 (#3
), initialize the parameters (#4). The function of each parameter is as follows.

JOBACT: Indicates that a certain page is being printed (printing of the set number of sheets has not been completed).

BMWWRITE: Indicates whether any data has been written to the BM-RAM32.

Indicates a JOBEJT niblint activation request.

PAUSE: Pause state (indicates print-stop state).

REF: Indicates that the received data is being reanalyzed.

REP: Indicates the reanalysis end address of received data.

REWIND: Indicates reanalysis of received data.

LPSTART: Indicates that analysis of page data has started.

LPWRITE: Indicates that temporary editing of page data (image) has started.

WAIT: Indicates a temporary stop of packet processing.

Next, clear the reception buffer (#5). here,
It means initializing the pointer, not in the buffer. R
- The buffer is managed by three pointers as shown in FIG. 9(C). Next, we will list the functions of pointers used.

RTOP: Indicates the storage address of the next received data.

RNOW: Indicates the address of the data to be analyzed next.

RBOT: R-indicates the area of data to be stored and held in the buffer.

The initial values of the above pointers are all 0.

Next, a memory control block (hereinafter referred to as MCB) that stores mode information used to analyze received data is initialized (#6). MCB is shown in Figure 9 (
As shown in b), it is a group of data such as the cassette used, paper size, image size, IFC related information, page start address, page end address, etc. next,
MCB buffer that stores MCB data (Fig. 9 (a)
) (see #7). The MCB buffer is
It is used to store the analysis conditions for each page when re-analyzing received data, and is managed by the following two pointers.

MCB TOP: Indicates the address for storing the next page's MCB.

MCB BOT: Indicates the area of data to be stored and held in the MCB buffer.

Both of these initial values are 0 and are updated for each MCB size.

Next, the font attributes used for editing the print data are read (#8) and interrupts are permitted (#9). After initial setting of the paper feed cassette (#lO), the actual processing loop (#11 to #14) is entered.

The actual processing loop can be roughly divided into the following four processes.

0 Received data processing (#11): Processes the received data from the data processing device ■ and converts it into a packet.

01FC command processing (#12): Data processing from print engine 4.

O packet processing (#13): BM-R according to the packet
Drawing processing to AM32.

0 print processing (#14): Processing of print sequence with IFC40.

In order to improve communication efficiency, the data sent from the data processing device 1 is once stored in the R-buffer 305, which is a reception buffer, by processing on the reception side, which will be described later.

The received character data is extracted from the R-buffer 304, converted into a packet, and stored once in the P-buffer 305 in reception data processing (#11). Thereafter, the font is extracted by packet processing (#13), and the corresponding font is drawn in the BM-RAM 32 by the bitmap writing section 31. Among the received data, print request code (PAG
E, EJECT) is detected, print processing (#14
) starts the actual printing.

In addition to this, processing such as temporary stopping of printing and interruption of processing is performed.

<Received Data Processing> The flow of received data processing (#ll) is shown from FIG. 11 onwards.

In FIG. 11, the received data is converted in advance into a packet that can be easily output to the bitmap writing section 31,
It is stored in the P-buffer 305.

This is to improve throughput by converting the received data in the BM-RAM 32 in parallel even during printing.

First, confirm that there is space in the P-buffer 305 (#21), and further, if data has been received in the R-buffer 304 (YES in #22), the process continues. Next, is it necessary to re-analyze the received data? (REWIND=
1? ) (#23), and if YES, re-analyze the received data (#24, see Figure 16);
If so, don't do it. Next, analyze the top data of the page (
LPSTART=0 7) Check #25), Y
If it is ES, set LPSTART to 1 and store the address at that time in MCB in preparation for reanalysis (#2
6). The MCB is also saved in the MCB buffer (#27, see FIG. 17). As a result, at the time of reanalysis,
All you have to do is take out the top address of the page from the MCB buffer. Then, data is taken out from the R-buffer indicated by R-NOW (#28), and RNOW is updated (#2°9).

Then, the interface control unit related code (IFC
related code) (YES in #30), the IFC related code is analyzed (#31).

Not an IFC related code (No in #30), PAGE,
If it is an EJECT code (YES in #32), this code indicates the end of one page of data, so
Printing is activated during packet processing, and when the previous characters have been written to the BM-RAM 32, printing is activated. This code is also output to the P-buffer 305 in order to synchronize processing with the preceding and succeeding characters (#33). At this time, reset the LPWRITE7 lag and LPSTART flag in preparation for temporary editing of the next page (#34
).

#32 is PAGE, not EJECT code (NO),
If it is a format control code (YES in #35), the write address to the BM-RAM 32 is changed corresponding to each code (136).

The received data is not a format control code (No in #35),
In the case of print data (YES in #37), if temporary page data editing has not started in #38 (LPWR
ITE=O? YES), check the image size shown in Figure 20 (#39), set LPWRITE = 1 to indicate that temporary editing of page data has started (#40), and check the font attributes read when the power was turned on. It is converted into a packet according to the following (#41). As a specific conversion procedure, first, the font address of the pattern corresponding to the character code is output to the P-buffer 305, and then the write address to the BM-RAM 32 is sequentially output to the P-buffer 305.
05, and the write mode to the bitmap writing section 31 is output. Finally, the write address of the next font to the BM-RAM 32 is updated according to the size of the current font, etc. (#42). L in #38
If PWRITE=O (No), leave it at #41
Move to.

After analyzing the above received data, if reanalysis is in progress (REF-1) (YES in #43), the next analysis address RNOW
and the re-analysis end address RFP (#44), and if the end address is reached (YES in #44), clear REF to return to normal analysis (#45).

FIG. 8 is a diagram explaining the image area. The portion indicated by the total area Al corresponds to the size of the paper and corresponds to the area set in the BM-RAM 32. The margin area A2 is a blank space when printing is actually performed on paper, and the print data is drawn in the remaining image area A3.

Printing starts from the upper left of image area A3,
Characters are printed sequentially according to the printing direction AIO. in the middle,
When a line feed code is input, the next printing position is moved by the line feed width A12 in the line feed direction All. Also, when the go-around code is input, the left end of the image area, go-around position A13
The next print position moves to .

Also, the drawing position is the cursor position P + (x, +3'+)
The address is BM-R of the cursor.
It is determined as the corresponding memory address on AM32. Furthermore, due to the hardware configuration, instead of P,
2 address is output. To calculate the address, in addition to the position of Pl (x+, y+), the memory size W in the width direction of the current image and the number of lines in the height of the image to be written are required. Address calculation of P2 is performed by the following formula.

Address of P2 = (y+-h+ l)xwx l 6
+x.

However, it is IW (word) - 16 bits.

This process determines the format of the final print result. This process is different from actual editing and drawing in the BM-RAM 32, and can be said to be virtual editing. When drawing the first character of a page, check the paper size of the current cassette (#42), and at the same time set the LPWRITE flag indicating the start of temporary editing (#43).
).

<IFC Command Processing> FIG. 12 is a flowchart of command processing (#12) from the interface control unit (IFC) 40.

EXP, END': ) 77 (#51) is a command to synchronize the print sequence with the interface control unit (IFC) 40, and indicates that the print engine 4 has finished laser exposure for one print. This command is valid only during printing, so JOBACT=
If it is not 1, just return, otherwise #
Move to 53 (#52). JOBAC indicating print status
Reset the T flag #53) and clear BMWRITE, which indicates the drawing status to BM-RAM32 #54)
, prepare for the next image. On the other hand, if paper cassette information is received (YES in #56), check if there is a newly installed cassette (#57); if YES, the cassette is assumed to contain the paper that the user wants to print from now on. Update the initialized cassette (
#58). After that, please update the information currently stored.
59), preparing for the next cassette selection (158), etc.

Next, for PAUSE ON information (YES in #60)
), sets the PAUSE flag to stop the print process (#61).

For PAUSE OFF information (#62), PAU
After canceling the SE state (#63), check whether the paper size or paper direction has been changed during PAUSE (#64). If it has been changed (YES), the received data processing routine (Fig. 11) is executed. Request for reanalysis (RE
WIND 4-1) (#65). Furthermore, set the WAIT7 lag to temporarily stop packet analysis (#66). This flag is reset by the C0NT I NUE packet output to the P-buffer 305 at the start of reanalysis. The stored values of other information are updated for other purposes (#68).

<Packet processing> In the flow of packet processing (#13) shown in Figure 13,
The packets stored in the P-buffer 305 are processed. The packet includes a packet for characters to be printed,
There is a control packet. To change BM-RAM32,
Since this process cannot be performed until the printout of the previous image is completed, the process is not performed in the print state (JOBACT=1) (7) (#71 No). Also, if there is no packet, that is, the P-basopha is empty (#
73: YES), no processing is performed. If there is a packet (No in #73), take out the packet #74), W
If AIT is in progress (No in #75), WAIT processing (FIG. 19) is performed (#76).

If the packet is for characters (YES in #77), it is output to the bitmap writing section 31 (178). The bitmap writing section 31 analyzes the packet and writes a pattern corresponding to the 7-ont address from the 7-ont section 33 to the BM-RAM.
Draw on 32. While one packet is being processed, the next packet cannot be processed (#72), so the process returns.

If this character is the first (BMWRITE = 0° #79: YES), set the BMWRITE flag (
#80).

For control packets other than character packets (N in #77)
o) First, the IFC related code (YES in #81) is
It is mainly used to specify the number of multi-print sheets, the paper cassette, and the operation mode of accessories.IFC40
(#82).

PAGE and EJECT (YES in #83) indicate page breaks, and before this code
The image drawn in 2 is output. To do this, first set the JOBACT flag, switch to the copy state, prohibit future drawing to the BM-RAM 32, and set the print start request flag JOBEJT (#
84). This flag is the print control (14th
), and the IFC40''-print command PRNCMD is actually output.Also, since there is no longer a need to re-analyze the received data, the data is discarded (
#85, Figure 18).

For size information (YES in #86), from then on, B
In order to change the writing mode in the M-RAM32 heavy bitmap writing unit, it is output to the bitmap writing unit (
#87). The mode changed here mainly involves the memory capacity per line of the image.

Print control> In the print control flow shown in Figure 14,
Printing is actually started according to the OB control flag (JOBEJT), PAUSE, and the state of the bitmap writing section 31.

Print startup is performed at the time of print startup request (JOBEJT=
1. #91: YES), but - when stopped (P
During AUSE 1) (No in #92), the bitmap writing unit 31 is processing the last packet (No in #93)
cannot be started.

If printing can be started, after switching the bitmap writing unit 31 to print mode (#94), the IFC 40
5TART command (#95) to request startup of paper feed, etc.
), a print command (PRNC) requesting the start of exposure
MD) is output (#96), and the JOBEJT7 lag is reset (#97).

<Interrupt Request> The flow in FIG. 15 is an interrupt request process for data transmission from the interface 308 of the data processing device l,
RTOP data (#103) from data processing device l
The data is stored in the R-buffer indicated by (#104).

If the R-buffer overflows (
# 101: YES), perform error handling (#102)
. Overflow is checked when it is determined that the write address RTOP to the Rτ buffer reaches the data holding address (when the update of RTOP becomes equal to RBOT).

<Data reanalysis> FIG. 16 shows the procedure for data reanalysis (REWIND).

First, the request flag (REWIND) is reset, the address RNOW in the reception buffer currently being analyzed is set to the reanalysis end address RFP, and the REF7 lag indicating that reanalysis is in progress is set (#111).

Next, in order to make the conditions for analysis the same as those for the first analysis of the relevant page, the information of the oldest unprinted page indicated by MCB BOT is restored to the MCB (#112). Then, set the page start address to the read pointer RNOW during analysis (#113)
. Next, in order to release the WAIT state during packet processing, the C0NTINUE code is output to the P-buffer (#114). Following this, the IFC-related code in the MCB is output to the P-buffer in order to update the engine mode (#115).

After this, the MCB buffer is initialized (#116), and the parameters for temporary editing are cleared (#117). As a result, when analyzing the first character data (Y in #38 in Figure 11)
ES), the image size is changed (#42, 11th
figure).

<MCB evacuation> FIG. 17 shows processing for saving MCB information.

First, the RNO indicating the address of the R-buffer at the end of the page (actually the address of the first data of the next page)
W is stored in the MCB (#121). This is used to indicate the scope of data discard processing (FIG. 18), which will be explained next. Next, save the entire MCB to the MCB buffer indicated by MCB TOP #122), and MCB TO
Update P (#123).

Data disposal> FIG. 18 shows the procedure of data disposal processing.

First, RBOT indicates the data holding area of the R-buffer.
Set the page end address of MCB data regarding the oldest page indicated by MCB BOT (#1
24). This means that the received data has been discarded. Furthermore, the MCB BOT is updated (#125), and the MCB data of the corresponding page is also discarded.

<WAIT> FIG. 19 shows the flow of WAIT processing. This process has a function of skipping old data when the paper size is changed during PAUSE and the temporarily edited data in the P-buffer is re-edited to the new paper size.

First, data extracted from the P-buffer (#74, first
3) is the C0NTINUE code indicating the beginning of new data (#126), otherwise (No)
, Skip it. When C0NTINUE is detected (YES)
, BM-RA to prepare for drawing to BM-RAM32.
If the previous data remains in M32 (BMWRITE=
1. YES in #127), and clears the BM-RAM32 (#128). When the processing is completed, the WAIT flag is reset and normal packet processing returns (#129).

<Image size check> FIG. 20 shows the flow of image size check.

This is done at the beginning of each page, and is mainly used when the size of the currently selected cassette (initial setting in #1O in Figure 1, see Figure 22) has been changed.
Perform this to change the image size during temporary editing.

As a process, check the cassette information input from the interface processing unit 40 and check whether there is a change in the paper size corresponding to the cassette code used (#47).
, if there is a change (YES), change the information. The method is to select the cassette in the cassette position specification mode (
448).

<Cassette Selection> FIG. 21 shows a flowchart for selecting a cassette. Cassette selection is valid only at the beginning of each page (specifically, before print data is received: L PWRITE -0) (YES in #l31). This is because the layout of the temporarily edited image is not guaranteed. There are two modes of cassette specification: specification by paper size and specification by cassette position. If both modes are already the same mode as the specified value, the process is omitted (NO in both #133 and #141).

First, if you specify the size (YES at #l32),
A cassette of the corresponding size is searched from the stored cassette information (#59, FIG. 12) (#134).

If it is found (YES in #135), it is checked whether paper is also included (YES in #136), and then updated. In other words, MC the cassette code and paper size used.
Store the image size calculation result in MCB #138), specify the paper cassette in P-
Output the size information to the buffer (#139), and output the size information to the P-buffer (#140).

The image size in #138 includes the dot conversion size (xmax, ymax) of the paper, the effective image size (xlimit, ylimit), the number of horizontal words, etc. shown in FIG.

On the other hand, in the case of specifying the cassette position (NO in #132),
Please check if the corresponding cassette is installed #142
), updated if available.

<Initial setting of paper feed cassette> Next, the initial setting of the paper feed cassette will be explained with reference to FIG. 22. The cassette information is mainly B of the temporary editing image.
When calculating the write address to M-RAM32 (#42),
This is necessary for controlling bitmap writing (
#87, Figure 13).

First, it waits for cassette information from IFC40 (#1
51). The I Fe12 sends initial information for each cassette when the power is turned on. From now on, when information changes, we will send it to you for updates. The cassette information includes the paper size of each cassette (51, 52, 53 in FIG. 4), the presence or absence of paper, and whether or not the cassette is installed. The paper size here is not a dot size, but a paper size code preset for each paper.

Next, an initial cassette is selected. The idea is that each cassette has a priority order (in this example, 51, 52, 53), and if any of the cassettes is installed and there is paper, then the priority order is determined. , searches for a usable cassette (#152). If there is no paper in all the cassettes (YES in #153), the cassettes installed are searched according to the same priority order (#154). This is done in consideration of a case where a frequently used cassette happens to be out of paper, or a case where a cassette is removed to prohibit the use of a malfunctioning cassette that has a high priority.

In this way, the determined cassette and its paper size are stored in the MCB as a cassette in use, and at the same time, the image size of the paper (width word count W, etc.) is determined from the paper size attribute table stored in advance. Find B
Prepare for calculation of write address to M-RAM (#1
57). Furthermore, a packet specifying the paper feed cassette is output to the P-buffer as an IFC related code (11
58).

Also, size information is output to the P-buffer in order to change the mode of the bitmap writing section (#159).

Also, if there is no installed cassette (NO in #l 55)
Assuming that all cassettes have some kind of abnormality,
Please output the error code directly to IFC #160), JL
stop the process. Recovery is initialized by turning the power on/off after loading the cassette.

<Analysis of IFC-related codes> FIG. 23 shows the flow of analysis of IFC-related codes among data from the host.

In the case of cassette selection (YES in #l71), it is determined whether or not it can be used according to the paper feed cassette information of the print engine 4 and external paper feed unit 5 input from the print engine interface 307 (#172).
, if it is available, determine whether temporary editing has been performed (#173), and if so (No in #l73).
, makes a negative response (#174). C if not done
YES in #173), an affirmative response is made (#175), and a cassette is selected (#176). If the cassette is unusable (No in #172), a negative response is also made.

If it is in sorter mode (YES in #l77), the sorter connection is checked (#178), and if YES, an affirmative response is made (#179), and the sorter mode is set to P-.
Output to the buffer (#181). Then, the MCB information is updated (#182). If the sorter is not connected (No in #178), make a negative response (#l
80).

For print system IO status requests (# l
83: YES), if reanalysis is not in progress (REF=O1
YES in #184), the corresponding status is output to the data processing device (#185).

If the code is different from the above code, it is output as is to the P-buffer as an IFC related code (#186).

<Affirmative response/Negative response> Figures 24(a) and (b) are the processing flows of an affirmative response and a negative response, respectively, and both are when reanalysis is not in progress (#191
, YES in #195), and the acknowledgment code (
ACK code), and negative response code (NA
K code) to the data processing device (#192.#
l96).

(d) Processing flow of interface control unit FIG. 25 is a processing flow of the IFC 40.

In IFC40, after internal initialization (#200)
, initialize each parameter (#201).

Each parameter is as follows.

PRNSTAT: Indicates that the engine section is printing.

PRNFLG: Indicates that a print command from the bitmap control unit 30 has been detected.

lN5TALL: Indicates that the engine initial state check has been completed.

5TART: Indicates that a 5TART command from the bitmap control unit 30 has been detected.

PAUSE: Indicates the status of the PAUSE key.

Then, enable the two interrupt processes described below (#2
02), if there is no abnormality in the print engine (#203
and lN5TALL=1), sorter 6 through bus B5,
External paper feeding unit 5, electrophotographic control section 41. An activation signal is output to the print head control unit 42 (#204), and the process moves to a processing loop. Note that the interrupts include a bitmap control section interrupt (FIG. 26) for receiving commands etc. from the bitmap control section 30, and a system timer interrupt (FIG. 27) for performing timer processing by the controller of the operation panel 44.

The presence or absence of an abnormality in the print engine section is checked by a system timer interrupt (FIG. 27), and can be confirmed by the IN5TALL flag in the main routine.

Before explaining the processing loop, two types of interrupt processing will be explained. First, bitmap control block interrupt (Figure 26)
I will explain about it. In the bitmap control unit interrupt, a command sent from the bitmap control unit 30 is received. Further, in the bitmap control unit interrupt, the received command is not directly executed, but only a flag in the interface control unit is set, and actual processing is performed when this flag is detected in the processing loop. This is to make the communication between the processing loop and the bitmap control section 30 asynchronous, thereby simplifying the configuration of the processing loop. Also, in the case of print or accessory mode information (#254
YES) is also stored in the -degree temporary area (#255),
Officially captured within the processing loop.

Next, the system timer interrupt (FIG. 27) will be explained. In the system timer interrupt, input/output processing of the operation panel 44 (#271, #272), counting processing of the timer set in the processing loop (#273), and checking of the status of each part of the print engine are performed (#275). ．．
#278. #281), if there is a change to notify BMC, output to BMC (#276, #279. #2
82). The size of the paper feed cassette and the presence or absence of paper are also checked here, and the paper is sent to the BMC (#274 to #276).

At this time, please also check if there are any problems #2
83), if it has occurred, it will be displayed on the operation panel; if not, the lN5TALL flag (
#203. (Fig. 25) is set (#285). Also, press the PAUSE key 901 to request a temporary stop of printing.
Each time you press (PAUSE・ON/PAUSE・0FF)
is controlled to repeat (#289 to #294). P
The AUSE flag is used to determine this state. Which state is in is displayed on the PAUSE LED 918 in FIG. 3 (#271). Also, every time there is a change, BMC
It will also be sent to (#291.4293).

Referring back to FIG. 25, the processing loop will be explained below. At the beginning of the processing loop, the process waits for a print start request (#205
), and when it is accepted, the mode information of the accessory is updated (#206 and #207). and detected 5
Reset TART and print status (PRNSTAT)
-1) (#208). After that, in order to perform the first printing, a paper feed request signal (FEED, REQ) is output to the electrophotographic control unit 41 through path B5 (#209).
. As a result, the electrophotographic control section 41 starts activating the electrophotographic processing section 45 for paper feeding and printing. However, the paper is in a standby state at a predetermined position. However, if the external paper feeding unit 5 is specified, the electrophotographic control section 41 only activates the electrophotographic processing section 45, and the external paper feeding unit 5 performs paper feeding. Note that the paper standby position is the same.

Then, the interface control unit 40 waits for a print command (#210).

In IFC40, PRN indicating reception of print command
When FLG-1 is detected, the request flag should be reset.#
211), EXP indicating exposure permission.

Output the ENB signal to the print head control unit 42 (#
212). Accordingly, the actual exposure is performed by the print head control section 42.

In the print head control unit 42, when the exposure is completed, the E
When the IFC40 that outputs the XP and END signals detects this (#213), it releases the print status #2
14), EXP that indicates permission to print the next page to BMC
, output END (#215), and return to waiting for the next print (#205).

In addition to the above-mentioned control, the IFC 40 performs communication control within the print engine 4, and exchanges data with each control section via the bus B5, and also has a relay function for communication between each control section.

Since this is not directly related to the present invention, detailed explanation will be omitted.

(Effects) It includes a protocol that outputs response data to the host computer when the host computer requests data reanalysis when the paper size or orientation is changed during printing or when a paper jam occurs. This also prevents the output of response data, which prevents trouble and eliminates the need to reset the printer.
Improved usability.

[Brief explanation of the drawing]

FIG. 1 is a system configuration diagram of an electrophotographic printer according to an embodiment of the present invention. FIG. 2 is a perspective view of the printing system. FIG. 3 is a diagram of the operation panel. FIG. 4 is a central sectional view of the printing system. FIG. 5 is a block diagram of the bitmap data processing device and print engine. FIG. 6 is a block diagram of the bitmap control section. FIG. 7 is a block diagram of the bitmap writing section. FIG. 8 is a diagram showing a method of calculating an image area and a write address. FIG. 9(a) shows the MCB bag 4. FIG. FIG. 9(b) is a diagram showing MCB information. FIG. 9(c) is a conceptual diagram of the R-buffer. 10 to 24 are diagrams showing the processing flow of the bitmap control section. FIG. 25 is a diagram showing the processing flow of the interface control section. FIG. 26 is a diagram showing the flow of bitmap control unit interrupt. FIG. 27 is a diagram showing the flow of system timer interrupt. l...Data processing device, 3...Bitmap type data processing device, 4...Glint engine, 30...Bitmap control section, 31...Bitmap writing section, 32...Bitmap RAM. 304...R-Buffer, 305...P-Buffer 7゜Patent Applicant Minolta Camera Co., Ltd. Agent Patent Attorney Aoshiro Ao and 2 others tiSI Figure 2 Figure 3 Figure 5 ＼\4 Figure 7 Arisitohet @ Sir Gp Figure 9 (0) MCB Ba””
(b) MCB No. 1014 Fig. 16 Fig. 17 Fig. 19 Fig. n Fig. C 24

Claims (1)

[Claims] (1) At least, an input means for inputting print data and control data, a storage means for storing the input data from the input means, an analysis means for analyzing the input data, and according to the analysis result of the analysis means a response output means for outputting the analyzed response data stored in the storage means; a reanalysis means for reanalyzing the analyzed input data stored in the storage means; and an output of the response output means is inhibited while the reanalysis means is in operation. What is claimed is: 1. A printer control device comprising an output blocking means.