Patent Application
20200314251
The present disclosure relates to an image forming apparatus such as a copier or a printer and, more particularly, to user interface (UI) control in a case where, when a malfunction occurs in the apparatus, the image forming apparatus makes a self-diagnosis of a fault to identify a location where the fault occurs.
According to a conventional technology, an image forming apparatus with a print function is provided which is capable of making a self-diagnosis in response to an error (abnormality) occurring in a hardware device during a job execution (Japanese Patent Application Laid-Open No. 2015-131415).
When a fault diagnosis is made when an error occurs, it is sometimes necessary to remove a sheet of paper remaining, due to a paper jam or the like, in a paper path through which the paper passes within the apparatus.
Usually, the image forming apparatus is capable of performing processing such as scan transmission without using paper even if a user does not remove the paper; therefore, the apparatus may be left while no action of the fault diagnosis is taken. Even if notification is given to prompt the user to remove the paper, he/she possibly cannot determine whether the notification is jam notification involving a fault diagnosis or normal jam notification.
As a consequence, there is a concern that a self-diagnosis is not made quickly which is necessary for effective maintenance such as identifying a location where the fault has occurred.
According to an aspect of the present disclosure, an image forming apparatus includes a display unit, a processor and a memory storing instructions that, when the instructions are executed by the processor, cause the image forming apparatus to perform operations including: displaying, in the display unit, a screen including a message for prompting removal of a sheet remaining in a paper path of the image forming apparatus, wherein, when the screen is displayed in a case where diagnosis processing is required on a detected abnormality, the screen does not include an instruction portion that allows the screen to be closed without removing the sheet, and wherein, when the screen is displayed in a case where the diagnosis processing is not required, the screen includes the instruction portion that allows the screen to be closed without removing the sheet, and performing the diagnosis processing, in response to a detection of removal of a sheet remaining in a paper path of the image forming apparatus in the case where the diagnosis processing is required.
Further features of the present disclosure will become apparent from the following description of exemplary embodiments with reference to the attached drawings.
Exemplary embodiments for describing modes for carrying out the present disclosure are described below with reference to the drawings.
The first exemplary embodiment is hereinafter described.
The PC 110 sends print data and so on via the network 100 to the multifunction peripheral 120. The multifunction peripheral 120 is a device for implementing a plurality of functions, e.g., copying, printing, scanning, and faxing. The multifunction peripheral 120 has, therein, a function of keeping a history of execution of the plurality of functions and a function of keeping a record of the occurrence of an error (abnormality) or an alarm. The multifunction peripheral 120 is detailed below. The below description takes an example of a multifunction peripheral; however, it is only required that the apparatus is an image forming apparatus for conveying a sheet to perform image processing, and the apparatus may be a single-function printer having a print function, a single-function scanner having a scan function, or the like.
Hardware Configuration
The information processing controller unit 201 includes a central processing unit (CPU) 301 which starts an operating system (OS) with a boot program stored in a read-only memory (ROM) 302. The ROM 302 includes a flash memory such as an embedded multimedia card (eMMC) and a controller thereof, and serves to store a control program of the CPU 301. The CPU 301 executes, on the OS, an application program stored in the ROM 302 or a hard disk drive (HDD) 304 to perform various processing. As a work area of the CPU 301, a random-access memory (RAM) 303 is used. Further, in addition to the work area, the RAM 303 provides an image memory area for temporarily storing image data. The ROM 302 or the HDD 304 stores the application program, image data, and various setting values. The HDD 304 may not be built-in in some cases.
The CPU 301 is connected to, an operation unit interface (I/F) 306, a device controller I/F 308, a network 305, and an image processing unit 307 as well as to the ROM 302 and the RAM 303 via a system bus 309.
The operation unit I/F 306 is an interface with the operation unit 206 having a touch panel. The operation unit I/F 306 outputs, to the operation unit 206, image data to be displayed in a display unit of the operation unit 206. The operation unit I/F 306 also sends, to the CPU 301, information entered by a user using the operation unit 206.
The device controller I/F 308 is connected to the scanner controller unit 203 and the printer controller unit 202, and the device controller I/F 308 performs synchronous conversion and asynchronous conversion on image data.
The network 305 is connected to the network 100, and inputs and outputs information, via the network 100, from/to the individual devices on the network 100.
The image processing unit 307 performs processing for outputting an image to the printer 204, processing for inputting an image from the scanner 205, image rotation, image compression, resolution conversion, color space conversion, gradation conversion, and so on.
The printer controller unit 202 is connected to the printer 204 having, for example, an electrophotographic printer engine. An engine control unit 313 controls the printer engine to carry out printing in accordance with image data received via the device controller I/F 308 from the information processing controller unit 201.
The printer controller unit 202 includes a CPU 310, and the CPU 310 executes a program stored in a ROM 311, uses a RAM 312 as a work memory to control the printer 204.
Software Configuration
The multifunction peripheral firmware 400 is stored in a storage unit of any one of the ROM 302, the RAM 303, and the HDD 304. When being executed by the CPU 301, the multifunction peripheral firmware 400 functions.
A job control module 401 is connected via the network 305 to the network 100. The job control module 401 receives a job such as printing with a specific communication protocol, and executes a job such as copying, printing, or scanning. At the time, the job control module 401 saves a job execution history in a job execution history database (DB) 402. In addition, the job control module 401 is capable of returning job-related data in response to an inquiry from another module, and of receiving an event purchase request to convey an event at a time of a state change of a job. For example, the event can be conveyed at a time when a job starts, stops, or ends. The job execution history DB 402 stores, therein, a job execution history which includes information associated with job execution such as an execution start date and time, an execution end date and time, the number of fed sheets of paper, the number of ejected sheets of paper, and the presence/absence of stapling; however, the job execution history may include other contents. The job execution history stored in the job execution history DB 402 is stored in the HDD 304. An operation unit control module 403 receives user operation for giving a command to execute a job such as copying or scanning from the operation unit 206 via the operation unit I/F 306 to notify the job control module 401.
A device controller I/F control module 404 is a module that receives image data to be processed and control data from the job control module 401 to control the printer controller unit 202 and the scanner controller unit 203. The device controller I/F control module 404 also receives, from the printer controller unit 202 and the scanner controller unit 203, usage information, sensor values, and fault-related information about parts installed in the printer 204 and the scanner 205.
A state management module 405 is a module that manages a state of the multifunction peripheral 120. The state management module 405 serves to manage an error code or an alarm code given in notification, for example, by the printer 204 and the scanner 205 connected to the multifunction peripheral 120. The error code is a code that indicates an error cause at a time when the operation of the multifunction peripheral 120 stops or degenerates. The alarm code is a code that indicates the occurrence of an abnormality in the apparatus although the operation of the multifunction peripheral 120 does not stop or degenerate. The state management module 405 records, in the state management DB 406, information concerning an error (abnormality) or an alarm given by the job control module 401 and the like.
When an error (abnormality) occurs in the printer controller unit 202 or the scanner controller unit 203, the state management module 405 also records, in the state management DB 406, a unit code calculated in a fault diagnosis processing module 409 of the printer controller unit 202 or the scanner controller unit 203. The unit code is information including a location where a fault has occurred, which is identified as a result of execution of a fault diagnosis program and an action method for recovering from the fault, and the unit code is detailed below with reference to
The printer controller unit firmware 407 is stored in a storage unit of either one of the ROM 311 and the RAM 312. When executed by the CPU 310, the printer controller unit firmware 407 functions.
An execution processing module 408 executes print processing on the basis of a print processing request sent from the device controller I/F control module 404. When the occurrence of an error is detected in the print processing, the execution processing module 408 requests the fault diagnosis processing module 409 to make a fault diagnosis.
The fault diagnosis processing module 409 performs fault diagnosis processing on the basis of a code of an error which has occurred in the print processing executed in the execution processing module 408. Further, the fault diagnosis processing module 409 serves to identify a location of the fault which has caused an error as a result of the fault diagnosis, and to calculate a unit code including an action method for recovering the fault area.
A part code 502 represents a unit corresponding to a faulty part, of the multifunction peripheral 120, which has caused an error identified in the result of the fault diagnosis. Examples of the unit include the information processing controller unit 201, the HDD, a fixing unit, a drum unit, a developing unit, and an intermediate transfer belt (ITB) unit included in the multifunction peripheral 120.
In a case where the unit has a sub-unit, sub-unit information 503 may be added. As the sub-unit information, in the case of a toner cartridge for example, Y, M, C, and K can be defined as the sub-unit information.
A part detailed code 504 represents a sub-component part in the unit. As to the fixing unit, for example, the part detailed code 504 represents the unit itself, a fixing film, a pressure roller, and so on.
An action information code 505 represents information about measures necessary to take against the faulty unit or the sub-component identified in the result of the fault diagnosis. Examples of the action method include a code indicating the need for replacement, a code indicating a high possibility of fault, a code indicating the need for cleaning, and a code indicating the need for adjustment.
An occurrence section code 506 is information that indicates a fault occurrence section and is used to identify a place where the unit is installed.
Entire Flow of Print Processing (Information Processing Controller)
The flow of processing performed within the information processing controller unit 201 will be discussed with reference to
In an image generation processing step S601, the job control module 401 causes the image processing unit 307 to perform processing for converting print data described in page description language (PDL) and so on into image data in a form that the printer 204 can interpret.
In the subsequent image print processing step S602, the job control module 401 requests the device controller I/F control module 404 to perform print processing for the image. The device controller I/F control module 404 requests the printer controller unit 202 to perform print processing for the image. The flow of processing in the printer controller unit 202 performed in step S602 is described below with reference to
In the subsequent step S603, the job control module 401 receives, from the device controller I/F control module 404, a result of the print processing, an event of paper jam detection, an event of the occurrence of an error, and so on. The job control module 401 requests the operation unit control module 403 to generate a screen in accordance with the content of the event thus received, and the operation unit control module 403 displays the screen in the display unit of the operation unit 206 via the operation unit I/F 306. The details of step S603 will be described below with reference to
The details of the flow of the image print processing executed in the printer controller unit 202 in step S602 will be described with reference to
In step S701, the execution processing module 408 requests the printer 204 to execute the print processing.
In step S702, the execution processing module 408 determines whether an error has occurred as a result of the print processing in step S701. If no error has occurred (NO in step S702), then the image print processing is finished. On the other hand, if an error has occurred (YES in step S702) as a result of the determination in step S702, the processing proceeds to step S703, and the image forming apparatus is brought to an emergency stop.
Next, in order to identify a cause of the error, in step S704, the fault diagnosis processing module 409 performs fault diagnosis processing. The details of the fault diagnosis processing in step S704 will be described below with reference to
Next, the details of the fault diagnosis processing in step S704 of
First, in step S710, a type of fault diagnosis is identified on the basis of the error which has occurred in the print processing of step S701. Table 1 shows one example of a correspondence relationship between an error code related to the error which has occurred in the print processing of step S701 and the type of fault diagnosis.
The type of fault diagnosis is the following two types. The type of fault diagnosis is determined to be a type ‘1’ in a case where the fault diagnosis can be made with a print sheet remaining in the apparatus. The type of fault diagnosis is determined to be a type ‘2’ in a case where the fault diagnosis cannot be made with the print sheet remaining in the apparatus due to a possibility of damage to the print sheet and the apparatus.
Table 1 indicates, for example, that the type of fault diagnosis is determined to be ‘2’ in a case where a fault corresponding to an error code ‘E006’ occurs.
Next, in step S711, the fault diagnosis processing module 409 determines whether the type of fault diagnosis corresponds to ‘2’ on the basis of the type of fault diagnosis determined in step S710.
If the type of fault diagnosis is determined to be ‘1’ (NO in step S711), the processing proceeds to step S716. If the type of fault diagnosis is determined to be ‘2’ (YES in step S711), the processing proceeds to step S712.
In step S712, the fault diagnosis processing module 409 determines whether there is a remaining sheet. If it is determined that no sheet remains (NO in step S712), then the processing proceeds to step S716. If it is determined that a sheet remains in step S712 (YES in step S712), then the processing proceeds to step S713.
In step S713, the fault diagnosis processing module 409 notifies the job control module 401 of identification information showing that the sheet is remaining, and the processing proceeds to step S714.
In the present exemplary embodiment, as the identification information showing that the sheet is remaining, a jam code that is different from a paper jam in a paper path serving as paper passage route in normal printing, is generated and is given as notification. The jam code herein is a code indicating a paper jam state including a location where the paper jam has occurred in the paper path.
The paper jam notification given in a case where the occurrence of an error is detected in step S702 of
The information processing controller unit 201 receives the ‘paper jam notification involving a fault diagnosis’ from the printer controller unit 202 and displays a paper jam screen as appropriate, and so on. The operation of the information processing controller unit 201 will be described below with reference to
In step S714, the fault diagnosis processing module 409 waits until the remaining sheet is removed, and if the remaining sheet is removed (YES in step S714), then the processing proceeds to step S715.
In step S715, the information processing controller unit 201 is notified that the paper jam has been cleared. Upon the receipt of the notification, the information processing controller unit 201 clears the paper jam screen, and the processing proceeds to step S716.
If, in step S711, the type of fault diagnosis is determined to be ‘1’ (NO in step S711), and in step S712, no sheet remains (NO in step S712), or if the paper jam has been cleared, then the processing proceeds to step S716. In step S716, the fault diagnosis processing module 409 notifies the information processing controller unit 201 to start a fault diagnosis, and the processing proceeds to step S717.
In step S717, the fault diagnosis processing module 409 executes the fault diagnosis program to identify a location of the fault. More specifically, the printer controller unit 202 diagnoses the printer 204 mechanically or electrically to identify a location of the fault. As a result of execution of the fault diagnosis program, the printer controller unit 202 identifies a location of the fault, record the same as a unit code, in the RAM 312, informs the information processing controller unit 201 of the completion of the fault diagnosis, and then finishes the fault diagnosis processing.
The flow of processing performed in the job control module 401 at a time when an event notified to the information processing controller unit 201 in the flow of processing of
[Processing when Paper Jam (No Error) has Occurred]
First, a description is given of the flow of processing in a case where notification of an event that a paper jam has occurred while no error occurs in printing is received from the printer controller unit 202.
In step S801, the CPU 301 determines whether a paper jam has occurred. In a case where the paper jam has occurred in printing (YES in step S801), the printer controller unit 202 notifies a jam code which is paper jam information showing the occurrence of the paper jam.
Subsequently, in step S802, it is determined whether the notification is ‘paper jam notification involving a fault diagnosis’ on the basis of the notified jam code.
In step S802, in a case where the notification is determined not to be ‘paper jam notification involving a fault diagnosis’ (NO in step S802), the processing proceeds to step S803.
In step S803, the information processing controller unit 201 gives an instruction to display a paper jam screen 901 (
A case will be described where the paper jam screen 901 is displaying a normal paper jam in the display unit of the operation unit 206, and in this state, an event that the “close” button 902 as the instruction portion continues to be pressed, is received from the operation unit 206.
In such a case, in the flow of processing of
In step S807, the operation unit control module 403 is requested to close the active paper jam screen 901 showing the normal paper jam.
[Processing when Paper Jam Involving Fault Diagnosis has Occurred]
Next, a description is given of the flow of processing at a time when an event that the paper jam involving a fault diagnosis has occurred is received from the printer controller unit 202.
In step S801, it is determined that the paper jam has occurred (YES in step S801) and the processing proceeds to step S802.
In step S802, a determination is made by using a jam code. The jam code is identification information which shows that there is a remaining sheet. With respect to the remaining sheet, the notification is given by the printer controller unit 202 about whether it is ‘paper jam notification involving a fault diagnosis’. If the notification is determined to be ‘paper jam notification involving a fault diagnosis’ (YES in step S802), then the processing proceeds to step S804.
In step S804, the operation unit control module 403 is requested to display a paper jam screen 903 (
The paper jam screen 903 involving a fault diagnosis changes display of the “close” button 902 arranged in the normal paper jam screen 901, or a button corresponding thereto, which is an instruction portion giving an instruction for deferring processing for removing the jammed sheet. More specifically, as shown in
Further, it is possible to display, in a lower part of the paper jam screen for giving paper jam notification involving a fault diagnosis, a message 905 showing the need for removing the jammed sheet in order to make the fault diagnosis.
An effect of displaying the screen is that, differently from a normal paper jam, the user knows the need for clearing the paper jam to make the fault diagnosis, and the user can, therefore, understand that the fault diagnosis is made after the paper jam is cleared, and the continued use is not allowed.
The screen display is made as above described and the flow of processing ends.
[Processing when State of Paper Jam Involving Fault Diagnosis is Cleared]
In a case where the user removes a jammed sheet, in step S715 of
In step S807, the operation unit control module 403 is requested to close the paper jam screen 903 involving a fault diagnosis, and the flow of processing ends.
[Processing when Fault Diagnosis is Completed]
Next, a description is given of the flow of processing in a case where, when the fault diagnosis is completed, event notification to that effect is received from the printer controller unit 202. When the fault diagnosis is completed, in the flow of processing of
In step S808, the determination is YES because an error code is given in notification at a time when notification of completion of fault diagnosis in step S705 is given, and the processing proceeds to step S809.
In step S809, the job control module 401 obtains the unit code 501 related to an error from the printer controller unit 202 via the device controller I/F control module 404. Alternatively, the unit code 501 may be returned along with the completion of the flow of processing of
In step S810, an error screen 906 (
In the foregoing flow of processing, in a case where the paper jam involving the fault diagnosis caused by an emergency stop of a device when an error has occurred, identification information is given which shows the presence of the remaining sheet different from that in the normal paper jam. Further, in a case where the paper jam involving the fault diagnosis occurs, by switching of a user interface (UI) control in accordance with the identification information showing the presence of the remaining sheet, a display is made in a UI in order to quickly remove the sheet. Since the UI display shows that removal of a sheet is necessary to make the fault diagnosis, the user can understand that the fault diagnosis is made after the paper jam is cleared, and the continued use is not allowed. This reduces the confusion of the user about operation after the paper jam is cleared.
Hereinafter, a second exemplary embodiment is described. In the first exemplary embodiment, the multifunction peripheral 120 is brought to an emergency stop in response to the occurrence of an error, and consequently, the paper jam screen 903 involving a fault diagnosis is displayed at a time when a paper jam has occurred. After the paper jam is cleared, the fault diagnosis is made, and when the fault diagnosis is finished, an error code and a unit code are displayed in the display unit of the operation unit 206. In the second exemplary embodiment, the flow of control processing is described in which an error screen is displayed immediately after the occurrence of an error, then the image forming apparatus is brought to an emergency stop, and the paper jam screen is displayed. The second exemplary embodiment focuses on points that are different from the first exemplary embodiment, and a description of flow that is similar to that in the first exemplary embodiment is omitted.
In the second exemplary embodiment, as for the flow of processing in the information processing controller unit 201 in a case where the multifunction peripheral 120 starts print processing, an error occurs in the printer 204 during the print processing, and the fault diagnosis is made, the description of the flow is omitted because the flow of processing is similar to that of
The flow of processing corresponding to
The flow of
The description of the subsequent image forming apparatus emergency stop (step S703) and the fault diagnosis processing (step S704) is omitted because the processing thereof is similar to that in the first exemplary embodiment.
Next, the description is given, with reference to
[Processing when Error has Occurred]
When an event occurs that an error state is notified in the error state notifying processing of step S1001 of
In step S808, a determination of YES is made because an error has occurred, and the processing proceeds to step S1201.
Subsequently, in step S1201, the job control module 401 requests the operation unit control module 403 to display the error screen 1101 including error information related to an error code given in the error state notifying processing of step S1001. The event processing is then finished.
[Processing when Paper Jam Involving Fault Diagnosis has Occurred]
In the print processing (step S701) of the flow of processing in
In this case, clearing of the paper jam is necessary to make a fault diagnosis (YES in step S711, and YES in step S712), and a jam code related to the paper jam is notified in the subsequent paper jam notification of step S713. The jam code in such a case is notified as a jam code different from that of a normal paper jam.
Then, the information processing controller unit 201 receives an event of the paper jam notification, and the processing proceeds to the flow of processing of
In step S1202, a paper jam screen involving a fault diagnosis is displayed in the display unit of the operation unit 206.
One example of a paper jam screen 1103 involving a fault diagnosis (
Further, in the foregoing description, the paper jam screen is displayed as soon as the paper jam is notified. Instead of this, however, it is possible to keep the error screen as-is because of the error occurrence state, and display the paper jam screen in response to pressing of a button in the error screen. One example of an error screen 1105 in such a case is shown (
[Processing when Fault Diagnosis is Completed]
A description will be given, with reference to
In the foregoing flow of processing, also in the case of displaying an error screen along with the occurrence of an error, if a paper jam involving a fault diagnosis caused by an emergency stop of a device has occurred, identification information is given which shows the presence of a remaining sheet different from that in a normal paper jam. Further, in a case where a paper jam involving a fault diagnosis has occurred, by switching of a UI control in accordance with the identification information showing the presence of a remaining sheet, the control method of the UI is changed such that the sheet is quickly removed. Further, by indicating that removal of a sheet is necessary to make a fault diagnosis in the UI display, the user can understand that the fault diagnosis is made after the paper jam is cleared, and the continued use is not allowed. This reduces the confusion of the user about operation after the paper jam is cleared.
In the foregoing exemplary embodiments, in the paper jam screens 903 and 1103 involving a fault diagnosis that prompt the user to remove a sheet, buttons to close the paper jam screens 903 and 1103 are not displayed or are blacked out. Instead of this, in another aspect, a close button is displayed in the screen to allow the user to press the button to close the screen, and pressing of the close button displays a message to the effect that diagnosis processing cannot be made.
Embodiment(s) of the present disclosure can also be realized by a computer of a system or apparatus that reads out and executes computer executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be referred to more fully as a ‘non-transitory computer-readable storage medium’) to perform the functions of one or more of the above-described embodiment(s) and/or that includes one or more circuits (e.g., application specific integrated circuit (ASIC)) for performing the functions of one or more of the above-described embodiment(s), and by a method performed by the computer of the system or apparatus by, for example, reading out and executing the computer executable instructions from the storage medium to perform the functions of one or more of the above-described embodiment(s) and/or controlling the one or more circuits to perform the functions of one or more of the above-described embodiment(s). The computer may include one or more processors (e.g., central processing unit (CPU), micro processing unit (MPU)) and may include a network of separate computers or separate processors to read out and execute the computer executable instructions. The computer executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, one or more of a hard disk, a random-access memory (RAM), a read only memory (ROM), a storage of distributed computing systems, an optical disk (such as a compact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™), a flash memory device, a memory card, and the like.
While the present disclosure has been described with reference to exemplary embodiments, it is to be understood that the disclosure is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.
This application claims the benefit of Japanese Patent Application No. 2019-058732, filed Mar. 26, 2019, which is hereby incorporated by reference herein in its entirety.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2019-058732 | Mar 2019 | JP | national |
