Image processing apparatus, method executed by image processing apparatus, and program product

Abstract

The invention provides an image processing apparatus, a method executed by the image processing apparatus, and a program product. The image processing apparatus has a display unit that manages state information and history information of the image processing apparatus, and performs processing based on the managed state information and history information. The processing includes displaying the display content in a single screen on the display unit based on the first display information and the second display information, the first display information is used for displaying abnormality-related information among state information and history information of the image processing apparatus for each category by dividing the abnormality-related information into a plurality of different categories, the second display information is used to display data corresponding to the abnormality-related information at a corresponding position on a schematic diagram of the image processing apparatus.

Description

Technical Field

[0001] This disclosure relates to a technique for displaying information in an image processing apparatus. Background Technology

[0002] When the image processing device malfunctions due to an issue that the user cannot resolve independently, service personnel will respond immediately. Additionally, service personnel will periodically visit users to maintain the image processing device. During emergency responses or regular visits, service personnel need to promptly assess the image processing device's status to take appropriate action, minimizing disruption to user operation. As a method for confirming the device's status, a standard service mode screen for service personnel displays component status, error history, paper jam history, etc., in a menu format. However, this requires service personnel to navigate between menus to obtain the necessary information, resulting in inefficient processing.

[0003] Japanese Patent Application Publication No. 2013-102350 discloses a means for displaying a status confirmation screen that integrates device errors and errors of various applications onto a single screen, as a method for confirming the status of an image processing device. While integrating the device status onto a single screen eliminates the hassle of moving back and forth between screens, the status confirmation screen in Japanese Patent Application Publication No. 2013-102350 does not provide sufficient information to service personnel. For example, service personnel need to identify the cause and determine appropriate measures by considering the location of the abnormality (error, paper jam, etc.), the positional relationship of multiple abnormalities, component status, error history, paper jam history, or the device's usage status (temperature, humidity, number of printed pages, etc.). Furthermore, as mentioned above, service personnel also need to complete the work efficiently in the shortest possible time.

[0004] As mentioned above, in a conventional menu format display, effort is required to provide on-screen navigation so that service personnel can obtain the required overall device status.

[0005] In contrast, methods that display device status on a single status confirmation screen, as described in Japanese Patent Application Publication No. 2013-102350, make it difficult for service personnel to determine the location relationship of two or more anomalies. If the two or more anomalies occur in close proximity, addressing them collectively would be more efficient. Summary of the Invention

[0006] This disclosure provides a technique for effectively displaying information required for the maintenance of an image processing device within a limited screen area.

[0007] An image processing apparatus having a display unit according to one aspect of this disclosure includes: a management unit for managing state information and historical information of the image processing apparatus; and a processing unit for processing based on the managed state information and historical information, wherein the processing based on the state information and historical information includes: displaying display content on the display unit in a single frame based on first display information and second display information, wherein the first display information is used to display abnormal information related to the state information and historical information of the image processing apparatus for each category by dividing abnormal information related to the image processing apparatus into different multiple categories, and the second display information is used to display data corresponding to the abnormal information related to the image processing apparatus at corresponding positions on a schematic diagram of the image processing apparatus. Further features of the invention will become apparent from the following description of embodiments with reference to the accompanying drawings. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating the construction of a system including an image processing apparatus according to an embodiment.

[0009] Figure 2 This is a block diagram illustrating the hardware structure of an image processing device.

[0010] Figure 3 This is a block diagram illustrating an example of processing functionality, which demonstrates functions relevant to this embodiment.

[0011] Figure 4 This is an example of the top screen displayed when there is an malfunction in the image processing device.

[0012] Figure 5 This is an example diagram showing the top screen when there are no abnormalities in the image processing device.

[0013] Figure 6 This is a diagram showing the lifespan of a component.

[0014] Figure 7 This is an image showing the status details screen.

[0015] Figure 8 This is a diagram showing the fault detection screen.

[0016] Figure 9 This is an image showing details of the pollution.

[0017] Figure 10 This is an image showing an error message.

[0018] Figure 11 This is an image showing the error details screen.

[0019] Figure 12 It is an image showing the paper jam screen.

[0020] Figure 13 This is an image showing the details of the cardstock.

[0021] Figure 14 It is a diagram showing the temperature change.

[0022] Figure 15 This is a diagram showing changes in humidity.

[0023] Figure 16 This is a diagram showing the number of sheets to be printed.

[0024] Figure 17 This is an image showing the history of ink cartridges.

[0025] Figure 18 Historical data used to display component lifespan information is shown.

[0026] Figure 19 Historical data used to display fault detection information is shown.

[0027] Figure 20 This displays historical data used to show error messages.

[0028] Figure 21 This displays historical data used to show information from the paper jam.

[0029] Figure 22 The temperature data used to display temperature change information is shown.

[0030] Figure 23 The display shows humidity data used to show humidity change information.

[0031] Figure 24 This displays the number of printed sheets used to show the number of printed sheets.

[0032] Figure 25 This displays ink cartridge operation data used to show historical information about the ink cartridges.

[0033] Figure 26 This is a flowchart illustrating an example of the display process of the top screen that includes the startup process of the status monitor.

[0034] Figure 27 It is shown Figure 26 The flowchart continues.

[0035] Figure 28 It is shown Figure 27 The flowchart continues.

[0036] Figure 29 It shows the basis Figures 4 to 17 The flowchart shows an example of screen transition processing for screen switching operations.

[0037] Figure 30 It is shown Figure 29 The flowchart continues.

[0038] Figure 31 It is shown Figure 30 The flowchart continues. Detailed Implementation

[0039] The embodiments of the present invention will be described in detail below. Please note that the embodiments described below are merely examples of implementing the present invention and should be appropriately modified or adjusted according to the construction of the device to which the present invention is applied and various conditions; the present invention is not limited to the embodiments described below. Furthermore, in all the accompanying drawings, components with the same function are represented by the same reference numerals, and repeated descriptions thereof are omitted.

[0040] <System Structure>

[0041] Figure 1 This diagram illustrates the configuration of a system including an image processing apparatus according to an embodiment. The system of this embodiment includes an image processing apparatus 103, a server PC (personal computer) 101, and a client PC 102. These image processing apparatus 103, server PC 101, and client PC 102 are interconnected via a network.

[0042] The network is a communication network implemented using any or a combination of, for example, LAN, WAN, telephone lines, dedicated digital lines, ATM, frame relay lines, cable television lines, and wireless lines for data broadcasting. Multiple image processing devices 103 can be installed in a single local area.

[0043] Image processing device 103 is a multi-functional peripheral device (MFP). That is, image processing device 103 is equipped with printing, copying, faxing, and scanning functions. Image processing device 103 not only has the function of copying paper originals, but also the function of printing print data sent from an external printer driver. In addition, image processing device 103 also has the function of reading paper originals and sending their image data to an external file server or email address (SEND function). Furthermore, image processing device 103 also has functions such as sending data to other image processing devices and printing on the destination image processing device (remote copying function, faxing function).

[0044] Although the image processing device 103 is connected via Ethernet (not shown), this connection is merely illustrative. All information processing devices (server PC 101, client PC 102) other than the image processing device 103 can be comprised of a single computer. Alternatively, the system can be constructed independently of the image processing device 103 by incorporating the information processing devices into it. The information processing device used in this embodiment does not necessarily have to be a PC, but can be a terminal device other than a PC or smartphone. The printing method of the image processing device 103 used in this embodiment can be an electrophotographic method, an inkjet method, or other methods.

[0045] <Hardware Structure of Image Processing Devices>

[0046] Figure 2 This is a block diagram showing the hardware structure of the image processing apparatus 103. The image processing apparatus 103 is equipped with a controller unit 200, an operation unit 212, various sensors 255, a scanner 270, and a printer 295.

[0047] The controller unit 200 is connected to the scanner 270, which is an image input device, and the printer 295, which is an image output device, and performs input and output of image information and device information by connecting to Ethernet and a public line.

[0048] The controller unit 200 includes a CPU 201, RAM 202, ROM 203, HDD (hard disk drive) 204, and an operation unit I / F 206. Additionally, the controller unit 200 has a network I / F 210, a modem 250, SRAM 209, a graphics bus I / F 205, and an RTC (real-time clock) 211. All these units are connected to the system bus 207.

[0049] Furthermore, the controller unit 200 includes 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 / expansion unit 240. These units are all connected to the image bus 208.

[0050] CPU 201 is a controller that controls the image processing device 103. RAM 202 is the system working memory for the CPU 201 to run, and also an image memory used for temporary storage of image data. ROM 203 is a boot ROM that stores the system's boot program. HDD 204 stores system software, applications, and image data.

[0051] It should be noted that the implementation is not limited to CPU 201, and PLDs (Programmable Logic Devices) such as FPGAs (Field-Programmable Gate Arrays) can be used. Alternatively, ASICs (Application-Specific Integrated Circuits) or DSPs (Digital Signal Processors) can be used. Furthermore, devices with storage media other than HDD 204 can be used. Storage media other than HDD 204 include, for example, flash memory, SSDs (Solid State Drives), optical storage media, or magneto-optical storage media.

[0052] Operation unit I / F 206 is an interface unit that engages with operation unit 212, which includes a touch panel, and outputs image data to be displayed to operation unit 212. Additionally, operation unit I / F 206 transmits information input by the user from operation unit 212 to CPU 201. Network I / F 210 is connected to a network and performs information input and output.

[0053] The modem 250 is connected to a public line and performs information input and output. The SRAM 209 is a non-volatile storage medium capable of high-speed operation. The RTC 211 can continue counting the current time even when the controller unit 200 is not powered.

[0054] Image bus I / F 205 is a bus bridge connecting system bus 207 and image bus 208 for high-speed image data transmission. This bus bridge performs data structure conversion. Image bus 208 is constructed, for example, by a PCI bus or IEEE 1394.

[0055] RIP 260 expands PDL code into bitmap images.

[0056] Device I / F 220 connects to various sensors 255 and acquires the status of the image processing device. Additionally, device I / F 220 connects scanner 270 and printer 295 to controller unit 200 and performs switching between synchronous and asynchronous systems for image data.

[0057] The scanner image processing unit 280 corrects, processes, and edits the input image data. The printer image processing unit 290 corrects (printer calibration), performs resolution conversion, etc., on the printed output image data. The image rotation unit 230 rotates the image data. The image compression / expansion unit 240 compresses and expands the image.

[0058] <Software Structure of Image Processing Devices>

[0059] Figure 3 This is a block diagram illustrating an example of processing functions, which demonstrate functions related to this embodiment in various units of the image processing apparatus 103. For example... Figure 2 As described below, the functions of the functional units described below, as well as the processing related to the flowcharts described later, are implemented by the CPU 201 executing all or part of the program on RAM 202 based on the program stored in ROM 203.

[0060] Display unit 302 displays the status of image processing device 103 and the operation menu on operation unit 212. Input unit 303 receives operation commands from the user. History management unit 304 processes information and stores the status information and history (usage history) information of image processing device 103 in a history database. History management unit 304 is an example of a management unit that manages the status information and history information of image processing device. Control unit 301 controls display unit 302, input unit 303, and history management unit 304. Control unit 301 (mainly CPU 201, etc.) is an example of a processing unit that processes the status information and history information managed by the management unit.

[0061] <Screen Construction According to the Embodiment>

[0062] Next, we will refer to Figures 4 to 15 The status monitoring screen used to display the status and history of the image processing device 103 to service personnel will be described. Although the status monitoring screen is displayed on the operation unit 212 of the image processing device 103, it is not intended for ordinary users and is therefore activated only through special operations. Figures 4 to 15 All screen data described herein are displayed based on data recorded in the history management unit 304.

[0063] Figure 4 This is an example of a top screen 400 showing the image processing device 103 in the event of an malfunction. The display unit 302 displays the location and type of the malfunction by mapping icons (icon images) on the cross-sectional view 401 of the image processing device. Cross-sectional view 401 is an example of a schematic diagram of the image processing device. The paper feed path is also shown in cross-sectional view 401, allowing service personnel to understand whether the malfunction might affect the use of the image processing device's main functions, such as scanning and printing. Although the paper feed path is shown with dashed lines in cross-sectional view 401, other lines or graphics could also be used to represent the paper feed path.

[0064] Figure 402 illustrates the types and contents of the icons mapped and displayed on sectional view 401. These types indicate whether there are parts that need to be replaced due to aging, whether there is a malfunction that requires inspection, or whether there are locations where paper jams are occurring or occur frequently. The abnormal information (content, type, etc.) and the coordinates of the abnormal location on sectional view 401 are predetermined in a one-to-one or many-to-one relationship.

[0065] In the top screen 400, the display unit 302 displays anomaly-related information from the image processing device's status information and historical information by dividing anomaly-related information into multiple different categories and displaying the anomaly-related information for each category. The multiple categories include, for example, component lifespan 403, fault detection 404, error 405, paper jam 406, and usage status (usage status button) 407. In this embodiment, among these categories, the anomaly-related information for the status is categorized as component lifespan 403, fault detection 404, error 405, and paper jam 406. In contrast, for the history, in this top screen 400, the history is displayed as the category labeled "usage status" (usage status button) 407. Furthermore, as described later, the history is displayed in multiple categories in a different screen than the top screen 400.

[0066] The areas displaying component lifespan 403, fault detection 404, error 405, and paper jam 406 are all notification areas that display (notify) information related to the abnormalities occurring in the image processing device 103. These notification areas include buttons for switching to a details screen, and for example, the entire notification area serves as an operation area for accepting actions from the user.

[0067] Although the usage status button 407 is an operation area for accepting actions from the user, it does not have a notification area. The usage status button 407 includes functionality for accepting actions to display usage status (history information) categorized into multiple classes, as described later. Figures 14 to 17 Additionally, for usage status, predetermined criteria can be established to identify anomalies, and the following structure can be adopted: a top screen 400, similar to other notification areas, notifies information related to these anomalies.

[0068] The display information related to various categories such as component lifespan 403, fault detection 404, error 405, paper jam 406, and usage status button 407 is an example of the first display information. In contrast, the display information of icons mapped onto the cross-sectional view 401 is an example of the second display information. Thus, the display content based on the display information of each notification area (and the usage status button 407) and the display information of icons on the cross-sectional view 401 (which may include legend 402) will be displayed as a single screen (i.e., top screen 400).

[0069] Because the displayable content in each notification area is limited by the screen area, exceptions are displayed sequentially from top to bottom, starting with the highest priority exceptions. If not all exceptions can be displayed, the remaining number of exceptions will be displayed as "Other". That is, in the exception-related information, a predetermined number of one or more display objects and one or more non-display objects that cannot be fully displayed in a single screen will be displayed together. For non-display objects, only their quantity is displayed. Although the predetermined number of display objects may be, for example, two or three, the predetermined number of display objects can be one, or it can be four or more. In contrast, in section view 401, icons indicating display objects and icons indicating non-display objects are displayed simultaneously.

[0070] Additionally, in the top screen 400, under the abnormality-related information section, information about abnormalities in the image processing device 103 that cannot be located and are not shown in the cross-sectional view 401 can also be displayed. Such abnormality information in the image processing device 103 that cannot be located includes, for example, system errors. This type of abnormality information that cannot be located can be notified as error 405, or it can be notified as another category (i.e., different categories not described here).

[0071] Prioritize anomaly-related information and predetermine the priority order. Anomaly-related information may include anomalies that require handling and anomalies that are recommended to be handled. Anomalies that require handling have a higher priority than anomalies that are recommended to be handled. For example, for the priority of component life 403, "replacement required" is set higher than "replacement recommended." When the priorities are the same, their order follows the arrangement of the component life screen described later.

[0072] For the priority of fault detection 404, "Need to check" is set higher than "Recommended check", and in the case of the same level, their order follows the arrangement order of the fault detection screens described later.

[0073] Error 405 is displayed in descending order of date and time. While you can prioritize errors 405 by date and time in descending order, you can also prioritize them by date and time in ascending order. Alternatively, you can set the priority based on other criteria.

[0074] For the paper jam 406 priority, "Paper jam occurred" (an anomaly requiring attention) is set higher than "Frequent paper jams" (an anomaly recommended for attention), and when the priorities are the same, they are displayed in descending order of occurrence date and time, similar to the paper jam screen described later. Additionally, the priority of anomaly-related information in each category can be set to level three or higher.

[0075] exist Figure 4 In the example, component lifespan 403 indicates, via an icon corresponding to illustration 402, that drum unit Y needs replacement, and that the replacement times for drum units M and C are approaching (replacement recommended). That is, the icon images differ according to priority. Additionally, component lifespan 403 indicates in "Others" that a component's lifespan limit (i.e., usage period) is approaching. Pressing the notification area for component lifespan 403 (or the strip button labeled "Component Lifespan" at the top of the notification area) will transition to the component lifespan screen, described later.

[0076] In the case where there are multiple pieces of information related to anomalies corresponding to the same location on section view 401, the icon corresponding to the anomaly with the highest priority is displayed.

[0077] exist Figure 4 In the example, fault detection 404 is illustrated with two scenarios that require checking and one scenario that is recommended to be checked. Pressing the notification area of ​​fault detection 404 or the button at the top of that notification area will transition to the fault detection screen, which will be described later.

[0078] exist Figure 4 In the example, error 405 is indicated by icons representing two errors occurring. Because many system-related errors cannot be located at a specific point in the cross-sectional view, icons are not displayed for error 405. Pressing the notification area for error 405 or the button at the top of that notification area will transition to the error screen described later.

[0079] exist Figure 4 In the example, paper jam 406 is indicated by icons to show a single paper jam, a location where paper jams frequently occur, and two other notifications. Pressing the notification area of ​​paper jam 406 or the button at the top of that notification area will transition to the paper jam screen, which will be described later.

[0080] The usage status button 407 is used to switch to the usage status screen, which will be described later.

[0081] Figure 5This diagram illustrates an example of the top screen 400 when there is no anomaly in the image processing device 103. Since there is no anomaly, the icon of legend 402 is not displayed on cross-sectional view 401. "No notification" is displayed in each notification area (403 to 406), and service personnel can immediately see that there is no anomaly. Thus, because service personnel can obtain information from the top screen 400 regarding whether there is an anomaly in the entire image processing device, the location of the anomaly, and its content, they can identify locations that require immediate attention and begin work immediately. Furthermore, service personnel can consider efficient workflows, such as centrally processing anomalies located close to each other, as shown in cross-sectional view 401.

[0082] Figure 6 This diagram illustrates the Part Life screen 500 displayed when the "Part Life" 403 in the top screen 400 is pressed. At the top of the screen, a Return button 501, a Part Life button 502, a Fault Detection button 503, an Error button 504, a Paper Jam button 505, and a Usage Status button 506 are displayed as buttons for switching screens. The Return button 501 is used to return to the top screen. Pressing the Fault Detection button 503, the Error button 504, the Paper Jam button 505, or the Usage Status button 506 transitions to the respective detail screen. Since these buttons 501 to 506 are also displayed in the detail screens described later, service personnel can easily move back and forth between the detail screens. Therefore, it becomes easier to estimate the cause of the malfunction by comparing the information displayed on each screen.

[0083] Although the component life screen 500 also displays cross-sectional view 401 and legend 402, the display is limited to the component's icon as the icon to be displayed.

[0084] Parts list 507 displays a list showing the status of replaced parts. Each column of parts list 507 displays the part's "part name," "status," and "number of sheets used," indicating the number of sheets passed (used) after the part replacement. It should be clearly stated here that part status is not entirely equivalent to the concept of "status information" managed and displayed by category as described above; rather, part status refers to the information about the part status within the overall status information.

[0085] In the parts list 507, the "Status" is displayed as a four-level level indicator icon based on the component's status value. For example, the level indicator icon displays: Level "0" indicating an undefined state immediately after component replacement, Level "1" indicating a status value of 0% to 79%, Level "2" indicating a status value of 80% to 99%, and Level "3" indicating a status value of 100% or higher. Additionally, the current status value is also displayed numerically to the right of the level indicator. These status values ​​are preset so that the values ​​increase as the component deteriorates, and the value becomes 100% when replacement is required. Parameters used to calculate the status value include, for example, the number of sheets used after replacement, the current value of each component, and the resistance value.

[0086] When the status level is "2", the left side of the list displays a recommended replacement icon, indicating that the corresponding part is nearing the end of its lifespan. Figure 6 In the example, "Drum Unit M," "Drum Unit C," and "Cartridge Roller 1" are in a recommended replacement state. When the state value level is "3," the left side of the list displays an icon indicating that the corresponding component has reached its usage limit and needs replacement. Figure 6 In the example, "Drum Unit Y" is in a state that needs to be replaced.

[0087] When service personnel replace parts, the status value of the replaced part temporarily reverts to level "0," indicating no data, upon detecting the replacement. Therefore, the "Need Replacement" or "Recommended Replacement" icons for the replaced part will no longer be displayed in section view 401 and part list 507. Unlike the notification area for part lifespan 403 on the top screen 400, part list 507 displays all parts managed by the service personnel, regardless of whether an anomaly exists. Therefore, it is also possible to confirm the status values ​​of parts that do not yet require replacement. Part list 507 allows scrolling up and down to display the status of all parts.

[0088] The Status Details button 508 is used to switch to a screen that displays the status value changes of the selected component in the component list 507 in graphical form.

[0089] Figure 7 The status details screen 510 is displayed by pressing the status details button 508. The status transition chart 511 shows the daily change of the selected component's status value. A reference line is displayed at 100%, indicating when the component needs to be replaced. The display period 512 is a drop-down menu for toggling the display period of the chart between 30 days and 180 days. The display period 512 is not limited to 30 days and 180 days. The close button 513 serves as a button to close the status details screen 510 and return to the component lifespan screen 500.

[0090] exist Figure 7In the example, graph 511 showing the state transition of "Drum Unit Y" in component lifespan screen 500 is displayed, showing the daily transitions until a state value exceeding 100% is reached. This allows service personnel to estimate whether degradation is progressing as assumed, or whether component degradation is progressing rapidly due to component defects or environmental changes. Although Figure 7 The example illustrates a situation where the condition value exceeds the component's usage limit. Even for components that haven't yet reached their usage limit, service personnel can predict approximately how many days it will take for the component to reach its limit based on the slope of the graph. This allows service personnel to determine whether a replacement part needs to be brought on the next visit and to be prepared for its replacement.

[0091] Figure 8 A diagram showing a fault detection screen 600 is provided, which is displayed by pressing the fault detection button 404 on the top screen 400 or by pressing the fault detection button 503 on each detail screen. Buttons 501 to 506 arranged at the top of the screen have... Figure 6 Buttons 501 to 506 shown have similar functions.

[0092] Although the fault detection screen 600 also displays cross-sectional view 401 and legend 402, the icons displayed on this screen are limited to those indicating whether a fault check is required.

[0093] Fault List 601 displays a list of fault objects and their contents that frequently require service personnel intervention. The "ADF Optical Unit Contamination" and "Reader Optical Unit Contamination" displays information indicating whether cleaning of the optical unit is necessary. ADF is an abbreviation for Automatic Document Feeder. For example, the contamination level of a reflector is detected based on the value of reflected light obtained from an optical sensor, etc. Similar to the status values ​​and status levels of the aforementioned components, the contamination degree [%] (the reference value for requiring cleaning is set to 100%) and contamination level (including an icon for a four-level contamination level meter) are displayed. Based on this contamination level or contamination level meter, information indicating whether action is required is displayed.

[0094] Specifically, for example, if no contamination level is defined, the icon for level "0" is displayed. If the contamination level is 0% to 79%, the icon for level "1" is displayed. If the contamination level is 80% to 99%, the icon for level "2" is displayed. If the contamination level is above 100%, the icon for level "3" is displayed. In the case of contamination level "2", a recommended check icon indicating recommended cleaning is displayed at the left end of the list. In the case of contamination level "3", a mandatory check icon indicating mandatory cleaning is displayed at the left end of the list.

[0095] Additionally, the messages related to objects / content in fault list 601 vary according to level. For example, level "0" displays "No Data," level "1" displays "Good," level "2" displays "Contamination," and level "3" displays "Severe Contamination." For contamination of the optical unit, select an object in fault list 601 and press the contamination details button 602 to confirm a graph showing the changes in contamination level (more on this later). Figure 9 (This is explained in the text).

[0096] In fault list 601, the ink cartridge malfunction section displays whether there are any abnormalities in each ink cartridge and its contents. Ink cartridge malfunctions are primarily identified by detecting misalignment of the paper adjustment plate (guide rail) within the cartridge. If an ink cartridge malfunction is detected, the list displays the message "Confirmation Required"; if no malfunction is detected, the list displays the message "None".

[0097] The "Processed" button 603 is a button that can be pressed when the optical unit or ink cartridge is in a "Check Required" or "Check Recommended" state. When a service technician selects the target optical unit from the fault list 601 after cleaning the optical unit and presses the "Processed" button 603, the contamination level returns to "0". As a result, the "Check Required" or "Check Recommended" icon will no longer be displayed in the cross-sectional view 401 and the fault list 601. Additionally, when a service technician selects the target ink cartridge from the fault list 601 after confirming the ink cartridge and presses the "Processed" button 603, the display will return to "No Abnormalities". As a result, the "Check Required" icon will no longer be displayed in the cross-sectional view 401 and the fault list 601.

[0098] Figure 9 This is a diagram showing the contamination details screen 610 displayed by pressing the contamination details button 602 for the optical unit. The contamination transition chart 611 shows the daily change in the contamination level of the selected optical unit in the fault list 601. A reference line is displayed at 100%, indicating when cleaning is needed. Display period 612 is a drop-down menu for switching the display period of the chart between 30 days and 180 days. The close button 613 is a button for closing the contamination details screen 610 and returning to the fault detection screen 600.

[0099] exist Figure 9 The example shows a contamination chart 611 for "Reader Optical Unit Contamination" in the fault detection screen 600, and the daily progression up to the recommended check at 81% contamination level can be seen. Based on the slope of the chart, service personnel can predict approximately how many days are needed for cleaning. Accordingly, service personnel can determine whether cleaning tools need to be brought on the next visit and can prepare the necessary cleaning tools.

[0100] Figure 10This diagram illustrates an error screen 700 displayed by pressing the error button 405 on the top screen 400 or by pressing the error button 504 on each detail screen. The buttons 501 to 506 arranged at the top of the screen have... Figure 6 and Figure 8 Buttons 501 to 506 shown have similar functions.

[0101] Error list 701 displays a list of errors that have occurred in the image processing device 103. Error list 701 displays the date, time, and recovery time of each error, along with the error code and its title. Errors in the first and second rows that do not display a recovery time indicate errors that are currently occurring. For example, by selecting an object in error list 701 and pressing the error details button 702, detailed information about the selected object's error can be viewed.

[0102] Figure 11 This diagram illustrates the error details screen 710 displayed by pressing the error details button 702. Error code 711 indicates the error code identifying the selected error. Error message 712 displays the error title, description, and handling method. Page up / down buttons 713 are used to switch pages when the error message includes multiple pages. Close button 714 is used to close the error details screen 710 and return to the error screen 700. Service personnel can view the currently occurring error and its details from this screen.

[0103] Figure 12 This diagram illustrates a paper jam screen 800 displayed by pressing the paper jam button 406 on the top screen 400 or by pressing the paper jam button 505 on each detail screen. The buttons 501 to 506 arranged at the top of the screen have... Figure 6 , Figure 8 and Figure 10 Buttons 501 to 506 shown have similar functions.

[0104] Although the paper jam screen 800 also displays cross-sectional view 401 and legend 402, the icons displayed are limited to those indicating the current paper jam or the paper jam that occurs frequently.

[0105] Paper jam list 801 displays a paper jam history list. Paper jam list 801 displays the date, time, and recovery time of each paper jam, along with the paper jam code, paper jam type, sensor number, and the cumulative number of times the same paper jam code is recorded. Paper jams in the first row that do not display a recovery time indicate currently occurring paper jams, and an icon indicating a paper jam occurs is displayed at the left end of paper jam list 801. Paper jams that occur more than a predetermined number of times (such as those in the second and fourth rows of paper jam history) are identified as frequent paper jams, and a frequent paper jam icon is displayed at the left end of the list. Figure 12In the example, paper jams occurring more than ten times are identified as frequent paper jams. When multiple histories exist for the same paper jam code, only the most recent paper jam code history is displayed in the list. This makes it easier to identify the types of paper jams that have occurred. By selecting an object in the paper jam list 801 and pressing the paper jam details button 802, detailed information about the selected object's paper jam can be viewed.

[0106] The reset button 803 is used to clear the displayed paper jam history. Service personnel use the reset button 803 when they wish to delete a notification by confirming a currently occurring or frequently occurring paper jam. When the reset button 803 is pressed, the reset date and time 804 are updated, and the paper jam list 801 displays the paper jam history after the reset date and time 804.

[0107] Figure 13 This diagram shows the paper jam details screen 810 displayed when the paper jam details button 802 is pressed. Paper jam content 811 displays the paper jam code and paper jam type of the selected paper jam in the paper jam list 801. Sensor number 812 displays the sensor number associated with the paper jam code and the location where the paper jam occurred.

[0108] Paper jam details list 813 displays paper jam histories with the same paper jam content 811 (i.e., paper jam code and paper jam type) in descending chronological order. Paper jam details list 813 displays the cumulative number of jams, date of occurrence, time of occurrence, recovery time, feed position, feed counter, and feed size. Feed position is the paper position at the time of the jam. The number displayed in the "Feed Counter" is the number of sheets of paper fed from the feed position when the jam occurred. Feed size is the size of the fed paper. Although... Figure 12 The paper jam list 801 makes paper jam changes easier to see by displaying only the most recent entry for each paper jam code, but Figure 13 The paper jam details list 813 makes it easier to see the frequency of the same paper jam. When there are many entries, the paper jam details list 813 can be scrolled up and down.

[0109] The close button 814 is used to return to the paper jam screen 800 by closing the paper jam details screen 810. Because service personnel can not only see the current paper jam, but also the locations and frequency of past paper jams, they can consider cleaning or replacing surrounding components in areas where paper jams are occurring or frequently.

[0110] Figures 14 to 17These are diagrams showing usage status screens 900 that are displayed by pressing the usage status button 407 on the top screen 400 or by pressing the usage status button 506 on each detail screen. At the right end of the usage status screen 900, temperature button 901, humidity button 902, print count button 903, and cartridge history button 904 are displayed for switching to each usage status screen. Because these buttons 901 to 904 are displayed... Figures 14 to 17 The various usage status screens 900 shown allow service personnel to easily move between them. Furthermore, by using the return buttons 501 to the usage status buttons 506, service personnel can easily move between the component life screen 500, fault detection screen 600, error screen 700, paper jam screen 800, and usage status screen 900. Therefore, service personnel can easily compare these abnormal information with the usage status and easily estimate the cause of the abnormality.

[0111] Figure 14 This is a graph showing the temperature change displayed when the temperature button 901 on the usage status screen 900 is pressed. The vertical axis of the temperature change graph 905 represents temperature (°C), and the horizontal axis represents time, displaying the temperature inside (representing the internal portion) and outside (representing the external portion) of the image processing device for a complete 24-hour period every 10 minutes. The date switch button 906 is used to switch the date displayed on the graph. By pressing the date switch button 906 and selecting a date, data from one month ago can be displayed.

[0112] In temperature change chart 905, the upper and lower limits are displayed as a reference range for temperature using dashed lines. When temperatures outside the reference range are shown, it indicates that an environmental inspection is required. Additionally, service personnel can compare with, for example... Figure 10 Error screen 700 or Figure 12 The paper jams occurred at the same time in 800 different paper jam scenarios. Figure 14 Use the time period of the temperature change screen to confirm whether the temperature change is caused by an error or a paper jam.

[0113] Figure 15 This is a graph showing the humidity change displayed when the humidity button 902 on the usage status screen 900 is pressed. The vertical axis of the humidity change graph 907 represents humidity (%), while the horizontal axis represents time, showing the internal / external humidity for one day every 10 minutes. The date toggle button 908 is used to switch the date displayed on the graph and can display data from one month ago.

[0114] In humidity variation graph 907, the upper and lower limits are displayed as a reference range for humidity using dashed lines. When humidity levels are outside the reference range, it can be determined that an environmental inspection is necessary. Additionally, service personnel can compare humidity levels with, for example... Figure 12 The paper jams occurred at the same time in 800 different paper jam scenarios. Figure 15 Use the time period shown in the humidity change image to confirm whether the humidity change is the cause of the paper jam.

[0115] Figure 16 This is a diagram showing the print count screen displayed when the print count button 903 on the usage status screen 900 is pressed. The vertical axis of the print count chart 909 represents the number of prints (sheets), while the horizontal axis represents time.

[0116] The display period switch button 910 is used to switch the unit of the chart display period to one month or one day. The date switch button 911 is used to switch the chart display date. When the display period switch button 910 is set to "Month", the data for one month is displayed at one-day intervals, and the data for each month is displayed by selecting the date switch button 911. Additionally, in this case, the date switch button 911 displays the year and month, which will be in days (instead of...). Figure 16 The example shown is in units of "Time" (time of day) and the horizontal axis of chart 909 displays the number of printed sheets.

[0117] In contrast, when "Day" is selected via the display time switching button 910, such as Figure 16 As shown in the example, the data for one day is displayed at hourly intervals, and the data for each day is switched and displayed by using a date toggle button. In this case, the date toggle button 911 displays the year, month, and day, and the horizontal axis of the print count chart 909 is displayed in units of time (time of day).

[0118] For example, in Figure 6 In the component lifespan chart 500, if a component is estimated to reach its service limit earlier than the predetermined time, the following estimation can be made. That is, based on the service personnel's assessment... Figure 16 Chart 909, which shows the number of printed pages, confirms that if a large number of prints were made just before the component reached its service limit, service personnel can estimate that the large number of prints may have been the cause of the component reaching its service limit prematurely.

[0119] Figure 17This diagram illustrates the ink cartridge history screen displayed when the ink cartridge history button 904 on the usage status screen 900 is pressed. The ink cartridge history list 912 displays the operation history of the ink cartridges in chronological order. The ink cartridge switch button 913 is used to select the target ink cartridge displayed in the ink cartridge history list 912. For example, in the event of a paper jam or error, service personnel can consider the following by checking the ink cartridge history in the ink cartridge history list 912. That is, service personnel can consider the following two points: whether the user's operational or setting errors while using the image processing device are the cause of these paper jams or errors, and whether the malfunction is caused by factors other than user operational or setting errors.

[0120] <Construction of Historical Data>

[0121] Next, we will explain the data recorded in the historical management unit 304, which manages the data displayed on the aforementioned status monitoring screen. The historical management unit 304 will... Figure 2 The device I / F 220 in the middle organizes the values ​​and settings obtained from various sensors 255, scanners 270 and / or printers 295 into necessary information and stores this information in HDD 204 or RAM 202. It should be noted that the "historical data" mentioned here refers to the historical data of "status information (component life, fault detection, errors, paper jams)" and "historical information (usage status)".

[0122] Figure 18 This displays historical data 1000 used to show component lifespan information. This historical data 1000 includes No. 1001, component name 1002, and historical data 1003 on component status. No. 1001 indicates the component's order in this historical data. The historical data 1003 on status includes, for example, the date the data was acquired, the component's status level, status value [%], and the number of sheets used. The historical data 1003 on status is stored daily. The status level, status value, and number of sheets used are as described above. Figure 6 As described in the description of Parts List 507.

[0123] In the historical data 1003 of the status, the component with a status level of "3" is... Figure 4 The cross-sectional view 401 and component life 403 show components that need to be replaced. Components with a status level of "2" are... Figure 4 The cross-sectional view 401 and component life 403 show the components recommended for replacement. All components shown under component name 1002 and their status are displayed in the order of number 1001. Figure 6 The components are listed in part list 507. Additionally, historical status data 1003 is used for display. Figure 7The status transition chart is shown in Figure 511. Since the display period includes 30 days and 180 days, at least 180 days of data are retained. If a service worker detects that a part has been replaced, the status level of the replaced part will change to "0". Status level "0" indicates a state where no value is defined after part replacement. Additionally, at this time, there is no data for the status value [%] and the number of sheets used. Thus, the part lifespan display on each screen will use... Figure 18 Historical data on component lifespan.

[0124] Figure 19 Historical data 1100 used to display fault detection information is shown. This historical data 1100 includes No. 1101, object 1102, and historical fault data 1103. No. 1101 indicates the order of faults in this historical data 1100. Object 1102 indicates the name or content of the fault. Historical fault data 1103 includes the date the data was acquired, contamination level, contamination percentage (%), and cartridge anomaly detection. The contamination level, contamination percentage (%), and cartridge anomaly detection are as described above. Figure 8 As described in the description of fault list 601.

[0125] In the case of an optical unit, the data includes the date the data was acquired, the pollution level, and the pollution percentage [%), and this data is stored daily. Figure 4 In the cross-sectional view 401 and fault detection 404, the optical unit with a contamination level of "3" is shown as a fault requiring inspection. Figure 4 In the cross-sectional view 401 and fault detection 404, the optical unit with contamination level "2" is shown as a fault requiring recommended inspection. Additionally, historical fault data 1103 related to the optical unit is used for display. Figure 9 The pollution transition is shown in Chart 611. Since the display periods are 30 days and 180 days, at least 180 days of data are retained.

[0126] In the case of ink cartridges, the historical data 1103 for each fault includes the date the data was acquired and whether any anomaly was detected, and this data is stored daily. Figure 4 In the cross-sectional view 401 and fault detection 404, ink cartridges with an anomaly detection result of "existence" will be displayed as faults requiring inspection. Figure 9 In the fault list 601, all faults of object 1102 and their status (contamination value and contamination level) are displayed in the order of number 1101.

[0127] The service personnel select an item from fault list 601 and press [button / button]. Figure 8In the case of the "Processed" button 603, the values ​​related to the object fault status will be updated as follows. That is, if the object fault is contamination of the optical unit, the contamination level value will become "0", i.e., in an undefined state. At this time, there is no data for the contamination degree [%]. If the object fault is related to the ink cartridge, the anomaly detection is updated to "None". Thus, Figure 19 Historical fault detection data is used for fault detection display on each screen.

[0128] Figure 20 Historical data 1200 used to display error information is shown. This historical data 1200 includes error code 1201, error title 1202, occurrence date 1203, occurrence time 1204, and recovery time 1205. Error code 1201 is used to identify the error. Occurrence date 1203 is the date the error occurred, and occurrence time 1204 is the time the error occurred. Recovery time 1205 is the time the error was resolved. Errors for which recovery time 1205 was not recorded are... Figure 4 Error 405 is displayed as an error that is currently occurring.

[0129] Figure 20 Historical data, displayed in descending order of occurrence date (1203) and occurrence time (1204), is shown... Figure 10 In error list 701. Although in Figure 20 The contents corresponding to each error code of error code 1201 are not shown, but these contents are stored in HDD 204 and displayed. Figure 11 The error details screen shows this. Thus, Figure 20 Error history data was used to display errors on various screens.

[0130] Figure 21 Historical data 1300 for displaying paper jam information is shown. This historical data 1300 includes paper jam code 1301, type 1302, sensor 1303, occurrence date 1304, occurrence time 1305, recovery time 1306, cumulative number of times 1307, paper feed position 1308, paper feed counter 1309, and paper feed size 1310.

[0131] Paper jam code 1301 is used to identify paper jams. Type 1302 is the type of paper jam corresponding to the paper jam code. Type 1302 includes various types, such as DELAY, where the sensor does not detect paper even after an expected time; STNRY, where the sensor detects paper for longer than the expected time; DOUBLE, where the ADF sensor detects double paper feed, etc. Sensor 1303 is the sensor number that detected the paper jam. Date of occurrence 1304 is the date the paper jam occurred, and time of occurrence 1305 is the time the paper jam occurred. Recovery time 1306 is the time the paper jam was resolved. Paper jams for which recovery time 1306 is not recorded are... Figure 4 The cross-sectional view 401 and the paper jam 406 show the paper jam in progress.

[0132] The cumulative count of 1307 represents the number of times paper jams with the same paper jam code have occurred. Figure 12 Paper jams occurring after the reset date and time 804 will be accumulated. For example, if the accumulated number reaches a predetermined number (more than 10 in this case), the paper jam is identified as a frequent paper jam, and... Figure 4 The cross-sectional view 401 and the paper jam 406 are shown. Paper feed position 1308 is the position where the paper jam occurs and the paper is supplied. Paper feed counter 1309 is the number of sheets of paper supplied from the paper feed position.

[0133] Figure 21 Historical data 1300 is displayed in descending order by occurrence date 1304 and occurrence time 1305. Figure 12 The paper jam list 801 is displayed. At this point, as described above, only the most recent instance of a paper jam with the same paper jam code is shown. The history of the same paper jam codes is displayed. Figure 13 The details are shown in the cardstock screen. It should be noted that... Figure 13 If the reset button 803 is pressed, the paper jam history before the date and time were pressed will be deleted. Thus, Figure 21 The historical data of the paper jams is used for the paper jam display of each screen.

[0134] It should be noted that, Figure 20 and Figure 21 Each historical data point can also have a consecutive number, for example... Figure 18 and Figure 19 The historical data shows numbers 1001 and 1101.

[0135] Figures 22 to 25 Each displays data used to show usage status information (temperature, humidity, number of prints, and cartridge history), which is used as historical information.

[0136] Figure 22Temperature data 1400, used to display temperature change information, is shown. This data 1400 includes date 1401, time 1402, internal data 1403, and external data 1404. Date 1401 indicates the date the temperature data was acquired, and for example, stores data for one month. Time 1402 indicates the time the temperature data was acquired, and for example, stores data every 10 minutes. Internal data 1403 stores temperature data acquired by a thermometer (not shown) installed inside the device. External data 1404 stores temperature data acquired by a thermometer (not shown) installed outside the device. Figure 22 The data shown is for display Figure 14 Temperature change chart 905.

[0137] Figure 23 Humidity data 1410, used to display humidity change information, is shown. This data 1410 includes date 1411, time 1412, internal data 1413, and external data 1414. Date 1411 indicates the date the humidity data was acquired, and for example, stores one month's worth of data. Time 1412 indicates the time the humidity data was acquired, and for example, stores data every 10 minutes. Internal data 1413 stores humidity data acquired by a hygrometer (not shown) installed inside the device. External data 1414 stores humidity data acquired by a hygrometer (not shown) installed outside the device. Figure 23 The data shown is for display Figure 15 The humidity change chart is shown in Figure 907.

[0138] Figure 24 Print count data 1420 is shown for displaying the number of printed pages. This data 1420 includes a date 1421, a time 1422, and the number of printed pages 1423. Date 1421 indicates the date the print count data was acquired. Time 1422 indicates the time the print count data was acquired. The number of printed pages 1423 indicates the number of pages printed by the image processing device 103. For example, the date 1421, time 1422, and print count 1423 for one month are stored every hour. Figure 24 The data shown is for display Figure 16 The number of printed sheets is shown in chart 909.

[0139] Figure 25The image processing device 103 displays ink cartridge operation data 1430 for displaying ink cartridge history information. This data 1430 is stored when a user performs an ink cartridge closing operation or a media (i.e., paper) change operation on the ink cartridges. This data includes date 1431, time 1432, ink cartridge 1433, and ink cartridge operation 1434. Date 1431 indicates the date the ink cartridge operation was performed. Time 1432 indicates the time the ink cartridge operation was performed. Ink cartridge 1433 indicates information about the location of the operated ink cartridge. In ink cartridge operation 1434, if an ink cartridge closing operation was performed, the message "Ink cartridge closed" is stored. Additionally, if a media change operation was performed, "Media changed" and the changed paper size and paper type are stored. For ink cartridge history information, a predetermined number of data entries (e.g., up to 300) are stored. Figure 25 The data shown is for display Figure 17 The ink cartridge history list is 912.

[0140] It should be noted that the ink cartridge operation data is not limited to the ink cartridge itself, and can also store the operation data of the manual paper feed tray.

[0141] <Processing performed by the image processing device>

[0142] Figures 26 to 28 This is the top screen showing the startup process, including the status monitor. Figure 4 The flowchart illustrates an example of the display processing. The program (e.g., firmware) used to implement this processing is stored in the HDD 204 of the image processing device 103, loaded into RAM 202, and executed by the CPU 201.

[0143] The process begins when the CPU 201 receives a special command from the service personnel via the operation unit 212 to activate the status monitor.

[0144] In step S1501, CPU 201 refers to the device configuration information (not shown) of the image processing apparatus stored in RAM 202.

[0145] In step S1502, CPU 201 determines the cross-sectional view to be displayed on each screen. For example, the cross-sectional view to be displayed may vary depending on the presence or absence of a scanner, the presence or absence of a paper feed option, and the presence or absence of a paper exit option. In the case of running a common program across multiple image processing devices, CPU 201 can switch to the cross-sectional view appropriate for that model based on the model information. This is because the paper transport path, components, and the position of the paper jam sensor may differ depending on the model of the image processing device.

[0146] In step S1503, CPU 201 references the data stored in HDD 204. Figure 18The historical data for component lifespan shown is 1000.

[0147] In step S1504, CPU 201 determines, based on the reference result in step S1503, whether there is a component with a status level of "2" or higher.

[0148] If the determination result in step S1504 is "No", then in step S1505, CPU 201 determines that... Figure 4 No component lifespan icon is displayed in the cross-sectional view 401, and "No notification" is displayed in the notification area of ​​component lifespan 403. If the result is "yes", in step S1506, the CPU 201 obtains information on components that need to be replaced with a status level of "3" from the historical component lifespan data.

[0149] In step S1507, CPU 201 obtains information on recommended replacement parts with a status level of "2" from the component lifespan history data. The order of steps S1506 and S1507 can be reversed.

[0150] In step S1508, CPU 201 displays icons at the corresponding coordinates on the cross-sectional view 401 indicating the parts that need to be notified and / or recommended for replacement, as obtained in steps S1506 and S1507.

[0151] In step S1509, the CPU 201 sequentially displays the components requiring notification, starting with those having the highest priority, obtained in steps S1506 and S1507. As a priority, "Needs Replacement" (status level "3") is set higher than "Recommended Replacement" (status level "2"). In cases where levels are the same, [the CPU 201]... Figure 18 The numbers 1001 are displayed sequentially.

[0152] In step S1510, CPU 201 determines whether the number of components to be notified is greater than the number of components that can be displayed in the notification area of ​​component lifetime 403 (e.g., 3). If the determination result is "No", the process proceeds to step S1512. If the determination result is "Yes", in step S1511, CPU 201 displays the notifications that cannot be fully displayed by using the text "Other:" and its quantity.

[0153] In step S1512, CPU 201 references the data stored in HDD 204. Figure 19 The historical data for fault detection shown is 1100.

[0154] In step S1513, CPU 201 determines, based on the reference results in step S1512, whether there is a fault with an optical unit contamination level of "2" or above and / or a cartridge malfunction.

[0155] If the result is determined to be "no", in step S1514, CPU 201 determines that... Figure 4 No fault detection icons are displayed in the cross-sectional view 401, and "No notification" is displayed in the notification area of ​​fault detection 404. If the result is determined to be "yes", in step S1515, the CPU 201 obtains information on optical units with a contamination level of "3" and / or cartridges with abnormalities from the historical data of fault detection.

[0156] In step S1516, CPU 201 obtains information about optical units with a contamination level of "2" from the fault detection history data. The order of steps S1515 and S1516 can be reversed.

[0157] In step S1517, CPU 201 displays icons at the corresponding coordinates on cross-sectional view 401 for required and / or recommended checks of the faults that need to be notified in steps S1515 and S1516.

[0158] In step S1518, the CPU 201 sequentially displays the faults requiring notification, obtained in steps S1515 and S1516, starting with the faults with the highest priority. As a priority, faults requiring inspection (contamination level "3") are set higher than those requiring recommended inspection (contamination level "2"), and in cases where the levels are the same, they are further prioritized according to... Figure 19 The numbers 1101 are displayed sequentially.

[0159] In step S1519, CPU 201 determines whether the number of faults to be notified is greater than the number of faults that can be displayed in the notification area of ​​fault detection 404 (e.g., three). If the determination result is "No", the process proceeds to step S1521. If the determination result is "Yes", in step S1520, CPU 201 displays the notifications that cannot be fully displayed through the text "Other:" and its quantity.

[0160] In step S1521, CPU 201 references the data stored in HDD 204. Figure 20 The historical data shown is 1200, which is incorrect.

[0161] In step S1522, CPU 201 determines whether the following exists based on the reference result of step S1521. Figure 20 The error that occurred at 12:05 is currently unregistered.

[0162] If the result is determined to be "No", in step S1523, it is determined that "No notification" will be displayed in the notification area of ​​error 405. If the result is determined to be "Yes", in step S1524, CPU 201 obtains information about the occurrence of the error at unregistered recovery time 1205 from the error history data.

[0163] In step S1525, CPU 201 retrieves the errors that need to be notified in step S1524 and displays them in descending order.

[0164] In step S1526, CPU 201 determines whether the number of errors to be notified is greater than the number of errors that can be displayed in the notification area of ​​error 405 (e.g., two). If the determination result is "No", the process proceeds to step S1528. If the determination result is "Yes", in step S1527, CPU 201 displays the notifications that cannot be fully displayed by specifying the text "Other:" and its quantity.

[0165] In step S1528, CPU 201 references the data stored in HDD 204. Figure 21 The historical data for the card shown is 1300.

[0166] In step S1529, CPU 201 determines whether the reference result from step S1528 exists. Figure 21 The current paper jam that occurred at time 1306 is not registered, or there are frequent paper jams that have occurred more than 10 times in total (1307).

[0167] If the result is determined to be "no", in step S1530, CPU 201 determines that... Figure 4 No paper jam icon is displayed in the cross-sectional view 401, and "No notification" is displayed in the notification area of ​​paper jam 406. If the result is "yes", in step S1531, CPU 201 obtains information about the currently occurring paper jam at unregistered recovery time 1306 from the historical data of paper jams.

[0168] In step S1532, CPU 201 retrieves information from historical paper jam data indicating frequent paper jams with a cumulative number of 10 or more (1307). The order of steps S1531 and S1532 can be reversed. Additionally, in... Figure 21 In cases where multiple records with the same paper jam code are found in the historical data of the paper jam, the latest data can be retrieved.

[0169] In step S1533, CPU 201 displays icons at corresponding coordinates on cross-sectional view 401 representing paper jams that occurred and / or frequently occurred and require notification, as obtained in steps S1531 and S1532.

[0170] In step S1534, the CPU 201 sequentially displays the paper jams that needed notification, acquired in steps S1531 and S1532, starting with the paper jam with the highest priority. As a priority, the currently occurring paper jam is set higher than frequently occurring paper jams. In cases where the priorities are the same, for example, they are displayed in descending order of acquisition order. Furthermore, if both currently occurring and frequently occurring paper jams exist simultaneously, the currently occurring paper jam is displayed with priority over frequently occurring paper jams.

[0171] In step S1535, CPU 201 determines whether the number of paper jams to be notified is greater than the number of paper jams that can be displayed in the notification area of ​​paper jam 406 (e.g., two). If the determination result is "No", the process proceeds to step S1537. If the determination result is "Yes", in step S1536, CPU 201 displays the notifications that cannot be fully displayed using the text "Other:" and its quantity.

[0172] In step S1537, the CPU 201 displays the content determined in steps S1501 to S1536 on the screen of the operation unit 212. That is, the display... Figure 4 The top view of the status monitor is 400.

[0173] pass Figures 26 to 28 The processing of the image processing device 103, including its anomalies and locations, can be displayed in the cross-sectional view 401 and notification areas (403 to 406) in which field service personnel urgently need to confirm the anomalies. Therefore, service personnel can understand the full picture of the image processing device anomalies and their locations from a single view, which serves as the top view 400. As a result, the efficiency of anomaly location confirmation is improved for field service personnel requiring rapid response. Furthermore, service personnel can identify locations where two or more anomalies are clustered together from the cross-sectional view 401 and can also consider efficient subsequent work processes, such as addressing these clustered anomalies collectively.

[0174] Thus, according to this embodiment, information required for the maintenance of the image processing device 103, especially information related to anomalies occurring in the device and their locations, can be effectively displayed within a limited screen area, thereby improving the work efficiency of service personnel.

[0175] In addition, service personnel can estimate the relationship between multiple anomalies based on their location in section diagram 401. For example, if a notification to replace ink cartridge roller 1 is received simultaneously, within similar time periods, or at similar intervals, along with a notification of frequent paper jams in the vicinity, it is understandable that replacing ink cartridge roller 1 is highly likely to resolve the frequent paper jams.

[0176] Next, we will explain the situation where service personnel operate the operation unit 212 after the status monitor's top screen 400 is displayed. Figures 4 to 17 An example of screen transition processing performed by screen switching operations. Figures 29 to 31 This is a flowchart illustrating the process. The program (e.g., firmware) used to implement the process is stored in the HDD 204 of the image processing device 103, loaded into the RAM 202, and executed by the CPU 201.

[0177] Display on operation unit 212 Figures 4 to 17 In the state of the screen, the CPU 201 starts the process by accepting input from the service personnel via the operation unit 212.

[0178] When the CPU 201 detects that a button on the screen has been pressed, in step S1601, the CPU 201 determines that the button has been pressed. Figures 4 to 17 Which button is shown?

[0179] First, we will explain the case where the pressed button is either the notification area of ​​component life 403 or the component life button 502. If the pressed button in step S1601 is either the notification area of ​​component life 403 or the component life button 502, the determination result of step S1601 becomes "component life", and the process proceeds to step S1602.

[0180] In step S1602, CPU 201 references the data stored in HDD 204. Figure 18 The historical data for component lifespan shown is 1000.

[0181] In step S1603, the CPU 201 displays the component lifespan history data referenced in step S1602 on the operation unit 212. Figure 6 The component lifespan screen shown is 500. At this time, the cross-sectional view 401 displays the same... Figure 26 The icons corresponding to component life-related anomalies identified in step S1508 are displayed. Other icons (those corresponding to fault detection and paper jam-related anomalies) are not displayed. Additionally, Figure 18 The status of all components listed in the historical data of component lifespan is displayed in component list 507.

[0182] After the component life screen 500 is displayed in step S1603, when the CPU 201 detects that a button on the screen has been pressed, in step S1604, the CPU 201 determines which button on the component life screen 500 has been pressed.

[0183] If the button pressed in step S1604 is the status details button 508, the determination result of step S1604 becomes "status details", and the process proceeds to step S1605.

[0184] In step S1605, CPU 201 references Figure 18 The component life history data shown is the component list 507, which contains the component status history data 1003 (i.e., the data used for graphic creation).

[0185] In step S1606, CPU 201 displays a graph of the status value [%] by creating a graph based on the time-series dates of the historical status data 1003 referenced in step S1605. Figure 7 The status details screen 510 is then displayed. At this time, the data for the specified display period in display period 512 is displayed as a status transition chart 511. After the status details screen 510 is displayed, the user returns to the component lifespan screen 500 by pressing the close button 513 (not shown). Afterwards, the user proceeds to the confirmation wait step in step S1601.

[0186] If the button pressed in step S1604 is not the status details button 508, the determination result of step S1604 becomes "other", and in step S1601, it is determined which button among buttons 501 to 506 was pressed.

[0187] Next, we will explain the case where the pressed button is either the notification area of ​​fault detection 404 or the fault detection button 503. If the pressed button in step S1601 is either the notification area of ​​fault detection 404 or the fault detection button 503, the determination result of step S1601 becomes "fault detection", and the process proceeds to step S1607.

[0188] In step S1607, CPU 201 references the data stored in HDD 204. Figure 19 The historical data for fault detection shown is 1100.

[0189] In step S1608, the CPU 201 displays the fault detection history data referenced in step S1607 on the operation unit 212. Figure 8 The fault detection screen 600 is shown. At this time, the cross-sectional view 401 displays... Figure 27 The icons corresponding to the fault detection-related anomalies identified in step S1517 are displayed. Other icons (those corresponding to component lifespan and paper jam-related anomalies) are not displayed. Additionally, Figure 19 The status of all faults listed in the fault detection history data is displayed in fault list 601.

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

[0191] If the button pressed in step S1609 is the contamination details button 602, the determination result of step S1609 becomes "contamination details," and the process proceeds to step S1610. In step S1610, CPU 201 references... Figure 19 The fault detection history data shown is the historical data 1103 of the optical unit selected in the fault list 601 (i.e., the data used to create the chart).

[0192] In step S1611, CPU 201 creates a pollution level [%] chart based on the date of the time series of the fault history data 1103 referenced in step S1610, and displays it. Figure 9 The pollution details screen 610 is displayed. At this time, the data for the display period specified in the display period 612 is displayed as a pollution transition chart 611. After displaying the pollution details screen 610, the user returns to the fault detection screen 600 by pressing the close button 613 (not shown). Then, the user proceeds to the confirmation wait step S1601.

[0193] If the button pressed in step S1609 is the processed button 603, the determination result of step S1609 becomes "processed," and processing proceeds to step S1612. In step S1612, CPU 201 performs processed handling on the fault selected in fault list 601. If the fault selected in fault list 601 is related to the optical unit, CPU 201 returns the contamination level of fault history data 1103 to the initial value "0." If the fault selected in fault list 601 is related to the ink cartridge, CPU 201 returns the anomaly detection of fault history data 1103 to the initial value "none." Afterward, CPU 201 displays a fault detection screen 600 reflecting the latest fault detection history data.

[0194] If the button pressed in step S1609 is neither the contamination details button 602 nor the processed button 603, the determination result of step S1609 becomes "Other". In this case, in step S1601, it is determined which button among buttons 501 to 506 was pressed.

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

[0196] In step S1613, CPU 201 references the data stored in HDD 204. Figure 20 The historical data shown is 1200, which is incorrect.

[0197] In step S1614, the CPU 201 displays the error history data referenced in step S1613 on the operation unit 212. Figure 10 Error screen 700 appears. At this point, error list 701 is displayed. Figure 20 All errors are listed in the error history data shown.

[0198] After displaying error screen 700 in step S1614, when CPU 201 detects that a button on the screen has been pressed, in step S1615, CPU 201 determines which button on error screen 700 has been pressed.

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

[0200] In step S1617, CPU 201 displays the error information referenced in step S1616. Figure 11 Error details screen 710 is displayed. After displaying error details screen 710, return to error screen 700 by pressing the close button 714 (not shown). Then, proceed to the confirmation wait in the return process step S1601.

[0201] If the button pressed in step S1615 is not the error details button 702, the determination result of step S1615 becomes "Other". In this case, in the determination of step S1601, it is determined which button among buttons 501 to 506 was pressed.

[0202] Next, the case where the pressed button is the notification area of ​​paper jam 406 or the paper jam button 505 will be explained. If the pressed button in step S1601 is the notification area of ​​paper jam 406 or the paper jam button 505, the determination result of step S1601 becomes "paper jam", and the process proceeds to step S1618.

[0203] In step S1618, CPU 201 references the data stored in HDD 204. Figure 21 The historical data for the card shown is 1300.

[0204] In step S1619, the CPU 201 displays the historical paper jam data referenced in step S1618 on the operation unit 212. Figure 12 The paper jam image is shown at 800. At this point, the cross-sectional view 401 displays the image... Figure 28 The icons corresponding to the paper jam-related anomalies identified in step S1533. Other icons (those corresponding to anomalies related to component lifespan and fault detection) are not displayed. Additionally, in Figure 21 In the historical data of the paper jams shown, the paper jam list 801 only displays the latest data for each paper jam code. That is, for data with the same paper jam code, the paper jam list 801 only displays the latest data.

[0205] After displaying the paper jam screen 800 in step S1619, when the CPU 201 detects that a button on the screen has been pressed, in step S1620, the CPU 201 determines which button on the paper jam screen 800 has been pressed. If the button pressed in step S1620 is the paper jam details button 802, the determination result of step S1620 becomes "paper jam details", and the process proceeds to step S1621.

[0206] In step S1621, CPU 201 references Figure 21 The data shown is the paper code that matches the paper code selected in paper list 801 from the historical data of the paper jams.

[0207] In step S1622, CPU 201 uses the data with the matching paper jam code referenced in step S1621 and displays it. Figure 13 The paper jam details screen 810 is displayed. After the paper jam details screen 810 is displayed, return to the paper jam screen 800 by pressing the close button 814 (not shown). Then, proceed to the confirmation wait in the return process step S1601.

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

[0209] In step S1623, CPU 201 deletes Figure 21 The paper jam history data will be reset, and the date and time will be reset (804). Figure 12 Update the date and time to the reset setting. Then, the display will reflect this. Figure 21 The latest historical data of the paper jam screen 800.

[0210] If the button pressed in step S1623 is neither the paper jam details button 802 nor the reset button 803, the determination result of step S1623 becomes "Other". In this case, in the determination of step S1601, it is determined which button among buttons 501 to 506 was pressed.

[0211] Next, the case where the pressed button is either the usage status button 407 or the usage status button 506 will be explained. If the pressed button in step S1601 is either the usage status button 407 or the usage status button 506, the determination result of step S1601 becomes "usage status", and the process proceeds to step S1624.

[0212] In step S1624, CPU 201 determines that... Figure 14 (to Figure 17 The button pressed in the usage status screen 900. The temperature button 901 is the button selected as the initial value of the usage status screen 900. Therefore, when changing from a screen other than the usage status screen 900, the determination result of step S1624 becomes "temperature", and the process proceeds to step S1625.

[0213] In step S1625, CPU 201 references the data stored in HDD 204. Figure 22 The temperature data shown is 1400.

[0214] In step S1626, CPU 201 uses the temperature data referenced in step S1625 to create a temperature change chart 905 for internal data 1403 and external data 1404 based on the time series date 1401 and time 1402. Figure 14 At this point, CPU 201 creates a chart for the date specified in date switch button 906. Then, CPU 201 displays the chart on operation unit 212. Figure 14 The temperature change screen is displayed. Afterwards, the process returns to step S1624 for confirmation and waiting.

[0215] If the button pressed in step S1624 is the humidity button 902, the determination result of step S1624 becomes "humidity," and the process proceeds to step S1627. In step S1627, CPU 201 references the data stored in HDD 204. Figure 23 The humidity data shown is 1410.

[0216] In step S1628, CPU 201 uses the humidity data referenced in step S1627 to create a humidity change chart 907 of internal data 1413 and external data 1414 based on the time series date 1411 and time 1412. Figure 15 At this point, CPU 201 creates a chart for the date specified in date switch button 908. Then, CPU 201 displays the chart on operation unit 212. Figure 15 The screen displays the humidity changes. Afterwards, the process returns to step S1624 for confirmation and waiting.

[0217] If the button pressed in step S1624 is the print count button 903, the determination result of step S1624 becomes "print count", and the process proceeds to step S1629. In step S1629, CPU 201 refers to the data stored in HDD 204. Figure 24 The number of printouts shown is 1420.

[0218] In step S1630, CPU 201 uses the print count data referenced in step S1629 to create a print count chart 909 for print count 1423 based on the time series date 1421 and time 1422. Figure 16 ).exist Figure 16 When "Day" is selected in the display time period switch button 910, a daily print count chart is created with an hourly interval. When "Month" is selected in the display time period switch button 910, a monthly print count chart is created with a dayly interval. Then, the CPU 201 displays the print count on the operation unit 212. Figure 16 The screen displays the number of printouts. Afterwards, the process returns to step S1624 for confirmation and waiting.

[0219] If the button pressed in step S1624 is the cartridge history button 904, the determination result of step S1624 becomes "cartridge history", and the process proceeds to step S1631. In step S1631, the CPU 201 references the data stored in the HDD 204. Figure 25 The ink cartridge operation data shown is 1430.

[0220] In step S1632, CPU 201 uses the cartridge operation data referenced in step S1631 to create a cartridge history list 912 of cartridge operation data 1424 based on the date 1431 and time 1432 of the time series. Here, CPU 201 extracts... Figure 17 The ink cartridge history list 912 is created by using the data of the selected ink cartridge on the ink cartridge switch button 913. For example, due to the data of the selected ink cartridge on the switch button 913, the ink cartridge history list 912 is created. Figure 17 The ink cartridge switch button 913 selected "Ink Cartridge 1", therefore the CPU 201 extracted... Figure 25 The data of "Cartridge 1" in cartridge 1433 is used to create the cartridge history list 912. Then, the CPU 201 displays it on the operation unit 212. Figure 17The ink cartridge history screen is displayed. Afterwards, the process returns to step S1624 for confirmation and waiting.

[0221] If the button pressed in step S1624 is not any of the temperature button 901, humidity button 902, print count button 903, or cartridge history button 904, the determination result of step S1624 becomes "other". In this case, in the determination of step S1601, it is determined which button 501 to 506 was pressed.

[0222] It should be noted that, in Figures 6 to 17 A return button 501 is provided. When the return button 501 is pressed, the determination in step S1601 changes to "return", and the process proceeds to step S1633.

[0223] In step S1633, CPU 201 executes... Figure 26 and Figure 27 The top screen display is processed and the top screen 400 is displayed.

[0224] Finally, will be on Figures 4 to 17 The following describes the case where an operation (not shown) for ending status monitoring is input on the screen. In step S1601, when the CPU 201 detects an operation for ending status monitoring, the determination result of step S1601 becomes "End". Then, in step S1634, processing for displaying the end of status monitoring is performed.

[0225] Thus, in Figures 29 to 31 During the processing, in order for service personnel to confirm detailed information, it can be done from... Figure 4 The top screen 400 transitions to a component lifespan screen 500, a fault detection screen 600, an error screen 700, a paper jam screen 800, and a usage status screen 900. Therefore, service personnel can immediately view these screens from the top screen 400 and gather the information needed to take appropriate action. Furthermore, since these screens can be navigated between using buttons 502 to 506, service personnel can estimate the cause of the anomaly based on the relevant information on each screen and consider countermeasures accordingly. Moreover, service personnel can estimate the timing of anomalies in locations where they have not yet occurred (primarily component lifespan and optical unit contamination) and prepare accordingly.

[0226] (Other embodiments)

[0227] As described in the above embodiments, predetermined criteria for identifying anomalies can also be established based on usage status (historical information). In this case, the display unit 302 displays an area in the top screen 400 that provides information related to anomalies in the usage status, similar to notification areas such as component lifespan 403 and error 405. Additionally, the display unit 302 can display icons corresponding to the anomaly-related information in the usage status on the cross-sectional view 401. For example, for temperature, if the current temperature exceeds... Figure 14 When the reference range indicated by the upper and lower dashed lines in the temperature change graph 905 is considered, anomalies can be identified, and notification of the current temperature anomaly can be provided. In this case, for example, simply displaying an icon corresponding to the temperature anomaly at a predetermined location in the cross-sectional view 401 (e.g., around or near the cross-sectional view 401). The same applies to humidity. For example, for the number of printed pages, an anomaly can be identified if the number of printed pages exceeds a threshold. Multiple thresholds can be set in stages as these temperature standards and printed page thresholds.

[0228] In the above embodiments, although temperature and humidity are constructed as elements within a state category, it is also possible to establish an "Environment" category as a separate state information category and construct temperature and humidity as elements within that "Environment" category. In this case, for example, it is only necessary to... Figure 4 and Figure 6 Further, "Environment" is established as a status category, and when the "Environment" button is pressed, a screen and buttons for displaying details of temperature or humidity can be shown.

[0229] In the above embodiments, Figure 4 In the top screen 400 shown, usage status (usage status button 407) is displayed as a category. However, the top screen 400 may also display temperature button 901, humidity button 902, print count button 903, and cartridge history button 904. Figure 14 ( ), instead of using status button 407.

[0230] In the above embodiments, Figure 4 In the top screen 400 shown, pressing the usage status button 407 transitions to another screen. Figures 14 to 17 However, by pressing the usage status button 407, with Figure 14 , Figure 15 , Figure 16 or Figure 17 The corresponding screen can be displayed in a pop-up overlay on the top screen 400.

[0231] Embodiments of this disclosure can also be implemented by a computer that reads and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (also more fully referred to as a "non-transitory computer-readable storage medium") to perform one or more functions in the above embodiments, and / or includes one or more circuits (e.g., application-specific integrated circuits (ASICs)) for performing one or more functions in the above embodiments. Furthermore, embodiments of the invention can be implemented using methods by which the computer of the system or device, for example, reads and executes the computer-executable instructions from the storage medium to perform one or more functions in the above embodiments, and / or controls the one or more circuits to perform one or more functions in the above embodiments. A computer may include one or more processors (e.g., a central processing unit (CPU), a microprocessor unit (MPU)) and may include separate computers or networks of separate processors to read and execute computer-executable instructions. The computer-executable instructions may be provided to the computer from, for example, a network or a storage medium. The storage medium may include, for example, a hard disk, random access memory (RAM), read-only memory (ROM), the memory of a distributed computing system, an optical disk (e.g., an optical disc (CD), a digital versatile optical disc (DVD), or a Blu-ray disc (BD)). TM One or more of the following: flash memory devices, memory cards, etc.

[0232] Embodiments of the present invention can also be implemented by providing software (including computer program products of computer programs) that performs the functions of the above embodiments to a system or device via a network or various storage media, and the computer (central processing unit (CPU) or microprocessor unit (MPU) of the system or device) reads and executes the computer program.

[0233] While this disclosure has been described with reference to exemplary embodiments, it should be understood that this disclosure is not limited to the exemplary embodiments disclosed. The scope of the appended claims should be interpreted in the broadest possible sense to encompass all such variations and equivalent structures and functions.

[0234] This application claims the benefit of Japanese Patent Application No. 2024-78846, filed on May 14, 2024, the entire contents of which are incorporated herein by reference.

Claims

1. An image processing apparatus having a display unit, the image processing apparatus comprising: The management department is used to manage the status and historical information of the image processing device, and The processing unit is responsible for processing information based on the managed status and historical data. The processing based on status information and historical information includes: displaying the display content on the display unit in a single screen based on the first display information and the second display information. The first display information is used to display the abnormal information in the status information and historical information of the image processing device for each category by dividing the abnormal information into different categories. The second display information is used to display the data corresponding to the abnormal information at the corresponding position on the schematic diagram of the image processing device.

2. The image processing apparatus according to claim 1, in, The exception-related information in the first display is shown according to the predetermined priority order for each category.

3. The image processing apparatus according to claim 2, in, The first displayed information includes icon images based on priority.

4. The image processing apparatus according to claim 1, in, The anomaly-related information includes: first information indicating the anomaly that needs to be addressed, and second information indicating the anomaly for which a recommended approach should be taken.

5. The image processing apparatus according to claim 4, in, The abnormal information in the first display information is displayed in the order that the first information is set to a higher priority than the second information, for each category.

6. The image processing apparatus according to claim 1, in, Among the abnormal information, for each category, a predetermined number of one or more display objects and the number of one or more non-display objects that cannot be fully displayed on the display unit are displayed as the first display information.

7. The image processing apparatus according to claim 6, in, The second display information includes both data corresponding to the one or more display objects in the first display information and data corresponding to the one or more non-display objects in the first display information.

8. The image processing apparatus according to claim 1, in, The area displaying the first display information includes multiple operation areas corresponding to the multiple categories. The multiple operation areas include the following functions: accepting operations to display a list of abnormal information related to the status information of each category on the display unit.

9. The image processing apparatus according to claim 1, in, The multiple categories display abnormal information as display content based on the first display information. In addition to the category related to paper jam, the multiple categories also include at least one of the following: component life, error, and malfunctions other than error and paper jam.

10. The image processing apparatus according to claim 1, in, The area displaying the first display information includes multiple operation areas corresponding to the multiple categories, and the operation area corresponding to historical information among the multiple operation areas includes the following function: accepting an operation to display the usage status of the image processing device based on historical information on the display unit, the usage status being divided into multiple different categories.

11. The image processing apparatus according to claim 10, in, The information displayed as the usage status is divided into at least two categories among temperature, humidity, number of printed pages, and ink cartridge operation history, and is displayed as one of the multiple categories.

12. The image processing apparatus according to claim 1, in, The second display information includes icon images corresponding to the anomaly-related information, based on a predetermined priority for the anomaly-related information.

13. The image processing apparatus according to claim 12, in, In the case where there are multiple anomaly-related information items corresponding to the same position on the diagram, the icon image corresponding to the anomaly-related information item with the highest priority is displayed.

14. The image processing apparatus according to claim 1, in, Different schematic diagrams are displayed on the display unit for each structure or type of the image processing device, as the schematic diagrams.

15. The image processing apparatus according to claim 1, in, The second display information includes information about the paper transport path shown in the schematic diagram.

16. The image processing apparatus according to claim 1, in, In the schematic diagram, in addition to the position corresponding to the paper jam, data corresponding to abnormal information is displayed at the position corresponding to at least one of component life, error, and malfunction other than error and paper jam, as the display content based on the second display information.

17. The image processing apparatus according to claim 1, in, The first display information includes information about an anomaly in which the location in the image processing device cannot be specified, and this anomaly information is not displayed in the second display information.

18. A method performed by an image processing apparatus having a display unit, the method comprising: Manage the status and historical information of the image processing device, and Processing is based on the managed status information and historical information. The processing based on status information and historical information includes: displaying the display content on the display unit in a single screen based on the first display information and the second display information. The first display information is used to display the abnormal information in the status information and historical information of the image processing device for each category by dividing the abnormal information into different categories. The second display information is used to display the data corresponding to the abnormal information at the corresponding position on the schematic diagram of the image processing device.

19. A program product for an image processing apparatus having a display unit, the program product causing a computer to perform steps of a method executed by the image processing apparatus, the method comprising: Manage the status and historical information of the image processing device, and Processing is based on the managed status information and historical information. The processing based on status information and historical information includes: displaying the display content on the display unit in a single screen based on the first display information and the second display information. The first display information is used to display the abnormal information in the status information and historical information of the image processing device for each category by dividing the abnormal information into different categories. The second display information is used to display the data corresponding to the abnormal information at the corresponding position on the schematic diagram of the image processing device.

Images