Image processing apparatus, control method, and storage medium

Abstract

To enable a serviceman to accurately specify the cause of a jam occurring in an image processor.SOLUTION: An image processing apparatus includes jam occurrence history display means for displaying a screen of a history of a jam in at least one place in the image processing apparatus, and jam detail display means for displaying details of individual histories of jams occurring in the same place on the basis of user operation to the screen of the history of the jam. At least one of the jam occurrence history display unit and the jam detail display unit displays at least one of a date and time of occurrence of the jam and sheet information about a sheet that has caused the jam.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an image processing apparatus, a control method, and a program. [Background technology]

[0002] There is a technology that notifies a service technician that maintenance is required when paper jams (hereinafter referred to as "jams") frequently occur in an image processing device such as a multifunction peripheral or a printer. This technology enables the service technician to respond appropriately to the jams based on the notification. There is also a known technology that supplements such notifications with information that is useful for maintenance to prevent jams from occurring.

[0003] For example, the management device disclosed in Patent Document 1 notifies a user of a problem along with supplemental information about the changed environment when a change that satisfies a predetermined condition occurs in the environment, such as temperature, humidity, or counter information about the number of printed sheets. The supplemental information helps a service technician perform maintenance. The change in the environment is detected by measuring the temperature, humidity, and other factors inside and outside the image processing device using a temperature sensor, humidity sensor, and the like. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-141797 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-described management device may not be able to notify the service technician of the supplementary information necessary to identify the cause of the jam.

[0006] SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide an image processing apparatus, a control method, and a program that enable a service person to accurately identify the cause of a jam that has occurred in the image processing apparatus. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, the image processing device of the present invention includes a jam occurrence history display means for displaying a screen of a jam history at at least one location in the image processing device, and a jam details display means for displaying details of each history of jams that have occurred at the same location based on a user operation on the jam history screen. At least one of the jam occurrence history display means and the jam details display means displays at least one of the date and time when the jam occurred and paper information related to the paper on which the jam occurred. [Effects of the Invention]

[0008] According to the present invention, it is possible to provide an image processing apparatus, a control method, and a program that enable a service person to accurately identify the cause of a jam that has occurred in the image processing apparatus. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a system configuration of an image processing system. [Figure 2] FIG. 1 illustrates an example of a hardware configuration of an image processing apparatus. [Figure 3] FIG. 2 is a diagram illustrating an example of processing functions of a processing unit of the image processing apparatus, illustrating functions related to the first embodiment. [Figure 4] FIG. 10 is a diagram illustrating an example of a top screen of a status monitor. [Figure 5] FIG. 10 is a diagram illustrating an example of a top screen of a status monitor. [Figure 6] FIG. 10 is a diagram illustrating an example of a parts life screen. [Figure 7] FIG. 10 is a diagram illustrating an example of a status details screen. [Figure 8]FIG. 10 is a diagram illustrating an example of a trouble detection screen. [Figure 9] FIG. 10 is a diagram showing an example of a stain details screen. [Figure 10] FIG. 10 is a diagram illustrating an example of an error screen. [Figure 11] FIG. 10 is a diagram illustrating an example of an error details screen. [Figure 12] FIG. 10 is a diagram showing an example of a jam screen. [Figure 13] FIG. 10 is a diagram showing an example of a jam details screen. [Figure 14] FIG. 10 is a diagram illustrating an example of a usage status screen. [Figure 15] FIG. 10 is a diagram illustrating an example of a usage status screen. [Figure 16] FIG. 10 is a diagram illustrating an example of a usage status screen. [Figure 17] FIG. 10 is a diagram illustrating an example of a usage status screen. [Figure 18] FIG. 10 is a diagram illustrating an example of history data of part lifespans. [Figure 19] FIG. 10 is a diagram illustrating an example of history data of trouble detection. [Figure 20] FIG. 10 is a diagram illustrating an example of error history data. [Figure 21] FIG. 10 is a diagram showing an example of jam history data. [Figure 22] FIG. 10 is a diagram illustrating an example of history data of usage status. [Figure 23] FIG. 10 is a diagram illustrating an example of history data of usage status. [Figure 24] FIG. 10 is a diagram illustrating an example of history data of usage status. [Figure 25] FIG. 10 is a diagram illustrating an example of history data of usage status. [Figure 26] 10 is a flowchart showing an example of the start-up of a status monitor top screen. [Figure 27] 10 is a flowchart showing an example of the start-up of a status monitor top screen. [Figure 28] 10 is a flowchart showing an example of the start-up of a status monitor top screen. [Figure 29]10 is a flowchart showing an example of screen transitions to a status monitor top screen and each detailed screen. [Figure 30] 10 is a flowchart showing an example of screen transitions to a status monitor top screen and each detailed screen. [Figure 31] 10 is a flowchart showing an example of screen transitions to a status monitor top screen and each detailed screen. [Figure 32] 10 is a flowchart illustrating a process of saving a jam occurrence history. [Figure 33] 10 is a flowchart illustrating a process for displaying a jam screen and a jam details screen. [Figure 34] 10 is a flowchart illustrating a process for displaying a jam screen according to a second embodiment. [Figure 35] FIG. 11 is a diagram showing how the history of a location mapped on a cross-sectional view of the image processing apparatus within the jam screen is displayed at a higher level in the second embodiment. [Figure 36] 13 is a flowchart illustrating a process for displaying a jam screen according to a third embodiment. [Figure 37] FIG. 11 is a diagram showing how, in the third embodiment, a service technician can select any icon mapped on a cross-sectional view of the image processing device in the jam screen to display a history of jams that have occurred at the selected location. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0011] [First embodiment] <System configuration> 1 is a diagram showing an example of the system configuration of an image processing system. The system according to the first embodiment includes an image processing device 103 connected to a network, a server PC (personal computer) 101 which is an information processing device, and a client PC 102 which is also an information processing device.

[0012] The image processing device 103 is a multifunction copier (MFP: Multifunction Peripheral). The image processing device 103 has not only a function for copying paper documents, but also a function for printing print data sent from an external printer driver and a function for sending image data generated by reading paper documents to an external file server or email address (SEND function). The image processing device 103 also has functions such as a function for sending data to another image processing device and printing it at the destination image processing device (remote copy function, facsimile function), etc.

[0013] In the first embodiment, the image processing device 103 is connected via Ethernet (registered trademark), not shown, but is not limited to this. In the first embodiment, the server PC 101 and the client PC 102, other than the image processing device 103, may all be configured as the same computer. Alternatively, the server PC 101 and the client PC 102 may be implemented in the image processing device 103, and the system may be configured only by the image processing device 103. Note that the information processing device used in the first embodiment may not be a PC, but may be a terminal device, a smartphone, or the like. The printing method of the image processing device 103 may be, for example, an electrophotographic method, an inkjet method, or another method.

[0014] <Hardware configuration of image processing device> 2 is a diagram showing an example of the hardware configuration of an image processing device. A controller unit 200 is connected to a scanner 270, which is an image input device, and a printer 295, which is an image output device. The scanner 270 is an example of a document reading means that reads documents, and the printer 295 is an example of a printing means that prints an image on a print medium based on image data. The controller unit 200 is also connected to Ethernet (registered trademark), a public line, etc., and executes input and output of image information, device information, etc.

[0015] The CPU (Central Processing Unit) 201 is a controller that controls the image processing device 103. The CPU 201 also operates as a jam-prone location determination means and a jam-current location determination means. The jam-prone location determination means determines whether or not there is a location where a jam has occurred more than a predetermined number of times. The jam-current location determination means determines whether or not there is a location where a jam is currently occurring. Specific examples of the jam-prone location determination means and the jam-current location determination means will be described later.

[0016] The RAM (Random Access Memory) 202 is a system work memory for the operation of the CPU 201, and is also an image memory for temporarily storing image data. The ROM (Read Only Memory) 203 is a boot ROM in which the system boot program is stored. The HDD (Hard Disk Drive) 204 stores system software, applications, image data, etc.

[0017] The operation unit I / F 206 is an interface with an operation unit 212 having a touch panel, and outputs image data to be displayed on the operation unit 212 to the operation unit 212. The operation unit I / F 206 also transmits information input by a system user using the operation unit 212 to the CPU 201. The network I / F is connected to a network and executes input and output of information. The modem 250 is connected to a public line and executes input and output of information.

[0018] The SRAM (Static Random Access Memory) 209 is a non-volatile recording medium capable of high-speed operation. The RTC (Real Time Clock) 211 executes a process of continuously counting the current time even when the controller unit 200 is not powered on. As shown in FIG. 2, these devices are arranged on the system bus 207.

[0019] The image bus I / F 205 is a bus bridge that connects the system bus 207 and an image bus 208 that transfers image data at high speed and converts the data structure. The image bus 208 complies with a PCI (Peripheral Component Interconnect) bus or IEEE1394.

[0020] The RIP (Raster Image Processor) expands PDL (Page Description Language) code into a bitmap image. The device I / F 220 is connected to various sensors 255 and acquires device status. The device I / F 220 also connects image input / output devices such as a scanner 270 and a printer 295 to the controller unit 200 and performs synchronous / asynchronous conversion of image data. The scanner image processing unit 280 corrects, processes, and edits input image data. The printer image processing unit 290 performs printer correction, resolution conversion, etc. on print output image data. The image rotation unit 230 rotates image data. The image compression / decompression unit 240 performs compression / decompression processing. As shown in FIG. 2, the above devices are arranged on the image bus 208.

[0021] <Software configuration of image processing device> 3 is a diagram showing an example of processing functions of the processing unit of the image processing apparatus, which shows functions related to the first embodiment. As described with reference to FIG. 2, the CPU 201 executes part or all of a program on the RAM 202 based on a program stored in the ROM 203, thereby realizing the functions of the processing unit and the processing according to the flowcharts described below.

[0022] The display unit 302 has a function of displaying the status of the image processing device 103 and an operation menu on the operation unit 212. The input unit 303 has a function of receiving operation instructions from a user. The history management unit 304 has a function of processing information and storing the status and usage history of the image processing device 103 in a history DB. The control unit 301 has a function of controlling the display unit 302, input unit 303, and history management unit 304.

[0023] The control unit 301 and the display unit 302 also operate as a jam occurrence history display means and a jam details display means. The jam occurrence history display means displays the history of jams that occurred when a document was read. The jam details display means displays the details of each jam that occurred in the same location. Furthermore, if it is determined that there is a location where jams have occurred more than a predetermined number of times, the jam occurrence history display means visualizes the location where jams have occurred more than a predetermined number of times. On the other hand, if it is determined that there is a location where a jam is currently occurring, the jam occurrence history display means visualizes the location where the jam is currently occurring. At least one of the jam occurrence history display means and the jam details display means displays at least one of the date and time when the jam occurred and paper information about the paper on which the jam occurred.

[0024] The jam occurrence history display means may display only the most recent history at the location where a jam has occurred or where a jam is currently occurring. When the jam occurrence history display means detects a designation of the location where a jam has occurred or where a jam is currently occurring and an instruction to display history other than the most recent history, the jam occurrence history display means may display each history of jams at the location related to the instruction.

[0025] The jam occurrence history display means may display only the most recent history of a location where a jam has occurred or a location where a jam is currently occurring. When the jam occurrence history display means detects an operation on a display area displaying information about a location where a jam has occurred more than a predetermined number of times or a location where a jam is currently occurring, the jam occurrence history display means may display each history of jams at the location related to the operation.

[0026] The jam occurrence history display means may display the jam history information indicating the jam history in the order of the date and time when the jam occurred.

[0027] The jam occurrence history display means may also display at a higher level jam history information indicating the jam history at a visualized location where a jam has occurred more than a predetermined number of times and at a location where a jam is currently occurring.

[0028] In addition, the jam occurrence history display means may display at least one of the locations where it is determined that a jam has occurred more than a predetermined number of times and the locations where it is determined that a jam is currently occurring by using an icon superimposed on the diagram of the image processing device 103.

[0029] In addition, the jam occurrence history display means does not need to display anything on the diagram of the image processing device if there are no locations where it has been determined that a jam has occurred more than a predetermined number of times or where it has been determined that a jam is currently occurring.

[0030] Furthermore, when there is no location where it is determined that jams have occurred more than the predetermined number of times, the jam occurrence history display means may display that there is no location where it is determined that jams have occurred more than the predetermined number of times, and may not display the location where jams have occurred more than the predetermined number of times.

[0031] Furthermore, when there is no location where it is determined that a jam is currently occurring, the jam occurrence history display means may display that there is no location where it is determined that a jam is currently occurring, and may not display the location where a jam is currently occurring.

[0032] The jam occurrence history display means and the jam details display means will be described in detail later.

[0033] <Screen configuration according to the first embodiment> Next, the status monitor screen, which displays the status and history of the image processing device 103 for service personnel, will be described with reference to Figs. 4 to 17. The status monitor screen is a screen displayed on the operation unit 212 of the image processing device 103, but is not intended for general users and is therefore a screen that can only be activated by a special operation. Furthermore, each screen shown in Figs. 4 to 17 is displayed based on data recorded in the history management unit 304.

[0034] Figures 4 and 5 are diagrams showing examples of the top screen of the status monitor. Figure 4 specifically shows an example of the top screen 400 when there is an abnormality in the image processing device 103. Figure 5 specifically shows an example of the top screen 400 when there is no abnormality in the image processing device 103.

[0035] 4, a cross-sectional view 401 of the image processing device 103 displays the location and type of abnormality of the image processing device 103 as an icon, mapping it on the cross-sectional view. The cross-sectional view 401 also shows the paper transport path, and can inform a service technician whether or not the abnormality has the potential to affect the use of the main functions of the image processing device 103, such as scanning and printing.

[0036] The legend 402 for the type of abnormality indicates the type and content of the icon that is mapped and displayed on the cross-sectional view 401. The types indicate locations where deteriorated parts need to be replaced, locations where trouble has occurred and inspection is required, locations where jams have occurred, locations where jams have occurred more than the specified number of times, etc.

[0037] Part life 403, Trouble detection 404, Error 405, and Jam 406 are areas that notify of abnormalities occurring in the image processing device 103, and are buttons that are pressed to transition to a detailed screen of the content of the notification. For Part life 403, Trouble detection 404, Error 405, and Jam 406, the content that can be displayed in each abnormality notification area is limited by the size of the area, so abnormalities are displayed in descending order of priority, and for abnormalities that cannot be displayed, only the number is displayed.

[0038] The priority of the part lifespan 403 is higher for parts that need to be replaced than for parts for which replacement is recommended. Furthermore, when parts have the same level of priority, the part lifespan 403 is displayed in the order of the part lifespan screen, which will be described later. The priority of the trouble detection 404 is higher for troubles that need to be checked than for troubles for which checking is recommended. Furthermore, when parts have the same level of priority, the trouble detection 404 is displayed in the order of the trouble detection screen, which will be described later. The error 405 displays only currently occurring errors in descending order of the date and time of occurrence. The priority of the jam 406 is higher for a location where a jam has currently occurred than for a location where a jam has occurred more than a predetermined number of times. Furthermore, when parts have the same level of priority, the jam 406 is displayed in descending order of the date and time of occurrence, similar to the jam screen, which will be described later.

[0039] As shown in Fig. 4, part life 403 indicates by icons displayed in legend 402 that drum unit Y needs to be replaced and that drum unit M and drum unit C are nearing the time for replacement and are recommended to be replaced. Also, as shown in Fig. 4, part life 403 indicates that there is one part that is nearing the end of its life. When part life 403 or a button at the top is pressed, the screen shown in Fig. 4 transitions to a part life screen, which will be described later.

[0040] As shown in Fig. 4, Trouble Detection 404 indicates that there are two troubles that need to be checked and one trouble that is recommended to be checked by icons displayed in legend 402. When Trouble Detection 404 or a button at the top is pressed, the screen shown in Fig. 4 transitions to the Trouble Detection screen, which will be described later.

[0041] As shown in Fig. 4, Error 405 indicates that there are two errors currently occurring. Note that Error 405 does not display the icon shown in Legend 402 because it is difficult to appropriately display many system-related errors at a specific position on a diagram such as a cross-sectional view of the image processing device 103. When Error 405 or a button at the top is pressed, the screen shown in Fig. 4 transitions to an error screen, which will be described later.

[0042] As shown in Fig. 4, Jam 406 indicates that there is one location where a jam is currently occurring and two locations where jams have occurred more than a predetermined number of times. When Jam 406 or a button on the top is pressed, the screen shown in Fig. 4 transitions to a Jam screen, which will be described later. Usage status 407 is a button that is pressed to transition the screen shown in Fig. 4 to a Usage status screen, which will be described later.

[0043] 5 does not display any icons shown in the legend 402 because there are no abnormalities in the image processing device 103. In other words, the part life 403, trouble detection 404, error 405, and jam 406 are all displayed as "No notification," allowing the service technician to recognize at a glance that no abnormalities have occurred.

[0044] 4 and 5 can inform the service technician whether or not an abnormality has occurred in the image processing device 103, the location where the abnormality has occurred, the location where the abnormality is currently occurring, and the details of the abnormality. Therefore, the top screen 400 shown in Fig. 4 and 5 can enable the service technician to quickly identify the location that needs to be addressed and start work immediately. Furthermore, the top screen 400 shown in Fig. 4 and 5 can enable the service technician to consider efficient work procedures, such as treating abnormalities in nearby locations together on the cross-sectional view 401.

[0045] FIG. 6 is a diagram showing an example of a parts lifespan screen. The parts lifespan screen 500 shown in FIG. 6 is displayed when the parts lifespan button 403 on the top screen 400 is pressed. The parts lifespan screen 500 displays a return to top screen button 501, a parts lifespan button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506 at the top. These six buttons are pressed to switch screens. These six buttons are also displayed on each detailed screen, which will be described later, allowing the service technician to easily switch between the detailed screens. Therefore, these six buttons allow the service technician to easily compare the information displayed on each detailed screen to infer the cause of an abnormality.

[0046] The part life screen 500 also displays a cross-sectional view 401 and a legend 402, but only displays icons for replacement parts. The parts list 507 displays a list showing the status of replacement parts. Each row of the parts list 507 displays the part name, status, and number of sheets used since replacement. The status is displayed in four levels according to the part's status value. These four levels are: Level 0, which indicates an indefinite status immediately after part replacement; Level 1, which indicates a status value of 0 to 79%; Level 2, which indicates a status value of 80 to 99%; and Level 3, which indicates a status value of 100% or more. These four levels are displayed using level meter icons. The status value is displayed numerically to the right of the level meter icon. The status value increases as the part deteriorates, and is preset so that the value at which the part requires replacement is 100%. Parameters used to calculate the status value include, for example, the number of sheets used after replacement, the current value of each part, and the resistance value of each part.

[0047] If the part status value is level 2, parts list 507 displays an icon indicating that the part is nearing the end of its life, indicating that replacement is recommended. In the example shown in Fig. 6, parts list 507 indicates that replacement of "Drum Unit M," "Drum Unit C," and "Cassette Roller 1" is recommended.

[0048] If the part status value is level 3, parts list 507 displays an icon indicating that the part needs to be replaced, indicating that the part has reached the end of its life. In the example shown in Figure 6, parts list 507 indicates that "drum unit Y" needs to be replaced.

[0049] When a part is replaced by a service technician and the replacement of the part is detected, the status value temporarily returns to level 0 (no data). Therefore, the parts list 507 does not display an icon indicating that a part needs to be replaced or an icon indicating that a part is recommended to be replaced in the cross-sectional view 401 or the parts list 507.

[0050] Unlike the notification area for part lifespan 403 on the top screen 400, parts list 507 displays all parts managed by the service technician, regardless of whether they are abnormal or not. Therefore, parts list 507 allows the service technician to check the status values ​​of parts that do not yet require replacement. Parts list 507 may display all parts, for example, by scrolling up and down. Status details button 508 is a button that is pressed to transition to status details screen 510, which displays a graph showing the progress of the status value of the part selected in parts list 507.

[0051] Fig. 7 is a diagram showing an example of a status details screen. Specifically, Fig. 7 shows a status details screen 510 that is displayed when the status details button 508 is pressed. As shown in Fig. 7, the status details screen 510 displays a status transition graph 511, a display period 512, and a close button 513.

[0052] The condition transition graph 511 shows the daily transition of the condition value of the selected part. The condition transition graph 511 also displays a reference line at 100%, the point at which the part needs to be replaced. The display period 512 is a pull-down menu that switches the graph display period between 30 days and 180 days. The close button 513 is a button that is pressed to close the condition details screen 510 and return to the part lifespan screen 500.

[0053] 7, status transition graph 511 shows the daily transition of the status value of "drum unit Y" on part life screen 500, and shows the daily transition when the status value exceeded 100%. As a result, status transition graph 511 allows the service technician to recognize whether the deterioration of the part is progressing as expected or whether the deterioration of the part is progressing rapidly due to environmental changes, part defects, etc.

[0054] 7 shows an example in which the status value exceeds 100% and the part has reached the end of its life. However, even if the status value is less than 100% and the part has not yet reached the end of its life, the status transition graph 511 allows the service technician to predict when the part will reach the end of its life based on the slope of the graph. Therefore, the status transition graph 511 allows the service technician to determine whether or not to bring a replacement part the next time maintenance is performed on the image processing device 103.

[0055] Fig. 8 is a diagram showing an example of a trouble detection screen. The trouble detection screen 600 shown in Fig. 8 is displayed when trouble detection 404 displayed on the top screen 400 is pressed or when trouble detection button 503 displayed on each detail screen is pressed. Like the part lifespan screen 500, the trouble detection screen 600 displays a return to top screen button 501, a part lifespan button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506 at the top. The trouble detection screen 600 also displays the cross section 401 and the legend 402, but only displays icons indicating that trouble checking is necessary and icons indicating that trouble checking is recommended.

[0056] The trouble list 601 displays a list of troubles that a service person is forced to deal with relatively frequently and the details of the troubles. "Dirt on the ADF optical unit" and "Dirt on the reader optical unit" shown in Fig. 8 indicate whether cleaning of the optical unit is necessary or whether cleaning of the optical unit is recommended.

[0057] The trouble list 601 displays whether or not action is required when the degree of dirt on the mirror is detected based on values ​​related to the reflected light from the mirror acquired by the optical sensor, etc. In other words, in this case, the trouble list 601 displays whether or not action is required using a four-level meter icon and a dirt level value, with the standard value that requires cleaning being 100%, in the same way as the status value of the part life.

[0058] The trouble list 601 displays a level 2 icon when the contamination level is 80-99%, and a level 3 icon when the contamination level is 100% or higher. Furthermore, when the contamination level is level 2, the trouble list 601 displays a check recommended icon on the left side of the list, indicating that cleaning is recommended, and when the contamination level is level 3, it displays a check required icon, indicating that cleaning is required. Furthermore, the trouble list 601 switches the messages displayed in each list depending on the contamination level. For example, the trouble list 601 displays the message "No Data" for level 0, "Good" for level 1, "Dirty" for level 2, and "Severely Dirty" for level 3.

[0059] The dirt details button 602 is pressed when a list relating to dirt on the optical unit is selected, and is used to check a graph showing the progress of the degree of dirt.

[0060] Trouble list 601 displays whether or not there is an abnormality in each cassette and the details of the abnormality. Cassette abnormalities are mainly detected when a misalignment of the paper guide plate (guide) inside the cassette is detected. If there is an abnormality in the cassette, trouble list 601 displays the message "Confirmation required" in the list, and if there is no abnormality in the cassette, displays the message "None" in the list.

[0061] The processed button 603 can be pressed when the optical unit or cassette needs to be checked or when a check is recommended. After the optical unit has been cleaned, if the processed button 603 is pressed with the optical unit selected, the contamination level returns to 0. In this case, the cross-sectional view 401 and the trouble list 601 do not display an icon indicating that a trouble check is required or an icon indicating that a trouble check is recommended. After the cassette has been checked, if the processed button 603 is pressed with the optical unit selected, the display returns to normal. In this case, the cross-sectional view 401 and the trouble list 601 do not display an icon indicating that a trouble check is required.

[0062] 9 is a diagram showing an example of a dirt details screen. The dirt details screen 610 is displayed when the dirt details button 602 is pressed. The dirt transition graph 611 shows the daily transition of the dirt level of the selected optical unit. The dirt transition graph 611 displays a reference line indicating 100%, which is the dirt level at which cleaning is required. The display period 612 is a pull-down menu for switching the display period of the dirt transition graph 611 between 30 days and 180 days. The close button 613 is a button that is pressed to close the dirt details screen 610 and return to the trouble detection screen 600.

[0063] 9, a dirt transition graph 611 for "reader optical unit dirt" is displayed on the trouble detection screen 600, showing the daily progress until the dirt level reaches 81%, which is the level at which checking is recommended. The dirt transition graph 611 allows a service technician to predict the timing when cleaning is necessary based on the slope of the graph. This also allows the service technician to determine whether or not to bring the tools necessary for cleaning the next time maintenance is performed on the image processing device 103.

[0064] 10 is a diagram showing an example of an error screen. The error screen 700 is displayed when the error 405 displayed on the top screen 400 is pressed or when the error button 504 displayed on each detail screen is pressed. The top screen 400 displays a return to top screen button 501, a parts life button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506. All six of these buttons are the same as the buttons displayed on the parts life screen 500 shown in FIG. 6.

[0065] The error list 701 displays a list of the error history that has occurred in the image processing device 103. The error history includes, for each error, the date and time of the error occurrence, the recovery time, the error code, and the title of the error. Furthermore, for errors that are still occurring, the error list 701 does not display the recovery time, as shown in the first and second lines of FIG. 10. The error details button 702 is pressed to check detailed information about the errors included in the error list 701. Furthermore, the error details button 702 is pressed when the error history is selected.

[0066] 11 is a diagram showing an example of an error details screen. The error details screen 710 displays an error code 711, error information 712, a page forward button 713, and a close button 714. The error code 711 is a code for identifying the selected error. The error information 712 includes the error title, description, and method of resolving the error. The page forward button 713 is a button for switching pages when the error information 712 spans multiple pages. The close button 714 is a button that is pressed to close the error details screen 710 and return to the error screen 700. The error details screen 710 allows a service technician to recognize the error that is occurring and the content of the error.

[0067] 12 is a diagram showing an example of a jam screen. The jam screen 800 is displayed when the jam 406 displayed on the top screen 400 or the jam button 505 displayed on each detail screen is pressed. The jam screen 800 displays a return to top screen button 501, a parts life button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506. All six of these buttons are the same as the buttons displayed on the parts life screen 500 shown in FIG. 6.

[0068] The jam screen 800 also displays a cross section 401 and a legend 402, but only displays icons for currently occurring jams and jams that have occurred more than a predetermined number of times. The jam screen 800 displays a jam list 801, a jam details button 802, a reset button 803, and a reset date and time 804.

[0069] The jam list 801 is a list of jam history. For each specific location set on the paper transport path, the jam list 801 includes the jam occurrence date, jam occurrence time, jam recovery time, jam code, jam type, sensor number, and the cumulative number of jams that have occurred at that location. In this embodiment, the specific locations correspond to each of the multiple sensors installed in the image processing apparatus for detecting jams. Furthermore, a different jam code is assigned to each jam that has occurred at that specific location. In other words, in this embodiment, the jam list 801 can be considered a list of information about jams for each specific location set on the paper transport path, a list of information about jams for each sensor, or a list of information about jams for each jam code. For jams that are currently occurring, the jam list 801 does not display the recovery time, but instead displays an icon indicating that a jam is occurring at the left end of the list, as shown in the first line of FIG. 12 . Furthermore, as shown in the second and fourth lines of FIG. 12, the jam list 801 determines that a jam that has occurred more than a predetermined number of times is a frequent jam, and displays a frequent jam icon on the left side of the list. In this embodiment, the icon displayed when a jam is currently occurring and the icon displayed when a frequent jam has occurred are the same mark, but are displayed in different colors, such as red and yellow. In the example shown in FIG. 12, a jam that has occurred 10 or more times is determined to be a frequent jam. Furthermore, if there are multiple records of the same jam code, the jam list 801 displays only the most recent record of the same jam code. This allows the jam list 801 to easily identify the type of jam that has occurred.

[0070] The jam details button 802 is a button that is pressed to check the details of the jam. The jam details button 802 is also pressed when the jam history is selected.

[0071] The reset button 803 is a button that is pressed to clear the jam history that is being displayed. The reset button 803 is pressed when checking for a currently occurring jam, a jam that has occurred more than a predetermined number of times, etc. is completed and the notification is to be deleted. When the reset button 803 is pressed, the date and time indicated by the reset date and time 804 is updated, and only the jam history from the reset date and time 804 onwards is displayed in the jam list 801.

[0072] 13 is a diagram showing an example of a jam details screen. A jam details screen 810 is displayed when the jam details button 802 is pressed. The jam details screen 810 displays a jam content 811, a sensor number 812, a jam details list 813, and a close button 814.

[0073] The jam details 811 include the jam code and type of jam selected on the jam list 801. The sensor number 812 is the sensor number associated with the jam code and the location where the jam occurred.

[0074] The jam details list 813 is a list that displays jam histories with the same jam content 811 in chronological descending order. The jam details list 813 includes the cumulative number, the date of occurrence, the time of occurrence, the time of recovery, the paper feed position when the jam occurred, the paper feed counter from the paper feed position when the jam occurred, and the size of the paper fed. While the jam list 801 displays the type of jam that occurred by displaying only the most recent jam history with the same jam code, the jam details list 813 makes it easier to see how often the same jam has occurred. Furthermore, if there are a large number of jams, the jam details list 813 may display details of all jams by scrolling up and down, for example.

[0075] The close button 814 is a button that is pressed to close the jam details screen 810 and return to the jam screen 800.

[0076] The jam details screen 810 displays not only the currently occurring jam, but also locations where jams have occurred in the past more than a predetermined number of times, the frequency of each jam, etc. This allows the jam details screen 810 to enable a service technician to consider cleaning or replacing parts around the location where a jam is currently occurring or where jams have occurred more than a predetermined number of times in the past.

[0077] 14 to 17 are diagrams showing examples of usage status screens. The usage status screen 900 is displayed when the usage status 407 displayed on the top screen 400 is pressed or when the usage status button 506 displayed on each detailed screen is pressed. The usage status screen 900 displays a temperature button 901, a humidity button 902, a number of prints button 903, and a cassette history button 904 on the right side, which can be pressed to transition to each usage status screen. These four buttons are also displayed on each usage status screen, allowing the service technician to easily move between each usage history screen.

[0078] The usage status screen 900 also displays a button 501 for returning to the top screen, a parts life button 502, a trouble detection button 503, an error button 504, a jam button 505, and a usage status button 506. This allows the service technician to easily move back and forth between the parts life screen 500, the trouble detection screen 600, and the usage status screen 900 using these six buttons. This also allows the service technician to easily guess the cause of a problem from the trouble information and usage status on the usage status screen 900.

[0079] FIG. 14 shows an example of a temperature change screen that is displayed when the temperature button 901 displayed on the usage status screen 900 is pressed. The temperature change graph 905 has a vertical axis representing temperature (°C) and a horizontal axis representing time, and shows the inside and outside temperatures for one day at 10-minute intervals. The date change button 906 is a button that is pressed to switch the displayed date, and can display data up to one month ago, for example. Furthermore, the temperature change graph 905 displays the reference value with a dotted line, allowing the service technician to determine that the environment needs to be reconsidered if a temperature outside the reference value is displayed. Furthermore, the service technician can compare the periods during which abnormalities occurred shown in FIGS. 6 to 13 with the temperature change screen shown in FIG. 14 to determine whether temperature changes are causing component degradation or jams.

[0080] FIG. 15 shows an example of a humidity change screen that is displayed when the humidity button 902 displayed on the usage status screen 900 is pressed. The humidity change graph 907 has a vertical axis representing temperature (°C) and a horizontal axis representing time, and shows the indoor humidity and outdoor humidity for one day at 10-minute intervals. The date switch button 908 is a button that is pressed to switch the displayed date, and can display data up to one month ago, for example. Furthermore, the humidity change graph 907 displays the reference value with a dotted line, allowing a service technician to determine that an environmental review is necessary if a humidity value outside the reference value is displayed. Furthermore, a service technician can compare the periods during which abnormalities occurred shown in FIGS. 6 to 13 with the humidity change screen shown in FIG. 15 to determine whether humidity changes are causing component deterioration or jams.

[0081] 16 shows an example of the print count screen that is displayed when the print count button 903 displayed on the usage status screen 900 is pressed. In the print count graph 909, the vertical axis represents the number of prints (sheets) and the horizontal axis represents time. The display period switch button 910 is a button that is pressed to change the display period to one month or one day. The date switch button 911 is a button that is pressed to change the date to be displayed.

[0082] When "Month" is selected with the display period switch button 910, the print count screen displays one month's worth of data at one-day intervals, and selecting the date switch button switches between displaying monthly data. When "Day" is selected with the display period switch button 910, the print count screen displays one day's worth of data at one-hour intervals, and selecting the date switch button switches between displaying daily data.

[0083] For example, Fig. 6 shows that the part's lifespan is coming to an end earlier than expected on the part's lifespan screen 500, and Fig. 16 shows that a large amount of printing was carried out just before the part's lifespan was about to expire on the print count graph 909. In this case, the service technician can infer that the part's lifespan is coming to an end earlier than expected due to the large amount of printing.

[0084] 17 shows an example of a cassette history screen that is displayed when the cassette history button 904 displayed on the usage status screen 900 is pressed. A cassette history list 912 displays the history of operations on cassettes in chronological order. A cassette switch button 913 is operated to select a cassette whose history is to be displayed.

[0085] For example, Fig. 6 shows that a cassette abnormality has been detected on the parts life screen 500, and the cassette history list 912 shown in Fig. 17 displays the operation history for the cassette. In this case, the service technician can infer that frequent operations on the cassette may be the cause of the misalignment of the cassette's paper guide.

[0086] <Configuration of History Data According to First Embodiment> Next, the data recorded in the history management unit 304, which manages the data displayed on the status monitor screen described above, will be described with reference to Figures 18 to 25. The history management unit 304 organizes values ​​and settings acquired from the various sensors 255, scanner 270, or printer 295 via the device I / F 220 shown in Figure 2 into necessary information and saves it in the HDD 204 or RAM 202.

[0087] FIG. 18 is a diagram showing an example of part life history data. Column 1001 is a column showing the number of the part in the order of arrangement. Column 1002 is a column showing the part name. Column 1003 is a column showing the status history data of each part. The status history data of each part is daily data related to the date the data was acquired, the part's status value, and the number of sheets of paper used after the part was replaced. The part's status value is a status level and a status value (%). Parts with a status level of 3 are displayed as parts requiring replacement in the cross-sectional view 401 and part life 403 shown in FIG. 4. Parts with a status level of 2 are displayed as parts recommended for replacement in the cross-sectional view 401 and part life 403 shown in FIG. 4. All of the parts and their statuses shown in FIG. 18 are displayed in the order of column 1001 in the parts list shown in FIG. 6.

[0088] The status history data is also used to display the status transition graph 511 shown in FIG. 7. The status history data is stored for at least 180 days, as there are display periods of 30 days and 180 days. When a service technician detects that a part has been replaced, the status level of the replaced part becomes level 0, which indicates an indefinite state after the part has been replaced. The status value (%) of the replaced part and the number of sheets of paper used become none. As described above, the part life history data shown in FIG. 18 is used to display the part life on each screen.

[0089] FIG. 19 is a diagram showing an example of trouble detection history data. Column 1101 is a column showing the trouble number in the order of sorting. Column 1102 is a column showing the name of the target. Column 1103 is a column showing the history data for each trouble. If the component is an optical unit, the history data for each trouble is daily data on the date the data was acquired and the degree of contamination. The degree of contamination is also the level of contamination and the degree of contamination (%).

[0090] An optical unit with a contamination level of 3 is displayed as a problem that requires checking in the cross-sectional view 401 and trouble detection 404 shown in Fig. 4. An optical unit with a contamination level of 2 is displayed as a problem that is recommended to be checked in the cross-sectional view 401 and trouble detection 404 shown in Fig. 4. The trouble history data for the optical unit is used to display the contamination level transition graph 611 shown in Fig. 9. Furthermore, since the display period for each trouble is either 30 days or 180 days, at least 180 days' worth of data is stored.

[0091] The cassette trouble history data is daily data regarding the date the data was acquired and whether or not an abnormality was detected. A cassette for which an abnormality has been detected is displayed as a trouble requiring check in the cross-sectional view 401 and the trouble detection 404 shown in FIG. 4. All of the troubles and their statuses shown in FIG. 19 are displayed in the order of column 1101 in the trouble list 601 shown in FIG. 8. Furthermore, when a service technician's press of the "Resolved" button 603 is detected, the contamination level and contamination degree are updated to the next value depending on the trouble for which "Resolved" has been performed. If the trouble for which "Resolved" has been performed is dirt in the optical unit, the contamination level becomes level 0, which is indefinite, and the contamination degree (%) data becomes null. If the trouble for which "Resolved" has been performed is a cassette, the "Anomaly Detection" is updated to "No." As described above, the trouble history data shown in FIG. 19 is used to display trouble detection on each screen.

[0092] FIG. 20 is a diagram showing an example of error history data. The history data shown in FIG. 20 is used to display error information. Column 1201 is a column showing an error code for identifying the error. Column 1202 is a column showing an error title corresponding to the error code. Column 1203 is a column showing the date the error occurred. Column 1204 is a column showing the time the error occurred. Column 1205 is a column showing the recovery time when the error was resolved. An error for which the recovery time is not recorded in column 1205 is displayed as an ongoing error in error 404 in FIG. 4. The history data shown in FIG. 20 is displayed in the error list 701 shown in FIG. 10 in the sorting order of column 1203 and in descending order of column 1204. Although not shown in FIG. 20, content corresponding to each error code is stored in HDD 204 and displayed on the error details screen shown in FIG. 11. As described above, the error history data shown in FIG. 20 is used to display errors on each screen.

[0093] FIG. 21 is a diagram showing an example of jam history data. The jam history data shown in FIG. 21 is used to display jam information. Column 1301 is a column showing a jam code for identifying a jam. Column 1302 is a column showing the type of jam corresponding to the jam code. Jams include various types such as delay (DELAY), retention (STNRY), and double feed (DOUBLE). A delay occurs when a sheet is not detected by a sensor even after a longer period of time than expected has passed. A retention occurs when a sheet continues to be detected by a sensor even after a longer period of time than expected has passed. A double feed occurs when a sensor in an ADF (Automatic Document Feeder) detects double feed of sheets.

[0094] Column 1303 is a column indicating the sensor number that detected the jam. Column 1304 is a column indicating the date the jam occurred. Column 1305 is a column indicating the time the jam occurred. Column 1306 is a column indicating the recovery time when the jam was cleared. Jams for which the recovery time is not recorded in column 1306 are displayed as ongoing jams in the cross-sectional view 401 and jam 405 shown in FIG. 4. Column 1307 is a column indicating the cumulative number of jams that have occurred with the same jam code. The number of jams that have occurred since the reset date and time 804 shown in FIG. 12 is counted up as the cumulative number. If the cumulative number of jams exceeds a predetermined number, for example, 9 times, it is determined to be a multiple jam, and this is displayed in the cross-sectional view 401 and jam 405 shown in FIG. 4.

[0095] Column 1308 is a column that indicates the paper feed position of the paper where the jam occurred. Column 1309 is a column that indicates the number of sheets of paper fed from the paper feed position. Column 1310 is a column that indicates the size of the paper fed. The jam history data shown in FIG. 21 is displayed on the jam screen 800 shown in FIG. 12 in descending order of occurrence date 1304 and occurrence time 1305. In this case, as described above, for jams with the same jam code, only the most recent jam is displayed. Furthermore, the jam history data for jams with the same jam code is displayed on the jam details screen 810 shown in FIG. 13. Note that when the reset button 803 is pressed, the jam history data before the date and time when the reset button 803 was pressed is deleted. As described above, the jam history data shown in FIG. 21 is used to display jams on each screen.

[0096] Fig. 22 is a diagram showing an example of usage history data. The usage history data shown in Fig. 22 is temperature data used to display the temperature change graph 905 displayed on the temperature change screen shown in Fig. 14.

[0097] Column 1401 is a column showing date data indicating the date on which the temperature data was acquired. Date data for one month is saved and displayed on the date switching button 906 shown in FIG. 14. Column 1402 is a column showing time data indicating the time at which the temperature data was acquired. Time data is saved at 10-minute intervals and displayed as the time on the horizontal axis of the temperature change graph 905 shown in FIG. 14.

[0098] Column 1403 is a column showing temperature data acquired by a thermometer installed inside the aircraft, not shown. This temperature data is data showing the temperature inside the aircraft, and is displayed as the inside-air temperature on the vertical axis of temperature change graph 905 shown in FIG. 14. Column 1404 is a column showing temperature data acquired by a thermometer installed outside the aircraft, not shown. This temperature data is data showing the temperature outside the aircraft, and is displayed as the outside-air temperature on the vertical axis of temperature change graph 905 shown in FIG. 14.

[0099] Fig. 23 is a diagram showing an example of usage history data. The usage history data shown in Fig. 23 is humidity data used to display the humidity change graph 907 displayed on the humidity change screen shown in Fig. 15.

[0100] Column 1411 is a column showing date data indicating the date on which the humidity data was acquired. Date data for one month is saved and displayed on the date switching button 908 shown in FIG. 15. Column 1412 is a column showing time data indicating the time at which the humidity data was acquired. Time data is saved at 10-minute intervals and displayed as the time on the horizontal axis of the temperature change graph 907 shown in FIG. 15.

[0101] Column 1413 is a column showing humidity data acquired by a hygrometer (not shown) installed inside the aircraft. This humidity data indicates the humidity inside the aircraft, and is displayed as the inside-aircraft humidity on the vertical axis of humidity change graph 907 shown in FIG. 15. Column 1414 is a column showing humidity data acquired by a hygrometer (not shown) installed outside the aircraft. This humidity data indicates the temperature outside the aircraft, and is displayed as the outside-aircraft humidity on the vertical axis of humidity change graph 907 shown in FIG. 15.

[0102] Fig. 24 is a diagram showing an example of usage history data. The usage history data shown in Fig. 24 is print count data used to display print count graph 909 displayed on the print count screen shown in Fig. 16.

[0103] Column 1421 is a column showing date data indicating the date when the print count data was acquired. Date data for one month is saved. The date data is used to display the date in the date switching button 908 when "day" is selected using the display period switching button 910 shown in FIG. 16. Furthermore, the date data is displayed as the date on the horizontal axis of the print count graph 909 when "month" is selected using the display period switching button 910 shown in FIG. 16.

[0104] Column 1422 is a column showing time data indicating the time when the print count data was acquired. The time data is saved at one-hour intervals, and is displayed as the time on the horizontal axis of the print count graph 909 when "day" is selected using the display period switch button 910 shown in FIG. 16. Column 1423 is a column showing print count data indicating the number of sheets printed by the image processing device 103. The print count data is displayed as the number of prints on the vertical axis of the print count graph 909 shown in FIG. 16.

[0105] Fig. 25 is a diagram showing an example of usage history data. The usage history data shown in Fig. 25 is cassette operation data used to display the cassette history list 912 displayed on the cassette history screen shown in Fig. 17. The cassette operation data is data that is saved when an operation to close a cassette in the image processing device 103 or an operation to change media is performed.

[0106] Column 1431 is a column showing date data indicating the date on which the cassette operation data was acquired. Up to 300 items of date data are saved. The date data is displayed in the cassette history list 912 shown in FIG. 17 in the order shown in column 1431. Column 1432 is a column showing time data indicating the time at which a cassette operation was performed. The time data is data indicating the time at which an operation on a cassette was performed, and is displayed as a time in the cassette history list 912 shown in FIG. 17.

[0107] Column 1433 is a column showing cassette operation data indicating which cassette an operation on the cassette has been performed on. Column 1433 displays "cassette closed" when an operation to close the target cassette has been performed. Column 1433 also displays "media change" when an operation to change the media on the target cassette has been performed. Furthermore, when an operation to change the media on the target cassette has been performed, the paper size and paper type are saved. The cassette operation data is displayed as a history of operations on the cassette in the cassette history list 912 shown in FIG. 17. Column 1433 may display not only cassette operation data but also manual feed operation data indicating that a manual feed operation has been performed.

[0108] <Characteristic Processing According to the First Embodiment> 26 to 28 are flowcharts showing an example of starting up the status monitor top screen. Firmware related to the processing of the flowcharts shown in Fig. 26 to 28 is stored in the HDD 204 of the image processing device 103, called up by the RAM 202, and executed by the CPU 201. This processing is started when a special command to start up the status monitor is input from the operation unit 212.

[0109] In step S1501, the CPU 201 refers to the device configuration information of the image processing device 103 stored in the RAM 202. Note that the device configuration information is not shown.

[0110] In step S1502, the CPU 201 determines the cross-sectional view to be displayed on each screen. The CPU 201 changes the cross-sectional view to be displayed depending on, for example, whether a scanner is installed, whether a paper feed option is installed, and whether a paper output option is installed. Furthermore, if the program is common to multiple devices, the CPU 201 may switch to a cross-sectional view that is compatible with each model according to device configuration information. This is because the paper transport path, the positions of each part, and the jam sensor differ depending on the model of the image processing device 103.

[0111] In step S1503, the CPU 201 refers to the part life history data stored in the HDD 204 and shown in FIG.

[0112] In step S1504, CPU 201 determines whether or not there are any parts with a status level of 2 or higher as a result of the reference made in step S1503. If CPU 201 determines that there are any parts with a status level of 2 or higher as a result of the reference made in step S1503 (step S1504: YES), it proceeds to step S1506. On the other hand, if CPU 201 determines that there are no parts with a status level of 2 or higher as a result of the reference made in step S1503 (step S1504: NO), it proceeds to step S1505.

[0113] In step S1505, the CPU 201 determines to display "No notification" in the notification area of ​​the part life 403 because there is no icon for the part life to be displayed in the cross-sectional view 401 shown in FIG.

[0114] In step S1506, the CPU 201 acquires information about parts whose status level is 3 and which need to be replaced from the part life history data in the HDD 204.

[0115] In step S1507, the CPU 201 acquires information about parts whose status level is 2 and for which replacement is recommended from the part life history data in the HDD 204.

[0116] In step S1508, CPU 201 determines the location where the icon relating to the part information acquired in step S1506 and the location where the icon relating to the part information acquired in step S1507 are to be displayed.

[0117] In step S1509, CPU 201 determines the abnormality to be displayed in the notification area. Then, in step S1509, CPU 201 displays the components for which information was obtained in step S1506 and the components for which information was obtained in step S1507 in descending order of priority. A component with a status level of 3 and requiring replacement has a higher priority than a component with a status level of 2 and for which replacement is recommended. Furthermore, if there are multiple components with the same status level, CPU 201 displays them in the order shown in FIG. 18.

[0118] Also, at this time, in step S1510, CPU 201 determines whether the number of parts to be notified is greater than the number of parts that can be displayed in the display area of ​​part lifespan 403. The number of parts that can be displayed in the display area of ​​part lifespan 403 is, for example, 3. If CPU 201 determines that the number of parts to be notified is equal to or less than the number of parts that can be displayed in the display area of ​​part lifespan 403 (step S1510: NO), CPU 201 proceeds to step S1512. On the other hand, if CPU 201 determines that the number of parts to be notified is greater than the number of parts that can be displayed in the display area of ​​part lifespan 403 (step S1510: YES), CPU 201 proceeds to step S1511.

[0119] In step S1511, the CPU 201 displays the notifications that cannot be displayed by the text "Other:" and the number of notifications.

[0120] In step S1512, the CPU 201 refers to the trouble detection history data stored in the HDD 204 and shown in FIG.

[0121] In step S1513, CPU 201 determines whether or not there is a problem with the optical unit that causes contamination level 2 or higher or an abnormality in the cassette as a result of the reference in step S1512. If CPU 201 determines that there is no problem with the optical unit that causes contamination level 2 or higher or an abnormality in the cassette as a result of the reference in step S1512 (step S1513: NO), the process proceeds to step S1514. On the other hand, if CPU 201 determines that there is a problem with the optical unit that causes contamination level 2 or higher or an abnormality in the cassette as a result of the reference in step S1512 (step S1513: YES), the process proceeds to step S1515.

[0122] In step S1514, the CPU 201 determines to display "No notification" in the notification area of ​​the trouble detection 404 because there is no trouble detection icon to display in the cross-sectional view 401 shown in FIG.

[0123] In step S1515, the CPU 201 acquires information about a problem that requires checking. For example, the CPU 201 acquires information about an optical unit with a contamination level of 3 and an abnormal cassette from the trouble detection history data of the HDD 204.

[0124] In step S1516, the CPU 201 acquires information about a problem that is recommended to be checked. For example, the CPU 201 acquires information about an optical unit whose status level is 2 from the trouble detection history data of the HDD 204.

[0125] In step S1517, CPU 201 determines the location where the icon relating to the trouble information acquired in step S1515 and the location where the icon relating to the trouble information acquired in step S1516 are to be displayed.

[0126] In step S1518, CPU 201 determines the abnormality to be displayed in the notification area. Then, in step S1518, CPU 201 displays the troubles for which information was obtained in step S1515 and the troubles for which information was obtained in step S1516 in descending order of priority. A trouble with a contamination level of 3 that requires checking has a higher priority than a trouble with a contamination level of 2 that is recommended to be checked. Furthermore, if there are multiple troubles with the same contamination level, CPU 201 displays them in the order shown in FIG. 19.

[0127] Also, at this time, in step S1519, CPU 201 determines whether the number of troubles to be notified is greater than the number of troubles that can be displayed in the display area of ​​trouble detection 404. The number of troubles that can be displayed in the display area of ​​trouble detection 404 is, for example, three. If CPU 201 determines that the number of troubles to be notified is equal to or less than the number of troubles that can be displayed in the display area of ​​trouble detection 404 (step S1519: NO), CPU 201 proceeds to step S1521. On the other hand, if the number of troubles to be notified is greater than the number of troubles that can be displayed in the display area of ​​trouble detection 404 (step S1519: YES), CPU 201 proceeds to step S1520.

[0128] In step S1520, CPU 201 displays the notifications that cannot be displayed with the text "Other:" and the number of notifications.

[0129] In step S1521, the CPU 201 refers to the error history data stored in the HDD 204 and shown in FIG.

[0130] In step S1522, CPU 201 determines, as a result of the reference in step S1521, whether or not there is a currently occurring error for which a recovery time is not registered in the error history data shown in Fig. 20. If CPU 201 determines that there is no currently occurring error for which a recovery time is not registered (step S1522: NO), it proceeds to step S1523. On the other hand, if CPU 201 determines that there is a currently occurring error for which a recovery time is not registered (step S1522: YES), it proceeds to step S1524.

[0131] In step S1523, CPU 201 determines to display "No notification" in the notification area for error 405.

[0132] In step S1524, the CPU 201 obtains information about a currently occurring error for which a recovery time is not registered in the error history data shown in FIG.

[0133] In step S1525, CPU 201 determines the abnormality to be displayed in the notification area, and then in step S1525, CPU 201 displays the necessary errors in the information acquired in step S1524 in descending order of acquisition.

[0134] Also, at this time, in step S1526, CPU 201 determines whether the number of errors to be notified is greater than the number of errors that can be displayed in the display area of ​​error 405. The number of errors that can be displayed in the display area of ​​error 405 is, for example, 2. If CPU 201 determines that the number of errors to be notified is equal to or less than the number of errors that can be displayed in the display area of ​​error 405 (step S1526: NO), CPU 201 proceeds to step S1528. On the other hand, if the number of errors to be notified is greater than the number of errors that can be displayed in the display area of ​​error 405 (step S1526: YES), CPU 201 proceeds to step S1527.

[0135] In step S1527, CPU 201 displays the notifications that cannot be displayed by the text "Other:" and the number of notifications.

[0136] In step S1528, the CPU 201 refers to the jam history data stored in the HDD 204 and shown in FIG.

[0137] In step S1529, the CPU 201 determines, as a result of the reference in step S1528, whether there is a currently occurring jam for which the jam clearance time shown in Fig. 21 is not registered or whether there are multiple jams with a cumulative number of 10 or more shown in Fig. 21. If the CPU 201 determines that there is no currently occurring jam for which the jam clearance time shown in Fig. 21 is not registered or whether there are multiple jams with a cumulative number of 10 or more shown in Fig. 21 (step S1529: NO), the CPU 201 proceeds to step S1530. On the other hand, if the CPU 201 determines that there is a currently occurring jam for which the jam clearance time shown in Fig. 21 is not registered or whether there are multiple jams with a cumulative number of 10 or more shown in Fig. 21 (step S1529: YES), the CPU 201 proceeds to step S1531.

[0138] In step S1530, CPU 201 determines to display "no notification" in the notification area for jam 406 because there is no jam icon to display in cross-sectional view 401 shown in FIG.

[0139] In step S1531, the CPU 201 obtains information about an occurring jam whose recovery time is not registered in the jam history data shown in FIG.

[0140] In step S1532, CPU 201 acquires information on frequent jams with a cumulative number of 10 or more recorded in the jam history data shown in Fig. 21 from the jam history data in HDD 204. Note that in step S1532, if multiple pieces of data with the same jam code are registered in the jam history data shown in Fig. 21, CPU 201 acquires information on the most recent jam.

[0141] In step S1533, CPU 201 determines the location where the abnormality is to be displayed on cross-sectional view 401 shown in Fig. 4. Then, in step S1533, CPU 201 displays icons at the coordinates of the locations for the jams about which information was acquired in step S1531 and the jams about which information was acquired in step S1532.

[0142] In step S1534, the CPU 201 determines the abnormality to be displayed in the notification area. Then, in step S1534, the CPU 201 displays the jams for which information was obtained in step S1531 and the jams for which information was obtained in step S1532 in descending order of priority. A currently occurring jam has a higher priority than a frequently occurring jam. Furthermore, if there are multiple jams with the same priority, the CPU 201 displays them in descending order of the order in which information was obtained. Furthermore, for a jam that corresponds to both a currently occurring jam and a frequently occurring jam, the CPU 201 displays the icon of the currently occurring jam preferentially.

[0143] At this time, in step S1535, CPU 201 determines whether the number of jams to be notified is greater than the number of jams that can be displayed in the display area of ​​jam 406. The number of jams that can be displayed in the display area of ​​jam 406 is, for example, 2. If CPU 201 determines that the number of jams to be notified is equal to or less than the number of jams that can be displayed in the display area of ​​jam 406 (step S1535: NO), CPU 201 proceeds to step S1537. On the other hand, if CPU 201 determines that the number of jams to be notified is greater than the number of jams that can be displayed in the display area of ​​jam 406 (step S1535: YES), CPU 201 proceeds to step S1536.

[0144] In step S1536, CPU 201 displays the notifications that cannot be displayed by the text "Other:" and the number of notifications.

[0145] In step S1537, CPU 201 displays the display content determined in steps S1501 to S1536 on the screen of operation unit 212. That is, in step S1537, CPU 201 displays top screen 400 of the status monitor shown in Fig. 4. By the processes shown in Fig. 26 to Fig. 28, CPU 201 can display, by means of a cross-sectional view 401 and a notification, any abnormality in image processing device 103 that an on-site service technician needs to check urgently and the location of the abnormality.

[0146] Therefore, the CPU 201 can notify the service technician of the entire abnormality of the image processing device 103 on a single screen of the top screen 400. This also enables the CPU 201 to improve the efficiency of the work of checking the abnormality by the service technician who is required to respond quickly on-site. Furthermore, this enables the CPU 201 to consider efficient work procedures, such as identifying areas where abnormalities are concentrated from the cross-sectional view 401 shown in FIG. 4 and working on the areas where abnormalities are concentrated all at once.

[0147] This also enables CPU 201 to enable a service technician to understand the relationship between the occurrence of each abnormality from the relative positions of the abnormality occurrence locations shown in cross-sectional view 401. For example, if a notification that cassette roller 1 needs to be replaced and a notification that frequent jams are occurring near cassette roller 1 are simultaneously received, CPU 201 can make the service technician aware of the following: In other words, in such a case, CPU 201 can make the technician aware that there is a high possibility that frequent jams will be resolved by replacing cassette roller 1.

[0148] Next, an example of a screen transition process in response to an operation to switch between the screens shown in Figures 4 to 17 will be described with reference to Figures 29 to 31. Figures 29 to 31 are flowcharts showing an example of a screen transition to the status monitor top screen and each detailed screen. The process shown in Figures 29 to 31 is started based on the reception of an input from the creation unit 212 while one of the screens shown in Figures 4 to 17 is displayed on the operation unit 212.

[0149] In step S1601, when CPU 201 detects that a button on the screen has been pressed, it determines which button has been pressed from among the buttons shown in Figures 4 to 17. First, a case will be described where the pressed button is part life 403 or part life button 502. In step S1601, when part life 403 or part life button 502 has been pressed, CPU 201 determines the determination result to be "part life" and proceeds to step S1602.

[0150] If the CPU 201 determines in step S1601 that the return to top screen button 501 has been pressed, the process proceeds to step S1633. If the CPU 201 determines in step S1601 that the error button 504 has been pressed, the process proceeds to step S1613. If the CPU 201 determines in step S1601 that the jam button 5054 has been pressed, the process proceeds to step S1618.

[0151] In step S1602, the CPU 201 acquires the part life history data stored in the HDD 204 and shown in FIG.

[0152] In step S1603, CPU 201 displays parts life screen 500 shown in Fig. 6 on operation unit 212 in accordance with the parts life history data acquired in step S1602. At this time, only the abnormal locations related to parts life determined in step S1508 of the flowcharts shown in Figs. 26 to 28 are displayed in cross-sectional view 401. In addition, parts list 507 displays the states of all parts listed in the parts life history data shown in Fig. 18.

[0153] In step S1604, the CPU 201 determines which button was pressed on the part lifespan screen 500. If the CPU 201 determines in step S1604 that the status details button 508 was pressed, the determination result is "status details," and the process proceeds to step S1605.

[0154] In step S1605, CPU 201 acquires graph data. Specifically, in step S1605, CPU 201 refers to history data 1003 of the state of the part selected in parts list 507 from the history data of part lifespans stored in HDD 204 and shown in FIG.

[0155] In step S1606, CPU 201 creates a graph of the status values ​​(%) according to the time series of dates of the status history data referenced in step S1605, and displays status details screen 510 shown in Fig. 7. At this time, CPU 201 displays data for the display period specified in display period 512 in status transition graph 511. Although not shown in Figs. 29 to 31, if close button 513 is pressed after status details screen 510 is displayed, the screen returns to part lifespan screen 500. Then, the screen returns to waiting for input in step S1601.

[0156] If it is determined in step S1604 that the detailed status button 508 has been pressed, the CPU 201 sets the determination result as "detailed status" and proceeds to step S1605.

[0157] If the CPU 201 determines in step S1604 that a button other than the status details button 508 has been pressed, it sets the determination result to "other" and proceeds to step S1601. Then, in step S1601, the CPU 201 determines which of the return to top screen button 501, part life button 502, trouble detection button 503, error button 504, jam button 505, and usage status button 506 has been pressed.

[0158] Next, a case where the CPU 201 determines in step S1601 that the trouble detection button 404 or the trouble detection button 503 has been pressed will be described.

[0159] In step S1601, if the CPU 201 determines that the trouble detection 404 or the trouble detection button 503 has been pressed, the determination result is "trouble detected" and the process proceeds to step S1607.

[0160] In step S1607, the CPU 201 acquires the trouble detection history data stored in the HDD 204 and shown in FIG.

[0161] In step S1608, the CPU 201 displays the trouble detection screen 600 shown in Fig. 8 on the operation unit 212 in accordance with the trouble detection history data acquired in step S1607. At this time, only the abnormality location related to the trouble detection determined in step S1517 is displayed in the cross-sectional view 401. In addition, the trouble list 601 displays the status of all the troubles listed in the trouble detection history data shown in Fig. 19.

[0162] In step S1609, if CPU 201 detects that a button on the screen has been pressed, it determines which button on the trouble detection screen 600 has been pressed. If CPU 201 determines that the pressed button is the dirt details button 602, it sets the determination result of step S1609 to "dirt details" and proceeds to step S1610.

[0163] In step S1610, CPU 201 acquires graph data. Specifically, in step S1610, CPU 201 refers to trouble history data 1103 of the optical unit selected in trouble list 601 from the trouble detection history data stored in HDD 204 and shown in FIG.

[0164] In step S1611, CPU 201 creates a graph of the degree of dirt (%) according to the time series of dates in the trouble history data referenced in step S1610, and displays dirt details screen 610 shown in Fig. 9. At this time, CPU 201 displays data for the display period specified in display period 612 in dirt transition graph 611. Although not shown in Figs. 29 to 31, if close button 613 is pressed after dirt details screen 610 is displayed, the screen returns to trouble detection screen 600. Then, the screen returns to waiting for input in step S1601.

[0165] In step S1609, the CPU 201 determines which button was pressed on the trouble detection screen 600. If the CPU 201 determines in step S1609 that the treated button 603 was pressed, it sets the determination result to "treated" and proceeds to step S1612.

[0166] In step S1612, the CPU 201 executes a process for indicating that the problem selected in the problem list 601 has been dealt with. For example, if the problem selected in the problem list 601 is the optical unit, the CPU 201 executes a process for resetting the contamination level in the problem history data shown in Fig. 19 to the initial value of 0. Furthermore, if the problem selected in the problem list 601 is the cassette, for example, the CPU 201 executes a process for resetting the abnormality detection in the problem history data shown in Fig. 19 to the initial value of none. Thereafter, the CPU 201 displays the problem detection screen 600 in Fig. 19, which reflects the latest problem detection history data.

[0167] In step S1609, if the pressed button is other than the stain details button 602 or the treated button 603, the CPU 201 determines the result of step S1609 as "other." Then, the CPU 201 proceeds to the determination of step S1601. In step S1601, the CPU 201 determines which button was pressed among the return to top screen button 501, part life button 502, trouble detection button 503, error button 504, jam button 505, and usage status button 506.

[0168] Next, a case where the CPU 201 determines in step S1601 that the error button 405 or the error button 504 has been pressed will be described.

[0169] In step S1601, if the CPU 201 determines that the error button 405 or the error button 504 has been pressed, the CPU 201 sets the determination result as "error" and proceeds to step S1613.

[0170] In step S1613, the CPU 201 acquires the error history data stored in the HDD 204 and shown in FIG.

[0171] In step S1614, CPU 201 displays error screen 700 shown in Fig. 10 on operation unit 212 in accordance with the error history data acquired in step S1613. At this time, error list 701 displays all errors listed in the error history data shown in Fig. 20.

[0172] In step S1615, CPU 201 determines which button was pressed on error screen 700. If CPU 201 determines in step S1615 that error details button 702 was pressed, it sets the determination result to "error details" and proceeds to step S1616.

[0173] In step S1616, CPU 201 acquires error detail data. Specifically, in step S1616, CPU 201 refers to detailed information (not shown) registered in HDD 204 for the error code selected in error list 701.

[0174] In step S1617, CPU 201 uses the error information referenced in step S1616 to display error details screen 710 shown in Fig. 11. Although not shown in Figs. 29 to 31, if close button 714 is pressed after error details screen 710 is displayed, the screen returns to error screen 700. Then, the screen returns to waiting for input in step S1601.

[0175] If the CPU 201 determines in step S1615 that a button other than the error details button 702 has been pressed, it sets the determination result to "other" and proceeds to step S1601. Then, in step S1601, the CPU 201 determines which of the return to top screen button 501, part life button 502, trouble detection button 503, error button 504, jam button 505, and usage status button 506 has been pressed.

[0176] Next, a case where the CPU 201 determines in step S1601 that the jam 406 or the jam button 505 has been pressed will be described.

[0177] In step S1601, if the CPU 201 determines that the jam button 406 or the jam button 505 has been pressed, the CPU 201 determines the result as "jam" and proceeds to step S1618.

[0178] In step S1618, the CPU 201 acquires the jam history data stored in the HDD 204 and shown in FIG.

[0179] In step S1619, the CPU 201 displays the jam screen 800 shown in FIG. 12 on the operation unit 212 in accordance with the jam history data acquired in step S1618. At this time, only the abnormal part related to the jam determined in step S1533 is displayed in the cross-sectional view 401. Furthermore, the jam list 801 displays only the most recent data for each jam code from the jam history data shown in FIG. 21. Note that in step S1619, if multiple pieces of data with the same jam code are registered in the jam history data shown in FIG. 21, the CPU 201 displays information about the most recent jam.

[0180] In step S1620, the CPU 201 determines which button was pressed on the jam screen 800. If the CPU 201 determines in step S1620 that the jam details button 802 was pressed, the determination result is "jam details" and the process proceeds to step S1621.

[0181] In step S1621, the CPU 201 acquires detailed jam data that is stored in the HDD 204 and matches the jam code of the jam selected in the trouble list 601 from the history data shown in FIG.

[0182] In step S1622, CPU 201 uses the jam detail data that matches the jam code acquired in step S1621 to display jam detail screen 810 shown in Fig. 13. Although not shown in Figs. 29 to 31, if close button 814 is pressed after jam detail screen 810 is displayed, the screen returns to jam screen 800. Then, the screen returns to waiting for input in step S1601.

[0183] If CPU 201 determines in step S1620 that reset button 803 has been pressed, it sets the determination result to "reset" and proceeds to step S1623.

[0184] In step S1623, CPU 201 deletes the jam history data shown in Fig. 21 and updates the date and time in reset date and time 804 to the date and time when reset was pressed. Thereafter, CPU 201 displays jam screen 800, which reflects the latest jam history data shown in Fig. 21.

[0185] If the CPU 201 determines in step S1620 that a button other than the jam details button 802 or the reset button 803 has been pressed, it sets the determination result to "other" and proceeds to step S1601. Then, in step S1601, the CPU 201 determines which of the return to top screen button 501, part life button 502, trouble detection button 503, error button 504, jam button 505, and usage status button 506 has been pressed.

[0186] Next, a case where the CPU 201 determines in step S1601 that the usage status 407 or the usage status button 506 has been pressed will be described.

[0187] In step S1601, if the CPU 201 determines that the usage status 407 or the usage status button 506 has been pressed, the CPU 201 sets the determination result as "usage status" and proceeds to step S1624.

[0188] In step S1624, CPU 201 determines which button was pressed on usage status screen 900. Since the initial value of usage status screen 900 is selection of temperature button 901, if transition has been made from a screen other than usage status screen 900, CPU 201 determines in step S1624 that the result is "temperature" and proceeds to step S1625.

[0189] In step S1625, the CPU 201 acquires the temperature data stored in the HDD 204 and shown in FIG.

[0190] In step S1626, the CPU 201 creates a temperature change graph of the on-board data and the off-board data based on the temperature data acquired in step S1625 in accordance with the time series of the date data and time data. The CPU 201 then displays the usage status screen 900 shown in Fig. 14 on the operation unit 212. Thereafter, the CPU 201 waits for input in step S1624.

[0191] If it is determined in step S1624 that the humidity button 902 has been pressed, the CPU 201 sets the determination result as "humidity" and proceeds to step S1627.

[0192] In step S1627, the CPU 201 acquires the humidity data stored in the HDD 204 and shown in FIG.

[0193] In step S1628, the CPU 201 creates a humidity change graph of the on-board data and a humidity change graph of the external data based on the humidity data acquired in step S1627 in accordance with the time series of the date data and time data. Then, the CPU 201 displays the humidity change screen shown in Fig. 15 on the operation unit 212. Thereafter, the CPU 201 waits for input in step S1624.

[0194] If it is determined in step S1624 that the print count button 903 has been pressed, the CPU 201 sets the determination result as "print count" and proceeds to step S1629.

[0195] In step S1629, the CPU 201 acquires the print count data stored in the HDD 204 and shown in FIG.

[0196] In step S1630, the CPU 201 creates a graph of the number of printed sheets data based on the number of printed sheets data acquired in step S1629 in accordance with the time series of date data and time data. Note that if "Day" is selected using the display period switching button 910 shown in FIG. 16, the CPU 201 creates a graph of the number of printed sheets data for each hour for one day. When "Month" is selected using the display period switching button 910 shown in Fig. 16, the CPU 201 creates a graph of the print count data for each day for one month. Then, the CPU 201 displays the print count screen shown in Fig. 16 on the operation unit 212. Thereafter, the CPU 201 waits for input in step S1624.

[0197] If it is determined in step S1624 that the cassette history button 904 has been pressed, the CPU 201 sets the determination result as "cassette history" and proceeds to step S1631.

[0198] In step S1631, the CPU 201 acquires the cassette operation data stored in the HDD 204 and shown in FIG.

[0199] In step S1632, the CPU 201 creates a cassette history list of the cassette operation data acquired in step S1631 in accordance with the chronological order of the date data and time data. The CPU 201 creates the cassette history list 912 by extracting only the data of the cassette selected with the cassette switching button 913 shown in FIG. 17. For example, in the example shown in FIG. 17, "cassette 1" is selected with the cassette switching button 913. Therefore, the CPU 201 creates the cassette history list 912 by extracting the data Nos. 1, 2, 6, 7, 8, 9, 10, and 11 indicating "cassette 1" from the column 1433 shown in FIG. 25. The CPU 201 then displays the cassette history screen shown in FIG. 17 on the operation unit 212. The CPU 201 then waits for input in step S1624.

[0200] If the CPU 201 determines in step S1624 that a button other than the temperature button 901, humidity button 902, number of prints button 903, or cassette history button 904 has been pressed, the determination result is "other" and the process proceeds to step S1601. Then, in step S1601, the CPU 201 determines which of the return to top screen button 501, part life button 502, trouble detection button 503, error button 504, jam button 505, or usage status button 506 has been pressed.

[0201] Since the "Return to Top" button 501 is displayed on each screen shown in Figures 6 to 17, if CPU 201 determines that the "Return to Top" button 501 has been pressed, it determines the result as "Return to Top" and proceeds to step S1633.

[0202] In step S1633, the CPU 201 executes the process for displaying the top screen shown in FIGS. 26 to 28, and displays the top screen 400.

[0203] Next, a case where an operation (not shown) to terminate the status monitor is input on each of the screens shown in FIGS. 4 to 17 will be described.

[0204] In step S1601, if the CPU 201 detects an operation to end the status monitor, the CPU 201 determines that the operation is “end.” Then, in step S1634, the CPU 201 executes processing to end the display of the status monitor.

[0205] As described above, the flowcharts shown in Figures 29 to 31 show that a service technician can transition from the top screen 400 shown in Figure 4 to each screen in order to check detailed information. The screens referred to here are the parts life screen 500, trouble detection screen 600, error screen 700, jam screen 800, and usage status screen 900 shown in Figures 6 to 17. This allows a service technician to immediately display each detailed screen from the top screen 400 and gather the information necessary for treatment.

[0206] As described above, each detailed screen can be switched using the parts life button 502, trouble detection button 503, error button 504, jam button 505, and usage status button 506. This allows a service technician to infer the cause of an abnormality from the information related to each detailed screen and consider countermeasures based on that inference. This also allows a service technician to infer when an abnormality will occur in a location where no abnormality is currently occurring and to make preparations based on that inference. Note that this timing is inferred mainly from the life of the parts and the degree of dirt on the optical unit.

[0207] Next, a process for saving a jam occurrence history will be described with reference to Fig. 21 and Fig. 32. Fig. 32 is a flowchart for explaining the process for saving a jam occurrence history. Each step shown in Fig. 32 is executed by the CPU 201 of the image processing device 103 executing a program.

[0208] In step S1701, the CPU 201 executes a job. In the first embodiment, it is assumed that a scan job is executed in step S1701, but other jobs such as a copy job may also be executed.

[0209] In step S1702, CPU 201 determines whether a jam has occurred based on various sensors 255. If CPU 201 determines that a jam has occurred (step S1702: YES), the process proceeds to step S1703. On the other hand, if CPU 201 determines that a jam has not occurred (step S1702: NO), the process ends.

[0210] In step S1703, the CPU 201 stores information about the occurrence of a jam as history using the history management unit 304. In the first embodiment, the date and time the jam occurred, the position of the sensor that detected the jam, and counter information indicating the total number of sheets of paper that were read are stored, but this information is not limited to this information as long as it is information necessary for dealing with the jam. For example, instead of information indicating the position of the sensor that detected the jam, information indicating the position where the jam occurred may be stored.

[0211] In step S1704, CPU 201 determines whether the jam has been cleared. If CPU 201 determines that the jam has been cleared (step S1705: YES), it proceeds to step S1705. On the other hand, if CPU 201 determines that the jam has not been cleared (step S1704: NO), it ends the process.

[0212] In step S1705, the CPU 201 adds the recovery time to the jam occurrence history using the history management unit 304. The recovery time added here is, for example, the recovery time shown in the column 1306 in FIG.

[0213] Next, a process for displaying the jam screen 800 will be described with reference to Fig. 12, Fig. 13, and Fig. 33. Fig. 33 is a flowchart for explaining a process for displaying the jam screen 800 and the jam details screen 810.

[0214] In step S1801, CPU 201 detects whether a button for displaying a jam occurrence history has been pressed using operation unit 212. In the first embodiment, it is assumed that CPU 201 detects whether jam 406 shown in Fig. 4 or 5 or jam button 505 shown in Fig. 6 has been pressed. Also, in step S1901, it is assumed that the button has been pressed by a service technician, but the button may also be pressed by a user.

[0215] In step S1802, the CPU 201 determines, via the control unit 301, whether the location where the jam is currently occurring or the location where jams frequently occur is in the jam occurrence history stored in the history management unit 304. In the first embodiment, a location where jams have occurred three or more times is considered to be a location where jams frequently occur, but a location where jams have occurred a number of times or more specified by the user may also be considered to be a location where jams frequently occur. Furthermore, the location where the jam is currently occurring refers to one for which the above-mentioned recovery time is not stored. Furthermore, for a jam occurrence history for which the recovery time is stored by the processing of step SS1705, the jam is considered to have been cleared.

[0216] If the CPU 201 determines that the location where the jam is currently occurring or the location where jams frequently occur is in the jam occurrence history stored in the history management unit 304 (step S1802: YES), the process proceeds to step S1803. On the other hand, if the CPU 201 determines that the location where the jam is currently occurring or the location where jams frequently occur is not in the jam occurrence history stored in the history management unit 304 (step S1802: NO), the process proceeds to step S1804.

[0217] In step S1803, the CPU 201 maps an icon indicating the location where a jam is currently occurring or where jams frequently occur onto the cross-sectional view 401 of the image processing device 103.

[0218] In step S1804, the CPU 201 acquires the jam occurrence history stored in the history management unit 304 using the control unit 301, and sorts it in order of the date and time when the jam occurred.

[0219] In step S1805, CPU 201 displays cross-sectional view 401 created by display unit 302 in step S1803 and jam screen 800 including the jam occurrence history created in step S1804. In the first embodiment, if there is no location where a jam currently occurs or where jams frequently occur (step S1802: NO), it is assumed that cross-sectional view 401 with no icon mapped will be displayed. However, if there is no icon to be mapped, CPU 201 may hide cross-sectional view 401 and display a message indicating that there are no locations where a jam currently occurs or where jams frequently occur.

[0220] As described above, Fig. 12 is a diagram showing an example of the jam screen. Fig. 12 shows a cross-sectional view 401 in which locations where jams are currently occurring or locations where jams frequently occur are mapped, and a jam list 801 that shows jam history information. Here, when the reset button 803 is pressed, the CPU 201 clears the icons mapped on the cross-sectional view 401 shown in Fig. 12 and the jam list 801. Note that the CPU 201 clears only the displayed jam list 801, and does not delete the history saved in step S1703.

[0221] In step S1806, the CPU 201 determines, via the control unit 301, whether or not it has been detected that a button for displaying a details screen of the jam occurrence history has been pressed. Here, whether or not it has been detected that a button has been pressed is assumed to be whether or not any button in the jam list 801 shown in Fig. 12 has been pressed and then the jam details button 802 has been pressed, but it may also be whether or not any button in the jam list 801 has been pressed.

[0222] If CPU 201 determines that the button for displaying the details screen of the jam occurrence history has not been pressed (step S1806: NO), it ends the process. On the other hand, if CPU 201 determines that the button for displaying the details screen of the jam occurrence history has been pressed (step S1806: YES), it proceeds to step S1807.

[0223] In step S1807, the CPU 201 causes the control unit 301 to acquire from the history management unit 304 the history of jams that have occurred at the location selected by the user, and sorts the history in order of the date and time of occurrence.

[0224] In step S1808, the CPU 201 displays the history of each jam that occurred at the selected location on the display unit 302 as a jam details screen 810.

[0225] As described above, Fig. 13 is a diagram showing an example of the jam details screen, and shows the screen when a service technician selects the second jam history from the top in the jam list 801 shown in Fig. 12. Fig. 13 shows the accumulated number of jams is 25, so the individual histories for the 25 jams are displayed. In the first embodiment, the paper feed position, paper feed counter, paper feed size, etc. are displayed as paper information on the details screen, but this is not limited to this as long as the paper information is necessary for dealing with the jam.

[0226] In the first embodiment, the jam screen 800 shown in Fig. 12 is transitioned to display the jam details screen 810 shown in Fig. 13 as a separate screen, but the screen configuration is not limited to this. For example, the CPU 201 may display the jam occurrence history and the jam details on the same screen, or may display the jam details screen 810 as a pop-up screen when the display area for the jam occurrence history is operated.

[0227] By executing the above processing, the CPU 201 visualizes the location where the jam is currently occurring and the location where jams frequently occur as a jam occurrence history using the cross section 401, and displays the location together with the date and time when the jam occurred and the details of the detected jam. Also, the jam details screen 810 displays the individual history of jams that have occurred in the same location.

[0228] This allows the service technician to get an overview of the cross-sectional view 401 that maps the location of the current jam or the location where jams frequently occur, as well as the date and time of the jam and the details of the detected jam. This also allows the service technician to recognize the time interval between jams that occurred in the same location, paper information, etc. This allows the service technician to easily identify the cause of the jam and quickly deal with the jam.

[0229] It is also possible to use a method in which a location where no jam has occurred is displayed as "0", or to display the same mark as a location where a jam has currently occurred or a location where jams have occurred frequently, but in a different color (for example, green). However, in contrast to such a configuration, in the first embodiment, only locations where jams have occurred are mapped. Therefore, locations that require attention are clearly displayed.

[0230] In addition, in this embodiment, it is possible to display details of the jam occurrence history on both the transport path that transports the document read by the document reading means and the transport path that transports the paper to be printed, but it is also possible to configure it so that it is displayed on only one of these transport paths.

[0231] [Second embodiment] In the first embodiment, the jam occurrence history is displayed in the order of the date and time when the jam occurred and the details of the detected jam along with the cross-sectional view 401 on which the location where the jam currently occurs and the location where jams frequently occur are mapped. This allows the service technician to get an overview of the location where the jam occurred and the details of the jam history. However, in the present invention, the history of the location mapped on the cross-sectional view 401 may be displayed at a higher level depending on the date and time when the jam occurred and the details of the detected jam.

[0232] In the second embodiment, a method will be described as an example in which the history of a location that requires a jam response can be immediately checked by displaying the history of the location mapped to the cross-sectional view 401 at a higher level on the jam screen 800 as shown in Fig. 12. Note that the second embodiment differs from the first embodiment in that the process for displaying the jam screen 800 is executed according to the flowchart shown in Fig. 33, in that the process is executed according to the flowchart shown in Fig. 34.

[0233] The process of displaying the jam screen 800 in the second embodiment will be described below with reference to Fig. 34 and Fig. 35. Fig. 34 is a flowchart for explaining the process of displaying the jam screen in the second embodiment.

[0234] In step S1901, the CPU 201 detects whether or not a button for displaying the jam occurrence history has been pressed using the operation unit 212. Also, in the second embodiment, similar to the first embodiment, it is assumed that there will be a situation in which it is detected whether or not the jam 406 shown in Fig. 4 or Fig. 5 or the jam button 505 shown in Fig. 6 has been pressed.

[0235] In step S1902, the CPU 201 determines, via the control unit 301, whether or not the jam occurrence history stored in the history management unit 304 includes a location where a jam is currently occurring or a location where jams frequently occur. If the CPU 201 determines that the jam occurrence history stored in the history management unit 304 includes a location where a jam is currently occurring or a location where jams frequently occur (step S1902: YES), the CPU 201 proceeds to step S1903. On the other hand, if the CPU 201 determines that the jam occurrence history stored in the history management unit 304 does not include a location where a jam is currently occurring or a location where jams frequently occur (step S1902: NO), the CPU 201 proceeds to step S1904.

[0236] In step S1903, the CPU 201 maps the location where a jam is currently occurring or the location where jams frequently occur onto the cross-sectional view 401 of the image processing device 103.

[0237] In step S1904, the CPU 201 acquires the jam occurrence history stored in the history management unit 304 by the control unit 301, and sorts the history by the control unit 301 so that the history of the location mapped to the cross-sectional view 401 is displayed at the top.

[0238] In step S1905, the CPU 201 displays the jam screen 800 including the cross-sectional view 401 created in step S1903 and the jam occurrence history created in step S1904.

[0239] 35 is a diagram showing how the history of a location mapped to a cross-sectional view of an image processing device on a jam screen is displayed at a higher level in the second embodiment. The jam screen 800 shown in FIG. 35 displays a jam list 2001 in which the history of a location mapped to a cross-sectional view 401 is displayed at a higher level.

[0240] In step S1906, CPU 201 determines whether it has detected that the button for displaying the jam occurrence history details screen has been pressed using operation unit 212. If CPU 201 determines that it has not detected that the button for displaying the jam occurrence history details screen has been pressed using operation unit 212 (step S1906: NO), CPU 201 ends the process. On the other hand, if CPU 201 determines that it has detected that the button for displaying the jam occurrence history details screen has been pressed using operation unit 212 (step S1906: YES), CPU 201 proceeds to step S1907.

[0241] In step S1907, the CPU 201 causes the control unit 301 to acquire the history of jams that have occurred at the selected location from the history management unit 304, and the control unit 301 rearranges the history so that the history of the location mapped to the cross-sectional view 401 is at the top.

[0242] In step S1908, the CPU 201 displays the history of each jam that occurred at the selected location as a jam details screen.

[0243] In the second embodiment, instead of the display process of the jam occurrence history according to the first embodiment, a process of displaying the history of the portion mapped to the cross-sectional view 401 on the jam screen 800 at a higher level is executed.

[0244] In the first embodiment, by sorting and displaying the jams in order of the date and time when they occurred, the service person can check the jams that have occurred recently, and the service person can take prompt action to prevent the jams from occurring. On the other hand, in the second embodiment, as shown in Fig. 35, by displaying the history of the locations mapped in the cross-sectional view 401 at the top, the service person can check the history of the locations that require attention to the jams, and can take prompt action to the locations.

[0245] [Third embodiment] In the first embodiment, the jam occurrence history is displayed by displaying all uncleared jam histories in chronological order of occurrence date and time, along with a cross-sectional view of the image processing device 103 on which the location where the jam currently occurs and the locations where jams frequently occur are mapped. This allows the service technician to get an overview of the locations where jams have occurred and the contents of the jam history. However, in the present invention, the history information of only one location selected from the locations mapped on the cross-sectional view 401 may be displayed.

[0246] In the third embodiment, a method will be described as an example in which a service technician selects any of the icons mapped to the cross-sectional view 401 on the jam screen 800 shown in Fig. 37, and the history of the selected location is displayed instead of the jam details screen. Note that, unlike the first embodiment in which the display unit 302 executes the display process for the jam screen 800 according to the flowchart shown in Fig. 33, the third embodiment executes this process according to the flowchart shown in Fig. 36.

[0247] The process of displaying the jam screen 800 in the third embodiment will be described below with reference to Fig. 36 and Fig. 37. Fig. 36 is a flowchart for explaining the process of displaying the jam screen in the third embodiment.

[0248] In step S2101, the CPU 201 detects whether or not a button for displaying the jam occurrence history has been pressed using the operation unit 212. Also, in the third embodiment, similar to the first embodiment, it is assumed that there will be a situation in which it is detected whether or not the jam 406 shown in Fig. 4 or Fig. 5 or the jam button 505 shown in Fig. 6 has been pressed.

[0249] In step S2102, the CPU 201 determines, via the control unit 301, whether or not the jam occurrence history stored in the history management unit 304 includes a location where a jam is currently occurring or a location where jams frequently occur. If the CPU 201 determines that the jam occurrence history stored in the history management unit 304 includes a location where a jam is currently occurring or a location where jams frequently occur (step S2102: YES), the CPU 201 proceeds to step S2103. On the other hand, if the CPU 201 determines that the jam occurrence history stored in the history management unit 304 does not include a location where a jam is currently occurring or a location where jams frequently occur (step S2102: NO), the CPU 201 proceeds to step S2104.

[0250] In step S2103, the CPU 201 maps the location where a jam is currently occurring or the location where jams frequently occur onto the cross-sectional view 401 of the image processing device 103.

[0251] In step S2104, the CPU 201 acquires the jam occurrence history stored in the history management unit 304 by the control unit 301, and sorts the history by the control unit 301 so that the history of the location mapped to the cross-sectional view 401 is displayed at the top.

[0252] In step S2105, the CPU 201 displays the jam screen 800 including the cross-sectional view 401 created in step S2104 and the jam occurrence history created in step S2104.

[0253] In step S2106, the CPU 201 determines whether it has detected that a button corresponding to any of the icons mapped to the cross-sectional view 401 has been pressed. If the CPU 201 determines that it has not detected that a button corresponding to any of the icons mapped to the cross-sectional view 401 has been pressed (step S2106: NO), the CPU 201 ends the process. On the other hand, if the CPU 201 determines that it has detected that a button corresponding to any of the icons mapped to the cross-sectional view 401 has been pressed (step S2106: YES), the process proceeds to step S2107.

[0254] In step S2107, the CPU 201 causes the control unit 301 to acquire the history of jams that have occurred at the selected location from the history management unit 304, and the control unit 301 rearranges the history in the order of the date and time when the jams occurred.

[0255] In step S2108, the CPU 201 displays the history of each jam that occurred at the selected location as a jam details screen.

[0256] In the third embodiment, it is assumed that the jam screen 800 shown in FIG. 12 is displayed in step S2105, and the jam screen 800 shown in FIG. 37 is displayed in step S2108. FIG. 37 is a diagram showing how, in the third embodiment, a service technician selects one of the icons mapped to the cross-sectional view of the image processing device in the jam screen to display a history of jams that have occurred at the selected location. Also, in the third embodiment, all of the icons mapped to the jam screen 800 shown in FIG. 37 in step S2108 are displayed, and the selected icon is highlighted. However, in the third embodiment, for example, only the icon selected upon transition to step S2108 may be displayed.

[0257] In step S2109, CPU 201 detects pressing of the back button via control unit 301. Note that in step S2109, CPU 201 may detect pressing of the icon pressed in step S2106 again via control unit 301, rather than pressing of the back button. Also, in step S2109, if CPU 201 detects pressing of an icon different from the icon pressed in step S2106, it may display the history of jams that occurred at the reselected location.

[0258] In step S2110, the CPU 201 returns to the display before the icon for the cross-sectional view 401 was pressed. That is, in step S2110, the CPU 201 displays again the screen that was displayed in step S2105.

[0259] In the third embodiment, instead of the process of displaying the jam occurrence history in the first embodiment, a process of displaying the history information of only one location selected by the service technician from among the locations mapped on the cross-sectional view 400 on the jam screen 800 is executed.

[0260] In the first embodiment, when a service technician presses the history and jam details button 802 on the jam screen 800 shown in Fig. 12, the jam details screen 810 shown in Fig. 13 is displayed. On the other hand, in the third embodiment, the history of jams that have occurred in the same location is displayed by the service technician's operation without changing the screen, as shown in Fig. 36, so the number of operation steps is fewer than in the first embodiment, and a more intuitive display is possible.

[0261] The present invention includes the following inventions that appropriately combine the above-mentioned features.

[0262] (Configuration 1) 1. An image processing device comprising: a jam occurrence history display means for displaying a screen showing the history of jams at at least one location within the image processing device; and a jam detail display means for displaying details of the history of individual jams that have occurred at the same location based on a user operation on the jam history screen, wherein at least one of the jam occurrence history display means and the jam detail display means displays at least one of the date and time when the jam occurred and paper information about the paper on which the jam occurred.

[0263] (Configuration 2) The image processing device according to configuration 1 further comprises a jammed location determination means for determining whether or not there is a location where a jam is currently occurring, and a frequent jam location determination means for determining whether or not there is a location where a jam has occurred more than a predetermined number of times, wherein the jam occurrence history display means, if it is determined that there is a location where a jam has occurred more than the predetermined number of times, visualizes the location where a jam has occurred more than the predetermined number of times, and, if it is determined that there is a location where a jam is currently occurring, visualizes the location where a jam is currently occurring.

[0264] (Configuration 3) The image processing device according to configuration 1 or 2, wherein the jam occurrence history display means displays only the most recent history at the location where the jam occurred or the location where the jam currently occurs, and when detecting a designation of the location where the jam occurred or the location where the jam currently occurs and an instruction to display history other than the most recent history, displays each history of jams at the location related to the instruction.

[0265] (Configuration 4) The image processing device according to any one of configurations 1 to 3, wherein the jam occurrence history display means displays only the most recent history of a location where a jam has occurred or a location where a jam is currently occurring, and when an operation on a display area displaying information about a location where a jam has occurred more than a predetermined number of times or a location where a jam is currently occurring is detected, displays each history of jams in the location related to the operation.

[0266] (Configuration 5) 5. The image processing apparatus according to any one of configurations 1 to 4, wherein the jam occurrence history display means displays jam history information indicating a history of jams in order of the date and time when the jams occurred.

[0267] (Configuration 6) The image processing device according to any one of configurations 1 to 5, wherein the jam occurrence history display means displays at a higher level jam history information indicating a history of jams at a visualized location among a location where a jam has occurred more than a predetermined number of times and a location where a jam is currently occurring.

[0268] (Configuration 7) The image processing device according to any one of configurations 1 to 6, wherein the jam occurrence history display means displays at least one of a location where it is determined that a jam has occurred more than a predetermined number of times and a location where it is determined that a jam is currently occurring by using an icon superimposed on a diagram of the image processing device.

[0269] (Configuration 8) The image processing device according to any one of configurations 1 to 7, wherein the jam occurrence history display means does not display anything on the diagram of the image processing device if there is no location where it is determined that a jam has occurred more than a predetermined number of times and no location where it is determined that a jam is currently occurring.

[0270] (Configuration 9) The image processing device according to any one of configurations 1 to 8, wherein, when there is no location where it is determined that a jam has occurred more than a predetermined number of times, the jam occurrence history display means displays that there is no location where it is determined that a jam has occurred more than the predetermined number of times, and does not display any location where a jam has occurred more than the predetermined number of times.

[0271] (Configuration 10) The image processing device according to any one of configurations 1 to 9, wherein, when there is no location determined to be currently jammed, the jam occurrence history display means displays that there is no location determined to be currently jammed, and does not display the location where the jam is currently occurring.

[0272] (Method 1) A method for controlling an image processing device, comprising: displaying a screen showing the history of jams at at least one location within the image processing device using a jam occurrence history display means; displaying details of the history of individual jams that have occurred at the same location using a jam detail display means based on a user operation on the jam history screen; and at least one of the jam occurrence history display means and the jam detail display means displaying at least one of the date and time when the jam occurred and paper information related to the paper on which the jam occurred.

[0273] (Program 1) A computer program that displays a screen showing the history of jams at at least one location in an image processing device using a jam occurrence history display means, and displays details of the history of individual jams that have occurred at the same location using a jam detail display means based on a user operation on the jam history screen, wherein at least one of the jam occurrence history display means and the jam detail display means displays at least one of the date and time when the jam occurred and paper information about the paper on which the jam occurred.

[0274] <Other embodiments> Some of the elements constituting the present invention can also be realized by supplying a program that realizes one or more of the functions of the above-described embodiments to a system or device via a network or a recording medium, and having one or more processors in the computer of the system or device read and execute the program. Also, some of the elements constituting the present invention can be realized by a circuit that realizes one or more functions, such as an ASIC (Application Specific Integrated Circuit).

[0275] The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments. In other words, the present invention includes embodiments in which various modifications have been made based on the spirit of the present invention, and these embodiments are not excluded from the scope of the present invention. [Explanation of symbols]

[0276] 1. Image processing device 201 CPU 204 HDD 255 Various Sensors 302 Display section 303 Input section 304 History Management Department

Claims

1. a jam occurrence history display means for displaying a screen of a jam history at at least one location in the image processing apparatus; a jam details display means for displaying details of the history of individual jams that have occurred at the same location based on a user operation on the jam history screen; Equipped with At least one of the jam occurrence history display means and the jam details display means displays at least one of the date and time when the jam occurred and paper information regarding the paper on which the jam occurred.

1. An image processing device comprising:

2. a jam occurrence location determination means for determining whether or not a location where a jam is currently occurring exists; a jam-prone location determination means for determining whether or not there is a location where jams have occurred more than a predetermined number of times; and the jam occurrence history display means, when it is determined that there is a location where jams have occurred more than the predetermined number of times, visualizes the location where jams have occurred more than the predetermined number of times, and when it is determined that there is a location where jams are currently occurring, visualizes the location where jams are currently occurring; 2. The image processing device according to claim 1, wherein:

3. the jam occurrence history display means displays only the most recent history at the location where a jam has occurred or where a jam is currently occurring, and when detecting a designation of the location where a jam has occurred or where a jam is currently occurring and an instruction to display a history other than the most recent history, displays each history of jams at the location related to the instruction.

2. The image processing device according to claim 1, wherein:

4. the jam occurrence history display means displays only the most recent history of a location where a jam has occurred or a location where a jam is currently occurring, and when it detects an operation on a display area where information about a location where a jam has occurred more than a predetermined number of times or a location where a jam is currently occurring is displayed, it displays each history of jams at the location related to the operation.

2. The image processing device according to claim 1, wherein:

5. the jam occurrence history display means displays jam history information indicating the history of jams in the order of the date and time when the jams occurred; 2. The image processing device according to claim 1, wherein:

6. the jam occurrence history display means displays, at a higher level, jam history information indicating the history of jams at a visualized location among a location where a jam has occurred more than a predetermined number of times and a location where a jam is currently occurring.

2. The image processing device according to claim 1, wherein:

7. the jam occurrence history display means displays at least one of a location where it is determined that a jam has occurred more than a predetermined number of times and a location where it is determined that a jam is currently occurring by using an icon superimposed on a diagram of the image processing device.

2. The image processing device according to claim 1, wherein:

8. the jam occurrence history display means displays nothing on the diagram of the image processing device when there is no location where it is determined that a jam has occurred more than a predetermined number of times and no location where it is determined that a jam is currently occurring.

2. The image processing device according to claim 1, wherein:

9. when there is no location where it is determined that jams have occurred more than a predetermined number of times, the jam occurrence history display means displays that there is no location where it is determined that jams have occurred more than the predetermined number of times, and does not display the location where jams have occurred more than the predetermined number of times; 2. The image processing device according to claim 1, wherein:

10. the jam occurrence history display means, when it is determined that there is no location where a jam is currently occurring, displays that there is no location where a jam is currently occurring, and does not display the location where a jam is currently occurring; 2. The image processing device according to claim 1, wherein:

11. displaying a screen showing a history of jams at at least one location in the image processing device by a jam occurrence history display means; displaying details of each history of jams that have occurred at the same location by a jam details display means based on a user operation on the jam history screen; At least one of the jam occurrence history display means and the jam details display means displays at least one of the date and time when the jam occurred and paper information regarding the paper on which the jam occurred.

2. A method for controlling an image processing apparatus comprising:

12. displaying a screen showing a history of jams at at least one location in the image processing device by a jam occurrence history display means; a jam detail display means displays details of each history of jams that have occurred at the same location based on a user operation on the jam history screen; A program for a computer, At least one of the jam occurrence history display means and the jam details display means displays at least one of the date and time when the jam occurred and paper information regarding the paper on which the jam occurred. A program characterized by:

Images