JP6623901B2 - Reboot system and reboot method - Google Patents

Description

  The present invention relates to a reboot system, and more particularly, to a reboot system and a reboot method for rebooting a power supply when a communication failure occurs between an operation unit and a control unit in a device.

2. Description of the Related Art It is known that in a device such as an image forming apparatus, a connection check is performed to determine whether or not there is a connection between a controller board as a control unit and an operation unit of the controller board. This connection confirmation causes an error message to be displayed on the operation unit when the communication between the operation unit that regularly communicates and the CPU (Central Processing Unit) in the controller board is temporarily interrupted.
In this case, a recovery operation for communication connection is performed. Conventionally, a user turns off / on the power supply, or replaces a controller board and peripheral components by a service person. For this reason, there is a problem that user's labor and service cost are required at the time of restoration.

  To solve this problem, for example, Japanese Patent Application Laid-Open No. 2005-219247 discloses, for the purpose of reducing the trouble of the user, a failure that is likely to be recovered by turning off / on the power supply and is targeted for reboot. A means for detecting a failure and a system for rebooting hardware resources and programs are disclosed. This system automatically reboots at the time of recovery. However, there is a problem that a serviceman call (SC) always occurs when a communication failure occurs between the operation unit and the controller.

  The present invention has been made in view of the above-mentioned conventional problems, and an object of the present invention is to make it possible to automatically perform a reboot in a reboot system that performs a reboot when a communication failure occurs between an operation unit and a control unit of a device. And to reduce the user's labor and service cost.

The present invention has an operation unit in a device, a main control unit that controls the device based on communication with the operation unit, and a sub-control unit that controls a power supply unit of the device. A reboot system that performs a reboot when a communication failure occurs with a main control unit, wherein the operation unit has an operation unit control unit, and the operation unit control unit communicates with the main control unit, A first communication monitoring unit that monitors a communication failure between the main control unit and the operation unit control unit; and when the first communication monitoring unit determines that the communication is poor, the fact is notified to the sub control unit. Notifying means for notifying, the sub-control means, when notified of communication failure from the operation unit, a reboot control means for making a reboot request to the power supply unit, the main control means and the main control means Communication with connected storage means Second communication monitoring means for monitoring the presence / absence of the communication, wherein the sub-control means determines that the first communication monitoring means has the communication failure, and the second communication monitoring means has the main control means On the condition that it is determined that there is no communication with the storage unit, the reboot request is made, and the sub-control unit sets the communication between the main control unit and the storage unit by the second communication monitoring unit. When it is determined that there is, a communication stop control unit that stops and controls communication between the main control unit and the storage unit, and the second communication monitoring unit controls communication between the main control unit and the storage unit. When it is determined that the main control unit has not stopped for a predetermined time, the main control unit controls the main control unit to stop communication with the storage unit on condition that a control signal applied to the storage unit is asserted. Communication stop control means Which is a reboot system according to claim.

  According to the present invention, in a reboot system that performs a reboot when a communication failure occurs between an operation unit and a control unit of a device, the reboot can be automatically performed, so that user's labor and service cost can be reduced as compared with the related art. .

FIG. 1 is a block diagram illustrating an overall configuration of a reboot system according to a first embodiment of the present invention. FIG. 5 is a flowchart illustrating an automatic reboot processing procedure in the reboot system according to the first embodiment of the present invention. It is a flowchart which shows the automatic reboot processing procedure in the reboot system which concerns on 2nd Embodiment of this invention. FIG. 3 is a waveform diagram showing HIGH and LOW of a CS signal. FIG. 14 is a flowchart illustrating an automatic reboot processing procedure in the reboot system according to the third embodiment of the present invention. FIG. 3 is a block diagram showing a circuit configuration for a sub CPU to mask a CS signal of a main CPU. It is a block diagram showing the whole reboot system composition concerning a 4th embodiment of the present invention. FIG. 14 is a flowchart illustrating a basic automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 16 is a flowchart illustrating a first automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 15 is a flowchart illustrating a second automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 21 is a flowchart illustrating a third automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 21 is a flowchart illustrating a fourth automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 18 is a flowchart illustrating a first example of a procedure for setting whether to execute a first automatic reboot processing procedure and a second automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention. FIG. 18 is a flowchart illustrating a second example of a procedure for setting whether to execute the first automatic reboot processing procedure and the second automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described, but before that, embodiments of the present invention will be schematically described. That is, the embodiment of the present invention has the following features when performing a reboot when a communication failure occurs between the operation unit and the control unit in the device.
In short, in the embodiment of the present invention, a sub CPU different from the main CPU is provided in the control unit, and a communication unit is provided in the operation unit and the sub CPU. Here, the main CPU and the operation unit communicate periodically, but if the main CPU stops operating for some reason, the main CPU does not respond to the periodic communication. In this case, when detecting that there is no response from the main CPU, the operation unit notifies the sub CPU. The sub CPU having received the notification from the operation unit automatically issues a reboot request to the power supply device. In response to the reboot request, the power supply is turned off / on (from the ON state to the OFF state to the ON state), and the system is rebooted.

Hereinafter, embodiments of a reboot system according to the present invention will be described with reference to the accompanying drawings.
[First Embodiment]
FIG. 1 is a block diagram showing the overall configuration of the reboot system according to the first embodiment of the present invention.
In the present embodiment, the reboot system 1 includes a controller board 10, an operation unit 12, and a power supply device 14 as a power supply unit, as illustrated.
The controller board 10 has a main CPU 100 as a main control unit, a sub CPU 102 as a sub control unit, and a nonvolatile memory 104, and the operation unit 12 has an operation unit CPU 120 as an operation unit control unit.
The power supply device 14 is connected to the main CPU 100, the sub CPU 102, and the operation unit CPU 120 of the controller board 10, respectively, and has a power supply line that supplies power to each of the controller board 10 and the operation unit 12. For this reason, power control of the power supply device 14 that supplies power to each device of the image forming apparatus according to instructions from the controller board 10 (main CPU 100 and sub CPU 102) is enabled. The main CPU 100 controls the entire apparatus based on communication with the operation unit CPU 120.

The controller board 10 and the operation unit 12 are connected by a main CPU 100 and an operation unit CPU 120, and perform communication at regular intervals, and perform communication while constantly confirming the connection between them. Further, an operation unit CPU 120 and a sub CPU 102 are connected to notify a communication failure between the operation unit 12 and the controller board 10.
Here, the operation unit CPU 120 of the operation unit 12 monitors communication between the operation unit CPU 120 and the main CPU 100 and, when detecting a communication failure, notifies the sub CPU 102 of the communication unit (the first communication monitoring unit 120a and the notification unit). 120b).

The main CPU 100 in the controller board 10 is connected to the nonvolatile memory 104, and the sub CPU 102 monitors communication (connection) between the main CPU 100 and the nonvolatile memory 104 (second communication monitoring means 102a). Function as
The sub CPU 102 further requests the main CPU 100 to stop the communication (connection) of the non-volatile memory 104 to stop the communication (connection), and issues a reboot request to the power supply 14 to turn off / off the power supply 14. It also functions as a reboot control unit 102c that performs on-control.
That is, these units of the operation unit CPU 120 and the sub CPU 102 are function realizing units that are realized by causing each computer configured by the operation unit CPU 120 and the sub CPU 102 to read a program.

  The nonvolatile memory 104 includes, for example, a non-volatile random access memory (NVRAM) 104a, a hard disk (HDD) 104b, a NOR flash memory 104c, and an electrically erasable programmable read-only memory (EEPROM) 104d as shown in the figure. .

FIG. 2 is a flowchart showing an automatic reboot processing procedure in the reboot system according to the first embodiment of the present invention. The automatic reboot processing procedure by the reboot system according to the present embodiment will be described with reference to this flowchart.
In the reboot system 1 shown in FIG. 1, when the power supply 14 is turned on, the main CPU 100 in the controller board 10 and the operation unit CPU 120 communicate with each other at regular intervals (step S101).
Here, if there is no response from the main CPU 100 to the communication (access) from the operation unit 12, (the first communication monitoring unit 120a of) the operation unit CPU 120 determines that there is a communication failure (step S101: No). ). The operating unit CPU 120 that has determined that the communication has failed (the notifying unit 120b thereof) notifies the sub CPU 102 in the controller board 10 of the communication failure (step S102).

Subsequent processing depends on the number of reboots performed.
In other words, the sub CPU 102 records the number of reboots performed as a count. If the number of reboots is equal to or greater than a certain number (N times) (step S103: Yes), the reboot is repeated if an error cannot be avoided by rebooting. In order to prevent such a situation, an error message is notified to the operation unit 12 without specifically issuing a reboot request, specifically, for example, a serviceman call is displayed (step S104), and this process ends.
On the other hand, if the number of reboots performed is less than the given number of times (step S103: No), the sub CPU 102 (the second communication monitoring unit 102a) determines whether communication between the main CPU 100 and the non-volatile memory 104 is present (exists). No) is confirmed (step S105).
In step S105, the sub CPU 102 confirms communication at regular intervals, and when confirming that the communication between the main CPU 100 and the nonvolatile memory 104 has been stopped (absent), reboots and shifts to start.

Specifically, for example, when the sub CPU 102 confirms communication between the main CPU 100 and the non-volatile memory 104, a time limit (constant time) is provided (step S106), and within the time limit (step S106: No), If no communication is confirmed (step S109: No), the sub CPU 102 (reboot control means 102c) issues a reboot request to the power supply device 14 and performs off / on control of the power supply device 14 (step S110). Reboot the entire system and go to start.
If the communication is confirmed within the time limit (step S106: No) at step S106 (there is communication) (step S109: Yes), the process returns to step S105, waits for the time limit to elapse, and continues until the time limit elapses. If the communication is continued (step S106: Yes), the sub CPU 102 (the communication stop control means 102b) requests the main CPU 100 to stop the communication (step S107). Here, the communication stop request is, for example, to assert a reset signal to the main CPU 100, thereby stopping the communication of the main CPU 100 with the nonvolatile memory 104 (step S108). After the communication is stopped, the sub CPU 102 performs off / on control of the power supply 14 (step S110), reboots the entire system, and shifts to start.

[Second embodiment]
In the first embodiment, when communication between the main CPU 100 and the non-volatile memory 104 has continued for a certain period of time, the sub CPU 102 issues a communication stop request to the main CPU 100 to stop communication.
However, in this case, if the power supply of the power supply device 14 is turned off while the nonvolatile memory 104 is being accessed (communicated), data in the nonvolatile memory 104 may be damaged. Therefore, in the second embodiment, when communication between the main CPU 100 and the nonvolatile memory 104 is continued (when communication is performed), the control signal (here, the CS signal) applied to the nonvolatile memory 104 is changed. When asserted, that is, on that condition, the sub CPU 102 requests the main CPU 100 to stop communication. The description of the second embodiment is somewhat simplified, but is otherwise the same as the first embodiment.

FIG. 3 is a flowchart showing an automatic reboot processing procedure in the reboot system according to the second embodiment of the present invention.
When the power supply device 14 is turned on, the main CPU 100 and the operation unit CPU 120 in the controller board 10 perform communication at regular intervals. Here, when there is no response from the main CPU 100 to the communication (access) from the operation unit 12, the operation unit CPU 120 determines that the communication is defective (step S201: No). Next, the operation unit CPU 120 notifies the sub CPU 102 in the controller board 10 of the communication failure that the communication failure has been determined (step S202).

Subsequent processing depends on the number of reboots performed.
That is, the sub CPU 102 records the number of reboots executed as a count. If the number of reboots is equal to or greater than a certain number (N times) (step S203: Yes), the sub CPU 102 does not issue a reboot request and sends a serviceman to the operation unit 12. The call is displayed (step S204), and this process ends.
On the other hand, if the number of reboots is less than the certain number (step S203: No), the sub CPU 102 checks whether there is communication between the main CPU 100 and the nonvolatile memory 104 (step S205). In step S205, the communication is confirmed at regular intervals, and if it is confirmed that the communication has stopped (absent), the entire system is similarly rebooted (to start).

  Specifically, for example, when the sub CPU 102 checks the communication between the main CPU 100 and the nonvolatile memory 104, a time limit (a fixed time) is provided (step S206), and the communication is performed within the time limit (step S206: No). If the absence is confirmed (step S210: No), the sub CPU 102 issues a reboot request to the power supply device 14, executes off / on control of the power supply device 14 (step S211), reboots the entire system, and starts. Move to.

In step S206, within the time limit (step S206: No), if communication is confirmed (step S210: Yes), the process returns to step S205 and waits for the elapse of a certain time (step S206: Yes). If the communication has continued until the elapse, the process waits until the CS (Chip Select) signal of the main CPU 100 is not LOW (step S207). Then, when it is no longer LOW (that is, it becomes HIGH; see FIG. 4) (step S207: No), the sub CPU 102 requests the main CPU 100 to stop communication (step S208).
Here, the communication stop request is, for example, to assert a reset signal to the main CPU 100 as in the first embodiment, thereby stopping the operation of the main CPU 100 (step S209). After the communication is stopped, the sub CPU 102 issues a reboot request to the power supply device 14, performs off / on control of the power supply device 14 (step S <b> 211), reboots the entire system, and shifts to start.

FIG. 4 is a waveform diagram showing HIGH and LOW of the CS signal.
In the second embodiment, the sub CPU 102 checks the CS signal before requesting the main CPU 100 to stop communication. In that case, while the CS signal of the main CPU 100 indicates LOW in FIG. It is determined that the non-volatile memory 104 is being accessed. For this reason, it is confirmed that the CS signal (CS_N) is HIGH, that is, a communication stop request is made on that condition.
In the figure, x indicates that communication stop request is impossible, and o indicates that communication stop request is possible.
According to the second embodiment, it is possible to eliminate the possibility that the power of the power supply device 14 is turned off while the non-volatile memory 104 is being accessed and the data is destroyed.

[Third Embodiment]
Next, a third embodiment of the present invention will be described.
In the first and second embodiments, a communication stop request is issued from the sub CPU 102 to the main CPU 100 to stop communication between the main CPU 100 and the nonvolatile memory 104. On the other hand, in the third embodiment, the access between the main CPU 100 and the nonvolatile memory 104 is stopped by masking the CS signal transmitted from the main CPU 100 to the nonvolatile memory 104. That is, when the communication between the main CPU 100 and the non-volatile memory 104 has not been stopped for a certain period of time, the sub CPU 102 (a CS signal masking unit) makes a communication stop request by masking the CS signal to stop the communication. The third embodiment differs from the first and second embodiments in this point, and is similar in other respects.

FIG. 5 is a flowchart showing an automatic reboot processing procedure in the reboot system according to the third embodiment of the present invention. The processing procedure of the automatic reboot by the reboot system will be described with reference to this flowchart.
If there is no response from the main CPU 100 to the communication from the operation unit 12 (step S301: No), the operation unit CPU 120 determines that the communication is defective, and the operation unit CPU 120 that determines that the communication is defective is stored in the controller board 10. The sub CPU 102 is notified of the communication failure (step S302).

Subsequent processing depends on the number of reboots performed.
That is, the sub CPU 102 records the number of reboots executed as a count. If the number of reboots is equal to or greater than a predetermined number (N times) (step S303: Yes), the sub CPU 102 does not issue a reboot request and the service unit 12 The call is displayed (step S304), and this process ends.
In this case, the sub CPU 102 performs a reboot, but the sub CPU 102 records the number of reboots of the power supply 14 due to a communication failure. If the number of reboots is equal to or greater than a certain number (step S303: Yes), the reboot is performed. First, a serviceman call is displayed on the operation unit 12 (step S304), and this process ends.
If the number of reboots is less than the predetermined number in step S303 (step S303: No), the process proceeds to a step (step S305) in which the sub CPU 102 checks whether there is communication with the nonvolatile memory 104 of the main CPU 100.
In step S305, communication is confirmed at regular intervals, and if it is confirmed that communication has stopped (nothing), the entire system is similarly rebooted (to start).

  Specifically, for example, when the sub CPU 102 confirms communication between the main CPU 100 and the nonvolatile memory 104, a time limit is provided (step S306), and there is no communication within the time limit (constant time) (step S306: No). Is confirmed (step S309: No), the sub CPU 102 issues a reboot request to the power supply device 14, executes off / on control of the power supply device 14 (step S310), reboots the entire system, and proceeds to start. Transition.

  In step S306, if communication is confirmed within the time limit (step S306: No) (step S309: Yes), the process returns to step S305, waits for the elapse of a certain time, and communication continues until the elapse of the time limit. If yes (step S306: Yes), the sub CPU 102 (control signal masking means) masks the control signal, here the CS signal (step S307). Thereby, the communication between the main CPU 100 and the nonvolatile memory 104 stops (step S308). After the communication is stopped, the sub CPU 102 performs off / on control for the power supply 14 (step S310), reboots the entire system, and shifts to start.

FIG. 6 is a block diagram showing a circuit configuration for the sub CPU 102 to mask the CS signal of the main CPU 100.
That is, in the reboot system 1 of FIG. 1, the NAND circuit 101 is arranged between the main CPU 100, the sub CPU 102, and the nonvolatile memory 104.
Here, upon receiving the CS signal of the main CPU 100 and confirming that there is communication between the main CPU 100 and the nonvolatile memory 104, the sub CPU 102 outputs a CS signal masking signal (CS_MASK_N) to the NAND circuit 101. In this case, the CS signal (CS_N) on the nonvolatile memory 104 side is set to HIGH regardless of whether the output of the main CPU 100 is HIGH or LOW, and the access to the nonvolatile memory 104 is stopped.
As described above, also in the third embodiment, it is possible to eliminate the possibility that the power of the power supply device 14 is turned off while the nonvolatile memory 104 is being accessed and the data is destroyed.

[Fourth embodiment]
First, a fourth embodiment of the present invention will be schematically described. In the fourth embodiment of the present invention, when a communication failure occurs between the controller board and the operation unit, the system is automatically rebooted in response to a reboot request to the power supply unit by the sub CPU in the controller board. At the time of automatic reboot, the sub CPU records the reboot history in the nonvolatile area. After an automatic reboot, the system is not guaranteed to be healthy. Therefore, the sub CPU monitors the elapse of time or the number of times the power is turned on / off, so that a period in which the sub CPU cannot be rebooted continuously is provided.

<Overall configuration of reboot system>
FIG. 7 is a block diagram showing the overall configuration of the reboot system according to the fourth embodiment of the present invention.
In this embodiment, the reboot system 2 includes a controller board 20 and an operation unit 21 as illustrated. This reboot system is also applied to, for example, an image forming apparatus as in the first embodiment (FIG. 1).

  The controller board 20 includes a main CPU 201 as a main control unit, a sub CPU 202 as a sub control unit, and a power supply circuit 203 as a power supply unit. The operation unit 21 includes an operation panel 211 as an operation display unit and an operation unit An operation unit CPU 212 is provided as control means.

  The power supply circuit 203 is connected to the main CPU 201 and the sub CPU 202 of the controller board 20 and the operation unit CPU 212 of the operation unit 21, respectively, and a power supply line for supplying power to each of the controller board 20 and the operation unit 21 is provided. Is provided. For this reason, the power of the power supply circuit 203 that supplies power to each device of the image forming apparatus can be controlled according to an instruction from the controller board 20 (the main CPU 201 and the sub CPU 202). The main CPU 201 controls the entire apparatus based on communication with the operation unit CPU 212.

The controller board 20 and the operation unit 21 are connected to each other by the main CPU 201 and the operation unit CPU 212, perform communication at regular intervals, and perform communication while constantly checking the connection with each other. The operation unit CPU 212 and the sub CPU 202 are connected to each other to notify a communication failure between the operation unit 21 and the controller board 20.
Here, the operation unit CPU 212 of the operation unit 21 functions as a first communication monitoring unit 212a, a notification unit 212b, a setting information input screen generation unit 212c, and a setting information acquisition unit 212d.

The first communication monitoring unit 212a monitors communication between the operation unit CPU 212 and the main CPU 201 and detects a communication failure, similarly to the first communication monitoring unit 120a in the first embodiment. When the first communication monitoring unit 212a detects a communication failure, the notification unit 212b notifies the sub CPU 202 of the communication failure (transmission of a communication failure notification signal). The notifying unit 212b notifies the sub CPU 202 of the setting information (details will be described later) acquired by the setting information acquiring unit 212d (transmission of a setting information notification signal).
The setting information input screen generation unit 212c generates an image for displaying a setting information input screen (details will be described later) on the operation panel 211. The setting information acquisition unit 212d acquires the setting information input from the setting information input screen.

The sub CPU 202 of the controller board 20 functions as a power monitoring unit 202a, a timer 202b, a counter 202c, and a reboot control unit 202d.
The power supply monitoring unit 202a monitors the state (ON, OFF, etc.) of the power supply circuit 203. The timer 202b counts various times (specific examples will be described later). The counter 202c counts the number of occurrences of various events (specific examples will be described later). The reboot control unit 202d issues a reboot request to the power supply circuit 203.

  These units of the operation unit CPU 212 and the sub CPU 202 are function realizing units realized by causing each computer configured by the operation unit CPU 212 and the sub CPU 202 to read a program.

  The sub CPU 202 has a nonvolatile area 202e composed of an EEPROM or the like. The non-volatile area 202e is provided with a reboot flag storage unit 202f, a start count storage unit 202g, and an energy saving return count storage unit 202h. The sub CPU 202 controls the reboot flag storage unit 202f (flag on / off, etc.), controls the storage value of the activation count storage unit 202g (increment, clear, etc.), and controls the storage value of the energy saving return count storage unit 202h (increment) , Clear, etc.). Note that a non-volatile memory may be connected to the outside of the sub CPU 202, and a reboot flag storage unit 202f, a start count storage unit 202g, and an energy saving return count storage unit 202h may be provided therein.

  In addition, when the sub CPU 202 is notified of the communication failure from the operation unit CPU 212 and transmits the error notification signal to the operation unit CPU 212 when the reboot flag is ON (hereinafter, also referred to as “standing” or “present”). I do. The operation unit CPU 212 causes the operation panel 211 to display error information (such as a serviceman call) based on the error notification signal.

<Basic automatic reboot processing procedure>
FIG. 8 is a flowchart showing a basic automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.

  As described above, the main CPU 201 and the operation unit CPU 212 in the controller board 20 perform communication at regular intervals. Then, when there is no response from the main CPU 201 to the communication from the operation unit CPU 212, (the first communication monitoring unit 212a of) the operation unit CPU 212 determines that there is a communication failure (step S401: No). The operation unit CPU 212 (a notification unit 212b thereof) notifies the sub CPU 202 in the controller board of the communication failure (step S402).

  The sub CPU 202 (reboot control means 202d) sets a reboot flag at the time of reboot due to communication failure. If the reboot flag is set (step S403: Yes), the sub CPU 202 sends an error notification signal to the operation unit CPU 212. It transmits (step S404). The operation unit CPU 212 displays a serviceman call on the operation panel 211 based on the error notification signal. If the reboot flag has not been set (step S403: No), a reboot flag is set in the reboot flag storage unit 202f in the nonvolatile area 202e (step S405), and a reboot request is issued to the power supply circuit 203 (step S406). In response to the reboot request, the power supply circuit 203 is turned off / on, and the reboot is executed.

<First automatic reboot processing procedure>
FIG. 9 is a flowchart showing a first automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.
This procedure is based on the assumption that the sub CPU 202 is driven by the power supplied by inserting the AC plug. In this case, since the power of the sub CPU 202 is not turned off while the AC plug is inserted, the time can be counted by the timer 202b.
It is assumed that when the communication between the controller board 20 and the operation unit 21 is interrupted, the system performs the first reboot according to the flow shown in FIG. For example, by setting the release time of the reboot flag to 24 hours, it is possible to create a period in which the reboot is not performed for 24 hours after the reboot is performed once. As a result, errors frequently occur, and it is possible to suppress a reboot that the user does not intend.

Hereinafter, description will be given along a flowchart.
The sub CPU 202 determines whether the reboot flag is set (step S501).
If the reboot flag is not set (step S501: No), the sub CPU 202 enters a state of waiting for a communication failure notification from the operation unit CPU 212 (step S506: No → step S501).
If the reboot flag is on (step S501: Yes), the sub CPU 202 starts (starts) the timer 202b (step S502). However, if the timer 202b is already running, step S502 is not performed.

  After the start of the timer, the time is checked, and the elapse of the time is determined (step S503). If the predetermined time has elapsed (step S503: YES), the timer 202b is stopped (step S504), and the reboot flag is cleared (step S505). If the predetermined time has not elapsed (step S503: No), the elapse of the time is counted while waiting for a communication failure notification from the operation unit CPU 212 (step S506: No → Step S501: Yes → Step S503).

  When a communication failure notification is received from the operation unit CPU 212 (step S506: Yes), (the reboot control unit 202d of) the sub CPU 202 determines the operation based on the presence or absence of the reboot flag. That is, when the reboot flag is present (is standing) (Step S507: Yes), it is determined that the fixed time has not elapsed after the reboot, and the error notification to the operation unit 21 is performed without rebooting again (Step S507). Step S508). If there is no reboot flag (step S507: No), a reboot flag is set in the non-volatile area 202e of the sub CPU 202 (step S509), and a reboot request is issued to the power supply circuit 203 (step S510).

<Second automatic reboot processing procedure>
FIG. 10 is a flowchart showing a second automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.
This procedure is a procedure assuming that the sub CPU 202 is driven by a power supplied by inserting an AC plug or a power that is turned off in a shutdown state (switch on / off). The power supply circuit 203 is monitored when driven by a power supply supplied by insertion of an AC plug, and the number of times of activation is counted by a counter 202c when driven by a power supply cut off in a shutdown state, thereby turning on / off the power supply. Can be counted.
For example, in the case of driving with a power supply that can be cut off by shutdown, if the sub CPU 202 is not to be rebooted until the power supply is turned off → on three times, a reboot flag is set at the time of rebooting, and the number of starts counted by the counter 202c is stored in the nonvolatile area This can be realized by writing in the start count storage unit 202g of 202e, and then releasing the reboot flag when the power is turned on three times (from power off to on).

Hereinafter, a case of driving with a power supply that is shut down will be described with reference to a flowchart.
After turning on the power (on), the sub CPU 202 first determines whether or not the reboot flag is set (step S601). If the reboot flag has not been set (step S601: No), the sub CPU 202 enters a state of waiting for a communication failure notification from the operation unit CPU 212 (step S606). When the reboot flag is set (step S601: Yes), the number of boots held by the number-of-boots storage unit 202g in the non-volatile area 202e is incremented by one (step S602).

  Thereafter, it is determined whether or not the number of times of activation is equal to or more than a predetermined value (N in this case) (step S603). If the number of times of activation is less than the predetermined value (step S603: No), it is in a state of waiting for a communication failure notification from the operation unit CPU 212 (step S606). If the number of starts is equal to or more than the predetermined value (step S603: Yes), the number of starts stored in the number-of-starts storage unit 202g is cleared (step S604), and the reboot flag stored in the reboot flag storage unit 202f is released. (Step S605) is performed.

  After that, it is in a state of waiting for a communication failure notification from the operation unit CPU 212 (step S606). When a communication failure notification is received from the operation unit CPU 212 (step S606: Yes), it is determined whether or not the reboot flag is set (step S607). That is, when the reboot flag is set (step S607: Yes), an error notification is performed to the operation unit CPU 212 without rebooting (step S608). If the reboot flag has not been set (step S607: No), a reboot flag is set (step S609), and a reboot request is issued to the power supply circuit 203 (step S610). In response to the reboot request, the power of the sub CPU 202 is turned off by the power supply circuit 203 and turned on again.

<Third automatic reboot processing procedure>
FIG. 11 is a flowchart showing a third automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.
This procedure is based on the assumption that the sub CPU 202 is driven by a power supplied by inserting an AC plug, a power that is turned off in a shutdown state, or a power that is turned off in an energy saving state. For example, the power supply circuit 203 is monitored when driven by a power supply supplied by inserting an AC plug, and the power supply is turned off and on by counting when the power supply is turned off in an energy-saving state. When the number of times of return is less than a certain number, a period during which a reboot cannot be performed can be created.

Hereinafter, a case of driving with a power supply that is shut down will be described with reference to a flowchart.
The sub CPU 202 monitors the power supply circuit 203 and determines whether or not a power supply that is turned off in the energy saving state (hereinafter, energy saving power supply) is off (step S701). If the energy-saving power supply is on (step S701: No), a state of waiting for a communication failure notification from the operation unit CPU 212 is waited (step S708), and steps S701 and S708 are repeated until the energy-saving state is reached.

If the energy-saving power supply is off (Step S701: Yes), the process waits until the energy-saving power supply is turned on (Step S702). When the energy-saving power supply is turned on (Step S702: Yes), it is confirmed whether or not the reboot flag is set (Step S703).
If the reboot flag has not been set (step S703: No), a state of waiting for a communication failure notification from the operation unit CPU 212 is waited (step S708), and steps S701 and S708 are repeated until an energy saving state is achieved.
If the reboot flag is set (Step S703: Yes), the number of times of energy saving return stored in the energy saving return number storage unit 202h is incremented by 1 (Step S704), and the number of times of energy saving return is equal to or more than a predetermined value (here, N). It is determined whether or not (step S705).

If the number of times of energy saving return is less than the predetermined value (step S705: No), the state of waiting for communication failure notification from the operation unit CPU 212 is waited (step S708), and steps S701 and S708 are repeated until the state of energy saving is reached.
If the number of times of energy saving return is equal to or greater than the predetermined value (step S705: Yes), the number of times of energy saving return stored in the energy saving return number storage unit 202h is cleared (step S706), and the reboot held by the reboot flag storage unit 202f is performed. The flag is cleared (step S707). After that, a state of waiting for a communication failure notification from the operation unit CPU 212 is set (step S708), and steps S701 and S708 are repeated until an energy saving state is set.

  When the communication failure notification is received from the operation unit CPU 212 (step S708: Yes), it is determined whether or not the reboot flag is set (step S709). That is, when the reboot flag is set (step S709: Yes), an error notification is performed to the operation unit CPU 212 without rebooting (step S710). If the reboot flag has not been set (step S709: No), a reboot flag is set (step S711), and a reboot request is issued to the power supply circuit 203 (step S712). In response to the reboot request, the power of the sub CPU 202 is turned off by the power supply circuit 203 and turned on again.

<Fourth automatic reboot processing procedure>
In the first automatic reboot processing procedure described above, while the AC plug is inserted, the power of the sub CPU 202 is turned on, so that the power consumption increases. The second automatic reboot procedure cannot cope with energy saving. Further, if there is a user who does not perform the shutdown, once the reboot is performed, there is a possibility that the reboot cannot be performed thereafter. The third automatic reboot processing procedure may not be able to cope with the case where there is a user who does not use the energy saving mode.

Therefore, in the fourth automatic reboot processing procedure, these problems are solved by combining the first to third automatic reboot processing procedures. This procedure is a procedure on the assumption that the sub CPU 202 is driven by a power supplied by inserting an AC plug, a power that is cut off in a shutdown state, or an energy-saving power.
FIG. 12 is a flowchart showing a fourth automatic reboot processing procedure in the reboot system according to the fourth embodiment of the present invention.

For example, when driven by the energy-saving power supply, the sub CPU 202 counts the number of times of activation of itself and counts time. Here, it is assumed that the period in which the reboot cannot be performed is set to the number of times of starting: 10 times and the time: 24 hours, so that the reboot cannot be continuously performed until one of the conditions is satisfied. This mechanism assumes the following cases (i) and (ii).
(i) When the User Uses the Energy-Saving Mode and Shutdown The sub-CPU 202 counts its own power off → on by the counter 202c, thereby realizing a period in which the sub CPU 202 cannot reboot until the number of startups becomes ten.
(ii) When the user does not use the energy saving mode or the shutdown mode. The sub CPU 202 counts the time with the timer 202b, and realizes a period in which the sub CPU 202 cannot reboot until 24 hours have elapsed.

Hereinafter, the case of driving with the energy-saving power supply will be described along the flowchart.
After turning on the power, the sub CPU 202 first determines whether or not the reboot flag is set (step S801). If the reboot flag has not been set (step S801: No), a state of waiting for a communication failure notification from the operation unit CPU 212 is entered (step S806: No → step S812).

If the reboot flag is set (step S801: Yes), the number of boots held by the number-of-boots storage unit 202g in the nonvolatile area 202e is incremented by 1 (step S802), and the number of boots is set to a predetermined value (here, N) It is determined whether or not it is equal to or greater than (step S803).
If the number of starts is equal to or greater than the predetermined value (step S803: Yes), the number of starts is cleared (step S804), and the reboot flag is cleared (step S805). After that, it is in a state of waiting for a communication failure notification from the operation unit CPU 212 (step S806: No → step S812).
If the number of times of activation is less than the predetermined value (step S803: No), the sub CPU 202 starts (starts) the timer 202b (step S807). However, if the timer 202b is already running, step S807 is not performed. After the start of the timer, the time is checked, and the elapse of the time is determined (step S808).

If the predetermined time has elapsed (Step S808: Yes), the timer is stopped (Step S809), the number of startups is cleared (Step S810), and the reboot flag is cleared (Step S811). After that, it is in a state of waiting for a communication failure notification from the operation unit CPU 212 (step S812).
If the predetermined time has not elapsed (step S808: No), the elapse of the time is counted while waiting for a communication failure notification from the operation unit CPU 212 (step S812: No → step S806 → step S808). When a communication failure notification is received from the operation unit CPU 212 (step S812: Yes), it is determined whether or not the reboot flag is set. That is, when the reboot flag is set (Step S813: Yes), an error notification is performed to the operation unit CPU 212 without rebooting (Step S814). If the reboot flag has not been set (step S813: No), a reboot flag is set (step S815), and a reboot request is issued to the power supply circuit 203 (step S816). In response to the reboot request, the power of the sub CPU 202 is turned off by the power supply circuit 203 and turned on again.

<Setting of First Automatic Reboot Processing Procedure and Second Automatic Reboot Processing Procedure (Part 1)>
FIG. 13 is a flowchart showing a first example of a procedure for setting whether to execute the first automatic reboot processing procedure and the second automatic reboot processing procedure.

  When the user performs an operation of selecting a setting information input screen (hereinafter, setting screen) from the operation panel 211 (step S901: Yes), the setting screen is generated by the setting information input screen generating unit 212c of the operation unit CPU 212, and the operation is performed. Displayed on panel 211. The setting information acquisition unit 212d of the operation unit CPU 212 determines whether or not the user has selected (input) to use the reboot flag release based on the number of starts on the setting screen (step S902).

  If the user selects to use (step S902: Yes), it is set to use (step S903), and if not to use (step S902: No), it is set not to use (step S902: No). Step S904).

  Next, the setting information acquisition unit 212d determines whether or not the user has selected (input) on the setting screen to use the reboot flag release by the timer (step S905). If the user selects to use (step S905: Yes), use is set (step S906). If the user does not select to use (step S905: No), use is set (step S905: No). Step S907).

  The setting information is acquired by the setting information acquiring unit 212d, is notified to the sub CPU 202 of the controller board 20 by the notifying unit 212b, and is reflected on the operation of the controller board 20.

<Setting of First Automatic Reboot Processing Procedure and Second Automatic Reboot Processing Procedure (Part 2)>
FIG. 14 is a flowchart illustrating a second example of a procedure for setting whether to execute the first automatic reboot processing procedure and the second automatic reboot processing procedure.

When the user performs an operation of selecting a setting screen from the operation panel 211 (step S1001: Yes), a setting screen is generated by the setting information input screen generation unit 212c and displayed on the operation panel 211. The setting information acquisition unit 212d of the operation unit CPU 212 determines whether or not the user has selected (input) to use the reboot flag release based on the number of starts on the setting screen (step S1002).
If the user selects to use (step S1002: Yes), use is set (step S1003). If not (step S1002: No), use is set to not use (step S1002: No). Step S1004). If step S1003 has been performed, an input value of the number of times of flag release input from the setting screen is set (step S1005).

  After performing Step S1004 or Step S1005, the setting information acquisition unit 212d determines whether or not the user has selected (input) to use the reboot flag release by the timer on the setting screen (Step S1006). If the user selects to use (step S1006: Yes), use is set (step S1007), and if not (step S1006: No), use is set to not use (step S1006: No). Step S1008). When step S1007 is performed, the input value of the flag release time is set next (step S1009).

  The setting information is acquired by the setting information acquiring unit 212d, is notified to the sub CPU 202 of the controller board 20 by the notifying unit 212b, and is reflected on the operation of the controller board 20.

  By performing the procedure shown in FIG. 13 or FIG. 14, the user can freely set unnecessary functions. That is, for example, customization such as not using the timer because the energy saving mode is used is possible. Further, the customer engineer can change the setting to an appropriate setting according to the usage of the user. That is, for example, the user who uses the energy saving function and turns off the power at the end of the day is set to turn off the time counting, whereby unnecessary reboot can be suppressed.

  In the above description, the reboot system according to the fourth embodiment has a function of executing all of the first to fourth automatic reboot processing procedures (FIGS. 9 to 12), and the user has the function of executing the procedures. Among them, the configuration has a configuration in which it is possible to select to execute one or more, but a function to execute one, two or three of the first to fourth automatic reboot processing procedures is provided, The configuration may be such that the user can select to perform one or more of them.

  1, 2, reboot system, 10, 20 controller board, 14 power supply device, 100, 201 main CPU, 102, 202 sub CPU, 102a second communication monitoring means, 102b communication stop control means, 102c , 202d ... reboot control means, 104 ... nonvolatile memory, 12, 21 ... operation unit, 120, 212 ... operation unit CPU, 120a, 212a ... first communication monitoring means, 120b, 212b ... notification means, 203 ... power supply circuit .

JP 2005-219247 A

Claims (9)

An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot system that performs a reboot when a communication failure occurs between
The operation unit has an operation unit control unit. The operation unit control unit communicates with the main control unit, and monitors a communication failure between the main control unit and the operation unit control unit. A communication monitoring unit, and a notifying unit that, when the first communication monitoring unit determines that the communication is defective, notifies the sub control unit of the communication failure;
The sub control unit, when notified of a communication failure from the operation unit, a reboot control unit that issues a reboot request to the power supply unit, and a communication between the main control unit and a storage unit connected to the main control unit. And second communication monitoring means for monitoring the presence or absence of
The sub-control unit has a condition that the first communication monitoring unit determines that the communication is not good and the second communication monitoring unit determines that there is no communication between the main control unit and the storage unit. Making the reboot request,
When the second communication monitoring means determines that there is communication between the main control means and the storage means, the sub-control means controls to stop communication between the main control means and the storage means. A control that the main control means adds to the storage means when the communication stop control means and the second communication monitoring means determine that communication between the main control means and the storage means has not been stopped for a predetermined time; A reboot system , characterized in that the main control means includes communication stop control means for stopping communication with the storage means on condition that a signal is asserted . An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot system that performs a reboot when a communication failure occurs between
The operation unit has an operation unit control unit. The operation unit control unit communicates with the main control unit, and monitors a communication failure between the main control unit and the operation unit control unit. A communication monitoring unit, and a notifying unit that, when the first communication monitoring unit determines that the communication is defective, notifies the sub control unit of the communication failure;
The sub control unit, when notified of a communication failure from the operation unit, a reboot control unit that issues a reboot request to the power supply unit, and a communication between the main control unit and a storage unit connected to the main control unit. And second communication monitoring means for monitoring the presence or absence of
The sub-control unit has a condition that the first communication monitoring unit determines that the communication is not good and the second communication monitoring unit determines that there is no communication between the main control unit and the storage unit. Making the reboot request,
When the second communication monitoring means determines that there is communication between the main control means and the storage means, the sub-control means controls to stop communication between the main control means and the storage means. Having communication stop control means,
The sub-control means, when the second communication monitoring means determines that communication between the main control means and the storage means has not been stopped for a predetermined time, the control to be applied to the storage means by the main control means. A reboot system characterized in that communication is stopped by masking a signal . An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot system that performs a reboot when a communication failure occurs between
The operation unit has an operation unit control unit. The operation unit control unit communicates with the main control unit, and monitors a communication failure between the main control unit and the operation unit control unit. A communication monitoring unit, and a notifying unit that, when the first communication monitoring unit determines that the communication is defective, notifies the sub control unit of the communication failure;
The sub-control unit, when notified of communication failure from the operation unit, has a reboot control unit that issues a reboot request to the power supply unit,
A reboot system, wherein the sub-control unit does not issue a reboot request for a predetermined period after a reboot is performed in response to the reboot request even if a communication failure is notified from the operation unit . The reboot system according to any one of claims 1 to 3,
The sub-control means counts the number of reboots performed in response to the reboot request, and notifies the operation unit of an error message when the counted number of reboots is equal to or more than a certain number. Reboot system. The reboot system according to claim 3,
The reboot system according to claim 1, wherein the predetermined period is a period until the number of activations of the power supply unit reaches a predetermined value . The reboot system according to claim 3 ,
The reboot system according to claim 1, wherein the predetermined period is a period until the number of times the power supply unit is turned on by returning from the power saving mode reaches a predetermined value . An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot method in a reboot system that performs a reboot when a communication failure occurs between
A first communication monitoring step for monitoring a communication failure between the main control means and the operation section control means, which is performed by the operation section control means of the operation section; and a determination of a communication failure in the first communication monitoring step And a notifying step of notifying the sub-control means that the communication failure is determined in the determining step,
A reboot control step of performing a reboot request to the power supply unit when a communication failure is notified from the operation unit, the communication between the main control unit and a storage unit connected to the main control unit, performed by the sub control unit; Having a second communication monitoring step of monitoring the presence or absence of
In the reboot control step, the first communication monitoring step determines that the communication is defective, and the second communication monitoring step determines that there is no communication between the main control unit and the storage unit. Making the reboot request,
When it is determined in the second communication monitoring step that there is communication between the main control means and the storage means, the communication between the main control means and the storage means is controlled to be stopped by the sub-control means. The main control unit adds the communication to the storage unit when it is determined that the communication between the main control unit and the storage unit has not been stopped for a predetermined time in the communication stop control step and the second communication monitoring step. A reboot method , wherein the main control means has a communication stop control step of stopping communication with the storage means on condition that a control signal is asserted . An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot method in a reboot system that performs a reboot when a communication failure occurs between
A first communication monitoring step for monitoring a communication failure between the main control means and the operation section control means, which is performed by the operation section control means of the operation section; and a determination of a communication failure in the first communication monitoring step And a notifying step of notifying the sub-control means that the communication failure is determined in the determining step,
A reboot control step of performing a reboot request to the power supply unit when a communication failure is notified from the operation unit, the communication between the main control unit and a storage unit connected to the main control unit, performed by the sub control unit; A second communication monitoring step of monitoring the presence or absence of
In the reboot control step, the first communication monitoring step determines that the communication is defective, and the second communication monitoring step determines that there is no communication between the main control unit and the storage unit. Making the reboot request,
Stop control of communication between the main control means and the storage means when the second communication monitoring step performed by the sub-control means determines that there is communication between the main control means and the storage means. Communication stop control step to perform,
In the communication stop control step, when it is determined in the second communication monitoring step that communication between the main control means and the storage means has not been stopped for a predetermined time, the information is added to the storage means of the main control means. A reboot system, wherein communication is stopped by masking a control signal . An operation unit in the device, a main control unit that controls the device based on communication with the operation unit, and a sub control unit that controls a power supply unit of the device, the operation unit and the main control unit A reboot method in a reboot system that performs a reboot when a communication failure occurs between
A first communication monitoring step for monitoring a communication failure between the main control means and the operation section control means, which is performed by the operation section control means of the operation section; and a determination of a communication failure in the first communication monitoring step And a notifying step of notifying the sub-control means that the communication failure is determined in the determining step,
Performed by the sub-control unit, when a communication failure is notified from the operation unit, a reboot control step of issuing a reboot request to the power supply unit,
Has ,
In the reboot control step, a reboot request is not made even if a communication failure is notified from the operation unit for a predetermined period after the reboot is performed in response to the reboot request .

Images