JP2005229210A - Image forming apparatus and automatic reboot method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus and an automatic reboot method wherein no mismatching is caused to values of various counters provided on the basis of charging and other managemental necessities in the case of applying automatic rebooting to a fault with high possibility of restoration by OFF/ON of power. <P>SOLUTION: The image forming apparatus including a hardware resource used for image forming and a program for implementing processing required for image forming, is provided with: a means for detecting a fault of a reboot object among faults with high restoration possibility by OFF/ON of power; a means for stopping the hardware resource and the program operation just after the fault of the reboot object is detected; and a means for rebooting the hardware resource and the program. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an image forming apparatus and an automatic reboot method.

  In an image forming apparatus such as a copying machine, various counters by hardware or software whose count value is increased (UP) each time printing is performed are provided for accounting and other management needs. For example, the following counter is provided.

・ Total counter on the controller side ・ Counter on the accounting side on the controller side ・ Mechanical counter on the engine side ・ Counter on the accounting side on the engine side These counters are required to increase the count value accurately every time printing is performed. Inconsistencies in values will affect billing and other management.

  FIG. 8 is a sequence diagram showing a counter-related operation in a normal time in the image forming apparatus. Here, it is assumed that two sheets are continuously printed.

  In FIG. 8, when a print job start is notified to the xCS 204 such as ECS (Engine Control Service) from the application 201 that controls the execution of copying or the like (Step S501), the xCS 204 sends an SCS (System Control Service) 203 The process start of the first print is notified (step S502), and the SCS 203 notifies the engine 206 of the process start of the first print (step S503). In response to this, the engine 206 starts feeding the first sheet, and notifies the SCS 203 to that effect (step S504). The SCS 203 further notifies the xCS 204 (step S505). In response, the xCS 204 notifies the SCS 203 of the start of the second print process (step S506), and the SCS 203 notifies the engine 206 of the start of the process of the second print (step S507). When the second sheet starts to be fed 206, it notifies the SCS 203 of that (step S508). The reason for notifying the start of the second sheet at the stage of feeding the first sheet is to improve the printing performance.

  The engine 206 prints the first sheet, and when the fixing is completed, the engine counter on the engine side is increased (step S509), and the completion of the first sheet is notified to the SCS 203 (step S510). In response to this, the SCS 203 increments the total counter on the controller side (step S511) and makes a count request to the engine 206 (step S512). In response to this, the engine 206 increases the counter of the charging device on the engine side (step S513).

  Thereafter, the engine 206 notifies the SCS 203 when the first sheet is normally discharged (step S514), and the SCS 203 further notifies the xCS 204 (step S515), and the xCS 204 further notifies the application 201. (Step S516). In response to this, the application 201 issues a count request to the SCS 203 (step S517), and the SCS 203 increases the counter of the accounting device on the controller side (step S518).

  Similarly, the engine 206 increases the mechanical counter on the engine side when the second sheet is fixed (step S519), and notifies the SCS 203 of the completion of fixing the second sheet (step S520). In response to this, the SCS 203 increases the total counter on the controller side (step S521), and makes a count request to the engine 206 (step S522). In response to this, the engine 206 increases the counter of the charging device on the engine side (step S523).

  Thereafter, the engine 206 notifies the SCS 203 when the second sheet is normally discharged (step S524), and the SCS 203 further notifies the xCS 204 (step S525), and the xCS 204 further notifies the application 201. (Step S526). In response to this, the application 201 makes a count request to the SCS 203 (step S527), and the SCS 203 increases the counter of the accounting device on the controller side (step S528).

  In the above operations, the values of the controller-side total counter, controller-side charging device counter, engine-side mechanical counter, and engine-side charging device counter are consistent for both the first and second sheets. ing.

  By the way, in the image forming apparatus, a failure based on various causes of hardware or a program (software) may occur. Failures are classified into the following four types A to D, for example. Note that these types are for convenience and do not necessarily imply an order of failure severity.

Type A ··· Failure requiring urgency and repair by a service person Type B · · Failure caused by a specific unit failure that does not affect basic functions Type C · · Log-only SC
Type D ··· Other failures that can be recovered by turning the power off (OFF) / ON (ON) Conventionally, among the above failures, those that fall under Type D are less than the predetermined number Therefore, the system automatically reboots the system without bothering the user.

  FIG. 9 is a sequence diagram showing a conventional operation when a reboot target failure occurs. When a reboot target failure occurs (step S601), the SCS 203 transfers to the xCS 204, and the SRM (system resource manager) 205 passes to the engine 206. Then, notification of operation suppression is sent to the apps 201 and 202 almost simultaneously (steps S602 to S606), and operation suppression processing (for stopping the operation in a state in which the processing in progress can be safely performed with a good reboot) Post-processing, suppression of new operation by suppressing interface, etc.) are performed (step S607), and after a response of operation suppression from each unit (steps S608 to S612), reboot is executed. (Step S613).

  Conventional reboot processing when a failure occurs is performed as described above, but there is a problem that inconsistencies occur in the values of various counters provided for accounting and other management needs.

  FIG. 10 is a sequence diagram showing a conventional counter-related operation when a reboot target failure occurs, and it is assumed that two sheets are printed in succession.

  In FIG. 10, when a print job start is notified from the application 201 to the xCS 204 (step S701), the xCS 204 notifies the SCS 203 of the start of the first print process (step S702), and the SCS 203 notifies the engine 206. In response to this, the process start of the first print is notified (step S703). In response to this, the engine 206 starts feeding the first sheet and notifies the SCS 203 to that effect (step S704), and the SCS 203 further informs the xCS 204 (step S705). In response to this, the xCS 204 notifies the SCS 203 of the start of the process of the second print (step S706), and the SCS 203 notifies the engine 206 of the start of the process of the second print (step S707). When the second sheet starts to be fed 206, it notifies the SCS 203 of that (step S708).

  Thereafter, when a failure to be rebooted occurs (step S709), the SCS 203 notifies the engine 206 of operation suppression and process cancellation (steps S710 to S712), and the xCS 204 and the application 201 operate almost simultaneously. Notification of suppression is performed (steps S713 and S714).

  The engine 206 tries to cancel the process as much as possible, but if the cancellation of the first print that has already entered the process is not in time, the print is executed and the engine side will be (Step S715), and the SCS 203 is notified of the completion of fixing the first sheet (step S716). In response to this, the SCS 203 increments the controller-side total counter (step S717), makes a count request to the engine 206 (step S718), and in response to this, the engine 206 increments the counter on the engine-side charging device. (Step S719).

  After that, the engine 206 notifies the SCS 203 when the first sheet is normally discharged (step S720), and the SCS 203 further notifies it to the xCS 204 (step S721). The xCS 204 further notifies the application 201. (Step S722). However, since the xCS 204 is already in operation suppression at this point, notification to the application 201 cannot be performed due to interface suppression. Therefore, the subsequent application 201 cannot make a count request (step S723) that should be made to the SCS 203, and the SCS 203 cannot increase the counter of the accounting device on the controller side (step S724).

  After that, the engine 206 cancels the second print, and thus performs abnormal paper discharge (paper discharge as blank), and notifies that to the SCS 203 (step S725), and the SCS 203 further notifies this to the xCS 204 ( Step S726).

  As is clear from the above operation, the first print is normally performed, and the mechanical counter on the engine side, the counter on the charging device on the engine side, and the total counter on the controller side are incremented. The counter of the billing apparatus is not incremented, and the counter value is inconsistent.

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to charge or otherwise perform automatic reboot for a failure that is likely to be recovered by turning the power OFF / ON. It is an object of the present invention to provide an image forming apparatus and an automatic reboot method in which inconsistency does not occur in the values of various counters provided in view of the necessity for management of the system.

  In order to solve the above problems, according to the present invention, as described in claim 1, an image forming apparatus having hardware resources used for image formation and a program for performing processing related to image formation In the above, the means for detecting a failure to be rebooted among failures that are likely to be recovered by power OFF / ON, and the operation of the hardware resources and the program are stopped immediately after the failure to be rebooted is detected. Means for performing, and means for rebooting the hardware resource and the program.

  According to a second aspect of the present invention, a total counter provided on the controller side of the program, a counter of a charging device provided on the controller side, a mechanical counter provided on the engine side of the hardware resource, A billing device counter provided on the engine side may be provided.

  According to a third aspect of the present invention, the operation stop includes a job stop and a new process control stop.

  According to a fourth aspect of the present invention, when the job is stopped, the application of the program can cancel an incomplete job.

  According to a fifth aspect of the present invention, the operation of the hardware resource and the program can be suppressed after the completion of the operation stop and before the reboot.

  According to a sixth aspect of the present invention, it is possible to wait for a predetermined time from the response from the hardware resource and the program to the execution of reboot after the response to the operation suppression.

  According to a seventh aspect of the present invention, the failure to be rebooted is within a range in which a failure that is likely to be recovered by turning the power OFF / ON does not reach a predetermined number of times while a predetermined number of prints are performed. It can be the case when it occurs.

  Further, as described in claim 8, the predetermined number can be 10 and the predetermined number can be 2.

  In addition, as described in claim 9, each of the means is a function of a system control service that performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, interrupt application control, and the like. Can be configured.

  According to a tenth aspect of the present invention, rebooting the hardware resource and the program sequentially performs engine reset, hard disk drive access stop, engine power off, engine power on, and application reboot. Can be.

  In addition, as described in claim 11, when a failure to be rebooted is detected, a screen informing the start of execution of automatic reboot can be displayed.

  According to a twelfth aspect of the present invention, the screen informing the start of execution of the automatic reboot may include a display indicating the progress status of post-processing of the hardware resource and the program.

  According to a thirteenth aspect of the present invention, the screen for notifying the start of execution of the automatic reboot may include a display indicating a time until the reboot is performed.

  In addition, as described in claim 14, the screen informing the start of execution of the automatic reboot may include a button for instructing the start of the reboot immediately.

  In addition, as described in claim 15, after the reboot is executed, a screen requesting confirmation from the user can be displayed.

  Further, as described in claims 16 to 18, there is a possibility that the image forming apparatus having hardware resources used for image formation and a program for performing processing relating to image formation may be restored by turning the power OFF / ON. A step of detecting a failure to be rebooted among high failures, a step of stopping the operation of the hardware resource and the program immediately after detecting the failure to be rebooted, and rebooting the hardware resource and the program It can comprise as an automatic reboot method provided with the process to do.

  In the present invention, when automatic reboot is performed for a failure that is highly likely to be recovered by turning the power OFF / ON, inconsistencies occur in the values of various counters provided for accounting and other management needs. There is no effect.

  Preferred embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a configuration diagram of an image forming apparatus according to an embodiment of the present invention.

  In FIG. 1, the image forming apparatus 1 is configured to include a software group 2, an image forming apparatus activation unit 3, and hardware resources 4.

  The image forming apparatus activation unit 3 is executed first when the image forming apparatus 1 is powered on, and activates the application layer 5 and the platform layer 6. For example, the image forming apparatus activation unit 3 reads the programs of the application layer 5 and the platform layer 6 from a hard disk device (hereinafter referred to as HDD) and transfers each read program to a memory area and activates it. The hardware resource 4 includes a scanner 25, a plotter 26, and a hardware resource 24 such as an ADF (Auto Document Feeder).

  The software group 2 includes an application layer 5 and a platform layer 6 activated on an operating system (hereinafter referred to as OS) such as UNIX (registered trademark). The application layer 5 includes programs that perform processing unique to user services related to image formation such as printers, copies, faxes, and scanners.

  The application layer 5 includes a printer application 9 that is a printer application, a copy application 10 that is a copy application, a fax application 11 that is a fax application, and a scanner application 12 that is a scanner application.

  The platform layer 6 interprets a processing request from the application layer 5 and generates a hardware resource 4 acquisition request, and manages one or more hardware resources 4 to control the control service layer. 7 includes a system resource manager (hereinafter referred to as “SRM”) 21 that arbitrates acquisition requests from 7 and a handler layer 8 that manages hardware resources 4 in response to acquisition requests from the SRM 21.

  The control service layer 7 includes a network control service (hereinafter referred to as NCS) 13, a delivery control service (hereinafter referred to as DCS) 14, an operation panel control service (hereinafter referred to as OCS) 15, and a fax control service (hereinafter referred to as FCS) 16. , Engine control service (hereinafter referred to as ECS) 17, memory control service (hereinafter referred to as MCS) 18, user information control service (hereinafter referred to as UCS) 19, system control service (hereinafter referred to as SCS) 20, etc. The service module is configured to be included.

  The platform layer 6 is configured to have an API 28 that can receive a processing request from the application layer 5 using a predefined function. The OS executes the software of the application layer 5 and the platform layer 6 in parallel as processes.

  The process of the NCS 13 provides a service that can be commonly used for applications that require network I / O. Data received from the network side according to each protocol is distributed to each application, and data from each application. Mediation when sending to the network side.

  For example, the NCS 13 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).

  The process of the DCS 14 performs control such as distribution of stored documents. The process of the OCS 15 controls an operation panel serving as information transmission means between the operator and the main body control. The FCS16 process provides APIs for sending and receiving faxes from the application layer 5 using the PSTN or ISDN network, registering / quoting various fax data managed in the backup memory, reading faxes, receiving faxes, etc. To do.

  The process of the ECS 17 controls the engine unit such as the scanner 25, the plotter 26, and other hardware resources 24. The process of the MCS 18 performs memory control such as acquisition and release of memory and use of the HDD. The UCS 19 manages user information.

  The process of the SCS 20 performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control.

  The process of the SRM 21 controls the system and manages the hardware resources 4 together with the SCS 20. For example, the process of the SRM 21 performs arbitration according to an acquisition request from an upper layer that uses the hardware resources 4 such as the scanner 25 and the plotter 26, and controls execution.

  Specifically, the process of the SRM 21 determines whether or not the requested hardware resource 4 is available (whether it is not used by another acquisition request). The higher layer is notified that the resource 4 is available. Further, the process of the SRM 21 performs scheduling for using the hardware resource 4 in response to an acquisition request from an upper layer, and the request contents (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) Has been implemented directly.

  The handler layer 8 includes a fax control unit handler (hereinafter referred to as FCUH) 22 for managing a fax control unit (hereinafter referred to as FCU), which will be described later, and an image for allocating memory to the process and managing the memory allocated to the process. And a memory handler (hereinafter referred to as IMH) 23. The SRM 21 and the FCUH 22 make a processing request for the hardware resource 4 by using an engine I / F 27 that enables transmission of a processing request for the hardware resource 4 by a predefined function.

  The image forming apparatus 1 can centrally process processes commonly required for each application by the platform layer 6. Next, the hardware configuration of the image forming apparatus 1 will be described.

  FIG. 2 is a hardware configuration diagram of the image forming apparatus according to the embodiment of the present invention.

  In FIG. 2, the image forming apparatus 1 includes a controller board 30, an operation panel 43, an FCU 44, and an engine 47. The FCU 44 includes a G3 standard compatible unit 45 and a G4 standard compatible unit 46.

  The controller board 30 includes a CPU 31, an ASIC 40, an HDD 42, a system memory (MEM-P) 32, a local memory (MEM-C) 41, a north bridge (hereinafter referred to as NB) 33, and a south bridge. (Hereinafter referred to as SB) 34, NIC 35 (Network Interface Card), USB device 36, IEEE 1394 device 37, and Centronics device 38.

  The operation panel 43 is connected to the ASIC 40 of the controller board 30. The SB 34, the NIC 35, the USB device 36, the IEEE 1394 device 37, and the Centronics device 38 are connected to the NB 33 via a PCI bus.

  The FCU 44 and the engine 47 are connected to the ASIC 40 of the controller board 30 via a PCI bus.

  The controller board 30 is connected to the ASIC 40 with the MEM-C 41, the HDD 42, and the like, and the CPU 31 and the ASIC 40 are connected to each other through the NB 33 of the CPU chip set. In this way, if the CPU 31 and the ASIC 40 are connected via the NB 33, it is possible to cope with the case where the interface of the CPU 31 is not disclosed.

  Further, the ASIC 40 and the NB 33 are not connected via a PCI bus, but are connected via an AGP (Accelerated Graphics Port) 39. In this way, in order to control execution of one or more processes forming the application layer 5 and the platform layer 6 in FIG. 1, the ASIC 40 and the NB 33 are connected via the AGP 39 instead of the low-speed PCI bus, thereby reducing the performance. It is preventing.

  The CPU 31 performs overall control of the image forming apparatus 1. The CPU 31 starts and executes the NCS 13, DCS 14, OCS 15, FCS 16, ECS 17, MCS 18, UCS 19, SCS 20, SRM 21, FCUH 22, and IMH 23 in FIG. The copy application 10, the fax application 11, and the scanner application 12 are activated and executed.

  The NB 33 is a bridge for connecting the CPU 31, the MEM-P 32, the SB 34 and the ASIC 40. The MEM-P 32 is a memory used as a drawing memory of the image forming apparatus 1. The SB 34 is a bridge for connecting the NB 33 to the PCI bus and peripheral devices. The MEM-C 41 is a memory used as a copy image buffer and a code buffer.

  The ASIC 40 is an IC for image processing applications having hardware elements for image processing. The HDD 42 is a storage for storing images, programs, font data, forms, and the like. The operation panel 43 is an operation unit that accepts an input operation from the user and performs display for the user.

  FIG. 3 is a block diagram illustrating a configuration example of a functional unit provided in the SCS 20 of FIG. 1 for handling a failure. Only the part related to failure handling is shown.

  In FIG. 3, the SCS 20 includes a failure detection unit 20 a that detects the type A and type D failures described above, a log writing unit 20 b that writes the failures that have occurred in a log, and a possibility of recovery by turning the power OFF / ON. Type D faults that are subject to rebooting (for example, if the type D fault does not reach twice while the total counter that counts the number of printed sheets is counted up by 10), that is, the first type And a reboot target failure detection unit 20c that detects a failure of D).

  The SCS 20 also includes a screen display control unit 20d that displays a screen relating to automatic notification and automatic reboot when a failure occurs, and a type A failure or a type D failure occurring at a predetermined frequency (for example, counting the number of printed sheets). If a Type D failure occurs twice while the total counter counts up by 10), an automatic notification function called CSS (Customer Satisfaction Service) or NRS (New Remote Service), which is a diagnostic service using the network, is used. And an automatic report control unit 20e that automatically reports to the service center.

  Further, immediately after the failure to be rebooted is detected, the SCS 20 stops the operation (stops the job) with respect to the engine or program (software group 2) that is the hardware resource 4 of the image forming apparatus 1 prior to rebooting. An operation stop control unit 20f that performs a new process control generation stop and the like, and waits for a response to the operation stop, and suppresses the operation of the engine or program (suppresses new operation, suppresses interprocess communication, HDD) And a reboot execution control unit 20h that performs a series of reboot (reset) processes on the engine and program of the image forming apparatus 1.

  FIG. 4 is an operation flowchart showing the operation of the image forming apparatus when a failure occurs.

  In FIG. 4, when a type A or type D failure occurs (step S101), a type A failure or a type D failure that is not a reboot target (the total counter for counting the number of printed sheets is incremented by 10). If a type D failure occurs twice during this period, if the image forming apparatus 1 has an automatic notification function by CSS or NRS and the function is valid, the automatic notification screen at the time of failure is displayed. Automatic notification is made to the service center (step S102). If the report is successful, a message is displayed indicating that the serviceman will wait for a repair (step S103), or a message indicating that the response will be the next business day because it is out of business hours as another pattern (step S105). It will be in the state of waiting for OFF / ON of (step S104, S106). If the report fails, the user is informed that the service center should be contacted (step S107) and waits for power OFF / ON (step S108).

  Further, when the type D is a failure and is subject to reboot (in the case of the first occurrence), automatic notification is not performed even if the automatic notification function of the image forming apparatus 1 is valid, and automatic reboot is performed. A screen notifying the start of execution is displayed (step S109). In this screen, the contents of the process will be erased by rebooting, indicating that it is necessary to start again. In addition, the progress of the post-processing for rebooting hardware resources and programs, and the reboot execution are displayed. And a button for instructing the start of reboot immediately. Here, the post-processing is processing by stopping operation and suppressing operation, and stops jobs and stops the generation of new process control so as not to cause inconsistencies in various counters, and prevents paper from remaining in the engine. Or an appropriate reboot so that an HDD failure or the like does not occur. Further, as a time until the reboot is executed, a waiting time of, for example, 30 seconds is provided after the post-processing is completed and the reboot can be performed. This is because when the post-processing is completed in a short time, a screen for informing the start of automatic reboot is displayed only for a short time, and the user cannot be sufficiently recognized. The reason why the button for instructing the start of the reboot is provided immediately is to perform the reboot without waiting for a predetermined waiting time when the operation is in a hurry, and to promptly recover.

  When a predetermined waiting time has elapsed since the screen informing the start of execution of automatic reboot has been displayed, automatic reboot is executed (step S110), and a screen for informing the user that automatic reboot has been executed and for confirmation is displayed. (Step S111). Then, when the user presses the confirmation button, the normal screen is displayed (step S112).

  Further, when the user presses a button for instructing the start of the reboot immediately from the screen informing the start of the automatic reboot, the automatic reboot is executed without a predetermined waiting time (step S113). The screen shifts to a screen (step S112). In this case, the screen (step S111) for notifying the user that automatic reboot has been executed and requesting confirmation is omitted.

  On the other hand, when the automatic notification function of the image forming apparatus 1 is invalid or the model does not have the automatic notification function itself, in the case of a type A failure or a type D failure and not subject to reboot, the user Is displayed to the effect that the service center should be contacted (step S117), and the system waits for power OFF / ON (step S118).

  If the type D is a failure and is to be rebooted, a screen notifying the start of execution of the automatic reboot is displayed (step S114) as in the case where the automatic notification function is enabled (step S109), and a predetermined standby When the time has elapsed, an automatic reboot is executed (step S115), a screen is displayed to inform the user that the automatic reboot has been executed and a confirmation request is displayed (step S111), and the user normally presses the confirmation button. The screen shifts to a screen (step S112). When the user presses a button for instructing the start of the reboot immediately from the screen informing the start of the automatic reboot, the automatic reboot is executed without passing a predetermined waiting time (step S116). The screen shifts to a screen (step S112).

  With the above operations, for failures that are likely to be recovered by turning the power off / on and that do not require automatic notification, rebooting is performed appropriately and automatically without bothering the user. It will be.

  Next, FIG. 5 is a sequence diagram showing the operation of the image forming apparatus when a reboot target failure occurs.

  In FIG. 5, SCS20 and SRM21 correspond to those shown in FIG. The applications 101 and 102 correspond to the printer application 9, the copy application 10, the fax application 11, and the scanner application 12 in FIG. 1, and the engine 103 corresponds to the hardware resource 4 in FIG. The xCS 104 corresponds to a process of the control service layer 7 such as NCS 13, DCS 14, FCS 16, ECS 17, MCS 18, UCS 19 in FIG. Note that the processing related to rebooting is mainly performed by the functional unit in the SCS 20 shown in FIG.

  In FIG. 5, when a failure to be rebooted (a failure of type D and occurs for the first time) occurs and the SCS 20 detects this (step S201), a screen is displayed to notify the start of automatic reboot. (Step S202) At the same time, the applications 101 and 102 are notified of the operation stop (Steps S203 and S204), and the engine 103 is notified of the operation stop via the SRM 21 (Steps S205 and S206). As a result, the applications 101 and 102 enter the operation stop process, stop the job, and the like (step S207), and notify the SCS 20 of an operation stop response when the operation stop process is completed (steps S210 and S211). Further, the engine 103 also enters a state in which no new process control is performed, and notifies the SCS 20 of an operation stop response (steps S208 and S209).

  Next, after confirming the response from each part (step S212), the SCS 20 notifies the xCS 104 to the engine 103 via the SRM 21 and to the applications 101 and 102 almost simultaneously (steps S213 to S217). , Causing each unit to perform operation suppression processing (post-processing to stop the operation in a state where a well-processed reboot can be safely performed, suppression of new operation by suppressing the interface, etc.) After a response to suppress operation (steps S218 to S222), reboot is executed (step S223). Then, a screen for informing the user that automatic reboot has been executed and requesting confirmation is displayed (step S224).

  Next, FIG. 6 is a sequence diagram showing counter-related operations when a reboot target failure occurs. FIG. 6 shows a period from the occurrence of a failure to be rebooted in FIG. 5 during printing (step S201) to the notification of operation suppression (steps S216 and S217). In FIG. 6, it is assumed that two sheets are printed continuously.

  6, when the print job start is notified from the application 101 to the xCS 104 (step S301), the xCS 104 notifies the SCS 20 of the start of the first print process (step S302), and the SCS 20 notifies the engine 103. In response to this, the process start of the first print is notified (step S303). In response to this, the engine 103 starts feeding the first sheet and notifies the SCS 20 to that effect (step S304), and the SCS 20 further notifies the xCS 104 (step S305). In response to this, the xCS 104 notifies the SCS 20 of the process start of the second print (step S306), and the SCS 20 notifies the engine 103 of the process of the second print start (step S307). When 103 starts feeding the second sheet, it notifies the SCS 20 of that (step S308).

  Thereafter, when a failure to be rebooted occurs (step S309), the SCS 20 makes an operation stop request to the application 101 (step S310). In response to this, the application 101 notifies the xCS 104 of job cancellation (step S311), the xCS 104 notifies the SCS 20 of the first process cancellation (step S312), and the SCS 20 notifies the engine 103 of this (step S311). Step S313). Subsequently, similarly, the xCS 104 notifies the SCS 20 of the second process cancellation (step S314), and the SCS 20 notifies the engine 103 of the cancellation (step S315).

  The engine 103 tries to cancel the process as much as possible, but if the cancellation of the first print that has already entered the process is not in time, the print is executed and the engine is (Step S316), the SCS 20 is notified of the completion of fixing the first sheet (step S317). In response to this, the SCS 20 increases the total counter on the controller side (step S318), makes a count request to the engine 103 (step S319), and in response to this, the engine 103 increases the counter of the charging device on the engine side. (Step S320).

  Thereafter, the engine 103 notifies the SCS 20 when the first sheet is normally discharged (step S321), and the SCS 20 further notifies the xCS 104 (step S322), and the xCS 104 further notifies the application 101. (Step S323). In this case, unlike the operation suppression, when the operation is stopped, the interface and the like are not suppressed, so that the transmission is normally performed. Accordingly, in response to this, the application 101 issues a count request to the SCS 20 (step S324), and the SCS 20 increases the counter of the accounting device on the controller side (step S325).

  After that, the engine 103 cancels the second print, and thus performs abnormal paper discharge (paper discharge as it is) and notifies the SCS 20 (step S326), and the SCS 20 further notifies the xCS 104 ( In step S327), the xCS 104 further conveys this to the application 101 (step S328). Since the operation stop of the process relating to the print job that has been continued is completed, the xCS 104 notifies the application 101 of the end of the job (step S329), and the application 101 notifies the SCS 20 of an operation stop response (step S329). Step S330).

  Thereafter, the SCS 20 waits for an operation stop response from another part (a predetermined time up is provided), and enters an operation suppression process (steps S331 and S332).

  As is clear from the above operation, each of the engine-side mechanical counter, the engine-side charging device counter, the controller-side total counter, and the controller-side charging device counter for each of the first prints that have been performed normally. Will be up normally and no inconsistency will occur.

  Next, FIG. 7 is a sequence diagram showing operations from the operation suppression to the reboot execution (steps S213 to S223) in FIG.

  In FIG. 7, the SCS 20 notifies the xCS 104, the applications 101 and 102, and the engine 103 of operation suppression (steps S401 to S404). Each unit that has received the notification of the operation suppression stops the operation in a state in which the process in process is in good condition and can be rebooted safely as post-processing, and suppresses the new operation by suppressing the interface. Is notified of the response (steps S405 to S408). The SCS 20 times out reception of a response, for example, in 3 minutes.

  Next, the SCS 20 waits for 30 seconds, for example (step S409), and enters the execution of reboot. Here, a communication stop request of the operation unit driver is made to the OCS 15, but there is no response because it is blocked in the function (step S410). Subsequently, the SCS 20 issues a reset request to the engine 103 (step S411) and receives a response from the engine 103 (step S412). Then, HDD access stop processing (step S413), engine power OFF (step S414), engine power ON (step S415), and reboot of the applications 101 and 102 (step S416) are sequentially performed on the engine 103. The controller is activated (step S417), and the engine configuration is received from the engine 103 (step S418).

  In this way, the operation of each module is suppressed, and after the processing during operation and the interface are suppressed, the system can be rebooted promptly without causing any remaining paper, HDD failure, data garbage, etc. it can.

1 is a configuration diagram of an image forming apparatus according to an embodiment of the present invention. 1 is a hardware configuration diagram of an image forming apparatus according to an embodiment of the present invention. It is a block diagram which shows the structural example of the function part for the failure response in SCS. FIG. 6 is an operation flow diagram illustrating an operation of the image forming apparatus when a failure occurs. FIG. 10 is a sequence diagram illustrating an operation of the image forming apparatus when a reboot target failure occurs. It is a sequence diagram which shows the counter related operation | movement at the time of reboot object failure generation | occurrence | production. It is a sequence diagram which shows operation | movement from operation suppression to reboot execution. It is a sequence diagram which shows the counter related operation | movement at the normal time. It is a sequence diagram which shows the conventional operation | movement at the time of reboot object failure generation | occurrence | production. It is a sequence diagram which shows the conventional counter related operation | movement at the time of reboot object failure generation | occurrence | production.

Explanation of symbols

1 Image forming device 15 OCS
20 SCS
20a Failure detection unit 20b Log writing unit 20c Reboot target failure detection unit 20d Screen display control unit 20e Automatic notification control unit 20f Operation stop control unit 20g Operation suppression control unit 20h Reboot execution control unit 21 SRM
101 application 102 application 103 engine 104 xCS

Claims (18)

In an image forming apparatus having hardware resources used for image formation and a program for performing processing relating to image formation,
Means for detecting a failure to be rebooted out of failures that are likely to be recovered by power OFF / ON;
Means for stopping the operation of the hardware resource and the program immediately after detecting the failure to be rebooted;
An image forming apparatus comprising: the hardware resource and means for rebooting the program. A total counter provided on the controller side of the above program;
A billing device counter provided on the controller side;
A mechanical counter provided on the engine side of the hardware resource;
The image forming apparatus according to claim 1, further comprising a counter of a charging device provided on the engine side.   The image forming apparatus according to claim 1, wherein the operation stop includes a job stop and a new process control stop.   The image forming apparatus according to claim 3, wherein the application of the program cancels an incomplete job when the job is stopped.   5. The image forming apparatus according to claim 1, wherein the operation of the hardware resource and the program is suppressed after completion of the operation stop and before the reboot. 6.   The image forming apparatus according to claim 5, wherein the image forming apparatus waits for a predetermined time from the response from the hardware resource and the program to the operation suppression until the reboot is executed.   The failure to be rebooted is a case where a failure that has a high possibility of being recovered by turning the power OFF / ON occurs within a range that does not reach a predetermined number of times during a predetermined number of printings. The image forming apparatus according to any one of 1 to 6.   The image forming apparatus according to claim 7, wherein the predetermined number is 10 and the predetermined number is two.   Each of the above means is configured as one function of a system control service that performs processing such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control. The image forming apparatus according to any one of 1 to 8.   10. The reboot of the hardware resource and the program includes sequentially resetting the engine, stopping access to the hard disk drive, turning off the engine power, turning on the engine power, and rebooting the application. The image forming apparatus according to claim 1.   11. The image forming apparatus according to claim 1, wherein a screen informing the start of execution of automatic reboot is displayed when a failure to be rebooted is detected.   12. The image forming apparatus according to claim 11, wherein the screen informing the execution start of the automatic reboot includes a display indicating a progress status of post-processing of the hardware resource and the program.   The image forming apparatus according to claim 11, wherein the screen informing the start of execution of the automatic reboot includes a display indicating a time until the reboot is executed.   14. The image forming apparatus according to claim 11, wherein the screen informing the start of execution of the automatic reboot includes a button for instructing the start of the reboot immediately.   The image forming apparatus according to claim 1, wherein a screen for requesting confirmation from the user is displayed after the reboot. A step of detecting a failure to be rebooted out of failures that are likely to be recovered by power OFF / ON in an image forming apparatus having hardware resources used for image formation and a program for performing processing relating to image formation; ,
Immediately stopping the operation of the hardware resource and the program immediately after detecting the failure to be rebooted,
An automatic reboot method comprising the steps of rebooting the hardware resource and the program.   17. The automatic reboot method according to claim 16, wherein the operation stop includes stop of a job and generation of new process control.   18. The automatic reboot method according to claim 16, wherein the application of the program cancels an incomplete job when the job is stopped.

Images