JP7073966B2 - Image processing equipment, its control method, and programs - Google Patents

Description

The present disclosure relates to the control of an image processing apparatus.

An image processing device such as an MFP (Multi-Functional Peripheral) includes an image forming unit including an element that executes image forming such as a photoconductor and a paper transport mechanism, and a control unit that controls the image forming unit. The control unit is realized by, for example, a control board in the center of the image processing device.

Conventionally, in the image processing apparatus, when a trouble occurs in a part, various techniques have been proposed for rebooting only the part where the trouble has occurred and continuing the operation of the other part. For example, Japanese Patent Application Laid-Open No. 2013-054314 (Patent Document 1) shows that when one CPU goes out of control in a plurality of CPU (Central Processing Unit) image forming devices, the other CPUs continue to function while running away. Discloses a technique for resetting a CPU. Japanese Patent Application Laid-Open No. 2016-175349 (Patent Document 2) interrupts a print job, stores print job information in a storage device, resets an image forming unit, and then resets the image forming unit when a failure occurs during execution of the print job. It discloses an image forming apparatus that connects an image forming unit and a control unit and restarts an interrupted print job. Japanese Patent Application Laid-Open No. 2017-046354 (Patent Document 3) reboots only the operation unit when an abnormality occurs in the operation unit in an image processing device operating on an OS (operating system) in which the operation unit and the image processing unit are different. Discloses the technology to be used.

Japanese Unexamined Patent Publication No. 2013-054314 Japanese Unexamined Patent Publication No. 2016-175349 Japanese Unexamined Patent Publication No. 2017-046354

In some conventional image processing devices, a processor that executes firmware (FW) for controlling elements such as a photoconductor is installed even in an image forming unit. The processor of the image forming unit is controlled by the processor of the control unit. In such an image processing device, the processor of the control unit may execute a job to be executed without using the image forming unit. An example of such a job is a job of transmitting data stored in a storage device of an image processing device to another device.

When a trouble occurs in the image forming unit, it may be possible to prevent the control unit from being unnecessarily rebooted by rebooting only the image forming unit. For example, if the controller of the control unit is executing a job to send data as described above, the processor of the control unit can be continuously executed without being unnecessarily rebooted.

However, troubles in the image forming unit may affect the processing of the control unit. In such a case, even if only the image forming unit is rebooted, a new trouble may occur in the image processing device.

The present disclosure has been conceived in view of the actual circumstances, and an object thereof is necessary while avoiding unnecessary rebooting of the control unit when a trouble occurs in the image forming unit in the image processing apparatus. It is to provide a technique for performing a reboot of the control unit according to the above.

According to a certain aspect of the present disclosure, an image forming unit for executing an image forming operation and a control unit for controlling the image forming operation of the image forming unit are provided, and the image forming unit is a driving unit driven for the image forming operation. And a control circuit that controls the drive unit. When the control unit detects the occurrence of the first trouble in the image forming unit during the execution of the print job, the control unit reboots to the control circuit without rebooting the control unit. Is provided, and an image processing device is provided that reboots the control circuit and the control unit when the occurrence of the second trouble is detected in the image forming unit before the end of the print job.

When the control unit detects the occurrence of the second trouble and is executing another job that does not use the image forming unit, the control unit may wait for the end of the other job and reboot the control unit.

The control unit may execute a job that uses the image forming unit in the first process space and a job that does not use the image forming unit in the second process space. The image forming unit may include a paper feed tray for accommodating paper used for a print job. The control circuit may transmit information for specifying the paper size in the paper feed tray to the control unit. The control unit may transmit a control instruction using information for specifying the paper size received from the control circuit to the control circuit for executing the print job.

The image forming unit generates correction information indicating the relationship between the image forming signal and the operation mode of the driving unit based on the image output by the driving unit according to a predetermined signal, and transmits the correction information to the control unit. You may. The control unit may transmit a control instruction using the correction information received from the control circuit to the control circuit in order to execute the print job.

According to another aspect of the present disclosure, in an image processing apparatus including an image forming unit that executes an image forming operation and a control unit that controls the image forming operation of the image forming unit, the image processing apparatus executed by the control unit. A control method is provided. The image forming unit includes a driving unit that drives for the image forming operation and a control circuit that controls the driving unit. The control method is a step of instructing the control circuit to reboot without rebooting the control unit when the occurrence of the first trouble is detected in the image forming unit during the execution of the print job, and the image before the end of the print job. When the formation unit detects the occurrence of the second trouble, the control circuit is instructed to reboot, and the control unit is provided with a step of rebooting.

According to still another aspect of the present disclosure, a program executed by a control unit is provided in an image processing apparatus including an image forming unit that executes an image forming operation and a control unit that controls the image forming operation of the image forming unit. Will be done. The image forming unit includes a driving unit that drives for the image forming operation and a control circuit that controls the driving unit. By executing the program, when the control unit detects the occurrence of the first trouble in the image forming unit during the execution of the print job, the step of instructing the control circuit to reboot without rebooting the control unit, and When the occurrence of the second trouble is detected in the image forming unit before the end of the print job, the step of instructing the control circuit to reboot and rebooting the control unit is executed.

According to the present disclosure, when the control unit of the image processing device detects the occurrence of the first trouble in the image forming unit during the execution of the print job, the control unit instructs the control circuit to reboot without rebooting the control unit. .. The control unit reboots the control circuit and the control unit of the drive unit when the occurrence of the second trouble is detected in the image forming unit before the end of the print job. This provides a technique for executing a reboot of the control unit as necessary while avoiding unnecessary rebooting of the control unit when a trouble occurs in the image forming unit in the image processing device. ..

It is an external view of the image processing apparatus 1. It is a hardware block diagram of the image processing apparatus 1. It is a figure for demonstrating the function realized by each of the main CPU 20 and the sub CPUs 30 and 31 of FIG. 2 executing a firmware program. It is a figure which shows an example of the structure of the virtual memory which the main CPU 20 manages in HDD 24. It is a figure which shows an example of the screen which is displayed on the display part 15 for inputting the setting of a print job. It is a figure which shows an example of the information (job information) which manages a job to be executed in an image processing apparatus 1. It is a sequence diagram of an example of communication between a controller FW201 and a mechanical controller FW301 of a printer unit 13. It is a sequence diagram of another example of communication between a controller FW201 and a mechanical controller FW301 of a printer unit 13. It is a figure which shows an example of the update mode of the job information according to an erroneous size information. It is a flowchart of the process executed for the print job by the main CPU 20. It is a flowchart of the subroutine of step S102 (detection of engine trouble) of FIG. It is a figure which shows the modification of the functional structure of the main CPU 20. It is a flowchart of the process executed by the main CPU 20 in the example of FIG. It is a figure for demonstrating another example of erroneous data transmitted from a mechanical control FW to a controller FW due to an engine trouble. It is a figure for demonstrating another example of erroneous data transmitted from a mechanical control FW to a controller FW due to an engine trouble. It is a figure for demonstrating another example of erroneous data transmitted from a mechanical control FW to a controller FW due to an engine trouble. 14 is a diagram showing a second modification of the functional configuration of the main CPU 20 corresponding to the processing described with reference to FIGS. 14 to 16. It is a flowchart of the process executed by the main CPU 20 in the example of FIG. It is a figure which shows an example of the configuration of the virtual memory managed for a FAX reception job. It is a figure for demonstrating the effect that the storage area used is separated for each process.

Hereinafter, an embodiment of the image processing apparatus will be described with reference to the drawings. In the following description, the same parts and components are designated by the same reference numerals. Their names and functions are the same. Therefore, these explanations will not be repeated.

[1. Appearance of image processing device]
FIG. 1 is an external view of the image processing device 1. As shown in FIG. 1, the image processing apparatus 1 includes a document transport unit 11 and a scanner unit 12 on the upper portion thereof. The document transport unit 11 automatically transports the documents placed on the document transport unit 11 to the scanner unit 12 one by one. As a result, the scanner unit 12 optically reads the characters, symbols, images, etc. recorded on the document.

A printer unit 13 is provided below the scanner unit 12. A paper feeding unit 14 is provided below the printer unit 13. The paper feeding unit 14 supplies paper to the printer unit 13. The paper feed unit 14 includes paper feed trays 14A to 14D, each of which accommodates paper.

The printer unit 13 executes a job related to copying, network printer, or FAX. More specifically, the printer unit 13 forms an image on the paper supplied from the paper feeding unit 14, and outputs the paper from the ejection port 19.

A display unit 15 and an operation unit 18 are provided on the front surface side of the image processing device 1. The display unit 15 displays to the user information about the job executed by the image processing device 1 and other information. The display unit 15 is realized by, for example, a liquid crystal display. The operation unit 18 accepts input of information to the image processing device 1 and includes a touch panel 16 and an operation button 17. In one example, the operation button 17 is arranged around the display unit 15.

[2. Image processing device hardware configuration]
FIG. 2 is a hardware block diagram of the image processing device 1. As shown in FIG. 2, in addition to the components shown in FIG. 1, the image processing apparatus 1 has a main CPU (Central Processing Unit) 20, a ROM (Read Only Memory) 21, and a RAM (Random Access Memory) 22. , Non-volatile memory 23, HDD (Hard Disc Drive) 24, NIC (Network Interface Card) 25, and FAX transmission / reception unit 26.

The main CPU 20 realizes basic functions (copy, network printer, scanner, FAX, etc.) as an image forming apparatus by reading a program (controller FW (FirmWare)) stored in the ROM 21 into the RAM 22 and executing the program. do. In the present specification, an element whose operation is controlled by a unique firmware is also referred to as a "mechanical element". The mechanical elements are, for example, a document transport unit 11, a scanner unit 12, a printer unit 13, and a paper feed unit 14. In the image processing device 1, the main CPU 20 that functions as an element for controlling a mechanical element is also referred to as a “controller”. The controller FW means a firmware program to be executed for the main CPU 20 to function as a controller.

The NIC 25 and the FAX transmission / reception unit 26 function as a communication interface in the image processing device 1 to enable the image processing device 1 to perform data communication with other devices. The communication by NIC25 may be wireless communication or wired communication. The FAX transmission / reception unit 26 communicates according to, for example, the G3-FAX standard, and is realized by a modem and a TA (terminal adapter). The program stored in the ROM 21 can be updated to the latest version of the program by downloading it from an external device via a network or the like.

The image processing device 1 further includes a sub CPU 30. The sub CPU 30 controls the driving of the printer unit 13 and the paper feeding unit 14, which are mechanical elements, by reading the program (mechanical controller FW) stored in the ROM 21 into the RAM 22 and executing the program. "Mechacon FW" means a firmware program for controlling mechanical elements. In the present specification, the printer unit 13 and the paper feed unit 14 may also be referred to as a “print engine”. The sub CPU 31 controls the driving of the document transport unit 11 and the scanner unit 12, which are mechanical elements, by reading the program stored in the ROM 21 into the RAM 22 and executing the program. In the present specification, the document transport unit 11 and the scanner unit 12 may also be referred to as a “scan engine”. The printer unit 13, the paper feed unit 14, the document transfer unit 11, and the scanner unit 12 may be collectively referred to as an “engine” in the present specification.

The main CPU 20 is an example of a control unit of an image processing device. The sub CPUs 30 and 31 are examples of control circuits of the drive unit.

[3. Functional configuration of image processing device (1)]
FIG. 3 is a diagram for explaining the functions realized by each of the main CPU 20 and the sub CPUs 30 and 31 of FIG. 2 executing the firmware program.

<Function of main CPU 20>
In FIG. 3, the function realized by the main CPU 20 executing the program of the controller FW is shown as the controller FW201. Hereinafter, the role of each function realized by the program module included in the controller FW will be described.

(Job control)
Job control is realized by the main CPU 20 executing a program module for Job control. The Job control instructs the "Print control" described later to start and stop the print job, and also instructs the "Print control" and the "Fax control" to start and stop the FAX job. Further, a job list is generated (or adjusted) by controlling the order of jobs, and the job list is sent to "Panel control" described later.

(Print control)
Print control is realized by the main CPU 20 executing a program module for print control. The Print control communicates with the printer unit 13 and communicates with the paper feed unit 14 via the mechanical controller FW301 for the printer unit 13. The Print control controls image transfer and paper feeding for a print job by communicating with the printer unit 13 and the paper feeding unit 14.

(Scan control)
Scan control is realized by the main CPU 20 executing a program module for Scan control. The Scan control communicates with the scanner unit 12 via the mechanical controller FW311 for the scanner unit 12. The Scan control reads an image by communicating with the scanner unit 12.

(Net control)
Net control is realized by the main CPU 20 executing a program module for Net control. The Net control sends and receives jobs to and from an external information processing device by communicating with the NIC 25.

(Fax control)
Fax control is realized by the main CPU 20 executing a program module for fax control. The fax control performs fax transmission / reception with a fax counter device by communicating with the fax transmission / reception unit 26.

(Box control)
Box control is realized by the main CPU 20 executing a program module for Box control. The Box control manages the file storage area 240 (commonly known as “BOX”) in the HDD 24 by communicating with the HDD 24. In one example, Box control performs creation and / or deletion of the file storage area 240 in the HDD 24. In another example, Box control stores image data in the file storage area 240 of the HDD 24.

(Panel control)
Panel control is realized by the main CPU 20 executing a program module for Panel control. The Panel control controls the display on the display unit 15 by communicating with the display unit 15, and sends the information input to the operation unit 18 to the "Job control" by communicating with the operation unit 18. In one example, the Panel control sends a job start instruction input to the operation unit 18 to the "Job control". As a result, "Job control" instructs the start of a job such as "Print control". In another example, the Panel control sends the settings for the job input to the operation unit 18 to the "Job control". As a result, the "Job control" adjusts the content of the job instructed to the "Print control" and the like.

(CPU error monitoring)
CPU abnormality monitoring is realized by the main CPU 20 executing a program module for CPU abnormality monitoring. The CPU abnormality monitoring detects a runaway of the sub CPUs 30 and 31 as an example of trouble in the "engine". In one example, when the CPU abnormality monitoring detects a runaway of the sub CPU, it instructs the runaway sub CPU to execute a firmware reboot.

<Functions of sub CPUs 30 and 31>
In FIG. 3, the function realized by the sub CPU 30 executing the firmware for the printer unit 13 and the paper feed unit 14 is shown as the mechanical controller FW301.

In FIG. 3, the function realized by the sub CPU 31 executing the firmware for the scanner unit 12 is shown as the mechanical controller FW311. The function realized by the sub CPU 31 executing the firmware for the document transfer unit 11 is shown as the mechanical controller FW312.

In the example of FIG. 3, the controller FW201 is realized by using one process space (process address space). Each of the Mechacon FW301, the Mechacon FW311 and the Mechacon FW312 is realized by using the process space one by one.

[4. Virtual memory configuration]
FIG. 4 is a diagram showing an example of a configuration of a virtual memory managed by the main CPU 20 in the HDD 24. As shown in FIG. 4, the virtual memory 2410 is roughly composed of a program area, a data area, and a stack area.

The program area 2411 is an area in which the program stored in the ROM 21 is loaded. The data area includes static memory 2412 and dynamic memory 2413. The dynamic memory 2413 can be secured and released. Thereby, the dynamic memory 2413 can be reused for different purposes. Once the static memory 2412 is secured, its area cannot be released.

In the stack area, data of functions and variables actually executed by the main CPU 20 are arranged in the program area. By executing the task scheduler control of the OS by the main CPU 20, the stack area to be used is switched from the plurality of stack areas, so that one main CPU 20 behaves as if a plurality of tasks are being performed at the same time. The task scheduler control determines the processing order of tasks based on the task priority. In the example of FIG. 4, four types of stack areas are defined. The stack area 2414 of the Job control task is used in the Job control of the controller FW201. The stack area 2415 of the Print control task is used in the Print control of the controller FW201. The stack area 2416 of the Scan control task is used in the Scan control of the controller FW201. The stack area 2417 of the Net control task is used in the Net control of the controller FW201.

[5. Print job settings]
FIG. 5 is a diagram showing an example of a screen displayed on the display unit 15 for inputting print job settings. As shown in FIG. 5, in the column 5100 of the screen 5000, an area 5110 for selecting a paper feed tray for supplying paper, an area 5120 for setting a printing surface (single-sided / double-sided) on paper, and printing. It includes an area 5130 for setting the number of pages of the target document. Region 5110 includes four types of options "automatic", "tray 1", "tray 2", and "tray 3". “Automatic” means that the image processing apparatus 1 selects a paper feed tray containing paper suitable for the size according to the size of the original (print target).

Each of "tray 1", "tray 2", and "tray 3" indicates each of the three paper feed trays (paper feed trays 14A, 14B, 14C) of the paper feed unit 14. The area 5110 displays information on the paper contained in each of the "tray 1", "tray 2", and "tray 3" as the item "paper information". In the example of FIG. 5, the “tray 1” is of the type “thick paper 1” and contains A3 size paper. The "tray 2" is a type of "plain paper" and contains A4 size paper. The "tray 3" contains A5 size paper of the type "thin paper 1".

In the example of FIG. 5, "tray 2" is selected in the area 5110, "both sides" is selected in the area 5120, and "1-2" (pages 1 to 2) is selected in the area 5130. ing.

[6. Job information]
FIG. 6 is a diagram showing an example of information (job information) for managing a job scheduled to be executed in the image processing device 1. The job information 600 has information for each page printed by the job. The job information includes the items "page position", "APS mode", "paper tray", "paper size", "paper type", and "printing surface".

"Page position" indicates the page position in the job.
The "APS mode" indicates whether or not to use the APS (automatic paper selection) function. When "automatic" is selected in the area 6110 of the setting screen, "ON" is set as the value of "APS mode" in the job information.

"Paper tray" indicates a paper tray selected by the user's setting or by the APS function.

"Paper size" indicates the size of the paper contained in the selected paper tray.
"Paper type" indicates the type of paper contained in the selected paper tray.

“Print surface” indicates the setting content of the print surface in the job.
In the job shown in FIG. 6, for example, the output of the first page utilizes plain paper of A4 size accommodated in the "tray 2" selected by the APS function. The set value of the printed surface of the first page and the second page is "both sides". As a result, the image of the first page is printed on the front surface of the paper, and the image of the second page is printed on the back surface of the paper.

[7. Communication between controller FW and mechanical controller FW (Example 1)]
FIG. 7 is a sequence diagram of an example of communication between the controller FW201 and the mechanical controller FW301 of the printer unit 13.

In the example of FIG. 7, the mechanical controller FW301 transmits the size information of the paper stored in each paper feed tray of the paper feed unit 14 as a “paper size report” to the controller FW201. In one example, the paper feed unit 14 may include a sensor that detects the size of the paper contained in each paper feed tray. The mechanical controller FW301 may transmit the paper size information to the controller FW201 according to the output of the sensor. The controller FW201 edits the job information according to the transmitted size information. In the example of FIG. 7, "A4 size" is transmitted as the size information of the tray 2. Correspondingly, as shown in FIG. 6, in the job information, "A4 size" is set as the value of the paper size of the page including "tray 2".

The controller FW201 transmits a "print start command" for printing the first page to the mechanical controller FW301. The "print start command" includes the information of the corresponding page in the job information (FIG. 6, etc.).

In the example of FIG. 7, a trouble has occurred in the mechanical element after the printing "print start command" of the first page is transmitted. In the present specification, the occurrence of a trouble in a mechanical element is also referred to as "engine trouble".

When the controller FW201 detects the occurrence of an engine trouble, it instructs the mechanical controller FW301 to reboot by transmitting a "reboot instruction".

In response to this, the sub CPU 30 reboots the mechanical controller FW301.
When the reboot of the Mechacon FW301 is completed, the controller FW201 sends the "print start command" of the first page to the Mechacon FW301 again. In the example of FIG. 7, the engine trouble in the mechanical element is solved by the reboot, and the mechanical element (paper feeding unit 14 and the printer unit 13) completes the printing of the image on the first page. After that, the controller FW201 transmits the "print start command" on the second page to the mechanical controller FW301. The mechanical elements (paper feed unit 14 and printer unit 13) complete printing of the image on the second page.

[8. Communication between controller FW and mechanical controller FW (Example 2)]
FIG. 8 is a sequence diagram of another example of communication between the controller FW201 and the mechanical controller FW301 mechanical controller FW301 of the printer unit 13.

In the example of FIG. 8, similar to the example of FIG. 7, an engine trouble occurs after the first transmission of the “print start command” on the first page.

In the example of FIG. 8, noise is generated due to engine trouble, and the mechanical controller FW301 transmits erroneous size information to the controller FW201 due to the noise. In this size information, the "tray 2" is associated with an "A3 size" (rather than the correct "A4 size").

The controller FW201 instructs the mechanical controller FW301 to reboot in response to the occurrence of engine trouble. As a result, the Mechacon FW301 reboots.

After that, the controller FW201 again transmits the "print start command" from the first page.

In the example of FIG. 8, the controller FW201 updates the job information according to the erroneous size information due to receiving the erroneous size information from the mechanical controller FW301. FIG. 9 is a diagram showing an example of an mode of updating job information according to incorrect size information. The job information 600 on the left side of FIG. 9 shows the correct information before the update. Upon receiving the incorrect size information, the controller FW201 rewrites the job information 600 to the job information 610 shown on the right side. In the job information 610, the paper size of the second page is changed to "A3 size".

Returning to FIG. 8, the controller FW201 transmits the “print start command” on the first page and then the “print start command” on the second page to the mechanical controller FW301. The "print start command" on the second page to be transmitted follows the job information 610 of FIG. According to the "print start command" on the first and second pages, the image on the first page is printed on the front surface of the paper, and the image on the second page is printed on the back surface of the paper. However, there is a contradiction that the paper sizes of the first page and the second page are different due to the erroneous update of the job information.

In the example of FIG. 8, an error occurs in the mechanical controller FW301 due to the above contradiction, so that a second engine trouble occurs.

The controller FW201 of the present embodiment reboots the entire system of the image processing device 1 when the second engine trouble occurs in the same job. As a result, the controller FW201 acquires the correct size information from the mechanical controller FW301, thereby generating consistent job information. According to the consistent job information, the consistent "print start command" is transmitted from the controller FW201 to the mechanical controller FW301.

That is, according to the examples of FIGS. 7 and 8, if the data used by the controller FW201 is not affected by the engine trouble, as shown in FIG. 7, the reboot of only the controller FW301 is instructed, and the controller FW201 processes. To continue. On the other hand, when the data used by the controller FW201 is affected by the engine trouble, the entire system of the image processing device 1 is rebooted.

In the same print job, after the reboot of only the mechanical controller FW in response to the occurrence of the first engine trouble, the reboot of the entire image processing device 1 including the reboot of the controller FW201 for the first time in response to the occurrence of the engine trouble again. Is carried out. As a result, while avoiding the reboot of the entire image processing apparatus 1 as much as possible, the entire image processing apparatus 1 is rebooted if necessary.

After the first engine trouble occurs during the execution of the first print job, the first print job is completed without any engine trouble thereafter, and then the first print job and the like. When the first engine trouble occurs in another second print job, not the reboot of the entire image processing apparatus 1 but the reboot of only the mechanical controller FW301 is executed.

In the present specification, the first engine trouble and the second engine trouble in the same job may be engine troubles of the same mechanical element or engine troubles of different types of mechanical elements. In the former case, in the same print job, the trouble that occurs in the paper feed unit 14 after the engine trouble occurs in the printer unit 13 is the first engine trouble. On the other hand, in the latter case, in the same print job, the trouble that occurs in the paper feed unit 14 after the engine trouble occurs in the printer unit 13 is the second engine trouble.

In the example of FIG. 7, after the first engine trouble, the second engine trouble was avoided by rebooting only the mechanical controller FW301. One example of the "first engine trouble" in such an example is that an abnormality occurs in the elements constituting the printer unit 13 and the paper feed unit 14. An example of an abnormality in the element is an abnormality in the rotation of a motor that drives a transfer belt or the like.

In the example of FIG. 8, after the first engine trouble, even if only the mechanical controller FW301 was rebooted, the second engine trouble occurred. One example of the "first engine trouble" in such an example is that an abnormality occurs in which the sub CPU 30 erroneously rewrites the data due to noise and further transmits the rewritten data to the main CPU 20.

[9. Processing flow]
FIG. 10 is a flowchart of processing executed for a print job by the main CPU 20. The process of FIG. 10 is realized, for example, by the main CPU 20 executing the program of the controller FW. The process of FIG. 10 is started, for example, in response to the input of the print job start instruction by the image processing device 1. An example of inputting a print job start instruction is to operate the start button in the operation button 17.

In step S100, the main CPU 20 transmits a print start command to the mechanical controller FW301.

In step S102, the main CPU 20 detects the presence or absence of engine trouble. The contents of step S102 will be described later with reference to FIG.

In step S104, the main CPU 20 determines whether or not an engine trouble has occurred, and if it is determined that the engine trouble has occurred, the control proceeds to step S108 (YES in step S104), and if it is determined that the engine trouble has not occurred, the control proceeds to step S106. The control is advanced (NO in step S104).

In step S106, the main CPU 20 determines whether or not the print job started for the process of FIG. 10 has been completed, and if it is determined that the print job has not been completed, returns control to step S102 (in step S106). NO), if it is determined that the process is completed, the process of FIG. 10 is terminated (YES in step S106).

In step S108, the main CPU 20 determines whether or not the engine trouble detected in the latest step S104 is the first engine trouble after the start of the process of FIG. 10 this time. If the main CPU 20 determines that it is the first one (YES in step S108), it advances the control to step S110, and if it determines that it is not the first one (NO in step S108), it advances the control to step S112. Proceed.

In step S110, the main CPU 20 instructs the mechanical controller FW301 to reboot, and then returns control to step S102.

In step S112, the main CPU 20 reboots the entire image processing device 1 including the controller FW201, and returns control to step S100.

FIG. 11 is a flowchart of the subroutine of step S102 (detection of engine trouble) of FIG. With reference to FIG. 11, in step S201, the main CPU 20 measures the usage time of the CPU 30 of each task of the mechanical controller FW301 within a fixed time.

In step S202, the main CPU 20 determines whether or not the usage time measured in step S201 exceeds the threshold value. An example of a fixed time may be 60 seconds. An example of the threshold value may be 54 seconds. When the main CPU 20 determines that the usage time exceeds the threshold value (YES in step S202), the control proceeds to step S203, and when it is determined that the threshold value is not exceeded (NO in step S202), the processing is performed as it is in FIG. Return to.

The main CPU 20 may further detect in step S102 (detection of engine trouble) of FIG. 10 whether or not there is an abnormality in the elements constituting the printer unit 13 and the paper feed unit 14. In one example, the main CPU 20 may measure the rotation speed of the motor in the printer unit 13 and determine that an engine trouble has occurred when the rotation speed is out of a given range. In another example, the main CPU 20 instructs the sub CPU 30 to move the transfer belt in the printer unit 13 to a predetermined initial position, the transfer belt measures the initial position, and the transfer belt measures the transfer belt. If it does not exist at the initial position, it may be determined that an engine trouble has occurred. In yet another example, the main CPU 20 may determine that an engine trouble has occurred when an abnormality occurs in other elements in the printer unit 13 and the paper feed unit 14.

In step S203, the main CPU 20 generates a determination result that "engine trouble has occurred", and then returns the process to FIG.

In the process of FIG. 11, it is determined whether or not an engine trouble has occurred according to the determination result of whether or not the ratio of the usage time of the sub CPU 30 exceeds a given ratio in step S202. The presence or absence of engine trouble may be determined according to any known standard.

In step S104 of FIG. 10, if the determination result of "engine trouble has occurred" is generated in step S203, the main CPU 20 determines that the engine trouble has occurred. If the above determination result is not generated, the main CPU 20 determines that no engine trouble has occurred.

[10. Functional configuration of image processing device (2)]
FIG. 12 is a diagram showing a modified example of the functional configuration of the main CPU 20. In the example of FIG. 12, the main CPU 20 executes two firmwares to function as a controller. That is, the main CPU 20 functions as the controller FW (1) 211 by executing the first firmware, and functions as the controller FW (2) 212 by executing the second firmware.

The "Job control 2" realized by the controller FW (2) 212 executes the control of the fax transmission job and the fax reception job. The "Job control 1" realized by the controller FW (1) 211 executes control of a type of job other than the fax transmission job and the fax reception job. That is, in the example of FIG. 12, the process space for controlling the fax transmission / reception job (controller FW (2) 212) is the process space for controlling the job other than the fax transmission / reception (controller FW (1) 211). Is set separately.

With such a configuration, in the image processing apparatus 1, the print job and the fax transmission job or the fax reception job can be controlled in parallel. In the example of FIG. 12, when the second engine trouble of the print job occurs during the execution of the fax reception job, the main CPU 20 waits for the reboot of the entire image processing apparatus 1 until the end of the fax reception job.

FIG. 13 is a flowchart of the process executed by the main CPU 20 in the example of FIG. The process of FIG. 13 includes the control of step S111 prior to step S112 as compared to the process of FIG.

That is, if the main CPU 20 determines in step S108 that the engine trouble has not occurred in the printing job being executed for the first time (NO in step S108), the main CPU 20 proceeds to control to step S111.

In step S111, the main CPU 20 determines whether or not the fax reception job is being executed. If the main CPU 20 determines that the fax receiving job is being executed (YES in step S111), the determination in step S111 is repeated, for example, at regular intervals, and if it is determined that the fax receiving job is no longer being executed (in step S111). NO), the control proceeds to step S112.

As shown in FIG. 13, if the fax reception job is being executed, the entire reboot of the image processing device 1 is postponed until the fax reception is completed, so that the fax counter device needs to retransmit the document. The situation that is done can be avoided. Sending a fax document may impose a communication fee on the user of the fax machine. By avoiding the retransmission of the fax document as much as possible, the image processing device 1 can avoid the situation where the user of the fax counter device requires an extra communication cost for the retransmission as much as possible.

[11. Other examples of incorrect data due to engine trouble]
14 to 16 are diagrams for explaining another example of erroneous data transmitted from the mechanical controller FW to the controller FW due to an engine trouble. In the example described with reference to FIGS. 7 and 8, erroneous data was transmitted regarding the size information of the paper. In the example described with reference to FIGS. 14-16, erroneous data is transmitted for the gamma data. The gamma data is an example of correction information showing the relationship (correction curve, etc.) between the signal for image formation (for example, image data related to a print job) and the operation mode of the drive unit (for example, the charging voltage of the photoconductor). be.

FIG. 17 is a diagram showing a second modification of the functional configuration of the main CPU 20 corresponding to the processes described with reference to FIGS. 14 to 16. In the example of FIG. 17, the main CPU 20 executes two firmwares to function as a controller. That is, the main CPU 20 functions as the controller FW (1) 231 by executing the first firmware, and functions as the controller FW (2) 232 by executing the second firmware.

The "Job control 2" realized by the controller FW (2) 232 executes the control of the print job. The "Job control 1" realized by the controller FW (1) 231 executes control of a type of job other than the print job. That is, in the example of FIG. 17, the process space for controlling the print job (controller FW (2) 232) is separate from the process space for controlling jobs other than fax transmission / reception (controller FW (1) 231). Is set to.

Returning to FIGS. 14 to 16, a schematic flow of the print job will be described.
First, refer to FIG. In the example of FIG. 14, erroneous data is not transmitted. That is, the mechanical controller FW301 transmits normal gamma data generated by image stabilization control or the like in the mechanical element (printer unit 13) to the controller FW (2) 232.

The controller FW (2) 232 uses normal gamma data to generate print job data, and sends a print start command to the mechacon FW301 based on the data.

For example, after transmitting the print start command on the 99th page, an engine trouble occurs in the mechanical controller FW301.

If the engine trouble occurs for the first time in the print job, the controller FW (2) 232 instructs the mechanical controller FW301 to reboot.

After the reboot, the mechacon FW301 requests the controller FW (2) 232 for permission to execute the image stabilization control (image stabilization control permission request).

The controller FW (2) 232 permits the mechanical controller FW301 to execute the image stabilization control (image stabilization control permission). In response to this, the printer unit 13 executes image stabilization control.

After that, the controller FW (2) 232 transmits a print start command for the remaining pages (the 100th page and thereafter) to the mechanical controller FW301.

Next, an example of FIG. 15 will be described. In the example of FIG. 15, the controller FW (2) 232 stabilizes the image on the mechanical controller FW301 if the number of remaining pages of the print job being executed at the time of the first engine trouble is less than or equal to a given value. The control execution instruction is omitted. The reason for the omission may be to terminate the running print job at an early stage.

More specifically, in the example of FIG. 15, the controller FW (2) 232 instructs the mechanical controller FW301 to reboot due to the occurrence of the first engine trouble.

After the reboot, the mechanical controller FW301 transmits an image stabilization control permission request to the controller FW (2) 232.

In the example of FIG. 15, the number of remaining sheets in the running print job is less than a given threshold. Therefore, the controller FW (2) 232 transmits the print start command for the remaining pages (the 100th and subsequent pages) without transmitting the image stabilization control permission to the mechanical controller FW301.

In the example of FIG. 16, in addition to the example of FIG. 15, the gamma data in the mechanical controller FW301 is updated to an abnormal value due to noise or the like at the time of the first engine trouble. The mechacon FW301 erroneously transmits abnormal gamma data to the controller FW (2) 232.

After that, even if the mechanical controller FW301 is rebooted according to the instruction from the controller FW (2) 232, the image stabilization control in the printer unit 13 is not performed as in FIG. 15, so that there is no chance that erroneous gamma data is corrected. ..

As a result, an error may occur in the mechanical controller FW301 due to the print start command transmitted thereafter in the print job. For example, the image data generated by the anomalous gamma data causes the Mechacon FW301 to enter a routine that is not inherently possible (eg, a process of dividing a given value by zero in calculating the applied voltage of the photoconductor). Due to an error in the Mechacon FW301, a second engine trouble occurs in the running print job.

In this case, the controller FW (2) 232 reboots the entire image processing device 1. As a result, the mechanical controller FW301 executes the image stabilization control of the printer unit 13, generates normal gamma data, and transmits it to the controller FW (2) 232.

FIG. 18 is a flowchart of the process executed by the main CPU 20 in the example of FIG. The process of FIG. 18 includes the control of steps S114 and S116 after step S110 as compared with the process of FIG.

More specifically, the main CPU 20 (controller FW (2) 232) instructs the mechanical controller FW301 to reboot in step S110, and then proceeds to control to step S114. In step S114, the main CPU 20 determines whether or not the number of remaining pages among the pages to be printed is equal to or less than a given threshold value in the printing job being executed. When the main CPU 20 determines that the number of remaining pages is not less than or equal to a given threshold value (NO in step S114), the main CPU 20 instructs the mechanical controller FW301 to execute the image stabilization control of the printer unit 13 in step S116. , Return control to step S102. On the other hand, when the main CPU 20 determines that the number of remaining pages is equal to or less than a given threshold value (YES in step S114), the main CPU 20 returns the control to step S102 without instructing the execution of the image stabilization control. An example of an instruction to execute the image stabilization control is to transmit a signal indicating that the image stabilization control permission request from the mechanical controller FW301 is permitted.

[12. Separation of process space]
In the image processing apparatus 1, as shown in FIG. 12 or FIG. 17, the process space of the firmware executed by the main CPU 20 can be separated for each type of job. In the example of FIG. 12, the process space is separated between the fax transmission / reception job and the other types of jobs. In the example of FIG. 17, the process space is separated between the print job and the other types of jobs.

By separating the process space, the storage area used in the RAM 22 (real memory) and the virtual memory on the HDD 24 is separated. As a result, even if the data on the controller side is rewritten by the erroneous data sent from the Mechacon FW for one type of job, the effect of such erroneous rewriting will affect the data on the controller side for other types of jobs. Being affected is avoided as much as possible.

Hereinafter, the data structure in the virtual memory will be described more specifically. In the example of FIG. 12, the process space for the fax receiving job is separated from the process space for the print job. As a result, the tasks generated for the print job are managed in an area as shown as virtual memory 2410 in FIG.

When applied to the example of FIG. 12, the “controller FW program area 2411” of FIG. 4 can be changed to the area where the “controller FW (1) 211” of FIG. 12 is loaded. Further, when applied to the example of FIG. 12, the “Job control task stack area 2414” of FIG. 4 can be modified to be used in the “Job control 1” of FIG.

On the other hand, the task generated for the FAX reception job is managed in an area different from the virtual memory 2410. FIG. 19 is a diagram showing an example of a virtual memory configuration managed for a fax receiving job.

As shown in FIG. 19, the virtual memory 2420 is generally composed of a program area, a data area, and a stack area.

The program area 2421 is an area in which the program (controller FW (2)) stored in the ROM 21 is loaded. The data area includes static memory 2422 and dynamic memory 2423.

The stack area includes an unused area 2424, 2427, a stack area 2425 of the “Job control 2” task, and a stack area 2426 of the fax control task. The stack area 2425 of the Job control 2 task is used in the Job control 2 of the controller FW (1) 211. The stack area 2426 of the fax control task is used in the fax control of the controller FW (1) 211.

FIG. 20 is a diagram for explaining the effect of separating the storage area used for each process. In FIG. 20, the virtual memory 2410 shows the configuration of a virtual memory managed for a print job as described with reference to FIG. The virtual memory 2420 shows a configuration of virtual memory managed for a fax receiving job as described with reference to FIG. In FIG. 20, a plurality of lines show the mapping between the virtual memory 2410 and the RAM 22. That is, each of the areas 5101, 5102, and 5103 of the virtual memory 2410 is mapped to each of the areas 2204, 2202, and 2205 of the RAM 22.

Also, in FIG. 20, a plurality of lines show the mapping between the virtual memory 2420 and the RAM 22. That is, each of the areas 5201 and 5202 of the virtual memory 2420 is mapped to each of the areas 2203 and 2201 of the RAM 22. In the virtual memory 2410 and the virtual memory 2420, data reading and writing are executed independently of each other. As a result, in the controller, the part that executes the fax reception job and the part that executes the print job can be restarted (rebooted) independently of each other.

Similarly, in the example of FIG. 17, in the controller, the part that executes the print job and the part that executes the non-print job can be restarted independently of each other.

It should be considered that each embodiment disclosed this time is exemplary in all respects and is not restrictive. The scope of the present invention is shown by the scope of claims rather than the above description, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims. Further, the inventions described in the embodiments and the modifications thereof are intended to be carried out alone or in combination as much as possible.

1 image processing unit, 11 document transfer unit, 12 scanner unit, 13 printer unit, 14 paper feed unit, 14A, 14B, 14C, 14D paper feed tray, 15 display unit, 16 touch panel, 17 operation buttons, 18 operation unit, 19 Outlet, 20 main CPU, 21 ROM, 22 RAM, 23 non-volatile memory, 26 transmitter / receiver, 30, 31 sub CPU, 301, 311, 312 Mechacon FW.

Claims (7)

An image forming unit that executes an image forming operation,
A control unit that controls the image formation operation of the image forming unit is provided.
The image forming unit includes a driving unit that drives for an image forming operation and a control circuit that controls the driving unit.
The control unit
When the occurrence of the first trouble is detected in the image forming unit during the execution of the print job, the control circuit is instructed to reboot without rebooting the control unit.
An image processing device that reboots the control circuit and the control unit when the occurrence of a second trouble is detected in the image forming unit before the end of the print job. When the control unit detects the occurrence of the second trouble and is executing another job that does not use the image forming unit, the control unit waits for the end of the other job and reboots the control unit. , The image processing apparatus according to claim 1. The first or second aspect, wherein the control unit executes a job that uses the image forming unit in the first process space, and executes a job that does not use the image forming unit in the second process space. Image processing equipment. The image forming unit includes a paper feed tray for accommodating paper used for the printing job.
The control circuit transmits information for specifying the paper size in the paper feed tray to the control unit.
Any of claims 1 to 3, wherein the control unit transmits a control instruction using information for specifying the paper size received from the control circuit to the control circuit for executing the print job. The image processing apparatus according to claim 1. The image forming unit generates correction information indicating the relationship between the image forming signal and the operation mode of the driving unit based on the image output by the driving unit according to a predetermined signal, and controls the correction information. Send to the department,
The control unit transmits a control instruction using the correction information received from the control circuit to the control circuit in order to execute the print job, according to any one of claims 1 to 4. The image processing device described. A control method for an image processing device executed by the control unit in an image processing device including an image forming unit that executes an image forming operation and a control unit that controls the image forming operation of the image forming unit.
The image forming unit includes a driving unit that drives for an image forming operation and a control circuit that controls the driving unit.
When the occurrence of the first trouble is detected in the image forming unit during the execution of the print job, the step of instructing the control circuit to reboot without rebooting the control unit, and the step of instructing the control circuit to reboot.
A control method for an image processing apparatus, comprising a step of instructing the control circuit to reboot and rebooting the control unit when the occurrence of a second trouble is detected in the image forming unit before the end of the print job. .. A program executed by the control unit in an image processing apparatus including an image forming unit that executes an image forming operation and a control unit that controls the image forming operation of the image forming unit.
The image forming unit includes a driving unit that drives for an image forming operation and a control circuit that controls the driving unit.
By executing the program, the control unit can be
When the occurrence of the first trouble is detected in the image forming unit during the execution of the print job, the step of instructing the control circuit to reboot without rebooting the control unit, and the step of instructing the control circuit to reboot.
A program for instructing the control circuit to reboot and executing a step of rebooting the control unit when the occurrence of a second trouble is detected in the image forming unit before the end of the print job.

Images