JPH02231178A - Image forming system - Google Patents

Abstract

PURPOSE:To transfer a number of state informations efficiently and rapidly without complicating communication and processing by a method wherein an image forming device and respective additional equipments make a group of various types of present states as one information code and transfer it to an image processor or a host system. CONSTITUTION:An image forming system consists of an image forming device body 4 receiving character code information, image information, and the like from a host system 1 and forming an image on a recording medium and additional equipments 5A-5E. A command issuance means 4b in the image forming device body 4 issues a command containing an identification code for individually specifying the respective additional equipments 5A-5E or a command containing a commom identification code for specifying all the additional equipments, as necessary. A serial communication part 4a transmits the command to the additional equipments 5A-5E through a signal bus SB. Therefore, the image forming device body 4 can conduct a control by individually specifying the additional equipments 5A-5E in a normal state, or issue and transmit the command containing the common identification code for specifying all the additional equipments, whereby such information such as an emergency stop command can be simultaneously transferred to the additional equipments 5A-5E to be conducted.

Description

[Detailed Description of the Invention] [Field of Industrial Application] This invention is applicable to various printer systems such as laser printers, LED printers, liquid crystal printers, and inkjet printers, or image processing devices such as high-performance copying machines and high-performance fax machines. Concerning the formation system. [Prior Art] In recent years, image forming devices such as laser printers have tended to be systematized in order to meet various demands. an image processing device that generates image information using image processing; an image forming device that receives image information from the image processing device and forms an image on a recording medium; Image forming systems are now being configured by connecting various additional devices for feeding, discharging, or conveying images through interfaces. In some cases, the host system has a function equivalent to the image processing apparatus described above, and in that case, the image forming apparatus directly receives image information from the host system and forms an image on the recording medium.

[Problem to be solved by the invention]

However, in the past, the instruction sets handled by these various image forming systems were independently developed for each system, and the interface protocols were different for each system.

Therefore, all specifications of the image processing device, image forming device, and various additional devices that make up the image forming system must be determined in advance at the time of initial conceptual design of the system, and as a result, there is no compatibility between systems. However, there was a problem that the system lacked expandability and flexibility.

Furthermore, when transmitting the current status of the image forming device and additional devices to the image forming device or host system, the transmission method and contents are unique to each system, and when expanding the additional devices, the same method and contents are required. This requires an additional interface section to be provided to the image forming apparatus, image processing apparatus, or host system, which is irrational.

Furthermore, the image processing device or host system must constantly manage the status of the five image forming devices and each additional device attached to it, and as the number of additional devices increases, the status management and processing become complicated. There were also problems.

The present invention has been made in view of these conventional problems, and is intended to improve the expandability of the system by making it easier to add and change additional devices to an image forming apparatus, and particularly to improve the expandability of the image forming apparatus and its additional devices. The status can be easily and quickly transmitted to the image processing device or host system, and the processing can be made more efficient. When a change in status occurs in the image forming device or additional device, the information can be transmitted as necessary. The purpose is to be able to immediately notify the image processing device or host system. [Means for Solving the Problems] In order to achieve the above object, the present invention includes an image processing device that generates image information by receiving character information or image information from a host system, and a system that generates image information from the image processing device. It consists of an image forming device that receives the received information and forms an image on a recording medium, and various additional devices that are removable from the image forming device and feed, eject, or transport the recording medium, and these are connected via an interface. In an image forming system that is connected to the image forming apparatus, the image forming apparatus and the additional apparatus are provided with a means for grouping the current status into one information code and transmitting it to the image processing apparatus; The apparatus is equipped with a state change notification means for notifying the image processing apparatus as an asynchronous message when a state change occurs. In addition, if the host system is equipped with the function of an image processing device, the image forming device and the additional device are provided with means for grouping the current status into one information code and transmitting it to the host system. , a status change notification means that notifies the host system as an asynchronous message when a status change occurs in the image forming device or the additional device. Furthermore, in any of the image forming systems described above, the image processing apparatus or the host system may include means for controlling the range of image forming apparatuses and additional devices to which the contents of the information code are reflected in the information code. good.

[For production]

In the image forming system according to the present invention configured as described above, the image forming apparatus and each additional device group various current states into one information code and transmit it to the image processing apparatus or the host system, so that communication is easy. A large amount of status information can be efficiently and quickly transmitted without complicating the process.

Additionally, when a change in status occurs in the image forming device or additional device and it is necessary to notify the image processing device or host system immediately, the information is sent as an asynchronous message to the image processing device or host system immediately. Can be notified.

Furthermore, the image processing device or the host system specifies the range of image forming devices and additional devices to which the contents of the information code are reflected in the information code, so that -
ffi processing can be made more efficient and simpler.

〔Example〕

Examples of this invention will be described below based on the drawings. I will explain in detail.

FIG. 1 is a block diagram showing the system configuration of a basic embodiment of the present invention.

This image forming system includes an image forming apparatus body 4 that receives character code information, image image information, etc. from a host system 1 and forms an image on a recording medium, and five units that are each detachable from the image forming apparatus body 4. Additional device 5A
The system consists of ~5E.

That is, the additional devices include a multi-stage paper feeder 5A and a mass paper feeder 5B, which are additional paper feeders, a reversing paper ejection device 5C and a mass paper ejection device 5D, which are additional paper ejection devices, and an additional recording medium transport device. A double-sided conveying device iH5E is mechanically connected and attached to the image forming apparatus main body 4, and all of them are connected by a common signal line (serial bus) SB.

The image forming apparatus main body 4 and each of the additional devices 5A to 5E are provided with serial communication units 4a and 5a to 5e as communication means for serial communication via the signal line SB, respectively.

Furthermore, a command issuing means 4 is provided in the image forming apparatus main body 4.
b, and this command issuing means 4b issues a command including an identification code for individually identifying each additional device 5A to 5E and a command including a common identification code for identifying all of each additional device, as necessary. The serial communication unit 4a sends each additional device r? via the signal line SB. 15A
- Send to 5E.

Therefore, the image forming apparatus main body 4 can normally specify and control each of the additional devices 5A to 5E individually, and if necessary, for example, if a serious error occurs in the system, the image forming apparatus main body 4 can be If you want to stop all mechanical operations in the attached devices, issue and send a command that includes a common identification code that identifies all attached devices, and issue an emergency stop command, etc. to each attached device 5A to 5E at the same time. information can be transmitted and executed.

Here, the communication protocol between the image forming apparatus main body 4 and each of the additional devices 5A to 5E will be briefly described.

Communication from the image forming apparatus main body to the additional device is performed by sending commands, and communication from the additional device to the image forming apparatus main body is performed by sending responses.

As shown in FIG. 2, one command is composed of an operator and an argument of 8 bits each, and the argument is sent first and the operator is sent after. The upper 3 bits b7 to b5 of the argument are always ゛111
It is.

As shown in FIG. 2(a), a normal command includes the identification code (ID) of the additional device specified as the communication partner in the upper three bits b7 to b5 of the operator, and b4
~bO contains a code indicating the type of instruction, etc.

Here, each additional device 5A to 5E in the embodiment of FIG.
The identification code (ID) is defined as follows, for example. Multi-stage paper feeder 5A: OOO (IN#1) Mass paper feeder 5B: oot (IN#2) Double-sided conveyance device 5
E: 010 (DPX# 1) Reversing paper ejection device 5C
:100 (OUT# l) Mass paper discharge device 5D:
101 (OUT#2) The upper two bits of this 3-bit identification code indicate the type of additional device (type: paper feed, conveyance, paper ejection), and the lower one bit indicates the device number (#1 or #2). ) is shown in parentheses for easy understanding. FIG. 2(b) shows the structure of a command (hereinafter referred to as ``global ID command'') that includes a common identification code (hereinafter referred to as ``global ID address'') that identifies all attached devices. This global ID command sets the upper 3 bits b7 to bs of the operator as the global ID address.
0'', and a code indicating the type of command is entered in b4 to bO, for example, in the case of an emergency stop instruction, 01111° is entered in b4 to bO.

When each of the additional devices i5A to 5E receives this global ID command through its respective serial communication section, each device recognizes that it has been specified and immediately executes the command without returning a response.

An example of the use of this global TD command is as follows.

(a) When performing system initialization (initialization operation and self-diagnosis).

(b) When setting the paper size in each additional device when performing an image forming operation by selecting a paper feeding device that cannot self-detect the paper size.

(C) When it is necessary to urgently transmit information to all additional devices (for example, when transmitting an emergency stop command when a paper jam occurs).

Logical ID and Device ID FIG. 3 is a block diagram showing the basic configuration of an embodiment that further enhances the expandability of the image forming system according to the present invention, and parts corresponding to those in FIG. 1 are given the same reference numerals. Therefore, their explanation will be omitted. This image forming system includes an image forming apparatus main body 4 that forms an image on a recording medium by receiving character code information or image image information from a host system 1, and seven units that can be attached to and detached from the image forming apparatus main body 4. The system consists of additional devices 5A to 5G. That is, a multi-stage sheet feeding device 5F and a multi-stage sheet discharging device 5G are added as additional devices to the image forming system shown in FIG. 1, and the image forming apparatus main body 4 and each of these additional devices 5A to 5
G are all connected by a common signal line SH. Furthermore, it is possible to add more additional devices as shown by the broken lines. The image forming apparatus main body 4 in this embodiment can simultaneously control up to two additional sheet feeding devices, up to two additional sheet discharging devices, and at most one additional double-sided conveying device. Here, being able to control simultaneously means a state that satisfies all of the following. It is possible to process execution commands, inquiry commands, selection commands, etc. through direct communication.

0 Feeding, transporting, and ejecting the recording medium can be executed by commands.

O Can be selected as the transport path for the recording medium.

Therefore, the image forming apparatus main body 4 has six types of codes as control identification codes (hereinafter referred to as "logical IDJ"). This corresponds to the identification code (ID) of each additional device in the above embodiment. In other words, all additional devices (optional units) are classified into three unit types: paper feeding device, paper ejecting device, and transport device, and the following logical I/O is created for each unit type.
I have prepared D.

Additional paper feeder 1 (IN #1) eOOO same (
IN #2) :oot additional conveyance device (D P
X-INP): 0 1 0 same (DPI
・OUT): 011 Additional paper ejection device (OUT# 1):
100 same (OUT$$2'): lo
tThis logical ID is a 3-bit code, of which the upper 2 bits are a unit type code that identifies the type of IN, OUT, and DPI, and the lower 1 bit is #1.
or #2 (double-sided conveyance device which is an additional conveyance device:
In the case of DPX, this is a code that identifies whether it is used as an input unit (INF) or an output unit (OIJT).

The image forming apparatus main body 4 has a serial communication function that sends a command including this logical ID to the signal line SB, and both the internal image processing section, image creation section, and external host system normally use this logical ID. Each of the additional devices 5A to 5G is specified using .

On the other hand, each of the additional devices 15A to 5G has a unique identification code (hereinafter referred to as "device (physical) IDJ)" and has a serial communication function to send a response including the device ID to the signal line SB.

In addition, each unit has its own unit type, that is, paper feeding device (IN), paper ejecting device (OUT), and duplex transport device i1.
(DPI) is also stored as a 2-bit code, similar to the unit type code of the logical ID.

If the device ID is given as a 4-bit code for each unit type, there will be 16 devices for each unit type, for a total of 48 devices.
Even the stand can be identified.

In this example, device IDs are assigned as follows. Multi-stage paper feeder 5A: (IN)0000 Multi-stage paper feeder 5F: (IN)0001 Large-scale paper feeder 5B
: (IN)0010 Reversing paper ejection unit 1f5c :
(OUT)0000 Multi-stage paper discharge device 5G: (OUT)
0001 Mass output device 15D: (OUT) 0010 Double-sided transport device 5E: (DPI) 0001 Note that IN, ○UT, and DPI in parentheses are actually assigned to each additional device (optional unit) as a 2-bit unit type code. Only the 4-bit code after that is the device ID.

Therefore, in the image forming apparatus main body 4, an additional device within the same unit type is specified for each logical ID (
Assign) and store the device ID in a table in memory, for example as shown in the following table.

On the other hand, each additional equipment i! 25A to 5G have a memory for storing their own unit type code (IN, DPX, OUT identification code) and device ID, and the above-mentioned logical ID.
When assigned (specified) to the logical rD
A memory is provided for each. In this way, six logical IDs and the device IDs of the additional devices assigned to them (however, D.
PX-INP and DPX-OUT are assigned the same device ID of the same double-sided conveyance device), so that the image forming apparatus main body 4 can identify the assigned additional device only by the logical ID. can be controlled by

In FIG. 3 and the above example, the logical ID (shown with Log in FIG. 3) as the additional paper feeder is IN$$1.
Multi-stage paper feeder 5A, large-volume paper feeder 5B on IN$$2, reversing paper feeder 5C on logical ID OUT#1 as additional paper ejection devices, mass paper ejection device 5D on OUT#2, additional double-sided The double-sided transport device 1!5E is assigned to the DPI (rNP and OUT) as the transport device for both.

In FIG. 3, this assigned additional device is shown in a double line frame. Therefore, the image forming apparatus main body 4 can control these five additional devices 15A to 5E at the same time. However, this assignment state can be changed as necessary, so even if other additional devices, such as the multi-stage paper feeder 5F and the multi-stage paper ejection device 5G, or even more additional devices are added, You can make them available.

Note that between the image processing device and the image forming device in the image forming device main body 4, and between the image forming device main body 4 and each additional device 5A.
The communication protocol for serial communication between ~5G and 5G provides two levels of commands.

One of them is a basic command, and if this image forming system consists of two or less additional paper feeding devices, two or less additional wandering paper devices, and one or less double-sided transport device, the logical ID Basic commands, which are commands that handle only added devices registered in , can encompass all system functions.

In this way, an image forming system in which all system functions can be controlled by basic commands is referred to as a basic system, and in this system, the code number of the device ID may be the same as the code number of the logical ID. The embodiment shown in FIG. 1 corresponds to this basic system.

The other is the enhance command (extension command), which is used when the image forming system has three or more additional paper feeding devices, three or more additional paper ejecting devices, or two or more duplex transport devices. The additional paper feeding device or additional wandering paper device and the second and subsequent duplex transport devices can be fed by the image forming apparatus main body 4 by assigning their device IDs to the logical IDs of the same unit type using the enhance command. It becomes possible to control paper, paper ejection, double-sided conveyance, etc.

Note that functions related to the present invention will be explained in detail in the following description of specific embodiments.

Laser Printer System Hereinafter, an embodiment in which the present invention is applied to a laser printer system will be described.

FIG. 4 is a block diagram showing a schematic configuration of the laser printer system, and parts corresponding to those in FIGS. 1 and 3 are given the same reference numerals. This laser printer system includes a host system 1, a printer main body 4 which is an image forming apparatus main body consisting of a controller 2 and a print engine (hereinafter simply referred to as "engine") 3, and various additional devices such as the above-mentioned additional devices 5A to 5G. An additional device (hereinafter also referred to as "option unit") 5, a host interface (hereinafter referred to as "host I/F"), and a laser printer video interface (hereinafter referred to as rLPV) that connect these devices.
The engine option interface (hereinafter abbreviated as rEOI/FJ) is comprised of an engine option interface (hereinafter abbreviated as rEOI/FJ).

The host system 1 is an information processing device such as a word processor, office computer, or personal computer that sends character information or image information.

The controller 2 is an image processing device that receives character information and image information from the host system 1 and generates image information (video data) for each page of print paper.

The engine 3 is an image forming device that prints image information generated by the controller 2 onto paper.

The host I/F is an interface for connecting the host system 1 and the controller 2, and is an RS232C
, Centronics I/F, etc. are well known.

LPVI is a controller 2 that constitutes the printer main body 4.
It is a standard interface that connects the engine 3 and the engine 3.
The video interface hardware, which had previously been determined individually for each engine (model), has been unified, making it independent of engine functionality.

E○I/F is engine 3 and various options Schnit 5
In order to perform serial communication by connecting the above-mentioned common signal line (serial bus) between them, and sending a command including the above-mentioned logical ID from the engine 3, the optional unit specified by that ID returns a response. This is a standard interface.

Figure 5 shows the hardware configuration of controller 2. The controller 2 includes a cPU 20 and a program ROM as shown in the figure.
2 1, RAM22, font ROM23, non-volatile R
It consists of an AM 24, an operation panel 25, a scaling processing unit 26, an option interface 27, a video control unit 28, an engine interface 2, the aforementioned host interface 4, and the controller side portion of the LPVI, each of which has a C
Connected by PU bus. The CPU 20 is a central processing unit that centrally controls the entire controller 2, and is a general-purpose 16-bit or 32-bit
Uses a bit microcomputer.

The program RoM21 stores microcode (program) for controlling the CPU20. RAM22
is a large-capacity random access memory that is mainly used for the following purposes.

(a) System memory (b) Input buffer (c) Page buffer (d) Font file (e) Macro file (f) Image file (g) Print control file (h) Video buffer Figure 6 shows data processing. The flow and the relationship between each buffer and file in this RAM 22 are shown.

Information sent from the host system 1 is stored in the input buffer 22b via the host interface 4. The data changed to this input buffer 22b is
A page buffer 22Q, a font file 22d, a macro file 22e, an image file 22f, a print control file 22g,
be registered in either.

That is, print sequence control data (specifying paper transport path, number of print sheets, etc.) is stored in the print control file 22g, page layout information (relationship between print data and print position, etc.) is stored in the page buffer 22Q,
Image information is registered in the image file 22f, downloaded fonts are registered in the font file 22d, overlay information, etc. are registered in the macro file 22e.

The image information processing section 202 expands the contents of the image file 22f, font file 22d, and font ROM 25 into the video buffer 22h through the scaling processing section 26 according to the contents of the page buffer 220.

When the printing data for one page is completed in the video buffer 22h, the print control unit 203 starts the engine 3 via LPVI according to the contents of the print control file 22g, and when the engine 3 reaches the image recording timing, 22h sends the developed video data to the engine 3 via the LPV equipment.

Engine 3 prints the video data sent through LPVI onto paper.

Returning to FIG. 5, the font ROM 23 stores font data for converting character information sent from the host system 1 via the host interface 4 into image information.

The nonvolatile RAM 24 is a memory that stores information for controlling the operating state of the printer after the power is turned on, and mainly stores the following items. (a) Print direction (b) Font (c)
Character size (d) Line spacing (e) Paper feed slot (f) Paper output slot (g) Host interface The memory contents of this non-volatile RAM 24 are stored in the operation panel 25.
Updated from. FIG. 7 shows an example of the appearance of the operation panel 25. The operation of updating the storage contents of the nonvolatile RAM 24 using the operation panel 25 is called a mode set.

This operation panel 25 includes an LCD display 250 for displaying the printer status and mode set contents in text, a power LED 251 that lights up when the power is turned on, an online LED 252 that shows the printer's online status, and an online LED 252 that lights up when the printer is abnormal. or blinking attention LED
25;, data LED 254 indicating that there is print data in the printer, online switch 255 for switching the printer online/offline, data L
Form feed for printing data in the printer when ED254 is lit.
eed) switch 256, test switch 257 for starting the printer's self-diagnosis test function, etc., reset switch 258 for resetting the printer, switches 25A, 25B, 25C, 25 for mode setting operation.
Consists of D.

As for the contents of the mode set, set items are arranged in a hierarchical manner as shown in FIG.

Then, in the offline state, press the upward arrow mode switch 2
By pressing 5A, the mode is set, and the "print direction" of the first layer is selected. If you want to select another item on this first level, use the left and right arrow switches 25B or 2
Operate 5C.

Each time the right arrow switch 25C is pressed, the set items change to r font, character size, r line spacing, paper feed, paper output, and host interface.

On the other hand, each time the left arrow switch 25B is pressed, the set items change in the opposite direction from "host interface" to "paper discharge port" and "paper feed port."

If the item to be set is "Typeface", select "Typeface" with the right arrow switch 25C, and then press the down arrow enter switch 25D to move the hierarchy to the second hierarchy.

There are three typefaces in the second layer: Courier and Elite.
, Gothic is selected using the left and right arrow switches 25B and 25C.

For example, select "R Elite" and press the down arrow enter switch 25D to set it.
"H" is registered in the nonvolatile RAM 24. That is, by pressing the enter switch 25D at the lowest level, the registered contents of the nonvolatile RAM 24 are updated.

・In other set items of the 1st floor calendar, "Print direction" is vertical and horizontal, r character size is 8 points, 10 points, 12 points.
point, and "line spacing" is 3 LPI (Line/In
ch), 6LPI, 8LPI, and the "paper feed slot" is the upper paper feed cassette, lower paper feed cassette, bulk paper feed unit,
``Paper output'' includes an upper wandering paper tray, a side paper output tray, and a bulk paper output unit. As for the "host interface", Centronics and RS-232C can be selected at the second layer.

Furthermore, RS-232 is used as a “host interface”.
If you select C. The type of parity check and baud rate (communication speed) can be selected and set on the third layer.

Returning to FIG. 5, the scaling processing section 2 is a scaling processing section for scaling the image information to an optimal size in accordance with the resolution of the engine 3.

The host interface 4 is an interface that connects the host system 111 and the controller 2, and is provided with two types: Centronics-compliant parallel and RS-232C, and is selected by operating the operation panel 25 described above.

The option interface 27 is an interface for externally supplying fonts and programs to expand functionality, and in this example can handle two IC cards 6.

The IC card 6 is a commercially available one, and depending on the type of data stored, there are cards that store a font card, a program card, or both, but they are physically the same card.

The file format of this IC card 6 is composed of file size, CRC check data, file type, resolution, and font data or program, as shown in FIG. The type of data is determined based on the file type. In other words, if the file type is ``1'', it is a font, and if the file type is ``0'', it is a program. Returning to FIG. 5, the video control unit 28 stores the bus width (1) of the CPU 20 in the video buffer 22h of FIG.
The video data stored in 6 bits or 32 bits is converted into serial data or 8 bit parallel data and sent to the engine 3 via LPVI.

Engine interface 2nd detects the engine status using bidirectional serial signals via LPVI,
Serial communication that sends commands to control the engine (
transmission/reception) functions.

Here, the LPVI signal is shown in FIG. The signals consist of an image signal system, a control signal system, and a power supply. The image signal system is /
WC L K, /WDATA. /LSYNC, /LGA
There are five types of signals: TE and /FGATE.

The control signal system is /PETXD, /PERXD, /PEC
There are four types of signals: TS and /PEDTR, and the power supply is:
There are two types: +5V and GND.

Here, the "/" prefixed to each signal name indicates negative logic (low active), and is shown with an overline in FIG. 10.

(a)/WCLK: Clock for synchronizing image data from the print engine. An image is printed by sending image data (/WDATA) in synchronization with the falling edge of this signal. Low level is black.

(b) /WDATA: Image data sent from the video control unit 28 in FIG.

(c) /LSYNC: Line synchronization signal indicating the start of each scan line.

/WC　L　K signal falling Sync.

(d)/LGATE: A signal indicating the effective image area of each scan line.

/WCLK signal falling Sync.

(e)/FGATE: A signal indicating the effective image area in the paper feeding direction. /LSY Synchronize with the falling edge of the NC signal.

(f) /PETXD: Status signal for informing the engine status from the engine to the controller.

(g) /PERXD: Command line from controller to engine.

(h) /PECTS: Indicates the ready of /PETXD signal. When this signal is at a low level, it becomes possible for the engine to send status information to the controller.

(i) /PEDTR: Indicates the ready state of the /PERXD signal. When this signal is at a low level, the controller can send commands to the engine.

(j) +5V: +5V power supplied from the engine.

(k) GND: Ground (earth) No. 11
The figure shows the relationship between the print area and the image signal.

7 is the effective printing area, 8 is the /WDATA signal 9a,
9b indicates an image area to be printed, and 9 indicates an image area to be printed by /WDATA signals 9a and 9b.

Next, the configuration of the engine will be explained with reference to FIGS. 12 and 13.

FIG. 12 is a schematic diagram of the engine main body constituting the mechanical section of the engine 3 of the laser printer system described above, and the mechanical sections of various optional units connected thereto.

Reference numeral 10 denotes an engine main body, which includes a photosensitive drum 101, an electrostatic charger 102, a light (laser) writing unit 103, a developing device 104, a transfer separation charger 105, a cleaning unit 106, a fixing unit 107, and a pair of registration rollers 108. It has built-in rollers for transporting paper, their immediate-acting motors, and drive mechanisms.

Reference numerals 11 and 12 indicate paper feed cassettes (trays) that are directly attached to the engine body 10, and can normally accommodate 100 to 200 sheets of paper. It is also possible to insert a multi-stage paper feeding unit corresponding to the above-mentioned multi-stage paper feeding devices 5A and 5F each having multi-stage paper feeding cassettes (trays) into these two paper feeding cassette slots of the engine main body 10. 13 is an inverter for switching the paper ejection path, which corresponds to the above-mentioned reversing paper ejection device 5C, and converts the wandering paper path to its own upper wandering paper tray 1.
4, a mailbox (multi-stage paper storage unit If) 15, a duplex unit 16, and a large quantity discharge unit 18.

In addition, sheets other than the upper paper tray 14 can be supplied with reversed paper to each unit. Of course, non-reversed paper can also be supplied. Therefore, by using this function, it is possible to arbitrarily select between face-up paper discharge and face-down paper discharge.

Reference numeral 15 denotes a mailbox having a large number of paper discharge trays 15a, which corresponds to the above-mentioned multi-stage wandering paper unit U5G, and any paper discharge tray can be selected according to a command from the controller 2.

On the 1st, there is a duplex unit that serves as a paper refeed unit for duplex printing, and corresponds to the aforementioned duplex conveyance device 5E, in which the paper printed on one side in the engine body 10 is transferred to the inverter 1.
3, the paper is reversed and fed, and from there it is fed again to the engine main body 10, where it prints on the other side, resulting in double-sided printing 6. Note that the duplex unit 1 used in this embodiment day,
Paper path 16 without stopping the fed paper
1 and a first conveyance path that conveys the paper directly to the paper feed side through the paper;
The stacker 162 sequentially stacks and holds the supplied sheets of paper, and has a second transport path that sequentially transports the sheets to the paper feed side after stacking the required number of sheets.

Reference numeral 17 denotes a large-volume paper feed unit corresponding to the above-mentioned large-volume paper feeder 5B, which can store approximately 2000 sheets of paper.

The large-volume paper discharge unit corresponds to the above-mentioned mass paper discharge device 5D and can store approximately 2000 sheets or more per day.

By making the number of sheets stored in the mass paper discharge unit 18 greater than the number of paper sheets stored in the mass paper feed unit 17, all the sheets supplied from the mass paper feed unit 17 can be collected into the mass paper discharge unit 18.

Reference numeral 19 denotes a printer table on which the engine body 10 and its optional units are placed, and the inside thereof is used as a storage space 19a for the controller 2 mentioned above.

Engine body 10 and optional units (inverter 13,
The mailbox 15, duplex unit 16, bulk paper feed unit 17, and bulk paper discharge unit 18) are connected by the engine option interface (EOI/F) mentioned above. Furthermore, it is also possible to configure the system by omitting some of these units, or by replacing or adding various other optional units to the above units. Here, the printing operation by each part within the engine body 10 will be briefly explained. As paper supply sources, an upper paper feed cassette 11, a lower paper feed cassette 12, and a bulk paper feed unit 1 of the engine main body 10 are used.
7 and duplex unit 1 (only when refeeding paper) is selected, paper is fed, and registration roller pair 1 is selected.
Wait at the position sandwiched by 0B. Meanwhile, the photosensitive drum 101 rotates in the direction of the arrow, and the optical writing unit 103 irradiates the surface charged by the charging charger 102 with laser light modulated according to the video signal while main scanning in the direction of the drum axis. and expose
Form a latent image 2. Develop the latent image with toner from the developing device 104, and apply the toner image to the registration roller pair 10.
8, the transfer separation charger 105 transfers the image onto the paper fed to the image transfer section at a predetermined timing, and separates the transferred paper from the surface of the photoreceptor drum 101.

The paper onto which the image has been transferred is conveyed to the fixing unit 107, where it is heated and fixed by a fixing roller heated to a constant temperature and a pressure roller. It is sent to the inverter 13. Then, the paper discharged from the engine body 10 and sent to the inverter 13 is sent out from one of the three outlets A, B, and C at the top, side, and bottom, and is sent to the upper paper discharge tray 14, It is discharged to mailbox 15 and duplex unit 1st.

If the paper is ejected to the duplex unit 16, the first
, the second conveyance path to the engine main body 10, or discharged to the bulk paper discharge unit 18.

Next, FIG. 13 shows a block configuration of an engine control section (engine driver) 30 that controls the engine main body 10 and the above-mentioned optional units connected thereto.

The CPU 3l is a central processing unit that centrally controls the engine control section 30, and uses a general-purpose 8-bit microcomputer.

32 is a program ROM, which stores microcode for controlling the sequence of the engine main body 10 and the connection with the controller 2 and each of the above units (engine option units).

33 is a RAM for storing control data, engine status, etc.

34 is an interval timer for creating a basic time for engine sequence control.

35 is the engine option interface (EOI)
/F), and the inverter 13, which is an optional unit,
This is a serial interface for connecting the mailbox 15, the duplex unit 1, the bulk paper feed unit 17, the paper discharge unit 18, etc. via a common line. Therefore, it has a serial communication function.

Each option unit has the device I described above.
D is set, and when communicating between this engine control section 30 and each option unit 13.15 to 18,
By sending a command with the logical ID assigned to that device ID, the other unit is identified,
Receive a response from that unit.

36 is a controller interface, which is an interface for receiving commands from the controller 2 via LPVI and for notifying the controller 1 and the controller 2 of the status of the engine 3.

37 is an optical control section, which receives image signals (video data) sent from the controller 2 via the LPVI and controls the optical writing unit 103.

38 is an A/D converter, which is a thermistor (temperature sensor) of the image forming/paper transport section 100 of the engine body 10.
An analog signal is amplified and input by an operational amplifier 41, and is converted into a digital signal so that the CPU 31 can perform arithmetic processing.

The thermistors are used to determine the temperature status of each unit within the machine, and are provided at several locations within the machine.

39 is an I/O port, which operates the motor, plunger, clutch, etc. in the image forming/paper transport section 100 of the engine main body 10 through the driver 42 and driver 43, and applies high voltage to various chargers. Signals from sensors, switches, etc. for controlling the power supply and detecting the state of the engine body 10 are inputted via the amplifier 44 as signals amplified to a logic level.

Each of these parts is connected to the CPU 3l by a CPU bus 40 consisting of a data bus, a control bus, and an address bus.
It is connected to the.

Communication between the controller and the print engine Next, communication between the controller and the print engine will be described.

First, the communication conditions between the controller and the print engine are as follows.

1. Interface: Asynchronous serial I/F2. Communication speed: 9 6 0 0 baud3. Parity bit: None4. Stop bit: 1 As mentioned above, communication between the controller and print engine is via LPVI and uses four types of signals: /PETXD,
/PERXD, /PECTS, and /PEDTR.

We briefly explained the signals for these interfaces earlier, but now we will explain them in more detail. (L)/PERXD This signal is a serial communication receive data signal line for sending commands from the controller to the print engine. (2) /PETXD This signal is a serial communication transmission data signal line that sends responses and event reports from the print engine to the controller.

(3) /PEDTR This signal is a serial communication ready signal line for command transmission. When this signal is ゜L゜, it indicates that the controller can send commands to the print engine. The print engine must hold this signal at 0°L except during power-up or initialization operations (including when establishing system configuration).

(4) /PECTS This signal is a serial communication ready signal line for transmitting a response or an event report.

When this signal is ``L'', it indicates that the print engine may send a response or event report to the controller. The controller must hold this signal "L-" except when the power is turned on or when it is unable to communicate with the print engine.

If the print engine receives too many event reports while this signal is at °H, it may discard old event reports.

Next, the communication protocol between the controller and print engine will be briefly explained.

When communicating between the controller and print engine,
This is done by sending a command from the controller to the print engine, which receives it and sends a response back to the controller.

Each command consists of a 1-byte argument and an operator, and as shown in FIGS. 14(a) and 14(b), the most significant bit of the argument is always "1" and the most significant bit of the operator is always "1". It is 0°.

The command sends the arguments first, then the operator. The argument can be omitted, and the print engine must still correctly recognize the command without that argument. If a command that consists of an argument and an operator (for example, a ``status request'' command) is issued by the controller without an argument, the previous argument for the same command effectively takes effect. When the print engine receives a command, if there are no valid arguments, the print engine takes the default value as the de facto argument. The response is from the print engine to the controller,
It sends the information requested by the received command. The length of each response is 1 byte, and its most significant bit is ゜0゛, as shown in Figure 14 (Q). However, in the case of a response to the "illegal command" shown in Figure (d), all bits are "1".The event report indicates that an event (jam occurrence, supply shortage, etc.) has occurred in the optional unit or print engine. Sometimes, the print engine sends unsolicited information to the controller as a response.Each event report consists of one event report, as shown in Figure 14(e).
It has a length of byte, the most significant bit of which is 61°. Whether or not to generate this event report is determined by the controller using the 'ETB' command. The types of commands issued by the controller in this embodiment are as follows: 13 basic commands and 3 enhanced commands.

<Basic commands> 1. Status request 'ENQ'2
．． Ink eye input tray condition 'SI'3. Ink Eye Output Tray Container 'so'4. Ink Eye Paper Size of Input Tray 'EM'5. Main feed start 'F F'6. Main print start 'VT'7. Book input tray select 'DCI'8. This output tray selection 'DC2'9. Event report enable 'ETB'10. This print engine mode set 'DC4'11. *Paper size set
'DC3'12. Inquire exited paper ID
r ID) ' A C K '13. Reset 'CAM' enhance command> 14. Assign device ID 'FS'
15. Inkaire Assign Device ID 'GS
'16. Inquire Communication Active Device ID 'RS' Among the above commands,
Commands marked with this mark are stored in the command queue buffer and executed sequentially.

However, for the commands “Input Tray Select,” “Output Tray Select,” “Print Engine Mode Set,” and “Vapor Size Set,” if a command with an argument is issued before a command with another argument is issued, If neither a ``feed start'' command nor a ``print start'' command follows, the previous command is deleted from the command cue buffer and has no effect.

This means that if not followed by any 'F F' or 'VT' commands, the tray, paper size or mode specified by the command will be changed to the selected tray, selected paper size or selected mode. It means not to be.

These commands are not valid for previous "feed start" or "print start" commands.

The print engine is ``Input Tray Select'',
The mode or status specified by the "Output Tray Select", "Print Engine Mode Select", or "Paper Size Set" commands is held until the status or mode is subsequently reselected by these commands.

The print engine never clears the contents of the command queue buffer itself; it clears it by commands it receives from the controller. Also, the 'FF' and 'VT' commands in the command cue buffer are deleted at the start of their execution. If mode set and tray select are done properly and a sufficient number of 'F F' and 'VT' commands are stored in the command cue buffer, or 'F F'
and 'VT' commands are issued by the controller at appropriate time intervals, the print engine executes these commands at maximum throughput (print speed).

A general command issuing sequence for the controller to request the print engine to execute printing is shown below.

l) Input tray selection Select the input tray containing the duplex input unit. If the argument is omitted, the previous tray is valid.

Furthermore, even if the "input tray select" command is not issued, the previous tray is valid.

2) Output tray selection Select the output tray containing the duplex output unit. If the argument is omitted, the previous tray is valid.

The previous tray is also valid even if the ``Output Tray Select'' command is not issued.

3) Send a feed request "feed start" command. If this command is not issued, the next 1' print start" command is valid for feed and print.

4) Print request Send the ``print start'' command.

The controller also determines that if the ``/PRINT signal ignore flag'' in ``11 system current mode'' is ``0'',
It is also possible to request the print engine to perform printing using a "print request sequence handshaked by /PRINT and /PREADY." Note that "/" in front of each signal means negative logic (low active).

This request is executed prior to the 'F F' and 'VT' commands. However, it is not stacked within the command cue buffer. The print request sequence is valid only in real-time execution.

If the controller does not request printing by the /PRINT signal, it can change the print engine mode by issuing the 'DC4' command.
It is best to set the mode to ``ignore INT signal'' mode.

If the print engine has a /PRINT signal and 'FF
If a print request is received with both ' and 'VT' commands, serious errors in command execution may occur due to command timing and sequence.

The controller queries the print engine's current status (eg, which input tray is currently active) just before requesting the print engine to perform a print via the /PRINT signal line.

Commands stored in the command queue buffer (
Responses to commands marked with an asterisk (*) are sent by the print engine immediately after receiving the command, not when the command is executed.

Therefore, the content of the response may sometimes differ from the actual status of the command execution.

For example, after responding to the ``Input Tray Select'' command, if a cassette of a different size is installed in the selected input tray, the actual paper size will be determined by the print engine as a response to the ``Input Select'' command. The size will be different from the one sent.

In such a case, the print engine status becomes an error state (input size mismatch).

For the ``Status Request'' command, which is a command that queries the currently active input tray, currently active output tray, and the current mode status of the system, the print engine will respond to the ``F F'' command or the first 2-mode 'VT'
Returns the currently active tray specified for the command, or the currently active mode at the time.

The print engine will not respond to tray codes or modes specified by commands that have not yet been executed in the command queue puffer.

The capacity of the command queue buffer should be as large as possible; it depends on the maximum print speed of the print engine, but if the print engine print speed is less than 20 pages/minute, the capacity of the command queue buffer should be as large as possible. It is enough to have it.

While the print engine is executing a 'FF' or 'VT' command, if the controller wants to change the currently active input tray or output tray because the paper is empty or the paver is full. , the controller first issues a "command queue buffer clear" command and then reselects a new input tray or output tray.

In some cases, the print engine must predict the status of each unit and predict a response depending on that predicted status.

For example, a duplex unit overflow or vapor empty status is expected due to dependencies on previous commands, even though the previous commands are still in the command buffer and have not yet been executed.

Between the print engine and options Shinji will explain the communication between the print engine and its various additional devices, the option units.

The communication conditions between the print engine and the optional unit are as follows, similar to the communication conditions between the controller and print engine described above. 1. Interface: Asynchronous serial I/F2. Communication speed: 9 6 0
0baud3. Parity bit: None4. Stop bit = 1 The communication protocol was briefly described earlier in the explanation of the basic system configuration, but will now be explained in more detail.

In this case as well, communication from the print engine to the option unit is performed by sending commands, and communication from the option unit to the print engine is performed by sending responses.

An example of the format of this command and response is shown in FIG.

One command consists of an operator and an argument, and arguments b7 to b5 are always ゜111.
.degree., and b7 to b5 of the operator indicate the logical ID code of the optional unit with which the print engine wants to communicate.

Operator also serves to signify the end of one instruction.

The types of commands used in this embodiment are as follows.

<Basic command> ■. Inquire unit status
+ Honki *10001”2. Inquire paper size
” *Book*lOO1083. Inquire unit condition
tion) ” *Book $10011”4. Inquire unit availability
unit availability) ' *
* * 1010 0°5. Inquire unit specification #1
specification #1) ” * * *
10101°6. Inquire unit specification #2
cation #2) ” * *Thursday 10110”7
．． Ink Air Unit Specification #3 (I
quire unit specification
$3) ” * * * 10 1 1 1 ”8.
Inquir Excited Paper ID (Inquir
e exited paper ID) ” *
*11000"9. Inquire unit firmware version
ware version) ” *Kuki 11111-
10. Tray selection
"Kikimoto00001゜11.Mode setting"
* * * O O 010 ”12.Paper size setting
“Tree*Tree00011”13. Paper feed start 14. Paper feed stop 15. Paper feed restart 16. Paper eject start 17. Paper eject end 18. Initializing 19. Abort 20. Length of print engine
path)21. Registration distance 2
2. Transport velocity゛*Toku0
0100"゜*Kimoto00101゜゜Kimotoki00110"゜Kimotoki01000" ゛moto**01001゜゛Kiregi01110- ゛Kimotoki01111゜゜Zeromotoki01010゜゜*Kimoto01011- ゛*Zero* 01100゜〈Enhance command〉 23. Assign Device ID (Assign Device IQ)
' *Kimoto 11001" 24. Inquire assigned device ID (Inquire assigned device ID)
Device ID) “KIZERO*11010”25
．． Inquire Device IQ
” *木木11011゜These commands are always executed in real time by the optional unit.

Each option unit has the specified tray selection, mode set, paper size set, print engine path length, registration distance, W1 feed speed, and designated device ID.
mode, status, or designation until reselected by these commands.

Commands must be sent with arguments first and operators after, but arguments for commands that consist of arguments and operators can be omitted, and option units must correctly recognize commands without arguments.

For example, if a command consists of an argument and an operator, such as the “Inquiry Unit Status” command, and the print engine sends it without an argument, the previous argument of the same command to the same logical ID unit is valid as the effective argument. be.

However, 'Page Ext Start' command, No. 15
"Assign Device ID" command shown in Figure (b) and ``Ink Eye Device ID''' shown in Figure (d)
Excludes commands. Previous arguments never take effect in these commands.

Furthermore, arguments to other commands and arguments to other logical ID units are invalid under any circumstances.

If there are no valid arguments on the option unit side when a command is received, the option unit must take the default value as the effective argument.

The response is a message sent from the option unit to the print engine, indicating that the command has been received. All responses are 1 byte long,
b7 is set to ゛O゜.

If the option unit does not support the functionality of the received command, the option unit will respond with <7Fhax>, i.e. '011141'.
11° must be returned.

Figure 15(b) shows the format of the ``Assign Device ID'' command that the print engine sends when assigning a device ID to a logical ID, and the response sent from the optional unit that receives it. .

The arguments b3 to bO of this command contain the device ID code to be assigned, and the operator's b7
~bs (indicated by *) is the logical ID to be assigned
Enter the code.

For example, if this command is "111xOO10,00011001°,"
Assign the device ID ``0010゜ (INF#3: Mass paper feed unit 17, corresponding to the mass paper feed device 5B in Figure 3) as the logical ID 'OOO゜ (IN#1).''
will be ordered.

On the other hand, the CPU of the optional unit with device ID "0010" (in the previous example, the large paper feed unit 17)
recognizes it and returns a response of “00000010°.

This is "device ID"0010" and logical ID"o
The answer is "I assigned it as 00° (IN#1)."

Here, although the device ID code does not have a unit type code, the two bits b6 and b5 of the logical ID code are the unit type code, and in this example, ゛OO゜ represents an input unit, so it can be distinguished. FIG. 15(c) shows the ``Inquire Assign Device ID'' command, which is a command to inquire about the device ID of an option unit assigned to a specific logical ID, and the response to the command. For example, "00011010-" inquires of each option unit what is assigned to the logic/L/ID "OOO".

Then, if the option unit with the assigned device ID is a mass paper feeder, then the response "゜00000010" (input option unit '0010' is assigned to IN#1 of O logical Ii) will be returned.

FIG. 15(d) shows the "Inquiry Device ID" command that inquires whether a specific optional unit is communicable or not, and the response thereto.

Enter the device ID code to be queried in arguments b3 to bO of this command, and the unit type code in b7 and bs of the operator. For example, ゜111×OO
10, oOX11011° is a command for inquiring whether communication is possible with the input option unit °0010° (mass paper feed unit 17).

If the mass paper feed unit 17 is assigned. ”It will return a response of OOOXOOICI.

Also, as mentioned above, command operators b7 to b
If 5 is the global ID address "110", it indicates that the command is a global ID command.

When a global ID command is sent from the print engine, all optional units that are in a communicable state must perform the cooling operation according to this command as much as possible. However, the option unit does not issue a response to this command, and the print engine can issue the next command without waiting for a response.

Initial Setup Next, the initial setup of this laser printer system will be explained with reference to FIGS. 16 and 17.

FIG. 16 shows the relationship between signal transmission and reception and operations among the operation panel, host system, controller, print engine, and each option unit during initialization, and FIG. 17 is a flowchart showing the operation of the print engine.

Mainly referring to FIG. 17, the print engine sends initialization commands to all additional devices (option units) when the power is turned on and upon receiving an initialization command from the controller.

This initialize command may be a global ID command.

Then, the print engine itself executes initialization and self-diagnosis and initializes, and all communicable additional devices that have received the initialization command also execute initialization and self-diagnosis and initialize.

After that, it is determined whether this printer system is an enhanced system or not, and if YES, it is an enhanced system, so the communication enabled/disabled status of all device IDs (48 ID) is confirmed at least twice, Each device I
When the state of D becomes the same as in the previous cycle, the state of each device ID is determined.

The reason for checking the coincidence of the two confirmation results is to avoid erroneously determining the state of the additional device which is in an unstable state such as a transient state when the power is turned on or off.

Next, one device ID is assigned to one logical ID in order of priority to establish a system configuration.

Here, the following priorities are 1 and 2.

Priority 1: Communication active device Priority 2: Younger device ID code On the other hand, if it is not an enhanced system, it is a thick system, so the communication enabled/disabled state of all logical ID units (5 IDs) must be changed more than once. Once the status of each logical ID unit is the same as the previous cycle, the status of each additional device is determined and the system configuration is established.

Note that the print engine must not issue any commands to any option unit while it is initializing itself.

Also, while any optional unit is initializing itself,
Do not send any responses to the print engine.

After establishing the system configuration, the print engine can communicate with the controller, but until then, the /PEDTR signal, which is a ready signal for communication with the controller, must be turned off.

<<About status information response>> Next, a status information response according to the present invention in this laser printer system will be described.

18 to 20 show a detailed flow of communication for the controller 2 to check the status of the print engine 3 and a specific option unit.

Further, FIG. 21 shows the print engine status code responded to by the print engine and its contents, and FIG. 22 shows the option input/output unit status code responded to by the option unit and its contents.

Using these diagrams, an overview of the communication between the controller, print engine, and optional units will be explained. First, as shown in FIG. 18, the controller sends a "printer general status" code (a shortcut code indicating the general status of the printer) to the engine. Bit bo''b6=O of this command indicates a request for general status.

In response, the engine returns the response, and each bit of bo-b6, ゜1゜ or ゛0゜, indicates the general status of the printer. Next, the controller sends a "print engine status" command to the engine to inquire about the status of the engine section.

If bit b6 of this command is 0, the engine tells the controller that it has the highest priority among the currently existing engine statuses (priority 1 of the "Print Engine Status Code" shown in Figure 21). →64), and if there is no information to return, set bit b6 of the response to 1 degree, and bits b5 to b
O sends an undefined response.

If bit b6 of the response is 1, the controller stops inquiring the status of the engine at that point and moves on to inquiring the status of the next unit. If bit b6 of the response is ``0'', there is still status information to be known in the engine status buffer, so a code is sent to the engine again to inquire about the status.

At this time, if bit b6 of the command is not set to 1°, the highest priority information will be sent again, so in order to inquire about the next priority status, set bit b6 to 1° and issue the "Print Engine Status" command. The status information of the next priority is obtained based on the response from the engine.

The controller must continue asking questions until bit b6 of the response becomes '1'. In this way, the controller can know all the current engine conditions.

The status code returned by the response follows the table agreed between the engine and the controller as shown in FIG.

After completing the status inquiry to the engine, the controller moves on to inquiry to the engine about the status of each additional device (option unit).

Its inquiry command is ``input unit #
1 status", bits b5 to b0 are ゜001001
It is ゜. When the print engine receives this, it sends the 'ink eye unit status' to input unit #1.
Send a command and receive a response from input unit #1.

The existence information of the state during this time is also exchanged. As in the exchange between the controller and the engine, a bit (
b6), and the answering side has a bit (b6) in the response that indicates whether the status buffer for storing the state is empty, and the controller inputs it to the engine until it knows that the status buffer is empty. Yutsunit #
Inquire about the status of 1.

The status code returned by the response follows the table agreed between the engine, controller, and option, as shown in FIG.

The engine transmits the status information obtained from input unit #1 in this way to the controller in a response.

Similarly, the controller sequentially inquires about the status of input unit #2, output unit #1, output unit #2, and duplex unit via the engine.

Here, the response example of the engine unit status is shown in the 23rd example.
As shown in the figure.

In this example, in the print engine, there is no paper in the paper feed tray in use (B), and cover open #1 (C).
and paper jam I$1CD) occurred at the same time, and then toner shortage (addition required) (A) occurred, then the problem of no paper in the paper feed tray in use (B) was resolved, and then (C) above. It is assumed that (A) is resolved after and (D) are resolved at the same time. The priority order of each status (state) is (D), (C), (B), and (A).

In the figure, 'ENQ' is the "print engine status" command, INPS is the command argument bit be (a flag that asks for the next priority position when it is "1-"), and SBE is the response bit be ("1 degree"). (Flag indicating that the status buffer is empty when

This command has an argument of 8 in hex code.
0H *Since the operator is 'ENQ' (05H in hex code), it is expressed as 80H 'ENQ' and is one of the status request commands, which inquires about the general status of the engine system including optional units. be.

Each bit of the response indicating the status from the print engine in response to this command is as follows.

Response (Status): b7: 'O' b6: There is paper in the system paper path b5: There is a discharged paper ID in the wandering paper ID buffer b4; Paper jam is fixed b3: Print start ready (registration point ready) b2: Paper feeding starts (During feeding) b1 = Status group code 1 bo = Status group code Q (Explanation) 1. "Paper present in system paper path" Paper feeding starts from any input tray (excluding duplex unit), and This flag is set to ``1'' when there is any paper in the paper path of the engine system, including the duplex bus, that has not been fully ejected to any output tray (excluding the duplex unit). Ru.

If there is no vapor in the paper path of the engine system, this flag is set to ``0''.

2. The flag "Discharged paper ID exists in the discharged paper ID buffer" is set to ``1'' when one sheet of paper has completely wandered to the output tray other than the duplex unit. This flag is set to 0 when the discharge ID buffer becomes empty by issuing event report #3 or by issuing a response to the 'ACK' command.

If there are still paper discharge IDs left in the paper discharge ID buffer, this flag remains at 1 degree, indicating that the paper discharge ID buffer is not empty.

The controller is 'INKIA EXIT PAPER ID
”: By issuing the 'ACK' command, the paper discharge ID can be asked.

3. ``Paper jam fixed'' In some cases, even if a jam (paper jam) occurs in the engine system during printing, the paper other than the jammed vapor may be transported and ejected to the output tray. Then, the jammed paper is fixed when the discharge of other papers is completed. The engine sets this flag to ``1'' when the jammed paper is fixed.

When this flag is 1°, the controller can ask for the Jamvapa ID pick-up by issuing a status request command.

When the engine confirms that there is no paper remaining in the paper path after the jam recovery operation is performed, it sets this flag to 0°.

4. "Print Start Ready" This flag is set to 1' when the fed paper is ready to be printed at the registration position.

When no paper is waiting to be printed at the registration position, this flag is set to 0.degree.

When this flag is "1", the engine is set to 'VT'.
Start printing to execute the command.

Depending on the correct print sequence, the controller will
A print start command may be sent without waiting for this flag.

5. "Start feeding (feeding)" This flag is set to ゜1゛ when the engine starts feeding one sheet of paper.

This flag is set to '0' when the engine is ready to begin feeding the next paper from the input tray currently in use. The timing to set this flag to ``0'' depends on what tray will be used next.

6. "Status Group Code" This 2-bit flag indicates the general status of the entire engine system.

The meanings of these flags are shown in FIG.

The status indicated by this status group code depends on the event report enable state.

It means that the status group code changes according to the bit bltbo of the argument of the 'ETB' command, which is the 'event report enable' command.

FIG. 25 shows the relationship between bits b1 and bo and the contents of the general status indicated by the status group code.

<<Regarding Notification of Event Report>> Hereinafter, the features of the present invention according to this embodiment will be described in detail.

According to this embodiment, when a change in status occurs in the printer system (engine + option units 1 to 1), the engine can notify the controller 1 to the controller by an event report that is an asynchronous message.

Therefore, the method for setting whether or not the controller can send asynchronous messages to the engine is based on the LPV
The /PERXD signal of I sends a command for setting whether or not to send an asynchronous message (event report) from the controller 2 to the engine 3 shown in FIG.
As shown in figure (A), (argument + 'E
Send the command ``Event Report Enable'' consisting of [T B '].

In response, the engine 3 sends information 0 0 H as to whether transmission is possible or not.
ex~7 F Hex as response/PETXD
The signal is sent back to the controller 2.

Here, 'ETB' for 'Event Report Enable'
About commands and responses to them, Part 2
This will be explained with reference to FIGS. 6(A) and 6(B).

This 'ETB' command is a command for enabling or disabling the engine to transmit various event reports for each event report number.

Format: “Argument” + ‘ETB’ (1 7he
x) Argument; b7: 1 b6~b2=Event report number bt tbo: Event report enablement condition Response: ゛'Enable flag b7: "O" b6~bz=Event report number bt, bo: Event report enablement condition default: Power The default enable state immediately after up or initialization is that bits bx,bo are ゜oo゜ for all event report numbers, and the engine is prohibited from sending any event reports.

It is desirable for the controller to check the engine diagnostic results after completing the initial settings. Therefore, 'ETB'
Set the command to default to prevent event reports from being emitted by the engine. After the initial configuration is complete, the controller can then ask about the status of the engine or enable the generation of event reports.

Here, the state changes that may occur in the engine are shown in Figure 26 (
As shown in A), it is divided into 12 types, an event report number is added as its recognition number, and it is assigned to bits b6 to b2 of the argument of this command.

Then, an instruction to designate transmission enabled or transmission disabled is assigned to bits b1 to bO.

Among these, for event report #4, whether or not it can be sent is divided into the following four levels. Bit bi, b(, ゛1 1゜; Sends all the states that have occurred to the device.

'10-; Sends all statuses that have occurred to the currently selected device or the error status of a serviceman call that has occurred to a device that is not currently selected.゜0 1゜; Sends all states that occur only to the currently selected device.

゛OO゜; No matter what happens, an event report will not be sent.

For other event reports, whether they can be sent or not is not divided into levels, but whether they can be sent or not is specified.

The controller sends an 'ETB' command to the engine using these arguments, thereby setting whether to send an event report.

When a state change occurs in engine 3, if it is specified that transmission is possible, the state change will be sent from the engine by 80Hex”F
F Hex code as event report/
It is sent to the controller 2 by the PETXD signal.

The format of this event report is shown in Figure 14 (e).
It consists of 8 bits as shown in .

Here, the event report will be explained in more detail.

The engine system has an event report enable condition of 'E'.
All state changes (events) that occur within the engine system while specified by the controller with the TB' command are stacked in the event buffer as an event report.

The engine then issues seven consecutive event reports if the /PECTS signal is active. Adequate event buffer capacity will depend on the scale of the engine system, but a number of events between 20 and 3o may be sufficient. Next, each event report number will be explained.

A. Event Report #0 (Paper Feed/Print Event) This event report is sent to the controller when the paper feed starts or when the paper is in the register position and ready for printing.

Report: b7 ~ b2: "100000" b1 = Print start ready (ready at registration position) bO = Paper feeding start (feeding in progress) Print start ready This flag indicates that the fed paper is ready for printing at the registration position. It is set to ``1'' when the

When there is no paper waiting to be printed at the registration position, this flag is set to 0°.

This event report indicates that this flag is from ゛0゜ to ゛1.
It is issued the moment the temperature changes to ゜, and it is not issued when the temperature changes from ゜1゜ to ゜0゜.

When this event report is issued due to the start of paper feeding, this flag is fixed at 'O'.

Feed Start This flag is set to '1' when the engine system starts feeding a sheet of paper. Then, when the engine system is ready to start feeding the next paper from the paper feed tray currently in use, this flag is set to °O°.

The timing at which this flag is set to 0° depends on what tray will be used next.

This event report indicates that this flag is from ゜○゜ to ゛1.
It is issued the moment the temperature changes to ゜, and it is not issued when the temperature changes from ゜1゜ to ゜0゜. When this event report is issued for "print start ready", this flag is fixed at 0.

B. Event Report #4 (General Status Group Code) This event report is sent to the controller when the status within the engine system changes.

Report: b7~bz: "100100゜b1 = General status group code 1 bo: General status group code 2 This "general status group code" flag indicates the general status of the engine system, and the flag's The meaning is as follows.

For details, see Figures 21 and 24.

b1 bO Error name 0 0 No error (ready) 0 1 Caution 1 0 Busy 1 1 Error The status indicated with this status group code depends on the event report enable condition. Please refer to FIG. 25 regarding this possible condition.

C. Event report #5, #6, #7, #8
, #9 Event report #5 Input unit #1 status group code event report #6 Input unit #2 status group code event report #7 Duplex unit #2 status group code event report #8 Output unit #1 status group code event report #9 Output Unit #2 Status Group Code These event reports are sent when the level of the "Status Group Code" of each unit changes.

Report: b7: "1" b6 to b2: Event report number b1; Option unit status group code 1 b2 = Option unit status group code O The "Status group code" of each unit is the same as the "Option unit general status" .

D. Event report #12 (first jam paper ID) This event report is sent to the controller when the jammed paper position is fixed, that is, when the ``paper jam fix flag'' in ``Printer General Status'' changes from ゛0゜ to ゜1゜. Sent. Report: b7~b+: "1011°B3~Bo: First jam paper ID (refer to printer general status code in Figure 21) E. Event Report #16 (Input Tray Paver End) This event report is sent to the controller when the status of any input tray in the system changes between paper empty and paper present.

Report: b7~b+: ”1100゜b3: ”x” (Preliminary {i!) b2: Paper end/exist b1t bo: Input unit number If the status of any input tray of either input unit is empty paper When the state changes, the bits bt,b
Set o to the input unit number and set bit b2 to ゜1
This event report is sent with this setting set to .

Then, when the input tray state of any input unit changes to the state where paper is present, set bits t) 1 p b (3 to the input unit number and set bit b2 to ゜O゜). An event report will be sent.

F. Event Report #20 (Output Tray Paper Full) This event report is sent to the controller when the state of any output tray in the system changes between vapor full and paper not full. Sent. Report: b7 to b4: ”1101゜b3: ”x” (spare) b2: Paper full/not full bi, bo: Output unit number Either output tray status of any output unit is full of paper When the state changes to , bit b1
1 This event report is sent with bO set to the output unit number and bit b2 set to ゜1゛. 6 Then, the output tray status of any one of the output units changes to not full of paper. When this happens, this event report is sent with bits bl and bo set to the output unit number and bit b2 set to '0'. G. Event Report #24 (Ejected Paper ID) This event report is sent to the controller when a print cycle is completed and a sheet of paper is completely ejected to the specified output tray. Report: b7~bz: '1110°B3~BO: Wandering Paper ID H. Event report #28 (Fun configuration change) This event report is sent to the controller when the system configuration (valid configuration state) changes.

Report: b7-b. : '1111゜b3: Communication possible flag b2~bo: Logical ID code communication possible flag is set to ゛1゜ when the option unit to which the specified logical ID code is assigned can properly communicate with the print engine. be done.

This flag is set to 0.degree. when communication between the assigned option unit and the print engine becomes impossible due to power being cut off or some communication being destroyed.

This event report is issued both at the timing of the change from ゜0゛ to ゜1゛ and when the change from ゜1゜ to ゛0゛.

Event reportability conditions a. For event report #0 b1: 1/O: "Print start ready" event enable/disable b o: 1/O; "Paper feeding start" event enable/disable b. See Figure 25 for event report #4.

C. For other event reports b1: 'x'; Reserve bo: 1/O; Event report enable/disable As explained above, according to this embodiment, the controller can control the printer system with one type of control command. (engine + additional equipment). To know the status of the printer system, see Figures 5 and 13.
In response to the LPVI /PERXD signal shown in the drawings, the controller 2 transmits a "printer general status" command (801-4'ENO'), which is the state detection command described above, to the engine 3.

In response, the status information response from engine 3 is /P
The ETXD signal is returned from 7 to controller 2. In addition, before Controller 2 sends this command, the ``Event Report Enable'' command (argument + 'ETB': specify the range of each device (engine or additional device) whose status information is reflected) is required. ) is sent to the engine 3 by the /PERXD signal, the status information for the devices within the specified range is sent to the controller 2.
will be returned to.

Here, with reference to the flowcharts in FIGS. 27 and 28, we will explain an example of how the controller specifies the device range of status information and the subsequent reading process when the power number is turned on and when there is a print request from the host system. do.

Processing when the power is turned on is performed as shown in FIG.

Since the controller 2 needs to know the state of the printer system in advance in the initial state, after self-checking and internal initialization, it sets the enablement conditions for the 'ETB' command (argument bits bt, bo) to the engine 3.
), and then send the 'Printer General Status' command 80H'ENQ' to read the printer general status (one information code that shows the current status as a group). This allows you to know the status of the entire printer system.

If the printer general status indicates a ready state, the controller 2 can proceed to the next process without making inquiries to each device.

When the printer general status indicates a state other than ready, the printer queries and reads the details of the status (contents of the status in the status group code shown in Figure 21) that is the reason why it does not become ready for the first time, and then reads the details. It is sufficient to display a warning on the LCD display 250 shown in FIG. 7. Next, the processing during the printing operation will be explained with reference to FIG. 28. When a print request is received from the host system, the controller 2 is activated according to the data processing flow shown in FIG.

Then, the print control unit 203 extracts instructions for paper feeding, paper wandering destination, and print mode (single-sided or double-sided printing) from the print control file 22g, and
The settings are made for engine 3.

Once the paper feed, paper output destination, and print mode are determined, in the system shown in Figure 12, the additional devices that will be activated during the print operation are determined, so it is necessary to manage the status of devices unrelated to the print operation. can be ignored.

Therefore, after setting the enabling condition of the 'ETB' command to the engine and sending it to ``0 1'' (see Figure 25), send the ``Printer General Status'' command 80H 'ETB' to confirm that it is selected. By reading the printer general status (group code) that indicates the status of only the devices that have been used, management during busy image processing is possible.

The loaded printer general status is ready (R
aady) or Caution, image processing and printing are executed, and this can be repeated until printing is completed. If the printer general status indicates an error state during printing, the details of the error can be postponed and the error processing must be carried out immediately.
First, output a busy message to the host system, etc.), then inquire about the specific error content, read the status details, and display the LCD shown in Figure 7.
Processing such as displaying a warning on the display 250 may be performed.

In this way, it is possible to use the 'Printer General Status', which is one information code that shows the current status of the printer system as a group, and the 'ETB' command, which controls the range of devices to which the contents of that information code are reflected. Condition settings can be used effectively. In the embodiment described above, the controller 2 and engine 3 are built into the printer body 4 as shown in FIG. 4, but the controller 2' is installed in the host system 1' as shown in FIG. The laser printer system is also built-in and connected to Engine 3 via LPVI.
This invention can be applied in the same way.

Further, the present invention is applicable not only to laser printer systems but also to image forming systems using other page printers, digital copying machines, facsimile machines, and the like.

〔Effect of the invention〕

As described above, in the image forming system according to the present invention, the image forming apparatus and the additional device group the current status and convert it into one information code (printer general status) to the image processing apparatus (controller) or host The image processing device or host system can quickly grasp the status of the entire system.
Processing can be made more efficient and simpler. Further, when a change in status occurs in the image forming device or the additional device, it can be immediately notified to the image processing device as an asynchronous message.

At that time, if you can specify the type of state change using the identification number added to the group and select which state change should be notified to the image processing device when it occurs, the image processing device can immediately It is possible to efficiently notify only the information that the person wants to know. It is also possible to efficiently notify only the necessary level of information based on the importance of the state change and the device where the change occurred, depending on the type and operating state of the controller. Furthermore, by providing the image processing device or host system with means for controlling the range of devices to which the contents of the information code are reflected, it is possible to request information codes that match the current state of the image forming device or host system. This makes it possible to further improve the efficiency and simplification of processing, and even if the number of additional devices increases, it becomes easier to manage their status.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the system configuration of a basic embodiment of the present invention, FIG. 2 is an explanatory diagram showing an example of the configuration of commands issued from the main body of the image forming apparatus to each additional device, and FIG. 3 is a block diagram showing the system configuration of another basic embodiment of this invention, FIG. 4 is a block diagram showing the configuration of a laser printer system which is an embodiment of this invention, and FIG. 5 is a block diagram showing the system configuration of another basic embodiment of this invention. Figure 6 is a block diagram showing the configuration of the data processing flow and the RAM shown in Figure 5.
7 is an external view showing a specific example of the operation panel 25 in FIG. 5. FIG. Separate explanatory diagrams: Fig. 9 is an explanatory diagram showing the file format of the IC card 6 in Fig. 5; Fig. 10 is an explanatory diagram of ■ and PVI signals in this embodiment; Fig. 11' is an explanatory diagram showing the file format of the IC card 6 in Fig. 5; An explanatory diagram showing the relationship between the printing area and image No. 4H, Figure 12 is a schematic diagram of the engine main body and the mechanical parts of various optional units connected to it, and Figure 13 is a diagram of the engine control unit. A block diagram showing the configuration; Fig. 14 is an explanatory diagram of commands and responses used between the controller and print engine; Fig. 15 is an explanatory diagram of commands and responses used for communication between the print engine and each option unit; FIG. 16 is a flow diagram showing the operation of the entire system at the time of power-on and initialization in this embodiment. FIG. 17 is a flow diagram showing the operation of the print engine at that time. FIGS. A flowchart showing the exchange of commands and responses when checking the status of the print engine and option unit. Figures 21 and 22 also show tables of print engine status codes and option unit status codes used for communication. Figure 23 is an explanatory diagram showing a response example of the engine unit status. Figure 24 is an explanatory diagram showing the relationship between status group codes and the status levels represented by them. Figure 25 is an explanatory diagram showing the relationship between status group codes and the status levels represented by them. An explanatory diagram showing the relationship between b1, bg and the contents of the general status indicated by the status group code. Figures 26 (A) and (B) are flow diagrams showing part of communication for various parameter settings and inquiries, and Figure 27 figure. and FIG. 28 is a flowchart showing an example of device range designation of status information by the controller and subsequent reading processing when the power is turned on and when a print request is received from the host system, and FIG. 29 is another embodiment of the present invention. 1 is a block diagram showing the configuration of a laser printer system of FIG. 1, 1'...Host system 2, 2'...Controller (image processing section) 3...Print engine (image forming section) 4...Image forming device (
Printer) Main body 5, 5A to 5G...Various additional devices 10...Engine main body 13...Reversing device (reversing paper ejecting device) 15...Mailbox (multi-stage paper wandering device) 1 day...
Duplex unit (duplex conveyor H) 17...Mass paper feed unit (Mass paper feed haze) 18...Mass paper discharge unit (
Mass paper ejection device) 1 day...Printer table 20...Controller CPU 25...Operation panel 27...Option interface 29...Engine interface 30...Engine control unit (engine driver) 31.
・CPU of engine control section

Claims (1)

[Scope of Claims] 1. An image processing device that receives text information or image information from a host system and generates image information, and an image that receives the image information from the image processing device and forms an image on a recording medium. In an image forming system that includes a forming device and various additional devices that are removably attached to the image forming device and feed, eject, or convey the recording medium, and that these devices are connected via an interface, the image forming system The forming device and the additional device are provided with a means for grouping the current state into one information code and transmitting it to the image processing device, and when a change in state occurs in the image forming device or the additional device, the information code is transmitted to the image processing device. An image forming system comprising: a state change notification means for notifying the image processing apparatus as an asynchronous message. 2. An image forming device that receives image information from a host system and forms an image on a recording medium, and various additional devices that are removable from the image forming device and feed, eject, or transport the recording medium. In an image forming system in which the image forming apparatus and the additional apparatus are connected through an interface, the image forming apparatus and the additional apparatus are provided with means for grouping current states into one information code and transmitting the same to the host system, An image forming system comprising: a state change notification means for notifying the host system of a change in state as an asynchronous message when a change in state occurs in the image forming apparatus or an additional device. 3. Claim 1 or 2, wherein the image processing device or the host system includes means for controlling a range of image forming devices and additional devices to which the content of the information code is reflected in the information code. The imaging system described.