JPH113252A - Preservation method for fault analysis log - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent a log preserved in a memory from being lost by subscription when a fault is generated. SOLUTION: When a fault is generated, it is determined whether or not a log freeze flag 19 is ON and, the write of the log is not performed in the case that the log freeze flag 19 is ON and the write of the log is performed in the case that it is not ON. In this case, since the write of the log is not performed in the case that the log freeze flag 19 is ON and the write of the log is performed in the case that it is not ON, the log preserved in the memory is not lost by the subscription when the fault is generated. Also, the need is eliminated for stopping a transaction device immediately after the fault is generated until a maintenance person or a designer or the like goes to the spot and outputs the log.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a method for storing a failure analysis log.

[0002]

2. Description of the Related Art Conventionally, in transaction devices such as vending machines, currency exchange machines, and automatic check-in devices for hotels, events, internal interface data, and the like are stored as logs. By analyzing the log, a designer or the like can determine the cause of the failure.

[0003] In this case, the log is written in a memory, but since the capacity of the memory is limited, all events after the transaction device is shipped, internal interface data, and the like are written. I can't put it. Therefore, events, for example, the number of transactions, the number of operations of the mechanism portion, etc., are written in a fixed area of the memory, and the internal interface data is written in a predetermined area using the memory cyclically. I have.

[0004]

However, in the above-described conventional method of storing a log for failure analysis, the memory is used cyclically, so that the transaction device operates to some extent after the failure occurs. In this case, when a failure occurs, the log stored in the memory is lost by overwriting.

[0005] Therefore, when investigating the cause of the failure by analyzing the log, the transaction is performed immediately after the failure occurs until a maintenance person or a designer goes to the site and outputs the log. The device must be stopped. Even when a maintenance person, a designer, or the like is in the field in advance, it is necessary to stop the transaction device while outputting the log.

The present invention solves the problem of the conventional method for storing a log for failure analysis, and when a failure occurs, the log stored in the memory is not lost due to overwriting, and the transaction is not performed. An object of the present invention is to provide a method for storing a failure analysis log that does not require stopping the device.

[0007]

For this purpose, in the method for storing a failure analysis log according to the present invention, when a failure occurs, it is determined whether or not the log freeze flag is on, and the log freeze flag is turned on. If not, the log is not written, and if not, the log is written.

[0008]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram of a transaction device according to the first embodiment of the present invention. As shown in the figure, a transaction device such as a vending machine, a currency exchange machine, an automatic hotel check-in device, etc., includes a card processing unit 11 for writing and reading data to and from a room card, a prepaid card, etc. Bank processing unit 12 that performs processing, coin processing unit 13 that performs coin deposit and withdrawal processing, receipt printer processing unit 14 that prints and issues receipts, and interface processing with a higher-level device (not shown) Interface (I
/ F) a processing unit 15, a main control unit 16 for controlling the entire transaction device, a memory processing unit 17 for managing a log freeze counter 20 as a time keeping means, an internal operation unit 18 for maintenance,
In addition, an event, internal interface data, and the like are stored in a memory (not shown) as a log, and a log freeze flag 19 indicating that the log is in an overwriting prohibited state.

In this case, the memory processing unit 17 writes events, for example, the number of transactions, the number of operations of the mechanism part, and the internal interface data into a predetermined area using the memory cyclically. Note that the event can be written to a fixed area of the memory. The internal operation unit 18 includes one rotary switch (0 to 9, A to F), four DIP switches, and one maintenance test activation switch (non-lock).

FIG. 2 is a flowchart showing a subroutine of log saving processing according to the first embodiment of the present invention, FIG. 3 is a flowchart showing a subroutine of failure processing according to the first embodiment of the present invention, and FIG. FIG. 5 is a flowchart showing a subroutine of a log timer check process according to the first embodiment of the present invention, and FIG. 5 is a flowchart showing a subroutine of an overwrite prohibition canceling process according to the first embodiment of the present invention.

The main controller 16 (FIG. 1) and the card processor 1
1. In order to store internal interface data between each processing unit such as the banknote processing unit 12, the coin processing unit 13, the receipt printer processing unit 14, the upper interface processing unit 15, and the like in a memory (not shown), the main control unit 16 A log saving process is performed each time an interface is established with each processing unit. In the log saving process, first, the main control unit 16 reads the log freeze flag 19, and
Is turned on, that is, whether the log is in the overwriting prohibited state. The log freeze flag 1
When 9 is on, the log is in the overwriting prohibited state, and the main control unit 16 ends the log saving process without writing the log, that is, without writing the internal interface data.

On the other hand, when the log freeze flag 19 is not turned on, the main control unit 16 writes the internal interface data to the memory because the log is not in the overwriting prohibited state. Next, the flowchart will be described. Step S1 The log freeze flag 19 is read. Step S2: It is determined whether the log freeze flag 19 is on. If the log freeze flag 19 is on, the process ends; otherwise, step S3.
Proceed to. Step S3 Write the log.

By the way, when a failure occurs in the transaction apparatus, when the transaction apparatus operates to some extent after the failure occurs, the log stored in the memory when the failure occurs is prevented from being lost by overwriting. Therefore, failure processing is performed. In the failure processing, the main control unit 16 turns on the log freeze flag 19 and sets a log freeze counter 20. The count value of the log freeze counter 20 is referred to in a log timer check process described later. Thereafter, the main control unit 16 displays the failure processing on a display unit (not shown).

For example, in order to maintain the overwriting prohibited state until a maintenance person, a designer, etc. outputs a log, the count value of the log freeze counter 20 is reduced by 2 to 3 until it reaches 0.
Set to take days. Even if another failure occurs during this time, the log is not written for the other failure. Next, the flowchart will be described. Step S11 The log freeze flag 19 is turned on. Step S12: The log freeze counter 20 is set. Step S13: The failure processing is displayed.

Next, the log timer check processing will be described. The log timer check process is performed in a timer interrupt process. First, the main control unit 16 sets the log freeze flag 1
9 is read, and it is determined whether or not the log freeze flag 19 is on. When the log freeze flag 19 is ON, the log freeze counter 20 is decremented because the log is in the overwriting prohibited state.

Subsequently, the main control unit 16 determines whether the count value of the log freeze counter 20 is 0,
If the count value is 0, the log freeze flag 19 is turned off. In the present embodiment, the time is measured by decrementing the log freeze counter 20. However, the time can be measured by incrementing the log freeze counter 20.

Next, the flowchart will be described. Step S21 The log freeze flag 19 is read. Step S22: It is determined whether the log freeze flag 19 is on. If the log freeze flag 19 is on, the process proceeds to step S23; otherwise, the process returns. Step S23: The log freeze counter 20 is decremented. Step S24: It is determined whether or not the count value of the log freeze counter 20 is 0. If the count value of the log freeze counter 20 is 0, the process proceeds to step S25; otherwise, the process returns. Step S25: The log freeze flag 19 is turned off.

Next, the overwriting prohibition release processing will be described. The main control unit 16 performs overwrite inhibition release processing when a power supply (not shown) is turned on. That is, the main control unit 1
6 reads the state of a rotary switch (not shown) of the internal operation unit 18 and determines whether the rotary switch is set to "8". When the rotary switch is set to “8”, the main control unit 16
The state of the maintenance test start switch of the internal operation unit 18 is read. Then, the main control unit 16 determines whether the maintenance test activation switch is pressed, and turns off the log freeze flag 19 when the maintenance test activation switch is pressed.

Therefore, for example, by setting the rotary switch to “8” and turning on the power while holding down the maintenance test start switch, the overwriting prohibited state of the log can be released. Note that, in the present embodiment, the setting of the rotary switch to “8” is a condition for releasing the overwriting prohibited state of the log. A condition for canceling the write-protected state may be set.

Next, the flowchart will be described. Step S31 The state of the rotary switch of the internal operation section 18 is read. Step S32: It is determined whether or not the rotary switch is set to "8". If the rotary switch is set to "8", the process proceeds to step S33, and if not, the process ends. Step S33 The state of the maintenance test start switch of the internal operation section 18 is read. Step S34: It is determined whether or not the maintenance test activation switch has been pressed. If the maintenance test activation switch has been pressed, the process proceeds to step S35, and if not, the process ends. Step S35: Turn off the log freeze flag 19.

As described above, when a failure occurs, the log overwriting prohibited state is set, so that the log already written when a new failure occurs is prevented from being lost. can do. Therefore, there is no need to stop the transaction device immediately after the occurrence of the failure and output the log, and the maintenance staff, the designer, and the like can output the log on a regular holiday or the like after the operation is completed. . In addition, by performing the overwriting prohibition release processing after outputting the log, it is possible to output the log when the next failure occurs.

Even when a failure that does not require log output occurs, when the count value of the log freeze counter 20 becomes 0, the overwriting prohibited state is automatically canceled. Work of a designer or the like can be simplified. Next, a second embodiment of the present invention will be described. FIG. 6 is a flowchart showing a subroutine of the failure processing according to the second embodiment of the present invention. In addition, about what has the same structure as 1st Embodiment, the description is abbreviate | omitted by attaching the same code | symbol.

In this case, the main control unit 16 (FIG. 1) determines whether to turn on the log freeze flag 19 based on the content of the fault that has occurred. That is, when a failure occurs, the main control unit 16 first determines whether the failure that has occurred requires log analysis, and sets the log freeze flag 19 if the failure requires log analysis. Turn on and set the log freeze counter 20.

If the failure that has occurred does not require analysis of the log, the log is not set in the overwriting prohibited state. Therefore, when a failure that requires log analysis occurs after a failure that does not require log analysis occurs, the log can be reliably written for the failure that requires log analysis. Next, the flowchart will be described. Step S41: It is determined whether or not the occurred failure requires log analysis. If the generated failure requires analysis of the log, step S42
If the log does not need to be analyzed, the process proceeds to step S44. Step S42 The log freeze flag 19 is turned on. Step S43: The log freeze counter 20 is set. Step S44: The failure processing is displayed.

The present invention is not limited to the above embodiment, but can be variously modified based on the gist of the present invention, and these are not excluded from the scope of the present invention.

[0026]

As described above in detail, according to the present invention, in the method of storing a log for failure analysis, when a failure occurs, it is determined whether or not the log freeze flag is on, and If the freeze flag is on, the log is not written, and if not, the log is written.

In this case, when the log freeze flag is on, the log is not written, and when the log freeze flag is not on, the log is written. Will not be lost by overwriting. Further, it is not necessary to stop the transaction apparatus immediately after the failure occurs until the maintenance staff, the designer, and the like go to the site and output the log.

[Brief description of the drawings]

FIG. 1 is a block diagram of a transaction device according to a first embodiment of the present invention.

FIG. 2 is a flowchart illustrating a subroutine of a log saving process according to the first embodiment of the present invention.

FIG. 3 is a flowchart illustrating a subroutine of a failure process according to the first embodiment of the present invention.

FIG. 4 is a flowchart showing a subroutine of a log timer check process according to the first embodiment of the present invention.

FIG. 5 is a flowchart illustrating a subroutine of overwrite inhibition release processing according to the first embodiment of the present invention.

FIG. 6 is a flowchart illustrating a subroutine of failure processing according to the second embodiment of the present invention.

[Explanation of symbols]

 16 Main control unit 18 Internal operation unit 19 Log freeze flag 20 Log freeze counter

Claims (4)

[Claims] (A) When a failure occurs, it is determined whether or not a log freeze flag is on. (B) When the log freeze flag is on, log writing is not performed, and when the log freeze flag is not on, Is a method of storing a log for failure analysis, which writes a log. 2. A log freezing flag is turned on in accordance with writing of a log, and a timer is set. (B) A log freeze flag is turned off when the clocking by the timer is completed. The method for saving a failure analysis log according to claim 1. 3. The method according to claim 1, wherein the overwriting prohibition state of the log is released by operating the internal operation unit. (A) determining whether or not the fault that has occurred requires analysis of the log; and (b)
3. The method according to claim 2, wherein the log freeze flag is turned on in accordance with writing of the log when the generated failure requires analysis of the log.