KR20180004825A - Debug device, debug method, and debug program - Google Patents

Debug device, debug method, and debug program Download PDF

Info

Publication number
KR20180004825A
KR20180004825A KR1020177036513A KR20177036513A KR20180004825A KR 20180004825 A KR20180004825 A KR 20180004825A KR 1020177036513 A KR1020177036513 A KR 1020177036513A KR 20177036513 A KR20177036513 A KR 20177036513A KR 20180004825 A KR20180004825 A KR 20180004825A
Authority
KR
South Korea
Prior art keywords
data
quot
dependency
name
unit
Prior art date
Application number
KR1020177036513A
Other languages
Korean (ko)
Other versions
KR101864565B1 (en
Inventor
유키 시미즈
Original Assignee
미쓰비시덴키 가부시키가이샤
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 미쓰비시덴키 가부시키가이샤 filed Critical 미쓰비시덴키 가부시키가이샤
Publication of KR20180004825A publication Critical patent/KR20180004825A/en
Application granted granted Critical
Publication of KR101864565B1 publication Critical patent/KR101864565B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software

Abstract

It is an object of the present invention to provide a debug apparatus which can easily grasp a dependency relationship between devices. The debug apparatus of the present invention stores the project data 24a including the control program executed by the control apparatus and the device memory which is data in which a prescribed technique for defining a plurality of devices as a plurality of work areas in the memory of the control apparatus is made A dependence data creation unit 21a2a for creating dependence data 24c indicating a dependency relationship between a plurality of devices described in the control program and storing the dependency data 24c in the storage unit, And drawing sections (21a2b, 21a2c) for displaying, on the display section, an image representing the dependence relationship of the plurality of devices on the basis of the dependent data.

Description

Debug device, debug method, and debug program

The present invention relates to a debug apparatus, a debug method, and a debug program for performing debugging of a control program executed by a control apparatus for controlling an industrial machine.

A control program executed by a control device for controlling an industrial machine accesses a plurality of devices which are a plurality of work areas in a memory of the control device. The control program writes data to another device in accordance with data of a certain device. That is, there is a dependency between the devices.

Conventionally, when debugging a control program, a user has to open a control program with a program editor and trace a dependency between the devices

However, there are cases where the first device depends on the second device, and the second device depends on the third device. In some cases, the fourth and fifth devices depend on the sixth device. In such a case, the user needs to open the control program with a plurality of program editors to find the dependency between the devices. Therefore, it is difficult for the user to grasp the dependence relationship between the devices, and the number of debug processes increases, and it is difficult to solve the trouble early.

As a related art, Patent Document 1 described below discloses a programming device that allows a plurality of control program languages to be mixedly displayed and compiles a mixed control program language (paragraphs 0092 to 0180 and figures 1 to 7).

Patent Document 1: Japanese Patent Application Laid-Open No. 2001-22412

However, the technique described in Patent Document 1 does not describe that it is easy to grasp the dependency relationship between the devices.

SUMMARY OF THE INVENTION The present invention has been made in view of the above, and an object of the present invention is to obtain a debug apparatus which can easily grasp a dependency relationship between devices.

In order to solve the above-mentioned problems and to achieve the object, the present invention provides a device memory, which is data in which a description (description) for specifying a plurality of devices, which are a plurality of work areas in a memory of a control program and control device, A dependence data creation unit for creating dependence data representing a dependency relationship between a plurality of devices described in the control program and storing the dependency data in a storage unit; And a drawing unit for displaying an image representing a dependency of a plurality of devices on the display unit based on the dependency data.

The debug apparatus according to the present invention achieves the effect that it is easy to grasp the dependency relationship between the devices.

1 is a diagram showing a configuration of a control system according to a first embodiment.
2 is a diagram showing the hardware configuration of the control apparatus according to the first embodiment.
3 is a diagram showing an example of label information according to the first embodiment.
4 is a diagram showing an example of a control program according to the first embodiment.
5 is a diagram showing a hardware configuration of the engineering tool according to the first embodiment.
6 is a functional block diagram of the engineering tool according to the first embodiment.
7 is a diagram showing an example of symbol data according to the first embodiment.
8 is a flowchart showing the processing of the engineering tool according to the first embodiment.
9 is a diagram showing an example of the dependency data according to the first embodiment.
10 is a flowchart showing the processing of the engineering tool according to the first embodiment.
11 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.
12 is a flowchart showing the processing of the engineering tool according to the first embodiment.
13 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.
14 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.
15 is a flowchart showing the processing of the engineering tool according to the first embodiment.
16 is a flowchart showing the processing of the engineering tool according to the first embodiment.
17 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.
18 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.
19 is a diagram showing a configuration of a control system according to the second embodiment.
20 is a functional block diagram of the engineering tool according to the second embodiment.
21 is a diagram showing an example of a control program according to the second embodiment.
22 is a diagram showing an example of a control program according to the second embodiment.
23 is a flowchart showing the processing of the engineering tool according to the second embodiment.
24 is a diagram showing an example of the dependency data according to the second embodiment.
25 is a diagram showing an example of the dependency data according to the second embodiment.

Hereinafter, a debug apparatus, a debug method, and a debug program according to an embodiment of the present invention will be described in detail with reference to the drawings. The present invention is not limited to these embodiments.

Embodiment 1

1 is a diagram showing a configuration of a control system according to a first embodiment. The control system (1) includes an engineering tool (2) and a control device (3). The engineering tool 2 and the control apparatus 3 are communicably connected via the network N1.

The engineering tool 2 creates project data including a control program executed by the control device 3 and transmits it to the control device 3. [ The control device 3 controls the machine by executing the control program included in the project data. The control device 3 is a programmable controller (JIS B 3502: 2011, programmable controllers (PLC)).

2 is a diagram showing the hardware configuration of the control apparatus according to the first embodiment. The control device 3 includes a main substrate 3a and a sub-substrate 3b.

The main board 3a includes a CPU (Central Processing Unit) 3a1, a memory 3a2 as a RAM (Random Access Memory), a communication interface 3a3, a bus interface 3a4, and a storage unit 3a5 . The CPU 3a1, the memory 3a2, the communication interface 3a3, the bus interface 3a4, and the storage unit 3a5 are connected via the internal bus B1.

The communication interface 3a3 communicates with the engineering tool 2.

The bus interface 3a4 is a bus bridge circuit that connects the internal bus B1 and the expansion bus B2. The sub board 3b is connected to the main board 3a via the expansion bus B2. The sub-board 3b is connected to the machine 4. [

The storage unit 3a5, and the project data 24a received from the engineering tool 2. [ An SSD (Solid State Drive) or an HDD (Hard Disk Drive) is exemplified as the storage unit 3a5.

The project data 24a includes a control program 24a1, a control parameter 24a2 referred to at the time of execution of the control program 24a1, and a technique for defining a plurality of devices as a plurality of work areas in the memory 3a2 Connection information 24a4 for specifying the connection relationship between the sub-substrate 3b and the machine 4 and device name as a name of each device and an alias name given to each device by the user And label information 24a5 associated with the label name.

Although the control program 24a1 is described in a ladder language (IEC 61131-3, JIS B 3503: 2012) in the first embodiment, the control program 24a1 is limited to being described in a ladder language It does not. In another language in which the control program 24a1 is described, a structured ladder language or a function block diagram (IEC 61131-3, JIS B 3503: 2012, Function Block Diagram (FBD)) language is exemplified.

In the memory 3a2, a plurality of devices defined by the device memory 24a3 are secured. The device name is systematically assigned by the manufacturer of the control device 3. [ In Embodiment 1, each of a plurality of devices in the memory 3a2 corresponds to a variable of the control program 24a1. In Embodiment 1, the data type of the device is a word type and a bit type.

3 is a diagram showing an example of label information according to the first embodiment. The label information 24a5 has a device name item and a label name item. &Quot; M101 " is described in the device name item of the row 71, and " B " is described in the label name item. That is, the user gives the label name " B " to the device having the device name " M101 ". The user can access the device with the device name " M101 " by describing the label name " B " in the control program 24a1.

This facilitates programming of the user and improves the readability of the control program 24a1.

4 is a diagram showing an example of a control program according to the first embodiment. The control program 24a1 includes rows 61, 62, 63 and 64. [

The row 61 includes a condition part 61A and an operation part 61b. The condition unit 61A is a load instruction for reading data of the device having the device name " X0 ". In Embodiment 1, the combination of the alphabetic character " X " and the numerical value indicates a bit type device.

The operation unit 61b is an output command for outputting data to the device having the device name " M100 ". In Embodiment 1, the combination of alphabetical letter " M " and numerical values indicates a device of bit type.

In the row 61, when the data of the device with the device name "X0" is "1", "1" is output to the device with the device name "M100". When the data of the device with the device name "X0" is "0", "0" is output to the device with the device name "M100".

That is, the device of the device name " M100 " directly relies on the device of the device name " X0 ".

The row 62 includes a condition part 62a and an operation part 62b. The condition part 62a is a load instruction for reading data of a device whose device name is " X1 ".

The operation unit 62b is an output command for outputting data to the device having the label name " B ". First, as described in the label information 24a5 shown in Fig. 3, the label name " B " is an alias assigned to the device of the device name " M101 " by the user.

In the row 62, when the data of the device having the device name "X1" is "1", "1" is output to the device having the label name "B". When the data of the device having the device name "X1" is "0", "0" is output to the device having the label name "B".

That is, the device having the label name "B" directly relies on the device having the device name "X1".

The row 63 includes condition parts 63a and 63b and an operation part 63c. The condition part 63a is a load instruction for reading data of the device having the device name " M100 ". The condition part 63b is a load command for reading data of the device having the label name " B ".

The operation unit 63c is an output instruction for outputting data to the device having the device name " Y10 ". In Embodiment 1, the combination of the alphabetical letter " Y " and numerical values indicates a device of bit type.

In the row 63, data is output to the device having the device name "Y10" according to the logical sum of the data of the device having the device name "M100" and the data of the device having the label name "B".

That is, when the data of the device having the device name "M100" is "1", "1" is outputted to the device having the device name "Y10" regardless of the data of the device having the label name "B".

When the data of the device with the label name "B" is "1", "1" is output to the device with the device name "Y10" regardless of the data of the device with the device name "M100".

When the data of the device having the device name "M100" is "0" and the data of the device having the label name "B" is "0", "0" is output to the device having the device name "Y10".

That is, the device with the device name "Y10" directly relies on the device with the device name "M100". In addition, the device with the device name "Y10" directly relies on the device with the label name "B".

The row 64 includes a condition part 64a and an operation part 64b. The condition part 64a is a load instruction for reading data of a device whose label name is " B ".

The operation unit 64b is an output command for outputting data to the device having the device name " Y11 ".

In the row 64, when the data of the device with the label name "B" is "1", "1" is output to the device with the device name "Y11". When the data of the device with the label name "B" is "0", "0" is output to the device with the device name "Y11".

That is, the device with the device name "Y11" directly relies on the device with the label name "B".

5 is a diagram showing a hardware configuration of the engineering tool according to the first embodiment. The engineering tool 2 according to the first embodiment can be realized by using a computer. The computer includes a CPU 21, a RAM 22, a ROM (Read Only Memory) 23, a storage unit 24, an input unit 25, a display unit 26, a communication interface 27 . The CPU 21, the RAM 22, the ROM 23, the storage unit 24, the input unit 25, the display unit 26 and the communication interface 27 are connected via a bus B. [

The CPU 21 executes the program stored in the ROM 23 and the storage unit 24 while using the RAM 22 as a work area. A program stored in the ROM 23 is a BIOS (Basic Input / Output System) or a UEFI (Unified Extensible Firmware Interface). Examples of the programs stored in the storage unit 24 are an operating system program and an engineering tool program. The storage unit 24 is an SSD or an HDD.

The input unit 25 accepts an operation input from the user. The input unit 25 may be a keyboard or a mouse. The display section 26 displays characters and images. The display section 26 is a liquid crystal display device. The communication interface 27 communicates with the control device 3.

6 is a functional block diagram of the engineering tool according to the first embodiment. The storage unit 24 stores the project data 24a, the symbol data 24b associating the data type of the device and the type and symbol name of the device name or label name of the device.

7 is a diagram showing an example of symbol data according to the first embodiment. The symbol data 24b has a data type item, a name type item, and a symbol item.

The bit type is described in the data type column of the row 81, the "device name" is described in the name type item, and the circle type is described in the symbol item. That is, in the row 81, a device of the bit type described by the device name indicates that a circular symbol is associated with the device.

In the data type field of the row 82, "word" is described, "name of device" is described in the name type item, and "square" is described in the symbol item. That is, the row 82 indicates that the device of the word type described by the device name is associated with a square symbol.

A "bit" is described in the data type item of the line 83, a "label name" is described in the name type item, and a triangle is described in the symbol item. That is, the line 83 indicates that the device of the bit type described by the label name is associated with the symbol of the triangle.

In the data type item of the line 84, "word" is described, "name of label" is described in the name type item, and "hexagon" is described in the symbol item. That is, the row 84 indicates that the device of the word type described by the label name is associated with the hexagonal symbol.

Referring back to Fig. 6, the CPU 21 executes the engineering tool program stored in the storage unit 24. [ Thereby, the engineering tool part 21a including the project data creation part 21a1 and the debug part 21a2 is realized.

The project data creating unit 21a1 creates the project data 24a and transmits it to the control device 3. [

The debug unit 21a2 includes a dependency data creation unit 21a2a that creates dependency data 24c indicating the dependency of a plurality of devices described in the control program 24a1 and stores the dependency data 24c in the storage unit 24. [

The debug unit 21a2 includes a first rendering unit 21a2b that displays an image representing the dependency relationship of a plurality of devices on the display unit 26 based on the dependent data 24c.

The debug unit 21a2 includes a second rendering unit 21a2c that displays a device directly dependent on the selected device on the display unit 26 based on the dependent data 24c when a device in the image is selected.

The debug unit 21a2 includes a monitoring unit 21a2d that displays an image based on the received data on the display unit 26 when receiving data of a device in the image from the control device 3. [

8 is a flowchart showing the processing of the engineering tool according to the first embodiment.

The dependent data creating unit 21a2a initially sets the variable N for controlling the loop from step S102 to step S114 to "1" in step S100.

In step S102, the dependency data creation unit 21a2a determines whether or not the flag of the Nth condition part is " 1 ". If the flag of the Nth condition part is judged to be " 1 " (Yes), the dependent data preparation section 21a2a proceeds to step S114. On the other hand, if it is determined that the flag of the Nth condition part is not "0", that is, "1" (No), the dependent data creating section 21a2a proceeds to step S104.

The dependency data creation unit 21a2a creates the dependency data 24c while scanning the device in the control program 24a1 as described later in the step S104 and thereafter sets a flag for each condition part in order to avoid duplication . The flag of the scanned conditional part is set to " 1 ". The flag may be provided in the RAM 22, in the storage unit 24, or in the control program 24a1.

In step S104, the dependent data creating unit 21a2a searches the control program 24a1 for a device directly dependent on the device described in the Nth condition part, and writes the device described in the Nth condition part and the device The dependent device is additionally described in the dependent data 24c, and the flag of the Nth condition part is set to " 1 ".

The dependency data creation unit 21a2a searches the control program 24a1 for the condition part in which the device searched in step S104 is described in step S106.

In step S108, the dependency data creation unit 21a2a determines whether or not the flag of the condition part retrieved in step S106 is " 1 ". If the flag of the condition part retrieved in step S106 is "1" (Yes), the dependent data creating section 21a2a proceeds to step S112. On the other hand, if it is determined that the flag of the conditional part retrieved in step S106 is not "0", that is, "1" (No), the dependent data creating section 21a2a proceeds to step S110.

The dependency data creation unit 21a2a additionally lists the device in the conditional part searched in step S106 and the device directly dependent on the device searched in step S106 in the dependent data 24c and sets the flag of the conditional part searched in step S106 as Quot; 1 ".

In step S112, the dependent data creating unit 21a2a determines whether there is a device directly dependent on the device directly dependent on the device in the condition part retrieved in step S106. If it is determined that there is a device directly dependent on the device directly dependent on the device in the condition part retrieved in step S106 (Yes), the dependent data creating unit 21a2a proceeds to step S106. On the other hand, if it is determined that there is no device directly dependent on the device directly dependent on the device in the condition part retrieved in step S106 (No), the dependent data creating unit 21a2a proceeds to step S114.

In step S114, the dependency data creation unit 21a2a determines whether or not the Nth condition part is the final condition part of the control program 24a1. If it is determined that the Nth condition part is not the final condition part of the control program 24a1 (No), the dependent data creation part 21a2a proceeds to step S116.

In step S116, the dependent data creating section 21a2a increments the variable N and proceeds to step S102.

On the other hand, if the Nth condition part is determined to be the final condition part of the control program 24a1 in step S114 (Yes), the dependent data creation part 21a2a ends the process.

9 is a diagram showing an example of the dependency data according to the first embodiment. Dependent data 24c includes rows 91, 92, 93 and 94.

The generation of the dependent data 24c will be described with reference to the control program 24a1 shown in Fig. 4 and the flowchart shown in Fig.

The dependent data creating unit 21a2a initially sets the variable N to "1" in step S100.

The dependency data creation unit 21a2a determines in step S102 that the flag of the Nth, that is, the first conditional part 61A is not "1" (No), and proceeds to step S104.

The dependency data creation unit 21a2a sets the device name of the device name " M100 " in the operation unit 61b directly dependent on the device of the device name " X0 " In the control program 24a1. The dependency data creation unit 21a2a further describes the dependency data 24c in the row 91 including the device name "X0" and the device name "M100".

Also, ":" in rows 91, 92, 93, and 94 is a delimiter. The device described in the left side of the drawing is a dependent destination rather than the delimeter ":", and the device described on the right side of the diagram is a dependent source than the delimiter ":".

The dependency data creation unit 21a2a searches the control program 24a1 for the condition part 63a in which the device name " M100 " searched in step S104 is described in step S106.

The dependent data creating unit 21a2a determines in step S108 that the flag of the condition part 63a retrieved in step S106 is not "1" (No), and the process proceeds to step S110.

The dependency data creation unit 21a2a includes the device name "M100" in the condition part 63a searched in step S106 and the device name "Y10" in the operation part 63c directly dependent on the device in step S110 Described in the dependent data 24c is a row 92 that is to be updated.

The dependent data creating unit 21a2a determines in step S112 that there is no device directly dependent on the device having the device name " Y10 " (No), and proceeds to step S114.

In step S114, the dependent data creating unit 21a2a determines that the Nth, that is, the first conditional part 61A is not the final conditional part (No), and proceeds to step S116.

In step S116, the dependent data creating unit 21a2a increments the variable N and proceeds to step S102.

The dependent data creating unit 21a2a determines in step S102 that the flag of the Nth, that is, the second conditional part 62a is not "1" (No), and proceeds to step S104.

The dependency data creation unit 21a2a sets the device name of the label name " B " in the operation unit 62b that directly depends on the device having the device name " X1 " in the Nth, In the control program 24a1. The dependency data creation unit 21a2a further describes the dependency data 24c in the row 93 including the device name "X1" and the label name "B".

The dependency data creation unit 21a2a searches the control program 24a1 for the condition parts 63b and 64a in which the label name " B " searched in step S104 is described in step S106.

The dependent data creating unit 21a2a determines in step S108 that the flag of the condition parts 63b and 64b retrieved in step S106 is not "1" (No), and the process proceeds to step S110.

The dependency data creation section 21a2a sets the label name "B" in the condition parts 63b and 64a retrieved in step S106 and the device name "Y10" in the operation section 63c directly dependent on the device in step S110 And a line 94 including the device name " Y11 " in the operating section 64b are additionally written in the dependent data 24c.

The dependent data creating unit 21a2a determines in step S112 that there is no device directly dependent on the device having the device name "Y10" or "Y11" (No), and the process proceeds to step S114.

In step S114, the dependent data creating unit 21a2a determines that the Nth, that is, the second conditional part 62a is not the final condition part (No), and proceeds to step S116.

In step S116, the dependent data creating unit 21a2a increments the variable N and proceeds to step S102.

In step S102, the dependency data creation unit 21a2a determines that the flag of the Nth, that is, the third conditional part 63a is "1" (Yes), and proceeds to step S114.

In step S114, the dependent data creating unit 21a2a determines that the Nth, or third, conditional part 63a is not the final condition part (No), and the process proceeds to step S116.

In step S116, the dependent data creating unit 21a2a increments the variable N and proceeds to step S102.

In step S102, the dependency data creation unit 21a2a determines that the flag of the Nth or fourth conditional part 63b is "1" (Yes), and proceeds to step S114.

In step S114, the dependent data creating unit 21a2a determines that the Nth, or fourth, conditional part 63b is not the final condition part (No), and proceeds to step S116.

In step S116, the dependent data creating unit 21a2a increments the variable N and proceeds to step S102.

The dependent data creating unit 21a2a determines in step S102 that the flag of the Nth, that is, the fifth conditional part 64a is " 1 " (Yes), and proceeds to step S114.

In step S114, the dependent data creating unit 21a2a determines that the Nth, or fifth, conditional part 64a is the final condition part (Yes), and ends the processing.

As described above, the dependency data creation section 21a2a can create the dependency data 24c indicating the dependency of the device described in the control program 24a1 by executing the process shown in the flowchart of Fig.

10 is a flowchart showing the processing of the engineering tool according to the first embodiment.

The first rendering unit 21a2b displays the symbol of the device of the dependency data 24c depending on the user or by the parameter specified by the parameter on the display unit 26 in step S200, The name or label name is displayed in the symbol. In the first embodiment, the first line of the dependent data 24c is designated.

In step S202, the first rendering unit 21a2b displays a symbol of a device directly dependent on the immediately preceding device, displays the device name or label name of the device in the symbol, and displays the symbol Indicates an oriented line indicating a dependence direction, which connects a symbol of a device and a symbol of a device directly dependent on the device.

It is also preferable that the first rendering unit 21a2b displays the symbol of the device directly dependent on the immediately preceding device on the right side of the device displayed immediately before.

The execution order direction of the control program 24a1 described in the ladder language is a direction from left to right. Accordingly, the first drawing section 21a2b displays the symbol of the device directly dependent on the immediately preceding device on the right side of the device displayed immediately before, similarly to the direction of the execution order of the control program 24a1, The dependency of the device can be grasped intuitively.

The first rendering unit 21a2b determines in step S204 whether or not there is a device directly dependent on the device displayed in step S202. If the first rendering unit 21a2b determines that there is a device directly dependent on the device displayed in step S202 (Yes), the process proceeds to step S202. On the other hand, when it is determined that there is no device directly dependent on the device displayed in step S202 (No), the first rendering unit 21a2b ends the process.

11 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.

The display screen of the engineering tool 2 will be described with reference to the dependency data 24c shown in Fig. 9 and the flowchart shown in Fig.

The first rendering unit 21a2b displays the symbol 101 of the device whose device name is "X0" in the first line of the dependent data 24c on the display unit 26 in step S200.

Also, " X0 " is a device name, and the device is a bit type. The first drawing section 21a2b refers to the row 81 of the symbol data 24b and displays the circular symbol 101 on the display section 26. [ In addition, the first rendering unit 21a2b displays the device name " X0 " in the symbol 101.

The first drawing unit 21a2b sets the symbol 102 of the device with the device name " M100 " directly to the device of the device name " X0 " Displays the device name "M100" of the device in the symbol 102 and displays the meridian line 103 connecting the symbol 101 and the symbol 102 displayed immediately before.

Further, " M100 " is a device name, and the device is a bit type. The first rendering unit 21a2b refers to the row 81 of the symbol data 24b and displays the circular symbol 102 on the display unit 26. [ In addition, the first drawing section 21a2b displays the device name " M100 " in the symbol 102. [

As a result, the user can easily grasp that the device of the device name " M100 " relies directly on the device of the device name " X0 ".

The first rendering unit 21a2b determines in step S204 whether or not there is a device directly dependent on the device of the device name " M100 " displayed in step S202.

In the row 92 of the dependency data 24c, the device of the device name "Y10" is directly dependent on the device of the device name "M100".

Therefore, the first rendering unit 21a2b determines that there is a device with the device name " Y10 " that directly relies on the device with the device name " M100 " displayed in step S202 (Yes), and proceeds to step S202 .

The first rendering unit 21a2b sets the symbol 104 of the device with the device name of "Y10" directly dependent on the device of the immediately preceding device name "M100" to the right of the symbol 102 Y10 "of the device is displayed in the symbol 104 and the meridian line 105 connecting the immediately preceding symbol 102 and the symbol 104 is displayed.

"Y10" is a device name, and the device is a bit type. The first rendering unit 21a2b refers to the row 81 of the symbol data 24b and displays the circular symbol 104 on the display unit 26. [ In addition, the first rendering unit 21a2b displays the device name " Y10 " in the symbol 104. [

Thus, the user can easily grasp that the device of the device name " Y10 " relies directly on the device of the device name " M100 ".

The first rendering unit 21a2b determines in step S204 whether or not there is a device directly dependent on the device whose device name is "Y10" displayed in step S202.

The dependency data 24c does not describe a device directly dependent on the device having the device name " Y10 ".

Therefore, the first rendering unit 21a2b determines that there is no device directly dependent on the device having the device name " Y10 " displayed in step S202 (No), and ends the process.

As described above, the first rendering unit 21a2b can display that the device of the device name " M100 " relies directly on the device of the device name " X0 ". In addition, the first rendering unit 21a2b can display that the device of the device name "Y10" directly relies on the device of the device name "M100".

Therefore, the user can easily grasp the dependency of the device. Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

12 is a flowchart showing the processing of the engineering tool according to the first embodiment.

The second rendering unit 21a2c determines in step S300 whether or not the symbol of the device displayed on the display unit 26 has been selected by the user. The symbol selection is exemplified by a double click.

If the second rendering unit 21a2c determines that the symbol of the device displayed on the display unit 26 is not selected by the user (No), the second rendering unit 21a2c waits in step S300.

If the second rendering unit 21a2c determines that the symbol of the device displayed on the display unit 26 has been selected by the user (Yes), the process proceeds to step S302.

In step S302, the second rendering unit 21a2c searches the dependent data 24c for a row containing the device name or the label name of the selected device.

The second rendering unit 21a2c displays a symbol of a device directly related to the selected device in the searched rows in step S304 and displays the symbol of the selected device in a direct dependency relationship with the device The directional line indicating the dependence direction connecting the symbols of the device is displayed, and the process is terminated.

13 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.

The display screen of the engineering tool 2 will be described with reference to the dependency data 24c shown in Fig. 9 and the flowchart shown in Fig.

The second rendering unit 21a2c determines in step S300 whether or not the symbol of the device displayed on the display unit 26 has been selected by the user.

In Embodiment 1, it is assumed that symbol 104 is selected on the display screen of Fig. 11 described earlier.

The second rendering unit 21a2c determines that the symbol 104 has been selected by the user (Yes), and proceeds to step S302.

The second rendering unit 21a2c searches the dependent data 24c for a row including the device name "Y10" of the selected symbol 104 in step S302.

In the line 94 of the dependency data 24c, it is described that the device of the device name "Y10" directly relies on the device of the label name "B".

The second rendering unit 21a2c displays the symbol 106 of the device of the label name "B" directly dependent on the device of the selected symbol 104 in step S304 and displays the selected symbol 104 Indicating a directional line 107 indicating a dependence direction, connecting the symbol 106 to which the device directly depends.

"B" is a label name, and the device is a bit type. The second drawing section 21a2c refers to the row 83 of the symbol data 24b and displays the triangle symbol 106 on the display section 26. [ In addition, the second drawing section 21a2c displays the label name " B " in the symbol 106. [

As described above, when the symbol 104 of the device with the device name " Y10 " is selected, the second drawing unit 21a2c selects the device of the label name " B " The symbol 106 of FIG.

Therefore, the user can easily grasp the dependency of the device of the device name " Y10 " and the device of the label name " B ". Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

Here, it is assumed that symbol 106 is additionally selected on the display screen of Fig.

14 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.

The second rendering unit 21a2c determines in step S300 whether or not the symbol of the device displayed on the display unit 26 has been selected by the user.

The second rendering unit 21a2c determines that the symbol 106 has been selected by the user (Yes), and proceeds to step S302.

The second rendering unit 21a2c retrieves from the dependent data 24c a row including the label name "B" of the selected symbol 106 in step S302.

In the row 93 of the dependency data 24c, it is described that the device of the label name "B" directly depends on the device of the device name "X1".

In the row 94 of the dependency data 24c, it is described that the device whose device name is "Y11" directly relies on the device with the label name "B".

The second rendering unit 21a2c displays the symbol 108 of the device with the device name " X1 " directly dependent on the device of the selected symbol 106 in step S304, Indicating a directional line 109 indicating a dependent direction, connecting the symbol 108 directly dependent on the device in question.

Also, " X1 " is a device name, and the device is a bit type. The second drawing section 21a2c refers to the row 81 of the symbol data 24b and displays the circular symbol 108 on the display section 26. [ The second rendering unit 21a2c displays the device name " X1 " in the symbol 108. [

The second rendering unit 21a2c displays the symbol 110 of the device with the device name " Y11 " directly dependent on the device of the selected symbol 106, and displays the selected symbol 106 and the device directly Which indicates the dependence direction, connecting the symbol 110 depending on the direction of the symbol.

"Y11" is a device name, and the device is a bit type. The second drawing section 21a2c refers to the row 81 of the symbol data 24b and displays the circular symbol 110 on the display section 26. [ The second rendering unit 21a2c displays the device name " Y11 " in the symbol 110. [

As described above, when the symbol 106 of the device with the label name " B " is selected, the second drawing unit 21a2c selects the device name " And the symbol 110 of the device with the device name " Y11 ".

Therefore, the user can easily grasp the dependency relation between the device having the label name "B" and the device having the device name "X1", and the dependency of the device having the label name "B" and the device having the device name "Y11". Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

15 is a flowchart showing the processing of the engineering tool according to the first embodiment.

The second rendering unit 21a2c determines in step S310 whether the symbol of the device selected in step S300 has been selected again by the user.

If the second rendering unit 21a2c determines that the symbol of the device selected in step S300 has not been selected again by the user (No), the second rendering unit 21a2c waits in step S310.

If the second rendering unit 21a2c determines that the symbol of the device selected in step S300 is selected again by the user (Yes), the second rendering unit 21a2c proceeds to step S312.

In step S312, the second rendering unit 21a2c erases the symbol and the forwarding line of the device displayed in step S304 from the display screen, and ends the processing.

When the symbol 106 of the device with the label name "B" is selected again on the display screen shown in Fig. 14 by the second drawing unit 21a2c executing the process shown in Fig. 15, The symbols 110 and the meridian lines 109 and 111 of the symbol 108 and the device with the device name " Y11 " are erased from the display screen.

As described above, when the symbol 106 of the device with the label name " B " is selected, the second drawing unit 21a2c selects the device name " The symbol 108 of the device with the label name "B" and the symbol 110 of the device with the device name "Y11" can be displayed. Then, when the symbol 106 of the device with the label name "B" It is possible to erase the symbol 108 of the device of the device name "X1" and the symbol 110 of the device of the device name "Y11" that directly relate to the device of the device name "Y11".

Therefore, the user can erase the symbol 108 of the device with the confirmed device name " X1 " and the symbol 110 of the device with the device name " Y11 " Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

16 is a flowchart showing the processing of the engineering tool according to the first embodiment.

The monitoring unit 21a2d acquires data of the device from the control device 3 in step S400.

The monitoring unit 21a2d determines in step S402 whether or not the data type of the device from which the data is acquired is a bit type.

If the monitoring unit 21a2d determines that the data type of the device from which the data is acquired is a bit type (Yes), the process proceeds to step S404.

If the monitoring unit 21a2d determines that the data type of the device from which the data is acquired is not a bit type, that is, a word type (No), the monitoring unit 21a2d proceeds to step S406.

In step S404, the monitoring unit 21a2d displays the symbol of the device that has acquired the data with the color corresponding to the value of the acquired data, and ends the process. The monitoring unit 21a2d may display the symbol as black when the acquired data value is "0" and display the symbol as white when the acquired data value is "1". In addition, black and white are examples, and other colors may be used. The monitoring unit 21a2d may flicker the symbol according to the value of the acquired data.

The monitoring unit 21a2d displays the value of the acquired data on the display unit 26 in step S406, and ends the process.

17 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.

When the monitoring unit 21a2d acquires the data "0" of the bit type device of the device name "X0" from the control device 3, the monitoring unit 21a2d displays the symbol 101 in black.

When the monitoring unit 21a2d acquires the data "0" of the bit type device of the device name "M100" from the control device 3, the monitoring unit 21a2d displays the symbol 102 in black.

When the monitoring unit 21a2d acquires data "0" of the bit type device of the device name "Y10" from the control device 3, the monitoring unit 21a2d displays the symbol 104 in black.

When the monitoring unit 21a2d acquires the data "1" of the bit type device of the label name "B" from the control device 3, the monitoring unit 21a2d displays the symbol 106 as white.

When the monitoring unit 21a2d acquires data "0" of the bit type device of the device name "X1" from the control device 3, the monitoring unit 21a2d displays the symbol 108 in black.

When the monitoring unit 21a2d acquires the data "1" of the bit type device of the device name "Y11" from the control device 3, the monitoring unit 21a2d displays the symbol 110 as white.

As a result, the user can intuitively grasp the value of each device.

18 is a diagram showing an example of a display screen of the engineering tool according to the first embodiment.

In the display screen shown in Fig. 18, the symbol 120 of the word type device with the device name " G11 " is displayed. In addition, a symbol 121 of the word type device of the device name "D100" is displayed. A fiducial line 122 indicating that the device of the device name " D100 " connecting the symbol 120 and the symbol 121 directly depends on the device of the device name " G11 "

In the display screen shown in Fig. 18, the symbol 123 of the word type device of the label name " A " is displayed. A meridian line 124 connecting the symbol 121 and the symbol 123 and indicating that the device of the label name "A" directly depends on the device of the device name "D100" is displayed.

In the display screen shown in Fig. 18, a symbol 125 of the word type device of the label name " C " is displayed. A meridian line 126 indicating that the device with the label name " C " connecting the symbol 121 and the symbol 125 directly depends on the device having the device name " D100 "

When the monitoring unit 21a2d acquires the data "60" of the word type device of the device name "D100" from the control device 3, the monitoring unit 21a2d displays an image 127 such as "60" next to the symbol 121 .

Displaying an image 127 such as " 60 " next to the symbol 121 means that the distance between the image 127 and the symbol 121 is between the image 127 and another symbol 120, 123 or 125 The image 127 is displayed so as to be shorter than the distance of the image 127. [

As described above, the monitoring unit 21a2d displays the value of the data acquired from the control device 3 on the display unit 26 so that the user can identify the value.

Therefore, the user can easily grasp the data of the device. Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

Embodiment 2 Fig.

19 is a diagram showing a configuration of a control system according to Embodiment 2 of the present invention. The control system 1A further includes a second control device 3A in addition to the engineering tool 2 and the first control device 3. [ The engineering tool 2 and the control devices 3 and 3A are connected so as to be able to communicate via the network N1.

The hardware configuration of the second control device 3A is the same as the hardware configuration of the first control device 3 described with reference to Fig. 2, and a description thereof will be omitted.

The control devices 3 and 3A have a local memory area and a shared memory area in the memory 3a2. The local memory area is an area that the control device 3 or 3A alone has. The shared memory area is an area shared by the control devices 3 and 3A.

When the first control device 3 writes data to the device in the shared memory area, the written data is transferred to the corresponding device in the shared memory of the second control device 3A. When the second control device 3A writes data to the device in the shared memory area, the written data is transferred to the corresponding device in the shared memory of the first control device 3. [

Thereby, the control devices 3 and 3A can share data.

20 is a functional block diagram of the engineering tool according to the second embodiment. The storage unit 24 further stores project data 24d in addition to the project data 24a and the symbol data 24b.

The project data 24d is created by the project data creation unit 21a1 in the same manner as the project data 24a. The project data 24d, like the project data 24a, includes control programs, control parameters, device memory, connection information, and label information.

The project data 24d is transmitted to the second control device 3A. The second control device 3A controls the machine by executing the control program in the project data 24d.

21 is a diagram showing an example of a control program according to the second embodiment. Control program 24a1 includes row 65 in addition to rows 61, 62, 63 and 64. [

The row 65 includes a condition part 65a and an operation part 65b. The condition unit 65a is a load instruction for reading data of the device having the device name " Y12 ".

The operation unit 65b is a " MOV " (move) instruction for transferring the value of the first argument to the second argument. The first argument " K1000 " is a constant " 1000 ". The second argument is a word type device whose device name is " D100 ".

In the second embodiment, the device with the device name " D100 " is arranged in the shared memory. In the device of the device name " D100 ", data is written by the first control device 3 executing the control program 24a1. Therefore, the operation unit 65b includes a character string such as " [PLC1: shared memory] " indicating that the first control device 3 writes data to the device having the device name " D100 ".

In the row 65, when the data of the device whose device name is "Y12" is "1", the constant "1000" is transmitted to the device of the device name "D100".

That is, the device with the device name "D100" directly relies on the device with the device name "Y12".

22 is a diagram showing an example of a control program according to the second embodiment. The control program 24d1 included in the project data 24d includes a line 131. [

The row 131 includes a condition part 131a and an operation part 131b. The condition part 131a is an " equal " instruction for determining whether the first argument and the second argument are equal.

In the second embodiment, the device with the device name " D100 " is arranged in the shared memory. In the device of the device name " D100 ", data is written by the first control device 3. Therefore, the condition part 131a includes a string such as " PLC1: shared memory " indicating that the first control device 3 writes data to the device having the device name " D100 ".

The operation unit 131b is an output instruction for outputting data to the device having the device name " Y20 ".

In the row 65, when the data of the device with the device name "D100" is equal to the constant "1000", "1" is output to the device with the device name "Y20".

That is, the device with the device name "Y20" directly relies on the device with the device name "D100".

23 is a flowchart showing the processing of the engineering tool according to the second embodiment.

The dependent data creating unit 21a2a executes the dependent data creating process shown in FIG. 8 in the control program 24a1 executed in the first control device 3 in step S500.

24 is a diagram showing an example of the dependency data according to the second embodiment. Dependent data 24c further includes a row 95 in addition to rows 91, 92, 93, and 94. [

Row 95 corresponds to row 65 of control program 24a1. The device name "Y12" of the dependent destination is described on the left side of the delimiter ":", and the device name "D100 [PLC1: shared memory]" of the dependency source is described on the right side of the delimiter ":".

Referring again to FIG. 23, in step S502, the dependent data creating unit 21a2a executes the dependent data creating process shown in FIG. 8 to the control program 24d1 executed in the second control device 3A, The processing is terminated.

25 is a diagram showing an example of the dependency data according to the second embodiment. The dependent data 24e includes a row 141. [

The row 141 corresponds to the row 131 of the control program 24d1. The destination device name "D100 [PLC1: shared memory]" is described on the left side of the delimiter ":", and the device name "Y20" of the dependent source is described on the right side of the delimiter ":".

The first rendering unit 21a2b uses the dependent data 24c and 24e as the dependent data of the object to be retrieved, and executes the processing shown in Fig.

Thus, the first drawing unit 21a2b can display the dependency of the device of the device name " D100 " and the device of the device name " Y20 ".

Therefore, the user can easily grasp the dependency of the device described in the control program 24a1 and the control program 24d1. Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

The second rendering unit 21a2c uses the dependent data 24c and 24e as the dependent data of the retrieval object, and executes the processes shown in Figs. 12 and 15.

Thus, when the device with the device name " D100 " is selected, the second drawing unit 21a2c displays the symbol of the device having the device name " Y20 " Then, when the device of the device name "D100" is selected again, the device of the device name "Y20" that relies directly on the device of the selected device name "D100" can be deleted.

Therefore, the user can erase the symbol of the confirmed device name " Y20 ", thereby making it easy to view the display screen. Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

The monitoring unit 21a2d executes the process shown in Fig.

Thus, when the monitoring unit 21a2d acquires the data of the device with the device name "D100" from the first control device 3, the acquired data can be displayed next to the symbol of the device with the device name "D100" have. Thus, the user can easily grasp the data of the device having the device name " D100 ".

When the monitoring unit 21a2d acquires the data of the device with the device name " Y20 " from the second control device 3A, the monitoring unit 21a2d can display the acquired data next to the symbol of the device with the device name " Y20 ".

Therefore, the user can easily grasp the data of the device with the device name " Y20 ". Thereby, the engineering tool 2 can reduce the number of debug processes, and it is possible to facilitate the early resolution of the trouble.

The configuration shown in the above embodiment represents one example of the content of the present invention and can be combined with other known technology and a part of the configuration can be omitted or changed within a range not departing from the gist of the present invention Do.

1, 1A: Control system 2: Engineering tool
21: CPU 21a: Engineering tool part
21a2: Debug unit 21a2a:
21a2b: first drawing section 21a2c: second drawing section
21a2d: monitoring unit 24:
24a, 24d: project data 24b: symbol data
24c, 24e: dependent data 26:
3, 3A: Control device

Claims (9)

A storage unit that stores project data including a control program executed by the control apparatus and a device memory that is data in which a description (description) for specifying a plurality of devices as a plurality of work areas in the memory of the control apparatus is made;
A display unit for displaying characters or images,
A dependence data creation unit that creates dependency data representing dependency relationships of the plurality of devices described in the control program and stores the dependency data in the storage unit;
And a rendering unit configured to display an image representing a dependency of the plurality of devices on the display unit based on the dependency data. The method according to claim 1,
Wherein the project data further includes label information associating a device name which is a name of the device with a label name which is a nickname of the device,
The imaging unit includes:
Wherein the label name is displayed on the device to which the label name is assigned and the device name is displayed on the device to which the label name is not assigned. The method of claim 2,
The storage unit stores,
Further storing symbol data in which the data type of the device and the device name of the device or the type of the label name and the symbol correspond to each other,
The imaging unit includes:
And said device is represented by said symbol based on said symbol data. The method according to claim 1,
Further comprising a second rendering unit for, when the device in the image is selected, further displaying, on the display unit, the device directly dependent on the selected device based on the dependency data. The method of claim 4,
Wherein the second rendering unit comprises:
And when the device in the image is selected again, erases the image of the device directly dependent on the again selected device. The method according to any one of claims 1 to 5,
Further comprising a monitoring unit configured to display an image based on the received data on the display unit when receiving data of the device in the image from the control apparatus. The method according to claim 1,
Wherein the storage unit stores a plurality of the project data,
The dependency data creation unit creates a plurality of dependency data indicating dependency relationships of the plurality of devices described in the plurality of control programs and stores the dependency data in the storage unit,
Wherein the rendering unit causes the display unit to display an image representing a dependency of the plurality of devices based on the plurality of dependency data. A storage unit that stores project data including a control program executed by the control apparatus and a device memory that is data in which a technique for defining a plurality of devices as a plurality of work areas in the memory of the control apparatus is made;
1. A method executed by an apparatus having a display unit for displaying a character or an image,
A dependence data creation step of creating dependency data representing dependency relations of the plurality of devices described in the control program and storing the dependency data in the storage section;
And a display step of displaying an image representing a dependency of the plurality of devices on the display unit based on the dependency data. A storage unit that stores project data including a control program executed by the control apparatus and a device memory that is data in which a technique for defining a plurality of devices as a plurality of work areas in the memory of the control apparatus is made;
A program for causing a computer having a display unit to display characters or images,
A dependence data creation step of creating dependency data representing dependency relations of the plurality of devices described in the control program and storing the dependency data in the storage section;
And causes the computer to execute a drawing step of causing the display unit to display an image representing a dependency of the plurality of devices on the basis of the dependency data.
KR1020177036513A 2015-06-01 2015-06-01 Debug device, debug method, and debug program KR101864565B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2015/065736 WO2016194099A1 (en) 2015-06-01 2015-06-01 Debug device, debug method, and debug program

Publications (2)

Publication Number Publication Date
KR20180004825A true KR20180004825A (en) 2018-01-12
KR101864565B1 KR101864565B1 (en) 2018-06-04

Family

ID=57440951

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020177036513A KR101864565B1 (en) 2015-06-01 2015-06-01 Debug device, debug method, and debug program

Country Status (4)

Country Link
JP (1) JP6150953B2 (en)
KR (1) KR101864565B1 (en)
CN (1) CN107615191B (en)
WO (1) WO2016194099A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20210114125A (en) * 2020-03-10 2021-09-23 엘에스일렉트릭(주) Method for preventing interference between plc program blocks

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6664562B1 (en) * 2019-04-18 2020-03-13 三菱電機株式会社 Debug support device, debug support method, and debug support program
WO2021210071A1 (en) * 2020-04-14 2021-10-21 三菱電機株式会社 Debugging assistance program, storage medium, debugging assistance device, and debugging assistance method
WO2022049724A1 (en) * 2020-09-04 2022-03-10 三菱電機株式会社 Program creation assistance program, program creation assistance device, and program creation assistance method
CN116670600A (en) * 2021-03-02 2023-08-29 三菱电机株式会社 Debugging support program, debugging support device, debugging support method, and machine learning device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001022412A (en) 1999-07-09 2001-01-26 Toshiba Corp Programming device, programmable controller, and computer readable recording medium storing program
JP5138090B2 (en) * 2009-02-18 2013-02-06 三菱電機株式会社 Program analysis support device
JP2013225251A (en) * 2012-04-23 2013-10-31 Mitsubishi Electric Corp Information processor and information processing method and program
JP5362148B1 (en) * 2012-12-17 2013-12-11 三菱電機株式会社 Program analysis support device and control device

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005025579A (en) * 2003-07-04 2005-01-27 Matsushita Electric Ind Co Ltd Simulator debugger
CN102449563B (en) * 2009-05-27 2014-06-18 三菱电机株式会社 Sequence program debugging device and debugging method
DE112010005963B4 (en) * 2010-10-27 2018-05-03 Mitsubishi Electric Corporation Log setting device, logging setting method and recording medium
JP5762154B2 (en) * 2011-06-08 2015-08-12 三菱電機株式会社 Information processing apparatus, information processing method, and program
US8726091B2 (en) * 2011-06-24 2014-05-13 Rockwell Automation Technologies, Inc. Troubleshooting system for industrial control programs
JP5942446B2 (en) * 2012-02-01 2016-06-29 オムロン株式会社 Support device and support program
JP2013161376A (en) * 2012-02-07 2013-08-19 Hakko Denki Kk Programmable display, program thereof, and display/control system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001022412A (en) 1999-07-09 2001-01-26 Toshiba Corp Programming device, programmable controller, and computer readable recording medium storing program
JP5138090B2 (en) * 2009-02-18 2013-02-06 三菱電機株式会社 Program analysis support device
JP2013225251A (en) * 2012-04-23 2013-10-31 Mitsubishi Electric Corp Information processor and information processing method and program
JP5362148B1 (en) * 2012-12-17 2013-12-11 三菱電機株式会社 Program analysis support device and control device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20210114125A (en) * 2020-03-10 2021-09-23 엘에스일렉트릭(주) Method for preventing interference between plc program blocks

Also Published As

Publication number Publication date
CN107615191B (en) 2019-03-15
WO2016194099A1 (en) 2016-12-08
CN107615191A (en) 2018-01-19
KR101864565B1 (en) 2018-06-04
JPWO2016194099A1 (en) 2017-06-22
JP6150953B2 (en) 2017-06-21

Similar Documents

Publication Publication Date Title
KR101864565B1 (en) Debug device, debug method, and debug program
US5841656A (en) Programming system for sequence control and control unit for executing program for sequence control
US8032232B2 (en) Natively retaining project documentation in a controller
US9727442B2 (en) Engineering tool, program editing device, and program editing system
KR101889631B1 (en) Device for assisting creation of sequence program
JP3963174B2 (en) Display / editing apparatus, display method, and program
US8549422B2 (en) Graphical approach to setup data sharing between two controllers
WO2018073868A1 (en) Debugging assistance device and debugging assistance method
JP6926841B2 (en) Control system, development support device, and control method
US20060224661A1 (en) Programmable terminal system
WO2019167512A1 (en) Display device, screen generation method, and screen generation program
US9395872B2 (en) Facilities controlling device, screen displaying method, and recording medium
CN109643096B (en) Programmable logic controller system and computer-readable storage medium storing engineering tool program
JP4971226B2 (en) Design support device
KR101230563B1 (en) Sequence control device using decision table, program creation device and interpreter execution engine
KR101846140B1 (en) Program diagnostic device, program diagnostic method, and program diagnostic program
US9830053B2 (en) Screen definition device for operating panel
CN113641350A (en) Software development environment providing system, method, and non-transitory computer-readable medium
JP2022012393A (en) Software development environment providing system, software development environment providing method, and software development environment providing program
CN113885852A (en) Software development environment providing system, method, and non-transitory computer-readable medium
WO2016139805A1 (en) Programmable logic controller engineering tool and programmable logic controller engineering tool program
US20190362660A1 (en) Engineering tool
JP2007179113A (en) Control device, program generating device thereof, program and recording medium therefor
CN113641348A (en) Software development environment providing system, method, and non-transitory computer-readable medium
JP2008172526A (en) Address setting apparatus

Legal Events

Date Code Title Description
A201 Request for examination
A302 Request for accelerated examination
E701 Decision to grant or registration of patent right
GRNT Written decision to grant