JPS6252352B2 - - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION (a) Field of Industrial Application This invention relates to a method for checking judgment data used for judging tickets of automatic ticket gates.

(B) Prior Art Generally, the validity of a ticket inserted into an automatic ticket gate is determined by comparing data stored on the ticket with determination data stored in advance in the automatic ticket gate. Specifically, the determination data includes the unique code of each station where you board and stop;
It consists of sections or fares (Special Publication No. 51-7080). This conventional automatic ticket gate does not have a function to determine whether the determination data is correct or incorrect.

(c) Problems to be solved by the invention As mentioned above, conventional automatic ticket gates store only judgment data and compare it with the data stored on the ticket to judge whether the ticket is correct or not. Therefore, when an abnormality judgment occurs, it is difficult to distinguish whether it is due to destruction of judgment data or failure or abnormality in other parts, and it takes a lot of time to determine the cause. In addition, the number of judgment data for automatic ticket gates may differ depending on the route to be judged by the ticket gate and the station where it is installed, and furthermore, there is a general method of checking judgment data that does not limit the codes that can be handled by the judgment data group. I had a problem that I couldn't get it.

SUMMARY OF THE INVENTION It is an object of the present invention to eliminate the above-mentioned drawbacks, quickly detect abnormalities in judgment data, and provide a more generalized method for checking judgment data of automatic ticket gates.

(d) Means and Effects for Solving Problems The automatic ticket gate judgment data checking method of the present invention is an automatic ticket checking method that compares data stored in a ticket with pre-stored judgment data to judge whether the ticket is correct or not. In the ticket gate, in addition to the area for storing the judgment data in the memory of the automatic ticket gate, an area for storing the number of data to be checked and an area for storing the check data are provided, and the number of data to be checked is stored in these areas. and check data are stored in advance, and the determination data is checked based on the number of determination data and the check data.

In the method of the present invention, only when an abnormality occurs in the judgment data, the abnormality can be discovered by checking based on the number of judgment data and the check data, and can be distinguished from abnormalities caused by other causes.

(E) Embodiments The present invention will be described below with reference to embodiments shown in the drawings.

FIG. 1 shows the arrangement of judgment data, etc. used in a device according to an embodiment of the present invention. 1 is a judgment data group in which, for example, station name codes and sections (or fares) for multiple stations are stored. be done. 2 is the number of data to be checked in the judgment data group, and 3 is sum check data.

FIG. 2 is a circuit block diagram showing an embodiment of the present invention, in which 4 is a CPU (central processing unit) and 5 is a memory. The memory 5 includes an area 6 for storing the number of check data, an area 7 for storing judgment data, an area 8 for storing sum data, an area 9 for storing comparison sum data, and a number counter 1.
0, address counter 11, further judgment result OK
It consists of OK flags 12, etc.

FIG. 3 is a control flow of the circuit block diagram shown in FIG. 2, and the operation of the CPU 4 is controlled according to this control flow.

In FIG. 3, initial processing for creating comparison data is performed in steps 20 to 22. In other words, after the operation starts, step 20
Clear the comparison sum data storage area 9 with . Subsequently, in step 21, the address of the check data number storage area 6 is stored in the address counter 11, and in step 22, the number of times counter 10 is set. The number counter 10 is set by storing a value obtained by subtracting one from the number of check data stored in the check data number storage area 6.

In step 23, comparison sum data is calculated. This calculation is based on the comparison sum data storage area 1
This is done by adding the contents of 4 and the data at the address indicated by the address counter 11, and storing this result in the comparison sum data storage area 14. Furthermore, in step 24, the address counter 11 is
1, the address is updated, and in step 25, the number of times counter 10 is decremented by 1, and the number of checks is subtracted. Step 26 is a step for checking the completion of comparison sum data calculation, and it is determined whether the content of the number of times counter 10 is 0 or not. If it is not 0, the process returns to step 23, and the calculations in steps 23 to 25 are repeated until the content of the number counter 10 becomes 0. If the content of the number counter 10 is 0, this means that the comparison sum data calculation has been performed as many times as the number of check data, and the process moves to the next step 27 when the comparison sum data has been created. In step 27, the sum stored in advance in the sum data storage area 8 is compared with the contents of the comparison sum data storage area 9 obtained by calculation. If the two data do not match, the judgment OUT is processed in step 28, but if the two data match, the process returns to step 28.
In step 29, the judgment data OK processing is performed.

An actual automatic ticket gate consists of a controller and a ticket gate, and each ticket gate receives judgment data from the controller, stores it in its own storage, and makes a judgment. The method for checking the judgment data described above is as follows:
It is used to check the judgment data at the time of initialization of the ticket gate, and also to check the judgment data of each ticket gate when judgment data is sent from the controller to each ticket gate, and if the check of the judgment data is OK, The OK flag shown in FIG. 2 is set so that there is no need to send judgment data from the controller to the ticket gate. Below, operation examples of these usage examples will be explained.

FIG. 4 shows the operational flow of the judgment data check at the time of initialization of the ticket gate.

In FIG. 4, step 40 is a check of determination data, and the same processing as that from step 20 to step 26 in FIG. 3 is performed until data creation is completed. In step 41, it is determined whether the contents of the sum data storage area 9 match. If both data match, the process advances to step 42, and the flag 12 for checking the judgment data is set. Thereafter, an OK determination is made, that is, it is determined that flag 12 is set, and the initial processing is performed.

If there is an abnormality in the judgment data, steps up to step 41 in FIG. Clear. Then, in step 44, an abnormality in the judgment data is displayed and a warning is issued to the staff.

FIG. 5 is an operational flowchart of judgment data check when judgment data is received from the controller of the ticket gate.

In FIG. 5, the initial check is that the judgment data is OK, and the OK flag 12 is checked.
Let us consider the operation when is set.

Step 50 analyzes the transmission command sent from the controller to the ticket gate. This is to determine whether the subsequent transmission data is determination data or other data. In this judgment, if the next data is judgment data, the process moves to step 51. At step 51, the OK flag 12 is checked to see if judgment data is required. According to the above-mentioned premise, it is assumed that the OK flag 12 is set, so there is no need to have the control device transmit the determination data, and the process ends.

Next, consider a case where the initial judgment data check is OUT and the OK flag 12 is cleared. The steps up to step 51 are the same as when the OK flag 12 is set, but the determination at step 51 as to whether or not the OK flag 12 is set is different.
Since the answer is NO, the process moves to step 52, where determination data is sent and received from the controller. Further steps
In step 53, the judgment data is recalculated. Next step 5
Compare the sum data and comparison data in step 4, and if a match is obtained, the judgment data is OK, so proceed to step 55.
Set OK flag 12 with . and step
56 turns off the error display. The ticket gate enters the operating state, and the process of receiving the judgment data ends.

Furthermore, let us consider the case where the determination data is out at the initial time and the determination data is out in the received data. Up to step 54, the same flow as in the case of initial determination data out and reception determination data OK is followed. However, since the judgment data at the time of reception is also out, the comparison of the sum data and comparison sum data in step 54 shows no match, and the process moves to step 57. In step 57, the OK flag 12 is cleared in order to receive the judgment data again. In step 58, the judgment data abnormality is displayed, and the process returns to the start and waits for reception of judgment data again. In addition,
If normal determination data cannot be received forever, the routine may be exited after steps 54, 57, 58, and 50 are repeated several times.

(F) Effects of the Invention According to the present invention, not only the judgment data but also the number of data to be checked and the check data are stored in advance, and the judgment data is checked based on the number of check data and the check data. If there is an abnormality in the judgment data, it can be quickly discovered and countermeasures can be taken quickly.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing an example of the arrangement of determination data, etc. of the present invention, FIG. 2 is a circuit block diagram showing an embodiment of the present invention, and FIG. 3 is a control flow diagram of the circuit block diagram of FIG. Figure 4 is a diagram showing the initial control flow when the circuit block diagram in Figure 2 is applied to an actual ticket gate, and Figure 5 is a diagram showing the initial control flow when the circuit block diagram in Figure 2 is applied to an actual ticket gate. FIG. 4 is a diagram showing a control flow when receiving data from a controller when applied to a controller. 4: CPU, 5: Memory, 6: Check data number storage area, 7: Judgment data storage area, 8:
Sum data storage area, 9: Comparison sum data storage area, 10: Number of times counter, 11: Address counter, 12: OK flag.

Claims (1)

[Scope of Claims] 1. In an automatic ticket gate that compares data stored on a ticket with pre-stored determination data to determine whether the ticket is correct or not, an area for storing the determination data in the memory of the automatic ticket gate is provided. In addition, an area for storing the number of data to be checked and an area for storing check data are provided, the number of data to be checked and the check data are stored in advance in these areas, and the number of data and the check data are stored in advance. A method for checking judgment data of an automatic ticket gate, characterized in that the judgment data is checked based on the judgment data.