JP2014228990A - Control program creation apparatus and control program creation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To optimize the configuration of a control program created in each of languages of a plurality of language types.SOLUTION: According to an embodiment, a control program creation apparatus comprises: a control program management unit that includes a compiler compiling a source file of a control program to convert the source file to an object file, and communication means transmitting the object file to a controller; and a database storing the source file and the object file and managing the source file and the object file according to key information set per control program. The database manages an object file constituting one program configuration unit by mixing the object file obtained by converting the source file created for a main routine in a first type language and the object file obtained by converting the source file for a sub routine in a second type language different from the first type language.

Description

  Embodiments described herein relate generally to a control program creation device and a control program creation method.

  A system programmer (user) provides a program for automatically operating a plant as an application program (hereinafter referred to as “control program”) of a plant control apparatus to a plant operator after creation, testing, and adjustment. The system programmer debugs the control program when adjusting the control program in order to control the plant safely.

  The control program is described using languages such as LD (ladder), FBD (function block diagram), SFC (sequential function chart), and ST (structured text) defined in IEC61131-3, for example. When debugging the control program, the operation of the control program is checked by replacing the control program unit or forcibly changing the contact (A contact, B contact, etc.) or variable value in the online state. At the time of this operation check, it is required that the control program creation device be presented in an easy-to-understand manner to the system programmer so as not to cause erroneous operations.

JP 2011-227823 A

In the control program creation device, the control program is divided into “PROGRAM” that is executed mainly and at least one “FUNCTION / FUNCTION BLOCK” that is called and executed from this “PROGRAM”. Each of “PROGRAM” and “FUNCTION / FUNCTION BLOCK” is loaded into the plant controller and executed as one program constituent unit.
“PROGRAM” and “FUNCTION / FUNCTION BLOCK” can be created using a graphic language such as LD / FBD / SFC or a text language such as ST.

  At present, the graphic language program and the text language program are separate program constituent units. For this reason, when a program created in a text language such as ST is called from a program created in a graphic language such as LD / FBD / SFC (“PROGRAM”), the text language program is called “FUNCTION / FUNCTION BLOCK”. Therefore, it is necessary to create the call source program and the call destination program as different program structural units.

  In addition, when a routine is divided into a main routine and a subroutine in one program configuration unit and a program is executed by calling the subroutine from the main routine, the main routine and the subroutine have the same graphic language or the same text language. It is necessary to create in.

  Therefore, for example, if you create a control program for "PROGRAM" to be executed in the main in a highly visible graphic language, and create a control program for "FUNCTION / FUNCTION BLOCK" in a text language that performs operations etc. in various places in the program, As the number of “FUNCTION / FUNCTION BLOCK” programs increases, the number of program constituent units increases. In this case, since the number of program structural units exceeds the allowable number of program structural units of the plant control device, it cannot be applied to the plant control device. Further, when there are a large number of “FUNCTION / FUNCTION BLOCK” control programs called from the main “PROGRAM” control program, it becomes difficult to perform unified management with the main “PROGRAM” control program.

  The present invention has been made in view of the above circumstances, and provides a control program creation device and a control program creation method capable of optimizing the configuration of a control program created in each of a plurality of types of languages. For the purpose.

  A control program creation device according to an embodiment is a control program creation device that writes an object file of a control program to a controller via a network, and includes a compiler that compiles a control program source file and converts it into an object file A control program management unit having a communication means for sending the object file to the controller, a database for storing the source file and the object file, and managing the source file and the object file by key information set for each control program; Is provided. The database includes an object file obtained by converting a source file created for a main routine in a first type language, and an object file obtained by converting a source file created for a subroutine in a second type language different from the first type. Are mixed and managed as an object file forming one program configuration unit.

The figure which shows schematically the example of 1 structure of the control program creation apparatus concerning embodiment. The figure which shows an example of the control program created using the graphic language prescribed | regulated by JISB3503 (or IEC61131-3). The figure which shows an example of the control program created using the text language prescribed | regulated by JISB3503 (or IEC61131-3). The figure which shows the structural example of the object file of the program structure unit in embodiment. The figure which shows roughly the example of 1 structure of the database of the control program creation apparatus which concerns on embodiment. The flowchart which shows an example of the operation | movement for editing the routine of a different language of the control program in embodiment. The flowchart which shows an example of the operation | movement for compiling the routine of the language from which the control program differs in embodiment. The figure which shows the structural example of the import / export file of the control program in embodiment. The flowchart which shows an example of the operation | movement for exporting the control program which has a routine of a different language in embodiment. The flowchart which shows an example of the operation | movement for importing the control program which has a routine of a different language in embodiment. 6 is a flowchart illustrating an example of an operation for printing a control program having a routine of a different language in the embodiment. The figure which shows the structural example of the object file of the conventional program structure unit.

Hereinafter, a control program creation device according to an embodiment will be described with reference to the drawings. FIG. 1 is a diagram schematically illustrating a configuration example of a control program creation device according to an embodiment.
The control program creation apparatus according to the present embodiment includes a computer 100 including a control program management unit 110, a database 150, an import / export unit 160, and a control program printing unit 170. In addition, the control program creation device includes a mouse 12 and a keyboard 14 as input devices of the computer 100 and a display device 16 as an output device of the computer 100. The computer 100 and the controller 200 of the plant control apparatus are connected to a network 300.

  The controller 200 of the plant control apparatus has an object memory 210 for storing an object file of a control program, and a standard processing unit 220 for writing, reading, and executing these objects. Further, the object memory 210 has a data memory 212 and a code memory 214.

  The standard processing unit 220 is a program load server unit 222, a program execution processing unit 224 for executing a control program recorded in the object memory 210, and a process signal for giving a process signal from a plant to be controlled to the control program. And a process input / output processing unit 226.

  The program load server unit 222 arranges the object file of the control program sent from the computer 100 via the network 300 in the data memory 212 and the code memory 214 of the object memory 210.

The computer 100 includes a control program management unit 110 for a system programmer to create a control program, and a database 150 for storing the control program.
The control program management unit 110 includes a graphic language editing screen 111, a text language editing screen 112, a program compiler 113, and a program load client unit 114.

  The graphic language editing screen 111 is a screen for editing a graphic language control program. The text language editing screen 112 is a screen for editing a text language control program. The program compiler 113 performs a compile process for converting a control program source file into an object file. The program load client unit 114 is a communication unit that sends the object file converted from the source file by the program compiler 113 to the controller 200.

  The import / export unit 160 imports or exports a control program between other plant control apparatuses. The control program printing unit 170 performs control program printing processing.

  The program compiler 113 is a graphic language compiler 113a for converting a control program source file created in a graphic language into an object file, and a text for converting a control program source file created in a text language into an object file. A language compiler 113b.

  The database 150 includes a source file unit 152 for storing a control program source file and an object file unit 154 for storing a control program object file.

FIG. 2 shows an example of a control program created using a graphic language defined by JISB3503 (or IEC61131-3). The control program shown in FIG. 2 can be assembled on the screen of the display device 16 by combining diagrams corresponding to the program language. For example, each of C1 to C7 shown in FIG. 2 corresponds to an instruction word described in a graphic language defined by JISB3503 (or IEC61131-3).
FIG. 3 shows an example of a control program created using the ST language (text language) defined by JISB3503 (or IEC61131-3).

  Thus, the system programmer assembles a diagram corresponding to the graphic language, or creates a control program source file by text input. The system programmer compiles the source file with the program compiler 113 to create an object file.

Next, a function for creating each routine of the control program using a different language will be described.
FIG. 12 is a diagram showing a configuration example of an object file in a conventional program configuration unit. As shown in FIG. 12, an object file of “PROGRAM” that constitutes one program unit is composed of a main routine object and a subroutine object. Conventionally, a language used for creating an object in the main routine is used. And the language used to create the object of at least one subroutine. In the case of using a program created in a text language in such a “PROGRAM” configuration, as shown in FIG. 12, a “FUNCTION / FUNCTION BLOCK” program having a different program configuration unit from this “PROGRAM” The main routine.

FIG. 4 is a diagram illustrating a configuration example of an object file in a program configuration unit in the embodiment.
In the example shown in FIG. 4, an object obtained by converting a source file created in a graphic language for a main routine of a control program, an object obtained by converting a source file created in a graphic language for subroutines A and B, and a subroutine Y For this purpose, objects obtained by converting source files created in a text language are mixed and combined as an object file forming one program configuration unit.

  With such a configuration, a main routine and a subroutine constituting one program configuration unit can be configured using different languages. In the example shown in FIG. 4, when the main routine is created in the graphic language and the program created in the text language is used in the “PROGRAM” configuration, the subroutine in the text language is included in the same “PROGRAM”. May be used. That is, compared with the example shown in FIG. 12, the number of “FUNCTION / FUNCTION BLOCK” programs forming different program structural units can be reduced. That is, since it is not necessary to increase the number of program constituent units due to the difference in language, the number of control programs can be suppressed within the allowable number of program constituent units of the plant control apparatus.

Next, a function for calling (specifying) a routine of a control program created in a different language will be described.
The main routine is created by designating either a graphic language or a text language when a new control program is created.
A call from the main routine to the subroutine is performed by a subcall instruction. In the main routine, a subcall instruction dedicated to the graphic language or a subcall instruction dedicated to the text language is arranged at an arbitrary program position.

  In the present embodiment, a call to a subroutine corresponding to an object file obtained by converting a source file created in a graphic language uses a subcall instruction dedicated to the graphic language subroutine. In addition, a call to a subroutine corresponding to an object file obtained by converting a source file created in a text language uses a subcall instruction dedicated to the text language subroutine.

  For example, the sub-calls A and B dedicated to the graphic language subroutine are used for the call from the main routine shown in FIG. 4 to the subroutines A and B. For the call from the main routine shown in FIG. 4 to the subroutine Y, the subcall Y dedicated to the text language subroutine is used.

  FIG. 5 shows a configuration example of the database 150. A source file of the control program is recorded in the source file portion 152 of the database 150. The source file unit 152 includes control program information 152A, routine information 152B, a graphic language program source 152C, and a text language program source 152D.

  In the example shown in FIG. 6, the routine information 152B for one control program information 152A, the graphic language program source 152C, and the text language program source 152D are composed of a plurality of data. The routine information 152B is provided for each routine in one program configuration unit as shown in FIG. The routine information 152B, graphic language program source 152C, and text language program source 152D are managed in a hierarchical structure. The highest hierarchy is the control program information 152A, and one unique key information is assigned to one control program. The control program information 152A includes unique key information, a program name, and a program type. The key information is information combining numbers and characters, for example. The program type is, for example, “PROGRAM” or “FUNCTION / FUNCTION BLOCK” shown in FIG.

Routine information 152B that is one layer below control program information 152A is associated with control program information 152A by this key information.
The routine information 152B manages information on the main routine and the subroutine, and includes sub key information, routine name, language type (graphic language or text language), and reference key information for referring to key information of the control program information 152A. included. The sub key information of the routine information 152B is unique information given to each routine information 152B of the control program, for example.

  The graphic language program source 152C and the text language program source 152D, which are one level lower than the routine information 152B, are associated with the routine information 152B by subkey information. The subkey information of the program source 152C is unique information given to each instruction word of the control program, for example.

The graphic language program source 152C manages each instruction word in the graphic language and refers to the sub key information, the instruction word position information in the graphic language, the instruction word code in the graphic language, and the sub key information in the routine information 152B. Reference key information.
The text language program source 152D manages each program text, and includes subkey information, program text, and reference key information for referring to a subkey of the routine information 152B. The subkey information of the program source 152D is unique information given for each program text of the control program, for example.

In the present embodiment, the control program information A and routine information 152B are managed by associating lower layer reference key information having the same information as the upper layer key information.
In this embodiment, the routine information 152B, the graphic language program source 152C, and the text language program source 152D are managed by associating lower layer reference key information having the same information as the upper layer sub key information. As a result, the program source of each routine can be centrally managed regardless of the language type.

  The control program information 154A stored in the object file unit 154 manages each object and includes key information, a program name, and an object. The control program information 154A stored in the object file unit 154 and the control program information 152A stored in the source file unit 152 are managed by associating the same key information.

  By managing source files and object files using such a hierarchical structure, it is possible to centrally manage source files generated in different languages and object files converted from the source files.

  The operations of the computer 100 and the controller 200 will be described below. The system programmer creates a control program using the graphic language editing screen 111 or the text language editing screen 112 displayed on the display device 16. When the system programmer saves the control program, the control program is stored in the source file section 152 of the database 150, and the source file is compiled by the graphic language compiler 113a or the text language compiler 113b of the program compiler 113. Are stored in the object file portion 154 of the database 150.

  After creating, storing, and compiling the control program as described above, the system programmer writes the object file to the controller 200 via the network 300 and causes the control program to be executed.

When the object file is written to the controller 200, the computer 100 and the controller 200 read the object file from the object file unit 154 of the database 150 by the program load client unit 114, and the program load server unit of the controller 200 via the network 300. To 222. The program load server unit 222 receives the object file, arranges it on the data memory 212 and the code memory 214 of the object memory 210, and the program execution processing unit 224 executes this to execute the control program. .
In the control program creation device according to the present embodiment, the control program is written into the controller 200, and the operation check and the debug operation are performed.

Next, editing a subroutine in a different language in the control program will be described. FIG. 6 is a flowchart illustrating an example of an operation for editing a subroutine of a different language of the control program in the embodiment.
The program of each subroutine is edited on an editing screen different from the main routine. The control program management unit 110 of the computer 100 shown in FIG. 1 determines the language type of the subcall instruction corresponding to the subroutine to be edited in order to determine the language type used to create the source file corresponding to the subroutine to be edited. Determine (S1). The control program management unit 110 reads out the language type of the routine information corresponding to the subroutine to be edited from the source file unit 152, so that the language type used to create the source file corresponding to the subroutine to be edited is discriminated. Good.

  When the subcall instruction is a subcall instruction dedicated to the graphic language, for example, subcalls A and B shown in FIG. 4 (YES in S2), the control program management unit 110 activates the graphic language editing screen 111 (S3). . Further, when the subcall instruction is a subcall instruction dedicated to the text language, for example, subcall Y shown in FIG. 4 (NO in S2), the control program management unit 110 activates the text language editing screen 112 (S4).

  Each editing screen manages main routine information (program name, routine name, language type) of a subroutine call source, call position information of a subcall instruction, and own subroutine information (routine name, language type).

Next, a function of compiling program sources created using different languages and generating an object file as one program structural unit will be described. FIG. 7 is a flowchart illustrating an example of an operation for compiling a routine of a different language of the control program in the embodiment.
When the control program management unit 110 of the computer 100 shown in FIG. 1 is requested to compile the program from the graphic language editing screen 111 or the text language editing screen 112 of the main routine or subroutine (S11), the program compiler 113 The compilation process is transferred (S12). The program compiler 113 selects a routine to be compiled from the main routine and each subroutine (S13), and determines the language type of the control program corresponding to this routine (S14).

  If the program is a graphic language routine (YES in S15), the program compiler 113 calls the graphic language compiler 113a (S16). If the program is a text language routine (NO in S15), the program compiler 113 calls the text language compiler 113b (S17).

  After S16 or S17, the program compiler 113 returns to S13 if there is another routine whose language type is not determined (YES in S18). If there is no other routine whose language type has not been determined (NO in S18), the program compiler 113 executes the compilation processing of all routines at once, and the object of each routine generated by this compilation processing is executed. As shown in FIG. 4, they are combined as an object file constituting one program structural unit (S19).

Next, a function of importing / exporting a control program having a routine in a different language as a program structural unit with another computer for a plant control apparatus will be described.
FIG. 8 is a diagram illustrating a configuration example of an import / export file of a control program in the embodiment. One import file or one export file is assumed for each program configuration unit. The import file or export file consists of control program program information (program name, program type), routine information (number of routines, routine name, routine language type), and program source information (program source size, program source). Configure.
As shown in FIG. 8, the graphic language program source includes graphic language instruction word position information and instruction word codes. The text language program source is composed of a text language program text.

FIG. 9 is a flowchart illustrating an example of an operation for exporting a control program having routines of different languages in the embodiment.
The import / export unit 160 of the computer 100 shown in FIG. 1 acquires control program information, related routine information, and program source information from the source file unit 152 of the database 150 at the time of export (S21).

  The import / export unit 160 determines the program name and program type of the acquired control program (S22). The import / export unit 160 determines the number of routines of the acquired control program (S23). The import / export unit 160 determines the routine name and language type of each routine (S24).

  The import / export unit 160 determines the size of each program source (S25). The import / export unit 160 acquires source information of each program source (S26).

The import / export unit 160 generates an export file in which control program information, routine information, and program source information are arranged as shown in FIG. 8 based on the discrimination or acquisition result from S22 to S26 (S27). .
The import / export unit 160 outputs the generated export file to a computer for another plant control device (S28).

FIG. 10 is a flowchart illustrating an example of an operation for importing a control program having routines of different languages in the embodiment.
The import / export unit 160 inputs an import file from a computer for another plant control device (S31).

  The import / export unit 160 decomposes the control program information, routine information, and program source information of the input import file (S32). Specifically, the import / export unit 160 determines the program name, program type, and routine number of the control program information. Further, the import / export unit 160 determines the routine name and language type of the routine information. Further, the import / export unit 160 determines the instruction word position information, the instruction word code, and the program text of the input program source information.

  The import / export unit 160 adds the result key information, subkey information, and reference key information obtained by the decomposition, and stores them in the source file unit 152 of the database 150 (S33).

  As is clear from the above results, in this embodiment, program information, routine information, and program source information of a control program having routines of different language types can be imported or exported as one file with the system programmer. it can. Thereby, it is possible to centrally manage the import file or the export file of the control program comprising the main routine and a plurality of subroutines.

Next, a function for printing a control program having a routine in a different language as one program constituent unit will be described.
FIG. 11 is a flowchart illustrating an example of an operation for printing a control program having a routine of a different language in the embodiment.
The control program printing unit 170 of the computer 100 shown in FIG. 1 receives a control program printing operation, and from the source file unit 152 of the database 150, the control program information of the control program to be printed, related routine information, and the program Source information is acquired (S41).

The control program printing unit 170 selects one of the acquired control program routines as a routine to be printed (S42), and determines the language type of this routine (S43).
If the routine language type is graphic language (YES in S44), the control program printing unit 170 prints the graphic language program (S45).
If the language type of the routine is a text language (NO in S44), the control program printing unit 170 prints the graphic language program (S46).

If the printing of all routines has not been completed (NO in S47), the control program printing unit 170 returns to S42. If the printing of all routines has been completed (YES in S47), the control program printing unit 170 ends the series of processes.
Header information (program name, routine name, printing date, etc.) and footer information (page number, etc.) are printed on the print result of the program.

  As is clear from the above results, in this embodiment, a control program having a routine of a different language type can be printed by a single operation. As a result, even if the language types of the main routine and the plurality of subroutines are different, it is possible to centrally manage the printing results of the control program comprising these routines.

  According to the embodiment, it is possible to provide a control program creation device and a control program creation method that optimize the configuration of a control program created in each of a plurality of types of languages.

Note that the methods described in the above embodiments are, as programs that can be executed by a computer, magnetic disks (floppy (registered trademark) disks, hard disks, etc.), optical disks (CD-ROMs, DVDs, etc.), magneto-optical disks. (MO), stored in a storage medium such as a semiconductor memory, and distributed.
In addition, as long as the storage medium can store a program and can be read by a computer, the storage format may be any form.
In addition, an OS (operating system) running on a computer based on an instruction of a program installed in the computer from a storage medium, MW (middleware) such as database management software, network software, and the like realize the above-described embodiment. A part of each process may be executed.
Furthermore, the storage medium in each embodiment is not limited to a medium independent of a computer, but also includes a storage medium that downloads and stores or temporarily stores a program transmitted via a LAN, the Internet, or the like.
Further, the number of storage media is not limited to one, and the case where the processing in each of the above embodiments is executed from a plurality of media is also included in the storage media in the present invention, and the media configuration may be any configuration. The computer in each embodiment executes each process in each of the above embodiments based on a program stored in a storage medium, and a single device such as a personal computer or a plurality of devices are connected to a network. Any configuration of the system or the like may be used.
In addition, the computer in each embodiment is not limited to a personal computer, and includes an arithmetic processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions of the present invention by a program. Yes.
Although several embodiments of the invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 12 ... Mouse, 14 ... Keyboard, 16 ... Display apparatus, 100 ... Computer, 110 ... Control program edit part, 111 ... Graphic language edit screen, 112 ... Text language edit screen, 113 ... Program compiler, 113a ... Graphic language compiler, 113b ... text language compiler, 114 ... program load client part (communication part), 150 ... database, 152 ... source file part, 154 ... object file part, 160 ... import / export part, 170 ... control program printing part, 200 ... controller, 210 ... Object memory, 212 ... Data memory, 214 ... Code memory, 220 ... Standard processing unit, 222 ... Program load server unit, 224 ... Program execution processing unit, 226 ... Process input / output processing , 300 ... network.

Claims (8)

A control program creation device for writing an object file of a control program to a controller via a network,
A control program management unit having a compiler that compiles and converts the source file of the control program into an object file, and a communication unit that sends the object file to the controller;
A database for storing the source file and the object file, and managing the source file and the object file by key information set for each control program;
The database is
An object file obtained by converting a source file created for a main routine in a first type language, and an object file obtained by converting a source file created for a subroutine in a second type language different from the first type. A control program creation device characterized by being managed as an object file that is mixed and forms one program structural unit. The control program management unit
A call from the main routine to a subroutine corresponding to an object file converted from a source file created in the first type language is performed using a subcall instruction for the first type language, and the second type The call from the main routine to the subroutine corresponding to the object file obtained by converting the source file created in the language of the type is performed using the subcall instruction for the language of the second type. The control program creation device according to 1. The database is
Managing the control program information of the control program, routine information, the source file created in the first or second type in a hierarchical structure with the control program information as the highest and the source file as the lowest,
The control program information includes a program name and program type information,
The routine information includes a routine name and language type information used to create the source file,
The control program information and routine information are associated with the key information,
The control program creation device according to claim 1, wherein the routine information and the source file are associated with each other by subkey information set for each routine. When the source file corresponding to the subroutine to be edited is created in the language of the first type, the editing screen corresponding to the language of the first type is activated, and the source file corresponding to the subroutine to be edited 2. The control program creation device according to claim 1, wherein an editing screen corresponding to the language of the second type is activated when the language is created in the language of the second type. The compiler of the program management unit is:
Determine the language type for each routine of the control program, compile the source file of the control program according to the determined language and convert it into an object file,
2. The control program creation device according to claim 1, wherein the object file converted for each routine by the compiler is combined as an object file forming one program structural unit. 4. The control program creation device according to claim 3, further comprising means for importing or exporting control program information, routine information, and source files managed by the database as a single file. 2. The control program creation device according to claim 1, further comprising means for determining a language type for each routine of the control program and printing the control program according to the determined language. A control program creation method applied to a control program creation device for writing an object file of a control program to a controller via a network,
The control program management unit compiles and converts the control program source file into an object file,
The control program management unit sends the object file to the controller;
The database stores the source file and the object file, and manages the source file and the object file by key information set for each control program,
An object file obtained by converting a source file created for the main routine in the first type language by the database and a source file created for the subroutine in a second type language different from the first type A control program creation method characterized by managing files as object files that form a single program component unit.

Images