CN107003649A - System design aided tool - Google Patents

Abstract

A system design support tool that generates a system label list having a plurality of system labels as identifiers, wherein a plurality of link devices set in a shared memory space are described in a control program While using the identifiers respectively, the system design assisting tool has: a system configuration diagram creating section which creates a system configuration diagram showing the network configuration of a plurality of control devices; an item distribution section which will respectively have control programs and A plurality of items of information to be referenced by the control program are allocated in the system configuration diagram; a network range allocation information creation unit creates network range allocation information having a station number and an area in the shared memory space The items of the starting address and the final address; and the system label creation department, which uses the site number as a keyword to check the system structure diagram, network range allocation information and multiple items, and creates a system label list, which has Items such as system label and device name.

Description

System Design Aids

technical field

The present invention relates to a system design support tool for assisting system design of a plurality of control devices connected in a network.

Background technique

Currently, in order to control a controlled device, a control device is used. An industrial machine is exemplified as a controlled device. As a control device, a programmable controller (JIS B 3502:2011, programmable controllers (PLC)) is exemplified.

In addition, in order to control a plurality of industrial machines, a control system configured by connecting a plurality of control devices to a network is used. In the control system described above, data is shared among a plurality of control devices by writing data in the shared memory area.

Patent Document 1: Japanese Unexamined Patent Publication No. 2011-227556

Patent Document 2: Japanese Unexamined Patent Publication No. 2012-108568

Patent Document 3: Japanese Patent Laid-Open No. 2013-246569

Contents of the invention

As a related technique, in Patent Document 1, peripheral devices collect global tag information shared among a plurality of programmable controllers, including tag names, memory area addresses and sizes in the programmable controllers. Also, the peripheral device creates a network range allocation setting database including addresses and sizes in the network shared memory area. Next, the peripheral device creates a refresh parameter setting file, which is used in the exchange of data between multiple programmable controllers, that is, the refresh operation, including the network shared memory address, size, and programmable controller memory region address. That is, the peripheral device described in Patent Document 1 determines the address in the network shared memory area based on the global tag information.

In addition, in Patent Document 2, on the label editing screen (see FIG. 7 of Patent Document 2), the name of the label, the device corresponding to the label, and the type of the device are input. And, on the control program creation screen (see FIG. 8 of Patent Document 2), a list of tags is displayed next to the control program input field. If the name of the tag and the device corresponding to the tag are input on the tag editing screen as described in Patent Document 2, editing errors may occur when adding, deleting, or changing the name of the tag or the device corresponding to the tag , the control program may perform unexpected actions.

In addition, in Patent Document 3, a system developer inputs a tag name on a system tag editor, and then selects a plurality of CPUs to share the tag on a system configuration editor. The label management support device creates a system label table that associates input label names with selected CPUs. In the case of inputting a tag name and selecting a plurality of CPUs as described in Patent Document 3, editing errors may occur when adding, deleting, or changing a tag name or CPU, and the control program may predict outside action.

The present invention has been made in view of the above circumstances, and an object of the present invention is to obtain a system design support tool capable of suppressing the possibility of a control program operating unexpectedly.

In order to solve the above-mentioned problems and achieve the object, the present invention is a system design support tool that generates a system label list having a plurality of system labels as Each control device is described in a plurality of link devices set in a shared memory space for sharing data in a network-connected control system, and the identifier is used respectively. The system design assistance tool is characterized in that , comprising: a system configuration diagram creation unit that creates a system configuration diagram that represents the network configuration of the plurality of control devices and includes station numbers that uniquely identify each of the plurality of control devices; an item allocation unit , which assigns a plurality of items each having a control program for controlling the controlled device and information referred to when the control program is executed or compiled to the plurality of items in the system configuration diagram. a control device; a network range allocation information creating unit that creates network range allocation information having the station number and an area in the shared memory space where data is written by each of the plurality of control devices These entries of the starting address and the final address; and the system label creation unit, which uses the station number as a keyword to check the system structure diagram, the network range allocation information and the multiple items, and create a A system label list of items such as the system label that uniquely identifies the identifier of the link device and the device name of the link device.

The effect of the invention

The system design support tool according to the present invention achieves the effect of being able to suppress the possibility that the control program operates unexpectedly.

Description of drawings

FIG. 1 is a diagram showing a hardware configuration for realizing a system design support tool according to the first embodiment.

FIG. 2 is a diagram showing the configuration of a control system using the system design assistance tool according to Embodiment 1. FIG.

3 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment.

FIG. 4 is a diagram showing a system configuration diagram according to Embodiment 1. FIG.

FIG. 5 is a diagram showing a system configuration diagram according to Embodiment 1. FIG.

FIG. 6 is a diagram showing network range allocation information according to Embodiment 1. FIG.

FIG. 7 is a diagram showing a system label list according to Embodiment 1. FIG.

8 is a flowchart showing a system label change operation of the system design assistance tool according to the first embodiment.

FIG. 9 is a diagram showing a system configuration diagram according to Embodiment 1. FIG.

FIG. 10 is a diagram showing a system configuration diagram according to Embodiment 1. FIG.

FIG. 11 is a diagram showing network range allocation information according to Embodiment 1. FIG.

FIG. 12 is a diagram showing a system label list according to the first embodiment.

FIG. 13 is a diagram showing network range allocation information according to Embodiment 1. FIG.

FIG. 14 is a diagram showing a system label list according to the first embodiment.

15 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment.

16 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment.

FIG. 17 is a diagram showing the configuration of a control system using a system design support device according to a comparative example.

FIG. 18 is a diagram showing network range allocation information within a project according to a comparative example.

FIG. 19 is a diagram showing system label information related to a comparative example.

FIG. 20 is a diagram showing a list of system tags in a project according to a comparative example.

FIG. 21 is a diagram showing a list of system tags in a project according to a comparative example.

FIG. 22 is a diagram showing a system label list in a project according to a comparative example.

FIG. 23 is a diagram showing network range allocation information in a project according to a comparative example.

FIG. 24 is a diagram showing system label information related to a comparative example.

FIG. 25 is a diagram showing a system label list in a project according to a comparative example.

FIG. 26 is a diagram showing a system label list in a project according to a comparative example.

FIG. 27 is a diagram showing a list of system tags in a project according to a comparative example.

detailed description

Hereinafter, the system design support tool according to the embodiment of the present invention will be described in detail based on the drawings. In addition, this invention is not limited to this embodiment.

Implementation mode 1.

FIG. 1 is a diagram showing a hardware configuration for realizing a system design support tool according to the first embodiment. The system design support device 5 that realizes the system design support tool according to Embodiment 1 is a computer. The system design support device 5 has a CPU (Central Processing Unit) 601 , a RAM (Random Access Memory) 602 , a ROM (Read Only Memory) 603 , a storage unit 604 , an input unit 605 , a display unit 606 , and a communication interface 609 .

CPU601 uses RAM602 as a work area, and executes the program memorize|stored in ROM603. Storage unit 604 stores data created by CPU 601 . The input unit 605 receives input from an operator. The display unit 606 displays characters and images. The communication interface 609 performs communication with other devices.

2 is a diagram showing the configuration of a control system using the system design assistance tool according to Embodiment 1 of the present invention.

The control system 1 is configured by connecting the control devices 2, 3, and 4 and the system design support device 5 through a network N. As shown in FIG.

Each of the control devices 2, 3, and 4 controls the controlled device by executing a control program. As the control devices 2, 3, and 4, a programmable controller is exemplified. An industrial machine is exemplified as a controlled device.

Each of the control devices 2, 3 and 4 includes a CPU and a memory. As the memory, RAM is exemplified. A part of the memory is used as a shared memory area, and another part of the memory is used as a local memory area. Each access unit in the shared memory area is called a link device. Data written by a certain control device to a certain link device is transferred to the link devices of the same address in all other control devices. In this way, data sharing among all control devices is realized. The link device is used for coordinating data between a plurality of applications executed by the control devices 2 , 3 , and 4 , that is, a plurality of control programs.

When creating a control program, each link device is described using a system label, which is an identifier that uniquely identifies each link device, instead of using an address. This facilitates the creation of the control program and improves the readability of the control program. Furthermore, when compiling the control program to create an object code, the system label is replaced with an address.

For the control device 2, the station number that uniquely identifies the control device 2 is set to "1". The control device 2 is a management site that manages the control devices 3 and 4 . For the control device 3, the station number that uniquely identifies the control device 3 is set to "2". The control device 3 is a conventional station managed by the control device 2 . For the control device 4, the station number that uniquely identifies the control device 4 is set to "3". The control device 4 is a conventional station managed by the control device 2 . For the network N, the network number that uniquely identifies the network N is set to "1".

The system design support device 5 has a system design support tool 6 for generating a system label list having a plurality of system labels as identifiers, and a storage unit 604. The control devices 2 , 3 , and 4 use the identifiers for describing a plurality of link devices set in the shared memory space for sharing data. A personal computer is exemplified as the system design support device 5 .

The system design support tool 6 is realized by the CPU 601 in the system design support device 5 executing a system design support program.

The system design support tool 6 includes: a system configuration diagram creation unit 10 that creates a system configuration diagram 30 showing the network configurations of the control devices 2, 3, and 4, including and a project creation unit 11 that creates projects 31a, 31b, and 31c each having a control program for controlling a controlled device and information to be referred to when the control program is executed or compiled. Each of the items 31a, 31b, and 31c includes the station number of the control device 2, 3, or 4, and execution data to be referred to when executing the object code of the control program.

Examples of information to be referred to at the time of execution or compilation of the control program include parameters, device memory that defines the work memory area, and connections that describe the connections between the multiple terminals of the control devices 2, 3, and 4 and industrial machinery. information.

In addition, the system design support tool 6 has: an item allocation unit 12 that allocates the items 31a, 31b, and 31c to the control devices in the system configuration diagram 30; and a network range allocation information creation unit 13 that creates network range allocation information 32 , the network range allocation information 32 has items such as the station number, the initial address and the final address of the link device, and the link device is in the shared memory space in which data is written by the plurality of control devices 2, 3 and 4 respectively area.

In addition, the system design support tool 6 has a system label list creation unit 14 that performs a system configuration diagram 30, network range allocation information 32, and items 31a, 31b, and 31c using the site number as a key (Key). After checking, a system label list 33 is created. The system label list 33 has entries such as a system label which is an identifier for uniquely specifying the link device and a device name for uniquely specifying the link device.

In addition, the system design support tool 6 has: a network range allocation information duplication determination unit 15 that determines whether or not the address ranges of a plurality of records (records) of the network range allocation information overlap; a first system label list change unit 16 that follows Changes in the system configuration diagram 30 change the system label list 33; and the second system label list change unit 17 changes the system label list 33 following changes in the network range allocation information.

In addition, the system design assisting tool 6 has: a system labeling target selection unit 18 that receives a selection from the user for a system label creation target area in the shared memory space; The usable network range is calculated and reflected in the network range allocation information 32 .

The storage unit 604 stores the system configuration diagram 30 created by the system configuration diagram creation unit 10, the items 31a, 31b, and 31, the network range assignment information 32, and the system label list 33. The items 31a, 31b, and 31 Created by the item creation unit 11 , the network range allocation information 32 is created by the network range allocation information creation unit 13 , and the system label list 33 is created by the system label list creation unit 14 . As the storage unit 604 , HDD (Hard Disk Drive) or SSD (Solid State Drive) are exemplified.

3 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment. First, in step S100 , the system configuration diagram creation unit 10 creates a system configuration diagram 30 .

FIG. 4 is a diagram showing a system configuration diagram according to Embodiment 1. FIG. When creating the system configuration diagram 30, first, the system configuration diagram creation unit 10 arranges the objects 30a, 30b, and 30c corresponding to the control devices 2, 3, and 4, respectively. The object 30a corresponds to the control device 2, and the station number "1" is set. The object 30b corresponds to the control device 3, and the site number "2" is set. The object 30c corresponds to the control device 4, and the site number "3" is set. Next, the system configuration diagram creation unit 10 arranges the object 30d connecting the objects 30a, 30b, and 30c. The object 30d corresponds to the network N, and the network number "1" is set.

The system configuration diagram creation unit 10 can automatically create the system configuration diagram 30 based on the information describing the network configuration of the control system 1 .

Referring again to Fig. 3, in step S102, the project creation part 11 carries out the establishment of the project 31a, 31b and 31c of each control device 2, 3 and 4, and the project distribution part 12 carries out the project 31a, 31b and 31c to the object 30a, 30b and the allocation of 30c.

FIG. 5 is a diagram showing a system configuration diagram according to Embodiment 1. FIG. The item assignment unit 12 assigns the object 30e to the object 30a corresponding to the control device 2 based on the operator's operation input. The object 30e corresponds to the item 31a, and the item name "prj01" is set. The item assignment unit 12 assigns the object 30f to the object 30b corresponding to the control device 3 based on the operator's operation input. The object 30f corresponds to the item 31b, and the item name "prj02" is set. The item assignment unit 12 assigns the object 30g to the object 30c corresponding to the control device 4 based on the operator's operation input. The object 30g corresponds to the item 31c, and the item name "prj03" is set.

Referring again to FIG. 3 , in step S104 , the network range allocation information creation unit 13 creates network range allocation information.

FIG. 6 is a diagram showing network range allocation information according to Embodiment 1. FIG. The network range allocation information 32 has items such as a station number, a start address and a final address of a link device which is an area in the shared memory space where each of the control devices 2, 3, and 4 writes data.

The operator enters the site number, the start address and the end address of the link device in each entry of the network range allocation information 32 . In the network range assignment information 32, the station number "1", the start address "0x0000" and the end address "0x000F" of the control device 2 are input in the first line 32a. In addition, the station number "2", the start address "0x0010" and the end address "0x001F" of the control device 3 are input in the second line 32b. In addition, the station number "3", the start address "0x0020" and the end address "0x002F" of the control device 4 are input in the third line 32c.

Therefore, the link device where the control device 2 of the station number "1" writes data is 16 bytes from the start address "0x0000" to the end address "0x000F". In addition, the link device to which the control device 3 of the station number "2" writes data is 16 bytes from the start address "0x0010" to the end address "0x001F". In addition, the link device where the control device 4 of the station number "3" writes data is 16 bytes from the start address "0x0020" to the end address "0x002F".

Referring to FIG. 3 again, in step S106, the system label list creation unit 14 checks the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a keyword, thereby performing a system label Creation of Listing 33.

FIG. 7 is a diagram showing a system label list according to Embodiment 1. FIG. The system label list 33 has items such as a system label which is an identifier for uniquely identifying a link device, a name of a CPU built in the control device, and a device name for uniquely identifying a link device. In addition, the system label list 33 may also supplementarily include item names of items, but the item names are not mandatory entries of the system label list 33 .

In the system label list 33, each of the plurality of rows 33a corresponds to each byte of the link device to which the control device 2 performs data writing. The system label list creation unit 14 creates and arranges a system label, which is an identifier that uniquely identifies each link device, in the entry of the system label in each of the plurality of lines 33 a according to a preset creation rule.

In Embodiment 1, the preset generation rule is a character string such as "start_", the station number of the control device that writes data to the link device, a character string such as "switch of the station", and The control device writes data to the rules in conjunction with the serial numbers of the link devices.

In the system label list 33 , the “start_1 station switch 1 ” generated by the system label list creation unit 14 is placed in the entry of the system label in the first line of the plurality of lines 33 a. In addition, the “start_1 station switch 16 ” generated by the system label list creation unit 14 is arranged in the entry of the system label in the last line of the plurality of lines 33 a.

In addition, the system label list creation unit 14 arranges the CPU name "CPU01" built in the control device 2 in the entry of the CPU name in each of the plurality of rows 33a. In addition, the system label list creation unit 14 arranges a device name uniquely identifying each link device in each of the plurality of rows 33 a in the device name entry.

In the system label list 33, each of the plurality of rows 33b corresponds to each byte of the link device to which the control device 3 writes data. The system label list creation unit 14 creates and arranges a system label, which is an identifier that uniquely identifies each link device, in the entry of the system label in each of the plurality of lines 33b in accordance with a preset creation rule.

In the system label list 33 , the “start_2 station switch 1 ” generated by the system label list creation unit 14 is placed in the entry of the system label in the first line of the plurality of lines 33 b. In addition, the “start_2 station switch 16 ” generated by the system label list creation unit 14 is arranged in the entry of the system label in the last line of the plurality of lines 33 b.

In addition, the system label list creation unit 14 arranges the CPU name "CPU02" built in the control device 3 in the entry of the CPU name in each of the plurality of rows 33b. In addition, the system label list creation unit 14 arranges a device name uniquely identifying each link device in each of the plurality of rows 33 b in the device name entry.

In the system label list 33, each of the plurality of rows 33c corresponds to each byte of the link device to which the control device 4 performs data writing. The system label list creation unit 14 creates and arranges a system label, which is an identifier that uniquely identifies each link device, in the entry of the system label in each of the plurality of lines 33 c according to a preset creation rule.

In the system label list 33 , the “start_3 station switch 1 ” generated by the system label list creation unit 14 is placed in the entry of the system label in the first line of the plurality of lines 33 c. In addition, the “activation_3 station switch 16 ” generated by the system label list creation unit 14 is arranged in the entry of the system label in the last line of the plurality of lines 33 c.

In addition, the system label list creation unit 14 arranges the CPU name "CPU03" built in the control device 4 in the entry of the CPU name in each of the plurality of rows 33c. In addition, the system label list creation unit 14 arranges a device name uniquely identifying each link device in the device name entry in each of the plurality of rows 33c.

As described above, according to the system design assisting tool 6, the system label list creation unit 14 can check the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c using the site number as a keyword, and create a system label List 33. This eliminates the need for the operator to input each entry of the system label list 33 , so that input errors in the system label list 33 can be suppressed. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, the system design support tool 6 preferably protects the system label list 33 so that the operator cannot change the system label list 33 with a spreadsheet program or a text editor. This prevents the operator from changing each entry in the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

8 is a flowchart showing a system label change operation of the system design assistance tool according to the first embodiment. Here, the case where the control apparatus 4 whose station number is "3" is replaced with the new control apparatus whose station number is "4" is demonstrated as an example.

First, in step S110 , the system configuration diagram creation unit 10 changes the system configuration diagram 30 . Specifically, the system configuration diagram creation unit 10 replaces the object 30c corresponding to the control device 4 with the station number "3" shown in FIG. 3 with the object corresponding to the new control device with the station number "4". 30h.

FIG. 9 is a diagram showing a system configuration diagram according to Embodiment 1. FIG. The system configuration diagram 30 is a system configuration diagram in which the object 30c corresponding to the control device 4 with the station number "3" is replaced with the object 30h corresponding to the new control device with the station number "4".

Referring to FIG. 8 again, in step S112, the item allocation part 12 changes the allocation of the item 31c to the object 30h.

FIG. 10 is a diagram showing a system configuration diagram according to Embodiment 1. FIG. The item assigning unit 12 assigns the object 30g to the object 30h corresponding to the new control device whose site number is "4" based on the operator's operation input. Object 30g corresponds to item 31c.

Referring again to FIG. 8 , in step S114 , the network range allocation information creation unit 13 changes the network range allocation information.

FIG. 11 is a diagram showing network range allocation information according to Embodiment 1. FIG. The operator performs an input to change the site number in the third row 32c of the network range allocation information 32 from "3" to "4".

Referring again to FIG. 8 , in step S116 , the network range allocation information duplication determination unit 15 checks for duplication of the network range allocation information 32 . Specifically, the network range allocation information overlap determination unit 15 checks whether the address ranges in each line of the network range allocation information 32 do not overlap.

Next, in step S118, the first system label list changing unit 16 checks the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a keyword, thereby performing a system label Changes to Listing 33.

FIG. 12 is a diagram showing a system label list according to the first embodiment. In the system label list 33 shown in FIG. 11, a plurality of lines 33d are changed, and other lines are not changed.

Each of the plurality of rows 33d of the system label list 33 corresponds to each byte of the link device whose data is written by the new control device whose station number is "4". The first system label list changing unit 16 creates and arranges a system label, which is an identifier that uniquely identifies each link device, in the entry of the system label in each of the plurality of lines 33d according to a preset creation rule.

In the system label list 33 , the “start_4 station switch 1 ” generated by the first system label list changing unit 16 is arranged in the entry of the system label in the first line of the plurality of lines 33 d. In addition, the “activation_4 station switch 16 ” generated by the first system label list changing unit 16 is arranged in the entry of the system label in the last line of the plurality of lines 33 d.

In addition, the first system label list change unit 16 arranges the CPU name "CPU04" built in the new control device whose station number is "4" in the entry of the CPU name in each of the plurality of rows 33d.

As described above, according to the system design assisting tool 6, the first system label list change unit 16 can check the system configuration diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a keyword, and The system label list 33 is changed. This eliminates the need for the operator to change each entry of the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, the system design support tool 6 preferably protects the system label list 33 so that the operator cannot change the system label list 33 with a spreadsheet program or a text editor. This prevents the operator from changing each entry in the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In the above, the case of replacing the control device 4 with the station number "3" with the new control device with the station number "4" was used as an example to use the flow chart of FIG. 8 , but next, the link device The case where increase and decrease are performed will be described with reference to the flowchart of FIG. 8 as an example.

In the case where link devices have been increased or decreased, the system configuration diagram creation unit 10 does not change the system configuration diagram 30 in step S110 because the system configuration has not been changed. In addition, step S110 may also be skipped when the system configuration is not changed.

When link devices are increased or decreased, since the system configuration is not changed, the item allocation unit 12 does not change the allocation of the items 31a, 31b, and 31c to the objects 30a, 30b, and 30c in step S112. In addition, when the system configuration is not changed, step S112 may be skipped.

Next, in step S114, the network range allocation information creation unit 13 changes the network range allocation information.

FIG. 13 is a diagram showing network range allocation information according to Embodiment 1. FIG. The operator enters "0x0010" in the entry of the final address in the first line 32a in the network range allocation information 32 . Thus, the link device to which the control device 2 of the station number "1" writes data is expanded to 17 bytes from the start address "0x0000" to the end address "0x0010".

In addition, the operator enters "0x0011" in the entry of the start address in the second line 32b in the network range allocation information 32 . In addition, the operator inputs "0x001F" in the entry of the final address in the second row 32b in the network range allocation information 32 . As a result, the link device where the control device 3 of the station number "2" writes data is reduced to 15 bytes from the start address "0x0011" to the final address "0x001F".

In addition, the operator inputs "0x0020" in the entry of the start address in the third line 32c in the network range allocation information 32 . In addition, the operator inputs "0x002E" in the entry of the final address in the third line 32c in the network range allocation information 32 . Thus, the link device where the control device 4 of the station number "3" writes data is reduced to 15 bytes from the start address "0x0020" to the end address "0x002E".

Referring to FIG. 8 again, in step S118, the second system label list changing unit 17 checks the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a keyword, thereby performing System label list 33 changes.

FIG. 14 is a diagram showing a system label list according to the first embodiment. The link device of the control device 2 whose station number is "1" is enlarged to 17 bytes, and a line 33e is added to the system label list 33 shown in FIG. 14 accordingly.

In addition, the link device of the control device 3 whose station number is "2" is reduced to 15 bytes, and accordingly, a cancel line is added to line 33f in the system label list 33 shown in FIG. 13 . In addition, the second system label list changing unit 17 may delete the row 33f.

In addition, the link device of the control device 4 whose station number is "3" is reduced to 15 bytes, and a cancel line is added to the line 33g in the system label list 33 shown in FIG. 14 . In addition, the second system label list changing unit 17 may delete the row 33g.

As described above, according to the system design assisting tool 6, the second system label list change unit 17 can check the system configuration diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a key word, and can identify the system The tag list 33 is changed. This eliminates the need for the operator to change each entry of the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, the system design support tool 6 preferably protects the system label list 33 so that the operator cannot change the system label list 33 with a spreadsheet program or a text editor. Accordingly, since the operator cannot change each item of the system label list 33 , it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, the system design support tool 6 allows an operator to select a target for system labeling from among all link devices.

15 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment. In the flowchart of FIG. 15 , steps S100 , S102 , S104 , and S106 are the same as those in the flowchart shown in FIG. 3 , and thus description thereof will be omitted.

In the flowchart of FIG. 15 , step S105 is added after step S104 and before step S106 .

In step S105 , the system labeling target selection unit 18 selects a system labeling target from among all link devices based on an operator's operation input. The operator can select a desired address range from among the address ranges described in the network range allocation information 32, thereby being able to select a system labeling target. In addition, the operator can select a desired object from among the objects arranged in the system configuration diagram 30 , thereby being able to select a system tagged object.

As described above, according to the system design support tool 6 , the system labeling target selection unit 18 can select a system labeling target from among all link devices based on an operator's operation input. Thus, the system design assistance tool 6 can create the system label list 33 containing only necessary link devices. Therefore, the system design support tool 6 can suppress the enlargement of the system label list 33 and can improve the readability of the system label list 33 .

In addition, the system design support tool 6 can also calculate the address range that is the network range that can be used by the link device. For example, other devices may be connected to the control system 1 via a network in addition to the control devices 2 , 3 , and 4 . As another device, a display device capable of displaying various information of the control devices 2 , 3 , and 4 is exemplified. When other devices are connected via a network, the address used by the display device cannot be used as the address of the link device.

16 is a flowchart showing a system label creation operation of the system design assistance tool according to the first embodiment. In the flow chart of FIG. 16 , steps S100 , S102 , S104 , and S106 are the same as those in the flow chart shown in FIG. 3 , and thus description thereof will be omitted.

In the flowchart of FIG. 16, step S103 is added after step S102 and before step S104.

In step S103 , the network range allocation calculation reflection unit 19 calculates an address range which is a network range usable by link devices based on the information describing the network configuration in the system configuration diagram 30 , and reflects it in the network range allocation information 32 . The operator can input an entry into the network range allocation information 32 in step S104 while referring to the address range reflected in the network range allocation information 32 in step S103 .

As described above, according to the system design support tool 6, the network range allocation calculation reflection unit 19 calculates the address range, which is the network range that can be used by the link device, based on the information describing the network configuration in the system configuration diagram 30, and reflects it on the network Range Allocation Information 32 . Thus, the system design assistance tool 6 can suppress address conflicts between link devices and other devices. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

Next, comparative examples of the present invention will be described.

FIG. 17 is a diagram showing the configuration of a control system using a system design support device according to a comparative example.

The control system 51 is configured by connecting the control devices 52, 53, and 54 and the system design support device 55 through the network N1.

Each of the control devices 52, 53, and 54 controls the controlled device by executing a control program.

For the control device 52, the station number that uniquely identifies the control device 52 is set to "1". The control device 52 is a management site that manages the control devices 53 and 54 . For the control device 53, the station number that uniquely identifies the control device 53 is set to "2". The control device 53 is a conventional station managed by the control device 52 . For the control device 54, the station number that uniquely identifies the control device 54 is set to "3". Control device 54 is a conventional station managed by control device 52 . For the network N1, the network number that uniquely identifies the network N1 is set to "1".

The system design support device 55 has a programming tool unit 56 , a table calculation unit 57 , and a storage unit 58 .

The programming tool unit 56 is realized by the CPU in the system design support device 55 executing a programming tool program. The table calculation unit 57 is realized by the CPU in the system design support device 55 executing a table calculation program.

The storage unit 58 stores the items 61 , 62 , and 63 created by the programming tool unit 56 and the system label information 70 created by the table calculation unit 57 .

Next, the system list creation operation of the system design support device 55 will be described.

First, the programming tool part 56 creates the network range allocation information 61a in the project 61 allocated to the control apparatus 52 as a management site based on the operator's input. In addition, items 62 and 63 respectively assigned to control devices 53 and 54 as normal stations do not contain network range assignment information.

FIG. 18 is a diagram showing network range allocation information within a project according to a comparative example. In the item 61, the item name which uniquely identifies the item 61 is set as "prj01". The network range allocation information 61a has entries of a site number, a start address, and a final address of a link device which is an area in the shared memory space where data is written by each of the control devices 52 , 53 , and 54 .

The operator enters the site number, the start address and the end address of the link device in each entry of the network range allocation information 61a. In the network range assignment information 61a, the station number "1", the start address "0x0000" and the end address "0x000F" of the control device 52 are input in the first line 61a1. In addition, the station number "2", the start address "0x0010" and the end address "0x001F" of the control device 53 are input in the second line 61a2. In addition, the station number "3", the start address "0x0020" and the end address "0x002F" of the control device 54 are input in the third line 61a3.

Therefore, the link device where the control device 52 of the station number "1" writes data is 16 bytes from the start address "0x0000" to the end address "0x000F". In addition, the link device where the control device 53 of the station number "2" writes data is 16 bytes from the start address "0x0010" to the end address "0x001F". In addition, the link device where the control device 54 of the station number "3" writes data is 16 bytes from the start address "0x0020" to the end address "0x002F".

Next, the table calculation unit 57 creates the system label information 70 based on the operator's input. The operator creates the system label information 70 while referring to the network range allocation information 61 a created by the engineering tool unit 56 .

FIG. 19 is a diagram showing system label information related to a comparative example. The system label information 70 has items such as a system label which is an identifier for uniquely identifying a link device, a name of a CPU built in a control device, and a device name for uniquely identifying a link device. In addition, the system label information 70 may also supplementarily include the project name of the project, but the project name is not a mandatory item of the system label information 70 .

In the system label information 70, each of the plurality of rows 70a corresponds to each byte of the link device to which the control device 52 performs data writing. The operator enters a system label, which is an identifier for uniquely specifying each link device, in the entry of the system label in each of the plurality of lines 70a.

In the system label information 70 , the entry of the system label in the first line of the plurality of lines 70 a is entered by the operator as "switch 1 of the start_1 station". In addition, in the entry of the system label in the last line of the plurality of lines 70a, "start_1 station switch 16" is input by the operator.

In addition, the operator inputs the CPU name "CPU01" built in the control device 52 into the entry of the CPU name in each of the plurality of rows 70a. In addition, the operator inputs a device name that uniquely specifies each link device in the entry of the device name in each of the plurality of rows 70a.

In the system label information 70 , each of the plurality of rows 70 b corresponds to each byte of the link device to which data is written by the control device 53 . The operator enters a system label, which is an identifier for uniquely specifying each link device, in the entry of the system label in each of the plurality of lines 70b.

In the system label information 70, the entry of the system label in the first line of the plurality of lines 70b is input by the operator with "start_2 station switch 1". In addition, the entry of the system label on the last line of the plurality of lines 70b is input by the operator with "start_2 station switch 16".

In addition, the operator inputs the CPU name "CPU02" built in the control device 53 into the entry of the CPU name in each of the plurality of rows 70b. In addition, the operator enters a device name that uniquely specifies each link device in the entry of the device name in each of the plurality of rows 70b.

In the system label information 70 , a plurality of rows 70 c correspond to respective bytes of link devices to which data is written by the control device 54 . The operator enters a system label, which is an identifier for uniquely specifying each link device, in the entry of the system label in each of the plurality of lines 70c.

In the system label information 70, the entry of the system label in the first line of the plurality of lines 70c is input by the operator with "start_3 station switch 1". In addition, the entry of the system label on the last line of the plurality of lines 70c is input by the operator with "start_3 station switch 16".

In addition, the operator inputs the CPU name "CPU03" built in the control device 54 into the entry of the CPU name in each of the plurality of rows 70c. In addition, the operator enters a device name that uniquely specifies each link device in the entry of the device name in each of the plurality of rows 70c.

Next, the programming tool unit 56 creates system label lists 61b, 62b, and 63b in the items 61, 62, and 63 based on the operator's input. The operator creates the system label lists 61 b , 62 b , and 63 b while referring to the system label information 70 created by the table calculation unit 57 .

FIG. 20 is a diagram showing a list of system tags in a project according to a comparative example. The system label list 61b has entries of a system label, a CPU name, and a device name. In addition, the system label list 61b may also supplementarily include the project name of the project, but the project name is not a mandatory entry of the system label list 61b. The operator inputs the value of each entry of the system label list 61 b while referring to a plurality of rows 70 a in the system label information 70 created by the table calculation unit 57 .

FIG. 21 is a diagram showing a list of system tags in a project according to a comparative example. The system label list 62b has entries of a system label, a CPU name, and a device name. In addition, the system label list 62b may also supplementarily include the project name of the project, but the project name is not a mandatory entry of the system label list 62b. The operator inputs the value of each entry of the system label list 62 b while referring to a plurality of rows 70 b in the system label information 70 created by the table calculation unit 57 .

FIG. 22 is a diagram showing a system label list in a project according to a comparative example. The system label list 63b has items of a system label, a CPU name, and a device name. In addition, the system label list 63b may also supplementarily include the project name of the project, but the project name is not a mandatory entry of the system label list 63b. The operator inputs the value of each entry of the system label list 63 b while referring to a plurality of rows 70 c in the system label information 70 created by the table calculation unit 57 .

As described above, in the comparative example, the system label information 70 and all the entries of the system label lists 61b, 62b, and 63b were input by the operator. Therefore, input errors easily occur in the system label information 70 and the system label lists 61b, 62b, and 63b. If there is an input error in the system label information 70 and the system label lists 61b, 62b, and 63b, the following situation may occur, that is, the control program in the items 61, 62, and 63 performs an unexpected action, and then the controlled device performs an unexpected action. outside action.

Next, the operation of changing the system list by the system design support device 55 will be described.

First, the programming tool unit 56 changes the network range assignment information 61a based on the operator's input.

FIG. 23 is a diagram showing network range allocation information in a project according to a comparative example. The operator changed the final address of the first row 61a1 of the network range allocation information 61a from "0x000F" to "0x0010". Therefore, the link device for data writing by the control device 52 of the site number "1" becomes the starting address " 0x0000" to the 17 bytes of the final address "0x0010".

Next, the operator changes the start address of the second row 61a2 of the network range allocation information 61a from "0x0010" to "0x0011". Therefore, the link device to which the control device 53 of the station number "2" writes data is 15 bytes from the start address "0x0011" to the end address "0x001F".

Next, the operator changes the final address of the third row 61a3 of the network range allocation information 61a from "0x002F" to "0x002E". Therefore, the link device to which the control device 54 of the station number "3" writes data is 15 bytes from the start address "0x0020" to the end address "0x002E".

Next, the table calculation unit 57 changes the system label information 70 based on the operator's input. The operator changes the system label information 70 while referring to the network range allocation information 61 a changed by the engineering tool unit 56 .

FIG. 24 is a diagram showing system label information related to a comparative example. The link device to which the control device 52 writes data is changed from 16 bytes to 17 bytes, and the operator adds a row 70d accordingly. In the entry of the system label on line 70d, "start_1 station switch 17" is entered by the operator. In addition, "CPU01" is entered by the operator in the entry of the CPU name in row 70d. In addition, "J1¥B10" is input by the operator in the entry of the equipment name in row 70d.

In addition, the link device to which the control device 53 writes data is changed from 16 bytes to 15 bytes, and accordingly, the operator adds a cancel line to line 70e. In addition, the operator can also delete row 70e.

In addition, the link device to which the control device 54 writes data is changed from 16 bytes to 15 bytes, and accordingly, the operator adds a cancel line to line 70f. In addition, the operator can also delete line 70f.

Next, the programming tool unit 56 changes the system label lists 61b, 62b, and 63b in the items 61, 62, and 63 based on the operator's input. The operator performs the work of changing the system label lists 61 b , 62 b , and 63 b while referring to the system label information 70 created by the table calculation unit 57 .

FIG. 25 is a diagram showing a system label list in a project according to a comparative example. The operator adds a row 70d to the system label information 70 by the table calculation unit 57, and accordingly adds a row 61b1 to the system label list 61b.

FIG. 26 is a diagram showing a system label list in a project according to a comparative example. The operator adds a cancel line to the row 70e of the system label information 70 by the table calculation unit 57, and accordingly adds a cancel line to the row 62b1 of the system label list 62b. In addition, the operator can also delete row 62b1.

FIG. 27 is a diagram showing a list of system tags in a project according to a comparative example. The operator adds a cancellation line to the line 70f of the system label information 70 by the table calculation unit 57, and accordingly adds a cancellation line to the line 63b1 of the system label list 63b. In addition, the operator can also delete row 63b1.

As described above, in the comparative example, the operator changed the system label information 70 and the system label lists 61b, 62b, and 63b. Therefore, a change error is likely to occur in the system label information 70 and the system label lists 61b, 62b, and 63b. If there is a change error in the system label information 70 and the system label lists 61b, 62b, and 63b, the following situation may occur, that is, the control program in the items 61, 62, and 63 performs an unexpected action, and then the controlled device performs an unexpected operation. outside action.

On the other hand, according to the system design support tool 6 according to Embodiment 1, the system label list creation unit 14 can check the system configuration diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c using the site number as a key. , create a system label list 33. This eliminates the need for the operator to input each entry of the system label list 33 , so that input errors in the system label list 33 can be suppressed. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, according to the system design assisting tool 6, the first system label list changing unit 16 can check the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a key, and can check the system label list 33 to make changes. This eliminates the need for the operator to change each entry of the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, according to the system design assisting tool 6, the second system label list changing unit 17 can check the system structure diagram 30, the network range allocation information 32, and the items 31a, 31b, and 31c by using the site number as a key, and can check the system label list 33 to make changes. This eliminates the need for the operator to change each entry of the system label list 33 , and thus it is possible to suppress the occurrence of a change error in the system label list 33 . Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

In addition, according to the system design support tool 6 , the system labeling target selection unit 18 can select a system labeling target from among all link devices based on an operator's operation input. Thus, the system design assistance tool 6 can create the system label list 33 containing only required link devices. Therefore, the system design support tool 6 can suppress the enlargement of the system label list 33 and can improve the readability of the system label list 33 .

In addition, according to the system design support tool 6, the network range allocation calculation reflection unit 19 calculates the network range that can be used by link devices, that is, the address range based on the information describing the network configuration in the system configuration diagram 30, and reflects it in the network range allocation information32. Thus, the system design assistance tool 6 can suppress address conflicts between link devices and other devices. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform unexpected operations, and can suppress the possibility that the controlled device will perform unexpected operations.

The configuration shown in the above embodiments is an example of the content of the present invention, and can be combined with other known techniques, and a part of the configuration can be omitted or changed without departing from the gist of the present invention.

Explanation of labels

1 Control System, 2, 3, 4 Control Device, 5 System Design Auxiliary Device, 6 System Design Auxiliary Tool, 10 System Structure Diagram Creation Department, 11 Project Creation Department, 12 Project Allocation Department, 13 Network Range Allocation Information Creation Department, 14 System Label List Creation Unit, 15 Network Range Allocation Information Duplication Judgment Unit, 16 First System Label List Change Unit, 17 Second System Label List Change Unit, 18 System Labeling Target Selection Unit, 19 Network Range Allocation Calculation Reflection Unit, 30 System structure diagram, 31a, 31b, 31c items, 32 network range allocation information, 33 system label list, 601 CPU, 604 storage unit.

Claims (7)

1. A system design assisting tool that generates a system label list having a plurality of system labels as identifiers, wherein, in order to identify in a control program in a control system in which a plurality of control devices are network-connected Describe the plurality of link devices set in the shared memory space used by the plurality of control devices to share data and use the identifiers respectively, The system design aid is characterized by: a system configuration diagram creation unit that creates a system configuration diagram showing a network configuration of the plurality of control devices, including station numbers uniquely identifying each of the plurality of control devices; an item assigning unit that assigns, to each of the items in the system configuration diagram, a plurality of items each having a control program for controlling the controlled device and information referred to when the control program is executed or compiled. a plurality of control devices; a network range allocation information creation unit that creates network range allocation information having the station number and the start of an area in the shared memory space where data is written by each of the plurality of control devices address and final address entries; and a system label creation unit that checks the system configuration diagram, the network range allocation information, and the plurality of items using the site number as a key, and creates an identifier that uniquely identifies the link device That is, the system label and the system label list of these items that uniquely determine the device name of the link device. 2. The system design aid tool according to claim 1, characterized in that, A system label list changing unit is provided for changing the system label list following changes in the system configuration diagram. 3. The system design aid tool according to claim 1, characterized in that, A system label list change unit is provided for changing the system label list following changes in the network range allocation information. 4. The system design aid tool according to claim 3, wherein: The system label list changing unit, based on the increase or decrease of the allocation range of the network range allocation information, newly creates the system label for the portion where the allocation range increases, and updates the system label for the portion where the allocation range decreases. delete. 5. The system design aid tool according to claim 1, wherein: A network range allocation information overlap judging unit for judging whether or not address ranges of a plurality of records of the network range allocation information overlap is provided. 6. The system design aid tool according to claim 1, wherein: A system labeling target selection unit is provided for receiving a selection of a system label creation target area in the shared memory space from a user. 7. The system design aid tool according to claim 1, wherein: A network range allocation calculation reflection unit is provided, and the network range allocation calculation reflection unit calculates the usable network range based on the system configuration diagram and reflects it in the network range allocation information.