CN114721325B - Multi-platform multi-version PLC engineering compatible method - Google Patents

Multi-platform multi-version PLC engineering compatible method Download PDF

Info

Publication number
CN114721325B
CN114721325B CN202210513877.5A CN202210513877A CN114721325B CN 114721325 B CN114721325 B CN 114721325B CN 202210513877 A CN202210513877 A CN 202210513877A CN 114721325 B CN114721325 B CN 114721325B
Authority
CN
China
Prior art keywords
information
engineering
version
module
platform
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN202210513877.5A
Other languages
Chinese (zh)
Other versions
CN114721325A (en
Inventor
陈思宁
胡艳萍
方杰
路达
张�杰
焦志鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aotuo Technology Co ltd
Original Assignee
Aotuo Technology Co ltd
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 Aotuo Technology Co ltd filed Critical Aotuo Technology Co ltd
Priority to CN202210513877.5A priority Critical patent/CN114721325B/en
Publication of CN114721325A publication Critical patent/CN114721325A/en
Application granted granted Critical
Publication of CN114721325B publication Critical patent/CN114721325B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/054Input/output
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/10Plc systems
    • G05B2219/11Plc I-O input output
    • G05B2219/1103Special, intelligent I-O processor, also plc can only access via processor
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

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

Abstract

The invention provides a multi-platform multi-version PLC engineering compatible method, which comprises the steps of firstly capturing engineering information, secondly generating the engineering information into an xml format file to realize multi-platform and multi-version PLC engineering compatibility, and finally exporting the xml format file; the engineering information includes: basic information and module information; the basic information comprises program version information, CPU type information and redundancy state information; the engineering information is generated into an xml format specifically as follows: and carrying out information description storage on engineering information according to the xml structure. The method realizes the compatibility of multi-platform and multi-version PLC engineering by exporting engineering information and generating the engineering information into an xml format file; a multi-platform multi-version PLC engineering compatible method is provided. The method has the advantages that the analysis of the engineering files of the old platform is not required to be realized independently, the version before the upgrading is compatible without extra workload, the engineering files of a plurality of operating system platforms are easily supported, the problem of compatibility of the old version software can be solved, and the compatibility is good.

Description

Multi-platform multi-version PLC engineering compatible method
Technical Field
The invention relates to the technical field of PLC (programmable logic controller), in particular to a method for engineering compatibility of multi-platform multi-version PLC.
Background
The PLC is widely applied in the field of world automation, and is continuously developed along with the business. The functions supported by the PLC programming configuration software are more and more, and meanwhile, applications of more software and hardware platforms are required to be met, for example, the software platforms need to support windows platforms, such as a winner kylin, a Galaxkylin, a condensing platform, a unified letter and other software platforms, such as a winner's desktop, a winner's office and the like. The hardware platform needs to support the X86 platform, the Loongson MIPS platform and the Feiteng ARM63 platform.
The need for continuous upgrades places higher demands on the PLC programmable configuration software. Three problems need to be solved:
1. compatibility problem of software developed by different development environments to the same engineering
The development environment is updated repeatedly, and the software with the same function needs to be replaced. For example, the original PLC configuration software is developed by VC and can only run on windows platform, and the requirement of cross-platform cannot be met. Since older versions of software have been used in the industry for many years, the work of reworking many large projects is significant.
2. Compatibility problem of software developed by the same platform to version before upgrade
The version before compatibility is required after the software upgrade. And the engineering files are stored in a serialization mode, and when the content is added and deleted, the new version cannot be directly compatible with the old version.
3. Compatibility problem of the same engineering on multiple operating system platforms
With the popularization of domestic substitution in industry, the cross-platform implementation of the PLC programming configuration software is imperative. VS also provides plug-in support for developing, building, and even debugging multi-platform Qt applications. Not all software developed by a development environment is cross-platform. How to use the same engineering file on multiple operating system platforms is also a problem to be solved. Aiming at the problem of compatibility of new and old versions of software developed in a replacement development environment, many software is directly not supporting the old version of software.
Compatibility problems among versions of software developed for the same platform. Often, the version number is used as a flag, and differentiated parsing paths are executed according to different versions. The method aims at the compatibility problem of the same project on a plurality of operating system platforms. If the software is not an engineering created by software that supports development across platform development environments, then multi-platform compatibility is not possible.
Disclosure of Invention
The object of the present invention is to solve at least one of the technical drawbacks.
Therefore, an object of the present invention is to provide a method for engineering compatibility of multi-platform and multi-version PLC, so as to solve the problems mentioned in the background art and overcome the defects existing in the prior art.
In order to achieve the above objective, an embodiment of an aspect of the present invention provides a method for multi-platform multi-version PLC engineering compatibility, which includes firstly capturing engineering information, secondly generating the engineering information into xml format files to achieve multi-platform multi-version PLC engineering compatibility, and finally exporting xml format files; the engineering information includes: basic information and module information; the basic information comprises program version information, CPU type information and redundancy state information; the engineering information is generated into an xml format, and specifically, the engineering information is stored in an information description mode according to an xml structure.
Preferably, a first rack is configured for engineering information, the first rack comprises a plurality of sub-racks, each sub-rack comprises a plurality of module nodes, and each module node comprises a plurality of module information; the module information comprises back plate information, CPU information, digital input/output module information, analog input/output module information, high-speed counting module information, communication module information and power module information.
In any of the above aspects, preferably, the engineering information further includes register information, the register information including a plurality of sub-register information, each of the sub-register information including a register point number, a name of the configured point, description information, module address information, and master-slave address information.
In any of the above schemes, preferably, the engineering information further includes task information, the task information includes a main task and a plurality of subtasks, each subtask includes a task main program, and the task main program includes a plurality of task subroutines.
In any of the above schemes, preferably, the engineering information further includes interrupt information, and the interrupt information includes a plurality of timing interrupt information and IO interrupt information;
in any of the above schemes, preferably, the engineering information further includes program information, the program information includes a main program and a plurality of groups, each group includes a plurality of subroutines, each subroutine includes a list and program content, and the subroutines are ladder diagrams or function block diagrams or instruction sheet programs or structured text or sequence control diagrams.
In any of the above schemes, it is preferable that the engineering information further includes data table information including a data type table, a variable table, a function module type table, and a function module instance.
Compared with the prior art, the invention has the following advantages and beneficial effects:
1. according to the multi-platform multi-version PLC engineering compatible method, engineering information is exported and generated into an xml format file so as to realize multi-platform and multi-version PLC engineering compatibility; a multi-platform multi-version PLC engineering compatible method is provided. The method has the advantages that the analysis of the engineering files of the old platform is not required to be realized independently, the version before the upgrading is compatible without extra workload, the engineering files of a plurality of operating system platforms are easily supported, the problem of compatibility of the old version software can be solved, and the compatibility is good.
2. The method for multi-platform multi-version PLC engineering compatibility can be compatible with the same engineering in software developed in the same development environment; the software developed by the same platform can be seamlessly compatible with the project created by the version before upgrading; the same engineering file can run on a plurality of operating system platforms, so that more resource cost is saved.
3. The multi-platform multi-version PLC engineering compatible method is directly compatible with a plurality of large projects, does not need to be reworked, saves a great deal of manpower and time, and abstracts complex engineering information into an xml format; software developed in different development environments is compatible through xml; software under different operating systems shares one engineering file through xml; multi-version compatibility is achieved.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The foregoing and/or additional aspects and advantages of the invention will become apparent and may be better understood from the following description of embodiments taken in conjunction with the accompanying drawings in which:
FIG. 1 is a schematic diagram of a multi-platform multi-version PLC engineering compatible method with engineering information rack according to an embodiment of the invention;
FIG. 2 is a schematic diagram of a sub-register rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 3 is a schematic diagram of a task information rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 4 is a schematic diagram of a configuration of an interrupt message rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 5 is a schematic diagram of a rack for grouping program information in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 6 is a schematic diagram of a ladder diagram rack in a method for engineering compatibility of a multi-platform and multi-version PLC according to an embodiment of the invention;
FIG. 7 is a schematic diagram of a functional module diagram rack in a method for multi-platform multi-version PLC engineering compatibility according to an embodiment of the invention;
FIG. 8 is a schematic diagram of the structure of an instruction sheet program rack in a method for multi-platform multi-version PLC engineering compatibility according to an embodiment of the invention;
FIG. 9 is a schematic diagram of a sequential control diagram rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 10 is a schematic diagram of a data type table rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
FIG. 11 is a schematic diagram of a variable table rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the invention;
fig. 12 is a schematic structural diagram of a functional module type table rack in a multi-platform multi-version PLC engineering compatible method according to an embodiment of the present invention.
Detailed Description
Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative and intended to explain the present invention and should not be construed as limiting the invention.
The compatibility problem of the old version software is solved, and the general method is that the new version and the old version engineering content are completely identical in storage format. This is not possible in many cases in reality, and the new version must be increased or decreased in content from the old version; another approach is that the new version can identify the old version of the engineering content format and convert to its own structure for storage. The engineering storage of the old version software is mostly serialized, and the difference of the new version and the old version causes a plurality of inconveniences caused by the fact that the old version engineering file cannot be identified by the same set of analysis mechanism.
The Qt development environment can meet the cross-platform requirement. The adoption of Qt to develop new programmable configuration software means that the configuration software cannot be directly compatible with the configuration software of the old version.
According to the multi-platform multi-version PLC engineering compatible method, engineering information is firstly captured, secondly, the engineering information is generated into an xml format file to achieve multi-platform multi-version PLC engineering compatibility, and finally, the xml format file is exported; the engineering information includes: basic information and module information; the basic information comprises program version information, CPU type information and redundancy state information; the engineering information is generated into an xml format specifically as follows: and carrying out information description storage on engineering information according to the xml structure.
Furthermore, the engineering information is stored according to the information description of the xml structure, namely at least one rack is configured for the engineering information, and each rack contains different kinds of information.
According to the multi-platform multi-version PLC engineering compatible method, engineering information is exported and generated into an xml format file so as to realize multi-platform and multi-version PLC engineering compatibility; a multi-platform multi-version PLC engineering compatible method is provided. The method has the advantages that the analysis of the engineering files of the old platform is not required to be realized independently, the version before the upgrading is compatible without extra workload, the engineering files of a plurality of operating system platforms are easily supported, the problem of compatibility of the old version software can be solved, and the compatibility is good.
The basic information comprises program version information, CPU type information and redundancy state information;
further, the module information comprises back plate information, CPU information, digital input/output module information, analog input/output module information, high-speed counting module information, communication module information and power module information; the method further comprises configuring a first rack for engineering information, wherein the first rack comprises a plurality of sub-racks, each sub-rack comprises a plurality of module nodes, and each module node comprises a plurality of module information.
And the configured module performs information description storage according to the xml structure. An engineering project may be configured with multiple racks, each of which may be configured with a variety of different modules. The content in the nodes in the different Module (Module) definitions is different. As shown in fig. 1, the engineering information includes a first rack, where the first rack includes a plurality of sub-racks, such as a first sub-rack to an nth sub-rack; each sub-rack comprises a plurality of module nodes, such as a first module node to an nth module node, each module node comprises different module information, and besides the module information, the module information further comprises module definition information (ModuleDef), communication protocol information (ModbusTcpList), serial port information (com), remote IO information (erioslay), ethernet information (Eth) and the like, and the module information can be set and grabbed according to requirements.
As shown in fig. 2, the engineering information further includes register information, the register (Regs) information includes a plurality of sub-register information, each of which includes a register point number (num), a name of a configured point (tagname), description information (descriptor), module address information (moduleAddr) and master-slave address information (masterId), identification code address information (slave id), definition information (defined), and time information (filtTime); the information of each relevant sub-register can be increased or decreased according to the requirement.
As shown in fig. 3, the engineering information further includes task information including a main task and a plurality of sub-tasks, each of the sub-tasks including a task main program, each of the task main programs including a plurality of task sub-programs; for one item, a plurality of task information can be configured as needed, and the invocation of the task main program depends on task allocation. Under the multi-task environment, the main task automatically executes the main task program, circularly executes the main task program and has the lowest priority. Up to 16 task subroutines are supported.
As shown in fig. 4, the engineering information further includes interrupt information including a plurality of timer interrupt information and IO interrupt information; an interrupt is a response and process to an external event or an internal event of the PLC. The PLC supports 5 interrupts, including 4 timed interrupts and 1 IO interrupt.
As shown in fig. 5, the engineering information further includes program information, where the program information includes main programs, each main program includes a plurality of groups, each group includes a plurality of sub programs, each sub program includes a list and program contents, and the sub programs are ladder diagrams or function block diagrams or instruction sheet programs or structured text or sequence control diagrams; the program content is the specific execution steps of the PLC and the like. The main program is used to perform the main steps and the grouping is used to perform each specific branching step.
As shown in fig. 6, a Ladder (LD) is a graphically represented programming language whose instruction syntax is similar to that of a circuit diagram, and using the ladder, the flow of data and current between instructions can be tracked on line. The ladder diagram includes attributes including version numbers and descriptions and events including multiple sub-events including type, location, input and output; different information is input and output, such as name parameters, type parameters and functions.
As shown in FIG. 7, a Functional Block Diagram (FBD) is a graphically represented programming language that includes functional block diagram attributes, enables, and events, the attributes including version numbers and descriptions, the enables including tags, the events including a plurality of sub-events, the sub-events including types, locations, inputs, and outputs; different information is input and output, such as name parameters, type parameters and functions.
As shown in fig. 8, the instruction sheet program (IL) and the Structured Text (ST) are both in text format, and the storage structure is relatively simple. The instruction list program comprises attributes and texts, wherein the attributes comprise version numbers, descriptions and the like, and the structured texts are identical with the instruction list program in structure.
As shown in FIG. 9, the sequence control diagram (SCC) provides a simple graphical process description, which is the most natural language for sequence control, and the corresponding control procedure is completed as long as the sequence control diagram is used to configure the overall process of a control. The storage structure of the SCC contains the data and attributes of the functional blocks and the wires. The sequence control diagram comprises attributes and events, wherein the attributes comprise version numbers, descriptions, passwords and rights, the events comprise a plurality of sub-events, and each sub-event comprises data, colors, positions, inputs and outputs; the data comprises names, addresses, expressions, execution types, execution conditions, call tags, execution tags, delete tags, add tags, instruction tags, start, end, numbers and set values, and the positions comprise x coordinates and y coordinates; the output sub-event includes a parameter name and detection information.
The engineering information further includes data table information including a data type table, a variable table, a function module type table, and a function module instance.
As shown in fig. 10, the data type table is the basis of other data tables. The data type table (DDT) node of the composite type does not need to expand the child node content, so that the xml line number is reduced, and the structure is clearer. The data type table includes a plurality of sub-events, each sub-event including a name, a function declaration, an expression, and the like.
As shown in FIG. 11, a variable table is a set of virtual measurement points for programming of programs such as ladder diagrams, structure text, instruction sheets, and the like. To reduce the xml number of rows, the comment section is stored in an information (info) node list, and the multidimensional and data type table (DDT) type variables store only one backup. The variable table comprises information and total events, wherein the information comprises a plurality of sub-information, and the sub-information comprises an information name, a value and an expression; the total event includes address, event name, function declaration, address, type, tag, size, and offset value.
As shown in fig. 12, a function block type table (DFB) is a model of a custom function block, requiring definition of node contents of input, output/output and variable parts. Each secondary node is equivalent to a node structure of a variable table. Annotation information is stored by the parent node to an information (info) node list, and variables of the multidimensional and data type table (DDT) type store only one backup. The function module type table includes a plurality of total events, each total event including a plurality of events, each event including a plurality of sub-events, each sub-event including a plurality of confidences, each information including a name, a value, and an expression, the sub-events including a name, a function declaration, a type, an expression, and a value.
An example of a functional module is several copies of the functional module, with the xml storage structure consistent with a functional module type table (DFB).
The invention takes the compatible upgrade version of the cross-platform PLC programming configuration software developed by Qt as an example, and the compatible PLC programming configuration software developed by VC and the compatible multi-platform operation as an example are explained. The old version of PLC programming configuration software is developed by Visual C++6.0, and Visual C++ is a powerful Visual software development tool developed by Microsoft in 1993. With the advent of new versions thereof, VC6.0 has failed to meet the needs of the user.
The novel cross-platform PLC programming configuration software adopts a Qt development framework, wherein the Qt development framework is a widely applied development framework, and the cross-platform C++ graphical user interface application development framework developed by Qt company can be used for developing GUI programs and non-GUI programs, such as console tools and servers. Qt is an object-oriented framework that uses special code to generate extensions called meta-object compilers (MetaObject Compiler, moc), and some macros, qt are easily extensible and allow for true component programming.
xml is an extensible markup language that is widely used for data exchange and data storage as a common file format. VC and Qt can well support xml and can read and write xml files.
In the embodiment of the invention, the new software adopts xml as an engineering storage mode. The legacy software exports configuration information in xml format. The xml format file of the new edition imported into the old edition project is loaded into the memory, and then the executable file is generated through compiling. Processing is carried out according to the nodes during the analysis of the engineering information in the xml format, and the problem of dislocation of the serialized storage bytes is avoided, so that the node content added by the new version is compatible; the Qt developed software can share one xml-format engineering file in windows when the winning kylin and the Galaxy kylin system are operated, and can normally operate only by importing the engineering file into the software and compiling the engineering file; in the process of upgrading the Qt developed software, only the xml file stored in the engineering file needs to be read according to the supported content, so that the problem of version compatibility after upgrading in future is solved once and for all.
The invention relates to a multi-platform multi-version PLC engineering compatible method, which comprises the steps of firstly capturing engineering information, including backboard information, module information, register information and program information, capturing data type table, variable table, function module type table, instance table information and the like, secondly, generating the engineering information into an xml format file to realize multi-platform multi-version PLC engineering compatibility, and finally exporting the xml format file; and (3) importing XML analysis by other systems and generating new projects.
According to the method for compatible multi-platform multi-version PLC engineering, the information of the PLC engineering can be completely stored in an xml file. The Xml file can be identified by different platforms and different versions of software, and can be compiled and used only by converting the Xml information into memory information in the software. Thus, the compatibility problem of the PLC engineering generated by different versions of different platforms is solved once and for all.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Although embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives, and variations may be made in the above embodiments by those skilled in the art without departing from the spirit and principles of the invention. The scope of the invention is defined by the appended claims and equivalents thereof.

Claims (1)

1. The method is characterized in that firstly engineering information is grabbed, secondly the engineering information is generated into an xml format file to realize multi-platform and multi-version PLC engineering compatibility, and finally the xml format file is exported; the engineering information includes: basic information and module information; the basic information comprises program version information, CPU type information and redundancy state information; the engineering information is generated into an xml format specifically as follows: carrying out information description storage on the engineering information according to an xml structure;
the module information comprises back plate information, CPU information, digital input/output module information, analog input/output module information, high-speed counting module information, communication module information and power module information; the method further comprises the step of configuring a first rack for the engineering information, wherein the first rack comprises a plurality of sub-racks, each sub-rack comprises a plurality of module nodes, and each module node comprises a plurality of module information;
the engineering information also comprises register information, wherein the register information comprises a plurality of sub-register information, and each sub-register information comprises register points, names of configured points, description information, module address information and master-slave address information;
the engineering information also comprises task information, wherein the task information comprises a main task and a plurality of subtasks, each subtask comprises a task main program, and the task main program comprises a plurality of task subprograms;
the engineering information also comprises interrupt information, wherein the interrupt information comprises a plurality of timing interrupt information and IO interrupt information;
the engineering information also comprises program information, wherein the program information comprises main programs, each main program comprises a plurality of groups, each group comprises a plurality of subroutines, each subroutines comprises a list and program content, and the subroutines are ladder diagrams, functional block diagrams, instruction sheet programs, structured texts or sequence control diagrams;
the engineering information also includes data table information including a data type table, a variable table, a function module type table, and a function module instance.
CN202210513877.5A 2022-05-11 2022-05-11 Multi-platform multi-version PLC engineering compatible method Active CN114721325B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210513877.5A CN114721325B (en) 2022-05-11 2022-05-11 Multi-platform multi-version PLC engineering compatible method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210513877.5A CN114721325B (en) 2022-05-11 2022-05-11 Multi-platform multi-version PLC engineering compatible method

Publications (2)

Publication Number Publication Date
CN114721325A CN114721325A (en) 2022-07-08
CN114721325B true CN114721325B (en) 2024-01-19

Family

ID=82231711

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210513877.5A Active CN114721325B (en) 2022-05-11 2022-05-11 Multi-platform multi-version PLC engineering compatible method

Country Status (1)

Country Link
CN (1) CN114721325B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006243841A (en) * 2005-02-28 2006-09-14 Omron Corp Plc tool device
CN101515167A (en) * 2009-04-07 2009-08-26 大连理工大学 Method for realizing IEC61499 flexible function block by using IEC61131-3 function block
CN108375952A (en) * 2018-03-08 2018-08-07 山东超越数控电子股份有限公司 A kind of PLC continuous functions schema compiler and explain method and apparatus
CN108681444A (en) * 2018-04-12 2018-10-19 华中科技大学 A kind of Soft- PLC configuration development approach based on XML technology
CN110161944A (en) * 2018-03-22 2019-08-23 李舒庆 A kind of programmed method of PLC programming software
CN111767406A (en) * 2019-04-01 2020-10-13 杭州电子科技大学 Knowledge representation method and device for PLC engineering
CN114385133A (en) * 2021-12-27 2022-04-22 杭州电子科技大学 Configuration program and data interactive mapping method of heterogeneous platform of programmable controller

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006243841A (en) * 2005-02-28 2006-09-14 Omron Corp Plc tool device
CN101515167A (en) * 2009-04-07 2009-08-26 大连理工大学 Method for realizing IEC61499 flexible function block by using IEC61131-3 function block
CN108375952A (en) * 2018-03-08 2018-08-07 山东超越数控电子股份有限公司 A kind of PLC continuous functions schema compiler and explain method and apparatus
CN110161944A (en) * 2018-03-22 2019-08-23 李舒庆 A kind of programmed method of PLC programming software
CN108681444A (en) * 2018-04-12 2018-10-19 华中科技大学 A kind of Soft- PLC configuration development approach based on XML technology
CN111767406A (en) * 2019-04-01 2020-10-13 杭州电子科技大学 Knowledge representation method and device for PLC engineering
CN114385133A (en) * 2021-12-27 2022-04-22 杭州电子科技大学 Configuration program and data interactive mapping method of heterogeneous platform of programmable controller

Also Published As

Publication number Publication date
CN114721325A (en) 2022-07-08

Similar Documents

Publication Publication Date Title
EP2169547B1 (en) Compilation model for programmable logic controllers (PLC).
Crnkovic et al. Challenges of component-based development
US20020069400A1 (en) System for reusable software parts for supporting dynamic structures of parts and methods of use
US6965800B2 (en) System of measurements experts and method for generating high-performance measurements software drivers
US5301270A (en) Computer-assisted software engineering system for cooperative processing environments
EP0622714A1 (en) Integrated automation development system and method
CN110109671B (en) Webpack label size and style conversion method and device
WO2001038978A1 (en) Configurable state machine driver and methods of use
US20070198562A1 (en) Method and Apparatus for Ensuring Business Process Integration Capability for one or more Distributed Component Systems in Communication with one or more Legacy Systems
CN1329818C (en) Implement method of the man machine command based on plain text command script files
CN114721325B (en) Multi-platform multi-version PLC engineering compatible method
CN114780154B (en) Method compatible with hardware states of master control boards of different manufacturers
CN115390846A (en) Compiling construction method and device, electronic equipment and storage medium
Lu et al. A UML profile to model safety-critical embedded real-time control systems
CN114938397A (en) Kaitai-based high-efficiency protocol unpacking and packing method, system and readable storage medium
Sarkar et al. Higher-order concurrency for microcontrollers
Lüders et al. Adopting a component-based software architecture for an industrial control system–a case study
CN113126961A (en) Pipeline processing method, device and storage medium
Fischer et al. Conceptual design of an engineering model for product and plant automation
Luders et al. Case study: Componentization of an industrial control system
Wang Component-based performance-sensitive real-time embedded software
Lüders et al. A Component-Based Software Architecture for Industrial Control
US20240184541A1 (en) Method and Apparatus for Executing Workflow Task Across Control Objects
Lüders et al. Experiences with component-based software development in industrial control
Krook et al. Higher-Order Concurrency for Microcontrollers

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant