Image processing apparatus, image processing method, and storage medium

Abstract

To provide an image processing apparatus capable of performing maintenance of the image processing apparatus at an optimum date and time.SOLUTION: The image processing apparatus includes a management unit configured to manage a contamination state of a predetermined part of the image processing apparatus as a numerical value in association with a date and time, a display unit configured to display a list of trouble situations that have occurred in the image processing apparatus, and a control unit configured to estimate a date and time at which the contamination state of the predetermined part reaches a predetermined threshold.SELECTED DRAWING: Figure 32

Description

[Technical Field]

[0001] The present invention relates to an image processing device, an image processing method, a computer program, and the like. [Background technology]

[0002] When an abnormality occurs in an image processing device that a user cannot handle by themselves, a serviceman (maintenance person) is dispatched in an emergency. In addition, the serviceman periodically visits the user to perform maintenance on the image processing device. During an emergency dispatch or a regular visit, the serviceman needs to immediately determine the status of the image processing device and take action so as to minimize interference with the user's use of the image processing device.

[0003] Conventionally, the method for checking the device status is to display the component status, error history, and jam history in a menu format on a service mode screen exclusively for service personnel. In this case, the service personnel must go back and forth between menus to obtain the necessary information, which is inefficient.

[0004] Patent Document 1 discloses a method for checking the status of a device by displaying a status confirmation screen that consolidates device errors and errors in each application on one screen. Consolidating the device status on one screen saves the trouble of having to go back and forth between screens, but the status confirmation screen in Patent Document 1 does not provide enough information for service personnel.

[0005] For example, the service technician must identify the cause by taking into consideration the location of the abnormality, the condition of the parts, the error history, the jam history and their relative positions, and the device usage conditions (temperature, humidity, number of printed pages, etc.), and then consider the appropriate measures. Also, as mentioned above, the service technician must perform his / her work as efficiently as possible in the shortest possible time.

[0006] Furthermore, the optical unit is a consumable item that accumulates dirt over time, which can be reflected in scanned documents. To address this issue, Patent Document 1 discloses a system that notifies the user of errors caused by dirt detected by the optical unit during scanning. This makes it possible to prevent dirt from being reflected in the scanning results. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-229786 Summary of the Invention [Problem to be solved by the invention]

[0008] Optical units are often parts that are maintained by service personnel. Therefore, service personnel must periodically check the condition of the parts and clean the optical units. However, cleaning requires time and tools. For these reasons, cleaning every time is difficult, and there is the issue of not knowing the optimal time to clean, even if one wants to decide on a specific time to do so.

[0009] In order to solve the above-mentioned problems, one of the objects of the present invention is to provide an image processing apparatus that allows maintenance of the image processing apparatus to be performed at an optimal date and time. [Means for solving the problem]

[0010] In the image processing device, a management means for managing the state of contamination of a predetermined part of the image processing device as a numerical value linked to a date and time; a display means for displaying a list of troubles occurring within the image processing device; a control means for predicting a date and time when the degree of contamination of the predetermined part will reach a predetermined threshold value; The display means displays the date and time estimated by the control means when the display of the trouble status relating to the predetermined part is selected. [Effects of the Invention]

[0011] According to the present invention, it is possible to provide an image processing apparatus that can perform maintenance on the image processing apparatus at an optimal date and time. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating a configuration of a system including an image processing apparatus according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing a hardware configuration of the image processing apparatus. [Figure 3] FIG. 2 is a block diagram showing an example of processing functions related to the present embodiment. [Figure 4] FIG. 10 is a diagram illustrating an example of a top screen when an abnormality occurs in the image processing device. [Figure 5] FIG. 10 is a diagram illustrating an example of a top screen when there is no abnormality in the image processing device. [Figure 6] FIG. 10 is a diagram showing a part life screen. [Figure 7] FIG. 10 is a diagram showing a status details screen. [Figure 8] FIG. 10 is a diagram showing a trouble detection screen. [Figure 9] FIG. 10 is a diagram showing a stain details screen. [Figure 10] FIG. 10 is a diagram showing an error screen. [Figure 11] FIG. 10 is a diagram showing an error details screen. [Figure 12] FIG. 10 is a diagram showing a jam screen. [Figure 13] FIG. 10 is a diagram showing a jam details screen. [Figure 14] FIG. 10 is a diagram showing a temperature change screen. [Figure 15] FIG. 10 is a diagram showing a humidity change screen. [Figure 16] FIG. 10 is a diagram showing a print count screen. [Figure 17] FIG. 10 is a diagram showing a cassette history screen. [Figure 18] Shows historical data used to display part life information. [Figure 19] This shows the history data used to display information on trouble detection. [Figure 20] Indicates the history data used to display error information. [Figure 21] 10 shows historical data used to display jam information. [Figure 22] This shows temperature data used to display temperature change information. [Figure 23] This shows humidity data used to display humidity change information. [Figure 24] This indicates the data of the number of printed sheets used to display information on the number of printed sheets. [Figure 25] The cassette operation data used to display the cassette history information is shown. [Figure 26] 10 is a flowchart illustrating an example of a top screen display process including a status monitor startup process. [Figure 27] 27 is a flowchart continuing from FIG. 26. [Figure 28] 28 is a flowchart continuing from FIG. 27. [Figure 29] 18 is a flowchart showing an example of a screen transition process in response to an operation to switch between the screens of FIGS. 4 to 17. [Figure 30] 30 is a flowchart continuing from FIG. 29. [Figure 31] 31 is a flowchart showing the continuation of FIG. 30. [Figure 32] 10 is a diagram showing another example of the stain details screen of FIG. 9. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Not all of the features in the embodiments of the present disclosure are essential, and multiple features may be combined as desired. Furthermore, the configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the illustrated configurations. In the drawings, the same reference symbols are used to designate the same or similar configurations, and redundant explanations will be omitted.

[0014] <System configuration> FIG. 1 is a diagram showing the configuration of a system including an image processing apparatus according to an embodiment. The system of this embodiment includes an image processing device 103, a server PC (personal computer) 101, and a client PC 102. The image processing device 103, the server PC 101, and the client PC 102 are connected to one another via a network.

[0015] The network is a communication network realized by, for example, any one or a combination of LAN, WAN, telephone line, dedicated digital line, ATM, frame relay line, cable television line, wireless line for data broadcasting, etc. Multiple image processing devices 103 may be installed in one local area.

[0016] The image processing device 103 is a multi-function copier (MFP: Multi-Function Peripheral). That is, the image processing device 103 has a print function, a copy function, a facsimile transmission function, a scan function, etc. 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.

[0017] The image processing device 103 also has a function (SEND function) of reading a paper document and sending the image data to an external file server or email address. Furthermore, the image processing device 103 also has a function (remote copy function, facsimile transmission function) of sending data to another image processing device and printing it at the destination image processing device.

[0018] The image processing device 103 is connected via Ethernet (registered trademark) (not shown), but this is merely an example. All of the information processing devices other than the image processing device 103 (server PC 101, client PC 102) may be configured as the same computer.

[0019] Alternatively, the system may be configured only with the image processing device 103 by implementing these information processing devices in the image processing device 103. The information processing device used in this embodiment may not be a PC, but may be a terminal device other than a PC or a smartphone. Furthermore, the printing method of the image processing device 103 used in this embodiment may be an electrophotographic method, an inkjet method, or another method.

[0020] The image processing device may be, for example, a digital camera, a network camera, a mobile object with a camera, etc. Alternatively, it may be a system including a scanner, a printer, a digital camera, a network camera, a mobile object with a camera, etc., and a PC, various terminal devices, a smartphone, etc., connected via a network or the like.

[0021] <Hardware configuration of image processing device> 2 is a block diagram showing the hardware configuration of the image processing device 103. The image processing device 103 includes a controller unit 200, an operation unit 212, various sensors 255, a scanner 270, and a printer 295.

[0022] The controller unit 200 is connected to a scanner 270, which is an image input device for reading images, and a printer 295, which is an image output device, and on the other hand, is connected to Ethernet (registered trademark) or a public line to input and output image information and device information.

[0023] The controller unit 200 includes a CPU 201 as a computer, a RAM 202, a ROM 203, an HDD (hard disk drive) 204, and an operation unit I / F 206. The controller unit 200 also includes a network I / F 210, a modem 250, an SRAM 209, an image bus I / F 205, and an RTC (real-time clock) 211. Each of these units is connected to a system bus 207.

[0024] Furthermore, the controller unit 200 has a RIP (raster image processor) 260, a device I / F 220, a scanner image processing unit 280, a printer image processing unit 290, an image rotation unit 230, and an image compression / decompression unit 240. Each of these units is connected to an image bus 208.

[0025] The CPU 201 is a controller that controls the image processing device 103. The RAM 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 203 is a boot ROM that stores a system boot program. The HDD 204 stores system software, computer programs such as applications, and image data.

[0026] It should be noted that instead of the CPU 201, a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array) may be used.

[0027] Alternatively, an ASIC (Application Specification Integrated Circuit) or a DSP (Digital Signal Processor) may be used.

[0028] It is also possible to use a device having a storage medium other than the HDD 204. Examples of storage media other than the HDD 204 include flash memory, an SSD (Solid State Drive), an optical recording medium, and a magneto-optical recording medium.

[0029] The operation unit I / F 206 is an interface unit with an operation unit 212 having a touch panel, and outputs image data to be displayed on the operation unit 212. The operation unit I / F 206 also transmits information input by a user from the operation unit 212 to the CPU 201. The network I / F 210 connects to a network and inputs and outputs information.

[0030] The MODEM 250 connects to a public line and inputs and outputs information. The SRAM 209 is a non-volatile recording medium capable of high speed operation. The RTC 211 continues to count the current time even when the controller unit 200 is not powered on.

[0031] The image bus I / F 205 is a bus bridge that connects the system bus 207 and an image bus 208, which transfers image data at high speed, and converts the data structure. The image bus 208 is configured, for example, by a PCI bus or IEEE 1394. The RIP 260 converts the PDL code into a bitmap image.

[0032] The device I / F 220 is connected to various sensors 255 for detecting the status of each part of the image processing device, and acquires detection outputs from the various sensors 255. The device I / F 220 also connects the scanner 270 and printer 295 to the controller unit 200, and performs synchronous / asynchronous conversion of image data.

[0033] The scanner image processing unit 280 corrects, processes, and edits input image data. The printer image processing unit 290 corrects (printer correction), converts resolution, and so on for print output image data. The image rotation unit 230 rotates image data. The image compression / expansion unit 240 performs image compression and expansion processing.

[0034] <Software configuration of image processing device> FIG. 3 is a block diagram showing an example of processing functions of the units in the image processing device 103, which functions are related to this embodiment.

[0035] As described in FIG. 2, the CPU 201 executes part or all of a program stored in the ROM 203 on the RAM 202, thereby realizing the functions of the functional units described below and the processing related to the flowcharts described below.

[0036] That is, the CPU 201 as a computer controls each unit of the image processing device 103 based on a computer program stored in a storage medium, thereby executing each process of the flowcharts in Figs. 26 to 31 described below and various operations in the image processing device 103.

[0037] The display unit 302 displays the status and operation menu of the image processing device 103 on the operation unit 212. The display unit 302 functions as a display means that executes a display step of displaying a list of trouble situations that have occurred in the image processing device.

[0038] An input unit 303 receives operation instructions from a user. A history management unit 304 processes information and stores status information and history information of the image processing device 103 in a history DB.

[0039] The history management unit 304 is an example of a management means for managing the status information and history information of the image processing device. The "history information" here refers to historical information about the usage status of the image processing device 103. The history management unit 304 as a management means manages the state of contamination of specific parts of the image processing device (for example, the scanner 270 for reading documents and the drum for printing images) as numerical values ​​linked to the date and time.

[0040] The history management unit 304 also manages information on the history of the state information, but to distinguish it from the above-mentioned "history information," the information on the history of the state information is referred to as "state history information" in this embodiment.

[0041] The control unit 301 controls the display unit 302, the input unit 303, and the history management unit 304. The control unit 301 is mainly composed of the CPU 201 and the like, and is an example of a processing means that performs processing based on the state information and history information managed by the management means.

[0042] <Screen configuration according to the embodiment> Next, the status monitor screen that displays the status and history of the image processing device 103 for service personnel will be described with reference to Figures 4 to 17. The status monitor screen is a screen that is 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 data described in Figures 4 to 17 is displayed based on data recorded in the history management unit 304.

[0043] 4 is a diagram showing an example of a top screen 400 when an abnormality occurs in the image processing device 103. As a schematic diagram of the image processing device, for example, a cross-sectional view 401 is displayed, and the location of the abnormality in the image processing device and its type are displayed as icons mapped on the cross-sectional view.

[0044] The cross-sectional view 401 also shows the paper transport path, allowing the service technician to know whether there is an abnormality that may affect the use of the main functions of the image processing device, such as scanning and printing. The paper transport path is shown by a dashed line in the cross-sectional view 401, but may be shown by other lines or diagrams.

[0045] 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 type indicates whether a deteriorated part needs to be replaced, whether a check is required due to a problem, whether there is a location where a jam is occurring or occurs frequently, etc.

[0046] The information about the abnormality (content, type, etc.) and the coordinates of the location where the abnormality has occurred on the cross-sectional view 401 are predetermined on a one-to-one basis or one for each of multiple locations.

[0047] Part life 403, trouble detection 404, error 405, and jam 406 are notification areas that display notifications of abnormalities occurring in the image processing device 103, and each include a button for transitioning to a detailed screen.

[0048] On the top screen 400, the display unit 302 divides information related to abnormalities, which is mainly status information managed by the history management unit 304, into a plurality of different categories and displays the information for each category. The plurality of categories of information related to abnormalities include, for example, part life 403, trouble detection 404, error 405, and jam 406. These plurality of categories are an example of a first category group.

[0049] The areas where part life 403, trouble detection 404, error 405, and jam 406 are displayed are notification areas that display (notify) information about abnormalities occurring in the image processing device 103. These notification areas include buttons for transitioning to detailed screens, and for example, the entire notification area is an operation area that accepts user operations.

[0050] Since the content that can be displayed in each notification area is limited by the screen area, abnormalities are displayed in order of priority, and if they cannot all be displayed, the remaining number of abnormalities is displayed as "Other." For example, for the priority of part life 403, "replacement required" is set higher than "replacement recommended," and if they are at the same level, the order follows that of the part life screen, which will be described later.

[0051] Regarding the priority of Trouble Detection 404, "Check Required" is set higher than "Check Recommended", and if they are at the same level, they will follow the sorting order of the Trouble Detection screen described later. Error 405 displays currently occurring errors in descending order of the date and time of occurrence.

[0052] For errors 405, the order of priority may be set in descending order of the date and time of occurrence as described above, or in ascending order of the date and time of occurrence. Alternatively, the order of priority may be set based on other criteria. For jams 406, "jam occurring" is set higher than "frequent jams," and if the priorities are at the same level, they are displayed in descending order of the date and time of occurrence, just like the jam screen described below.

[0053] In the example of Figure 4, part life 403 indicates that drum unit Y needs to be replaced, and that drum unit M and drum unit C are nearing the time to replace them (replacement recommended) using icons corresponding to legend 402.

[0054] Furthermore, part lifespan 403 indicates that there is another part that is nearing the end of its lifespan, i.e., its expiration date. When the notification area for part lifespan 403 (or the band-shaped button at the top of the notification area labeled "part lifespan") is pressed, the screen transitions to a part lifespan screen, which will be described later.

[0055] 4, Trouble Detection 404 uses icons to indicate that there are two items that need to be checked and one item that is recommended to be checked. When the notification area of ​​Trouble Detection 404 or the button at the top of the notification area is pressed, the screen transitions to the Trouble Detection screen, which will be described later.

[0056] In the example of Figure 4, Error 405 uses an icon to indicate that there are two errors currently occurring. No icon is displayed for Error 405 because many system errors cannot be determined to be located at a specific position on the cross-sectional view. Pressing the notification area for Error 405 or the button at the top of that notification area will take you to the error screen, which will be described later.

[0057] 4, Jam 406 uses icons to indicate that there is one active jam, one frequent jam, and two other notifications. When the notification area for Jam 406 or the button at the top of the notification area is pressed, the screen transitions to a jam screen, which will be described later.

[0058] The usage status button 407 is a button for transitioning to a usage status screen. The usage status is the usage status of the image processing device 103 based on the history information managed by the history management unit 304. As will be described later, the usage status is displayed in multiple categories on a screen separate from the top screen 400.

[0059] 5 is a diagram showing an example of the top screen 400 when there are no abnormalities in the image processing device 103. Since there are no abnormalities in the cross-sectional view 401, no icons are displayed in the legend 402. "No notification" is displayed in each notification area (403 to 406), allowing the service technician to recognize at a glance that there are no abnormalities.

[0060] In this way, the service technician can obtain information on the presence or absence of an abnormality in the entire image processing apparatus, or the location and details of the abnormality, from the top screen 400, so that the technician can quickly identify the location where the necessary action should be taken and begin work immediately. In addition, the service technician can also consider efficient work procedures, such as treating abnormalities in locations close to each other together on the cross-sectional view 401.

[0061] 6 is a diagram showing a parts lifespan screen 500 that is displayed when the parts lifespan 403 on the top screen 400 is pressed. At the top of the screen, there are displayed buttons for switching between screens: a back 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.

[0062] A back button 501 is a button for returning to the top screen. When the trouble detection button 503, the error button 504, the jam button 505, or the usage status button 506 is pressed, the screen transitions to the respective detailed screen.

[0063] These buttons 501 to 506 are also displayed on each detailed screen, which will be described later, allowing the service technician to easily move between the detailed screens, making it easier to compare the information displayed on each screen and deduce the cause of the abnormality.

[0064] The part life screen 500 also displays the cross section 401 and legend 402, but the icons displayed are limited to parts.

[0065] Parts list 507 displays a list showing the status of replacement parts. Each column of parts list 507 displays the "part name," "status," and "number of sheets used" of paper that has been passed (used) after the part was replaced. Just to be clear, the status of parts is not a concept that completely matches the "status information" that is managed and displayed by the above categories, but rather refers to the information on the status of parts within the overall status information.

[0066] In the parts list 507, the "status" is displayed as a four-level meter icon according to the status value of the part. For example, level meter icons are displayed for level "0," which indicates an indefinite value immediately after a part has been replaced, 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.

[0067] The current status value is also displayed numerically to the right of the level meter. This status value increases as the part deteriorates, and is preset so that the value at which replacement is required is 100%. Parameters used to calculate the status value include, for example, the number of sheets used after replacement, and the current and resistance values ​​of each part.

[0068] When the status value level is "2," a replacement recommended icon is displayed on the left side of the list, indicating that the corresponding part is nearing its expiration date. In the example in Figure 6, "Drum Unit M," "Drum Unit C," and "Cassette Roller 1" are in a state where replacement is recommended. When the status value level is "3," a replacement required icon is displayed on the left side of the list, indicating that the corresponding part has reached its expiration date. In the example in Figure 6, "Drum Unit Y" is in a state where replacement is required.

[0069] When a service technician replaces a part, the replacement of the part is detected and the status value temporarily returns to the no-data level "0." Therefore, the icons indicating whether the replaced part needs to be replaced or is recommended for replacement are hidden from the cross-sectional view 401 and the parts list 507.

[0070] Unlike the notification area for the part life 403 on the top screen 400, the parts list 507 displays all parts managed by the service technician, regardless of whether they are abnormal or not. Therefore, the status values ​​of parts that do not yet require replacement can also be confirmed.

[0071] The status of all parts can be displayed by scrolling up and down the parts list 507. A status details button 508 is a button for transitioning to a screen that displays a graph showing the transition of the status value of the part selected in the parts list 507.

[0072] 7 shows a status details screen 510 that is displayed when the status details button 508 is pressed. A status transition graph 511 shows the daily transition of the status value of the selected part. A reference line is displayed on the graph at 100%, the point at which the part needs to be replaced.

[0073] The display period 512 is a pull-down menu for switching the graph display period between 30 days and 180 days. The display period 512 is not limited to 30 days or 180 days. The close button 513 is a button for closing the status details screen 510 and returning to the part lifespan screen 500.

[0074] The pull-down menu for switching the display period 512 is an example of a setting area that accepts an operation to set the display period. The pull-down menu for switching the display period 612 and the date switching button 906, which will be described later, are also examples of setting areas.

[0075] 7 shows a status transition graph 511 for "drum unit Y" on the part lifespan screen 500, which allows the user to see the daily transitions until the status value exceeded 100%. This allows the service technician to estimate whether the deterioration has progressed as expected, or whether the deterioration of the part has progressed rapidly due to a defective part or an environmental change.

[0076] In the example in Figure 7, the status value is shown as having exceeded the expiration date of a part, but for parts that have not yet reached their expiration date, the service technician can predict from the slope of the graph how many days until the part's expiration date. This allows the service technician to determine whether or not to bring a replacement part during their next visit, and have the replacement part ready.

[0077] The state transition graph 511 is data generated based on state history information managed by the history management unit 304. Similarly, the dirt transition graph 611 (FIG. 9), the error list (FIG. 10), and the jam detail list 813 (FIG. 12) are also data generated based on state history information.

[0078] 8 is a diagram showing a trouble detection screen 600 that is displayed when trouble detection 404 on the top screen 400 is pressed, or when trouble detection button 503 on each detailed screen is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIG.

[0079] The trouble detection screen 600 also displays the cross section 401 and the legend 402, but the icons displayed are limited to those indicating whether or not a trouble check is required.

[0080] A trouble list 601 displays a list of troubles that service personnel often need to deal with and their details. "Dirt on the ADF optical unit" and "Dirt on the reader optical unit" display information on whether cleaning of the optical unit is required. ADF is an abbreviation for Automatic Document Feeder.

[0081] For example, the degree of dirt on the mirror is detected from the value of the mirror's reflected light obtained by an optical sensor. As with the part life status value and status level described above, the degree of dirt [%] is displayed, with 100% being the standard value for when cleaning is required, and the dirt level is displayed as a four-level level meter icon corresponding to the degree of dirt. Based on this degree of dirt or dirt level, information on whether or not action is required is displayed.

[0082] Specifically, for example, if the degree of dirtiness is indefinite, a level "0" icon is displayed. If the degree of dirtiness is 0 to 79%, a level "1" icon is displayed. If the degree of dirtiness is 80 to 99%, a level "2" icon is displayed.

[0083] If the dirt level is 100% or higher, a level "3" icon will be displayed. If the dirt level is level "2," a check recommended icon will be displayed on the left side of the list, indicating that cleaning is recommended. If the dirt level is level "3," a check required icon will be displayed on the left side of the list, indicating that cleaning is required.

[0084] Also, messages regarding the objects / contents of the trouble list 601 change depending on the level. For example, level "0" displays "No data," level "1" displays "Good," level "2" displays "Dirty," and level "3" displays "Severely Dirty."

[0085] Regarding the dirt on the optical unit, by selecting one item from the trouble list 601 and pressing the dirt details button 602, a graph showing the progress of the dirt level (explained later in FIG. 9) can be viewed.

[0086] In the trouble list 601, whether or not there is an abnormality in each cassette is displayed along with the details of the abnormality. It is determined that an abnormality has occurred in the cassette mainly when a misalignment of the paper regulation plate (guide) inside the cassette is detected. If there is an abnormality in the cassette, the message "Check required" is displayed in the list, and if there is no abnormality, the message "None" is displayed.

[0087] The treated button 603 can be pressed when the optical unit or cassette "needs checking" or "check recommended." After cleaning the optical unit, if the service technician selects the target optical unit from the trouble list 601 and presses the treated button 603, the contamination level returns to "0."

[0088] As a result, the "Check Required" or "Check Recommended" icon disappears from the cross-sectional view 401 and the trouble list 601. Also, if the service technician selects the target cassette in the trouble list 601 after checking the cassette and presses the "Processed" button 603, the display returns to normal. As a result, the "Check Required" icon disappears from the cross-sectional view 401 and the trouble list 601.

[0089] 9 is a diagram showing a dirt details screen 610 that is displayed when the dirt details button 602 for the optical unit is pressed. A dirt transition graph 611 shows the daily transition of the dirt level of the optical unit selected in the trouble list 601.

[0090] A reference line is displayed on the graph at 100%, the point at which cleaning becomes necessary. Display period 612 is a pull-down menu that switches the graph display period between 30 days and 180 days. Close button 613 is a button that closes the dirt details screen 610 and returns to the trouble detection screen 600.

[0091] In the example of FIG. 9, a dirt transition graph 611 for "Dirt on reader optical unit" on the trouble detection screen 600 is shown, and the daily transition can be seen until the dirt level reaches 81% and a check is recommended.

[0092] From the slope of this graph, the service technician can predict how many days until the condition will become necessary for cleaning, which allows the service technician to determine the date of the next visit, or whether they should bring cleaning tools with them when they next visit, and then prepare accordingly.

[0093] Here, the degree of contamination of the parts is displayed in detail, but if another part is selected, a different analysis result may be displayed. For example, if cassette 1 is selected in Fig. 8, 602 in Fig. 8 is changed to display "Cassette details," and the cassette in Fig. 17 described below is displayed.

[0094] 10 is a diagram showing an error screen 700 that is displayed when error 405 on the top screen 400 in FIG. 4 is pressed, or when error button 504 on each detailed screen (for example, FIG. 6, FIG. 8, etc.) is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIG. 6 and FIG. 8.

[0095] The error list 701 displays a list of the error history that has occurred in the image processing device 103. For each error, the error list 701 displays the date and time of the error occurrence, and the time of recovery (for example, "8:50" on the third line or "16:40" on the fourth line), and also displays the error code and its title as the contents.

[0096] Errors on the first and second lines that do not display the recovery time indicate that the error is still occurring. For example, by selecting one error in the error list 701 and pressing the error details button 702, detailed information about the selected error can be confirmed.

[0097] 11 shows an error details screen 710 that is displayed when the error details button 702 is pressed. An error code 711 indicates an error code that identifies the selected error. Error information 712 displays the title, description, and solution of the error.

[0098] The page forward button 713 is a button for advancing to the next page when there are multiple pages of error information. The close button 714 is a button for closing the error details screen 710 and returning to the error screen 700. The service technician can check the currently occurring error and its contents from this screen.

[0099] 12 is a diagram showing a jam screen 800 that is displayed when jam 406 on the top screen 400 in FIG. 4 is pressed, or when jam button 505 on each detailed screen (for example, FIG. 6, FIG. 8, etc.) is pressed. Buttons 501 to 506 arranged at the top of the screen have the same functions as buttons 501 to 506 shown in FIG. 6, FIG. 8, and FIG. 10.

[0100] The jam screen 800 also displays the cross section 401 and the legend 402, but the icons displayed are limited to those indicating jams that are currently occurring or frequent jams.

[0101] The jam list 801 displays a list of jam history. The jam list 801 displays the date, time, and recovery time of each jam, as well as the jam code and type of jam. The sensor number and the cumulative number of the same jam code are also displayed.

[0102] The jam in the first line, which does not display the recovery time, indicates that the jam is still occurring, and an icon indicating that a jam is occurring is displayed at the left end of the jam list 801. Jams with a cumulative number of occurrences exceeding a predetermined number, such as the jam history in the second and fourth lines, are determined to be frequent jams, and a frequent jam icon is displayed at the left end of the list.

[0103] In the example of FIG. 12, a jam that has occurred 10 or more times is determined to be a frequent jam. If there are multiple records of the same jam code, only the most recent one is displayed on the list. This makes it easier to understand the type of jam that has occurred. By selecting one item from the jam list 801 and pressing the jam details button 802, detailed information about the selected jam can be confirmed.

[0104] The reset button 803 is a button for clearing the jam history that is being displayed. A service technician uses the reset button 803 when he or she has finished checking for an ongoing or frequent jam and wishes to delete the notification. When the reset button 803 is pressed, the date and time in the reset date and time 804 is updated, and the jam list 801 now displays the jam history from the reset date and time 804 onwards.

[0105] 13 is a diagram showing a jam details screen 810 that is displayed when the jam details button 802 is pressed. Jam details 811 displays the jam code and type of jam selected in the jam list 801. Sensor number 812 displays the jam code and the sensor number associated with the location where the jam occurred.

[0106] The jam details list 813 displays, in descending chronological order, the history of jams with the same jam content 811 (i.e., jam code and jam type). The jam details list 813 displays the cumulative number, occurrence date, occurrence time, recovery time, paper feed position, paper feed counter, and paper feed size.

[0107] The paper feed position is the position of the paper when the jam occurred. The number shown in the "paper feed counter" is the number of sheets fed from the paper feed position when the jam occurred. The paper feed size is the size of the paper fed.

[0108] In the jam list 801 in Fig. 12, the same jam code is aggregated into the most recent case and displayed, making it easy to see the variations in jams that have occurred, but in the jam details list 813 in Fig. 13, it is easier to see how often the same jam has occurred. When there are a large number of cases in the jam details list 813, it is possible to scroll up and down the list.

[0109] The close button 814 is a button for closing the jam details screen 810 and returning to the jam screen 800. Since the service technician can know not only the current jam but also the locations where jams have frequently occurred in the past and their frequency, the technician can consider cleaning or replacing surrounding parts in the locations where jams have occurred or occur frequently.

[0110] As will be described below with reference to Figs. 14 to 17, information on the usage status of the image processing device 103 is displayed in multiple categories on a screen separate from the top screen 400. These categories include "temperature," "humidity," "number of printed sheets," and "cassette history." These multiple categories of information on the usage status are an example of a second category group.

[0111] 14 to 17 are figures showing the usage status screen 900 that is displayed when the usage status button 407 on the top screen 400 of FIG. 4 is pressed, or when the usage status button 506 on each detailed screen (e.g., FIG. 6, FIG. 8, etc.) is pressed.

[0112] A temperature button 901, a humidity button 902, a number of prints button 903, and a cassette history button 904, which transition to each usage status screen, are displayed on the right edge of the usage status screen 900. These buttons 901 to 904 are displayed on each usage status screen 900 shown in Figures 14 to 17, so the service technician can easily move between each usage status screen 900.

[0113] Furthermore, by using the back button 501 to the usage status button 506 described above, the service technician can easily move back and forth between the parts life screen 500 in Fig. 6, the trouble detection screen 600 in Fig. 8, the error screen 700, jam screen 800, and usage status screen 900 in Fig. 10. This allows the service technician to easily compare the abnormality information with the usage status, and easily deduce the cause of the abnormality.

[0114] 14 is a diagram showing a temperature change screen that is displayed when a temperature button 901 is pressed on the usage status screen 900. A temperature change graph 905 shows the temperature (°C) on the vertical axis and the time (hour) on the horizontal axis, and shows the temperature inside (inside) / outside (outside) the image processing device for one day at 10-minute intervals.

[0115] The date switching button 906 is a button for switching the date of the displayed graph. By pressing the date switching button 906 and selecting a date, data from up to one month prior can be displayed.

[0116] The temperature change graph 905 displays the upper limit (e.g., 30°C) and lower limit (e.g., 15°C) of the temperature reference range as dotted lines, and if the temperature is outside the reference range, it can be determined that the environment needs to be reviewed. Furthermore, the service technician can compare the period on the temperature change screen in Figure 14 that is the same as the period during which a jam occurred on the error screen 700 in Figure 10 or the jam screen 800 in Figure 12, for example, to check whether the temperature change is the cause of the error or jam.

[0117] 15 is a diagram showing a humidity change screen that is displayed when the humidity button 902 on the usage status screen 900 is pressed. The humidity change graph 907 shows humidity (%) on the vertical axis and time (hours) on the horizontal axis, and shows the humidity inside and outside the aircraft for one day at 10-minute intervals. The date change button 908 is a button that changes the date of the displayed graph, and can display data from up to one month ago.

[0118] The humidity change graph 907 displays the upper limit (e.g., 60%) and lower limit (e.g., 40%) of the standard humidity range as dotted lines, and if the humidity is outside the standard range, it can be determined that the environment needs to be reviewed. Also, the service technician can compare the period in which a jam occurred on the jam screen 800 in Fig. 12 with the same period on the humidity change screen in Fig. 15 to confirm whether humidity changes are the cause of the jam.

[0119] 16 is a diagram showing the print count screen that is displayed when the print count button 903 on the usage status screen 900 is pressed. The print count graph 909 shows the number of prints (sheets) on the vertical axis and time (hours) on the horizontal axis.

[0120] The display period switch button 910 is a button for changing the graph display period to one month or one day. The date switch button 911 is a button for switching the date on which the graph is displayed.

[0121] When "Month" is selected with the display period switch button 910, one month's worth of data is displayed in one-day intervals, and the data for each month can be switched and displayed by selecting with the date switch button 911. In this case, the date switch button 911 displays the year and month, and the horizontal axis of the print count graph 909 is displayed in days (rather than "hours" as shown in the example of FIG. 16).

[0122] On the other hand, when "day" is selected with the display period switch button 910, one day's worth of data is displayed at one-hour intervals, as shown in the example of Fig. 16, and the data for each day can be switched and displayed by selecting with the date switch button. In this case, the date switch button 908 displays the year, month, and day, and the horizontal axis of the print count graph 909 is displayed in time (hour) units.

[0123] For example, if it is estimated that a part will reach its expiration date earlier than expected based on the part lifespan screen 500 in Fig. 6, the following inference is possible: That is, if a service technician confirms from the print count graph 909 in Fig. 16 that a large amount of printing was done just before the expiration date, the technician can infer that the large amount of printing may be the cause of the earlier expiration of the part.

[0124] 17 is a diagram showing a cassette history screen that is displayed when the cassette history button 904 on the usage status screen 900 is pressed. A cassette history list 912 displays the operation history of the cassette in chronological order.

[0125] The cassette switching button 913 is a button for selecting the target cassette to be displayed in the cassette history list 912. For example, if a jam or an error occurs, a service technician can check the cassette history in the cassette history list 912 and make the following observations.

[0126] In other words, the service technician can determine whether the jam or error was caused by an operation or setting mistake made by the user of the image processing device, or whether the malfunction was caused by some other factor other than the operation or setting mistake made by the user.

[0127] For ease of explanation, the above-described parts life screen 500, trouble detection screen 600, error screen 700, jam screen 800, and usage status screen 900 may be referred to as "information screens by category" below.

[0128] As described above, the status transition graph 511, the dirt transition graph 611, the error list 701, and the jam detail list 813 are examples of time-series data generated for each category in the first category group, and are examples of first data indicating information related to an abnormality. In this way, these time-series data are displayed in list format or graph format.

[0129] Similarly, the data of the temperature change graph 905, humidity change graph 907, number of printed sheets graph 909, and cassette history list 912 are examples of time series data generated for each category in the second category group, and are examples of second data indicating usage status.

[0130] Hereinafter, the status transition graph 511, the dirt transition graph 611, the error list 701, the jam detail list 813, the temperature change graph 905, the humidity change graph 907, the number of printed sheets graph 909, and the cassette history list 912 may each be referred to as time-series data.

[0131] 6, 8, 10, 12, 14 to 17, the screen area including the part life button 502, the trouble detection button 503, the error button 504, the jam button 505, and the usage status button 506 is an example of the first area. The first area has a function of accepting an operation to switch the display between the first display information and the second display information.

[0132] The parts list 507 (FIG. 6), the trouble list 601 (FIG. 8), the error list 701 (FIG. 10), and the jam list 801 (FIG. 12) are examples of the first display information. The status transition graph 511 (FIG. 7), the dirt transition graph 611 (FIG. 9), and the jam detail list 813 (FIG. 13) are also examples of the first display information.

[0133] In this way, when displaying the first display information, the display unit 302 divides information about an abnormality into multiple categories and displays each category on one screen. Note that the first display information may also include a cross-sectional view 401 and other operation buttons.

[0134] The other operation buttons include, for example, buttons for displaying details in each category (508, 602, 702, 802, etc.), a processed button 603, a reset button 803, etc.

[0135] Temperature change graph 905 (FIG. 14), humidity change graph 907 (FIG. 15), number of printed sheets graph 909 (FIG. 16), and cassette history list (FIG. 17) are examples of the second display information. In this way, when displaying the second display information, display unit 302 divides the information on usage status into multiple categories and displays one category per screen.

[0136] The first area includes a first operation area that accepts an operation to select one category from the first category group to display the first display information, and a second operation area that accepts an operation to display the second display information. The area that includes all of the buttons 502 to 505 is an example of the first operation area. On the other hand, the usage status button 506 is an example of the second operation area.

[0137] The screen areas that display the temperature change graph 905, humidity change graph 907, number of printed sheets graph 909, and cassette history list 912 are examples of the second area.

[0138] As described above, in this embodiment, the display unit 302 has a first area that accepts an operation to switch the display between first display information for displaying information regarding abnormalities in the image processing device and second display information for displaying information regarding the usage status of the image processing device.

[0139] Moreover, the display unit 302 has a second area for switching between the first display information and the second display information by operating the first area, and furthermore, the display unit 302 is configured to be able to display a screen configured to include the first area and the second area on a single screen.

[0140] The entire temperature button 901, humidity button 902, number of prints button 903, and cassette history button 904 shown in the temperature change graph 905 (Figure 14) are an example of a third area operation that accepts an operation to select one category from the second category group.

[0141] <History data configuration> Next, we will explain the data recorded in the history management unit 304, which manages the data displayed on the status monitor screen. The history management unit 304 organizes values ​​and settings obtained from the various sensors 255, scanner 270, and / or printer 295 via the device I / F 220 in Figure 2 into necessary information and saves it in the HDD 204 or RAM 202.

[0142] Note that "history data" here refers to both the history data of "status information (part lifespan, trouble detection, errors, jams)" and "usage status based on history information." The history data of status information is an example of "status history information," as described above.

[0143] 18 shows history data used to display information about the lifespan of a part. This history data includes a number (No.) 1001, a part name 1002, and history data 1003 of the part's condition.

[0144] Number 1001 indicates the order in which the parts are arranged in this history data. The status history data 1003 includes, for example, the date the data was acquired, the part's status level, status value [%], and number of parts used. The status history data 1003 is saved by day. The status level, status value, and number of parts used are as described above in the explanation of parts list 507 in FIG. 6.

[0145] In the condition history data 1003, parts with a condition level of "3" are displayed as parts requiring replacement in the cross-sectional view 401 and part life 403 of Fig. 4. Parts with a condition level of "2" are displayed as parts recommended for replacement in the cross-sectional view 401 and part life 403 of Fig. 4.

[0146] All parts and their states indicated in the part name 1002 are displayed in the order of the number 1001 in the parts list 507 of Fig. 6. Furthermore, the state history data 1003 is used to display the state transition graph 511 of Fig. 7.

[0147] For example, the display period can be 30 days or 180 days, so at least 180 days of data is retained. If a part replacement by a service technician is detected, the condition level of the replaced part will be set to "0."

[0148] A status level of "0" means that the value is indefinite after a part has been replaced. In addition, there is no data for the status value [%] and number of sheets used. As described above, the part life history data in Figure 18 is used to display part life on each screen.

[0149] 19 shows history data used to display information on trouble detection. This history data includes a number (No.) 1101, a target 1102, and trouble history data 1103. The number 1101 indicates the order in which the troubles are arranged in this history data. The target 1102 indicates the name of the trouble or its details.

[0150] The trouble history data 1103 includes the date when the data was acquired, the dirt level, the dirt degree [%], and the detected abnormality of the cassette. The dirt level, the dirt degree [%], and the detected abnormality of the cassette are as described above in the explanation of the trouble list 601 in FIG. 8.

[0151] In the case of optical units, the data includes the date the data was acquired, the contamination level, and the degree of contamination [%], and this data is saved daily. An optical unit with a contamination level of "3" is displayed in the cross section 401 and trouble detection 404 in Figure 4 as a problem that requires checking.

[0152] An optical unit with a contamination level of "2" is displayed in the cross section 401 and in the trouble detection 404 in Fig. 4 as a problem that requires checking. Furthermore, trouble history data 1103 related to the optical unit is used to display the contamination transition graph 611 in Fig. 9. Since the display period can be either 30 days or 180 days, at least 180 days' worth of data is stored.

[0153] In the case of cassettes, the history data 1103 for each trouble includes the date the data was acquired and whether or not an abnormality was detected, and this data is saved by day. Cassettes for which an abnormality has been detected are displayed in the cross section 401 and trouble detection 404 in Figure 4 as troubles that require checking. The troubles and their status (degree and level of contamination) for all objects 1102 are displayed in the trouble list 601 in Figure 9 in the order of number 1101.

[0154] 8, when a service technician selects one of the troubles in the trouble list 601 and presses the "resolved" button 603, the value relating to the trouble state of that trouble is updated to the following value: That is, if the trouble of that trouble is dirt on the optical unit, the dirt level value becomes level "0", which is in an indefinite state.

[0155] At that time, there will be no data for the degree of contamination [%]. If the problem is with the cassette, the abnormality detection will be updated to "none." As described above, the trouble detection history data in Figure 19 is used to display trouble detection on each screen.

[0156] As described above, in this embodiment, the history management unit 304 as a management unit executes a management step of managing the state of contamination of a predetermined part of the image processing apparatus as a numerical value in association with the date and time.

[0157] Note that the predetermined parts in this embodiment include, for example, the ADF optical unit and reader optical system of the scanner 270 for reading a document, cassettes 1 to 4, a drum for printing an image, etc. In other words, the predetermined parts may be any parts that are susceptible to contamination in the image processing device.

[0158] 20 shows history data used to display error information. This history data includes an error code 1201, an error title 1202, an occurrence date 1203, an occurrence time 1204, and a recovery time 1205.

[0159] The error code 1201 is a code for identifying the error. The occurrence date 1203 and occurrence time 1204 are the date and time when the error occurred, respectively. The recovery time 1205 is the time when the error was resolved. An error for which the recovery time 1205 is not recorded is displayed as an ongoing error in error 405 in Figure 4.

[0160] The history data in Fig. 20 is displayed in the error list 701 in Fig. 10 in descending order of occurrence date 1203 and occurrence time 1204. Although not shown in Fig. 20, content corresponding to each error code in error code 1201 is stored in HDD 204 and is displayed on the error details screen in Fig. 11. As described above, the error history data in Fig. 20 is used to display errors on each screen.

[0161] 21 shows history data used to display jam information. This history data includes a jam code 1301, a type 1302, a sensor 1303, an occurrence date 1304, an occurrence time 1305, a recovery time 1306, a cumulative number 1307, a paper feed position 1308, a paper feed counter 1309, and a paper feed size 1310.

[0162] The jam code 1301 is a code for identifying the jam. The type 1302 is the type of jam corresponding to the jam code. There are various types of types 1302, such as DELAY, in which the sensor does not detect the paper even after the expected time has passed, STNRY, in which the sensor continues to detect the paper for the expected time or longer, and DOUBLE, in which the ADF sensor detects double-feeding of paper.

[0163] Sensor 1303 is the sensor number that detected the jam. Occurrence date 1304 and occurrence time 1305 are the date and time when the jam occurred, respectively. Recovery time 1306 is the time when the jam was cleared. A jam for which the recovery time 1306 is not recorded is displayed as an ongoing jam in the cross section 401 and jam 406 in FIG. 4.

[0164] The cumulative number 1307 is the 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 in Fig. 12 is counted up as the cumulative number. For example, if the cumulative number reaches a predetermined number (here, 10 or more), it is determined to be a multiple jam, and is displayed in the cross section 401 and jam 406 in Fig. 4.

[0165] A paper feed position 1308 is the position where the jammed paper was fed, and a paper feed counter 1309 is the number of sheets of paper fed from the paper feed position.

[0166] The history data in Fig. 21 is displayed in the jam list 801 in Fig. 12 in descending order of occurrence date 1304 and occurrence time 1305. In this case, as described above, only the most recent jam with the same jam code is displayed. The history of the same jam code is displayed on the jam details screen in Fig. 13.

[0167] 12, when the reset button 803 is pressed, the jam history before the date and time of pressing is deleted. As described above, the jam history data in FIG. 21 is used to display the jam on each screen. Note that each piece of history data in FIGS. 20 and 21 may also have a consecutive number such as the history data numbers 1001 and 1101 shown in FIGS. 18 and 19.

[0168] 22 to 25 show data used to display information on usage status (temperature, humidity, number of printed sheets, and cassette history).

[0169] 22 shows temperature data used to display information about temperature changes. This data includes date 1401, time 1402, inside the device 1403, and outside the device 1404. Date 1401 indicates the date on which the temperature data was acquired, and data for one month, for example, is saved.

[0170] Time 1402 indicates the time when the temperature data was acquired, and data is saved, for example, at 10-minute intervals. Inside 1403, temperature data acquired by a thermometer installed inside the machine (not shown) is saved. Outside 1404, temperature data acquired by a thermometer installed outside the machine (not shown) is saved. The above data shown in FIG. 22 is used to display the temperature change graph 905 in FIG. 14.

[0171] 23 shows humidity data used to display information about humidity changes. This data includes a date 1411, a time 1412, an inside-aircraft location 1413, and an outside-aircraft location 1414. The date 1411 indicates the date on which the humidity data was acquired, and data for one month is saved, for example. The time 1412 indicates the time when the humidity data was acquired, and data is saved, for example, at 10-minute intervals.

[0172] Temperature data acquired by a hygrometer installed inside the machine (not shown) is stored in inside 1413. Temperature data acquired by a hygrometer installed outside the machine (not shown) is stored in outside 1414. The above data shown in Fig. 23 is used to display the humidity change graph 907 in Fig. 15.

[0173] 24 shows data on the number of printed sheets used to display information on the number of printed sheets. This data includes a date 1421, a time 1422, and a number of printed sheets 1423. The date 1421 indicates the date on which the number of printed sheets data was acquired. The time 1422 indicates the time when the number of printed sheets data was acquired.

[0174] The number of printed sheets 1423 indicates the number of printed sheets printed by the image processing device 103. For example, the data for the date 1421, the time 1422, and the number of printed sheets 1423 for one month are saved at one-hour intervals. The above data shown in Fig. 24 is used to display the number of printed sheets graph 909 in Fig. 16.

[0175] 25 shows cassette operation data used to display cassette history information. This data is saved when a user closes a cassette of the image processing device 103 or changes the media (i.e., paper).

[0176] This data includes a date 1431, a time 1432, a cassette 1433, and a cassette operation 1434. The date 1431 indicates the date on which the cassette operation was performed. The time 1432 indicates the time at which the cassette operation was performed.

[0177] Cassette 1433 indicates information about the location of the cassette that was operated. Cassette operation 1434 stores information about "cassette closed" when an operation to close the cassette is performed. Also, when an operation to change the media is performed, "media change" and the changed paper size and paper type are stored. A predetermined number of pieces of data (for example, up to 300 pieces) are stored as cassette history information.

[0178] The above data shown in Fig. 25 is used to display the cassette history list 912 in Fig. 17. Note that the cassette operation data is not limited to cassette operation, and manual feed operation data may also be saved.

[0179] <Processing performed by the image processing device> 26 to 28 are flowcharts showing an example of the display process of the top screen (FIG. 4) including the startup process of the status monitor. A program (for example, firmware) that realizes this process is stored in the HDD 204 of the image processing device 103, called into the RAM 202, and executed by the CPU 201.

[0180] This process is started when the CPU 201 receives an input of a special command to start the status monitor from a service person via the operation unit 212. In S1501, the CPU 201 refers to device configuration information (not shown) of the image processing device stored in the RAM 202.

[0181] In step S1502, the CPU 1501 determines the cross-sectional view to be displayed on each screen. For example, the cross-sectional view to be displayed changes depending on whether a scanner, a paper feed option, or a paper output option is installed.

[0182] When a common program is used among a plurality of image processing devices, the CPU 1501 may switch to a cross-sectional view suitable for the device model according to the device model information, since the positions of the paper transport path, parts, and jam sensors may differ depending on the device model.

[0183] In S1503, the CPU 201 refers to the part life history data shown in FIG.

[0184] In S1504, the CPU 201 determines whether or not there are any parts whose status level is "2" or higher as a result of the reference in S1503.

[0185] If the determination result in S1504 is NO, in S1505, the CPU 201 determines that there is no part life icon to be displayed in the cross-sectional view 401 in Fig. 4 and that "No notification" will be displayed in the notification area of ​​the part life 403. If the determination result is YES, in S1506, the CPU 201 obtains information on parts that require replacement and have a status level of "3" from the part life history data.

[0186] In S1507, the CPU 201 acquires information on parts recommended for replacement with a condition level of "2" from the part life history data. The order of S1506 and S1507 may be reversed.

[0187] In S1508, the CPU 201 displays the icons indicating the need for replacement and / or recommended replacement of the parts requiring notification, acquired in S1506 and S1507, at the corresponding coordinates on the cross-sectional view 401.

[0188] In S1509, the CPU 201 displays the parts requiring notification, acquired in S1506 and S1507, in descending order of priority. The priority is set such that parts requiring replacement (status level "3") are higher than parts recommended for replacement (status level "2"). In the case of parts with the same level, they are displayed in the order of number 1001 in FIG. 18.

[0189] In S1510, CPU 201 determines whether the number of parts to be notified is greater than the number of parts (e.g., three) that can be displayed in the notification area of ​​part life 403. If the determination result is NO, the process proceeds to S1512. If the determination result is YES, in S1511, CPU 201 displays the notifications that cannot be displayed with the characters "Other:" and the number of notifications.

[0190] In S1512, the CPU 201 refers to the trouble detection history data shown in FIG.

[0191] In S1513, the CPU 201 determines, as a result of the reference in S1512, whether or not there is a problem with the optical unit where the contamination level is "2" or higher and / or there is a cassette abnormality.

[0192] If the determination result is NO, in S1514, the CPU 201 determines that there is no trouble detection icon to be displayed on the cross-sectional view 401 in FIG. 4 and that "No notification" is to be displayed in the notification area of ​​the trouble detection 404.

[0193] If the determination result is YES, in S1515, the CPU 201 acquires information on optical units with a contamination level of "3" and / or cassettes with abnormalities from the trouble detection history data.

[0194] In S1516, the CPU 201 acquires information about optical units whose status level is “2” from the trouble detection history data. The order of S1515 and S1516 may be reversed.

[0195] In S1517, the CPU 201 displays the icons indicating that check is required and / or that check is recommended for the trouble requiring notification, which were acquired in S1515 and S1516, at the corresponding coordinates on the cross-sectional view 401.

[0196] In S1518, the CPU 201 displays the troubles that require notification, acquired in S1515 and S1516, in descending order of priority. The priority is set such that check required (soil level "3") is higher than check recommended (soil level "2"), and if the levels are the same, the troubles are displayed in the order of number 1101 in FIG. 19.

[0197] In S1519, CPU 201 determines whether the number of troubles to be notified is greater than the number of troubles (e.g., three) that can be displayed in the notification area of ​​trouble detection 404. If the determination result is NO, the process proceeds to S1521. If the determination result is YES, in S1520, CPU 201 displays the notifications that cannot be displayed with the text "Other:" and the number of notifications.

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

[0199] In S1522, the CPU 201 determines, as a result of the reference in S1521, whether or not there is a currently occurring error for which the recovery time 1205 in FIG. 20 is not registered.

[0200] If the determination result is NO, in S1523, it is determined to display "No notification" in the notification area of ​​the error 405. If the determination result is YES, in S1524, the CPU 201 obtains information about the currently occurring error for which the recovery time 1205 is not registered from the error history data.

[0201] In step S1525, the CPU 201 displays the errors that require notification, acquired in step S1524, in descending order of acquisition.

[0202] In S1526, CPU 201 determines whether the number of errors to be notified is greater than the number of errors (for example, two) that can be displayed in the notification area of ​​error 405. If the determination result is NO, the process proceeds to S1528. If the determination result is YES, in S1527, CPU 201 displays the notifications that cannot be displayed with the text "Other:" and the number of notifications.

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

[0204] In S1529, the CPU 201 determines, as a result of the reference in S1528, whether there is a currently occurring jam for which the jam recovery time 1306 in FIG. 21 is not registered, or whether there is a frequent jam with the cumulative number 1307 of 10 or more.

[0205] If the determination result is NO, in S1530, the CPU 201 determines that there is no jam icon to be displayed in the cross-sectional view 401 of Fig. 4 and that "No notification" is to be displayed in the notification area of ​​the jam 406. If the determination result is YES, in S1531, the CPU 201 obtains information about an occurring jam for which the recovery time 1306 is not registered from the jam history data.

[0206] In S1532, the CPU 201 acquires information on frequent jams where the cumulative number 1307 is 10 or more from the jam history data. The order of S1531 and S1532 may be reversed. Note that if multiple pieces of data with the same jam code are registered in the jam history data in Fig. 21, the latest piece of information is acquired.

[0207] In step S1533, the CPU 201 displays the icons indicating that a jam is occurring and / or that there are many jams that require notification, which were acquired in steps S1531 and S1532, at the corresponding coordinates on the cross-sectional view 401.

[0208] In S1534, the CPU 201 displays the jams that require notification, acquired in S1531 and S1532, in descending order of priority. Current jams are set higher in priority than frequent jams. If the priority levels are the same, the information is displayed in descending order of acquisition, for example. Furthermore, if there is a jam that is both current and frequent, the information about the current jam is displayed first.

[0209] In S1535, the CPU 201 determines whether the number of jams to be notified is greater than the number of jams (for example, two) that can be displayed in the notification area of ​​the jam 406. If the determination result is NO, the process proceeds to S1537. If the determination result is YES, in S1536, the CPU 201 displays the notifications that cannot be displayed with the characters "Other:" and the number of notifications.

[0210] In S1537, CPU 201 displays the display content determined in S1501 to S1536 on the screen of operation unit 212. That is, top screen 400 of the status monitor in FIG. 4 is displayed.

[0211] 26 to 28, the abnormality of the image processing device 103 and the location of the abnormality that the on-site service person wants to check urgently can be displayed in the cross-sectional view 401 and the notification area (403 to 406). This allows the service person to know the whole picture of the abnormality of the image processing device and the location of the abnormality on a single screen of the top screen 400.

[0212] As a result, the efficiency of the work of checking abnormalities by service personnel who are required to respond quickly on site is improved. Furthermore, the service personnel can also consider efficient subsequent work procedures, such as identifying a location where two or more abnormalities are concentrated from the cross-sectional view 401 and working on the concentrated abnormalities together.

[0213] Furthermore, the service technician can also estimate the correlation between the occurrence of multiple abnormalities from the relative positions of the abnormality locations on the cross-sectional view 401. For example, if a notification that cassette roller 1 needs to be replaced and a notification that frequent jams have occurred nearby are received at the same time, in a similar time period, or in a similar time period, it can be determined that there is a high possibility that frequent jams will be resolved by replacing cassette roller 1.

[0214] In this embodiment, the display can be switched between information about abnormalities in the status information (for example, any one of FIGS. 6, 8, 10, and 12) and information about the usage status (for example, any one of FIGS. 14 to 17).

[0215] This allows the service technician to easily compare and confirm information about the abnormality with, for example, information about usage conditions related to the abnormality. In other words, the information necessary for maintenance work on the image processing device 103 can be efficiently displayed within a limited screen area, improving the work efficiency of the service technician.

[0216] Next, an example of screen transition processing in response to an operation in which a service technician operates the operation unit 212 to switch between the screens shown in Figures 4 to 17 after the top screen 400 of the status monitor is displayed will be described. Figures 29 to 31 are flowcharts showing this processing. A program (for example, firmware) that realizes this processing is stored in the HDD 204 of the image processing device 103, called into the RAM 202, and executed by the CPU 201.

[0217] This process is started when the CPU 201 receives an input from a service technician via the operation unit 212 while the screens of FIGS. 4 to 17 are displayed on the operation unit 212.

[0218] When the CPU 201 detects that a button on the screen has been pressed, in S1601 it determines which button shown in FIGS. 4 to 17 has been pressed.

[0219] First, we will explain the case where the pressed button is the notification area of ​​part lifespan 403 or part lifespan button 502. If the button pressed in S1601 is the notification area of ​​part lifespan 403 or part lifespan button 502, the determination result in S1601 is "part lifespan," and the process proceeds to S1602.

[0220] In S1602, the CPU 201 refers to the part life history data shown in FIG.

[0221] In S1603, the CPU 201 displays the part life screen 500 of Fig. 6 on the operation unit 212 in accordance with the part life history data referenced in S1602. At this time, an icon corresponding to the abnormality related to the part life determined in S1508 of Fig. 26 is displayed on the cross-sectional view 401.

[0222] Other icons (icons corresponding to abnormalities related to trouble detection or jams) are not displayed. Also, the parts list 507 displays the status of all parts listed in the part life history data shown in FIG.

[0223] After the parts lifespan screen 500 is displayed in S1603, when the CPU 201 detects that a button on the screen has been pressed, it determines in S1604 which button on the parts lifespan screen 500 has been pressed.

[0224] If the button pressed in S1604 is the detailed status button 508, the determination result in S1604 is "detailed status", and the process proceeds to S1605.

[0225] In S1605, the CPU 201 refers to the history data 1003 (that is, data used to create a graph) of the state of the part selected in the parts list 507 from the history data of the part lifespan shown in FIG.

[0226] In S1606, the CPU 201 creates a graph of the status value [%] according to the time series of dates in the status history data 1003 referenced in S1605, and displays the status details screen 510 in Fig. 7. At this time, data for the display period specified in the display period 512 is displayed as a status transition graph 511. After the status details screen 510 is displayed, the close button 513 is pressed to return to the part life screen 500 (not shown). Thereafter, the process returns to waiting for a determination in S1601.

[0227] If the button pressed in S1604 is other than the detailed status button 508, the determination result in S1604 is "other", and the process proceeds to S1601 to determine which of the buttons 501 to 506 was pressed.

[0228] Next, a description will be given of the case where the pressed button is in the notification area of ​​trouble detection 404 or the trouble detection button 503. If the pressed button in S1601 is in the notification area of ​​trouble detection 404 or the trouble detection button 503, the determination result in S1601 is "trouble detected," and the process proceeds to S1607.

[0229] In S1607, the CPU 201 refers to the trouble detection history data shown in FIG.

[0230] In S1608, the CPU 201 displays the trouble detection screen 600 of Fig. 8 on the operation unit 212 in accordance with the trouble detection history data referenced in S1607. At this time, an icon corresponding to the abnormality related to the trouble detection determined in S1517 of Fig. 27 is displayed on the cross-sectional view 401.

[0231] Other icons (icons corresponding to abnormalities related to part life or jams) are not displayed. Also, the trouble list 601 displays the status of all troubles listed in the trouble detection history data shown in FIG.

[0232] After the trouble detection screen 600 is displayed in S1608, when the CPU 201 detects that a button on the screen has been pressed, it determines in S1609 which button on the trouble detection screen 600 has been pressed.

[0233] If the button pressed in S1609 is the dirt details button 602, the determination result in S1609 is "dirt details," and the process proceeds to S1610. In S1610, the CPU 201 refers to the trouble history data 1103 (i.e., data used to create a graph) of the optical unit selected in the trouble list 601 from the trouble detection history data shown in Fig. 19.

[0234] In S1611, the CPU 201 creates a graph of the dirt level [%] according to the time series of dates in the trouble history data 1103 referenced in S1610, and displays the dirt details screen 610 of Fig. 9. At this time, data for the display period specified in the display period 612 is displayed as a dirt transition graph 611. After the dirt details screen 610 is displayed, the close button 613 is pressed to return to the trouble detection screen 600 (not shown). Then, the process returns to waiting for a judgment in S1601.

[0235] If the button pressed in S1609 is the treated button 603, the determination result in S1609 is "treated", and the process proceeds to S1612. In S1612, the CPU 201 executes a treated process for the trouble selected in the trouble list 601. If the trouble selected in the trouble list 601 is the optical unit, the CPU 201 resets the contamination level of the trouble history data 1103 to the initial value of "0".

[0236] If the trouble selected in the trouble list 601 is a cassette, the CPU 201 resets the abnormality detection in the trouble history data 1103 to the initial value of "none." Then, the CPU 201 displays the trouble detection screen 600 reflecting the latest trouble detection history data.

[0237] If the button pressed in S1609 is neither the stain details button 602 nor the treated button 603, the determination result in S1609 is “other.” In this case, the process proceeds to S1601 to determine which of the buttons 501 to 506 was pressed.

[0238] Next, a description will be given of the case where the pressed button is in the notification area for error 405 or the error button 504. If the pressed button in S1601 is in the notification area for error 405 or the error button 504, the determination result in S1601 is "error", and the process proceeds to S1613.

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

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

[0241] After the error screen 700 is displayed in S1614, if the CPU 201 detects that a button on the screen has been pressed, it determines in S1615 which button on the error screen 700 has been pressed.

[0242] If the button pressed in S1615 is the error details button 702, the determination result in S1615 is "error details," and the process proceeds to S1616. In S1616, the CPU 201 refers to detailed information (not shown) registered in the HDD 204 regarding the error code selected in the error list 701.

[0243] In S1617, CPU 201 uses the error information referenced in S1616 to display error details screen 710 of Fig. 11. After the error details screen 710 is displayed, the close button 714 is pressed to return to the error screen 700 (not shown). Thereafter, the process returns to waiting for a determination in S1601.

[0244] If the button pressed in S1615 is other than the error details button 702, the determination result in S1615 is “other.” In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0245] Next, a description will be given of the case where the pressed button is the notification area of ​​jam 406 or the jam button 505. If the pressed button in S1601 is the notification area of ​​jam 406 or the jam button 505, the determination result in S1601 is "jam", and the process proceeds to S1618.

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

[0247] In S1619, the CPU 201 displays the jam screen 800 of Fig. 12 on the operation unit 212 in accordance with the jam history data referenced in S1618. At this time, an icon corresponding to the jam-related abnormality determined in S1533 of Fig. 28 is displayed on the cross-sectional view 401.

[0248] Other icons (icons corresponding to abnormalities related to part life or trouble detection) are not displayed. Also, the jam list 801 displays only the most recent data for each jam code from the jam history data shown in Fig. 21. In other words, for data of the same jam code, only the most recent item is displayed in the jam list 801.

[0249] After the jam screen 800 is displayed in S1619, if the CPU 201 detects that a button on the screen has been pressed, then in S1620 it is determined which button on the jam screen 800 has been pressed. If the button pressed in S1620 is the jam details button 802, the determination result in S1620 is "jam details," and the process proceeds to S1621.

[0250] In S1621, the CPU 201 refers to the data that matches the jam code of the jam selected in the jam list 801 from the jam history data shown in FIG.

[0251] In S1622, the CPU 201 displays the jam details screen 810 of FIG. 13 using the data that matches the jam code referenced in S1621.

[0252] If the button pressed in S1620 is the reset button 803, the determination result in S1620 is "reset", and the process proceeds to S1623.

[0253] In S1623, the CPU 201 deletes the jam history data in Fig. 21 and updates the date and time of the reset date and time 804 (Fig. 12) to the date and time when the reset button was pressed. After that, the jam screen 800 reflecting the latest jam history data in Fig. 21 is displayed.

[0254] If the pressed button in S1623 is neither the jam details button 802 nor the reset button 803, the determination result in S1623 is “other.” In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0255] Next, a description will be given of the case where the pressed button is the usage status button 407 or the usage status button 506. If the pressed button in S1601 is the usage status button 407 or the usage status button 506, the determination result in S1601 is "usage status," and the process proceeds to S1624.

[0256] In S1624, CPU 201 determines which button was pressed on usage status screen 900 of Fig. 14 (to Fig. 17). The button selected as the initial value on usage status screen 900 is temperature button 901. Therefore, when transitioning from a screen other than usage status screen 900, the determination result in S1624 is "temperature," and processing proceeds to S1625.

[0257] In S1625, the CPU 201 refers to the temperature data stored in the HDD 204 and shown in FIG.

[0258] In S1626, the CPU 201 creates a temperature change graph 905 (FIG. 14) for the inside of the apparatus 1403 and the outside of the apparatus 1404 based on the temperature data referenced in S1625 in chronological order of the date 1401 and the time 1402. At this time, the CPU 201 creates a graph for the date specified by the date switching button 906. Then, the CPU 201 displays the temperature change screen of FIG. 14 on the operation unit 212.

[0259] In S1627, the CPU 201 determines which button was pressed on the temperature change screen of Fig. 14. If the button pressed in S1627 is the date change button 906, the determination result in S1627 is "date change", and the process proceeds to S1628.

[0260] In S1628, the date display is updated in accordance with the date switching performed by the date switching button 906. The CPU 201 also proceeds to S1626 and displays the temperature change graph 905 with the updated date data. If the button pressed in S1627 is other than the date switching button 906, the determination result in S1627 is "other," and the process returns to waiting for a determination in S1624.

[0261] If the button pressed in S1624 is the humidity button 902, the determination result in S1624 is "humidity", and the process proceeds to S1629. In S1629, the CPU 201 refers to the humidity data stored in the HDD 204 and shown in FIG.

[0262] In S1630, the CPU 201 creates a humidity change graph 907 (FIG. 15) for inside the apparatus 1413 and outside the apparatus 1414 based on the temperature data referenced in S1629 in chronological order of date 1411 and time 1412. At this time, the CPU 201 creates a graph for the date specified by the date switching button 908. Then, the CPU 201 displays the humidity change screen of FIG. 15 on the operation unit 212.

[0263] In S1631, the CPU 201 determines which button was pressed on the humidity change screen of Fig. 15. If the button pressed in S1631 is the date change button 908, the determination result in S1631 is "date change", and the process proceeds to S1632.

[0264] In S1632, the date display is updated in accordance with the date switching of the date switching button 908. The CPU 201 also proceeds to S1630 and displays the humidity change graph 907 with the updated date data. If the button pressed in S1631 is other than the date switching button 908, the determination result in S1631 is "other", and the process returns to waiting for a determination in S1624.

[0265] If the button pressed in S1624 is the print count button 903, the determination result in S1624 is "print count", and the process proceeds to S1633. In S1633, the CPU 201 refers to the print count data stored in the HDD 204 and shown in FIG.

[0266] In step S1634, the CPU 201 creates the print count graph 909 (FIG. 16) of the print count 1423 based on the print count data referenced in step S1633 in chronological order of the date 1421 and the time 1422.

[0267] When "Day" is selected with the display period switching button 910 in Fig. 16, a graph showing the number of printed sheets for one day is created in hourly increments. When "Month" is selected with the display period switching button 910, a graph showing the number of printed sheets for one month is created in daily increments. Then, the CPU 201 displays the number of printed sheets screen in Fig. 16 on the operation unit 212.

[0268] In S1635, the CPU 201 determines which button was pressed on the print count screen in Fig. 16. If the button pressed in S1635 is the display period switch button 910, the determination result in S1635 is "display period switch", and the process proceeds to S1636.

[0269] In S1636, the CPU 201 updates the display in accordance with the change in the month and date and period of the display period switching button 910. The CPU 201 also proceeds to S1634 and displays the print count graph 909 with the updated display period data. If the button pressed in S1635 is other than the display period switching button 910, the determination result in S1635 is "other," and the process returns to waiting for a determination in S1624.

[0270] If the button pressed in S1624 is the cassette history button 904, the determination result in S1624 is "cassette history", and the process proceeds to S1637. In S1637, the CPU 201 refers to the cassette operation data stored in the HDD 204 and shown in FIG.

[0271] In S1638, the CPU 201 creates a cassette history list 912 of the cassette operation data 1424 by sorting the cassette operation data referenced in S1637 in chronological order of the date 1431 and the time 1432. Here, the CPU 201 creates the cassette history list 912 by extracting data of the cassette selected by the cassette switching button 913 in FIG.

[0272] For example, since "cassette 1" is selected in the cassette switching button 913 in Fig. 17, the CPU 201 extracts the data of "cassette 1" in the cassette 1433 in Fig. 25 and creates the cassette history list 912. Then, the CPU 201 displays the cassette history screen in Fig. 17 on the operation unit 212.

[0273] In S1639, the CPU 201 determines which button was pressed on the cassette history screen of Fig. 17. If the button pressed in S1639 is the cassette switch button 913, the determination result in S1639 is "cassette switch", and the process proceeds to S1640.

[0274] In S1640, the CPU 201 updates the display in accordance with the cassette switching of the cassette switching button 913. The CPU 201 also proceeds to S1638 and displays the cassette history list 912 with the updated cassette data. If the button pressed in S1639 is other than the cassette switching button 913, the determination result in S1639 is "other", and the process returns to waiting for a determination in S1624.

[0275] If the button pressed in S1624 is other than the temperature button 901, humidity button 902, number of prints button 903, or cassette history button 904, the determination result in S1624 is "other." In this case, in the determination in S1601, it is determined which of the buttons 501 to 506 was pressed.

[0276] 6 to 17 include a return to top button 501. When the return to top button 501 is pressed, the determination in S1601 becomes "return to top," and the process proceeds to S1641.

[0277] In S1641, the CPU 201 executes the top screen display process of FIGS. 26 and 27, and displays the top screen 400.

[0278] Finally, a case where an operation (not shown) to end the status monitor is input on the screens of Figures 4 to 17 will be described. In S1601, when CPU 201 detects an operation to end the status monitor, the determination result of S1601 becomes "end." Then, in S1642, processing is executed to end the display of the status monitor.

[0279] 29 to 31, the service technician can transition from the top screen 400 in FIG. 4 to an information screen for each category (500, 600, 700, 800, or 900) to check detailed information. This allows the service technician to immediately display the information screen for each category from the top screen 400 and gather the information necessary for treatment.

[0280] In addition, by being able to move back and forth between these screens using buttons 502 to 506, service personnel can infer the cause of an abnormality from the related information on each screen and consider countermeasures based on that. Furthermore, service personnel can predict when an abnormality will occur in areas that have not yet reached an abnormality (mainly due to the end of part life and dirt on the optical unit) and make preparations for that.

[0281] In the above embodiment, when the display period of any one of the time series data displayed for each category is changed, the display period of at least one other time series data may also be changed in conjunction with the change, and the display may be switched.

[0282] For example, on the humidity change screen in Fig. 15, the date is changed to "2024 / 1 / 25" using the date change button 908. If the temperature button 901 is then selected to display the temperature change screen in Fig. 15, the date change button 906 on the temperature change screen also changes to "2024 / 1 / 25", and a temperature change graph 905 for "2024 / 1 / 25" is displayed.

[0283] Furthermore, if the error button 504 is selected, the error that occurred on "2024 / 1 / 25" will be displayed on the error screen 700 in Fig. 10. If no error occurred on "2024 / 1 / 25", an error for a nearby date (for example, the date closest to or before the specified date) may be displayed.

[0284] As a result, the service technician can check two or more pieces of time-series data in association with each other. The specific example of linking the display periods described above is an example of a display process in which the display periods of the first data and the second data are linked.

[0285] For example, the display units of the display periods of the graphs may be different between the two categories. For example, the control unit 301 can perform display processing such that the temperature change graph 905 (humidity change graph 907) displays the display period of one day in 10-minute units, while the print count graph 909 displays the display period of one day in 1-hour units.

[0286] Alternatively, the display unit 302 may have a function that allows the user to set the display unit and accept an operation to change the setting.

[0287] Of the time-series data displayed for each category, two or more pieces of time-series data may be displayed together. For example, in the case of graph-format data, "displaying together" means that graphs for two or more categories are displayed overlapping each other with the same display period.

[0288] For example, the temperature change graph 905 and the humidity change graph 907 can be superimposed and displayed, or the condition transition graph 511 and the dirt transition graph 611 can be superimposed and displayed. Alternatively, "displaying together" may mean, for example, that in the case of data in list format, lists for two or more categories can be displayed together as a single list.

[0289] For example, since there may be a correlation between the occurrence of a jam and the cassette operation history, the jam details list 813 and the cassette history list 912 can be displayed in chronological order in a single list. This allows the service technician to simultaneously check the cassette operations that were performed before and after the date and time of the jam occurrence.

[0290] Alternatively, "displaying together" means, for example, displaying two or more pieces of time-series data on one screen. For example, a humidity change graph 907 and a print count graph 909 can be displayed on one screen.

[0291] In the case where two or more pieces of time-series data are displayed together as described above, the display unit 302 may have a function to accept an operation to select whether to display them together or separately.

[0292] In the above embodiment, on the information screens for each category (500, 600, and 800), time-series data was displayed when a button for displaying time-series data as a separate screen (such as the status details button 508) was pressed (FIGS. 7, 9, and 13).

[0293] However, these time series data may be displayed superimposed on a part or all of the area of ​​the information screen for each category (500, 600, and 800) as in Figures 10, 14 to 17. Alternatively, conversely, the time series data shown in Figures 10, 14 to 17 may be displayed as a screen separate from the information screen for each category (700, 900).

[0294] In the above embodiment, for example, temperature and humidity are configured to be elements within the category of usage status, but for example, "environment" may be provided as a separate category of status information, and temperature and humidity may be configured to be elements within that category. In this case, for example, in Figures 4 and 6, "environment" may be provided as a status category, and when the "environment" button is pressed, a screen and button for displaying details of the temperature or humidity may be displayed.

[0295] <Other embodiments> Next, another embodiment of the present invention will be described. In this embodiment, the predicted date when the contamination on the optical unit will reach 100% is displayed on the contamination details screen shown in Fig. 9. Note that detailed description of the same configuration as the above-mentioned embodiment will be omitted.

[0296] Fig. 32 is a diagram showing another example of the dirt details screen of Fig. 9, which is displayed when the dirt details button 602 shown in Fig. 8 is pressed for the optical unit. Note that in Fig. 31, 610 to 613 are the same as in Fig. 9. In Fig. 32, predicted date information 1701 has been newly added to the screen of Fig. 9.

[0297] The predicted date information 1701 indicates the predicted date when the contamination of the optical unit is expected to reach a predetermined threshold (for example, 100%). That is, in this embodiment, in S1611 of Fig. 29, the CPU 201 predicts and displays, for example, the date when the contamination of the optical unit will reach 100% from the slope of the graph in Fig. 32 based on the trouble history data shown in Fig. 19. The period for making the prediction is within the range of history information stored as the trouble history data 1103 in Fig. 19.

[0298] At this time, CPU 201 functions as a control means for executing a control step of estimating the date and time when the degree of contamination of a predetermined part (scanner, drum, etc.) will exceed a predetermined threshold. Furthermore, when display of a trouble condition related to a predetermined part is selected, display unit 302 displays the date and time estimated by the control means. Furthermore, at this time, the degree of contamination of the predetermined part is displayed as a graph in chronological order.

[0299] 32 shows the predicted date when the optical unit is expected to be 100% dirty, but it is not limited to 100%. For example, it could be 90%. Also, it could be the predicted date when maintenance such as cleaning of a specific part such as the optical unit will be required. Also, it is not limited to the optical unit, but it could be the predicted date when a replacement part should be replaced, the predicted date when the replacement part's lifespan expires, or, instead of the predicted date, for example, the number of days remaining until the predicted date (remaining days) could be displayed.

[0300] In this manner, in this embodiment, the date and time when the degree of contamination of a specific part will reach a specific threshold is estimated, and when display of the trouble status for the specific part is selected, the estimated date and time is displayed, thereby enabling maintenance of the image processing device to be performed at the optimal date and time.

[0301] In this embodiment, the display of date and time includes, as described above, the predicted date when maintenance such as cleaning of specified parts will be required, the predicted date when replacement parts should be replaced, the predicted date when the life of the replacement parts will end, for example, the number of days remaining until the predicted date (remaining days), etc.

[0302] The present invention has been described in detail above based on its preferred embodiments, but the present invention is not limited to the above embodiments, and various modifications and combinations of the above embodiments are possible based on the spirit of the present invention, and these are not excluded from the scope of the present invention.

[0303] The present invention also includes those that realize the functions of the above embodiments using, for example, at least one processor such as a CPU, memory, or circuit (for example, ASIC). Also, multiple processors may be used to perform distributed processing.

[0304] In order to realize part or all of the control in the above-described embodiments, a computer program that realizes the functions of the above-described embodiments may be supplied to an image processing device or the like via a network or various storage media. Then, a computer (or a CPU, MPU, or the like) in the image processing device or the like may read and execute the program. In this case, the program and the storage medium storing the program constitute the present invention. The present invention also includes the following combinations.

[0305] (Configuration 1) An image processing device having a management means for managing the state of contamination of specified parts of the image processing device as numerical values ​​linked to date and time, a display means for displaying a list of trouble conditions that have occurred within the image processing device, and a control means for estimating the date and time when the degree of contamination of the specified parts will reach a specified threshold, wherein the display means displays the date and time estimated by the control means when display of the trouble condition related to the specified parts is selected.

[0306] (Configuration 2) The image processing device according to Configuration 1, wherein the display means displays the degree of dirt on the specified part in chronological order when displaying the trouble status related to the specified part is selected.

[0307] (Configuration 3) The image processing device according to configuration 1 or 2, wherein the predetermined parts include a scanner for reading a document.

[0308] (Configuration 4) The image processing device according to any one of configurations 1 to 3, wherein the predetermined part includes a drum for printing an image.

[0309] (Configuration 5) An image processing device described in any one of configurations 1 to 4, characterized in that the display means displays on a single screen: a first area that accepts an operation to switch between displaying first display information for displaying information regarding abnormalities in the image processing device and second display information for displaying information regarding the usage status of the image processing device; and a second area that switches between displaying either the first display information or the second display information by an operation on the first area.

[0310] (Method) An image processing method comprising a management step of managing the state of contamination of specified parts of an image processing device as numerical values ​​linked to date and time, a display step of displaying a list of trouble conditions that have occurred within the image processing device, and a control step of estimating the date and time when the degree of contamination of the specified parts will reach a specified threshold, wherein the display step displays the date and time estimated by the control step when display of the trouble condition related to the specified parts is selected.

[0311] (Program) A computer program for controlling each means of the image processing device according to any one of configurations 1 to 5 by a computer. [Explanation of symbols]

[0312] 103: Image processing device 201:CPU 202:RAM 203:ROM 204: HDD 212:Operation unit 304: History Management Department 1701: Forecast date information

Claims

1. a management means for managing the state of contamination of a predetermined part of the image processing device as a numerical value linked to a date and time; a display means for displaying a list of troubles occurring within the image processing device; a control means for predicting a date and time when the degree of contamination of the predetermined part will reach a predetermined threshold value; The image processing device is characterized in that the display means displays the date and time estimated by the control means when display of the trouble status related to the predetermined part is selected.

2. 2. The image processing apparatus according to claim 1, wherein said display means displays the degree of dirt on said predetermined part in chronological order when display of a trouble condition related to said predetermined part is selected.

3. 2. The image processing apparatus according to claim 1, wherein the predetermined parts include a scanner for reading an original.

4. 2. The image processing apparatus according to claim 1, wherein the predetermined part includes a drum for printing an image.

5. The display means a first area that accepts an operation to switch between displaying first display information for displaying information regarding an abnormality in the image processing device and displaying second display information for displaying information regarding a usage status of the image processing device; a second area for switching and displaying either the first display information or the second display information in response to an operation on the first area; 2. The image processing apparatus according to claim 1, wherein the image processing apparatus displays the above on one screen.

6. a management step of managing the state of contamination of a predetermined part of the image processing device as a numerical value linked to a date and time; a display step of displaying a list of troubles occurring within the image processing device; a control step of estimating the date and time when the degree of soiling of the predetermined part will reach a predetermined threshold value, The image processing method is characterized in that the display step, when display of the trouble status related to the predetermined part is selected, displays the date and time estimated by the control step.

7. A computer program for controlling each unit of the image processing apparatus according to any one of claims 1 to 5 by a computer.

Images