WO2016110983A1

WO2016110983A1 - System design assistance tool

Info

Publication number: WO2016110983A1
Application number: PCT/JP2015/050399
Authority: WO
Inventors: 真哉尾上; 直樹竹下
Original assignee: 三菱電機株式会社
Priority date: 2015-01-08
Filing date: 2015-01-08
Publication date: 2016-07-14
Also published as: CN107003649A; JP6076564B2; JPWO2016110983A1; CN107003649B; KR101918430B1; KR20170088966A

Abstract

Provided is a system design assistance tool which generates a system label list provided with a plurality of system labels which are identifiers used to describe within a control program each of a plurality of link devices which are set within a common memory space, said system design assistance tool comprising: a system diagram creating unit which creates a system diagram which signifies a network configuration of a plurality of control devices; a project allotment unit which allots within the system diagram a plurality of projects which respectively have a control program and information which is queried by the control program; a network range allotment information creating unit which creates network range allotment information which has items of a station number, and a header address and a terminal address of a region within the common memory space; and a system label creating unit which queries, with the station number as a key, the system diagram, the network range allotment information, and the plurality of projects, and creates a system label list which has items of system labels and device names.

Description

System design support tool

The present invention relates to a system design support tool that supports system design of a plurality of control devices connected to a network.

Conventionally, control devices are used to control controlled devices. The controlled device is exemplified by an industrial machine. Examples of the control device include programmable controllers (JIS B 3502: 2011, programmable controllers (PLC)).

Also, in order to control a plurality of industrial machines, a control system configured by connecting a plurality of control devices over a network is used. In such a control system, data is shared among a plurality of control devices by writing data in a shared memory area.

JP 2011-227556 A JP 2012-108568 A JP 2013-246469 A

As a related technique, in Patent Document 1, a peripheral device collects global label information including a label name, a memory area address in a programmable controller, and a size shared among a plurality of programmable controllers. Then, the peripheral device creates a network range assignment setting database including the address and size in the network shared memory area. Next, the peripheral device creates a refresh parameter setting file including a network shared memory address, a size, and a memory area address in the programmable controller, which are used for a refresh operation that is an exchange of data among a plurality of programmable controllers. That is, the peripheral device described in Patent Document 1 determines an address in the network shared memory area based on the global label information.

In Patent Document 2, the label name, the device corresponding to the label, and the device type are input on the label editing screen (see FIG. 7 of Patent Document 2). Then, on the control program creation screen (see FIG. 8 of Patent Document 2), a list of labels is displayed beside the control program input field. As described in Patent Document 2, if the label name and the device corresponding to the label are input to the label editing screen, an editing error occurs when adding, deleting, or changing the device corresponding to the label name or label. May occur, and the control program may behave unexpectedly.

In Patent Document 3, the system developer inputs a label name on the system label editor, and further selects a plurality of CPUs sharing the label on the system configuration editor. The label management support apparatus creates a system label table in which the input label name is associated with a plurality of selected CPUs. As described in Patent Document 3, if a label name is input and a plurality of CPUs are selected, an edit error may occur when a label name or CPU is added, deleted, or changed. May behave unexpectedly.

The present invention has been made in view of the above, and an object of the present invention is to obtain a system design support tool capable of suppressing the possibility that a control program will perform an unexpected operation.

In order to solve the above-described problems and achieve the object, the present invention is set in a shared memory space for sharing data among the plurality of control devices in a control system in which the plurality of control devices are network-connected. A system design support tool for generating a system label list having a plurality of system labels, which are identifiers respectively used for describing a plurality of link devices in a control program, and comprising a network configuration of the plurality of control devices A system configuration diagram creation unit that creates a system configuration diagram including a station number that uniquely identifies each of the plurality of control devices, a control program for controlling the controlled device, and a runtime or compilation of the control program A plurality of projects each having information that is sometimes referred to are referred to as the plurality of controls in the system configuration diagram. Network range allocation information having items of a project allocation unit to be allocated to each device, the station number, and a start address and a final address of an area in the shared memory space where each of the plurality of control devices writes data The network range allocation information creating unit for creating the identifier, the system configuration diagram, the network range allocation information and the plurality of projects are collated with the station number as a key, and the system is an identifier for uniquely identifying the link device And a system label creating unit that creates a system label list having a label and a device name item that uniquely identifies the link device.

The system design support tool according to the present invention has an effect that it is possible to suppress the possibility that the control program performs an unexpected operation.

1 is a diagram illustrating a hardware configuration that implements a system design support tool according to a first embodiment; The figure which shows the structure of the control system using the system design support tool concerning Embodiment 1. FIG. 1 is a flowchart showing a system label creation operation of the system design support tool according to the first embodiment. The figure which shows the system block diagram concerning Embodiment 1. FIG. The figure which shows the system block diagram concerning Embodiment 1. FIG. The figure which shows the network range allocation information concerning Embodiment 1. The figure which shows the system label list concerning Embodiment 1. FIG. A flowchart showing a system label changing operation of the system design support tool according to the first embodiment. The figure which shows the system block diagram concerning Embodiment 1. FIG. The figure which shows the system block diagram concerning Embodiment 1. FIG. The figure which shows the network range allocation information concerning Embodiment 1. The figure which shows the system label list concerning Embodiment 1. FIG. The figure which shows the network range allocation information concerning Embodiment 1. The figure which shows the system label list concerning Embodiment 1. FIG. 1 is a flowchart showing a system label creation operation of the system design support tool according to the first embodiment. 1 is a flowchart showing a system label creation operation of the system design support tool according to the first embodiment. The figure which shows the structure of the control system using the system design assistance apparatus concerning a comparative example The figure which shows the network range allocation information in the project concerning the comparative example The figure which shows the system label information concerning a comparative example The figure which shows the system label list in the project concerning the comparative example The figure which shows the system label list in the project concerning the comparative example The figure which shows the system label list in the project concerning the comparative example The figure which shows the network range allocation information in the project concerning the comparative example The figure which shows the system label information concerning a comparative example The figure which shows the system label list in the project concerning the comparative example The figure which shows the system label list in the project concerning the comparative example The figure which shows the system label list in the project concerning the comparative example

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

Embodiment 1 FIG.
FIG. 1 is a diagram illustrating a hardware configuration for realizing the system design support tool according to the first embodiment. The system design support apparatus 5 that implements the system design support tool according to the first embodiment is a computer. The system design support apparatus 5 includes a central processing unit (CPU) 601, a random access memory (RAM) 602, a read only memory (ROM) 603, a storage unit 604, an input unit 605, a display unit 606, and communication. And an interface 609.

The CPU 601 executes a program stored in the ROM 603 while using the RAM 602 as a work area. The storage unit 604 stores data created by the CPU 601. The input unit 605 receives input from the worker. The display unit 606 displays characters and images. The communication interface 609 performs communication with other devices.

FIG. 2 is a diagram showing a configuration of a control system using the system design support tool according to the first embodiment of the present invention.

The control system 1 is configured by connecting

control devices

2, 3, and 4 and a system design support device 5 through a network N.

Each of the

control devices

2, 3 and 4 controls the controlled device by executing a control program. The

control devices

2, 3 and 4 are exemplified by programmable controllers. The controlled device is exemplified by an industrial machine.

Each of the

control devices

2, 3 and 4 includes a CPU and a memory. The memory is exemplified by a RAM. Part of the memory is used for the shared memory area, and the other part of the memory is used for the local memory area. Each access unit in the shared memory area is called a link device. Data written to a certain link device in a certain control device is transferred to the link device having the same address in all other control devices. This realizes data sharing among all the control devices. The link device is used to link data between a plurality of control programs that are a plurality of applications respectively executed by the

control devices

2, 3, and 4.

When a control program is created, each link device is described using a system label that is an identifier for uniquely identifying each link device, not an address. This facilitates creation of the control program and improves the readability of the control program. Then, when the control program is compiled and the object code is created, the system label is replaced with the address.

The control device 2 is set to “1” as a station number that uniquely identifies the control device 2. The control device 2 is a management station that manages the

control devices

3 and 4. In the control device 3, “2” is set as the station number that uniquely identifies the control device 3. The control device 3 is a normal station managed by the control device 2. In the control device 4, “3” is set as a station number that uniquely identifies the control device 4. The control device 4 is a normal station managed by the control device 2. In the network N, “1” is set in the network number that uniquely identifies the network N.

The system design support apparatus 5 is a plurality of identifiers used to describe a plurality of link devices set in a shared memory space for the

control apparatuses

2, 3 and 4 to share data in the control program. A system design support tool 6 for generating a system label list having the system labels and a storage unit 604. The system design support apparatus 5 is exemplified by a personal computer.

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

The system design support tool 6 shows a network configuration of the

control devices

2, 3, and 4, and creates a system configuration diagram creation unit that creates a system configuration diagram 30 including a station number that uniquely identifies each of the

control devices

2, 3, and 4. 10 and a project creation unit 11 that creates

projects

31a, 31b, and 31c having control programs for controlling controlled devices and information referred to when the control programs are executed or compiled. Each of the

projects

31a, 31b, and 31c includes a station number of the

control device

2, 3 or 4 and execution data referred to when the object code of the control program is executed.

Information referred to at the time of execution or compilation of the control program includes parameters, device memory that defines a work memory area, and connection information that describes the connection between a plurality of terminals of the

control devices

2, 3, and 4 and the industrial machine. Illustrated.

In addition, the system design support tool 6 includes the project allocation unit 12 that allocates the

projects

31a, 31b, and 31c to the control devices in the system configuration diagram 30, the station number, and each of the plurality of

control devices

2, 3, and 4. A network range assignment information creating unit 13 for creating network range assignment information 32 having items of a head address and a final address of a link device, which are areas in the shared memory space in which data is written.

Further, the system design support tool 6 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b and 31c with the station number as a key, and a system label which is an identifier for uniquely identifying the link device, and The system label list creating unit 14 creates a system label list 33 having a device name item for uniquely specifying a link device.

Further, the system design support tool 6 follows the change of the network range assignment information duplication determination unit 15 for determining whether or not the address ranges of the plurality of records of the network range assignment information overlap, and the change in the system configuration diagram 30. The first system label list changing unit 16 that changes the system label list 33 and the second system label list changing unit 17 that changes the system label list 33 following the change of the network range allocation information.

Further, the system design support tool 6 calculates a usable network range from the system labeling target selection unit 18 that accepts selection of a target area for creating a system label in the shared memory space from the user and the system configuration diagram 30. A network range allocation calculation reflection unit 19 that reflects the network range allocation information 32.

The storage unit 604 includes a system configuration diagram 30 created by the system configuration diagram creation unit 10,

projects

31 a, 31 b and 31 created by the project creation unit 11, and a network range created by the network range assignment information creation unit 13. The allocation information 32 and the system label list 33 created by the system label list creation unit 14 are stored. The storage unit 604 is exemplified by an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

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

FIG. 4 is a diagram illustrating a system configuration diagram according to the first embodiment. In creating the system configuration diagram 30, first, the system configuration diagram creation unit 10 arranges

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 station number “2” is set. The object 30c corresponds to the control device 4, and the station number “3” is set. Next, the system configuration diagram creation unit 10 arranges an object 30d that connects 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 information describing the network configuration of the control system 1.

Referring to FIG. 3 again, in step S102, the project creation unit 11 creates the

projects

31a, 31b and 31c of the

control devices

2, 3 and 4, and the project allocation unit 12 creates the

projects

31a, 31b and 31c. Allocation to the

objects

30a, 30b and 30c is performed.

FIG. 5 is a diagram showing a system configuration diagram according to the first embodiment. The project assignment unit 12 assigns the object 30e to the object 30a corresponding to the control device 2 based on the operation input of the operator. The object 30e corresponds to the project 31a, and the project name “prj01” is set. The project assignment unit 12 assigns the object 30f to the object 30b corresponding to the control device 3 based on the operation input of the operator. The object 30f corresponds to the project 31b, and the project name “prj02” is set. The project assignment unit 12 assigns the object 30g to the object 30c corresponding to the control device 4 based on the operation input of the operator. The object 30g corresponds to the project 31c, and the project name “prj03” is set.

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

FIG. 6 is a diagram of the network range allocation information according to the first embodiment. The network range allocation information 32 includes items of a station number and a head address and a last address of a link device that is an area in the shared memory space where each of the

control devices

2, 3 and 4 writes data.

The worker inputs the station number, the head address of the link device, and the last address in each item of the network range assignment information 32. In the network range allocation information 32, the station number “1”, the head address “0x0000”, and the last address “0x000F” of the control device 2 are input to the first row 32a. In the second row 32b, the station number “2”, the head address “0x0010”, and the last address “0x001F” of the control device 3 are input. Further, the station number “3”, the head address “0x0020”, and the last address “0x002F” of the control device 4 are input to the third row 32c.

Therefore, the link device to which the control device 2 with the station number “1” writes data is 16 bytes from the head address “0x0000” to the last address “0x000F”. The link device to which the control device 3 with the station number “2” writes data is 16 bytes from the head address “0x0010” to the last address “0x001F”. The link device to which the control device 4 with the station number “3” writes data is 16 bytes from the head address “0x0020” to the last address “0x002F”.

Referring to FIG. 3 again, in step S106, the system label list creation unit 14 collates the system configuration diagram 30, the network range assignment information 32, and the

projects

31a, 31b, and 31c with the station number as a key, thereby obtaining the system label. A list 33 is created.

FIG. 7 is a diagram showing a system label list according to the first embodiment. The system label list 33 includes items of a system label that is an identifier for uniquely identifying a link device, a CPU name built in the control apparatus, and a device name for uniquely identifying the link device. The system label list 33 may supplementarily include the project name of the project, but the project name is not an essential item 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 writes data. In each of the plurality of rows 33a, the system label list creation unit 14 creates and arranges system labels, which are identifiers that uniquely identify each link device, in the system label item according to a predetermined generation rule.

In the first embodiment, a predetermined generation rule includes a character string “activation_”, a station number of a control device that writes data to the link device, a character string “switch of station”, and the control device. Is a rule for combining the serial number of the link device to which data is written.

In the system label list 33, in the item of the system label in the first row of the plurality of rows 33a, the “start_1 station switch 1” generated by the system label list creation unit 14 is arranged. Further, in the item of the system label in the last line of the plurality of lines 33a, the “activation_1 station switch 16” generated by the system label list creation unit 14 is arranged.

Further, the system label list creation unit 14 arranges the CPU name “CPU01” built in the control device 2 in the item of CPU name in each of the plurality of rows 33a. Further, the system label list creation unit 14 arranges a device name for uniquely identifying each link device in the device name item in each of the plurality of rows 33a.

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. In each of the plurality of rows 33b, the system label list creation unit 14 creates and arranges system labels, which are identifiers that uniquely specify each link device, in accordance with a predetermined generation rule.

In the system label list 33, in the item of the system label in the first row of the plurality of rows 33b, “switch 1 of startup_2 station” generated by the system label list creation unit 14 is arranged. In addition, in the item of the system label in the last row of the plurality of rows 33b, the “start_2 station switch 16” generated by the system label list creation unit 14 is arranged.

Also, the system label list creation unit 14 arranges the CPU name “CPU02” built in the control device 3 in the item of CPU name in each of the plurality of rows 33b. Further, the system label list creation unit 14 arranges a device name that uniquely identifies each link device in the item of device name in each of the plurality of rows 33b.

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 writes data. In each of the plurality of rows 33c, the system label list creation unit 14 creates and arranges system labels, which are identifiers that uniquely identify each link device, in the system label item according to a predetermined generation rule.

In the system label list 33, “start_3 station switch 1” generated by the system label list creation unit 14 is arranged in the system label item of the first row of the plurality of rows 33c. In addition, in the item of the system label in the last row of the plurality of rows 33c, the “start_3 station switch 16” generated by the system label list creation unit 14 is arranged.

Further, the system label list creation unit 14 arranges the CPU name “CPU03” built in the control device 4 in the item of CPU name in each of the plurality of rows 33c. Further, the system label list creation unit 14 arranges a device name that uniquely identifies each link device in the device name item in each of the plurality of rows 33c.

As described above, according to the system design support tool 6, the system label list creation unit 14 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key, and the system A label list 33 can be created. Thereby, since it becomes unnecessary for an operator to input each item of the system label list 33, it is possible to prevent an input error from occurring in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

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. Thereby, since an operator cannot change each item of the system label list 33, it can suppress that a change mistake occurs in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

FIG. 8 is a flowchart showing the system label changing operation of the system design support tool according to the first embodiment. Here, a case where the control device 4 with the station number “3” is replaced with a new control device with the station number “4” will be described 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 corresponds to the object 30c corresponding to the control device 4 with the station number “3” shown in FIG. 3 to the new control device with the station number “4”. To the object 30h to be replaced.

FIG. 9 is a diagram showing a system configuration diagram according to the first embodiment. In the system configuration diagram 30, 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 project allocation unit 12 changes the allocation of the project 31c to the object 30h.

FIG. 10 is a diagram showing a system configuration diagram according to the first embodiment. The project assignment unit 12 assigns the object 30g to the object 30h corresponding to the new control device having the station number “4” based on the operation input of the operator. The object 30g corresponds to the project 31c.

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

FIG. 11 is a diagram of network range allocation information according to the first embodiment. The operator inputs to change the station number in the third row 32c of the network range assignment information 32 from “3” to “4”.

Referring to FIG. 8 again, in step S116, the network range assignment information duplication determination unit 15 checks the duplication of the network range assignment information 32. Specifically, the network range assignment information duplication determination unit 15 checks whether there is no duplication in the address range of each row of the network range assignment information 32.

Next, in step S118, the first system label list changing unit 16 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key, whereby the system label list 33 Make changes.

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 rows 33d are changed, and the other plurality of rows are not changed.

Each of the plurality of rows 33d of the system label list 33 corresponds to each byte of the link device to which the new control device having the station number “4” writes data. The first system label list changing unit 16 creates a system label, which is an identifier for uniquely identifying each link device, in each of the plurality of rows 33d according to a predetermined generation rule, and arranges the system label. To do.

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

Further, the first system label list changing unit 16 sets the CPU name “CPU04” incorporated in the new control device having the station number “4” in the item of CPU name in each of the plurality of rows 33d. Deploy.

As described above, according to the system design support tool 6, the first system label list changing unit 16 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b and 31c with the station number as a key. The system label list 33 can be changed. Thereby, since it becomes unnecessary for an operator to change each item of the system label list 33, it is possible to suppress occurrence of a change mistake in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

In the above description, the control device 4 having the station number “3” has been replaced with a new control device having the station number “4”. The flowchart of FIG. 8 will be described by taking as an example the case where the number of link devices increases or decreases.

When the number of link devices increases or decreases, the system configuration is not changed, and therefore the system configuration diagram creation unit 10 does not change the system configuration diagram 30 in step S110. If there is no change in the system configuration, step S110 may be skipped.

When the number of link devices is increased or decreased, the system configuration is not changed. Therefore, in step S112, the project allocation unit 12 does not change the allocation of the

projects

31a, 31b, and 31c to the

objects

30a, 30b, and 30c. If there is no change in the system configuration, step S112 may be skipped.

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

FIG. 13 is a diagram of network range allocation information according to the first embodiment. In the network range assignment information 32, the worker inputs “0x0010” in the item of the last address in the first row 32a. As a result, the link device to which the control device 2 with the station number “1” writes data is expanded to 17 bytes from the head address “0x0000” to the last address “0x0010”.

In addition, in the network range assignment information 32, the operator inputs “0x0011” in the item of the top address of the second row 32b. In addition, in the network range allocation information 32, the worker inputs “0x001F” in the item of the final address in the second row 32b. As a result, the link device to which the control device 3 with the station number “2” writes data is reduced to 15 bytes from the head address “0x0011” to the last address “0x001F”.

In addition, in the network range assignment information 32, the worker inputs “0x0020” in the item of the top address of the third row 32c. In addition, in the network range allocation information 32, the worker inputs “0x002E” in the item of the final address in the third row 32c. As a result, the link device to which the control device 4 with the station number “3” writes data is reduced to 15 bytes from the head address “0x0020” to the last address “0x002E”.

Referring to FIG. 8 again, in step S118, the second system label list changing unit 17 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key. The system label list 33 is changed.

FIG. 14 is a diagram showing a system label list according to the first embodiment. As the link device of the control device 2 whose station number is “1” is expanded to 17 bytes, a line 33e is added to the system label list 33 shown in FIG.

Further, as the link device of the control device 3 with the station number “2” is reduced to 15 bytes, a strikethrough is added to the row 33f in the system label list 33 shown in FIG. Note that the second system label list changing unit 17 may delete the row 33f.

Further, as the link device of the control device 4 with the station number “3” is reduced to 15 bytes, a strikethrough is added to the row 33g in the system label list 33 shown in FIG. The second system label list changing unit 17 may delete the row 33g.

As described above, according to the system design support tool 6, the second system label list changing unit 17 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key. The system label list 33 can be changed. Thereby, since it becomes unnecessary for an operator to change each item of the system label list 33, it is possible to suppress occurrence of a change mistake in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

Also, the system design support tool 6 allows the operator to select a system labeling target from all link devices.

FIG. 15 is a flowchart of the system label creation operation of the system design support tool according to the first embodiment. In the flowchart of FIG. 15, steps S100, S102, S104, and S106 are the same as the flowchart shown in 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 all the link devices based on the operation input of the operator. The operator can select a system labeling target by selecting a necessary address range from the address ranges described in the network range allocation information 32. Further, the operator can select a system labeling target by selecting a necessary object from the objects arranged in the system configuration diagram 30.

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 all link devices based on the operation input of the operator. Thereby, the system design support tool 6 can create the system label list 33 including 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.

The system design support tool 6 can also calculate a network range, that is, an address range that can be used for the link device. For example, in addition to the

control devices

2, 3, and 4, a device may be connected to the control system 1 via a network. The other device is exemplified by a display device that can display various information of the

control devices

2, 3, and 4. When another device is connected to the network, the address used in the display device cannot be used as the address of the link device.

FIG. 16 is a flowchart of the system label creation operation of the system design support tool according to the first embodiment. In the flowchart of FIG. 16, steps S100, S102, S104, and S106 are the same as the flowchart shown in FIG.

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 a network range that can be used for the link device, that is, an address range, 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 worker can input items to the network range assignment information 32 in step S104 while referring to the address range reflected in the network range assignment 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 network range, that is, the address range that can be used for the link device, based on the information describing the network configuration in the system configuration diagram 30. And reflected in the network range allocation information 32. Thereby, the system design support tool 6 can suppress an address conflict between the link device and another device. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

Next, a comparative example of the present invention will be described.

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

The control system 51 is configured by connecting

control devices

52, 53 and 54 and a system design support device 55 via a network N1.

Each of the

control devices

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

The control device 52 is set to “1” as a station number that uniquely identifies the control device 52. The control device 52 is a management station that manages the control devices 53 and 54. In the control device 53, “2” is set in the station number that uniquely identifies the control device 53. The control device 53 is a normal station managed by the control device 52. In the control device 54, “3” is set as a station number that uniquely identifies the control device 54. The control device 54 is a normal station managed by the control device 52. In the network N1, “1” is set in the network number that uniquely identifies the network N1.

The system design support device 55 includes a programming tool unit 56, a spreadsheet 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 the programming tool program. The spreadsheet unit 57 is realized by the CPU in the system design support device 55 executing a spreadsheet program.

The storage unit 58 stores the

projects

61, 62, and 63 created by the programming tool unit 56 and the system label information 70 created by the spreadsheet unit 57.

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

First, the programming tool unit 56 creates network range allocation information 61a in the project 61 allocated to the control device 52, which is a management station, based on the operator's input. The

projects

62 and 63 allocated to the control devices 53 and 54, which are normal stations, do not include network range allocation information.

FIG. 18 is a diagram showing network range allocation information in the project according to the comparative example. In the project 61, “prj01” is set as a project name for uniquely identifying the project 61. The network range allocation information 61a includes items of a station number and a head address and a final address of a link device that is an area in the shared memory space where each of the

control devices

52, 53, and 54 writes data.

The worker inputs the station number, the head address of the link device, and the last address in each item of the network range assignment information 61a. In the network range allocation information 61a, the station number “1”, the head address “0x0000”, and the last address “0x000F” of the control device 52 are input to the first row 61a1. In the second row 61a2, the station number “2”, the head address “0x0010”, and the last address “0x001F” of the control device 53 are input. Further, the station number “3”, the head address “0x0020”, and the last address “0x002F” of the control device 54 are input to the third row 61a3.

Therefore, the link device to which the control device 52 with the station number “1” writes data is 16 bytes from the head address “0x0000” to the last address “0x000F”. The link device to which the control device 53 with the station number “2” writes data is 16 bytes from the head address “0x0010” to the last address “0x001F”. The link device to which the control device 54 with the station number “3” writes data is 16 bytes from the head address “0x0020” to the last address “0x002F”.

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

FIG. 19 is a diagram showing system label information according to the comparative example. The system label information 70 includes items of a system label that is an identifier for uniquely identifying the link device, a CPU name built in the control device, and a device name for uniquely identifying the link device. The system label information 70 may additionally include the project name of the project, but the project name is not an essential 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 writes data. In each of the plurality of rows 70a, the worker inputs a system label, which is an identifier for uniquely identifying each link device, in the system label item.

In the system label information 70, “Activation_1 Station Switch 1” is input by the operator to the system label item in the first row of the plurality of rows 70 a. In addition, in the item of the system label in the last row of the plurality of rows 70a, the operator inputs “switch 16 of startup_1 station”.

In addition, the worker inputs the CPU name “CPU01” built in the control device 52 to the item of CPU name in each of the plurality of rows 70a. In addition, in each of the plurality of rows 70a, the worker inputs a device name that uniquely identifies each link device in the device name item.

In the system label information 70, each of the plurality of rows 70b corresponds to each byte of the link device to which the control device 53 writes data. In each of the plurality of rows 70b, the operator inputs a system label that is an identifier for uniquely identifying each link device in the item of system label.

In the system label information 70, “Activation_2 Station Switch 1” is input by the operator to the system label item in the first row of the plurality of rows 70 b. In addition, in the item of the system label in the last row of the plurality of rows 70b, the operator inputs “switch 2 of startup_2 station”.

Further, the worker inputs the CPU name “CPU02” built in the control device 53 to the item of CPU name in each of the plurality of rows 70b. In addition, in each of the plurality of rows 70b, the worker inputs a device name that uniquely identifies each link device in the device name item.

In the system label information 70, each of the plurality of rows 70c corresponds to each byte of the link device to which the control device 54 writes data. In each of the plurality of rows 70c, the worker inputs a system label that is an identifier for uniquely specifying each link device in the item of system label.

In the system label information 70, the “start_3 station switch 1” is input by the operator to the system label item in the first row of the plurality of rows 70c. In addition, in the system label item in the last row of the plurality of rows 70c, the operator has input “Start_3 Station Switch 16”.

Further, the worker inputs the CPU name “CPU03” built in the control device 54 to the item of CPU name in each of the plurality of rows 70c. In addition, in each of the plurality of rows 70c, the worker inputs a device name that uniquely identifies each link device in the device name item.

Next, the programming tool unit 56 creates system label lists 61b, 62b and 63b in the

projects

61, 62 and 63 based on the input of the operator. The worker creates the system label lists 61b, 62b, and 63b while referring to the system label information 70 created by the spreadsheet unit 57.

FIG. 20 is a diagram showing a system label list in the project according to the comparative example. The system label list 61b has items of a system label, a CPU name, and a device name. The system label list 61b may supplementarily include the project name of the project, but the project name is not an essential item of the system label list 61b. The worker inputs the value of each item in the system label list 61b while referring to the plurality of rows 70a in the system label information 70 created by the spreadsheet unit 57.

FIG. 21 is a diagram showing a system label list in the project according to the comparative example. The system label list 62b has items of a system label, a CPU name, and a device name. The system label list 62b may supplementarily include the project name of the project, but the project name is not an essential item of the system label list 62b. The worker inputs the value of each item in the system label list 62b while referring to the plurality of rows 70b in the system label information 70 created by the spreadsheet unit 57.

FIG. 22 is a diagram showing a system label list in the project according to the comparative example. The system label list 63b has items of a system label, a CPU name, and a device name. The system label list 63b may supplementarily include the project name of the project, but the project name is not an essential item of the system label list 63b. The worker inputs the value of each item in the system label list 63b while referring to the plurality of rows 70c in the system label information 70 created by the spreadsheet unit 57.

As described above, in the comparative example, the worker inputs all items of the system label information 70 and the system label lists 61b, 62b, and 63b. Therefore, input mistakes are likely to 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 control program in the

projects

61, 62, and 63 may perform an unexpected operation, and thus the controlled device may perform an unexpected operation. there were.

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

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

FIG. 23 is a diagram showing network range allocation information in the project according to the comparative example. The operator changes the final address of the first row 61a1 of the network range allocation information 61a from “0x000F” to “0x0010”. Therefore, the link device to which the control device 52 with the station number “1” writes data is 17 bytes from the head address “0x0000” to the last address “0x0010”.

Next, the worker changes the head address of the second row 61a2 of the network range allocation information 61a from “0x0010” to “0x0011”. Accordingly, the link device to which the control device 53 with the station number “2” writes data is 15 bytes from the head address “0x0011” to the last address “0x001F”.

Next, the worker 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 with the station number “3” writes data is 15 bytes from the head address “0x0020” to the last address “0x002E”.

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

FIG. 24 is a diagram showing system label information according to the comparative example. The operator adds a row 70d when the link device to which the control device 52 writes data is changed from 16 bytes to 17 bytes. In the item of the system label in the row 70d, the operator inputs “switch 1 of startup_1 station”. Further, “CPU01” is input by the operator to the item of CPU name in the row 70d. In the device name item in the row 70d, “J1 ¥ B10” is input by the operator.

Further, the operator adds a strike-through line to the row 70e when the link device to which the control device 53 writes data is changed from 16 bytes to 15 bytes. The worker may delete the row 70e.

Also, the operator adds a strikethrough to the row 70f when the link device to which the control device 54 writes data is changed from 16 bytes to 15 bytes. The worker may delete the row 70f.

Next, the programming tool unit 56 changes the system label lists 61b, 62b, and 63b in the

projects

61, 62, and 63 based on the operator's input. The worker changes the system label lists 61b, 62b, and 63b while referring to the system label information 70 created by the spreadsheet unit 57.

FIG. 25 is a diagram showing a system label list in the project according to the comparative example. The worker adds a row 61b1 to the system label list 61b in accordance with the addition of the row 70d to the system label information 70 by the spreadsheet 57.

FIG. 26 is a diagram showing a system label list in the project according to the comparative example. The worker adds a strike-through line to the row 62b1 of the system label list 62b when the strike-through line is added to the row 70e of the system label information 70 by the spreadsheet section 57. The worker may delete the row 62b1.

FIG. 27 is a diagram showing a system label list in the project according to the comparative example. The operator adds a strike-through line to the row 63b1 of the system label list 63b in accordance with the strike-through line being added to the row 70f of the system label information 70 by the spreadsheet 57. Note that the operator may delete the 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, it is easy for mistakes to occur in the system label information 70 and the system label lists 61b, 62b, and 63b. If there is a change mistake in the system label information 70 and the system label lists 61b, 62b, and 63b, the control program in the

projects

On the other hand, according to the system design support tool 6 according to the first embodiment, the system label list creating unit 14 compares the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key. Then, the system label list 33 can be created. Thereby, since it becomes unnecessary for an operator to input each item of the system label list 33, it is possible to prevent an input error from occurring in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

Further, according to the system design support tool 6, the first system label list changing unit 16 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b, and 31c with the station number as a key, and the system label The list 33 can be changed. Thereby, since it becomes unnecessary for an operator to change each item of the system label list 33, it is possible to suppress occurrence of a change mistake in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

Further, according to the system design support tool 6, the second system label list changing unit 17 collates the system configuration diagram 30, the network range allocation information 32, and the

projects

31a, 31b and 31c with the station number as a key, and the system label The list 33 can be changed. Thereby, since it becomes unnecessary for an operator to change each item of the system label list 33, it is possible to suppress occurrence of a change mistake in the system label list 33. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

Further, according to the system design support tool 6, the system labeling target selection unit 18 can select a system labeling target from all the link devices based on the operation input of the operator. Thereby, the system design support tool 6 can create the system label list 33 including 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.

Further, according to the system design support tool 6, the network range allocation calculation reflection unit 19 calculates the network range, that is, the address range that can be used for the link device based on the information describing the network configuration in the system configuration diagram 30, and the network This is reflected in the range assignment information 32. Thereby, the system design support tool 6 can suppress an address conflict between the link device and another device. Therefore, the system design support tool 6 can suppress the possibility that the control program will perform an unexpected operation, and can suppress the possibility that the controlled apparatus will perform an unexpected operation.

The configuration described in the above embodiment shows an example of the contents of the present invention, and can be combined with another known technique, and can be combined with other configurations without departing from the gist of the present invention. It is also possible to omit or change the part.

1 control system, 2, 3, 4 control device, 5 system design support device, 6 system design support tool, 10 system configuration diagram creation unit, 11 project creation unit, 12 project allocation unit, 13 network range allocation information creation unit, 14 System label list creation unit, 15 network range assignment information duplication determination unit, 16 first system label list change unit, 17 second system label list change unit, 18 system label target selection unit, 19 network range assignment calculation reflection unit, 30 System configuration diagram, 31a, 31b, 31c project, 32 network range allocation information, 33 system label list, 601 CPU, 604 storage unit.

Claims

In a control system in which a plurality of control devices are connected to a network, the plurality of control devices are used to describe a plurality of link devices set in a shared memory space for sharing data in a control program. A system design support tool for generating a system label list having a plurality of system labels as identifiers,
A system configuration diagram creating unit for creating a system configuration diagram showing a network configuration of the plurality of control devices and including a station number for uniquely identifying each of the plurality of control devices;
A project allocation unit for allocating a control program for controlling a controlled device and a plurality of projects each having information referred to at the time of execution or compilation of the control program to the plurality of control devices in the system configuration diagram; ,
A network range assignment information creating unit for creating network range assignment information having items of the station number and the start address and end address of the area in the shared memory space where each of the plurality of control devices writes data When,
The system configuration diagram, the network range allocation information, and the plurality of projects are collated using the station number as a key, and the system label that is an identifier that uniquely identifies the link device and the device that uniquely identifies the link device A system label creation unit for creating a system label list having a name item;
A system design support tool characterized by comprising:
The system design support tool according to claim 1, further comprising a system label list changing unit that changes the system label list following the change in the system configuration diagram.
The system design support tool according to claim 1, further comprising a system label list changing unit that changes the system label list following the change of the network range assignment information.
The system label list changing unit creates a new system label based on an increase / decrease in the allocation range of the network range allocation information, and a portion decreased in the allocation range is the system label. The system design support tool according to claim 3, wherein the system design support tool is deleted.
The system design support tool according to claim 1, further comprising a network range assignment information duplication determination unit for judging whether or not address ranges of a plurality of records of the network range assignment information overlap.
The system design support tool according to claim 1, further comprising a system labeling target selection unit that receives a selection of a target area for generating a system label in the shared memory space from a user.
The system design support tool according to claim 1, further comprising a network range allocation calculation reflection unit that calculates a usable network range from the system configuration diagram and reflects the calculated network range in network range allocation information.