WO2018030831A1 - Appareil et procédé de conversion de programme de contrôle de cpl en données structurées - Google Patents

Appareil et procédé de conversion de programme de contrôle de cpl en données structurées Download PDF

Info

Publication number
WO2018030831A1
WO2018030831A1 PCT/KR2017/008728 KR2017008728W WO2018030831A1 WO 2018030831 A1 WO2018030831 A1 WO 2018030831A1 KR 2017008728 W KR2017008728 W KR 2017008728W WO 2018030831 A1 WO2018030831 A1 WO 2018030831A1
Authority
WO
WIPO (PCT)
Prior art keywords
contact
relationship
block
plc control
control program
Prior art date
Application number
PCT/KR2017/008728
Other languages
English (en)
Korean (ko)
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
Priority claimed from KR1020170101465A external-priority patent/KR102004456B1/ko
Application filed by 주식회사 유디엠텍 filed Critical 주식회사 유디엠텍
Priority to CN201780049616.XA priority Critical patent/CN109643100B/zh
Publication of WO2018030831A1 publication Critical patent/WO2018030831A1/fr

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/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
    • G05B19/408—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by data handling or data format, e.g. reading, buffering or conversion of data

Definitions

  • the present invention relates to a PLC control program, and more particularly, to an apparatus and method for converting a text-based PLC control program into a structure data consisting of objects.
  • PLC Programmable Logic Controller
  • LD Layer Diagram
  • BFD Function Block Diagram
  • ST Structured Text
  • IL Instruction List
  • SFC Sequential Function Chart
  • CFC Continuous Function Chart
  • the structure of the PLC control program can be largely divided into tag information containing information about a PLC contact point and logic information containing information about a driven PLC control program.
  • logic information is the most basic element in operating an automated process, and includes all the information about sequences and conditions for facility / process / line control. Can be used as key information for
  • a key element of the automated process operation analysis is to enable rapid and accurate cause identification and response to various abnormal situations occurring in the automated process, which aims to improve productivity and process optimization.
  • the abnormal occurrence of the automation process is caused by the occurrence (ON or OFF) of an abnormal symbol (ON or OFF) on the PLC control program that operates the automation process.
  • a myriad of abnormal signals are included for each process up to and including the abnormal signal.
  • the abnormal situation information displayed on the HMI controller is an abnormal signal belonging to the upper stage among the abnormal signals of the process in which the abnormality occurred, and does not include information on the actual cause of the abnormality (abnormal signal belonging to the lower stage). It is impossible to reproduce the situation.
  • a PLC control program in the form of a structure data is required, but at present, a PLC manufacturer or a PLC programming software, for example, an LD-based PLC control program or a text-based PLC control program converted therefrom. It does not provide PLC control program of structure data format.
  • an object of the present invention is to provide an apparatus and method for automatically converting a text-based PLC control program into a PLC control program having a structure data format.
  • An apparatus for converting a PLC control program into structure data according to the present invention for solving the above technical problem is to build a class library including classes for each of the rung (Rung), input contact and output contact of the PLC control program Class library construction unit; And receiving a common PLC control program converted from a text-based PLC control program, and based on the class library, an object for each of a rung, an input contact, and an output contact of the PLC control program of the common type. And a structure generator for generating structure data to be included.
  • the class library further includes a relationship class for representing a relationship between a corresponding input contact or output contact for each input contact or output contact and at least one other input contact or output contact, wherein the structure data is in the common format.
  • the apparatus may further include a relationship object representing a relationship between a corresponding input contact or output contact for each input contact or output contact of the PLC control program and at least one other input contact or output contact.
  • the relationship class and the relationship object may be data fields and may have a data field for representing a previous input contact, a previous output contact, a next input contact, or a next output contact based on the corresponding input contact or output contact.
  • the structure generating unit may include: an index generating unit for assigning an index to each contact included in the corresponding rung for each rung of the common type PLC control program; An object generation unit for generating an object and a relationship object for each of a rung, an input contact and an output contact of the PLC control program of the common type by reflecting the given index based on the class library; And a relationship forming unit defining the data field of the relationship object.
  • the relationship forming unit may define an index of a previous input contact, a previous output contact, a next input contact, or a next output contact as the data field.
  • the common type PLC control program includes a symbol indicating an OR coupling relationship, and the relationship forming unit uses a symbol indicating the OR coupling relationship, and the common type is combined in an OR relationship in the PLC control program of the common type.
  • a relation block generator that defines a relation block, wherein the relation block has a data field for representing a previous input contact, a previous output contact, a next input contact, or a next output contact;
  • An in-step relationship forming unit defining, for each rung of the PLC control program of the common type represented by the relationship block, the data field for the relationship block, the input contact point, and the output contact constituting the rung;
  • a relationship forming unit in a relationship block defining the data field with respect to the contacts included in the relationship block.
  • the relationship forming unit in the relationship block may distinguish internal elements coupled in an OR relationship in the relationship block, and may include at least one input contact included in the internal elements based on the data field defined for the relationship block, or The data field of the output contact can be defined.
  • the relationship forming unit in the relationship block may redefine the data field of the previous or next input contact or output contact of the corresponding relationship block based on the data field defined for the contacts included in the relationship block.
  • a method for converting a PLC control program into structure data includes: constructing a class library including classes for each of a rung, an input contact, and an output contact of the PLC control program; step; And receiving a common PLC control program converted from a text-based PLC control program, and based on the class library, an object for each of a rung, an input contact, and an output contact of the PLC control program of the common type. And generating the structure data to include.
  • the class library further includes a relationship class for representing a relationship between a corresponding input contact or output contact for each input contact or output contact and at least one other input contact or output contact, wherein the structure data is in the common format.
  • the apparatus may further include a relationship object representing a relationship between a corresponding input contact or output contact for each input contact or output contact of the PLC control program and at least one other input contact or output contact.
  • the relationship class and the relationship object may be data fields and may have a data field for representing a previous input contact, a previous output contact, a next input contact, or a next output contact based on the corresponding input contact or output contact.
  • the generating of the structure data may include: assigning an index to each contact included in the corresponding rung for each rung of the PLC control program of the common type; Generating an object and a relationship object for each of a rung, an input contact and an output contact of the PLC control program of the common type by reflecting the given index based on the class library; And defining the data field of the relationship object.
  • an index of a previous input contact, a previous output contact, a next input contact, or a next output contact may be defined as the data field.
  • the common type PLC control program includes a symbol indicating an OR coupling relationship
  • the step of defining the data field includes: (a) OR in the common type PLC control program using a symbol indicating the OR coupling relationship; Defining a common type combined in a relationship as a relationship block, wherein the relationship block has a data field for representing a previous input contact, a previous output contact, a next input contact, or a next output contact based on the relationship block; ; (b) defining, for each rung of the PLC control program of the common format represented by the relationship block, the data field for the relationship block, the input contact point and the output contact point constituting the rung; And (c) defining the data field with respect to the contacts included in the relationship block.
  • step (c) the internal elements coupled in the OR relationship in the relationship block are distinguished, and at least one input contact or output included in the internal elements based on the data field defined for the relationship block. And defining the data field of the contact.
  • the step (c) may include redefining the data field of a previous or next input contact or output contact of the relation block based on the data field defined for the contacts included in the relation block. Can be.
  • the PLC control program of the structure data format can be the basis of a system that visualizes and traces the actual cause of the occurrence of an abnormal situation in the automation process, thereby contributing to the improvement of the productivity of the automation process and the optimization of the process operation. Can be.
  • FIG. 1 is a block diagram of an apparatus for converting a PLC control program into structure data according to an embodiment of the present invention.
  • 5A shows an example of a PLC control program of the Mitsubishi LD structure.
  • FIG. 5B illustrates a text-based PLC control program converted from the PLC control program of FIG. 5A.
  • FIG. 6 shows IL objects generated by the IL object generator 14 for the first rung and the second rung, respectively.
  • FIG. 7A shows IL blocks generated by the IL block generator 15 for the first rung.
  • FIG. 7B shows IL blocks generated by the IL block generator 15 for the second rung.
  • FIG. 8A illustrates a process of expressing a coupling relationship between common blocks by applying a joint instruction OR to the common blocks shown in FIG. 7A in a common format.
  • FIG. 8B illustrates a process of expressing a coupling relationship between common blocks by applying a joint instruction OR to the common blocks shown in FIG. 7B in a common format.
  • FIG. 9 illustrates a process of expressing a coupling relationship between common blocks by applying a joint command ORB to common blocks after applying the joint command OR through FIG. 8B.
  • FIG. 12 shows common formats of common blocks represented through FIGS. 9 through 11 for the second rung.
  • FIG. 13 shows the final common format for the first rung N0 and the second rung N5, converted from the text-based PLC control program of FIG. 5B.
  • 15A to 15E illustrate data field structures of a 'Step' class, a 'Coil' class, a 'Contact' class, a 'Relation' class, and a 'Tag' class, respectively.
  • FIG. 16 shows a specific configuration of the structure generation unit 22 according to an embodiment of the present invention.
  • FIG. 17 shows an example of the indices given to the contacts for the PLC control program of the common type shown in FIG.
  • FIG. 18 illustrates examples of objects generated from a PLC-type control program of a common type indexed as shown in FIG. 17 based on the class libraries of FIGS. 14 and 15.
  • FIG. 19 illustrates a PLC control program in which the common type PLC control program with an index is expressed in the form of an object as shown in FIG. 17.
  • 21 shows a result of expressing NO step using a relationship block.
  • FIG. 24A shows a result of applying the relation block RBK 0 shown in FIG. 22 to the format of FIG. 23.
  • 24B shows a result of defining a relationship with other contacts for each contact included in the relationship block RBK 0 .
  • FIG. 25 illustrates a result in which all of the relationships between the corresponding input contact or output contact and another input contact or output contact are expressed for each input contact or output contact of the NO step.
  • 26 shows the result of expressing N5 Step using a relationship block.
  • FIG. 28 shows the result of applying the relationship block RBK 0 and the relationship block RBK 1 shown in FIG. 27 to the format of FIG. 23 and defining the relationship with other contacts for each contact included in the RBK 0 and RBK 1 .
  • FIG. 29 illustrates a result of replacing relation block RBK 1 in relation block RBK 0 with contacts I2 and I3 included in FIG. 28.
  • Figure 30 shows the results of replacing with a, a relationship is defined between the contact included in the block RBK 0, i.e. RBK 0 in FIG. 29 the relationship block RBK 0 of Fig.
  • FIG. 31 shows a result of applying the relation block RBK 2 shown in FIG. 27 to the format of FIG. 23.
  • Figure 32 shows the results of replacing with a, a relationship is defined, the contact in the relation RBK block 2, i.e. 2 RBK of the relationship RBK block 2 of Fig. 30 Fig. 31.
  • 34 is a flowchart of a method of converting a common PLC control program into structure data according to an embodiment of the present invention.
  • FIG. 1 is a block diagram of an apparatus for converting a PLC control program into structure data (hereinafter, referred to as a structure data converting apparatus) according to an embodiment of the present invention.
  • the structure data converting apparatus includes a common instruction library constructing unit 11, a storage unit 12, a common format converting unit 13, a class library constructing unit 21, and a structure forming unit 22. can do.
  • the common instruction library construction unit 11, the storage unit 12, and the common format conversion unit 13 share a PLC control program having a different text format for each PLC manufacturer.
  • a so-called common type conversion device hereinafter, referred to as a common type conversion device
  • the common format conversion apparatus is disclosed in detail and in detail in Korean Patent Application No. 10-2015-0181242 filed by the applicant of the present invention, the entire contents of which are incorporated herein by reference.
  • the common format converting apparatus is composed of a common instruction library constructing unit 11, a storage unit 12, and a common format converting unit 13, and the structure data converting apparatus is connected to the class library constructing unit 21. It may be composed of the structure forming part 22.
  • the common instruction library construction unit 11 generates a common instruction library for instructions used in text-based PLC control programs having different formats according to the common instruction generation algorithm, constructs a common instruction library, and stores the storage unit 12. ).
  • the instruction information used in the PLC control program for each PLC manufacturer and the corresponding instruction information corresponding to the PLC instruction before the start of construction of the common instruction library are already in the common instruction library construction unit 11. It is preferable that the storing or input is completed.
  • the common instruction library building unit 11 constructs the common instruction library according to the common instruction generation algorithm.
  • the common command generation algorithm is an algorithm that sequentially performs the first step, the second step and the third step to generate a common command for the commands used in text-based PLC control programs having different formats to be.
  • the first step is to classify the commands used for text-based PLC control programs having different formats into the same display command groups having the same meaning on the display.
  • the second step is to check whether all the commands belonging to the same display command group have the same function.
  • the third step is to generate a common command in a different manner depending on whether all of the commands belonging to the same display command group are the same function or not.
  • a dictionary word indicating the same commands belonging to the same display command group and having the same function is a common command for the commands having the same function. Is generated.
  • a parameter qualifier included in the command having the same function may be inserted into the common command for the command having the same function.
  • the position at which the parameter qualifier is inserted is not limited thereto.
  • AB's command 'DEQU' for 'equal' is a command with the parameter qualifier D (Double) appended to the command 'EQU'.
  • 'D' limits the parameter size of the command 'EQU'.
  • the 'EQU' command processes 1 Word (16bit), and the 'DEQU' command processes 2 Word (32bit).
  • parameter qualifiers that define command parameters may be inserted as prefixes of common commands.
  • an operation modifier included in the command having the same function may be inserted into the common command for the commands having the same function. If any one of the operation qualifiers limiting the operation of the command, that is, P (Negative Pulse) or N (Negative Pulse) is included in the corresponding command, the operation qualifier may be inserted as a suffix in the common command of the command. However, the position at which the operation modifier is inserted is not limited thereto.
  • Mitsubishi's 'ANDP' command is 'P', an operation qualifier that converts 'AND', which has a function to turn on when the address value is On, to a positive pulse form. (Positive pulse) '. Therefore, 'XICP', a common command for 'ANDP', may be generated by suffixing an operation modifier 'P' to 'XIC (eXamine If Closed)', a common command for 'AND'.
  • the dictionary words for displaying the same commands belonging to the same display command group but not all have the same function do not have the same function. It is possible to generate a common command for the commands, and insert the manufacturer name of the PLC controlled by the PLC control program in which the command having the same function is not used in the common command for the commands having the same function.
  • the command 'LIMIT' may be mentioned.
  • the command 'LIMIT' is used the same in the PLC control program of Mitsubishi, LS Industrial Systems and AB, but it does not have the same function.
  • 'LIMIT' command is not used in Siemens PLC control program.
  • the common command for the command 'LIMIT' may be generated as the word 'LIMIT' in the dictionary. Since the command 'LIMIT' does not have the same function for each PLC manufacturer, the manufacturer name of each PLC can be inserted in the common command 'LIMIT'. For example, Mitsubishi's 'm', 'S' for Siemens, 'ab' for AB, and 'ls' for LS prenatal can be inserted as a prefix of the common command 'LIMIT'. In other words, it can be 'mLIMIT' for Mitsubishi, 'sLIMIT' for Siemens, 'abLIMIT' for AB, and 'lsLIMIT' for LS.
  • a parameter qualifier included in the command that does not have the same function may be inserted into the common command for the commands that do not have the same function.
  • AB's command 'DLIMIT' is a command with the parameter qualifier D (Double) appended to the command 'LIMIT'.
  • 'D' limits the parameter size of the command 'LIMIT'.
  • the 'LIMIT' command processes 1 Word (16bit), and the 'DLIMIT' command processes 2 Word (32bit).
  • parameter qualifiers that define command parameters may be inserted into common commands, which may be placed after a prefix indicating the PLC manufacturer, for example, 'ab' indicating the AB company. After all, the common command for AB 'DLIMIT' may be 'abDLIMIT'.
  • an operation modifier included in the command that does not have the same function may be inserted into the common command for the commands that do not have the same function.
  • Mitsubishi's 'LIMITP' command includes 'P (Postive Pulse)', an operation modifier that converts the positive 'pulse' form of the command 'LIMIT'.
  • an action modifier that restricts the operation of the command may be inserted as a suffix to the public command.
  • the public command for Mitsubishi's command 'LIMITP' may be 'mLIMITP'.
  • the common command generated by sequentially performing steps 1 to 3 may be converted into an XML (eXtensible Markup Language) file format to build a common command library in the storage unit 12.
  • XML eXtensible Markup Language
  • the XML file for the common command includes instructions corresponding to each of the Instructio Name 'XIC', 'XICP', and 'XICF' for each PLC manufacturer.
  • the command 'XIC' corresponds to AB
  • the command 'XIC' corresponds to AB
  • Mitsubishi's' LD ',' AND 'and' OR ' respectively
  • the common format converting unit 13 converts the text-based PLC control program that is requested to be converted into a common format into a common PLC control program, and uses the common command library to read the text-based PLC control program. Convert to a common PLC control program.
  • the common format conversion unit 13 includes an IL object generation unit 14, an IL block generation unit 15, a common block conversion unit 16, and a joint relationship expression unit 17.
  • the text-based PLC control program is converted into the PLC control program of the common format.
  • the IL object generation unit 14 confirms whether the text-based PLC control program requested for conversion to the common format can be converted to the PLC control program of the common format.
  • whether the text-based PLC control program can be converted to the common format can be determined using at least one of a file extension and a data structure of the text-based PLC control program.
  • the text-based PLC control program cannot be converted into a common PLC control program.
  • the IL object generation unit 14 performs a rung constituting the control logic of the text-based PLC control program as the text-based PLC control program requested to be converted to the common format can be converted to the PLC control program of the common format.
  • At least one contact point is generated as an IL object including a command and a tag, respectively, according to a logic order. That is, the IL object used throughout the present invention is used in the same sense as the contact point.
  • the IL block generation unit 15 generates at least one IL block by blocking at least one IL object generated by the IL object generation unit 14 using a block command.
  • the block instruction includes LD, LDI, ANB, OR, ORB, MPP, MRD, and MPS.
  • LD is an abbreviation of Load and indicates that the contact point on the control logic is loaded.
  • the LD may continue to produce blocks of control logic of the PLC program.
  • LDI Load Inverse. It contains Inverse meaning, so the contact is ON when the tag is OFF.
  • ANB stands for AND Block, indicating that two blocks created before the ANB instruction are in AND relationship with each other.
  • OR indicates that the symbol preceding the OR command and the symbol of the OR command are ORed together.
  • ORB stands for OR Block, indicating that two blocks created before the ORB instruction are OR'ed together.
  • MPS Multi Point Start. When multiple output contacts appear, the first output contact is written to the front of the first output contact and the contacts associated with that output contact.
  • MRD Multi Read Down and is used when three or more output contacts appear.
  • MPP Multi Point Period. When multiple output contacts appear, the MPP is written at the front of the last output contact and the contacts associated with that output contact.
  • OR, ORB, ANB, MPS, MRD, and MPP among the block commands are combined commands used in the connection relationship expression unit 17.
  • the combined instruction except the OR instruction includes only the instruction when expressing the IL object, and expresses only the association relationship between each block. Therefore, since the block combining instruction indicating the relationship between the blocks, the instruction of the IL object including the block combining instruction is not converted into the common instruction when the transform unit 16 is executed to the common block.
  • the IL block generation unit 15 checks whether a block instruction is included in the IL objects while moving the IL objects arranged in the control logic order, and generates a new IL block if the block instructions are included. On the other hand, if the block instruction is not included, the IL object is sequentially included in the previously generated IL block until a new block instruction appears.
  • the common block converting unit 16 generates a common object by converting the instruction into a common instruction for each of the at least one IL object in the at least one IL block by using the common instruction library, and thus, the at least one IL block. Converts to at least one shared block.
  • the coupling relationship expression unit 17 expresses the coupling relationship between the at least one shared block by at least one of the symbols "[", "]” and ",” using a coupling command.
  • the combined instruction may include OR, ORB, ANB, MPP, MPS, and MRD.
  • the combined instructions used for the input (conditional) are OR, ANB and ORB, and the combined instructions used for the output are MPS, MRD and MPP.
  • the coupling relationship expression unit 17 may express the coupling relationship between the common blocks expressed in the common format with at least one of the symbols "[", “]” and “,”. To this end, the coupling relationship expression unit 17 expresses the coupling relationship between the common blocks expressed in the common form according to the coupling instruction used in the input unit (conditional) with at least one of the symbols "[", “]” and ",” After that, the coupling relationship between the common blocks represented by the coupling command used in the input unit may be expressed by at least one of the symbols "[", "]” and ",” according to the combining command used in the output unit.
  • the coupling command used in the input unit is applied to the common blocks expressed in the common format in the order of OR-> ANB-> ORB, and the symbol "[" , "]" And ",” can be expressed by at least one.
  • the application of the combined command used in the input unit to the common blocks expressed in the common format in the order of OR-> ANB-> ORB is just one embodiment, but is not limited thereto.
  • the common blocks represented by the combined command used in the input unit may be applied to the common blocks represented by the combined command used in the input unit in the order of MPS-> MRD-> MPP.
  • the coupling relationship between the two may be expressed by at least one of the symbols "[", "]" and ",".
  • the application of the combined command used in the output unit to the common blocks represented by the combined command used in the input unit in the order of MPS-> MRD-> MPP is just one embodiment and is not limited thereto.
  • the IL object generating unit 14 converts the control logic of the text-based PLC control program as the text-based PLC control program requested to be converted into a common format can be converted into a PLC control program of the common format.
  • at least one contact point is generated as an IL object including a command and a tag, respectively, in a logic order (S71).
  • the IL block generation unit 15 generates at least one IL block by blocking the at least one IL object by using a block command. This may correspond to steps S72 to S76 in FIG. 4.
  • the IL block generation unit 15 sequentially extracts the IL object from the IL object list (S72), until the final IL object of the rung (S73) is assigned to the block instruction 'LD, AND, Check whether OR, ORB, MPP, MRD, and MPS 'are included (S74), and if so, create a new IL block (S75), and if not, insert the IL object into the most recently generated IL block. Repeat (S76).
  • the common block converting unit 16 generates a common object by converting an instruction into a common instruction for each of at least one IL object in the at least one IL block by using a common instruction library to generate the at least one IL block. At least one common block is converted (S77).
  • the coupling relationship expression unit 17 expresses the coupling relationship between the at least one shared block by at least one of the symbols "[", "]” and ",” using a coupling command. This may be performed by steps S78 to S90 in FIG. 4.
  • the coupling relationship expression unit 17 sequentially extracts the public blocks shown in FIG. 8 (S78), and checks whether the extracted public block is the last public block (S79).
  • the association relationship expression unit 17 checks whether the combined instruction ORB or OR is included in the extracted common block (S80). If included, "[", ",", “]” is inserted into the two previous shared blocks (S81).
  • the association relation expression unit 17 checks whether the combined common block ANB is included in the extracted common block (S82). If included, the two preceding public blocks of the extracted common block are pasted (S83).
  • the association relationship expression unit 17 checks whether the combined common block MPS is included in the extracted common block. If included, insert "[" in front of the corresponding common block (S85).
  • the association relationship expression unit 17 checks whether the joint command MRD is included in the extracted common block (S86). If included, the ",” is inserted in front of the corresponding common block (S87).
  • the association relationship expression unit 17 determines that the combined common block MPP is included in the extracted common block, and inserts ",” in front of the corresponding common block. Insert "]" at the rear (S88).
  • the joint relationship expression unit 17 sequentially merges the common blocks in which the joint relationship is indicated in the common format (S89), and the joint relationship between the merged public blocks. Output the common format indicated by (S90).
  • FIG. 5A illustrates an example of a PLC control program of an LD structure of Mitsubishi
  • FIG. 5B illustrates a text-based PLC control program converted from the PLC control program of FIG. 5A.
  • the process of converting the text-based PLC control program of FIG. 5B into the common control PLC control program by the above-described common format conversion unit 13 will be described.
  • the PLC control program of FIGS. 5A and 5B is composed of two rungs, and includes, as instructions, LD, OR, AND, ANI, OUT, LDI, ORB, MPS, MPP, and the like with tags X0, X1, M0. , X3, Y0, X4, X5, X6, X8, X7, X9, X10, Y2 and the like.
  • FIG. 6 shows IL objects generated by the IL object generator 14 for the first rung and the second rung, respectively.
  • the IL objects may be arranged according to the control logic order of the text-based PLC control program illustrated in FIG. 5B. That is, the order of the IL objects is the same as the control logic order of the text-based PLC control program. Specifically, if the order of IL objects is listed in the order of Command, LD, OR, AND, ANI, OUT for the first rung, and LDI, AND, for the second rung.
  • FIG. 7A shows IL blocks generated by the IL block generator 15 for the first rung.
  • an IL block 1 is generated by a block instruction 'LD' and includes one IL object, that is, an IL object that is an instruction LD.
  • the IL block 2 is generated by the block instruction 'OR' and includes four IL objects, that is, an IL object that is an instruction OR, an IL object that is an instruction AND, an IL object that is an instruction ANI, and an IL object that is an instruction OUT.
  • FIG. 7A illustrates a result of converting IL blocks into shared blocks by the common block converter 16.
  • the common block converting unit 16 converts the IL block # 1 by converting an IL object having an instruction 'LD' into a common object having a common command 'XIC' using the common command library. Convert to shared block # 1. Therefore, the common type of shared block 1 can be expressed as 'XIC (X0)'.
  • the common block converting unit 16 converts the IL object having the instruction 'OR' into the common object having the common instruction 'XIC' using the common instruction library, and the IL object having the instruction 'AND'. Is converted to a public object with public command 'XIC', IL object with command 'ANI' is converted to a public object with public command 'XIO', and IL object with command 'OUT' is converted to a public object with public command 'OUT' By transforming, the IL block 2 is converted into the 2 common block. Therefore, the common type of shared block 2 can be expressed as 'XIC (X1) XIC (M0) XIO (X3) OUT (Y0)'.
  • FIG. 7B shows IL blocks generated by the IL block generator 15 for the second rung.
  • the IL block # 1 is generated by the block instruction 'LDI' and includes two IL objects, that is, the IL object that is the instruction LDI, and the instruction AND. Contains an IL object.
  • the IL block 2 is generated by the block instruction 'LDI' and includes one IL object, that is, the IL object which is the instruction LDI.
  • the IL block 3 is generated by the block instruction 'OR' and includes two IL objects, that is, an IL object that is an instruction OR and an IL object that is an instruction AND.
  • the IL block 4 is generated by the block instruction 'ORB' and includes two IL objects, that is, an IL object that is an instruction ORB and an IL object that is an instruction AND.
  • the IL block 5 is generated by the block instruction 'MPS' and includes two IL objects, that is, the IL object which is the instruction MPS and the IL object which is the instruction OUT.
  • the IL block 6 is generated by the block instruction 'MPP' and includes three IL objects, that is, the IL object which is the instruction MPS, the IL object which is the instruction ANI, and the IL object which is the instruction OUT.
  • FIG. 7B illustrates a result of converting IL blocks into shared blocks by the common block converter 16.
  • the common block converting unit 16 converts the IL object having the instruction 'LDI' into a common object having the common instruction 'XIC' using the common instruction library, and has the instruction 'AND'
  • the common type of common block 1 can be expressed as 'XIC (X4) XIC (X5)'.
  • the common block converting unit 16 converts the IL object having the instruction 'LDI' to a common object having the common instruction 'XIC' using the common instruction library, thereby converting the IL block # 2 twice. Convert to shared block. Therefore, the common type of common block 2 can be expressed as 'XIC (X6)'.
  • the common block converting unit 16 converts the IL object having the instruction 'OR' into the common object having the common instruction 'XIC' using the common instruction library, and the IL object having the instruction 'AND'. Converts IL block 3 to public block 3 by converting it to a public object with public command 'XIC'. Therefore, the common type of common block 3 can be expressed as 'XIC (X8) XIC (X7)'.
  • the common block converting unit 16 does not convert the IL object that is the block combining instruction 'ORB' into the common instruction using the common instruction library, and converts the IL object that is the instruction 'AND' into the common instruction.
  • IL block 4 is converted to 4 public blocks. Therefore, the common type of common block 4 can be expressed as 'XIC (X9)'.
  • the common block converting unit 16 does not convert the IL object that is the block combining instruction 'MPS' into the common instruction using the common instruction library, and converts the IL object that is the instruction 'OUT' into the common instruction. Converts IL block 5 to public block 5 by converting it to a public object that is 'OUT'. Therefore, the common type of common block 5 can be expressed as 'OUT (M0)'.
  • the common block converting unit 16 does not convert the IL object that is the block combining instruction 'MPP' into the common instruction using the common instruction library, and converts the IL object that is the instruction 'ANI' into the common instruction.
  • the IL block 6 is converted to the common block 6 by converting the IL object of the instruction 'OUT' into an IL object of the common instruction 'OUT'. Therefore, the common type of common block 6 can be expressed as 'XIO (X10) OUT (Y2)'.
  • the PLC control program of the common format may be expressed in a common format for at least one rung constituting the control logic of the text-based PLC control program.
  • At least one point of contact in the text-based rung is represented as a common object including a common instruction and a tag, and the at least one common object is A coupling relationship between at least one common block generated by blocking may be represented by at least one of the symbols "[", “]” and ",”.
  • the symbols "[”, “]” represent a coupling point
  • the symbol ",” represents a branch point.
  • the association relation representation between these common blocks may be performed by the association relation representation unit 17.
  • FIG. 8A is a diagram illustrating a process of expressing a coupling relationship between common blocks by applying a joint instruction OR to the common blocks shown in FIG. 7A in a common format.
  • the coupling relationship expression unit 17 checks whether the common block shown in FIG. 7A includes a common block including a coupling instruction OR.
  • the coupling relationship between the public block and the two public blocks of the previous public block is expressed using the symbols "[", "]" and ",”.
  • FIG. 8A a coupling relationship between a common block 2 including a joint instruction OR and a shared block 1 is expressed using the symbols "[", "]" and ",”.
  • next public block of the common block 2 including the combined instruction OR does not include the combined instruction OR, inserts "]" after the common format of the IL object including the OR instruction among the common forms of the current public block 2 (S3). If the next public block of the current public block containing an OR contains a combined instruction OR, insert "," at the end of the public format of the current public block.
  • the common type of the 2nd common block of the first rung becomes '[XIC (X0), XIC (X1)] XIC (M0) XIO (X3) OUT (Y0)'.
  • FIG. 8B is a diagram illustrating a process of expressing a coupling relationship between common blocks by applying a joint instruction OR to the common blocks shown in FIG. 7B in a common format.
  • the coupling relationship expression unit 17 checks whether the common block including the coupling instruction OR is present in the common blocks illustrated in FIG. 7B.
  • the coupling relationship between the public block and the two public blocks of the previous public block is expressed using the symbols "[", "]" and ",”.
  • next public block of the common block 3 including the combined instruction OR does not include the combined instruction OR, inserts "]" after the common format of the IL object including the OR instruction among the common forms of the current public block 3 (S7). . If the next public block of the current public block containing an OR contains a combined instruction OR, insert "," at the end of the public format of the current public block.
  • FIG. 9 is a diagram illustrating a process of expressing a coupling relationship between common blocks by applying a joint command ORB to common blocks after applying the joint command OR through FIG. 8B.
  • the coupling relationship expression unit 17 checks whether the common block including the coupling instruction ORB is present in the common blocks after applying the coupling instruction OR. Two non-empty public blocks in front of the public block including the included public block and the joint instruction ORB are used to express the association relationship to the public blocks.
  • association relationship expression unit 17 inserts "[" at the beginning of the common format expression of the first public block of the first non-empty public blocks of the two non-empty public blocks in front of the common block ORB. (S9).
  • association relationship unit 17 adds "," to the beginning of the common type representation of the third common block, which is the second common block of the two non-empty common blocks before the fourth common block including the joint instruction ORB. Insert (S10).
  • association relationship expression unit 17 checks whether the public block including the association instruction OR and the common block including the association instruction ORB exist in the public block after the fourth common block including the association instruction ORB, and only when it does not exist. Insert "]" at the beginning of the common type representation of the common block 4, including the combined instruction ORB (S11).
  • the joining relation expression unit 17 merges the first public block and the third public block into the fourth public block with the lowest number among the first public block, the third public block, and the fourth public block, and then merges the fourth public block.
  • the public object including the combined instruction ORB is deleted from the public block (S12).
  • the common type of shared block 4 of the second rung is '[XIC (X4) XIC (X5), [XIO (X6), XIC (X8)] XIC (X7)] XIC (X9)'. do.
  • 10 is a view showing a result of applying the combined command MPS used in the output unit.
  • the association relationship expression unit 17 checks whether there is a common block including the combined instruction MPS, and inserts "[" in front of the common form representation of the corresponding common block if there is a shared block including the combined instruction MPS. (S13).
  • association relation expression unit 17 inserts "[" at the beginning of the common format representation of the common block 5 including the association instruction MPS.
  • the common format of the 5th common block of the second rung is '[OUT (M0)'.
  • 11 is a view showing a result of applying the combined command MPP used in the output unit.
  • the association relationship expression unit 17 checks whether there is a common block including the combined instruction MPP, and if there is a shared block including the combined instruction MPP, inserts "," at the beginning of the common form representation of the corresponding common block. And inserting "]" at the end of the common format expression of the corresponding common block (S14).
  • association relationship expression unit 17 inserts ",” at the front and "]" at the front of the common format representation of the common block 6 including the association instruction MPP.
  • the common type of common block 6 of the second rung is ', XIO (X10) OUT (Y2)]'.
  • FIG. 12 shows common formats of common blocks represented through FIGS. 9 through 11 for the second rung. Referring to FIG. 12, when the common formats of the 4th, 5th and 6th common blocks are merged in order, the final common format for the second rung is obtained.
  • FIG. 13 shows a final common format for the first rung N0 and the second rung N5 converted from the text-based PLC control program of FIG. 5B through the above process.
  • the following describes a process of converting a PLC control program of a common format output from the common format conversion unit 13 into structure data by the class library construction unit 21 and the structure generation unit 22. .
  • the class library construction unit 21 is different from the rungs, input contacts, output contacts, tags for the PLC control program, and the corresponding input contact or output contact for each input contact or output contact. Constructs and stores a class library including relation classes, which are classes representing relations with input contacts or output contacts.
  • the class library includes 'StepS' representing a set of all 'Steps' as a top-level class, and a rung of the PLC control program as a subclass of 'StepS' (the logic of the PLC control program).
  • 'Step' which represents the constituent unit
  • 'CoilS' which represents the set of all 'Coil' as a subclass of 'Step'
  • 'C' which indicates the output contact which belongs to the rung as a subclass of 'CoilS'.
  • 15A to 15E illustrate data field structures of a 'Step' class, a 'Coil' class, a 'Contact' class, a 'Relation' class, and a 'Tag' class, respectively.
  • a 'Step' class has a step key, a unique identifier of a corresponding 'Step', a Program, a name of a PLC control program, and a Step Index, an index of the 'Step', as a data field. It has 'CoilS' and 'ContactS'.
  • Step key can consist of the name and rung number of the PLC control program. For example, if the name of the PLC control program is 'Main', the step index for the rung number '0' can be 'Main.0' and the step index for the rung number '5' can be 'Main.5'. . The rung number can be used as the step index.
  • the 'Coil' class has a command which is a command for a corresponding output contact as a data field, an Index which is a unique index in a corresponding Step, and has a 'Tag' and a 'Relation' as a subclass.
  • the 'Contact' class has a command which is a command for a corresponding input contact as a data field, an Index which is a unique index in a corresponding Step, and has a 'Tag' and a 'Relation' as subclasses.
  • the 'Relation' class is a data field based on a corresponding contact or coil, and includes a previous contact, a previous contact index, a previous coil, a previous coil, a next contact index, and a next contact. It has Next Coil which is the index of Coil of.
  • the 'Tag' class has a data field as an address of a corresponding tag and a description as a description of the corresponding tag.
  • the structure generation unit 22 receives a PLC control program of a common format from the common format conversion unit 13, and based on the class library constructed by the class library construction unit 21, Rungs, input contacts, output contacts, objects for tags, and other input contacts or outputs different from the corresponding input contact or output contact for each input contact or output contact of the PLC control program of the common type.
  • Structure data including a relationship object, which is an object representing a relationship with a contact point, is formed, and a PLC control program in the form of a structure is output.
  • a process in which the structure generation unit 22 generates structure data from the PLC control program of the common format will be described using the PLC control program of the common format shown in FIG. 13 as an example.
  • a PLC control program of a given common type is composed of two rungs, so there are two steps.
  • the structure generator may include an index generator 23, an object generator 24, and a relationship generator 25.
  • the index generator 23 internally assigns an index to each contact included in the corresponding rung for each rung (ie, one sentence or line) of the common PLC control program.
  • the index may be sequentially assigned to the contacts, for example, with integers of zero or more. These indices are used by the relationship forming unit 25 to be described later to express the relationship between the contacts.
  • FIG. 17 shows an example of the indices given to the contacts for the PLC control program of the common type shown in FIG.
  • the five contacts XIC (X0), XIC (X1), XIC (M0), XIO (X3) and OUT (Y0) of the first (zero) rung are respectively 0, 1, 2, Index of 3, 4 is given
  • 9 contacts of the second (5th) rung XIC (X4), XIC (X5), XIO (X6), XIC (X8), XIC (X7), XIC (X9) , OUT (M0), XIO (X10), and OUT (Y2) are given indices of 0, 1, 2, 3, 4, 5, 6, 7, and 8, respectively.
  • the object generator 24 divides the contacts of the command (Tag) type of the PLC control program of the given common type into an input contact and an output contact, and is given by the index generator 23. Reflecting the index, a step object, a contact object, a coil object, a tag object, a relation object, and the like are generated based on the class library. Step object, Contact object, Coil object, Tag object, and Relation object correspond to Step class, Contact class, Coil class, Tag class, Relation class of class library, respectively.
  • 'Command' in the form of 'Command (Tag)'.
  • 'Command' corresponding to the input contact point is a common command corresponding to the input such as XIC, XIO, AFI, INV, MEP, MEF, EGP, EGF, EQU, GEQ, GRT, LEQ, LES, MEQ, LIM, Including CMP, 'Command' corresponding to the output contact is the common command corresponding to the output, OUT, SET, RST, MOV, TON, TOFF, RTO, TMR, CTU, CTD, UDCNT, MCR, FOR, NEXT, Includes BREAK, LABEL, RET, CJ, SCJ, CALL, JMP, SBRT, FROM, TO, and more.
  • 'Command' for the distinction between input contact and output contact is a parameter qualifier (eg Double Word: D, Block: BK) or operation qualifier (eg Positive Pulse: P, Negative). Also included are common commands combined with Pulse: N).
  • a parameter qualifier eg Double Word: D, Block: BK
  • operation qualifier eg Positive Pulse: P, Negative
  • common commands eg Positive Pulse: N).
  • XIC (X0), XIC (X1), XIC (M0), and XIO (X3) correspond to an input contact and OUT (Y0) corresponds to an output contact in a first rung.
  • XIC (X4), XIC (X5), XIO (X6), XIC (X8), XIC (X7), XIC (X9), and XIO (X10) correspond to the input contacts and OUT ( M0) and OUT (Y2) correspond to output contacts.
  • FIG. 18 illustrates examples of objects generated from a PLC-type control program of a common type indexed as shown in FIG. 17 based on the class libraries of FIGS. 14 and 15.
  • Step 0 has a Step key, a Program, and a Step Index of Main.0, Main, and 0, respectively, and have four Contact objects and one Coil object.
  • a Contact object with an index of 0 has a command of 'XIC'
  • a Tag object belonging to it has an Address of X0 and a Description of IN0.
  • Step key, Program, and Step Index are Main.5, Main, and 5, respectively, and have 7 Contact objects and 2 Coil objects.
  • a Contact object with an index of 2 has a command of 'XIO'
  • a Tag object belonging to it has an Address of X6 and a Description of IN6.
  • each Contact object and the Relation object belonging to each Coil object are defined.
  • FIG. 19 illustrates a PLC control program in which the common type PLC control program with an index is expressed in the form of an object as shown in FIG. 17.
  • an input contact is represented by 'I'
  • an output contact is represented by 'O'
  • an index is represented by a subscript.
  • the relationship forming unit 25 may include a relationship block generating unit 26, an in-step relationship forming unit 27, and an relationship block forming unit 28.
  • the common type PLC control program includes symbols "[", "]” and ",” representing a coupling relationship, and has a common type structure beginning with "[" and ending with "]". Is defined as a 'Relation Block'.
  • the relationship block generator 26 generates such a relationship block.
  • the inner elements of the relation block are combined in an OR relationship, and the criteria for distinguishing the inner elements is ",".
  • a relation block may exist inside the relation block (for example, referring to FIG. 19, '[I 0 I 1 , [I 2 , I 3 ] I 4 ]' of N5 Step).
  • the relation block generation unit 26 may express the relation block to be generated as "RBK" and assign an index to each relation block in Step.
  • the relation block [I 0 , I 1 ] can be represented by RBK 0 .
  • N0 Step is expressed as 'RBK 0 I 2 I 3 O 4 ' as shown in FIG.
  • In-step relationship forming unit 27 defines a relationship with other contacts (or relationship blocks) with respect to the contacts (or relationship blocks) in Step. Specifically, the intra-step relationship forming unit 27 defines a previous contact, previous coil, next contact, or next coil of a relation object belonging to each contact or relationship block in the step. In this case, if the index to be included in the previous contact, previous coil, next contact, or next coil belongs to the relation block, 'R' may be indicated before the index to indicate the relation block.
  • Previous Contact, Previous Coil, Next Contact, or Next Coil of one contact (or relation block) if Next Contact or Next Coil is defined, Previous Contact, Previous Coil of the next contact (or relation block) should correspond to it. Can be defined automatically.
  • the Next Contact field of RBK 0 is defined as '2'.
  • the Previous Contact field of I 2 is defined as R 0. Since the next contact of I 2 is I 3 , that is, the input contact, the Next Contact field of I 2 is defined as '3', and the Previous Contact field of I 3 is defined as '2'. Since the next contact of I 3 is O 4 , that is, the output contact, the Next Coil field of I 3 is defined as 4, and correspondingly, the Previous Contact field of O 4 is defined as '3'.
  • the relationship forming unit 28 in the relationship block defines a relationship with other contacts (or relationship blocks) with respect to the contacts (or relationship blocks) included in the relationship block. Specifically, the relationship forming unit 28 in the relationship block defines a previous contact, previous coil, next contact, or next coil of a relation object belonging to each contact or relationship block in the relationship block. If there is a relation block in the relation block, first define the relation to the contacts (or relation blocks) of the outer relation block. Since the internal elements of the relationship block are combined in an OR relationship, the relationship forming unit 28 in the relationship block may distinguish the internal elements based on ",". Each inner element may be referred to as OR 1 , OR 2 , ..., OR n for convenience. 23 shows a format in which the relationship block is divided into internal elements.
  • FIG. 24A illustrates a result of applying RBK 0 illustrated in FIG. 22 to the format of FIG. 23.
  • RBK 0 [I 0 , I 1 ]
  • RBK 0 has I 0 and I 1 as internal elements
  • Next Contact is an index '2'.
  • a Relation object of I 0 is included in OR 1
  • a Relation object of I 1 is included in OR 2
  • Next Contact is represented by an index '2'.
  • the Previous Contact or Previous Coil of the relationship block becomes the Previous Contact or Previous Coil of the first (ie leftmost) contact that is placed for every internal element.
  • the next contact or next coil of the relation block becomes the next contact or next coil of the last (ie rightmost) contact point for all internal elements.
  • the contact becomes the first and last contact (in the case of Fig. 24).
  • both the contact I 0 of the OR1 and the contact I 1 of the OR2 are defined as the index '2'.
  • the relationship forming unit 28 in the relationship block selects the relationship block from the result of defining the relationship between the contacts (or relationship block) for the step. Replace with the contacts included therein.
  • the relationship forming part 28 in the relationship block is defined as 'R #' by the relationship forming part 27 in the step.
  • the contact point that has the relationship block as Previous Contact or Previous Coil
  • the index of the last contact point is defined as Previous Contact or Previous Coil for all internal elements of the relationship block
  • the relationship block is called Next Contact or Next Coil.
  • the index of the first contact is defined as Next Contact or Next Coil for all internal elements of the relation block.
  • FIG. 25 illustrates a result in which all of the relationships between the corresponding input contact or output contact and another input contact or output contact are expressed with respect to each input contact or output contact of the NO step.
  • N5 Step between blocks is represented by the RBK 0 [I 0 I 1, [I 2, I 3] I 4], the relationship block in the RBK 0 [I 2, I 3 ] is represented by RBK 1, between the block [O 6 , I 7 O 8 ] may be represented by RBK 2 .
  • the Next Contact field of RBK 0 is defined as '5'
  • the Previous Contact field of I 5 is correspondingly defined as R0.
  • the next contact of I 5 is RBK 2
  • the Next Contact field of I 5 is defined as 'R2'
  • the Previous Contact field of RBK 2 is defined as '5'.
  • FIG. 28 shows the results of applying RBK 0 and RBK 1 shown in FIG. 27 to the format of FIG. 23.
  • the contact of the I 0 is defined as a "1" Next Contact field of the I 0 Since I 1, I correspond be defined as one of the Previous Contact field is '0' it. Since the next contact of RBK 1 is I 4 , the Next Contact field of RBK 1 is defined as '4' and the Previous Contact field of I 4 is defined as 'R1'. RBK 0 is Next Contact index "5" Because this Next Contact of I 1 contacts placed at the end of the OR1 is defined as a '5', the last Next Contact the junction of I 4 is placed in OR2 also '5' Is defined as
  • next contact is defined as the index '4' for both the contact I 2 of OR1 and the contact I 3 of OR2.
  • FIG. 29 shows a result of replacing RBK 1 in RBK 0 with I 2 and I 3 included in the contacts in FIG. 28.
  • I 4 since I 4 has RBK 1 as a previous contact and the last contact point of all internal elements of RBK 1 is I 2 and I 3 , as shown in FIG. 29, the previous contact of I 4 is '2, 3'. To be redefined.
  • Figure 30 shows the results of replacing with a, the relationship between the contact point included in the definition RBK 0, i.e. 0 RBK of the RBK 29 0 of Fig.
  • I 5 has a RBK 0 to RBK 0 to Previous Contact and the RBK Since the last contact point of all the internal elements of 0 I 1 and I 4, as shown in Fig. 30 I 5 Previous Contact is redefined as '1, 4.'
  • FIG. 31 shows a result of applying RBK 2 shown in FIG. 27 to the format of FIG. 23.
  • RBK 2 [O 6 , I 7 O 8 ]
  • RBK 2 has O 6 and I 7 O 8 as internal elements
  • Previous Contact is '5'. Therefore, as shown in FIG. 31, a Relation object of O 6 is inserted into OR 1 , and a Relation object of I 7 O 8 is contained in OR 2 , Previous Contact is represented by index '5'.
  • the Next Coil field of I 7 is defined as '8', and correspondingly, the Previous Contact field of O 8 is defined as '7'.
  • RBK 2 is because the Previous Contact index "5", the contact O 6 placed at the beginning of the OR1 Previous Contact is defined as a '5', the contacts I 7 placed at the beginning of the OR2 Previous Contact is also defined as a '5' do.
  • Figure 32 shows the results of replacing with a, the relationship between the contact point included in the definition RBK 2, i.e. RBK 2 of the RBK 2 of Fig. 30 Fig. 31. 30 and 31, since I 5 has RBK 2 as a next contact and the first contact point of all internal elements of RBK 2 is O 6 and I 7 , the next contact of I 5 as shown in FIG. 32. Is redefined to '7' and Next Coil to '6'.
  • FIG. 33 is structure data finally generated through the above process, in which the relations are defined in the objects of FIG. 18 for each contact point of N0 Step as shown in FIG. 25 and each contact point of N5 Step as shown in FIG. Represents the structure data that reflects the result of defining relations.
  • FIG. 34 is a flowchart of a method of converting a common PLC control program into structure data according to an embodiment of the present invention.
  • the method according to the present embodiment consists of the steps processed in the structure data converting apparatus described above. Therefore, even if omitted below, the above description of the structure data converting apparatus also applies to the method according to the present embodiment.
  • the common instruction library building unit 11 constructs a common instruction library by generating common instructions for instructions used in text-based PLC control programs having different formats.
  • the class library building unit 21 includes a class library including a rung of the PLC control program, a class for an input contact, an output contact, and a class for expressing a relationship between a corresponding contact and another contact for each contact. Build.
  • step 130 the common format converting unit 13 converts the text-based PLC control program into a common PLC control program using the common command library.
  • step 140 the structure generating unit 22 establishes a relationship between the rung, the input contact and the output contact of the PLC control program of the common type, the corresponding contact for each contact, and the other contact, based on the class library. Create structure data containing the objects to represent.
  • Combinations of each block of the block diagrams and respective steps of the flowcharts attached to the present invention may be performed by computer program instructions.
  • These computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment such that instructions executed through the processor of the computer or other programmable data processing equipment may not be included in each block or flowchart of the block diagram. It will create means for performing the functions described in each step.
  • These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, and thus the computer usable or computer readable memory.
  • instructions stored in may produce an article of manufacture containing instruction means for performing the functions described in each block or flowchart of each step of the block diagram.
  • Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions that perform processing equipment may also provide steps for performing the functions described in each block of the block diagram and in each step of the flowchart.
  • each block or step may represent a portion of a module, segment or code that includes one or more executable instructions for executing a specified logical function (s).
  • a specified logical function s.
  • the functions noted in the blocks or steps may occur out of order.
  • the two blocks or steps shown in succession may in fact be executed substantially concurrently or the blocks or steps may sometimes be performed in the reverse order, depending on the functionality involved.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Manufacturing & Machinery (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Programmable Controllers (AREA)

Abstract

La présente invention concerne un appareil de conversion d'un programme de contrôle de CPL en données structurées qui est caractérisé en ce qu'il comprend : une unité de construction de bibliothèque de classe pour la construction d'une bibliothèque de classe incluant des échelons et des classes pour chaque point parmi un point de contact d'entrée et un point de contact de sortie du programme de contrôle de CPL ; et une unité de génération structure pour la réception d'entrée d'un programme de contrôle de CPL à format commun qui est converti à partir d'un programme de contrôle de CPL à base textuelle, et la génération de données structurées incluant des échelons et des objets pour chaque point parmi un point de contact d'entrée et un point de contact de sortie du programme de contrôle de CPL à format commun, sur la base de la bibliothèque de classe.
PCT/KR2017/008728 2016-08-12 2017-08-11 Appareil et procédé de conversion de programme de contrôle de cpl en données structurées WO2018030831A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201780049616.XA CN109643100B (zh) 2016-08-12 2017-08-11 用于将plc控制程序转换为结构化数据的设备和方法

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2016-0102809 2016-08-12
KR20160102809 2016-08-12
KR10-2017-0101465 2017-08-10
KR1020170101465A KR102004456B1 (ko) 2016-08-12 2017-08-10 Plc 제어 프로그램을 구조체 데이터로 변환하는 장치 및 방법

Publications (1)

Publication Number Publication Date
WO2018030831A1 true WO2018030831A1 (fr) 2018-02-15

Family

ID=61163218

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/008728 WO2018030831A1 (fr) 2016-08-12 2017-08-11 Appareil et procédé de conversion de programme de contrôle de cpl en données structurées

Country Status (1)

Country Link
WO (1) WO2018030831A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704396A (zh) * 2019-09-26 2020-01-17 中国人民解放军军事科学院军事医学研究院 毒物信息库的建立方法、信息检索方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100904557B1 (ko) * 2008-11-20 2009-06-25 주식회사 이글루시큐리티 이기종 방화벽 통합관리시스템 및 방법
JP2010020635A (ja) * 2008-07-11 2010-01-28 Nippon Reliance Kk プログラミング言語変換装置、変換方法及び変換プログラム
KR20120095513A (ko) * 2011-02-21 2012-08-29 성균관대학교산학협력단 Ｐｌｃ 기반 제어 코드를 ｘｍｌ 인터페이스를 이용하여 범용 프로그램 코드로 변환하는 방법 및 프레임워크 시스템
JP2013161106A (ja) * 2012-02-01 2013-08-19 Omron Corp サポート装置およびサポートプログラム
KR101627769B1 (ko) * 2015-12-17 2016-06-08 주식회사 유디엠텍 Ｐｌｃ 제어 프로그램의 공용형식 변환장치 및 방법

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010020635A (ja) * 2008-07-11 2010-01-28 Nippon Reliance Kk プログラミング言語変換装置、変換方法及び変換プログラム
KR100904557B1 (ko) * 2008-11-20 2009-06-25 주식회사 이글루시큐리티 이기종 방화벽 통합관리시스템 및 방법
KR20120095513A (ko) * 2011-02-21 2012-08-29 성균관대학교산학협력단 Ｐｌｃ 기반 제어 코드를 ｘｍｌ 인터페이스를 이용하여 범용 프로그램 코드로 변환하는 방법 및 프레임워크 시스템
JP2013161106A (ja) * 2012-02-01 2013-08-19 Omron Corp サポート装置およびサポートプログラム
KR101627769B1 (ko) * 2015-12-17 2016-06-08 주식회사 유디엠텍 Ｐｌｃ 제어 프로그램의 공용형식 변환장치 및 방법

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110704396A (zh) * 2019-09-26 2020-01-17 中国人民解放军军事科学院军事医学研究院 毒物信息库的建立方法、信息检索方法、装置及电子设备

Similar Documents

Publication Publication Date Title
WO2017104934A1 (fr) Dispositif et procédé de conversion de type commun de programme de commande d'automate programmable
EP3735662A1 (fr) Procédé de réalisation d'apprentissage d'un réseau neuronal profond et appareil associé
WO2018082484A1 (fr) Procédé et système de capture d'écran pour dispositif électronique, et dispositif électronique
WO2017047884A1 (fr) Serveur de reconnaissance vocale et son procédé de commande
WO2019168315A1 (fr) Procédé de rendu graphique de zone de confiance et dispositif d'affichage utilisant celui-ci
WO2017111197A1 (fr) Système et procédé de visualisation de mégadonnées pour l'analyse d'apprentissage
WO2020032655A1 (fr) Procédé d'exécution d'une fonction basée sur la voix et dispositif électronique le prenant en charge
WO2023153821A1 (fr) Procédé de compression d'un modèle de réseau neuronal et appareil électronique pour sa mise en œuvre
WO2022131521A1 (fr) Dispositif d'entrée comprenant un écran tactile et son procédé de fonctionnement
WO2018030831A1 (fr) Appareil et procédé de conversion de programme de contrôle de cpl en données structurées
EP3030960A1 (fr) Procédé d'affichage et dispositif électronique associé
WO2014189236A1 (fr) Procédé de compression d'image sans perte et de restauration, et appareil le réalisant
WO2021194089A1 (fr) Procédé pour changer l'interface utilisateur graphique d'un bloc de circuit, et support de stockage lisible par ordinateur doté d'un programme enregistré comprenant des instructions pour effectuer chaque étape d'un procédé destiné à changer l'interface utilisateur graphique d'un bloc de circuit
WO2019074185A1 (fr) Appareil électronique et procédé de commande associé
EP3659073A1 (fr) Appareil électronique et procédé de commande associé
WO2021002724A1 (fr) Appareil électronique et procédé de commande associé
WO2016165211A1 (fr) Appareil de multiplication modulaire de montgomery et puce de sécurité incorporée dotée de celui-ci
WO2023158133A1 (fr) Procédé et programme informatique pour fournir une interface d'édition pour un contenu traduit
WO2020213885A1 (fr) Serveur et son procédé de commande
WO2022203387A1 (fr) Système et procédé de développement intégrés, pour plate-forme d'interface utilisateur, comportant un compilateur de sources
WO2022203381A1 (fr) Système et procédé de développement de plateforme d'interface utilisateur intégrée, de type d'application à une seule page
WO2022131723A1 (fr) Procédé pour offrir une fonction de lecture et de recherche de dessin, et dispositif et système associés
WO2024005590A1 (fr) Dispositif de mise à l'échelle d'image et procédé de mise à l'échelle d'image
WO2017032119A1 (fr) Procédé et appareil pour mettre en correspondance une image schématique de mise à l'échelle avec un registre de mise à l'échelle
WO2015102266A1 (fr) Processeur et son procédé de commande

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17839848

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28.06.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17839848

Country of ref document: EP

Kind code of ref document: A1