JP3373163B2 - Program editing device for programmable controller - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program editing device for programming a sequence program used in a programmable controller, and more particularly to programming of a sequence program used in a programmable controller in which a plurality of programmable controllers for controlling a mechanical equipment group cooperate with each other. The present invention relates to a program editing device for performing.

[0002]

2. Description of the Related Art Conventionally, programmable controllers (hereinafter referred to as "P") have been used to control the sequence of mechanical equipment.
C) is used, and in order to control complicated mechanical equipment, a plurality of PCs may be linked to each other to construct a system. The cooperation between the PCs is to publish information to be shared with other PCs among the information in the own PCs, and start or stop control of the own PCs by referring to the shared information published by the other PCs.

FIG. 23 shows a general example of a PC link system for controlling the sequence of mechanical equipment by a plurality of PCs that cooperate with each other. 1st PC main body (CPU unit) 50 ₁ , 2nd PC main body 50 _{2 to} nth PC
The communication unit 60 ₁ to 60 _n are connected to the respective body 50 _n, are communicatively coupled to one another communication unit 60 ₁ to 60 _n is the network communication line 70.

The memory 51 _{1 of the} PC body 50 ₁ to 50 _n
51 _n has an in-PC information memory unit 52 _{1 to} 52 _n that stores information necessary for controlling the own device, and a part of this in-PC information memory unit 52 _{1 to} 52 _n is another PC (another device). To the public information part 53 _{1 to} 5 which stores the information to be disclosed by itself
There are 3 _n .

A data sharing information memory unit 62 is allocated to the memory 61 of the communication unit 60 ₁ of the parent PC, here the first PC body (CPU unit) 50 ₁ . The data in the data sharing information memory unit 62 is information that is transferred by the PC-to-PC network communication and is shared between the connected PCs.
Is, the first unit PC public information portion 53 ₁ and the contents of public information portion 62 _1, a Second PC public information portion 53 ₂ and the contents of public information portion 62 ₂ of ~n stand eyes of PC of of of Each PC based on the public information part 53 _n and the public information part 62 _n having the same content
It consists of the public information part of.

[0006] Public information portion 62 ₁ of the PC 50 public information portion 53 ₁ and the data shared information memory section 62 in _1,
Public information part 53 of the PC 50 _{2 2} and data sharing information public information portion 62 ₂ to PC body 50 in the memory portion 62
Public information in _n part 53 _n and data sharing information memory section 6
In the public information part 62 _{n in} 2, each PC transfers the information of the public information part inside itself to the corresponding data sharing information memory while the data of the data sharing information memory part 62 is transferred by network communication. By reflecting in the public information parts 62 _{1 to} 62 _n in the part 62, the same contents are always maintained.

As a result, each PC can know the status of another PC by referring to the shared information in the data shared information memory unit 62. Each PC controls in accordance with a sequence program for performing sequence control in cooperation with other PCs.

24 and 25 show a PC main body 50 ₁ and a PC.
The sequence program in the case of operating in cooperation with the main body 50 ₂ is shown using a generally popular ladder circuit.

In FIG. 24, 100 is a PC main body 50 ₁
Is a condition determination command for determining whether or not the state of the external contact (X1) of the shared information contact (B1) in the data shared information memory unit 62 is true if the condition on the left is true.
0) is an output command unit for turning on.

In FIG. 25, 110 is a condition determination command for determining whether or not the shared information contact (B0) in the data shared information memory unit 62 is on, and 111 is the external contact (X0) of the PC main body 50 _2. Is a condition determination command for determining whether or not is ON. Since the condition determination commands 112 on the left are arranged in series, the internal contact (Y10) of the PC main body 50 ₂ is turned on only when these conditions are true. It is an output command section.

25 and the ladder circuit shown in FIG.
By linking the ladder circuits shown in
External contact (X1) 100 of the main body 50 ₁ is turned further in the case where the external contacts (X0) 111 of the PC 50 ₂ is turned on, the internal contact (Y10) 112 of the PC 50 ₂ will be turned on.

In this way, when the PCs are linked,
The data in the data sharing information memory unit 62 can be mutually output and referred to.

[0013]

In the above-mentioned conventional system, since the amount of information that can be shared is finite, the information shared between the PCs can be shared by all PCs that cooperate in advance.
It is necessary to make an agreement between them, which complicates the creation of the sequence program.

Further, in the conventional system, it is necessary to set the range of shared information for each PC in order to cooperate with a plurality of PCs, which complicates the creation of the sequence program and causes an error in the setting information. If there is, there is a problem that the PCs of both do not operate normally.

Further, in the conventional system, the condition determination command based on the shared information state must be added to the sequence program for controlling the own PC, which causes a problem that the creation of the sequence program becomes complicated.

The present invention has been made to solve the above-mentioned problems, and obtains a program editing device for efficiently and accurately creating a program for a sequence program used by a programmable controller in which a plurality of programmable controllers cooperate with each other. The purpose is to

[0017]

In order to achieve the above-mentioned object, a programmable controller program editing apparatus according to the present invention is a program editing apparatus for creating a sequence program for use in a programmable controller in which a plurality of programmable controllers cooperate with each other. , A programmable controller unique name for registering information identifying a programmable controller to which a device belongs, and a shared information collection table for registering the name of a device which is an interlock condition are stored in the memory and registered in the shared information collection table. Based on the data
A trigger program including an external contact and a shared information contact is automatically added to the sequence program of the corresponding programmable controller, and the shared information contact of the trigger program is connected to the PC interlock contact in the sequence program of the programmable controller targeted for inter-PC interlock. The program creation processing is automatically added as.

According to another aspect of the present invention, there is provided a program editing device for a programmable controller, which includes a PC interlock contact instruction and a PC interlock contact instruction set in an original sequence program of a programmable controller to be interlocked between PCs.
A program creating process for automatically adding the inter-PC interlock contact to all the programs during the inter-interlock end instruction is performed.

A programmable controller program editing apparatus according to the next invention has a device description section in which the PC interlock contact instruction is a programmable controller proper name of the PC interlock and an interlock condition, and the original sequence program The inter-PC interlock contact instruction is extracted and the shared information collection table is automatically created from the data of the inter-PC interlock contact instruction.

A program editing device for a programmable controller according to the next invention is a program editing device for creating a sequence program to be used by a programmable controller in which a plurality of programmable controllers cooperate with each other. It has a shared information collection table in memory that registers the controller unique name and the name of the device that is the interlock condition,
Based on the data registered in the shared information collection table in the step of one sequential execution type program in which the unique name of each programmable controller is given to each step and the interlock contact between PCs is described as a transition condition A trigger program including a contact and a shared information contact is automatically added, and the shared information contact of the trigger program is added as an inter-PC interlock contact to the sequence program in the step corresponding to the transition condition, and the one sequential execution type The program creating process is performed in which the program is separated for each step and automatically converted into a sequence program for each programmable controller.

In the programmable controller program editing apparatus according to the next invention, the programmable controller unique name attached to each step and the inter-PC interlock contact described in one sequential execution type program as a transition condition, The shared information collection table is automatically created.

A programmable controller program editing apparatus according to the next invention automatically detects the device range of the shared information contact for each programmable controller from the data content of the shared information collection table, and the device of the shared information contact for each programmable controller is detected. A shared information memory definition table indicating a range is automatically created.

[0023]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of a programmable controller program editing apparatus according to the present invention will be described in detail below with reference to the accompanying drawings.

Embodiment 1. FIG. 1 shows a hardware configuration of a program editing device (peripheral device) of a programmable controller according to the present invention. Program editing device 1
Reference numeral 0 has a processing unit 11 including a CPU, a memory 12, an auxiliary storage device control unit 13, a key input control unit 14, and a screen control unit 15, and the auxiliary storage device control unit 13 has an auxiliary storage unit. The device 16 includes the keyboard 1 in the key input control unit 14.
7, and a CRT 18 is connected to the screen control unit 15.

The memory 12 of the program editing device 10 is
PC unique name management table 20 for the program editing apparatus 10 to grasp the PC connected to the network
A shared information collection table 21 and a shared information memory map definition table 22 described later are stored.

As shown in FIG. 2, the PC unique name management table 20 shows the total P connected to the network.
Data part 20a of C number and P uniquely attached to each PC
A data section 20b indicating a C unique name is allocated. The data is stored in the program editing device 10 by inputting a PC unique name arbitrarily given by the user for all PCs connected to the network.

FIG. 3 shows an example of an original sequence program edited by the program editing apparatus 10. This original sequence program allows the user to use another PC (PC in this case).
It is a sequence program of the PC 2 that specifies to interlock with the shared information of 1).

In FIG. 3, 120 is an inter-PC interlock contact instruction which can be used in the program editing device 10,
121 indicates an external contact, 122 indicates an internal contact, and 123 indicates an inter-PC interlock end instruction that can be used in the program editing apparatus 10. The inter-PC interlock contact instruction 120 has a unique name of the PC to be interlocked and a description part of the external contact of the PC. Note that P
C1 and PC2 are equivalent to those of the PC system shown in FIG.

The shared information collection table 21 is stored in the memory 12 in order for the program editing apparatus 10 to grasp a device which is an interlock condition of a program of another PC among PCs connected to the network. Yes, and as shown in FIG.
A PC unique name column 21a for registering information identifying C, a device column 21b for registering the name of a device which is an interlock condition, and a P unique name and a device specific P
Reflection flag string 21 for registering flag information indicating whether the interlock contact information between Cs is reflected in the program
It is composed of c.

The shared information collection table 21 includes a PC unique name management table 20 as shown in FIG. 2, and FIG.
Data is automatically stored by the program editing device 10 from the contents of the sequence program illustrated in FIG. That is, the shared information collection table 21 is automatically created from the inter-PC interlock contact instruction data by extracting the inter-PC interlock instruction in the original sequence program.

Based on the data in the shared information collection table 21, the program editing apparatus 10 causes the sequence program for the PC 1 to use the external contact (X0) 130 and the shared information contact (B0) as shown in FIG. A trigger program including 131 is automatically added. The program editing device 10 interlocks all the sequence programs from the inter-PC interlock contact instruction 120 to the inter-PC interlock end instruction 123 by the external contacts of the PC designated by the inter-PC interlock contact instruction 120. Automatically converted to. This is done by automatically adding the shared information contact of the trigger program to the sequence program of the corresponding range as the inter-PC interlock contact.

[0032] Figure 6 shows a sequence program to convert automatically by PC2 program editing apparatus 10 a sequence program for that shown in FIG. 3, between the PC from the PC between the interlock contact point instructions 120 interlock final Share information contacts to each step until Ryoyubi shows 123 (B
0) are added in series.

Shared information memory map definition table 22
Is stored in the memory 12 in order for the program editing apparatus 10 to grasp the device range of the information shared between the PCs connected to the network. As shown in FIG. It has a unique name column 22a and a device range column 22b showing the device range of the shared information contact for each programmable controller. The shared information memory map definition table 22 is the shared information collection table 2
It is automatically generated by automatically detecting the device range of the shared information contact for each programmable controller from the data content of 1.

The program editing device 10 uses the data in the shared information memory map definition table 22 to store each of the data shared information memory units 62 held by a communication unit equivalent to the communication unit 60 ₁ of the parent PC shown in the conventional example. The public information parts 62 ₁ , 62 _2, ... Of the PC are automatically mapped as shown in FIG. In other words,
Data sharing information memory map is automatically generated.

Next, the operation will be described. It is assumed that there is a network system configuration as shown in FIG. First, the user gives arbitrary unique names to all the PCs existing on the network. By the user input, the program editing apparatus 10 stores the total number of PCs existing on the network in the total number of PCs 20a of the PC unique name management table 20 shown in FIG. 2, and the PC unique name 20b exists on the network. The unique names of all the PCs to be registered are registered.

Assume that an original sequence program as shown in FIG. 3 is created for the second PC 2. The method of designating the interlock condition between PCs in this original sequence program is a method determined for the sake of easy understanding by the user, and thus cannot be actually used in the PC as it is.

Therefore, the program editing apparatus 10 is also subjected to a conversion process for creating a sequence program as shown in FIGS. 5 and 6 so that the PC can perform the expected operation. This conversion process is performed by the user using the keyboard 17
Is started by issuing a conversion instruction. This conversion process is performed according to the flowchart shown in FIG.

When the conversion process starts, first, the shared information collection table 21 is created (step S150).
The shared information collection table 21 is created according to the flow chart shown in FIG. After the shared information collection table 21 is created, the shared information memory map definition table 22 is created (step S1).
51). Creation of the shared information memory map definition table 22 is performed according to the flowchart shown in FIG.

When the creation of the shared information memory map definition table 21 is completed, all the reflection flags of the shared information collection table 21 are initialized in a non-reflected state (step S152), after which the interlock part program substitution is performed. The process (step S153) is performed. The interlock program substitution process is performed according to the flowchart shown in FIG. Here, the unreflected state is the reflection flag = “0”, and the flag in the state where the processing related to this shared information has been reflected in the program = “1”.
Will be distinguished from

Creation of the shared information collection table will be described with reference to the flow chart shown in FIG. First, the registration number counter N is set to 0 (step S200). Next, it is checked whether the programs for all the PCs registered in the PC proper name management table 20 have been checked (step S201), and if all the programs have been checked, the process ends.

If all the programs have not been checked, it is judged whether or not the checked portion of the shared information collection is the end of the program (step S).
202). At the end of the program, check the next program. If it is not the end of the program being checked but is in the middle, it is checked whether the check target is an instruction in the format of the inter-PC interlock contact instruction 120 (step S203). If it is not the inter-PC interlock contact instruction 120, it is determined that there is no information to be acquired in the shared information collection table, and step S2
Returning to 02, the next part of the program is checked.

[0042] In the case of the PC between the interlock contacts instruction 120, PC unique name for N-th row of the shared information collection table 21 and the PC unique name to extract the PC proper name from the description of the PC between the interlock contacts instruction 120 It is registered in the data field (step S204). Next, the external contact is extracted from the inter-PC interlock contact instruction 120 and registered in the device data field of the Nth row of the shared information collection table 21 (step S205).

Next, the reflection flag of the Nth row of the shared information collection table 21 is initialized in the unreflected state (step S
206). As a result, the setting of the information of one inter-PC interlock contact instruction 120 in the shared information collection table 21 is completed. Next, the registered device number counter N
= N + 1 is performed (step S207), and the process returns to step S202 to collect the next information.

When the check is completed for the programs of all PCs, the P connected to this network is
The shared information collection table 21 in which the information on the device names that C needs to share is stored is completed.

The creation of the shared information memory map definition table will be described with reference to the flowchart shown in FIG. First , the device usage counter N for each PC is set to N = 0 (step S250). Next, it is checked whether the programs for all the PCs registered in the PC unique name management table 20 have been checked (step S251). If the programs of all the PCs have been checked, the process ends.

When the programs of all the PCs have not been checked, the shared information collection table 21 is checked in order to check the programs of the PCs that have not been checked by referring to the shared information collection table 21 from the beginning. The reference registration information number counter J referred to by is set to 0 (step S252).

Next, it is checked whether the reference registration information number counter J is at the end of the shared information collection table 21 (step S253). If the reference registration information number counter J is at the end of the shared information collection table, it means that the check of the shared information collection table 21 for the PC of this unique name has been completed, so the shared information memory map definition table 2
The PC unique name is registered in the PC unique name data field No. 2 and N is registered as the number of devices used in the device range data field (step S262) , and the process returns to step S250 to check the next PC unique name.

If the reference registration information number counter J is not at the end of the shared information collection table, it is checked whether the reflection flag of the row of the reference registration information number counter J of the shared information collection table 21 is "0" and it has not been reflected. Yes (step S254). When the reflection flag of the row of the reference registration information number counter J of the shared information collection table 21 is “1”,
Assuming that the information of the corresponding line has already been reflected, the reference registration information number counter J = J + 1 is set (step S263),
It returns to step S253.

On the other hand, the reflection flag of the row of the reference registration information number counter J of the shared information collection table 21 is "0".
In this case, since this shared information has not been reflected on the device yet, it is checked whether the PC unique name at the position of the reference registration information number counter J in the shared information collection table 21 is the PC unique name currently being checked. (Step S2
55). When the PC unique name in the row of the reference registration information number counter J of the shared information collection table 21 is not the PC unique name currently being checked, this shared information is ignored and the reference registration information number counter J = J + 1 is set (step S26).
3) and returns to step S253.

The PC unique name in the row of the reference registration information number counter J of the shared information collection table 21 is P which is currently checked.
In the case of the C unique name, it is assumed that there is information about a new device that needs to be shared with this PC, and the device usage number N = N + 1 is set (step S256).

Next, "1" is assigned to the reflection flag of the shared information collection table 21 to indicate that the information has already been reflected (step S257). Then, in order not to doubly count the information on the same device as this device as the number N of shared devices used, it is necessary to search the reference registration information number counter J of the shared information collection table 21 and thereafter for the information on the same device. , Set the registration information number counter I for the same device search, and set I = J +
1 (step S258).

Next, it is checked whether the registration information number counter I for searching the same device is at the end of the shared information collection table 21 (step S259). If the registration information number counter I for searching the same device is the last in the shared information collection table 21, it means that the search for the same device has been completed, so the reference registration information number counter J = J + 1 is set (step S263), step S253. Return to.

On the other hand, if the device search registration information counter I is not at the end of the shared information collection table 21, the shared information at the position of the reference registration information number counter J and the device search registration information number counter I is the same. It is checked whether the devices in the collection table 21 are the same (step S260). If the devices are different, the same device search registration information number counter I = I + 1 is set (step S
264) and the process returns to step S259.

If the device of the shared information collection table 21 is the same as the reference registration information number counter J and the information of the same device search registration information number counter I, the information of the same device search registration information number counter I has already been calculated. It is considered that the reflection has been completed by the reference registration information number counter J, and "1" is set to the reflection flag of the shared information collection table in the row of the registration information number counter for identical device search I as already reflected (step S261).

Next, the same device search registration information number counter I = I + 1 is set (step S264), and the process returns to step S259. When the check of the shared information collection table 21 is completed for all the PC unique names, the shared information memory map definition table 22 storing the necessary range information of the shared device for the PC connected to this network is automatically created. To be done.

The interlock program substitution process will be described with reference to the flow chart shown in FIG. First, the shared device number counter N = 0 is set (step S300). Next, it is checked whether the programs for all PCs have been checked (step S30).
1). If all programs have been checked, the process ends. If all programs have not been checked, the program check position counter J is set to 0 (step S302).

Next, it is checked whether the checked part is the end of the program (step S303). If the checked portion is the last of the program, trigger program substitution is performed (step S311). The trigger program substitution process is performed according to the flowchart shown in FIG. When the process related to the shared device indicated by the shared device number counter N is completed by the trigger program substitution process, the shared device number counter N = N + 1 is performed (step S310), and step S310.
Return to 301.

If the checked part is not the end of the program, it is checked whether the checked part is in the format of the inter-PC interlock contact instruction 120 (step S304). Interlock contact instruction between PCs 120
If not, the program check position counter J
= J + 1 (step S312), and step S30
Return to step 3 and check the next part of the program.

In the case of the inter-PC interlock contact instruction 120, next, the inter-PC interlock end instruction 123.
Whether or not it is checked (step S305). PC
In the case of the inter-interlock end instruction 123, the program check position counter J = J + 1 is performed (step S
312) and returns to step S303 to check the next part of the program.

If it is not the inter-PC interlock end instruction 123, the program check position counter J = J +
1 (step S306), the inter-PC interlock contact instruction 120 to the inter-PC interlock end instruction 12
Since it is necessary to interlock all programs up to 3 under the conditions specified by the interlock contact between PCs, the shared information contact 140 is placed in front of the external contact 121 attached to the line on the left side of the ladder diagram. I have to add. Therefore, next, it is checked whether or not it is the external contact 121 attached to the line on the left side of the ladder diagram (step S
307). If it is not the external contact 121 attached to the left line, the process returns to step S305.

On the other hand, in the case of the external contact 121 attached to the left line, the shared information contact 140 is added to the current portion.
Is inserted (step S308). By this insertion, the position counter J from the beginning of the program is displaced, so the program check position counter J = J + 1 is performed (step S309), and the process returns to step S305. All PC
When the check is completed for this program, it means that the insertion of the instruction regarding the interlock between the PCs has been completed in the program of the PC connected to this network.

The interlock trigger program substitution process will be described with reference to the flowchart shown in FIG. First, the reference registration number counter J of the shared information collection table 21 is set to 0 (step S350). Next, the reference registration number counter J displays the shared information collection table 2
It is checked whether it is the end of 1 (step S351). In the case of the last of the shared information collection table 21, the processing is ended.

If the reference registration number counter J is not at the end of the shared information collection table 21, it is checked whether the reflection flag of the row of the reference registration number counter J of the shared information collection table 21 is "0" which is not reflected (step). S353).
When the reflection flag is not “0” which is not reflected, the reference registration number counter J = J + 1 is set (step S361), and the process returns to step S351.

When the reflection flag 131 of the row J of the shared information collection table 21 is "0" and is not reflected, the PC unique name of the row J of the shared information collection table 21 is the PC unique name currently being checked. Check whether (step S35)
4). If it is not the PC unique name currently being checked,
As reference registration number counter J = J + 1 (step S3
61) and the procedure returns to step S351.

In the case of the PC unique name currently being checked,
At the end of the program, a trigger program as shown in FIG. 5 for turning on the shared information contact 131 with respect to turning on the external contact 130 is added (step S355). As a result, the reflection processing of the shared device information of the row J of the shared information collection table 21 to the program is completed, and thus "1" is substituted into the reflection flag of the shared information collection table 21 at the position of the reference registration number counter J. (Step S
356).

The reference registration information number counter J of the shared information collection table 21 is set in order not to double insert the trigger program for the same device as this device.
After that, the same device search registration information number counter I is set, and I = J + 1 is set to search for information regarding the same device (step S357).

Next, it is checked whether the registration information number counter I for searching the same device is at the end of the shared information collection table 21 (step S358). When the registration information number counter I for searching the same device is the last in the shared information collection table 21, it is determined that the search for the same device is completed, the reference registration number counter J = J + 1 is set (step S361), and the process returns to step S351.

If the same device search registration information number counter I is not at the end of the shared information collection table 21, the shared information collection table 21 at the position of the reference registration number counter J and the same device search registration information number counter I.
It is checked whether the device and the PC unique name are the same (step S359). If they are different, the same device search registration information number counter I = I + 1 is set (step S3).
62) and the process returns to step S358. In the case of the same, "1" is substituted for the reflection flag of the shared information collection table 21 in the row of the registration information number counter I for the same device search (step S360), and it is determined that the reflection processing for this information is completed Registration information number counter I for search
= I + 1 (step S362), step S358
Return to.

When the reflection of all the shared information is completed, all the trigger programs of the shared device necessary for the interlock are inserted at the end of the program of each PC, and the device of the internal contact set by the user with the interlock contact is turned on. By doing so, the automatically assigned corresponding shared device is turned on.

Since the shared information contact 140 for interlock regarding the corresponding shared device is automatically inserted by the interlock part program substitution processing routine, the user does not have to be aware of the shared device when executing the program. By turning on / off the device of the interlock contact between PCs designated by itself, the program is interlocked until the interlock end instruction between PCs.

The range of the automatically allocated shared device is stored in the shared information memory map definition table 22 by the shared information memory map definition table creating routine, so that it can be referred to as necessary.

Embodiment 2. FIG. 14 shows a hardware configuration of a program editing device (peripheral device) of a programmable controller according to the present invention. The program editing device 30 includes a processing unit 31 including a CPU and the like, a memory 32,
It has an auxiliary storage device control unit 33, a key input control unit 34, and a screen control unit 35. The auxiliary storage device control unit 33 has an auxiliary storage device 36, the key input control unit 34 has a keyboard 37, and a screen. A CRT 38 is connected to each of the control units 35. The memory 32 of the program editing device 30 is
A shared information collection table 41 and a shared information memory map definition table 42 described later are stored.

FIG. 15 shows an example of a sequential execution type program edited by the program editing device 30. This sequential execution type program is composed of a plurality of PCs, and a sequence program, which must be separately written for each PC in the past, is written in one. Figure 1
The sequential execution type program illustrated in 5 is an initial step (process 1) corresponding to the program of the first PC, a step (process 2) corresponding to the program of the second PC, and a program of the third PC. The corresponding step (process 3) is described as one program.

Each step has a separate label S1, S
2 and S3 are attached, and each label S1, S2, and S3 is attached with a PC unique name for executing the sequence. Each step has an in-step sequence A, B, C.

Next to the in-step sequence A of the process 1, a transition T2 which is a condition judgment for moving from the process 1 to the process 2 and an inter-PC interlock contact M0 which is a trigger of an interlock between the PC1 and the PC2. There is.

Next to the in-step sequence B of the process 2, a transition T3 which is a condition judgment for shifting from the process 2 to the process 3 and an inter-PC interlock contact M10 which is a trigger of the interlock between the PC2 and the PC3. There is.

The shared information collection table 41 is stored in the memory 32 in order for the program editing apparatus 30 to grasp the device which becomes the interlock condition of the program of another PC among the PCs connected to the network. Yes, as shown in FIG. 16, a PC unique name column 41a for registering information identifying the PC to which the device belongs,
The inter-PC interlock contact row 41b for registering the name of the device (contact) that is the interlock condition is configured.

The shared information collection table 41 is automatically created from the PC unique name assigned to each step and the inter-PC interlock contact described in one sequential execution type program as a transition condition. The program editing device 30 executes the PC sequence creation processing on the data performed by referring to the shared information collection table 41 to create the sequential execution type program described above as shown in FIG.
The sequence program is divided and converted into a sequence program for each PC as shown in (c).

FIG. 17A shows a PC1 sequence program, in which a normally closed contact (dummy contact) M9036 is automatically added to the in-step sequence A, and finally a PC1 interlock condition sequence (trigger program) corresponding to the transition T2. 200 is automatically added.
The PC1 interlock condition sequence 200 has an internal contact M 0 and a shared information contact B 0 .

FIG. 17B shows a sequence program of the PC 2, in which the shared information contact B is added to the in-step sequence B.
0 is automatically added, and finally, the PC2 interlock condition sequence (trigger program) 201 corresponding to the transition T3 is automatically added. The PC2 interlock condition sequence 201 has an internal contact M10 and a shared information contact B10.

FIG. 17C shows a sequence program of the PC 3, in which the shared information contact B is added to the in-step sequence C.
10 is automatically added.

The program editing device 30 secures an area in the memory 32 for editing each sequence program and provides a storage area for each sequence.

FIG. 18 shows a data sharing information memory map developed in the memory 61 (see FIG. 23) of the communication unit 60 ₁ of the master PC. The shared information is information (shared information contact) shared between PCs connected by a network, and this memory map is a PC1 occupied area (PC1 public information portion) for storing information disclosed by the first PC. ) P for storing the information disclosed by the second PC
It consists of an occupied area for public information of each PC, such as a C2 occupied area (PC2 public information part).

Shared information memory map definition table 42
19 is stored in the memory 32 in order for the program editing apparatus 30 to grasp the device range of the information shared between the PCs connected to the network.
As shown in FIG. 3, it has a PC unique name column 42a and a device range column 42b. The shared information memory map definition table 42 is automatically generated by automatically detecting the device range of the shared information contact for each programmable controller from the data content of the shared information collection table 41.

Based on the data in the shared information memory map definition table 42, the program editing device 30 includes each of the data shared information memory units 62 held by a communication unit equivalent to the communication unit 60 ₁ of the parent PC shown in the conventional example. The public information parts 62 ₁ , 62 _2, ... Of the PC are automatically mapped as shown in FIG. In other words, the data sharing information memory map is automatically generated.

Next, the operation will be described. In the second embodiment as well, it is assumed that there is a network system configuration as shown in FIG. First, in accordance with a user input, the program editing apparatus 30 sets arbitrary unique names to all PCs existing on the network. Next, the user uses the program editing device 30 to create a sequential execution type program for a plurality of PCs as shown in FIG.

Next, the shared information collection table creating process is executed in the program editing device 30. The shared information collection table creation process is performed according to the flowchart shown in FIG. First, the determination position of the program content is moved to the initial step at the beginning of the sequential execution type program (step S400). Next, it is checked whether the step corresponding to the determination position is an end step (step S401). When you first come to this step, it is not always an end step.

If it is not the end step, the PC unique name added to the label of the corresponding step (for example,
"PC1") is stored in the blank line of the PC unique name column 41a of the shared information collection table 41 (step S402).

Next, the process proceeds to the transition (step S403), and the device (for example, "M0") at the inter-PC interlock condition contact in the transition in the transition is set to the inter-PC interlock contact sequence in the shared information collection table 41. The data is stored in the corresponding line of 41b (the same line as the storage line of "PC1") (step S404).

Next, the process proceeds to the next step of the sequential execution type program for a plurality of PCs, and the process returns to step S401.
When the end step is reached, the data storage rows of the shared information collection table 41 are replaced in ascending order of the device numbers of the inter-PC interlock contact row (step S405).

The shared information collection table 41 as shown in FIG. 16 is automatically created by the above processing. When the automatic creation of the shared information collection table 41 is completed, the process proceeds to the shared information memory map definition table creation processing (step S406).

The shared information memory map definition table creating process is performed according to the flowchart shown in FIG. First, the determination position is moved to the top row of the shared information collection table 41 (step S450). Next, it is checked whether data is set in the row of the shared information collection table 41 (step S451).

If the data is set, it is checked whether the unique name of the current row of the PC unique name column of the shared information collection table 41 is different from the unique name of the previous row (step S452). If the unique names are different, a blank line PC in the shared information memory map definition table 42 in which the PC unique name is not set yet
The PC unique name is set in the unique name data field, and the same number as the inter-PC interlock contact number in the shared information collection table 41 is set as the shared information contact number at the beginning of the device range data field in that row (step S453). After this, the process moves to the next line of the shared information collection table 41 and returns to step S451.

If it is determined in step S452 that the unique name of the current row of the PC unique name column 41a of the shared information collection table 41 is the same as the unique name of the previous row, the device range data field of the current row is set to the end. As the shared information contact number, the same number as the inter-PC interlock contact number in the shared information collection table 41 is set (step S45).
4). After this, the process moves to the next line of the shared information collection table 41 and returns to step S451.

When the check of the shared information collection table 41 is completed for all the PC unique names, the required range information of the shared devices for the PCs connected to this network is stored as in the case of the first embodiment. The shared information memory map definition table 42 is automatically created.

Each PC sequence creation process is performed according to the flow chart shown in FIG. First, the execution position is moved to the initial step which is the first step of the sequential execution type program for plural PCs (step S50).
0). Next, it is checked whether the step is an end step (step S501).

If it is not the end step, the PC unique name attached to the step label of the program is checked (step S502). It is checked whether the PC unique name does not match the PC unique name of each PC sequence storage area allocated in the memory 32 (step S50).
3). If the new PC unique name has no PC sequence storage area yet, each new PC sequence storage area is created in the memory 32 (step S504).

Next, the sequence existing in the step of the sequential execution type program for a plurality of PCs is copied to the corresponding PC sequence area (step S505). Next, by looking at the PC proper name attached to the label of the next step of the program (step S506), it is checked whether it is the same PC proper name as the previous step (step S50).
7). If they are the same, the process returns to step S505 to copy to the PC sequence area.

On the other hand, when the PC proper names are different, the transition inter-PC interlock condition contact (M0, M10) in the transition before the step.
Etc.) on the input side contact of each PC sequence storage area,
An interlock condition sequence in which shared information contacts (B0, B10, etc.) having the same number as the device of the interlock condition contact between PCs in transition are placed on the output side is added to the end of the sequence program in each PC sequence storage area (step S508). .

Next, the inter-PC interlock condition contact (B0, B10, etc.) in the transition of the transition before the step of the program is added to the position of the interlock condition sequence (step S509). When this is completed, the process returns to step S501, and steps S502 to S509 are repeatedly executed until the end step is reached, whereby the sequence for each PC as shown in FIGS. The program is created automatically.

[0101]

As can be understood from the above description, according to the programmable controller program editing apparatus of the present invention, the programmable controller proper name for registering the information specifying the programmable controller to which the device belongs and the interlock condition. Based on the data of the shared information collection table in which the device name is registered, the trigger program including the external contact and the shared information contact is automatically added to the sequence program of the corresponding programmable controller, and the programmable controller of the interlocking target between PCs Since the shared information contact of the trigger program is automatically added to the sequence program as an interlock contact between PCs, it can be used in a programmable controller that works with multiple programmable controllers. Over Ken scan program to improve the creation efficiency, yet it is possible to create certainty in the exact sequence program without setting error.

According to the program editing device for a programmable controller of the following invention, all between the inter-PC interlock contact instruction and the inter-PC interlock end instruction set in the original sequence program of the programmable controller of the inter-PC interlock target are performed. Since the program creation process that automatically adds the inter-PC interlock contact to the above program is performed, by setting the inter-PC interlock contact instruction and inter-PC interlock end instruction in the original sequence program, the inter-PC interlock contact is set within the predetermined range of the sequence program. Interlock contacts can be added automatically, improving the efficiency of creating sequence programs used by programmable controllers that work with multiple programmable controllers, and accurate sequence programming without setting errors. It is possible to reliably create the beam.

According to the programmable controller program editing apparatus of the next invention, the inter-PC interlock contact instruction includes the programmable controller specific name of the inter-PC interlock and the device description part which is the interlock condition. Since the shared information collection table is automatically created from the contact instruction data, the shared information collection table does not need to be created, and the shared information collection table is created correctly, ensuring an accurate sequence program without setting errors. Can be created.

According to the program edit device of the programmable controller of the next invention, the interlock contact between PCs is described as the transition condition in the program edit device for creating the sequence program used in the programmable controller in which a plurality of programmable controllers cooperate. Based on the data registered in the shared information collection table, a trigger program including an external contact and shared information contact is automatically added to the step of one sequential execution type program, and the sequence program in the corresponding step as a transition condition. The shared information contact of the trigger program is added to the PC as an interlock contact between PCs, and one sequential execution type program is separated for each step and the sequence program of each programmable controller is separated. Since automatically converted to grams, improved creation efficiency of the sequence program for use in a programmable controller in which a plurality of programmable controllers to cooperate, moreover it is possible to create reliable accurate sequence program without setting error.

In the programmable controller program editing device according to the next invention, the unique name of the programmable controller provided for each step and the inter-PC interlock contact described in one sequential execution type program as a transition condition are provided. Since the shared information collection table is automatically created from the above, it does not take time and effort to create the shared information collection table, and the shared information collection table is created accurately, and an accurate sequence program without setting mistakes can be surely created. You can

According to the programmable controller program editing apparatus of the next invention, the device range of the shared information contact of each programmable controller is automatically detected from the data content of the shared information collection table, and the shared information contact of each programmable controller is detected. Since the shared information memory definition table indicating the device range is automatically created, it is possible to automatically generate the common information memory map that needs to be specified as the common information of individual PCs connected to the network. Creation efficiency is improved.

[Brief description of drawings]

FIG. 1 is a block diagram showing a hardware configuration of a program editing device of a programmable controller according to the present invention.

FIG. 2 is a configuration diagram of a PC unique name management table used in the programmable controller program editing device according to the present invention.

FIG. 3 is a ladder circuit diagram showing an example of an original sequence program created by a program editing device for a programmable controller according to the present invention.

FIG. 4 is a configuration diagram of a shared information collection table used in the program editing device of the programmable controller according to the present invention.

FIG. 5 is a ladder circuit diagram of a trigger program.

FIG. 6 is a ladder circuit diagram of a sequence program after conversion by the program editing device of the programmable controller according to the present invention.

FIG. 7 is a configuration diagram of a shared information memory map definition table created by the program editing device of the programmable controller according to the present invention.

FIG. 8 is a configuration diagram of a shared information memory map.

FIG. 9 is a flowchart showing a general processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 10 is a flowchart showing a shared information collection table creation processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 11 is a flowchart showing a shared information memory map definition table creation processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 12 is a flowchart showing an interlock section program substituting process flow in the programmable controller program editing apparatus according to the present invention.

FIG. 13 is a flowchart showing a trigger program substitution processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 14 is a block diagram showing a hardware configuration of a program editing device for a programmable controller according to the present invention.

FIG. 15 is a ladder circuit diagram showing an example of a sequential execution type program for a plurality of PCs created by the program editing device of the programmable controller according to the present invention.

FIG. 16 is a configuration diagram of a shared information collection table used in the program editing device of the programmable controller according to the present invention.

17 (a) to (c) are each PC by the program editing device of the programmable controller according to the present invention.
FIG. 9 is a ladder circuit diagram showing a sequence program of each PC that is divided and created by a sequence program creation process.

FIG. 18 is a configuration diagram of a shared information memory map.

FIG. 19 is a configuration diagram of a shared information memory map definition table created by the program editing device of the programmable controller according to the present invention.

FIG. 20 is a flowchart showing a shared information collection table creation processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 21 is a flowchart showing a shared information memory map definition table creation processing flow in the program editing device of the programmable controller according to the present invention.

FIG. 22 is a flowchart showing each PC sequence program creation processing flow in the programmable controller program editing device according to the present invention.

FIG. 23 is a block diagram showing a general example of a PC link system that performs sequence control of mechanical equipment by a plurality of PCs that cooperate with each other.

FIG. 24 is a ladder circuit diagram showing a sequence program (trigger program) of the PC 50 ₁ .

FIG. 25 is a ladder circuit diagram showing a sequence program of an interlock part of the PC 50 ₂ .

[Explanation of symbols]

10 program editing device, 11 processing unit, 12 memory, 13 auxiliary storage device control unit, 14 key input control unit, 15 screen control unit, 16 auxiliary storage device, 17 keyboard, 18 CRT, 20 PC unique name management table, 21 shared Information collection table, 22 shared information memory map definition table, 30 program editing device, 3
1 processing unit, 32 memory, 33 auxiliary storage device control unit, 34 key input control unit, 35 screen control unit, 36
Auxiliary storage device, 37 keyboard, 38 CRT, 41
Shared information collection table, 42 Shared information memory map definition table, 50 ₁ to 50 _n PC main body, 51 _{1 to} 51
_n memory, 52 _{1 to} 52 _n PC internal information memory unit, 53 ₁
~ 53 _n public information part, 60 ₁ ~ 60 _n communication unit,
61 memory, 62 data sharing information memory unit, 120
PC interlock contact instruction, 123 PC interlock end instruction, 200, 201 interlock condition sequence (trigger program).

─────────────────────────────────────────────────── ─── Continuation of the front page (72) Shigeru Yamada Inventor Shigeki Yamada 1071-Kami 5-5-chome, Sone-machi, Kita-ku, Nagoya-shi, Aichi Mitsubishi Electric Mechatronics Software Co., Ltd. (72) Inventor Kazuki Ochiai Kita-ku, Nagoya-shi, Aichi 5107-107, Kami-chome, Sone-machi, Higashi-Odai Mitsubishi Electric Mechatronics Software Co., Ltd. (72) Inventor Shuji Oguchi 5-107, Kami-chome, Higashi-Osone Mechatronics Software Co., Ltd., Kita-ku, Nagoya-shi, Aichi (56) References JP-A-6-95713 (JP, A) JP-A-6-43913 (JP, A) (58) Fields investigated (Int. Cl. ⁷ , DB name) G05B 19/05

Claims (4)

(57) [Claims] 1. A plurality of programmable controllers program editing apparatus of the programmable controller to create respectively a sequence program used in the programmable controller in a system that works, the programmable controller connected to the network
The programmable controller is registered with the unique name of
Famous management table, device name and programmer for interlock condition
The correspondence with the unique name of the bull controller is registered.
Yes Information collection table and programmable controller interlock between PC
Describes the device name that is a famous and interlock condition
PC interlock contact instruction and interlock
PC interlock end instruction that describes the end of the lock
Programmable controller for interlocking between PCs including
From the sequencer program of the trawler,
-Extract the lock contact instruction and extract the interlock between PCs
Programmable controller described in the contact instruction
Unique name and interlock condition device name and before
Register the programmable controller unique name management table.
Create the shared information collection table using the recorded data
Based on the shared information collection table creation means and the registered data of the shared information collection table,
Programmable controller sequence program
Trigger program including input contact and shared information contact
Automatically adding trigger program adding means and programmable controller for PC interlock
Interface between PCs set in the original sequencer program
-Between lock contact instruction and PC interlock end instruction
Share the trigger program to all programs in
Information contacts are automatically attached as interlock contacts between PCs
An interlock unit adding means for adding the programmable controller.
Program editing device. 2. A programmable controller unique name,
Correspondence with the device range of the shared information contact is registered
The shared information memory map definition table and the shared information based on the registration data of the shared information collection table
Co-create a specific information memory map definition tables automatically
Existence information memory map definition table creation means and the registration data of the shared information memory map definition table
Based on the communication of the predetermined master unit programmable controller
Each program in the data sharing information memory part of the unit
Mapping the public information part of the ramable controller
The public information mapping means for performing further , and the professional of Claim 1 characterized by the above-mentioned.
Program editing device for programmable controllers. 3. For a plurality of programmable controllers
Sequential execution type program that continuously describes the sequence program
Flop to create a sequence program used in the programmable controller in a system that operates in a plurality of programmable controllers in cooperation with Gram
In the programmable controller program editing device of the programmable controller, the name of the device that becomes the interlock condition and the programmer
The correspondence with the unique name of the bull controller is registered.
Existence information collection table and each programmable code in the sequential execution type program
Described for each sequence program for controllers,
Unique name and transition of the programmable controller
The interlock contact between PCs as a condition is extracted.
The name of the device that will be the interlock condition
And the unique name of the programmable controller
The shared information collection table to be registered is automatically created.
Based on the existing information collection table creation method and the registered data of the shared information collection table,
Sequence program for programmable controller
Trigger program including input contact and shared information contact
Is automatically added and applicable programmable
The trigger in the sequence program for the controller
Shared information contact of program is interlock contact between PC
As an interlock creating means, and each of the one sequential execution type programs can be programmed.
Separate each program into a sequence program for the controller.
The programmable controller sequence program
And a program separating means for dynamically converting the programmable controller.
Program editing device . 4. A programmable controller unique name,
Correspondence with the device range of the shared information contact is registered
The shared information memory map definition table and the shared information based on the registration data of the shared information collection table
A shared information memory map definition table is automatically created.
Existence information memory map definition table creation means and the registration data of the shared information memory map definition table
Based on the communication of the predetermined master unit programmable controller
Each program in the data sharing information memory part of the unit
Mapping the public information part of the ramable controller
The public information mapping means for performing further , and the professional of Claim 3 characterized by the above-mentioned.
Program editing device for programmable controllers.