JP7364995B2 - image forming system - Google Patents

Description

The present invention relates to an image forming system that forms images.

As a conventional image forming apparatus, there is known one that notifies an SC (service call) when the occurrence of an abnormality is detected based on the detection value of a sensor included in the image forming apparatus (for example, Patent Document 1 reference.).

Japanese Patent Application Publication No. 2004-248256

However, in conventional image forming apparatuses, the occurrence of an abnormality is determined when the detected value of the sensor installed in the image forming apparatus is not within the normal range. There is a problem in that it is not possible to detect complex abnormalities that occur according to a series of processes based on the system.

SUMMARY OF THE INVENTION Therefore, an object of the present invention is to provide an image forming system that can detect complex abnormalities that occur in accordance with a series of processes.

The image forming system of the present invention includes a touch panel, and identifies a count of invalid touches on the touch panel based on a log of touches on the touch panel, and when the count of invalid touches on the touch panel is equal to or higher than a specific threshold. The present invention is characterized in that an abnormality in freezing of a screen displayed on the touch panel is detected.

With this configuration, the image forming system of the present invention identifies the count of invalid touches on the touch panel based on the log of touches on the touch panel, and when the count of invalid touches on the touch panel is equal to or greater than a specific threshold, the image forming system of the present invention specifies the count of invalid touches on the touch panel. Since the abnormality of freezing of the displayed screen is detected, it is possible to detect complex abnormalities that occur according to a series of flows.

The image forming system of the present invention may perform recovery processing to recover from the abnormality.

With this configuration, the image forming system of the present invention executes the recovery process to recover from the abnormality, so that it is possible to reduce the user's effort to deal with the abnormality, and to quickly recover from the abnormality. can.

In the image forming system of the present invention, the specific threshold value may be set depending on the type of the screen.

With this configuration, in the image forming system of the present invention, a threshold value for counting invalid touches for detecting an abnormality of screen freezing is set depending on the type of screen, so that the image forming system can Freezing abnormalities can be detected.

The image forming system of the present invention can detect complex abnormalities that occur in accordance with a series of flows.

1 is an external perspective view of an image forming system according to an embodiment of the present invention. 2 is a block diagram of the MFP shown in FIG. 1. FIG. 2 is a block diagram of the kiosk terminal shown in FIG. 1. FIG. 4 is a flowchart of the operation of the kiosk terminal shown in FIG. 3 when adding or deleting a schedule for execution of recovery processing to or from the schedule list. 5 is a flowchart of invalid touch count identification processing shown in FIG. 4. FIG. 6 is a flowchart of invalid touch count shaping processing shown in FIG. 5. FIG. 5 is a flowchart of the kiosk terminal screen identification process shown in FIG. 4. FIG. 5 is a flowchart of abnormal operation presence/absence shaping processing shown in FIG. 4; 3 is a flowchart of the operation of the image forming system 10 when an abnormality occurs. 10 is a diagram showing an example of a recovery process start instruction request screen displayed in the operation shown in FIG. 9. FIG.

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

First, the configuration of an image forming system according to an embodiment of the present invention will be described.

FIG. 1 is an external perspective view of an image forming system 10 according to the present embodiment.

As shown in FIG. 1, the image forming system 10 includes an MFP (Multifunction Peripheral) 20 as an image forming device, and a kiosk terminal 30 as a function reinforcement device that reinforces the functions of the MFP 20. MFP 20 and kiosk terminal 30 are placed next to each other. The image forming system 10 is installed, for example, in a retail store such as a convenience store.

The MFP 20 and the kiosk terminal 30 are connected to be able to communicate with each other via a LAN (Local Area Network). Examples of a situation where the connection between the MFP 20 and the kiosk terminal 30 is disconnected include a situation where a LAN cable for connecting the MFP 20 and the kiosk terminal 30 is not connected to at least one of the MFP 20 and the kiosk terminal 30; A situation where the power of at least one of the MFP 20 and the kiosk terminal 30 is turned off, a situation where the application software that controls communication between the MFP 20 and the kiosk terminal 30 is not running on at least one of the MFP 20 and the kiosk terminal 30, etc. exist.

FIG. 2 is a block diagram of the MFP 20.

As shown in FIGS. 1 and 2, the MFP 20 includes an operation unit 21, which is an operation device such as a button, through which various operations are input, and a printer 22, which is a printing device that prints an image on a recording medium such as paper. , a scanner 23 that is a reading device that reads images from a document, a fax communication unit 24 that is a fax device that performs fax communication with an external facsimile device (not shown) via a communication line such as a public telephone line, and a LAN, the Internet, etc. A communication unit 25, which is a communication device that communicates with an external device via a network or directly by wire or wirelessly without going through a network, and a communication device that stores various information, such as a semiconductor memory or an HDD (Hard Disk Drive). ), and a controller 27 that controls the entire MFP 20 .

The operation unit 21 includes a touch panel 21a that displays various information and allows input of various operations.

The storage unit 26 can store a device log 26a that is a log of various devices in the MFP 20, such as the operation unit 21, the printer 22, and the scanner 23. Note that the log is text that indicates records such as "the screen was touched", "processing of XX has started", and "the status has changed to XX", for example.

The control unit 27 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Memory) as a memory used as a work area for the CPU of the control unit 27. Access Memory). The CPU of the control unit 27 executes a program stored in the storage unit 26 or the ROM of the control unit 27.

The control unit 27 includes a device control unit 27a that controls various devices in the MFP 20, such as the operation unit 21, the printer 22, and the scanner 23, by executing programs stored in the storage unit 26 or the ROM of the control unit 27. and a log management unit 27b that manages the device log 26a. The log management unit 27b can transmit at least a portion of the device log 26a to the kiosk terminal 30 using, for example, the Syslog protocol.

FIG. 3 is a block diagram of the kiosk terminal 30.

As shown in FIGS. 1 and 3, the kiosk terminal 30 includes an operation unit 31 that is an operation device through which various operations are input, a photo printer 32 that is a printing device that prints photos, and a USB (Universal Serial Bus). A media reader 33 that communicates with an external storage medium such as a memory, a fee collection device 34 that collects usage fees for the image forming system 10, and a printing device that prints a receipt for the usage fee collected by the fee collection device 34. A receipt printer 35, a speaker 36, a communication unit 37 which is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly by wire or wirelessly without going through a network, and various types of devices. The kiosk terminal 30 includes a storage section 38 that is a nonvolatile storage device such as a semiconductor memory or an HDD for storing information, and a control section 39 that controls the entire kiosk terminal 30 .

The operation unit 31 includes a touch panel 31a that displays various information and allows input of various operations.

The screen size of the touch panel 31a of the kiosk terminal 30 is larger than the screen size of the touch panel 21a of the MFP 20.

The image forming system 10 shown in FIG. 1 can provide various services in response to operations on the main menu screen 41 displayed on the touch panel 31a. For example, the image forming system 10 provides a "copy" service in which an image read from a document by a scanner 23 is printed by a printer 22, and an image read from a document by the scanner 23 is sent by fax by a fax communication unit 24 (see FIG. 2). ``Fax'' service, which uses the scanner 23 to read an image from a document and saves it to an external storage medium such as a USB memory via the media reader 33, and is managed by an external data management system (not shown). The data is received via the communication unit 37 (see Figure 3) and the communication unit 25 (see Figure 2), and is printed by the printer 22 or photo printer 32 (see Figure 3) based on the received data. document data acquired from an external storage medium such as a USB memory via the media reader 33, or acquired by wireless communication from the outside by at least one of the communication unit 25 and the communication unit 37; A "document print" service that prints a document by the printer 22 based on the information obtained from an external storage medium such as a USB memory via the media reader 33, or from the outside by at least one of the communication unit 25 and the communication unit 37. This service includes a "photo print" service in which a photo is printed by the photo printer 32 based on image data acquired through wireless communication. Further, the image forming system 10 can also provide a "maintenance" service for maintaining the MFP 20 in response to a special operation on the touch panel 21a.

The photo printer 32 includes a photo outlet 32a from which printed photos are taken out.

The fee collection device 34 includes a coin input port 34a into which coins are inserted, and a coin return port 34b into which coins are returned.

The receipt printer 35 includes a receipt outlet 35a from which a printed receipt is taken out.

The storage unit 38 includes a device log 38a that is a log of various devices in the image forming system 10, such as the MFP 20, the operation unit 31, the photo printer 32, the fee collection device 34, and the speaker 36, as well as “copy”, “fax”, It is possible to store a service log 38b that is a log of various services in the image forming system 10, such as "scan", "network print", "document print", "photo print", and "maintenance".

The storage unit 38 can store a schedule list 38c indicating a schedule for processing execution.

The control unit 39 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM as a memory used as a work area for the CPU of the control unit 39. The CPU of the control unit 39 executes a program stored in the storage unit 38 or the ROM of the control unit 39.

The control unit 39 controls the image forming system 10 , such as the MFP 20 , the operation unit 31 , the photo printer 32 , the fee collection device 34 , and the speaker 36 , by executing a program stored in the storage unit 38 or the ROM of the control unit 39 . a device control unit 39a that controls various devices in the image forming system 10, and a device control unit 39a that controls various devices in the image forming system 10, such as "copy", "fax", "scan", "network print", "document print", "photo print", "maintenance", etc. A service control unit 39b that controls various services in , and a log management unit 39c that manages a device log 38a and a service log 38b are realized. The log management unit 39c can add a log received from the MFP 20 using, for example, the Syslog protocol to the device log 38a.

Note that in the image forming system 10, the touch panel 21a of the MFP 20 is basically not used. However, an MFP of the same model as the MFP 20 may be installed not only as part of an image forming system but also as a standalone MFP. Therefore, the MFP 20 includes a touch panel 21a.

Next, the operation of the image forming system 10 will be explained.

The image forming system 10 may become unusable due to an abnormality in which the screen displayed on the touch panel 31a freezes. Generally, when the screen displayed on the touch panel 31a freezes, the user often touches the screen many times to check the reaction. By detecting such an abnormal operation, the image forming system 10 can detect an abnormality in which the screen displayed on the touch panel 31a freezes.

The kiosk terminal 30 can perform recovery processing for an abnormality in which the screen displayed on the touch panel 31a freezes. One of the causes of the screen displayed on the touch panel 31a freezing is that the amount of RAM used by the control unit 39 has increased too much. The processing includes recovery of the RAM of the control unit 39. In addition, one of the reasons why the screen displayed on the touch panel 31a freezes is that a response is not returned from the outside of the kiosk terminal 30 due to a communication failure via the communication unit 37. Recovery processing for an abnormality in which the displayed screen freezes includes forced termination of communication via the communication unit 37. Furthermore, since the screen displayed on the touch panel 31a freezes due to a program malfunction, recovery processing for the abnormality in which the screen displayed on the touch panel 31a freezes includes forced termination of the service. .

First, the operation of the kiosk terminal 30 when adding or deleting a schedule for execution of recovery processing to the schedule list 38c will be described.

FIG. 4 is a flowchart of the operation of the kiosk terminal 30 when adding or deleting a schedule for execution of recovery processing to the schedule list 38c.

Each time the number of logs increases by one in at least one of the device log 38a and the service log 38b, the log management unit 39c executes the operation shown in FIG. 4 for the added log.

As shown in FIG. 4, the log management unit 39c executes invalid touch count identification processing to identify a count of invalid touches (hereinafter referred to as "invalid touch count") on the touch panel 31a (S101).

Note that an invalid touch on the touch panel 31a is a touch that does not cause the image forming system 10 to start a specific operation such as changing copy settings or starting copying, for example. On the other hand, a valid touch on the touch panel 31a is a touch that causes the image forming system 10 to start a specific operation. Therefore, a log of touches that initiate a specific action is a log of valid touches, and a log of touches that do not initiate a specific action is a log of invalid touches.

FIG. 5 is a flowchart of the invalid touch count identification process shown in FIG. 4.

As shown in FIG. 5, the log management unit 39c performs formatting to parse the date and time on the character string copied from the target log (S121). For example, if the target log is the character string "2018/1/1 00:50:20...", the log management unit 39c performs the process of S121 (2018/1/1 00:50:20, “...”) is generated. Note that "..." indicates the specific contents of the log.

After the process in S121, the log management unit 39c performs an invalid touch count formatting process on the character string generated in S121 to replace the specific content of the log with an invalid touch count (S122).

FIG. 6 is a flowchart of the invalid touch count shaping process shown in FIG.

As shown in FIG. 6, the log management unit 39c determines the type of the target log based on the specific content of the log described in the target log (S141).

When the log management unit 39c determines in S141 that the type of the target log is a log of valid touches on the touch panel 31a, the log management unit 39c sets the specific content of the log to the character string generated in S121 as "count=-". 1'' (S142), and the operation shown in FIG. 6 ends.

If the log management unit 39c determines in S141 that the type of the target log is not a log of a touch on the touch panel 31a, that is, it is a general log, the log management unit 39c inputs a specific type of the log to the character string generated in S121. The content is replaced with "count="previous invalid touch count"" (S143), and the operation shown in FIG. 6 is ended. Here, the "previous invalid touch count" is actually a specific invalid touch count included in the character string generated in the previous invalid touch count shaping process.

If the log management unit 39c determines in S141 that the target log type is a log of invalid touches on the touch panel 31a, the log management unit 39c determines whether a specific time period, such as 30 seconds, has elapsed since the previous invalid touch log. It is determined whether or not (S144).

If the log management unit 39c determines in S144 that a specific amount of time has passed since the last invalid touch log, it sets the specific content of the log to "count=1" for the character string generated in S121. (S145), and the operation shown in FIG. 6 ends.

If the log management unit 39c determines in S144 that a specific amount of time has not elapsed since the last invalid touch log, the log management unit 39c sets the specific content of the log to the character string generated in S121 by adding "count="previous Invalid touch count + 1'' (S146), and the operation shown in FIG. 6 ends. Here, "previous invalid touch count + 1" is actually the value obtained by adding 1 to the specific invalid touch count included in the character string generated in the previous invalid touch count formatting process. be.

For example, if the character string generated in S121 is (2018/1/1 00:50:20, “...”), the log management unit 39c determines that the target log type is invalid for the touch panel 31a. If it is a touch log ("invalid touch log" in S141) and a specific time has not elapsed since the previous invalid touch log (NO in S144), it is generated in the previous invalid touch count shaping process. If the string is (2018/1/1 00:50:00, count=5), in the process of S146, the string (2018/1/1 00:50:20, count=6) is generate.

As shown in FIG. 5, after the process in S122, the log management unit 39c performs formatting to delete the date and time from the character string generated in S122 (S123). For example, if the character string generated in S122 is (2018/1/1 00:50:20, count=6), the log management unit 39c generates a character string "count=6" in the process of S123. .

After the process of S123, the log management unit 39c ends the operation shown in FIG.

As shown in FIG. 4, after the process in S101, the log management unit 39c executes a kiosk terminal screen specifying process to specify the screen of the kiosk terminal 30, that is, the screen displayed on the touch panel 31a (S102).

FIG. 7 is a flowchart of the kiosk terminal screen identification process shown in FIG. 4.

As shown in FIG. 7, the log management unit 39c determines whether the type of the target log is a log of screen transition of the kiosk terminal 30 (S161).

If the log management unit 39c determines in S161 that the type of target log is a log of transition of the screen of the kiosk terminal 30, it generates the character string "screen="name of screen of kiosk terminal"" (S162). . Here, the "name of the screen of the kiosk terminal" is the name of the screen of the kiosk terminal 30 included in the target log. For example, the log management unit 39c generates a character string "screen="setting screen"" in the process of S162.

When the log management unit 39c determines in S161 that the type of the target log is not a log of transition of the screen of the kiosk terminal 30, or when the process in S162 ends, the operation shown in FIG. 7 ends.

As shown in FIG. 4, after the process of S102, the log management unit 39c stores the invalid touch count that was last identified in the invalid touch count identification process up to now, and the invalid touch count that was generated last in the kiosk terminal screen identification process up to now. and the resulting character string (S103). For example, the log management unit 39c determines that the last invalid touch count specified in the previous invalid touch count identification process is "count=6", and that the last character string generated in the previous kiosk terminal screen identification process is "count=6". If "screen="setting screen"", a character string (count=6, screen="setting screen") is generated in the process of S103.

After the processing in S103, the log management unit 39c executes an abnormal operation presence/absence formatting process that specifies the presence or absence of an abnormal operation based on the character string generated in S103 (S104).

FIG. 8 is a flowchart of the abnormal operation presence/absence shaping process shown in FIG.

As shown in FIG. 8, the log management unit 39c determines whether the invalid touch count is "-1" based on the character string generated in S103 (S181).

If the log management unit 39c determines in S181 that the invalid touch count is "-1", it replaces the character string generated in S103 with "none" (S182), and ends the operation shown in FIG. 8.

When determining in S181 that the invalid touch count is not "-1", the log management unit 39c determines whether the screen of the kiosk terminal 30 is the main menu screen 41 and the invalid touch count is 30 or more in S103. The determination is made based on the character string generated in (S183).

If the log management unit 39c determines in S183 that the screen of the kiosk terminal 30 is the main menu screen 41 but the invalid touch count is less than 30, or that the screen of the kiosk terminal 30 is not the main menu screen 41, the log management unit 39c It is determined whether the screen No. 30 is a screen other than the main menu screen 41 and the invalid touch count is 15 or more based on the character string generated in S103 (S184).

The log management unit 39c determines in S183 that the screen of the kiosk terminal 30 is the main menu screen 41 and the invalid touch count is 30 or more, or the screen of the kiosk terminal 30 is a screen other than the main menu screen 41. If it is determined in S184 that the invalid touch count is 15 or more, the character string generated in S103 is replaced with "Yes" (S185), and the operation shown in FIG. 8 is ended.

If the log management unit 39c determines in S184 that the screen of the kiosk terminal 30 is a screen other than the main menu screen 41 but the invalid touch count is less than 15, it replaces the character string generated in S103 with "Hold" ( S186), the operation shown in FIG. 8 ends.

As shown in FIG. 4, after the process of S104, the log management unit 39c stores the character string specified in the abnormal operation presence/absence shaping process of the immediately preceding S104 and the character string specified in the abnormal operation presence/absence shaping process of the previous abnormal operation presence/absence shaping process of this abnormal operation presence/absence shaping process. It is determined whether or not the specified character string is the same (S105).

If the log management unit 39c determines that they are not the same in S105, it determines the character string specified in the abnormal operation presence/absence formatting process in the immediately preceding S104 (S106).

If the log management unit 39c determines in S106 that the character string identified in the abnormal operation presence/absence shaping process in the immediately preceding S104 is "present," it adds a schedule for executing the recovery process to the schedule list 38c (S107).

If the log management unit 39c determines in S106 that the character string specified in the abnormal operation presence/absence shaping process in the immediately preceding S104 is "none", it deletes the schedule for execution of the recovery process from the schedule list 38c (S108).

The log management unit 39c determines in S105 that they are the same, or determines in S106 that the character string specified in the abnormal operation presence/absence formatting process in immediately previous S104 is "pending", or executes the process in S107 or S108. Then, the operation shown in FIG. 4 ends.

Next, the operation of the image forming system 10 when an abnormality occurs will be described.

FIG. 9 is a flowchart of the operation of the image forming system 10 when an abnormality occurs.

As shown in FIG. 9, the log management unit 39c determines whether a schedule for executing the recovery process exists in the schedule list 38c until it determines that a schedule for executing the recovery process exists in the schedule list 38c ( S201).

If the log management unit 39c determines in S201 that a schedule for executing the recovery process exists in the schedule list 38c, it determines whether the situation is such that the recovery process can be executed (S202). For example, a situation in which a recovery process start instruction request screen 42 (see FIG. 10), which will be described later, is displayed on the touch panel 31a or a situation in which the recovery process is being executed is not a situation in which the recovery process can be executed.

If the log management unit 39c determines in S202 that the situation is not such that the recovery process can be executed, it executes the process in S201.

If the log management unit 39c determines in S202 that the situation is such that the recovery process can be executed, it deletes the schedule for executing the recovery process from the schedule list 38c (S203), and issues an instruction as to whether or not to start the recovery process. A recovery process start instruction request screen 42 (see FIG. 10) requested from the user is displayed on the touch panel 31a (S204). Here, the recovery process start instruction request screen 42 has a "Yes" button 42a (see FIG. 10) for instructing to start the recovery process, and a "No" button for instructing not to start the recovery process. button 42b (see FIG. 10).

After the process of S204, the log management unit 39c determines whether the "Yes" button 42a has been pressed (S205).

When the log management unit 39c determines in S205 that the "Yes" button 42a has been pressed, it ends the display of the recovery process start instruction request screen 42 on the touch panel 31a (S206), executes the recovery process (S207), and executes the recovery process in S201. Execute the process.

If the log management unit 39c determines in S205 that the "Yes" button 42a has not been pressed, it determines whether the "No" button 42b has been pressed (S208).

If the log management unit 39c determines in S208 that the "No" button 42b has not been pressed, it executes the process in S205.

If the log management unit 39c determines in S208 that the "No" button 42b has been pressed, it ends the display of the recovery process start instruction request screen 42 on the touch panel 31a (S209), and executes the process of S201.

As described above, the image forming system 10 identifies the count of invalid touches on the touch panel 31a based on the log of touches on the touch panel 31a (S101), and determines that the count of invalid touches on the touch panel 31a is greater than or equal to a specific threshold. If this is the case (YES in S183 or YES in S184), an abnormality in which the screen displayed on the touch panel 31a freezes is detected (S185), thereby detecting a complex abnormality that occurs according to a series of steps. be able to.

Since the image forming system 10 executes recovery processing to recover from the abnormality (S207), it is possible to reduce the user's effort to deal with the abnormality and to quickly recover from the abnormality.

In the image forming system 10, a threshold value for counting invalid touches for detecting a screen freezing abnormality is set depending on the screen type (S183 and S184). Freeze abnormalities can be detected. Note that although the image forming system 10 changes the threshold value depending on whether the screen is the main menu screen 41 or not, the threshold value may be different between a plurality of screens other than the main menu screen 41.

In the present embodiment, the image forming system 10 uses the kiosk terminal 30 to detect an abnormality that occurs in the image forming system 10 . However, in the image forming system 10, the abnormality occurring in the image forming system 10 may be detected by the MFP 20, or may be detected by both the MFP 20 and the kiosk terminal 30. For example, when an abnormality occurring in the image forming system 10 is detected by both the MFP 20 and the kiosk terminal 30, the image forming system 10 detects the abnormality occurring in the MFP 20 by itself, and detects the abnormality occurring in the kiosk terminal 30 by detecting the abnormality occurring in the kiosk terminal 30. It may be detected by the terminal 30 itself.

Although the image forming apparatus of the present invention is an MFP in this embodiment, it may be an image forming apparatus other than the MFP, such as a dedicated printer, a dedicated copy machine, a dedicated fax machine, a dedicated scanner, or the like.

10 Image forming system 26a Device log 31a Touch panel 38a Device log 38b Service log

Claims (6)

Equipped with a touch panel,
A count of invalid touches on the touch panel is determined based on a log of touches on the touch panel, and when the count of invalid touches on the touch panel is equal to or greater than a specific threshold, freezing of the screen displayed on the touch panel is determined. An image forming system that detects an abnormality,
An invalid touch on the touch panel is a touch that does not cause the image forming system to initiate a specific operation ;
The image forming system executes a recovery process to recover from the abnormality,
adding a schedule for executing the recovery process when the abnormality is detected;
If a schedule for executing the recovery process exists and the situation is such that the recovery process can be executed, delete the schedule and execute the recovery process;
An image forming system characterized in that the schedule is deleted when the newly added log is a log of valid touches on the touch panel . Equipped with a touch panel,
A count of invalid touches on the touch panel is determined based on a log of touches on the touch panel, and when the count of invalid touches on the touch panel is equal to or greater than a specific threshold, freezing of the screen displayed on the touch panel is performed. An image forming system that detects an abnormality,
An invalid touch on the touch panel is a touch that does not cause the image forming system to initiate a specific operation;
The image forming system executes a recovery process to recover from the abnormality,
adding a schedule for executing the recovery process when the abnormality is detected;
When a schedule for executing the recovery process exists and the recovery process is executable, the schedule is deleted and the user is requested to instruct whether or not to start the recovery process. displaying a process start instruction request screen on the touch panel;
An image forming system characterized in that the schedule is deleted when the newly added log is a log of valid touches on the touch panel . 3. The image forming system according to claim 2, wherein a situation in which the recovery process start instruction request screen is displayed on the touch panel is determined to be a situation in which the recovery process cannot be executed. 4. The image forming system according to claim 1, wherein a situation in which the recovery process is being executed is determined to be a situation in which the recovery process is not executable. If the newly increased log is a log of invalid touches on the touch panel, and a certain amount of time has passed since the previous log of invalid touches on the touch panel, a count of invalid touches on the touch panel. The image forming system according to any one of claims 1 to 4, wherein: 1. 6. The image forming system according to claim 1, wherein the specific threshold value is set depending on the type of the screen.

Images