WO2016013111A1

WO2016013111A1 - Engineering tool

Info

Publication number: WO2016013111A1
Application number: PCT/JP2014/069693
Authority: WO
Inventors: 真弘平田; 博子永松; 康人光安; 周志田中
Original assignee: 三菱電機株式会社
Priority date: 2014-07-25
Filing date: 2014-07-25
Publication date: 2016-01-28
Also published as: JPWO2016013111A1; JP5980422B2

Abstract

An engineering tool is provided with: a project management unit (11) that manages a project including a plurality of items of project data used in a plurality of programmable logic controllers; a read/write data management unit (12) that manages combination data indicating a combination of each of the plurality of programmable logic controllers and the project data used by each of the plurality of programmable logic controllers; and a communication unit (15) that transmits the project data used by each of the plurality of programmable logic controllers to each of the plurality of programmable logic controllers on the basis of the combination data.

Description

Engineering tools

The present invention relates to an engineering tool for managing project data used in a programmable logic controller (hereinafter referred to as PLC).

In the FA (Factory Automation) field, a PLC that controls various devices communicates with an engineering tool realized by executing an engineering tool program on a computer, and is set, maintained, and managed from the engineering tool.

In a conventional engineering tool, parameters such as parameters set in the PLC and referred to by the PLC, and data written in the PLC and executed by the PLC are collectively managed in a management unit called a project. Data including parameters managed in a project is called project data.

In the conventional engineering tool, when setting, maintaining and managing the PLC, the PLC and the project on the engineering tool have a one-to-one relationship from the viewpoint of easy understanding and use of the operator. It was.

However, recently, data used in PLCs is required to ensure quality and reduce costs by standardization, structuring and reuse. Therefore, it is required to support a plurality of devices, that is, a plurality of PLCs, by combining a plurality of componentized data.

Conventionally, when the data created for the first device is reused for another second device similar to the first device, the first project created for the first device is copied. Two projects were used for the second device. For this reason, when a program used in common in the first device and the second device is modified, a duplicate work of modifying both the first project and the second project occurs, resulting in a reduction in work efficiency. It was.

In addition, when one project has a plurality of programs, it is necessary for an operator to manually select a program to be written into a device, that is, a PLC, or a program to be verified. For this reason, the operator may forget to select a program or make a mistake.

The following

Patent Documents

1 and 2 are known as related technologies.

JP 2007-94898 A JP 2012-141722 A

The technology described in Patent Document 1 assigns one project to one PLC and assigns a subproject to each of a plurality of CPU modules mounted on one PLC. However, Patent Document 1 does not describe a method for managing a plurality of PLCs. Japanese Patent Application Laid-Open No. 2004-228561 describes that the signal definition is shared among the subprojects, but does not describe that the program is shared and modularized between the subprojects.

The technology described in Patent Document 2 assigns a project to each of a plurality of CPU units mounted on one PLC, and performs parameter setting that is consistent between the projects. That is, a plurality of devices mounted on one PLC. The parameter setting is made consistent between the CPU units. However, Patent Document 2 does not describe a method for managing a plurality of PLCs. Further, Patent Document 2 describes that parameter settings that are consistent between projects are performed, but does not describe that a program is shared and modularized between projects.

The present invention has been made in view of the above, and an object thereof is to provide an engineering tool that can easily manage a plurality of PLCs.

In order to solve the above-described problems and achieve the object, an engineering tool according to the present invention is an engineering tool that communicates with a plurality of programmable logic controllers, and a plurality of project data used in the plurality of programmable logic controllers. A project management unit that manages a project having a read / write data management unit that manages combination data representing a combination of each of the plurality of programmable logic controllers and project data used in each of the plurality of programmable logic controllers; Based on the combination data, project data used in each of the plurality of programmable logic controllers is converted into each of the plurality of programmable logic controllers. And a communication unit for transmitting.

According to the present invention, by managing a plurality of project data used in a plurality of PLCs in one project, standardization, structuring, componentization, and reuse of project data are facilitated. Thereby, the efficiency of the operator's project data creation can be improved.

FIG. 1 is a diagram illustrating an FA system using an engineering tool according to a first embodiment of the present invention. FIG. 2 is a flowchart showing a project creation process of the engineering tool according to the first embodiment of the present invention. FIG. 3 is a diagram showing an example of a recording screen of the engineering tool according to the first embodiment of the present invention. FIG. 4 is a flowchart showing the project data writing process to the PLC of the engineering tool according to the first embodiment of the present invention. FIG. 5 is a diagram illustrating an example of a writing screen of the engineering tool according to the first embodiment of the present invention. FIG. 6 is a flowchart showing collation processing between the data held in the PLC and the project data of the engineering tool according to the first embodiment of the present invention. FIG. 7 is a diagram illustrating an example of a matching screen of the engineering tool according to the first embodiment of the present invention.

Hereinafter, an embodiment of an engineering tool according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited to these embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating an FA system using an engineering tool according to a first embodiment of the present invention. This FA system includes a personal computer 1, a first device 100, a second device 110, and a third device 120. The personal computer 1 and the first device 100, the second device 110, and the third device 120 can communicate with each other by wire or wirelessly.

The first device 100 is connected to the first PLC 101 and is controlled by the first PLC 101. The second device 110 is connected to the second PLC 111 and is controlled by the second PLC 111. The third device 120 is connected to the third PLC 121 and is controlled by the third PLC 121.

In the first embodiment, the first device 100 is a device that fills a 2 liter container with a beverage, the second device 110 is a device that fills a 1.5 liter container with a beverage, and the third device. Although 120 is an apparatus which fills a 500 milliliter container with a drink, this invention is not limited to this.

The personal computer 1 has an engineering tool 10. The engineering tool 10 is realized by a CPU (Central Processing Unit) in the personal computer 1 executing an engineering tool program recorded on a recording medium in the personal computer 1. Examples of the recording medium include ROM (Read Only Memory), RAM (Random Access Memory), flash memory (registered trademark), SSD (Solid State Drive), and HDD (Hard Disk Drive).

The engineering tool 10 includes a project management unit 11, a read / write data management unit 12, a data write unit 13, a data collation unit 14, and a communication unit 15.

The project management unit 11 manages the project 20. Here, the project 20 is set in the first PLC 101, the second PLC 111, and the third PLC 121, and is set in the program group 30, the first PLC 101, the second PLC 111, and the third PLC 121 that are executed by the first PLC 101, the second PLC 111, and the third PLC 121. A parameter group 40 referred to by the second PLC 111 and the third PLC 121, a device memory group 50 that is set in the first PLC 101, the second PLC 111, and the third PLC 121 and defines a work memory area of the first PLC 101, the second PLC 111, and the third PLC 121, and the first PLC 101 Connection between a plurality of terminals and a plurality of sensors and actuators of the first device 100, a plurality of terminals of the second PLC 111 and a plurality of sensors and actuators of the second device 110 And connection information group 60 which describes the connection of a plurality of sensors and actuators data between the connection and the 3PLC121 plurality of terminals of the third device 120 is a management unit for managing. The project may be a data structure recorded on a recording medium of the personal computer 1. Further, the project management unit 11 can manage a plurality of projects.

The program group 30 includes a “MAIN1” file 31, a “MAIN2” file 32, and a “MAIN3” file 33.

The parameter group 40 includes a “PARAM1” file 41, a “PARAM2” file 42, and a “PARAM3” file 43.

The device memory group 50 includes a “DEVMEM1” file 51, a “DEVMEM2” file 52, and a “DEVMEM3” file 53.

The connection information group 60 includes first device connection information 61 describing connections between a plurality of terminals of the first PLC 101 and a plurality of sensors and actuators of the first device 100, a plurality of terminals of the second PLC 111, and a plurality of terminals of the second device 110. Second device connection information 62 describing connections between sensors and actuators, and third device connection information 63 describing connections between a plurality of terminals of the third PLC 121 and a plurality of sensors and actuators of the third device 120 are included.

“MAIN1” file 31, “MAIN2” file 32, “MAIN3” file 33, “PARAM1” file 41, “PARAM2” file 42, “PARAM3” file 43, “DEVMEM1” file 51, “DEVMEM2” managed by the project 20 ”File 52,“ DEVMEM 3 ”file 53, first device connection information 61, second device connection information 62, and third device connection information 63 are project data.

In the first embodiment, the operations of the first device 100, the second device 110, and the third device 120 are common in the basic point that the beverage is sequentially filled in the container, while the size of the container and the type of the beverage It differs in that it depends on the interval at which the beverage is packed. Therefore, the file read / written to / from the first PLC 101 from the engineering tool 10, the file read / written from the engineering tool 10 to the second PLC 111, and the file read / written from the engineering tool 10 to the third PLC 121 are partly common, but the other part Is different. The project management unit 11 collectively manages the files read / written to / from the first PLC 101, the second PLC 111, and the third PLC 121 with one project 20.

The read / write data management unit 12 defines data 70 for the first device that defines a file to be read from and written to the first PLC 101 that controls the first device 100, and a file that is read from and written to the second PLC 111 that controls the second device 110. It manages the specified second device data 80 and the third device data 90 that defines the files to be read from and written to the third PLC 121 that controls the third device 120. The first device data 70, the second device data 80, and the third device data 90 correspond to the combination data of the present invention.

In the first embodiment, it is assumed that the first PLC 101 executes the programs “MAIN1” file 31 and “MAIN2” file 32. In the first PLC 101, the parameters of the “PARAM1” file 41 are referred to. Further, the first PLC 101 uses the work memory area defined in the “DEVMEM1” file 51. The connection between the plurality of terminals of the first PLC 101 and the plurality of sensors and actuators of the first device 100 is described in the first device connection information 61.

Therefore, the data 70 for the first apparatus includes “MAIN1” specifying information 71 that is information specifying the “MAIN1” file 31, “MAIN2” specifying information 72 that is information specifying the “MAIN2” file 32, and “PARAM1” file. “PARAM1” specifying information 73, which is information specifying 41, “DEVMEM1” specifying information 74, which is information specifying the “DEVMEM1” file 51, and first device connection information specifying, which is information specifying the first device connection information 61 Information 75 is included.

The engineering tool 10 reads / writes the file specified by the specific information in the first device data 70 to / from the first PLC 101 based on the information in the first device data 70.

Note that each specifying information is not a program file, a parameter file, a device memory file, and a connection information file itself, but information that uniquely specifies them. The specific information is exemplified by a file name, a file identifier, and a symbolic link to the file.

In the first embodiment, it is assumed that the program of the “MAIN1” file 31 is executed in the second PLC 111. In the second PLC 111, the parameters of the “PARAM2” file 42 are referred to. In the second PLC 111, it is assumed that the work memory area defined in the “DEVMEM2” file 52 is used. The connection between the plurality of terminals of the second PLC 111 and the plurality of sensors and actuators of the second device 110 is described in the second device connection information 62.

Therefore, the data 80 for the second device includes “MAIN1” specifying information 81 that is information specifying the “MAIN1” file 31, “PARAM2” specifying information 82 that is information specifying the “PARAM2” file 42, and “DEVMEM2” file. 52 includes “DEVMEM2” specifying information 83 that is information for specifying 52 and second device connection information specifying information 84 that is information for specifying second device connection information 62.

The engineering tool 10 reads / writes the file specified by the specific information in the second device data 80 to / from the second PLC 111 based on the information in the second device data 80.

In the first embodiment, it is assumed that the third PLC 121 executes the programs “MAIN2” file 32 and “MAIN3” file 33. In the third PLC 121, the parameters of the “PARAM3” file 43 are referred to. In the third PLC 121, a work memory area defined in the “DEVMEM3” file 53 is used. The connection between the plurality of terminals of the third PLC 121 and the plurality of sensors and actuators of the third device 120 is described in the third device connection information 63.

Therefore, the data 90 for the third apparatus includes “MAIN2” specifying information 91 that is information specifying the “MAIN2” file 32, “MAIN3” specifying information 92 that is information specifying the “MAIN3” file 33, and “PARAM3” file. “PARAM3” specifying information 93 which is information specifying 43, “DEVMEM3” specifying information 94 which is information specifying “DEVMEM3” file 53, and third device connection information specifying which is information specifying third device connection information 63 Information 95 is included.

The engineering tool 10 reads / writes the file specified by the specific information in the third device data 90 to / from the third PLC 121 based on the information of the third device data 90.

The communication unit 15 reads / writes the file specified by the specific information in the first device data 70 to / from the first PLC 101, reads / writes the file specified by the specific information in the second device data 80 to / from the second PLC 111, and The file specified by the specific information in the data 90 for the three devices is read from and written to the third PLC 121.

The data writing unit 13 writes the file specified by the specific information in the first device data 70 to the first PLC 101, writes the file specified by the specific information in the second device data 80 to the second PLC 111, and When writing the file specified by the specific information in the data 90 for the third device to the third PLC 121, the communication unit 15 is controlled.

When the data collating unit 14 collates the data in the first PLC 101 and the file specified by the specific information in the first device data 70, the data collating unit 14 uses the data in the second PLC 111 and the specific information in the second device data 80. The communication unit 15 is controlled when collating the specified file and when collating the data in the third PLC 121 and the file specified by the specific information in the data 90 for the third device.

Each identification information is not a program file, a parameter file, a device memory file, and a connection information file itself, but is information that uniquely identifies a program file, a parameter file, a device memory file, and a connection information file. There is an effect. For example, the MAIN1 file 31 is executed by the first PLC 101 and also by the second PLC 111. Here, it is assumed that the program in the MAIN1 file 31 needs to be corrected. In this case, the operator only needs to correct the MAIN1 file 31. The MAIN1 specifying information 71 in the first device data 70 and the MAIN1 specifying information 81 in the second device data 80 are information for specifying the MAIN1 file 31, not the program file itself. Therefore, if the worker corrects only the MAIN1 file 31 and executes the writing process to the first PLC 101 and the writing process to the second PLC 111 as will be described later, the corrected MAIN1 file 31 is transferred to the first PLC 101 and the second PLC 111. Is done. Therefore, it is possible to improve the efficiency of the worker's file correction work and reduce errors in the file correction work.

FIG. 2 is a flowchart showing a project creation process of the engineering tool according to the first embodiment of the present invention. First, in step S100, the project management unit 11 of the engineering tool 10 creates a project in the recording medium of the personal computer 1 in response to input from the operator.

Next, in step S102, the project management unit 11 generates project data, that is, a program file, a parameter file, a device memory file, and a connection information file in response to input from the worker, and records them in the project.

Next, in step S104, the project management unit 11 receives the input from the worker and records the list data of the device and the project data. In the first embodiment, the operator identifies an item that identifies the first device 100, the second device 110, and the third device 120 (for example, a “2 liter container” that means a device that fills a 2 liter container with a beverage). Character string, "1.5 liter container" meaning a device for filling beverages in a 1.5 liter container, "500 milliliter container" character string meaning a device for filling beverages in a 500 milliliter container) Input to the project management unit 11. In addition, the worker identifies items for identifying each file (for example, a character string of “common line” indicating a program executed in common in each device, and a parameter for filling a beverage in a 2 liter container “ The character string “PARAM2000” (character string “DEVMEM2000”, which means a device memory for filling beverages in a 2 liter container) is input to the project management unit 11.

Next, in step S106, the read / write data management unit 12 of the engineering tool 10 receives the input from the operator and records the combination data of the device and the project data used in the device. More specifically, the read / write data management unit 12 displays a combination data recording screen based on the list data input in step S104, and receives input from the operator.

FIG. 3 is a diagram showing an example of a recording screen of the engineering tool according to the first embodiment of the present invention. In an area 210 extending in the horizontal direction at the top of the recording screen 200 in the figure, items 211, 212, 213, and 214 for identifying the device are displayed. The item 211 has a character string “2l container” that identifies the device that fills the 2 liter container with the beverage, that is, the first device 100. Item 212 has a string of “1.5 liter container” that identifies the device that fills the 1.5 liter container with the beverage or second device 110. Item 213 has the string “500 ml container” identifying the device that fills the 500 milliliter container with the beverage, ie, the third device 120. Item 214 has the string “350 ml container” identifying the device that fills the 350 ml container with beverage.

Further,

items

221, 222,... That identify program files are displayed in an area 220 extending in the vertical direction in the left part of the drawing of the recording screen 200. The item 221 has a character string of “common line” that identifies a program file that is executed in common in each apparatus. Item 222 has a character string “PROG2000” that identifies a program file that is executed by the device that fills the 2 liter container with a beverage.

In addition, an item 2301,... For identifying a parameter file is displayed in a region 230 extending in the vertical direction below the region 220 of the recording screen 200. The item 231 has a character string “PARAM2000” that identifies a parameter file that is referred to by a device that fills a 2-liter container with a beverage.

Further, in the area 240 extending vertically below the area 230 of the recording screen 200, items 241 for identifying the device memory file are displayed. Item 241 has the string “DEVMEM2000” identifying the device memory file that defines the work memory area of the device that fills the 2 liter container with beverage.

Also, the direction from the items 211, 212, 213, and 214 on the recording screen 200 to the lower side in the figure, and the

items

221, 222,..., 231,. Check boxes are displayed in a matrix at intersections of directions.

In FIG. 3, the connection information is not displayed on the recording screen 200 due to space limitations, but may be displayed in the same manner as the program, parameter, and device memory.

Here, a case where an operator inputs a combination of a device that fills a 2-liter container with a beverage, that is, the first device 100, and project data used in the first device 100 will be described.

Since the device identified by the item 211 that is the character string “2l container”, that is, the first device 100 is a device that fills the 2-liter container with the beverage, it is identified by the item 221 that is the character string “common line”. And the file program identified by the item 222 which is the character string “PROG2000” are executed.

Therefore, the operator inputs a check into a check box 251 displayed at the intersection of the direction from the item 211 to the lower side in the figure and the direction from the item 221 to the right side in the figure. Similarly, the operator inputs a check into a check box 252 displayed at the intersection of the direction from the item 211 toward the lower side in the figure and the direction from the item 222 toward the right side in the figure.

In addition, since the device identified by the item 211 that is the character string “2l container”, that is, the first device 100 is a device that fills the 2-liter container with the beverage, it is identified by the item 231 that is the character string “PARAM2000”. Refers to the parameter of the file to be processed.

Therefore, the operator inputs a check into a check box 253 displayed at the intersection of the direction from the item 211 to the lower side in the figure and the direction from the item 231 to the right side in the figure.

Further, since the device identified by the item 211 that is the character string “2l container”, that is, the first device 100 is a device that fills the 2-liter container with the beverage, it is identified by the item 241 that is the character string “DEVMEM2000”. The work memory area specified for the file to be used is used.

Therefore, the worker inputs a check into a check box 254 displayed at the intersection of the direction from the item 211 to the lower side in the figure and the direction from the item 241 to the right side in the figure.

Next, the worker clicks the button 260 having the character string “execute”. In response to this, the read / write data management unit 12 in the engineering tool 10 is identified by the item 222, which specifies the file identified by the item 221 based on the check in the

check boxes

251, 252, 253 and 254. Creating and recording data 70 for the first device on the recording medium of the personal computer 1 including information specifying the file to be identified, information identifying the file identified by the item 231 and information identifying the file identified by the item 241 .

The operator clicks a button 261 having a character string “cancel” when canceling the check input on the recording screen 200. In this case, the read / write data management unit 12 in the engineering tool 10 discards the check input on the recording screen 200 and does not create the first device data 70.

FIG. 4 is a flowchart showing the project data writing process to the PLC of the engineering tool according to the first embodiment of the present invention. First, in step S200, the data writing unit 13 of the engineering tool 10 acquires the device and project data list data created in step S104 and the combination data of the device and project data created in step S106. .

Next, in step S202, the data writing unit 13 displays a writing screen and displays a list of devices and project data.

FIG. 5 is a diagram showing an example of the writing screen of the engineering tool according to the first embodiment of the present invention. Items 3101, 312, 313, and 314 for identifying devices are displayed in an area 310 extending in the horizontal direction at the top of the writing screen 300 in the drawing. The item 311 has a character string “2l container” for identifying a device that fills a 2 liter container with a beverage, that is, the first device 100. Item 312 has the string “1.5 l container” that identifies the device that fills the 1.5 liter container with the beverage, ie, the second device 110. Item 313 has the string “500 ml container” identifying the device that fills the 500 milliliter container with the beverage, ie, the third device 120. Item 314 has a “350 ml container” string that identifies the device that fills the 350 ml container with beverage.

Here, a case where the operator writes the project data into the first PLC 101 of the first device 100, that is, the device that fills the 2 liter container with the beverage will be described.

A check box 315 for selecting a device for filling a beverage in a 2 liter container, that is, the first device 100, is displayed on the left side of the item 311. A check box 316 for selecting a device for filling a 1.5 liter container with a beverage, that is, the second device 110, is displayed on the left side of the item 312. On the left side of the item 313, a check box 317 for selecting a device for filling a beverage in a 500 milliliter container, that is, the third device 120, is displayed. A check box 318 for selecting that a device for filling a 350 ml container with a beverage is to be written is displayed to the left of the item 314. Here, the worker inputs a check into the check box 315. However, in addition to the check box 315, the worker may input a check into the

check box

316, 317, or 318.

Further,

items

321, 322,... That identify program files are displayed in an area 320 that extends in the vertical direction on the left side of the writing screen 300 in the drawing. The item 321 includes a character string of “common line” that identifies a program file that is executed in common in each apparatus. The item 322 has a character string “PROG2000” that identifies a program file to be executed by the apparatus for filling a 2 liter container with a beverage.

Further, in the area 330 extending vertically below the area 320 of the writing screen 300, items 331,... For identifying the parameter file are displayed. The item 331 has a character string “PARAM2000” that identifies a parameter file that is referred to by a device that fills a 2-liter container with a beverage.

In the area 340 extending vertically below the area 330 on the writing screen 300, items 341,... For identifying a device memory file are displayed. Item 341 has the string “DEVMEM2000” identifying the device memory file that defines the work memory area of the device that fills the 2 liter container with beverage.

Further, the direction from the

items

311, 312, 313 and 314 of the writing screen 300 to the lower side in the figure, and the

items

321, 322,..., 331,. Check boxes are displayed in a matrix at intersections of directions.

Here, since no check is input in the

check boxes

316, 317, and 318, the direction from the items 312, 313, and 314 toward the lower side in the figure and the

items

321, 322,..., 331,. A plurality of check boxes 355 located at the intersections between 341,... And the direction toward the right side in the drawing are displayed in a thin state so that a check cannot be input.

In FIG. 5, the connection information is not displayed on the writing screen 300 due to space limitations, but may be displayed in the same manner as the program, parameter, and device memory.

In step S106 of the project creation process described above (see FIG. 2), the device identified by the item 311, that is, the first device 100 is identified by the file identified by the item 321, the file identified by the item 322, and identified by the item 331. The combination data indicating that the file to be used and the file identified by the item 341 are used are recorded on the recording medium of the personal computer 1.

Therefore, the data writing unit 13 checks, based on the combination data, as an initial value that is displayed at the intersection of the direction from the item 311 to the lower side in the figure and the direction from the item 321 to the right side in the figure. A check is displayed in the box 351, and the file identified by the item 321 is selected. Similarly, the data writing unit 13 checks the check box 352 displayed at the intersection of the direction from the item 311 to the lower side in the figure and the direction from the item 322 to the right side in the figure as an initial value. And the file identified by the item 322 is selected.

In addition, as an initial value, the data writing unit 13 checks the check box 353 displayed at the intersection of the direction from the item 311 to the lower side in the figure and the direction from the item 331 to the right side in the figure. A file that is displayed and identified by the item 331 is selected.

In addition, as an initial value, the data writing unit 13 checks the check box 354 displayed at the intersection of the direction from the item 311 to the lower side in the figure and the direction from the item 341 to the right side in the figure. A file that is displayed and identified by the item 341 is selected.

Note that the plurality of check boxes 355 are displayed in a thin state so that the check cannot be input, but the direction from the items 312, 313, and 314 toward the lower side in the figure as an initial value based on the combination data. And the check box displayed at the intersection of the direction from the

item

321, 322,... Thereby, the worker can visually recognize a plurality of project data used in the apparatus identified by the items 312, 313 and 314.

Referring to FIG. 4 again, in step S204, the data writing unit 13 accepts selection of project data used by the writing target device, that is, the first device 100, on the writing screen 300.

Referring again to FIG. 5, when increasing or decreasing the file to be written to the device identified by the item 311, that is, the first device 100 on the writing screen 300, the worker positions the item 311 in the downward direction in the figure. Add or remove checks from the check boxes.

In the writing screen 300, as an initial value, a check is displayed based on the combination data, and the project data to be written to the PLC of the writing destination device is selected. For this reason, it is considered that the operator need not add or delete the check unless there is a particular change in the apparatus or program.

Referring to FIG. 4 again, in step S206, the data writing unit 13 executes the writing of the selected project data to the PLC of the designated device when the designation of the device and the execution instruction of the writing are input.

Referring again to FIG. 5, when the operator clicks the button 360 having the character string “execute” on the writing screen 300, the data writing unit 13 is based on the check in the

check boxes

351, 352, 353, and 354. The file identified by the item 321, the file identified by the item 322, the file identified by the item 331, and the file identified by the item 341 are read from the project 20, and the first device 100 of the first device 100 is read via the communication unit 15. Write to the first PLC 101.

Note that the operator clicks a button 361 having a character string “cancel” when not writing to the first PLC 101. In this case, the data writing unit 13 does not execute writing to the first PLC 101.

As described above, since the engineering tool 10 can select the project data to be written in the PLC of the writing destination device on the writing screen 300, the project data used in the PLC of the writing destination device can be easily and It is possible to reliably write to the PLC of the writing destination device. As a result, the work efficiency of the operator can be improved, and mistakes in writing project data can be reduced.

In addition, the engineering tool 10 assumes that the project data to be written to the PLC of the writing destination apparatus is selected as the initial value on the writing screen 300 based on the combination data. For this reason, it is considered that the operator need not add or delete the check unless there is a particular change in the apparatus or program. As a result, the work efficiency of the operator can be improved, and mistakes in writing project data can be reduced.

FIG. 6 is a flowchart showing a collation process between the data held in the PLC and the project data of the engineering tool according to the first embodiment of the present invention. First, in step S300, the data verification unit 14 of the engineering tool 10 acquires the device and project data list data created in step S104 and the combination data of the device and project data created in step S106. .

Next, in step S302, the data collation unit 14 displays a collation screen and displays a list of devices and project data.

FIG. 7 is a diagram showing an example of the verification screen of the engineering tool according to the first embodiment of the present invention.

Items

410, 412, 413, and 414 for identifying the device are displayed in an area 410 extending in the horizontal direction in the upper part of the verification screen 400 in the drawing. The item 411 includes a character string “2l container” that identifies the device that fills the 2 liter container with the beverage, that is, the first device 100. Item 412 has a string of “1.5 liter container” that identifies the device that fills the 1.5 liter container with beverage, or second device 110. Item 413 has a string of “500 ml container” that identifies the device that fills the 500 milliliter container with the beverage, ie, the third device 120. Item 414 has the string “350 ml container” identifying the device that fills the 350 ml container with beverage.

Here, a case where an operator collates data held in the first PLC 101 of the first device 100 with the device that fills the 2 liter container with beverage, that is, the project data in the project 20 will be described.

A check box 415 for selecting that a device for filling a beverage in a 2 liter container, that is, the first device 100, is displayed on the left side of the item 411 is displayed. On the left side of the item 412, a check box 416 for selecting a device for filling a 1.5 liter container with a beverage, that is, the second device 110, is displayed. On the left side of the item 413, a check box 417 for selecting a device for filling a beverage in a 500 ml container, that is, the third device 120, is displayed. On the left side of the item 414, there is displayed a check box 418 for selecting that a device for filling a beverage in a 350 ml container is to be checked. Here, the worker inputs a check into the check box 415. However, in addition to the check box 415, the operator may input a check into the

check box

416, 417, or 418.

Further,

items

421, 422,... For identifying program files are displayed in an area 420 extending in the vertical direction on the left side of the verification screen 400 in the drawing. The item 421 has a character string of “common line” that identifies a program file that is executed in common in each apparatus. Item 422 has a string of “PROG2000” that identifies the program file that is executed on the device that fills the 2 liter container with the beverage.

In addition, an area 430 extending in the vertical direction under the area 420 of the verification screen 400 displays items 431,... For identifying a parameter file. The item 431 has a character string “PARAM2000” that identifies a parameter file that is referred to by a device that fills a 2-liter container with a beverage.

Further, an area 440 extending in the vertical direction below the area 430 of the verification screen 400 displays items 441 for identifying the device memory file. Item 441 has the string “DEVMEM2000” identifying the device memory file that defines the work memory area of the device that fills the 2 liter container with beverage.

Also, the direction from the

items

411, 412, 413, and 414 on the verification screen 400 to the lower side in the figure, and the

items

421, 422,..., 431,. Check boxes are displayed in a matrix at intersections of directions.

Here, since no check is input in the

check boxes

416, 417, and 418, the direction from the

items

412, 413, and 414 to the lower side in the figure, and the

items

421, 422, ..., 431, ... A plurality of check boxes 455 located at the intersections of 441,..., And the direction toward the right side in the figure are displayed in a thin state, and the check cannot be input.

In FIG. 7, the connection information is not displayed on the collation screen 400 due to space limitations, but may be displayed in the same manner as the program, parameter, and device memory.

In step S106 of the project creation process described above (see FIG. 2), the device identified by the item 411, that is, the first device 100 is identified by the file identified by the item 421, the file identified by the item 422, and identified by the item 431. The combination data indicating that the file to be used and the file identified by the item 441 are used are recorded on the recording medium of the personal computer 1.

Therefore, based on the combination data, the data collation unit 14 checks the initial values displayed at the intersections of the direction from the item 411 to the lower side in the figure and the direction from the item 421 to the right side in the figure. A check is displayed in the box 451, and the file identified by the item 421 is selected. Similarly, the data collation unit 14 checks the check box 452 displayed at the intersection of the direction from the item 411 to the lower side in the figure and the direction from the item 422 to the right side in the figure as an initial value. And the file identified by the item 422 is selected.

In addition, the data collation unit 14 checks the check box 453 displayed at the intersection of the direction from the item 411 toward the lower side in the figure and the direction from the item 431 to the right side in the figure as an initial value. A file that is displayed and identified by the item 431 is selected.

In addition, as a default value, the data collation unit 14 checks the check box 454 displayed at the intersection of the direction from the item 411 to the lower side in the figure and the direction from the item 441 to the right side in the figure. A file that is displayed and identified by the item 441 is selected.

The plurality of check boxes 455 are displayed in a thin state so that a check cannot be input. However, based on the combination data, as an initial value, the direction from the

items

412, 413, and 414 to the lower side in the figure. And the check box displayed at the intersection of the

items

421, 422,... Thereby, the worker can visually recognize a plurality of project data used in the apparatus identified by the

items

412, 413 and 414.

Referring again to FIG. 6, in step S <b> 304, the data collation unit 14 accepts selection of collation target project data held in the collation target device, that is, the first PLC 101 of the first device 100 on the collation screen 400.

Referring to FIG. 7 again, when the operator increases or decreases the verification target device identified by the item 411 on the verification screen 400, that is, the verification target file held by the first PLC 101 of the first device 100, A check is added to or deleted from a check box located in the direction from the item 411 toward the lower side in the figure.

In the verification screen 400, a check is displayed as an initial value based on the combination data, and the verification target project data held in the PLC of the verification target device is selected. For this reason, it is considered that the operator need not add or delete the check unless there is a particular change in the apparatus or program.

Referring to FIG. 6 again, in step S306, the data collating unit 14 reads the project data to be collated from the PLC of the designated collation target device when an instruction to specify the device and execution of collation are input. To do.

Referring again to FIG. 7, when the operator clicks the button 460 having the character string “execute” on the collation screen 400, the data collation unit 14 is based on the check in the

check boxes

451, 452, 453, and 454. , The file identified by the item 421, the file identified by the item 422, the file identified by the item 431, and the file identified by the item 441 via the communication unit 15, the device to be verified, that is, the first device 100. Read from the first PLC 101.

Next, in step S308, the data matching unit 14 is identified by the file identified by the item 421, the file identified by the item 422, and the item 431 based on the checks in the

check boxes

451, 452, 453, and 454. And the file identified by the item 441 are read from the project 20. Then, the data collating unit 14 collates the collation target file read from the collation target device, that is, the first PLC 101 of the first device 100, with the file read from the project 20. If the collation target file read from the first PLC 101 of the first device 100 matches the file read from the project 20 as a result of the collation, the data collation unit 14 displays a match. If the verification target file read from the first PLC 101 of the first device 100 and the file read from the project 20 do not match, a message indicating that they do not match is displayed.

Note that the worker clicks the button 461 having a character string “cancel” when the collation with the first PLC 101 is not performed. In this case, the data collation unit 14 does not read and collate files from the first PLC 101.

As described above, the engineering tool 10 can select the project data held in the PLC of the verification target device on the verification screen 400, so the project data held in the PLC of the verification target device. And the project data in the project 20 can be easily and reliably collated. As a result, it is possible to improve the work efficiency of the operator and reduce project data collation errors.

Further, the engineering tool 10 assumes that the verification target project data held in the PLC of the verification target device is selected as the initial value on the verification screen 400 based on the combination data. For this reason, it is considered that the operator need not add or delete the check unless there is a particular change in the apparatus or program. As a result, it is possible to improve the work efficiency of the operator and reduce project data collation errors.

In the first embodiment, each of a plurality of project data managed by the project 20, that is, a program, a parameter, a device memory, and connection information is a file. However, the present invention is not limited to this. For example, the project data may be described directly in the project 20 and the entire project 20 may be a single file. In this case, each of the plurality of project data is a part of one file.

As described above, the engineering tool 10 manages a plurality of project data used in a plurality of PLCs, that is, the first PLC 101, the second PLC 111, and the third PLC 121 in one project 20, thereby standardizing and structuring the project data. Componentization and reuse are easy, and horizontal development to all PLCs using the modified project data is facilitated by modifying only one project data. As a result, the efficiency of the operator's project data creation can be improved, and mistakes in file correction work can be reduced.

Further, the engineering tool 10 manages the combination data of the device PLC and the project data used in the device PLC by the read / write data management unit 12 so that the project data is written to the PLC and the project data is collated. By simply specifying the target device, the writing target is selected on the writing screen 300, and the verification target project data is selected on the verification screen 400. As a result, the operator can easily select project data to be written and collated, and can reduce project data selection errors.

As described above, the engineering tool program according to the present invention is suitable for managing a plurality of PLCs.

1 personal computer, 10 engineering tool, 11 project management unit, 12 read / write data management unit, 13 data writing unit, 14 data verification unit, 15 communication unit, 20 project, 30 program group, 40 parameter group, 50 device memory group, 60 Connection information group, 70 1st device data, 80 2nd device data, 90 3rd device data, 100 1st device, 101 1st PLC, 110 2nd device, 111 2nd PLC, 120 3rd device, 121st 3PLC.

Claims

An engineering tool that communicates with multiple programmable logic controllers,
A project management unit for managing a project having a plurality of project data used in the plurality of programmable logic controllers;
A read / write data management unit that manages combination data representing a combination of project data used in each of the plurality of programmable logic controllers and each of the plurality of programmable logic controllers;
Based on the combination data, a communication unit that transmits project data used in each of the plurality of programmable logic controllers to each of the plurality of programmable logic controllers;
Engineering tool with.
When any programmable logic controller of the plurality of programmable logic controllers is designated by the user, the designated programmable logic is selected from the plurality of project data managed in the project based on the combination data. The data writing part which selects one or a plurality of project data used with a controller, and transmits the selected one or a plurality of project data to the designated programmable logic controller via the communication part further comprises: The engineering tool according to 1.
The data writing unit has a plurality of first items that respectively identify the plurality of programmable logic controllers along a first direction, and a plurality of second items that respectively identify the plurality of project data. From an item that displays a writing screen having a second direction that intersects a first direction and that identifies the designated programmable logic controller in the plurality of first items based on the combination data One or more used in the designated programmable logic controller at a plurality of intersections between a direction along the second direction and a direction along the first direction from the plurality of second items; The engineering tool according to claim 2, wherein a selection image indicating a selection state of a plurality of project data is displayed.
The data writing unit has a direction along the second direction from an item for identifying the designated programmable logic controller in the plurality of first items on the writing screen, and the plurality of second items. Receiving an input for changing a selection state of one or a plurality of project data used by the designated programmable logic controller at a plurality of intersections with the direction along the first direction from the item 3. The engineering tool according to 3.
When any programmable logic controller of the plurality of programmable logic controllers is designated by a user, one or more project data held in the designated programmable logic controller is communicated based on the combination data. One or a plurality of project data received via a section and one or a plurality of project data selected based on the combination data among the plurality of project data managed in the project The engineering tool according to claim 1, further comprising a data matching unit for matching.
The data collating unit has a plurality of first items that respectively identify the plurality of programmable logic controllers along a first direction, and a plurality of second items that respectively identify the plurality of project data. From the item which displays the collation screen which has along the 2nd direction which intersects the 1st direction, and identifies the specified programmable logic controller in the plurality of 1st items based on the combination data One held by the designated programmable logic controller at a plurality of intersections between the direction along the second direction and the direction along the first direction from the plurality of second items. The engineering tool according to claim 5, wherein a selection image indicating a selection state of a plurality of project data is displayed.
The data collating unit includes a direction along the second direction from an item for identifying the designated programmable logic controller in the plurality of first items on the collation screen, and the plurality of second items. Receiving an input for changing a selection state of one or a plurality of project data held by the designated programmable logic controller at a plurality of intersections with the direction along the first direction from the item Item 7. The engineering tool according to Item 6.