JPH09101810A - Device and method for analyzing change recording data of input/output contact of programmable logic controller - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily understand the constitution of a program by analyzing the log data of a PLC to pattern-sorted data to be functionally regarded as a group of data. SOLUTION: This analyzer is provided with a pattern-sorted data storing means 5 and a specifying means 3. The means 5 previously stores plural I/O contact status changes to be functionally regarded as a group of data as pattern- sorted data. When status change storing data are provided, the means 3 refers to respective pattern-sorted data and specifies a range corresponding to each pattern-sorted data out of the status change storing data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for analyzing change record data of input / output contacts of a programmable logic controller, and more particularly to data generation for analyzing a sequence program used in the programmable logic controller.

[0002]

2. Description of the Related Art Today, a controlled device control system using a programmable logic controller (hereinafter referred to as PLC) is known. The PLC controls the device to be controlled according to a program stored in advance based on outputs (open state or closed state) from various sensors that detect the state of the device to be controlled.

FIG. 25 shows a schematic diagram of a PLC-controlled system. In this system, when the motor M1 rotates, the belt conveyor B conveys the work 200 to the defect detection position. The size of the work 200 is detected by the sensors 201 and 202, and if the work 200 is out of the standard, it is discharged by the defect detection cylinder 210. If it is within the standard, the motor M1 rotates again, and the work moves to the end of the belt conveyor B. The sensor 205 is the work 200
Is detected, and the motor M1 is stopped after a certain period of time. As a result, the work 200 is placed on the table 211. When this state is detected by the sensor 207, the work cylinder 200 moves the work 200 onto the table 215.

On the table 215, when the sensor 219 detects the work 200, the jig 217 is locked and the motor M2 is rotated to lower it. As a result, the work 200 is drilled. When the drilling process is completed, it is ejected by the ejection cylinder 221.

In this system, the equipment to be controlled is controlled by an instruction input device which gives an instruction to these and a state detector which detects the state thereof. For example, each cylinder is equipped with a solenoid that is a command input device and a sensor that is a state detector (neither is shown). When the forward solenoid is turned on, the cylinder moves forward and when the front end sensor detects the front end. , The reverse solenoid is turned on and the vehicle retreats. It stops when the trailing edge is detected by the trailing edge sensor.

A program for performing such control is generally represented by a ladder chart as shown in FIGS. The ladder chart is composed of a plurality of single ladder circuits. Each single ladder circuit is composed of multiple contacts. For example, in the single ladder circuit L39 shown in FIG. 26, the contacts 00200, 00005, 00.
If 008 is on and contact 00104 is off, contact 0
0202 turns on. The contact 00202 is held by itself.

When the contact 00202 is turned on, the contact 00202 of the other single ladder circuit L48 is turned on. In this way, the state of the contact of the other single ladder circuit changes according to the output result at the contact of the certain single ladder circuit L39, and the control target device finally connected is controlled.

By the way, as for the sequence program, the debug device verifies in advance whether there is an error.

As such a verification method, P
A method of connecting an LC and reproducing the states of the input contact and the output contact of the PLC on a computer screen is widely used. That is, the operator refers to the time chart or the like to register the input contact and the output contact related to the sequence program to be debugged in the CRT of the debug device. As a result, a list of input / output contacts as shown in FIG. 28 can be obtained. The operator clicks one of the displayed input contacts with a mouse. As a result, a simulated input signal is applied to the input contact of the PLC instead of the sensor or the like. The PLC executes the stored sequence program for a predetermined time (tens of meters).
s) every time. Therefore, when the state of the input contact is changed by the simulated input signal, the state of the output contact changes accordingly. The change in the state of the output contact is displayed on the CRT of the debug device. In this way, the state change of the input / output contact is repeated and it is judged whether or not the desired state change occurs for each output contact.

By using such a verification method,
The sequence program can be debugged without connecting the PLC to the actual machine. Therefore, it is possible to safely and easily detect a bug in a program of a dangerous and complicated control device such as a chemical plant. Further, since the simulation apparatus can perform the simulation on the screen, the program can be debugged in advance before the system configuration is completed.

[0011]

However, the above-described debug device has the following problems.

First, it is not easy to find a bug even if the contact changes unexpectedly. This is because, in the simulation, the state of a certain output contact is displayed in response to a change in the state of a certain input contact, and it is determined whether the corresponding output contact changes to the desired state, thereby finding a bug in the program. I am trying to do it. For this reason,
The operator predicts in advance which output contact will change when a certain input contact is changed, and checks whether or not the output contact changes accordingly. Therefore, it is difficult for the operator to discover a contact that has not been predicted.

Further, in reality, at the same time that the defective discharge of the work _n is detected, the work _{n + 1} is input. In such a case, there is no problem when individually simulated, but when connected to an actual plant or the like, inconvenience may occur in the mutually related parts.

Secondly, unlike the ordinary computer program, the ladder chart is not necessarily described in non-sequential order in the processing order. Therefore, it becomes difficult for anyone other than the ladder chart creator to understand the structure of the sequence program. Also, unless the creator also records the program structure in some form, it becomes difficult to grasp the contents later.

SUMMARY OF THE INVENTION It is an object of the present invention to solve the above problems and to provide an analyzing device and an analyzing method capable of analyzing state change record data of input / output contacts of a PLC into pattern-specific data which can be regarded as one functional group. And

Another object of the present invention is to provide an apparatus and a method by which debugging of a sequence program used for PLC can be effectively performed.

[0017]

[Means for Solving the Problems]

[0018]

[Technical idea devised to solve the problem] In the change record data analyzer for input / output contacts according to claim 1, the PL
In order to obtain the analysis data of the state change record data of the input / output contact of C, a plurality of state changes of the input / output contact that can be regarded as one functional group are stored as pattern-specific data and correspond to the pattern-specific data. I'm trying to identify the range to do.

That is, as shown in FIG. 1, which is a diagram showing the overall configuration of the invention, in the change record data analyzer of the input / output contact according to claim 1, when the state of the input contact is given, it is stored. It is a device for analyzing the state change record data of the input / output contact of the programmable logic controller that changes the state of the output contact, based on the stored sequence program. When a pattern-based data storage unit that stores a plurality of patterns in advance and the state-change storage data are given as pattern-based data, each of the pattern-based data is referenced to correspond to the pattern-based data of the state-change storage data. It is characterized by including a specifying means for specifying a range.

According to another aspect of the present invention, there is provided an input / output contact state change record data analyzing apparatus, which comprises: A) The pattern-specific data storage means, for each pattern, indicating the number of input / output contacts whose states change in the pattern-specific data. It is stored as index data, B) the specifying means has the following means b1) to b3), and b1) temporary division for temporarily dividing the stored data so as to include a predetermined number of input / output contacts whose states change. Means, b2) Matching judging means for judging whether or not the pattern-wise data in which the number of input / output contacts whose states change in the temporarily divided data are the same, and the state change in the input / output contacts match, b3) The coincidence determination Is obtained, the state change storage data identifying means for identifying the state change storage data portion corresponding to the coincident portion as a range corresponding to the pattern-specific data is characterized.

In the input / output contact state change record data analyzing apparatus according to claim 3, the specifying means further matches a part of the contacts in the temporarily divided data when the matching judgment cannot be obtained. It is characterized in that it has a re-judgment determining means which is removed from the judgment object and causes the coincidence judging means to judge again.

In the record data analyzing apparatus of claim 4, A) each of the input / output contacts has characteristic data which is expressed by a combination of a plurality of basic words and which indicates characteristics of a device connected to the input / output contacts. B) the identifying means has the following means b1) to b4), and b1) dictionary means for storing basic word related data representing attributes and relationships of basic words for each of the basic words. B2) an inference division means for inferring mutual association data regarding each of the input / output contacts based on the basic word-related data and the characteristic data to divide the state change record data, b3) a state of the divided data Matching judgment means for judging whether or not the pattern-based data in which the number of changing input / output contacts is the same as the input / output contact state change, b4) When the above-mentioned matching judgment is obtained, this matching part is matched. Status change stored data specifying means for the state change stored data portion is specified as a range corresponding to the pattern specific data to be, characterized by.

According to another aspect of the recorded data analyzing apparatus of the present invention, the specifying means associates the input / output contacts with each other based on the inferred mutual relation data.

According to another aspect of the recorded data analyzing apparatus of the present invention, when the state of the input contact is given, the state of the input / output contact of the programmable logic controller is changed based on the stored sequence program. A device for analyzing and displaying recorded data, wherein when the state change memory data is given, a state change portion of the input / output contact which can be regarded as one set functionally is specified,
Display means for displaying an analysis result of the state change storage data is provided.

According to a seventh aspect of the recorded data analysis method of the present invention, when the state of the input contact is given, the state of the input / output contact of the programmable logic controller is changed based on the stored sequence program. A method of analyzing recorded data, wherein a plurality of state change recording data of input / output contacts which can be regarded as one set functionally are stored as pattern-specific data, and when the state change storage data is given, It is characterized in that a range corresponding to the pattern-specific data in the state change storage data is specified by referring to the pattern-specific data.

In the method for analyzing state change record data of input / output contacts according to claim 8, A), for each pattern, the number of input / output contacts whose states change in the pattern-specific data is stored as index data. B) The identification is performed according to the following procedure: b1) Temporarily divides the stored data so as to include a predetermined number of input / output contacts that change states, and b2) Input / output that changes states of the temporarily divided data. If it is determined whether or not the pattern change data having the same number of contacts and the state change of the input / output contacts match, b3) When the match determination is obtained, the state change storage data portion corresponding to this match portion is set to the pattern. It is characterized by specifying as a range corresponding to another data.

In the input / output contact state change record data analysis method according to claim 9, if the coincidence determination cannot be obtained, a part of the contacts in the temporarily divided data is excluded from the coincidence determination target, and the contact determination is performed. It is characterized by repeating the determination of whether or not they match.

In the method of analyzing state change record data of input / output contacts according to claim 10, A) each of the input / output contacts is represented by a combination of a plurality of basic words and is connected to the input / output contact. Characteristic data indicating characteristics is attached, B) the identification is performed in the following procedure, b1) basic word related data representing attributes and relevance of basic words is stored for each basic word. Every b2) based on the basic word-related data and the characteristic data, inferring mutual relational data regarding each of the input / output contacts, dividing the state change recording data, and b3) changing the state of the divided data. If it is determined whether or not the pattern-based data with the same number of input / output contacts and the state change of the input / output contacts match, b4) If the match determination is obtained, the state change record corresponding to this matching part is obtained. Specifying the data portion as a range corresponding to the pattern specific data, characterized by.

According to the recorded data analysis method of the eleventh aspect, based on the inference result, the contact of the input / output contact whose state changes with the temporarily divided data is made to correspond.

In the recorded data analysis method according to the twelfth aspect, when the state change storage data is given, the state change portion of the input / output contact which can be regarded as one set is specified.
It is characterized in that the analysis result of the state change storage data is displayed.

A computer-readable storage medium according to a thirteenth aspect stores a program for implementing the device or method according to any one of the first to twelfth aspects by using a computer.

[0032]

[Definition of terms] The concept of the terms of the claims used to express the technical idea devised to solve the problems is defined as follows, and the relationship between the terms and the embodiments will be described. .

"State change record data": data in which the state change of the input / output contact of the programmable logic controller is recorded. It includes both data when detected every predetermined time and when there is a change in the input contact. Further, regardless of the data format, for example, the open / closed states of all the contacts may be stored, or the initial state and the contacts changed from this initial state may be stored. In the embodiment, it corresponds to log data.

"Data for each pattern": A group of input / output contact state changes that can be functionally regarded as one set. In the embodiment, the data corresponds to the contact change state for each class shown in FIG.

"Index data": Data indicating the number of input / output contacts whose state changes in the data for each pattern for each pattern. In the embodiment, for example, for class 0, the number of input contacts is 1 and the number of output contacts is 1
Is applicable.

"Characteristic data": data attached to each input / output contact, which is represented by a combination of a plurality of basic words and shows characteristics of a device connected to the input / output contact. In the embodiment, it corresponds to a comment. Any comment such as an I / O table or ladder chart may be used as the comment.

"Basic word-related data": data representing the attribute and relevance of each basic word. The attribute means the type of the basic word, and in the embodiment corresponds to the type information. Further, the relevance is a property indicating a relation between basic words, and corresponds to pair relation information, causal relation information, and synonym information in the embodiment.

"Mutual relation data": data indicating the relation between the devices inferred based on the basic word relation data and the characteristic data. For example, in the embodiment, the address "00003" shown in FIG. 23. What is the relationship between the device connected to the address "00004" and the device connected to the address "00004" and the device connected to the address "00103" and the device connected to the address "00104" shown in FIG. Inferred.

"Data storage means for each pattern": In the embodiment, the hard disk 26 corresponds thereto.

"Dictionary means": In the embodiment, the hard disk 26 corresponds.

"Specifying means": In the embodiment, CP
This corresponds to the process of step ST15 of U23.

"Temporary dividing means": C in the embodiment
This corresponds to the process of step ST21 of PU23.

"Match determining means": In the embodiment,
This corresponds to the process of step ST29 of the CPU 23.

"Re-judgment determining means": In the embodiment, it corresponds to the process of step ST39 of the CPU 23 and the process of repeating step ST21 and subsequent steps.

"State change storage data specifying means": In the embodiment, it corresponds to the process of step ST30 of the CPU 23.

"Inference means": CP in the embodiment
This corresponds to the process of step ST117 of U23.

"Determination means": CP in the embodiment
This corresponds to the processing of step ST118 of U23.

[0048]

According to the recorded data analyzing apparatus or method of the first and seventh aspects, a plurality of state changes of the input / output contacts which can be regarded as one functional group are stored as pattern-specific data. When the state change memory data is given, the range of the state change memory data corresponding to the pattern data is specified by referring to the pattern data. By such identification, the state change storage data can be easily analyzed.

By thus dividing the pattern into functional patterns that can be regarded as one set, it is possible to easily know the overall configuration of the sequence program.

In particular, regarding the change recording data used for the pattern-specific data, if the data actually operated by the operator at the time of debugging is used, the state change storage data can be obtained without performing a separate analysis process. Can be easily analyzed. Furthermore, it is possible to divide the sequence program by function based on the analysis result.

In the recorded data analyzing apparatus or the method thereof according to claims 2 and 8, the stored data is provisionally divided so as to include a predetermined number of input / output contacts whose states change. With respect to the temporarily divided data, it is determined whether or not the pattern-based data in which the number of input / output contacts whose states change is the same as the state change of the input / output contacts. When the coincidence determination is obtained, the state change storage data portion corresponding to the coincidence portion is specified as the range corresponding to the pattern-specific data.
As a result, the state change storage data can be easily analyzed.

In the recording data analyzing apparatus or the method thereof according to claims 3 and 9, when the coincidence judgment cannot be obtained, some contacts in the temporarily divided data are excluded from the coincidence judgment object, The determination of whether or not they match is repeated. As described above, the change storage data can be more easily analyzed by repeating the match determination until the match determination is obtained after the temporary division.

In the recording data analyzing device or the method thereof according to claims 4 and 10, the input / output contacts are
Characteristic data, which is represented by a combination of a plurality of basic words and indicates the characteristic of the device connected to the input / output contact, is attached. Basic word-related data representing attributes and relationships of basic words are stored for each of the basic words, and based on the basic word-related data and the characteristic data, inferring mutual-related data regarding each of the input / output contacts. , The state change recording data is divided. For the divided data, it is determined whether or not the pattern-based data in which the number of input / output contacts whose states change is the same as the state change of the input / output contacts. When the coincidence determination is obtained, the state change storage data portion corresponding to the coincidence portion is specified as the range corresponding to the pattern-specific data. Therefore, the coincidence determination can be made accurately and promptly.

In the recorded data analyzing apparatus or the method thereof according to claims 5 and 11, the input / output contact whose state changes with the temporarily divided data is made to correspond based on the inference result. Therefore, the contact can be assigned accurately and quickly. As a result, the coincidence determination can be made more quickly.

In the recording data analyzing apparatus or the method thereof according to claims 6 and 12, when the state change storage data is given, a portion of the state change of the input / output contact which can be regarded as one set is specified. The analysis result of the state change memory data is displayed. As a result, the state change storage data can be easily analyzed.

[0056]

DESCRIPTION OF THE PREFERRED EMBODIMENTS

1. Functional Block Diagram One embodiment of the present invention will be described with reference to the drawings. FIG.
1 shows an apparatus (hereinafter referred to as an analysis apparatus) 1 for analyzing state change record data of input / output contacts of a programmable logic controller (PLC). The PLC determines the state of the detection signal from the state detector that detects the state of the control target device at a predetermined cycle, and based on the state of this detection signal,
A device that outputs a predetermined output signal.

The analysis device 1 is provided with the pattern-based data storage means 3 and the identification means 5.

The pattern-based data storage means 3 stores in advance a plurality of input / output contact state changes that can be regarded as one functional group as pattern-based data. Further, the pattern-based data storage unit 3 stores, for each pattern, the number of input / output contacts whose states change in the pattern-based data as index data. It should be noted that each input / output contact is provided with characteristic data which is represented by a combination of a plurality of basic words and which indicates the characteristics of a device connected to the input / output contact.

When the state change storage data is given, the specifying means 5 refers to each pattern data and specifies the range corresponding to the pattern data among the state change storage data.

Details of the specifying means 5 will be described. The characteristic means 5 has a temporary dividing means 11, a coincidence judging means 13, a re-judgment determining means 15 and a state change storage data specifying means 17.

The temporary dividing means 11 temporarily divides the stored data so as to include a predetermined number of input / output contacts whose states change. The coincidence judging means 13 judges whether or not the pattern-wise data in which the number of input / output contacts whose states change is the same in the temporarily divided data and the state change in the input / output contacts coincide. Here, the coincidence of the state changes of the input / output contacts means that both the order of the state change and the on / off states coincide. When the coincidence judgment cannot be obtained, the re-judgment determination means 15 removes some of the contacts in the temporarily divided data from the coincidence judgment target and causes the coincidence judgment means 13 to make the judgment again. When the coincidence determination is obtained, the state change storage data identification means 17 identifies the state change storage data portion corresponding to this coincidence portion as the range corresponding to the pattern-specific data.

The following configuration can also be adopted. Characteristic data indicating a characteristic of a device connected to the input / output contacts is attached to each of the input / output contacts, which is represented by a combination of a plurality of basic words. The specifying unit 3 has a dictionary unit, an inference dividing unit, a coincidence judging unit, and a state change storage data specifying unit.

The dictionary means stores basic word-related data representing attributes and relationships of basic words for each of the basic words. The inference dividing means infers mutual relational data relating to each of the input / output contacts based on the basic word-related data and the characteristic data, and divides the state change record data. The coincidence determination means, regarding the divided data,
It is determined whether or not the pattern-based data in which the number of input / output contacts whose states change is the same as the state change of the input / output contacts. When the coincidence determination is obtained, the state change storage data identification means identifies the state change storage data portion corresponding to the coincidence portion as a range corresponding to the pattern-specific data.

Further, the specifying means 3 may associate the input / output contacts with each other based on the inferred mutual relation data.

When the state of the input contact is given, the analyzer 1 analyzes the state change record data of the input / output contact of the programmable logic controller which changes the state of the output contact based on the stored sequence program. A device for displaying the state change storage data, and when the state change storage data is given, a display for identifying the state change portion of the input / output contact that can be regarded as one set functionally and displaying the analysis result of the state change storage data. It can be grasped as a state change record data analysis device of the input / output contact characterized by including the means. .

2. Hardware Configuration FIG. 2 shows an example of a hardware configuration in which the analyzer 1 shown in FIG. 1 is realized by using a CPU. The analysis device 21 is C
PU23, FDD25, memory 27, hard disk 2
6, a keyboard 28, an input / output interface 33, a mouse 31, a CRT 30 as a display means, and a bus line 29.

The CPU 23 controls each unit via the bus line 29 according to the control program stored in the hard disk 26.

This control program is read from the flexible disk storing the program via the FDD 25 and stored (installed) in the hard disk 26. The hard disk 26 stores various data described later. The memory 25 stores the calculation result and the like. A switch box used for debugging is displayed on the CRT 29.

The input / output interface 33 has a PLC
34 is connected. A sequence program to be debugged is stored in the PLC 34.

3. Flowchart Next, a program stored in the ROM 25 will be described with reference to FIG. 3. First, the CPU 23 sets the simulation mode (step ST5 in FIG. 3). The simulation is similar to the conventional one, but will be briefly described.

The operator registers an input / output contact to be debugged prior to debugging. As a result, the switch box in which the input contacts are displayed and the output monitor in which the output contacts are displayed are displayed on the CRT 30 (see FIG. 2).

For debugging, the operator changes the input state by using the switch box shown in FIG.
It is performed by determining whether or not the output monitor changes to correspond to it.

When the operator finds that there is a bug in the program, the operator gives a debug processing shift instruction from the keyboard 28. The CPU 23 determines whether or not a debug process shift instruction is given (step ST
7) When a debug process shift instruction is given, the process shifts to the debug mode (step ST9).

When the debug mode ends, step ST
The simulation mode of 5 is executed again. CPU2
When the debug mode shift command is not input in step ST7, the process 3 determines whether or not there is a simulation end command (step ST11).

If there is no simulation end command, the processes in and after step ST5 are repeated. Step S
If a simulation end command is given at T11, the log data is stored in the hard disk 26 (step ST13 in FIG. 3). The log data stored in this hard disk is the state change data of the input / output contact in the ladder chart after the debug is completed.

An example of log data is shown in FIG. The log data is data indicating the change state of the input / output contact. 1
"I" in the line indicates the input contact, and the next "00"
“0” indicates the channel number of the PLC 34, and the next “9411” indicates the ON / OFF state of 16 input contacts.

Specific description will be made. The first "9" is "1001" in binary notation, and the next "4" is "0".
100 ". The next "1" is "0001".
The next "1" is also "0001". When this is lined up,
It becomes "1001010000010001". Reverse this, that is, "1000100000101001"
Is associated with the I / O table shown in FIG. That is, the address "00000" (operation switch) corresponds to the first "1" (ON) and the address "0000".
1 "(stop switch) corresponds to the next" 0 "(OFF). The address "00002" (release switch) corresponds to the next "0" (OFF), and the address "00003"
(Faulty front end) corresponds to the next "0" (OFF) ....

Similarly, the next "001-0005" is
The state of each bit of PLC channel "001" is "0".
005 ”. "0005" means "941"
If it is arranged in the same manner as in the case of "1", "0000000000"
0010 ”. Reverse this, that is, "101
6 side by side with "0000000000"
Corresponds to the / O table. That is, the address "00
"100" (lamp during operation) is "1" (ON), and address "00101" (abnormal lamp) is "0" (OF
F), the address "00102" (motor 1) is "1" (ON), and so on.

In this way, the log data for debugging is stored and the class is identified using this log data (step ST15). Class identification will be described with reference to FIG. The CPU 23 cuts out a part of the log data (step ST21 in FIG. 4).

The CPU 23 cuts out the log data shown in FIG. 5 in a predetermined number of lines. In the present embodiment, the partial cutout is performed by cutting out six lines from the line immediately before the first change in the output contact.

Since the first line is the initial state of the input contacts and the second line is the initial state of the output contacts, the line in which the output contact first changed is the fourth line excluding these. . Therefore, six lines are cut out from the immediately preceding third line.

Next, the CPU 23 extracts the contact whose state has changed from the cut out log data (step ST23 in FIG. 4). In the log data shown in FIG. 5, it is difficult to understand the ON / OFF state of each input / output contact, so the input / output contact in the ON state is shown with comments for easy understanding (FIGS. 7 to 7). 10).

The comment is determined by referring to the I / O table shown in FIG. 6 based on the address of the input / output contact.

For the contact whose state has changed, the state of the output contact when the state of the next input contact is given is associated with the state of the previous output contact. The same applies to the input contact.

For example, in the initial state, the input / output contact shown in FIG. 7B is in the ON state. Then, as shown in the third line, the input contact is changed, so that the output contact is changed in state as shown in FIG. 8B. In this case, regarding the input contact, the contact “00003” (defective front end) is ON, and the contact “00004” (defective rear end) is OFF. For output contact, refer to contact "0010
3 ”is OFF and contact“ 00104 ”is ON. Therefore, it can be determined that these are the contacts whose states have changed. The same applies to FIGS. 9 and 10.

In this way, from the third line to the eighth line, as shown in FIG.
One input contact and four output contacts are extracted.

Next, the CPU 23 extracts the data of the class shown in FIG. 11 in which the number of extracted input contacts and output contacts is the same (step ST25 in FIG. 4). The hard disk 26 stores the state change data of the input / output contacts of each class and the image data corresponding thereto. FIG. 12 shows state change data of the input / output contacts of each class. According to this, it is understood that, for example, class 0 is a class having one input contact and one output contact. FIG. 13 shows image data of class 0 and class 1.

The CPU 23 extracts from the hard disk 26 the data of the class having the number of input contacts of 2 and the number of output contacts of 4,
The input contact and the output contact shown in FIG. 11 whose state has changed are associated with the input contact and the output contact of the extracted class (step ST27 in FIG. 4). In the present embodiment, the contacts are associated in the order of appearance.

Specifically, the number of input contacts is 2 and the number of output contacts is 4
For the data of the class (not shown), input contact "0
0003 "(defective front end) to sensor (SE) 0, input contact" 00004 "(defective rear end) to sensor (SE) 1,
Set the output contact "00102" (motor 1) to the solenoid (S
OL) 0, output contact “00103” (defective forward) to solenoid (SOL) 1, output contact “00104” (defective backward) to solenoid (SOL) 2, output contact “00
105 ”(defective defect) is associated with the solenoid (SOL) 3. When there are a plurality of classes each having two input contacts and four output contacts, all the previously stored classes are extracted.

Next, the CPU 23 determines whether or not the state change of the acquired power contact of the extracted class matches the state change of the input / output contact in the log data shown in FIG. 5 (step ST29 in FIG. 4). When it is determined that they do not match, the CPU 23 determines whether all contact patterns have been considered (step ST33), and when all have not been considered, the contact pattern is changed (step ST3).
5).

For example, the input contact “00004” is changed to the sensor 0 and the input contact “00003” is changed to the sensor 1. In addition, not only the input contact may be replaced, but only the output contact may be replaced, or both of them may be replaced.

Then, again, it is judged whether or not the state change of the input / output contact of the cut out log data and the state change of the input / output contact of the class are matched (step ST2).
9).

If the two do not match, the CPU 23 repeats the processing of steps ST33 and ST35.

In step ST33, when all contact patterns have been examined for a certain class, it is determined whether or not there are remaining candidate classes (step ST3).
7). When determining that the remaining candidate classes extracted in step ST25 exist, the CPU 23 extracts data of the next candidate class (step ST38). Then, the processing from step ST27 onward is performed. In this way, this processing is repeated until the state changes of the input / output settings in the data of the class having the same number of input / output contacts match.

When there is no candidate class having the same number of contacts in step ST37, a process of removing some contacts is performed (step ST39). For example, in the case of two input contacts and four output contacts shown in FIG. 11, any one of the output contacts is removed. In this embodiment, the output contact "00102" that appears first is removed.

In this way, the coincidence judgment is made for the candidate class having the number of input contacts of 2 and the number of output contacts of 3. In this way, a part of the contacts are sequentially removed, and the state change of the input / output contacts corresponding to any class is detected. Specifically, the case of removing the output contact “00103”, the case of removing the output contact “00104”, and the case of removing the output contact “00202” are examined in the same manner. Further, as in the case where the input contact 2 and the output contact 2 are combined, the contacts are sequentially removed to determine whether or not the data matches the data of each class.

In the present embodiment, when the number of extracted state change contacts differs between the input contact and the output contact, the larger one is preferentially removed.

The CPU 23 executes step ST2 in FIG.
If it is determined in step 9 that they match, the range, class ID, and contact relationship data are stored (step S
T30). In the present embodiment, as shown in FIG. 14, the log range, the class identification number (ID), and the correspondence with the contact point are stored in the hard disk 26.

The CPU 23 determines whether or not the range, class ID and contact relation data of the log data are stored (step ST31). When all are stored, the class identification processing ends. On the other hand, when the process is not completed, the processes in and after step ST21 are repeated.

For the class having the same number of contacts as the input / output contacts extracted in this way, it is judged whether or not the state changes of the two match, so that the log data in the range within the range is extracted from the extracted log data. Only the data about the contacts needed to understand the function can be obtained.
As a result, the log data can be functionally divided into a range that can be regarded as one block.

As described above, in the present embodiment, since the log data is functionally divided by using the log data in the ladder chart after the debug is completed, the ladder chart creator will explain the ladder chart functionally. There is no need to create drawings.

An example of a method of using the data after such class identification processing will be described with reference to FIGS.

The CPU 23 reads out the data shown in FIG. 14 (range, class ID, relationship data with contact points) (step ST51 in FIG. 15). The CPU 23 reads the corresponding symbol data from the hard disk 26 (step ST53). The CPU 23 displays the symbol and the corresponding contact data on the CRT 30 (step ST55). It is determined whether or not symbols and the like have been displayed for all the ranges (step ST57), and if not all, the next corresponding symbol data is read (step S).
T59). Then, the processing from step ST55 onward is repeated. If it is determined in step ST57 that all of them are displayed, the process ends. In this way, as shown in FIG. 16, the log data processing configuration displays the symbol data and the comment information of the contact in which the state change occurs. As a result, the procedure of processing in the program can be visually judged, and a third party other than the program creator can easily understand the sequence program.

Another method of using the data after the class identification processing will be described. As will be described below, by executing two ranges at the same time, debugging can be performed more effectively than in the case where one range is simulated.

For example, there are ladder charts shown in FIGS. 18 and 19, and the X portion "00200" shown in FIG.
(1U operation) is mistakenly "00201" (2U operation)
If the following error occurs, the following situation will occur.

When the portion shown in FIG. 18 is simulated by itself, it is difficult to find a bug, as will be described below. Turn off the contact for 1U operation "00200" 1
When the U stop switch is pressed, even if the X part is "0020
Even if it is erroneously described as "1" (2U operation), the output contact "00103" (defective forward) is turned off. Therefore, the operator overlooks whether or not there is a bug in the program, assuming that the operator performs the desired operation. Further, in the case of debugging the portion of the ladder chart shown in FIG. 19, when the contact “00201” (2U operation) is turned off, the output contact “00105” (make-advancing) and the output contact “0010”.
Since 6 ”(returning of injection) is turned off, it is determined that there is no bug in this case as well.

On the other hand, by executing the portions shown in FIGS. 18 and 19 at the same time, it can be found that the program shown in FIG. 18 has a bug as shown below. The program shown in FIG. 18 uses the input contact “0020
When "1" (2U operation) is turned off, the output contact "00103" (defective forward) should not be turned off. However, as shown in FIG. 20, when the input contact “00201” (2U operation) is turned off,
Output contact "00105" (close forward), output contact "00
106 "(closed after closing), the output contact" 0010
3 ”(defective forward) is turned off. This allows the operator to find the bug.

That is, when a contact which does not appear in the debug target part is described,
Debuggers are usually unaware of such contacts. Therefore, it is difficult to find a bug when moving that part alone. On the other hand, by executing them simultaneously in this way, it is possible to find out that there is a bug in the PLC sequence program without connecting to the actual system.

The simultaneous execution simulation will be described with reference to FIG. The CPU 23 stores the class-specific log data and symbol data in the hard disk 26.
Read out from the memory (step ST71). Next, the log data for each class is displayed side by side on the CRT 30 in the order of connection (step ST73).

The operator designates a class to be simultaneously executed (step ST75 in FIG. 17). The designation of the simultaneous execution class is performed by designating the class designated by the mouse 31.

Next, the operator inputs an input contact state change command (step ST77). Specifically, the switch box shown in FIG. 27 is displayed on the CRT 30, and a command for changing the state of the input contact is input with the mouse 31. C
The PU 23 gives the given state of the input contact to the PLC 34, and displays the state change based on the state of the output contact of the PLC on the switch box.

The operator observes the change in the state of the output contact to determine whether debugging is necessary. When debugging is required, a debug start command is input from the keyboard 28. When the debug start command is given, the CPU 23 displays the relevant ladder chart portion (step ST83 in FIG. 17). In the present embodiment, the display of the corresponding portion is performed by displaying the single ladder circuit portion and its front and rear portions for the single ladder circuit in which the state of the output contact has changed (ON to OFF or OFF to ON). It was In this way, by displaying the relevant part of the ladder chart related to the output contact during debugging, debugging can be easily performed.

The operator gives a correction instruction when the correction is necessary (step ST85). The CPU 23 returns the state of the output contact to the previous state (step ST87),
The processing from step ST77 onward is repeated. By the processing in step ST87, the state that was executed before debugging can be returned to, so that the operator does not need to return the state change of the input / output contact, and the re-simulation can be easily performed. Regarding the processing of step ST87, the previous state may be stored in the memory and read out as necessary.

Further, since the data for dividing the log data by function is stored, even when a change is made to replace a part of the system, the non-changed part of the log data can be judged. This allows the log data to be reused.

The ladder chart may be functionally divided based on the data that functionally divides the log data. Specifically, the portion of the single ladder circuit in which the changed contact is described in the log data may be extracted. In this way, it is easy to functionally divide the ladder chart.

In the present embodiment, the state change of the auxiliary contact is also extracted as the changed state contact. However, any one of the input contact, the output contact and the auxiliary contact is stored in the I / O table. The change of the auxiliary contact may not be extracted as the contact whose state has changed. As a result, the coincidence determination in step ST29 of FIG. 4 can be performed more efficiently.

In the present embodiment, the range of partial cutting out from the log data shown in FIG. 5 is set to 6 lines from the input portion immediately before the first output contact changed, but this is set to be long. You may do it. Even when the length is increased in this way, when the correspondence with the class database is performed, the associating process ends when there is no state change data of the corresponding class. Therefore,
This is because the subsequent lines will not be compared.

As described above, in determining the range for extracting the state change, the number of input / output contacts stored in the class database should be larger than the number of stored input / output contacts. For example, when the number of input / output contacts is maximum for input 3 and output 4, it is sufficient to perform partial cutting so as to include them.

As described above, when the length is set to be long, there is a problem that the number of input / output contacts to be extracted increases and the number of coincidence determination increases, but if the length is not too long, there is not much inconvenience. It should be noted that the clipping range may be set small and the clipping range may be increased when the corresponding class does not exist.

In the present embodiment, the changed input contact on the first line is judged to be the trigger condition and is not considered in the number of changes of the input contact of the class database.

4. Other Embodiments The processes of steps ST21 to ST27 shown in FIG. 4 may be processed as follows using the comment added to the sequence program.

Such processing will be described with reference to FIG. The CPU 23 extracts an input / output contact whose state changes according to the log data. Then, for each of the extracted input / output contacts, the comment is extracted as basic data by referring to the I / O table (see FIG. 6) (step ST111 in FIG. 21).

The dictionary section of the hard disk 26 is shown in FIG.
Basic word-related data as shown in is stored. In the present embodiment, the basic word-related data includes four types of information: type information, pair relationship information, causal relationship information, and synonym information. In this embodiment, the following “class”, “name”, “motion”, and “position” are adopted as the type information. The “class” is type information indicating the functions of a group of programs that have been collected to some extent in order to realize one function such as loading, inspection, and supply. The “name” is type information indicating the name of the control target device. “Operation” is type information indicating the operation of the control target device. "position"
Is type information indicating the position of the control target device.

The pair relationship information is information indicating the pair relationship of basic words, and for example, the basic word "forward" and the basic word "backward" have a pair relationship.

The causal relationship information is information indicating a basic word having a deep causal relationship with a certain basic word.
It represents the relationship between motion and position, such that when "advancing", the "front end" is reached. The relationship between the solenoid for controlling the movement of the cylinder and the sensor will be described below. The advance solenoid is turned on and the cylinder advances. When the cylinder reaches the front end, the sensor attached to the front end of the cylinder turns on. As a result, the solenoid is turned off and the movement of the cylinder is stopped. Such a relationship between the solenoid and the sensor is called a causal relationship.

The synonym information is information indicating that the basic words have the same meaning. For example, the basic word “forward end” corresponds to the basic word “forward end”.

The CPU 23 uses the basic word-related data to divide the basic data into basic word units (step ST113 in FIG. 21). For example, the comment “Driving S
Regarding “W”, referring to the basic word-related data, there is a basic word “driving” and also a basic word “SW”. Therefore, it is divided into these two "operations" and "SWs". The CPU 23 repeats such division processing for all the contacts, and creates the basic data shown in FIGS. 23 and 24 in the order of the contacts (FIG. 21, step ST11).
5).

Next, the CPU 23 classifies each contact point using the basic data shown in FIGS. 23 and 24 (step ST117 in FIG. 21). Contact point "0000
Pay attention to the basic word "detection" of the comment "defect detection front end" of "3. In the basic data of FIGS. 23 and 24, the other contact having this basic word “detection” is the contact “000”.
04 ”, contact“ 00103 ”, and contact“ 00104 ”. Therefore, it can be inferred that these four contact points belong to the same class. Further, in order to classify surely, pair information, causal relationship information, and synonym information may be used to determine whether or not the class belongs.

For example, it is understood that the basic word "rear end" is paired with the basic word "forward end", the basic word "forward" is causally related, and the basic word "forward end" is synonymous. .

Next, the CPU 23 divides the log data into parts in which the input / output contacts belonging to the same class are in a state change (step ST118 in FIG. 21).

Next, the contacts are associated (step ST119). Also in this association, pair information,
By using the causal information and the synonym information, it is possible to know the characteristics of the contact point, so that it is possible to perform the operation more quickly and reliably.

In the above embodiment, the basic words used for comments are limited to some extent. However, by storing a large number of synonyms, even when the basic words are expressed by various basic words. The division is possible.

In the present embodiment, the basic data (see FIGS. 23 and 24) having the basic word-related data of the basic words is created before the log data is divided, but the present invention is not limited to this. Instead, the basic word-related data may be referred to at the time of division.

Further, in this embodiment, when the log data is divided, the comment of the I / O table is extracted. However, the data is not limited to this, and any data may be used as a reference as long as the data includes a comment, and for example, a comment added to a time chart or ladder chart created when creating a program may be used.

In the present embodiment, the input / output contacts whose states have changed are extracted and the basic data is created only for these, but the data shown in FIGS. 23 and 24 are created in advance for all the contacts. Then, each contact may be classified into a class, and the characteristics (class, pair information, etc.) of each contact may be stored in the hard disk.

Further, the processing using such a comment may be applied only to either the log data division processing or the contact correspondence processing. As a result, the necessary dictionary data can be reduced. For example, when only contact points are to be associated, pair information, causal information, and synonym information may be stored.

In the present embodiment, all the input / output contacts that change the state are extracted from the log data, but they may be temporarily divided.

[0138] 5. Others In the class identification process of FIG. 3, it is assumed that there is a class to be identified, but if there is no corresponding class stored in advance, it may be registered as a new class. Good. In this case, since the appropriate range can be specified as one class by using the comment, the class can be registered more reliably.

Further, in the simultaneous simulation shown in FIG. 17, the steps ST77 and ST79 are executed manually, but the state change of the input contact is given to the CPU 23 by referring to the class log data. You may do it. Particularly, in this case, the CPU 23 determines whether the same output result as the output result of the class log data is given, and if not given, the process may automatically shift to the process of step ST83.
As a result, the operator does not need to open / close the input contact (operation of the switch box) when simulating, so that the debugging work can be simplified. By doing so, it is possible to easily find inconveniences that occur when they are executed simultaneously.

In this case, it is possible to switch the frame feeding mode which is executed step by step and the automatic feeding mode which is automatically executed.

In this embodiment, in order to simulate the PLC sequence program,
The case has been described as an example where the mutual relationship between the respective contact points is obtained. However, the present invention is not limited to this, as long as it is represented by a combination of a plurality of basic words and is given with characteristic data indicating the characteristic of each of the command input device or the state detector, the same applies to any one. Can be applied. For example, it is possible to obtain correlation data for simulation of a control system program such as a chemical plant or a nuclear reactor.

The controlled equipment corresponds to the cylinder and the motor in the above embodiment, but may be any equipment that performs a predetermined operation when a predetermined command is given. Of course, it is a concept including larger equipment such as a reactor and a reactor of a chemical plant.

Further, the state detector corresponds to a sensor in the embodiment, but includes any device as long as it can detect the state of the controlled device.

In this embodiment, a normal PLC 34 is connected as a debug device for a sequence program, and the sequence program stored in the PLC 34 is read to extract input / output contacts required for debugging. . However, such PLC34
Alternatively, the sequence program to be debugged may be stored in the hard disk 26 without being connected, and an execution means for executing the sequence program may be further provided.

In the present embodiment, the CPU 23 is used to realize each of the functions described above, and this is realized by software. However, some or all of them may be realized by hardware such as a logic circuit.

[Brief description of the drawings]

FIG. 1 is a functional block diagram of a debugger 1 according to an embodiment of the present invention.

FIG. 2 is a diagram showing a hardware configuration in which a debugger 1 shown in FIG. 1 is realized by a CPU.

FIG. 3 is a diagram showing an overall flowchart.

FIG. 4 is a flowchart of class identification processing.

FIG. 5 is a diagram showing an example of log data.

FIG. 6 is a diagram showing an I / O table.

FIG. 7 is a diagram showing input / output contacts whose states change and comments in the first and second lines of the log data of FIG.

8 is a diagram showing input / output contacts whose states change and comments in the third and fourth lines of the log data of FIG. 5. FIG.

9 is a diagram showing input / output contacts whose states change and comments on lines 5 and 6 of the log data of FIG. 5. FIG.

10 is a diagram showing input / output contacts whose states change and comments on lines 7 and 8 of the log data of FIG. 5. FIG.

FIG. 11 is a diagram showing the extracted input contact and output contact whose state has changed.

FIG. 12 is a diagram showing the number of input / output contacts whose states change in each class and the state change data.

FIG. 13 is a diagram showing image data of classes 0 and 1.

FIG. 14 is a diagram showing analysis data for analyzing log data.

FIG. 15 is a flowchart showing a function display process.

FIG. 16 is a view showing a connection state of class-specific symbols displayed on the CRT 30.

FIG. 17 is a flowchart for performing simultaneous simulation.

FIG. 18 is a diagram showing one ladder chart that is simultaneously executed.

FIG. 19 is a diagram showing another ladder chart simultaneously executed.

FIG. 20 is a diagram showing a time chart in the case of simultaneous execution.

FIG. 21 is a flowchart for performing processing using a comment.

22 is a diagram showing an example of data in a dictionary section of the hard disk 26. FIG.

FIG. 23 is a diagram showing a data structure of basic data.

FIG. 24 is a diagram showing a data structure of basic data.

FIG. 25 is a diagram showing an outline of a system configuration controlled by a PLC (prior art).

FIG. 26 is a ladder chart for controlling the system of FIG. 24 (prior art).

FIG. 27 is a ladder chart for controlling the system of FIG. 24 (prior art).

FIG. 28 is a diagram showing a software wear switch box and an output monitor (prior art).

[Explanation of symbols]

 3 ... Data storage means by pattern 5 ... Specification means 11 ... Temporary division means 13 ... Match determination means 15 ... Re-determination determination means 17 ... State change storage data identification means

[Procedure amendment]

[Submission date] November 14, 1995

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] 0065

[Correction method] Change

[Correction contents]

When the state of the input contact is given, the analyzer 1 analyzes the state change record data of the input / output contact of the programmable logic controller which changes the state of the output contact based on the stored sequence program. A device for displaying the state change storage data, and when the state change storage data is given, a display for identifying the state change portion of the input / output contact that can be regarded as one set functionally and displaying the analysis result of the state change storage data. It can be grasped as a state change record data analysis device of the input / output contact characterized by including the means .

[Procedure amendment 2]

[Document name to be amended] Statement

[Name of item to be corrected] 0070

[Correction method] Change

[Correction contents]

3. Flowchart Next, the program stored in the hard disk 26 will be described with reference to FIG. 3. First, the CPU 23 sets the simulation mode (step ST5 in FIG. 3). The simulation is similar to the conventional one, but will be briefly described.

[Procedure 3]

[Document name to be amended] Drawing

[Correction target item name] Fig. 1

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 4]

[Document name to be amended] Drawing

[Correction target item name] Figure 2

[Correction method] Change

[Correction contents]

[Fig. 2]

[Procedure Amendment 5]

[Document name to be amended] Drawing

[Correction target item name] Figure 3

[Correction method] Change

[Correction contents]

[Figure 3]

[Procedure correction 6]

[Document name to be amended] Drawing

[Correction target item name] Fig. 4

[Correction method] Change

[Correction contents]

FIG. 4

[Procedure amendment 7]

[Document name to be amended] Drawing

[Correction target item name] Fig. 5

[Correction method] Change

[Correction contents]

[Figure 5]

[Procedure amendment 8]

[Document name to be amended] Drawing

[Correction target item name] Fig. 6

[Correction method] Change

[Correction contents]

FIG. 6

[Procedure amendment 9]

[Document name to be amended] Drawing

[Name of item to be corrected] Figure 7

[Correction method] Change

[Correction contents]

FIG. 7

[Procedure amendment 10]

[Document name to be amended] Drawing

[Correction target item name] Fig. 8

[Correction method] Change

[Correction contents]

[Figure 8]

[Procedure amendment 11]

[Document name to be amended] Drawing

[Correction target item name] Figure 9

[Correction method] Change

[Correction contents]

FIG. 9

[Procedure amendment 12]

[Document name to be amended] Drawing

[Name of item to be corrected] Fig. 10

[Correction method] Change

[Correction contents]

FIG. 10

[Procedure amendment 13]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 11

[Procedure Amendment 14]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure Amendment 15]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 13

[Procedure Amendment 16]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 14

[Procedure amendment 17]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 18]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 16

[Procedure amendment 19]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 20]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 21]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 22]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 23]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 21

[Procedure amendment 24]

[Document name to be amended] Drawing

[Correction target item name] Fig. 22

[Correction method] Change

[Correction contents]

FIG.

[Procedure amendment 25]

[Document name to be amended] Drawing

[Correction target item name] Fig. 23

[Correction method] Change

[Correction contents]

FIG. 23

[Procedure amendment 26]

[Document name to be amended] Drawing

[Correction target item name] FIG.

[Correction method] Change

[Correction contents]

FIG. 24

[Procedure amendment 27]

[Document name to be amended] Drawing

[Correction target item name] Fig. 25

[Correction method] Change

[Correction contents]

FIG. 25

[Procedure amendment 28]

[Document name to be amended] Drawing

[Correction target item name] FIG. 26

[Correction method] Change

[Correction contents]

FIG. 26

[Procedure amendment 29]

[Document name to be amended] Drawing

[Correction target item name] FIG. 27

[Correction method] Change

[Correction contents]

FIG. 27

[Procedure amendment 30]

[Document name to be amended] Drawing

[Correction target item name] FIG. 28

[Correction method] Change

[Correction contents]

FIG. 28

Claims (13)

[Claims] 1. A device for analyzing state change record data of an input / output contact of a programmable logic controller, which changes a state of an output contact based on a stored sequence program when a state of an input contact is given. A pattern-based data storage unit that stores a plurality of state changes of input / output contacts that can be functionally regarded as one set in advance as pattern-based data. When the state change storage data is given, the pattern-based data is referred to. An input / output contact state change record data analysis apparatus comprising: an identifying unit that identifies a range of the state change storage data corresponding to the pattern-specific data. 2. The input / output contact state change record data analyzing apparatus according to claim 1, wherein A) the pattern-based data storage means has the number of input / output contacts whose state changes in the pattern-based data for each pattern. Is stored as index data, and B) the specifying means has the following means b1) to b3), and b1) the storage data is temporarily divided so as to include a predetermined number of input / output contacts whose states change. Dividing means, b2) Matching judging means for judging whether or not the pattern-wise data in which the number of input / output contacts whose states change is the same for the temporarily divided data match the change in state of the input / output contacts, b3) The matching When the judgment is obtained, the state change memory data specifying means for specifying the state change memory data part corresponding to the coincident part as a range corresponding to the pattern-specific data, input / output contact State-change recording data analysis apparatus. 3. The input / output contact state change record data analyzing apparatus according to claim 2, wherein the specifying means further determines a part of the contacts in the temporarily divided data when the coincidence determination cannot be obtained. A state change record data analysis device for input / output contacts, comprising re-judgment determining means for removing the coincidence judging object and causing the coincidence judging means to make a judgment again. 4. The input / output contact state change record data analyzing apparatus according to claim 1, wherein A) each of the input / output contacts is represented by a combination of a plurality of basic words and is connected to the input / output contact. Characteristic data indicating the characteristics of B), B) the specifying means has the following means b1) to b4), and b1) basic word related data representing attributes and relationships of basic words, Dictionary means for storing each word, b2) Inference division means for inferring mutual relation data relating to each input / output contact based on the basic word relation data and the characteristic data, and dividing the state change record data, b3) Concerning the divided data, coincidence determination means for determining whether or not the state change of the input / output contacts matches the pattern-based data having the same number of input / output contacts whose states change, b4) When the coincidence determination is obtained Status change stored data specifying means for specifying a range to the appropriate state change stored data portion corresponding to the matching portion in the pattern specific data, the state change recording data analyzer input and output contacts, characterized in. 5. The state of the input / output contact according to claim 4, wherein the specifying means associates the contact of the input / output contact with each other based on the inferred mutual relation data. Change record data analyzer. 6. A device for analyzing and displaying state change record data of an input / output contact of a programmable logic controller for changing the state of the output contact based on a stored sequence program when the state of the input contact is given. In addition, when the state change memory data is given, a display unit that specifies a state change portion of the input / output contact that can be functionally regarded as one set and displays an analysis result of the state change memory data is provided. A data analysis device for recording state changes of input / output contacts. 7. A method for analyzing state change record data of an input / output contact of a programmable logic controller, which changes a state of an output contact based on a stored sequence program when a state of an input contact is given. , A plurality of state changes of the input / output contacts that can be regarded as one set functionally are stored as pattern-specific data, and when the state change storage data is given, the state change is referred to by referring to the pattern-specific data. A method for analyzing state change record data of input / output contacts, characterized in that a range corresponding to the pattern-based data is specified in the stored data. 8. The method for analyzing state change record data of input / output contacts according to claim 7, wherein A), for each pattern, the number of input / output contacts whose state changes in the pattern-specific data is stored as index data. B) The identification is performed according to the following procedure: b1) Temporarily divides the stored data so that a predetermined number of input / output contacts whose states change is included, and b2) Inputs whose states change about the temporarily divided data. When it is determined whether or not the pattern change data having the same number of output contacts and the state change of the input / output contacts match, b3) When the match determination is obtained, the state change storage data portion corresponding to this match portion is written A method for analyzing the state change record data of the input / output contact, characterized in that it is specified as the range corresponding to the data for each pattern. 9. The input / output contact state change record data analysis method according to claim 8, wherein when the coincidence determination cannot be obtained, some contacts in the temporarily divided data are excluded from the coincidence determination target, A method for analyzing state change record data of an input / output contact, characterized in that the determination as to whether they match is repeated. 10. The method for analyzing state change record data of an input / output contact according to claim 7, wherein A) each of the input / output contacts is represented by a combination of a plurality of basic words and is connected to the input / output contact. Characteristic data indicating the characteristics of B), B) the identification is performed according to the following procedure, b1) basic word related data representing attributes and relationships of basic words are stored for each basic word. A) b2) based on the basic word-related data and the characteristic data, inferring mutual-related data regarding each of the input / output contacts, dividing the state change recording data, and b3) changing the state of the divided data. If the coincidence judgment is obtained, the status change memory corresponding to this coincidence part is judged. State change recording data analysis method of the input and output contacts, wherein, to identify the over data portion as a range corresponding to the pattern specific data. 11. The method of analyzing recorded data according to claim 10, wherein the contact of the input / output contact is made to correspond based on the inference result. 12. A method of analyzing and displaying state change record data of an input / output contact of a programmable logic controller that changes the state of an output contact based on a stored sequence program when the state of an input contact is given. When the state change storage data is given, the state change portion of the input / output contact which can be regarded as one set functionally is specified, and the analysis result of the state change storage data is displayed. Analyzing method of recorded data of input / output contact state change. 13. A computer-readable storage medium storing a program for realizing the device or method according to any one of claims 1 to 12 by using a computer.