JP2008293058A - Programming device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a programming device which can create a sequence control program for increasing the reusability of an auxiliary program which can be used in common by a plurality of sequence control programs without requiring high level skill to a user. <P>SOLUTION: The programming device is equipped with an engineering tool part 11, an engineering database 12 and a programming part 13. The engineering tool part 11 is equipped with: a program editing part 111; an action insertion point detection part 112 for detecting a point into which an action can be inserted from a sequence control program; an aspect definition part 113 for modularizing the set of information where the action and the point into which the action can be inserted form a pair; and an action editing part 114 to be operated by a user when inserting the action. The engineering database 12 is equipped with a program table 121; an action insertion point table 122; and an aspect table 123. The programming part 13 is equipped with a program synthesis part 131 and a source buffer 132. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a program creation device, and more particularly to a sequence control program creation device that controls a device using a PLC (Programmable Logic Controller).

  Conventionally, as a method for creating a sequence control program, there is programming using a ladder language. Ladder language was devised to describe logic circuits with relays, and programs written in ladder language are equivalent to circuits using relays, so it is relatively easy to understand. For example, when a device fails Even if it is essentially a simple circuit that interrupts the process, the addition of an auxiliary function such as a time-out process for detecting a failure complicates the input work. .

  In order to improve the input operation of such a sequence control program, for example, Patent Document 1 discloses a technique for easily creating a complicated ladder program using a special table.

Japanese Patent Laid-Open No. 6-4111 (FIG. 2)

  When the sequence control program becomes complicated, there is a problem that not only the input operation becomes complicated, but also the reusability of the program is lowered. For example, if the auxiliary program used in one sequence control program is the application source, the other sequence control program is the application destination, and the auxiliary program of the application source is also applied to the application program If the user does not know the two program specifications of the original and application destinations, the application cannot be applied and a high level of skill is required of the user.

  The present invention has been made to solve the above-described problems, and it is possible to reproduce an auxiliary program that can be commonly used among a plurality of sequence control programs without requiring a high level of skill from the user. An object of the present invention is to provide a program creation device capable of creating a sequence control program with improved usability.

  According to a first aspect of the present invention, there is provided a program creation device that receives a sequence control program written in a ladder language and converts it into a predetermined programming language, and the converted sequence control program is a main program as a main flow. And a program editing unit that divides into unit instructions defined by contact load, contact reference and coil output, and the sequence control program after conversion is analyzed, and the main program is analyzed with respect to the main program. An action insertion point detection unit that detects an insertion point of an action defined as a program other than a program, and information obtained by pairing information of the detected insertion point and the action to be inserted therein into a module. In the aspect definition section defined as A program holding unit that holds a divided program divided into a main program and the unit instruction, an action insertion point holding unit that holds the insertion point detected by the action insertion point detection unit, and an aspect definition unit The defined aspect holding unit that holds the aspect, the main program held in the program holding unit, and the aspect held in the aspect holding unit are read and held in the action insertion point holding unit And a program synthesis unit that synthesizes the main program and the action based on the insertion point.

  According to the program creation device of the first aspect of the present invention, separately from the main program, an action defined as a program other than the main program is modularized as an application source program, which is applied to the application main program Since it is synthesized, the main program can be easily understood, and maintainability and reusability can be improved. In addition, since the aspect of the application source is also modularized, there is an effect that the reusability is improved.

<Description example of sequence control program in ladder language>
Prior to the description of the embodiment of the present invention, an example of a sequence control program using a ladder language will be described with reference to FIGS.

  FIG. 1 shows a sequence control program written in a ladder language, and FIG. 2 shows a timing chart at each contact.

  As shown in FIG. 1, the sequence control program is based on a row composed of relay contacts and actuators called coils, and contacts with the same numbers are connected to the coils. The program of FIG. 1 is composed of four lines 01 to 04, and is repeatedly executed in order from the top.

  The basic operation is that the input side contact on the left side of each row is turned on, and the output side coil on the right side of the row is turned on.

  In the sequence control program shown in FIG. 1, the main program is to interrupt the process by turning on the coil M1050 in the 04th row when the device fails, that is, when the contact M1020 in the 03th row is turned on. In order to perform a power recovery process for maintaining the current state and a time-out process for detecting a failure, the power recovery timer T335 (described as timer (1)) is started in line 01, and the power recovery in the coil M1254 in line 02 Timer T300 (described as timer (2)) is generated when the generation of an electric signal, the start of timer T300 for detecting a failure at line 03, and the power recovery signal at line 04 are OFF (contact M1254 is OFF). If the time is up, there is an auxiliary program that interrupts the processing.

  The operation of the sequence control program will be further described with reference to FIG. 2. When a power failure occurs and the contact M1250 is turned off as shown in FIG. 2A, a coil M1254 is shown as shown in FIG. However, when the power failure ends and the power is restored, the power recovery timer T335 is started. Therefore, the power recovery signal continues to be generated after the power recovery while the power recovery timer T335 is active.

In such a situation, as shown in part (c), when a device failure occurs during a power failure, the contact M1020 is turned on and the timer T300 is activated for a certain period. However, the period during which the power recovery signal is generated is not immediately interrupted even if the power recovers, but the period from when the power failure occurs until the power recovery signal is eliminated, that is, the OFF delay (D _off ) has elapsed. After that, the process will be interrupted.

<Embodiment>
Hereinafter, an embodiment of a program creation device according to the present invention will be described with reference to FIGS.

<A. Device configuration>
FIG. 3 is a block diagram showing the configuration of the sequence control program creation device 10 according to the embodiment of the present invention. The sequence control program creation device 10 is a device that creates a sequence control program that operates on the PLC 22. The created sequence control program is given to the compiler 21, converted into an executable format, and RS232C or Ethernet (registered). (Trademark) to the PLC 22 via the network and executed.

  As shown in FIG. 1, the sequence control program creation device 10 includes an engineering tool unit 11, an engineering database 12, and a program generation unit 13.

  The engineering tool unit 11 includes a program editing unit 111 used by a user to create a sequence control program, an action insertion point detection unit 112 that detects a point where an action can be inserted from the created sequence control program, an action, It includes an aspect definition unit 113 that modularizes a set of information paired with action insertable points (a modularized form is referred to as an aspect), and an action editing unit 114 that a user operates when inserting an action. Yes.

  The engineering database 12 includes a program table 121 that stores a sequence control program created by the program editing unit 111, an action insertion point table 122 that stores action insertion point data given from the action insertion point detection unit 112, And an aspect table 123 that stores the aspect defined by the aspect definition unit 113.

  The program generation unit 13 includes a source buffer 132 and a program synthesis unit 131 that reads a sequence control program from the engineering database 12 and stores the sequence control program in the source buffer 132 in units of action insertion points.

<B. Device operation>
<B-1. Overall operation>
With reference to FIG. 3, the overall operation of the sequence control program creation device 10 will be described using the flowchart shown in FIG.

  When the creation of the sequence control program is started, the user first creates a sequence control program using the program editing unit 111 of the engineering tool unit 11 (step ST101), and the sequence control program is stored in the program table 121 of the engineering database 12. Save (step ST102).

  At this time, the action insertion point detection unit 112 analyzes the sequence control program, detects a point where an action can be inserted (step ST103), and updates the action insertion point table 122 of the engineering database 12 (step ST104). Here, the point at which an action can be inserted includes a point before the start of execution of the main program (main program) and after the end of execution, and a point where contact loading, reference and output to the coil are performed.

  Next, the user operates the action editing unit 114 of the engineering tool unit 11 to describe an action to be inserted (step ST105), and selects an insertion point and an insertion method of the action (step ST106). The results are collected into aspects and stored in the aspect table 123 of the engineering database 12 (step ST107).

  Thereafter, the user uses the program synthesis unit 131 of the program generation unit 13 to select a sequence control program (main program) from the engineering database 12 and whether or not the program has an action insertion point specified in the aspect table 123. If there is a corresponding action insertion point, an action designated in the aspect is selected and inserted into the source buffer 132, thereby creating an executable source program (step ST108).

  Then, the compiler 21 is called according to the type of the created program, and the created source program is transferred to the program PLC 22 (step ST109), thereby completing the creation of the sequence control program.

<B-2. Operation of each part>
Next, the operation of each unit of the sequence control program creation device 10 will be described using the ladder program described with reference to FIG. 1 as an example.

  In the following, in order to simply describe a complicated data structure, the data structure is defined using XML (Extensible Markup Language), which is a recommendation of the World Wide Web Consortium (W3C). That is, the data structure is defined using the start tag (“<XXX>”) to the end tag (“</ XXX>”). If other data or data structure is included in the defined data, describe it nested in the start tag.

<B-2-1. Operation of the program editor>
In editing the sequence control program, first, the user uses the engineering tool unit 11 to input a program described in a graphical language such as a ladder diagram. In the following description, an operation when the sequence control program shown in FIG. 1 is input will be described.

  The input sequence control program is stored in a dedicated language on the memory, for example, LD (Ladder diagram), IL (Instruction List), ST (Structured Text) of IEC61131-3, which is a standard for programming languages of programmable controllers. Or POL (Problem Oriented Language).

  Here, FIG. 5 shows an example in which the sequence control program shown in FIG. 1 is described in POL. FIG. 5 shows a POL expression corresponding to each of lines 01 to 04 in FIG. 1. “$” and “;” are commands, and the values of the contacts described in the operands following these are loaded. . For example, “$” loads a logical negation value of the contact, and “−>” is a command indicating an output to the contact, and the loaded value is output to the coil described in the following operand. To do. In addition, “or” and “ani” are logical operators, which indicate that a logical operation is performed between a contact point described in an operand following this and a loaded value. “Or” is a logical sum, and “ani” is a logical product. In this example, for example, line 04 loads the value of timer T300 and takes the logical product of the value and the negative value of register M1254. It shows that the result is assigned to the contact M1050.

  FIG. 6 describes the main program of the sequence control program shown in FIG. 1, that is, the program for interrupting the processing by turning on the coil M1050 when the apparatus fails.

  Returning to the description of the editing operation in the program editing unit 111, the editing operation in the program editing unit 111 will be described below using the flowchart shown in FIG.

  When the editing operation is started, first, a program ID is input by the user (step ST601). The program ID is an identification number for uniquely identifying the source program created below, and is arbitrarily set by the user.

  Thereafter, the user inputs a sequence control program (FIG. 1) in a ladder language (step ST602). Note that the sequence control program input in the ladder language is converted into, for example, the POL language, and the following processing is performed based on the converted language.

  Next, in step ST603, it is determined whether or not a contact load instruction is included in one row of the input sequence control program. If a load instruction is included, in step ST604, a contact load instruction is included. Are divided into unit instructions, and the attribute type (explained later) is set to “Load” (step ST604).

  If a contact load command is not included, the process proceeds to step ST605, where it is determined whether or not an output command to the coil is included in one row of the input sequence control program. If an instruction is included, in step ST606, the output instruction to the coil is divided as a unit instruction, and the attribute type is set to “Store” (step ST606).

  If the output instruction to the coil is not included, the process proceeds to step ST607, where it is determined whether or not the reference instruction for the contact is included in one line of the input sequence control program. In step ST608, the contact reference instruction is divided as a unit instruction, and the attribute type is set to “Reference” (step ST608). If the contact reference command is not included, the process from step ST602 onward is repeated for the next line of the sequence control program. Here, the order of determining the attribute type is not limited to the order described above.

  After the attribute of the instruction is determined in steps ST604, ST606, and ST608, in step ST609, an instruction execution number is assigned to the instruction as the attribute index number (to be described later). The number is set to 1, and thereafter, every time a new instruction is identified, the instruction execution number is incremented by one, and the attribute index and the instruction assigned thereto are stored in the program editing unit 111.

  Next, in step ST610, it is checked whether or not the input for all the lines of the sequence control program has been completed. If the input has not been completed, the step is performed for the next line of the sequence control program. The processing from ST602 is repeated. On the other hand, when all the lines of the sequence control program have been input, the contents stored in the program editing unit 111 are stored in the program table 121 in the XML format shown in FIG.

  Here, an example of an XML sequence control program stored in the program table 121 will be described with reference to FIG.

  FIG. 8 is obtained by converting the main program shown in FIG. 6 into the XML format. In FIG. 8, “Program”, which is an XML tag, defines a program and has an attribute id for identifying the program. Here, it is shown that the program is id 001.

  An XML tag “Instruction” indicates a unit instruction included in the program. The attribute index is an ID indicating an instruction execution number starting from 1. The attribute type indicates the type of instruction. The types of instructions include “Load (load contact)”, “Store (output to coil)”, and “Reference (contact reference)” described with reference to FIG.

<B-2-2. Action of Action Insertion Point Detection Unit>
Next, the detection operation in the action insertion point detection unit 112 will be described.
The action insertion point detection unit 112 analyzes the XML-format sequence control program created by the program editing unit 111, detects an action insertion point, and creates an action insertion point table. The action insertion point corresponds to the load point of the contact, the output to the coil, and the reference point of the contact point before and after the program execution, and is generated from the information in the program table shown in FIG. An example of an action insertion point table is shown.

  In FIG. 9, “PointCuts” that is an XML tag indicates a list of action insertion points, “JoinPoints” that is an XML tag indicates each insertion point, an attribute pid indicating an ID of a related program, and an instruction execution order And an attribute index indicating how to insert the attribute index. The attribute advice includes “before” to be inserted before the instruction, “around” to replace the instruction itself, and “after” to insert after the instruction is executed.

  Here, with respect to the sequence control program shown in FIG. 1, a ladder diagram of the main program is shown in FIG. 10, and a ladder diagram of auxiliary processing summarized as a power recovery processing aspect is shown in FIG. As shown in FIG. 10, JP (1) is detected as “JoinPoints” before the execution of the main program, and the attribute advice of JP (1) becomes “before”. Further, JP (2) is detected as “JoinPoints” and the attribute advice of JP (2) is “around” in the portion where the contact M1020 for detecting a device failure is loaded. In the output part to the coil M1050 that executes the process interruption, JP (3) is detected as “JoinPoints”, and the attribute advice of JP (3) becomes “around”. Note that if “JoinPoints” is detected after the main program ends, JP (4) and the attribute advice of JP (4) are “after”, but the ladder diagram shown in FIG. There is no action corresponding to "", which is virtually shown.

  FIG. 11 shows a ladder diagram of actions inserted in each of “JoinPoints” JP (1) to JP (3). The box (A) of JP (2) corresponds to the device failure detection operation at the contact M1020, and the box (B) of JP (3) corresponds to the processing interruption operation at the coil M1050.

  Here, the detection operation in the action insertion point detection unit 112 will be described with reference to the flowchart shown in FIG.

  When the action insertion point detection unit 112 starts the detection operation, first, an instruction (XML tag instruction) list is read from the sequence control program in the XML format input from the program editing unit 111 (step ST801).

  Next, it is confirmed from the read instruction list whether or not there is an action to be inserted before the execution of the main program starts. When the action is detected, an insertion point (attribute) indicating the program execution start point is detected. An insertion point where advice becomes before is created (step ST802).

  Next, it is confirmed whether or not there is an action to be replaced from the read instruction list, and when the action is detected, an insertion point indicating the replacement (insertion point where the attribute advice is around) is created. (Step ST803).

  After creating the replacement insertion point, in step ST804, the instruction execution number as the attribute index number is incremented by one to prepare for reading the next line of the instruction list. Then, in step ST805, it is checked whether or not the input for all the lines of the instruction list is completed. If the input is not complete, the process following step ST803 is performed for the next line of the instruction list. Repeat the process. On the other hand, if input for all the lines of the instruction list has been completed, in step ST806, an insertion point indicating the end of execution of the main program (insertion point where the attribute advice is after) is created and detected. Exit.

  Through the above processing, an action insertion point table as shown in FIG. 9 is created and stored in the engineering database 12 as the action insertion point table 122.

<B-2-3. Operation of aspect definition section>
Next, the definition operation in the aspect definition unit 113 will be described.
Here, an aspect is a collection of information in which an action insertion point and an action inserted at the insertion point are paired. In this embodiment, in FIG. This is shown as the “power recovery aspect” to which the process is applied. In the description so far, an auxiliary program for the main program has been used as an action. However, programs other than the main program, including programs that perform exceptional processing, may be handled as actions, and the aspect constitutes them. Sometimes it is done.

  The definition operation in the aspect definition unit 113 will be described with reference to the flowchart shown in FIG.

  When the definition operation is started, the aspect definition unit 113 first reads out a sequence control program stored in the program table 121 and divided for each unit instruction as a source program (step ST1001).

  Next, the action insertion point table 122 is read from the engineering database 12 (step ST1002).

  Next, when the user selects a point at which an action is inserted from the action insertion point table 122 (step ST1003), the aspect definition unit 113 branches the process depending on the type of the attribute advice of the selected insertion point.

  Specifically, in step ST1004, it is determined whether or not the attribute advice of the selected insertion point is “before”. If “before”, the process proceeds to step ST1008, and the user sets “before”. The sequence control program to be inserted, that is, the action is described in the aspect table 123 of the engineering database 12.

  On the other hand, when it is determined in step ST1004 that the attribute advice of the selected insertion point is not “before”, it is determined in step ST1005 whether or not the attribute advice of the selected insertion point is “after”. If it is “after”, the process proceeds to step ST1008, and the user describes the sequence control program to be inserted as “after”, that is, the action in the aspect table 123 of the engineering database 12.

  On the other hand, if it is determined in step ST1005 that the attribute advice of the selected insertion point is not “after”, it is determined in step ST1006 that the attribute advice of the selected insertion point is “around”. Proceeding to ST1007, the user selects a box to be inserted. Here, the box is a portion that corresponds to a component (contact or coil) of the main program in the action in which the insertion point attribute advice is inserted “around” as a black box. In FIG. ), Which corresponds to the portion indicated as box (B).

  In this way, by handling a part corresponding to a component of the main program as a black box, and using a different main program as an application destination, it can be handled by putting the component of the application destination in the black box. This can increase the reusability of actions.

  After the selection of the box is completed, in step ST1008, the user describes the sequence control program to be inserted as “around”, that is, the action in the aspect table 123 of the engineering database 12.

  After the description of the action in the aspect table 123 is completed, it is confirmed whether or not the input (selection) of the action insertion point by the user has been completed (step ST1009). The process is repeated, and when the input is completed, the definition operation is terminated.

  As described above, by classifying the insertion point attribute advice into “before”, “after”, and “around”, any sequence control program can be supported.

Here, an example of the aspect table 123 will be described with reference to FIG.
As shown in FIG. 14, the aspect table describes an ID for identifying an action insertion point and an action to be inserted, and is stored in the order in which it is executed in the source program. In FIG. 14, the XML tag “Aspect” indicates the definition of the entire aspect, and the attribute name is named “recovery processing”.

  The XML tag “Advice” describes the action insertion point and the action to be inserted. In FIG. 14, in line 02, “JP (1)” in the action insertion point table shown in FIG. This indicates that an action starting from line 03 is executed at the insertion point. The action starting from line 03 corresponds to the action indicated by “JP (1)” in FIG.

  Since the insertion point JP (1) is found from the action insertion point table shown in FIG. 9 to be an insertion point before the execution of the program 001 (main program shown in FIG. 8), the user can edit the action editing unit 114. To describe the actions from line 03 to line 04. The described action is inserted into the source buffer 132 of the program generation unit 13 later.

  Further, line 06 indicates that the action of line 07 is executed at the insertion point of “JP (2)” in the action insertion point table shown in FIG. 9, and the notation {□} is shown in FIG. Box (A).

  The insertion point JP (2) is found from the action insertion point table shown in FIG. 9 to be the point of the instruction number 1 (unit instruction 1) of the program 001. Here, it can be seen from FIG. 8 that the unit instruction 1 is a load of the contact M1020, so the user operates the action editing unit 114 to replace the box part with M1020; and describes the action of M1020-> T300. . The described action is inserted into the source buffer 132 of the program generation unit 13 later.

  Similarly, line 09 indicates that 10 lines of action are executed at the insertion point of “JP (3)” in the action insertion point table shown in FIG. 11 is box (B).

  The insertion point JP (3) is found from the action insertion point table shown in FIG. 9 to be the point of the instruction number 2 (unit instruction 2) of the program 001. Here, it can be seen from FIG. 8 that the unit command 2 is an output to the coil of the contact point M1050, so that the user operates the action editing unit 114 to replace the box part with M1050; T300 ani M1254-> M1050 Describe the action. The described action is inserted into the source buffer 132 of the program generation unit 13 later.

  Here, a specific example of the action editing unit 114 is a program having a function corresponding to a text editor, and the action editing unit 114 also has a function of adding contents edited by the editor or the like to the aspect table 123. is doing.

<B-2-4. Operation of the program generator>
Next, the program generation operation in the program generation unit 13 will be described with reference to the flowchart showing the operation of the program synthesis unit 131 shown in FIG.

  When the synthesizing operation is started, the program synthesizing unit 131 first reads a main program, which is an application program, from the program table 121 of the engineering database 12 as a source program and displays a list thereof in step ST1101.

  Next, in step ST1102, the user selects a target program from the displayed programs. Here, a case where the main program shown in FIG. 8 is selected is taken as an example, and a program named 001 is selected.

  Next, in step ST1103, the program composition unit 131 reads the contents of the aspect table 123 of the engineering database 12 and displays a list of aspects.

  Next, in step ST1104, the user selects an aspect to be applied from the displayed aspects, that is, an application source program. Here, the case of selecting “recovery processing” shown in FIG. 14 is taken as an example, and the aspect “recovery processing” is selected.

  The program composition unit 131 reads the contents of the selected aspect from the aspect table 123 up to the first insertion point, and checks whether or not the XML tag “Advice” is included in the read (step ST1105). If “Advice” is not included, the process proceeds to step ST1108. If “Advice” is included, the “Advice” designates an action insertion point “before” indicating that the program is not yet executed. Whether or not there is is confirmed (step ST1106).

  If “before” is designated, the corresponding action (described by the user operating the action editing unit 114) is inserted into the source buffer 132 in step ST1104. If “before” is not designated, the process proceeds to step ST1108.

  In step ST1108, reading is performed up to the next insertion point of the selected aspect, and it is confirmed whether or not the XML tag “Advice” is included in the read (step ST1109). If “Advice” is not included, the process proceeds to step ST1113. If “Advice” is included, whether or not “Advice” specifies an action insertion point “around” indicating replacement is determined. This is confirmed (step ST1110).

  If “around” is designated, the box portion of the corresponding action is replaced with a contact or coil for which the user has designated replacement by operating the action editing unit 114 (step ST1111), and the result is stored in the source buffer. It inserts in 132 (step ST1112). If “around” is not designated, the process proceeds to step ST1113.

  In step ST1113, the next insertion point of the selected aspect is read, and it is confirmed whether or not the read action insertion point is the last insertion point. If the read action insertion point is not the last insertion point, the process from step ST1108 is repeated, and if it is the last insertion point, the process proceeds to step ST1114.

  In step ST1114, it is confirmed whether or not the XML tag “Advice” is included in the read. If “Advice” is not included, the program generation operation is terminated. If “Advice” is included, the “Advice” is an action insertion point “after” indicating that the program has been completed. Is checked (step ST1115).

  If “after” is designated, the corresponding action (described by the user operating the action editing unit 114) is inserted into the source buffer 132 in step ST1116. If “after” is not designated, the program generation operation is terminated.

<C. Modification>
In the above description, only “recovery processing” is illustrated as an aspect to be applied. However, when a plurality of aspects are stored in the aspect table, the program composition unit 131 applies them to the main program. Therefore, it is possible to handle a program that executes more complicated processing.

  In this case, since a plurality of aspects may specify the same action insertion point, it is necessary to specify the application order of the aspects. For example, when combining aspects that check that other devices are not operating before the execution of the program, interlock aspects, and aspects that check whether the previous program process is complete, etc. When sharing the same source program, the priority order is determined and applied.

<D. Effect>
As described above, in the sequence control program creation device 10, the auxiliary processing that can be used in common among a plurality of programs and an exceptional processing program called an aspect separately from the main program. Thus, the application source program is combined with the main program of the application destination to create a sequence control program that can be executed by the PLC. As described above, since the application source program is managed separately from the application target main program, the main program can be easily understood, and maintainability and reusability can be improved. In addition, since the aspect of the application source is also modularized, there is an effect that the reusability is improved.

It is a figure which shows the sequence control program described by the ladder language. It is a figure which shows the timing chart in each contact of a sequence control program. It is a block diagram which shows the structure of the sequence control program creation apparatus of embodiment which concerns on this invention. It is a flowchart explaining the whole operation | movement of the sequence control program creation apparatus of embodiment which concerns on this invention. It is the figure which described the sequence control program by POL. It is the figure which described the main program of the sequence control program by POL. It is a flowchart explaining operation | movement of a program edit part. It is a figure which shows the sequence control program of the XML format preserve | saved at a program table. It is a figure which shows an action insertion point table. It is a figure which shows the main program described by the ladder language. It is a figure which shows the power recovery process aspect described by the ladder language. It is a flowchart explaining operation | movement of an action insertion point detection part. It is a flowchart explaining operation | movement of an aspect definition part. It is a figure which shows an aspect display table. It is a flowchart explaining operation | movement of a program synthetic | combination part.

Claims (4)

A sequence control program written in a ladder language is input and converted into a predetermined programming language. The converted sequence control program is a main program as a main flow, contact loading, contact reference, and output to a coil. A program editing unit that divides the unit command defined by
An action insertion point detector that analyzes the sequence control program after conversion and detects an insertion point of an action defined as a program other than the main program for the main program;
An aspect definition unit that collectively defines information in which the detected insertion point and the action to be inserted therein are paired and defines it as an aspect;
In the program editing unit, a program holding unit that holds a divided program divided into the main program and the unit instruction;
An action insertion point holding unit for holding the insertion point detected by the action insertion point detection unit;
An aspect holding unit that holds the aspect defined by the aspect definition unit;
Reading the main program held in the program holding unit and the aspect held in the aspect holding unit, and based on the insertion point held in the action insertion point holding unit, the main program and the action And a program composition unit for synthesizing the program. The action insertion point detector is
Classification is made when the insertion point of the action is a point indicating the start of execution of the main program, a point indicating replacement of the main program, or a point indicating the end of execution of the main program. The program creation device according to claim 1, wherein the insertion point is detected. The aspect definition unit includes:
In the action inserted at the point indicating the replacement of the main program, a portion corresponding to a component of the main program is processed as a black box, and the program synthesis unit stores the part of the main program in the black box. The program creation device according to claim 2, wherein a component is inserted. The program synthesis unit
The program creation device according to claim 1, wherein when combining the main program and the action, a plurality of different types of aspects are applied to the main program by specifying an application order.

Images