CN116088411A - Version management method and device of PLC system - Google Patents

Version management method and device of PLC system Download PDF

Info

Publication number
CN116088411A
CN116088411A CN202310115835.0A CN202310115835A CN116088411A CN 116088411 A CN116088411 A CN 116088411A CN 202310115835 A CN202310115835 A CN 202310115835A CN 116088411 A CN116088411 A CN 116088411A
Authority
CN
China
Prior art keywords
version
plc
lower computer
engineering
plc engineering
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.)
Pending
Application number
CN202310115835.0A
Other languages
Chinese (zh)
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.)
Shanghai Flexem Technology Co ltd
Original Assignee
Shanghai Flexem 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 Shanghai Flexem Technology Co ltd filed Critical Shanghai Flexem Technology Co ltd
Priority to CN202310115835.0A priority Critical patent/CN116088411A/en
Publication of CN116088411A publication Critical patent/CN116088411A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/054—Input/output
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • 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
    • G05B2219/00—Program-control systems
    • G05B2219/10—Plc systems
    • G05B2219/11—Plc I-O input output
    • G05B2219/1103—Special, intelligent I-O processor, also plc can only access via processor
    • Y—GENERAL 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a version management method of a PLC system, which belongs to the technical field of engineering management, and comprises the following steps: judging whether the upper computer supports the current PLC engineering version, if not, upgrading the upper computer version, and if so, loading and compiling the PLC engineering; judging whether the lower computer firmware version supports the PLC engineering version, if so, issuing the PLC engineering to the lower computer firmware, and if not, upgrading the lower computer firmware version or updating the PLC engineering version and then issuing the lower computer; judging whether the lower computer firmware version is within the range of the maximum version and the minimum version of the firmware version supported by the current issued PLC engineering, if so, successfully issuing the current PLC engineering, if the lower computer firmware version is smaller than the minimum version, upgrading the lower computer firmware version, and if the lower computer firmware version is larger than the maximum version, upgrading the PLC engineering version. The stability of the PLC system can be improved by the scheme.

Description

Version management method and device of PLC system
Technical Field
The invention relates to the technical field of PLC engineering, in particular to a version management method and device of a PLC system.
Background
The PLC is widely applied in the field of automation, and because of continuous iterative updating of a development environment, the development environment of the upper computer software needs to be updated in time, and the problem that new and old versions cannot be compatible possibly occurs after the software is updated. And an upper computer controls a plurality of lower computers, so that the optimization and upgrading of the functional logic are more and more frequent, and the lower computer program is required to be upgraded in order to achieve a better operation effect.
Most of the PLC upper computers belong to equipment special, some manufacturers strongly bind the PLC upper computers with the lower computers, and release independent software aiming at different versions of the lower computers, so that development and maintenance cost is increased. And the functions among different versions are not consistent, the version upgrade is difficult, and a user needs to ensure that the upper computer, the lower computer firmware and the PLC engineering are the same version, so that the system can work normally. Some manufacturers unbind the upper computer and the lower computer of the PLC and respectively develop and manage the upper computer and the lower computer independently, but the upper computer and the lower computer of the PLC have inconsistent functions in practical application.
Therefore, a version management method of a PLC system is needed, which can ensure the compatibility and consistency of versions among a PLC project, an upper computer and a lower computer, and improve the working stability of the PLC system.
Disclosure of Invention
In view of the above problems, the present solution provides a version management method of a PLC system, which can reduce the dependency between the upper computer and the lower computer and improve the stability of the operation of the PLC system by separately managing the version information of the upper computer, the lower computer and the PLC engineering and labeling the differences between each version.
According to a first aspect of the present invention, there is provided a version management method of a PLC system, including: firstly, acquiring a current PLC engineering version, judging whether the upper computer supports the current PLC engineering version, if not, upgrading the upper computer version, and if so, loading and compiling the PLC engineering. And secondly, after the upper computer is connected with the lower computer, judging whether the lower computer firmware version supports the PLC engineering version, if so, issuing the PLC engineering to the lower computer firmware, and if not, upgrading the lower computer firmware version or updating the PLC engineering version and then issuing the lower computer firmware again.
And finally, judging whether the lower computer firmware version is within the maximum version and the minimum version of the firmware version supported by the currently issued PLC engineering, if the lower computer firmware version is within the maximum version and the minimum version, the current PLC engineering is successfully issued, if the lower computer firmware version is smaller than the minimum version, the lower computer firmware version is upgraded, and if the lower computer firmware version is larger than the maximum version, the PLC engineering version is upgraded.
By the technical scheme, whether the upper computer supports the current version of the PLC engineering is judged in the process of creating or loading the PLC engineering, if so, loading and compiling of the PLC engineering are completed, and if not, the version of the upper computer is upgraded, so that the upgraded upper computer can support the current PLC engineering, and loading and compiling of the PLC engineering are completed.
In the process of issuing the PLC engineering to the lower computer, judging whether the lower computer firmware is in the version range supported by the PLC engineering of the current version, if so, completing the issuing of the PLC engineering, and if not, upgrading the lower computer firmware or after upgrading the version of the PLC engineering, and then compiling again to complete the issuing of the PLC engineering.
Therefore, the method and the device can reduce the cost of the version management of the PLC system, independently manage the versions of the upper computer and the lower computer, reduce the dependence of the upper computer and the lower computer, and solve the problems of the function of the upper computer and the release of the firmware of the lower computer.
Optionally, in the method, a relational database is used to store version information of the upper computer and version information of the lower computer, where the version information of the upper computer includes an upper computer version number, a PLC engineering version number supported by the upper computer version number, and a lower computer firmware version number; the version information of the lower computer comprises a lower computer firmware version number, and a maximum version number and a minimum version number of the lower computer firmware version supported by the PLC engineering version number.
By respectively storing, managing and labeling the version information of the upper computer and the version information of the lower computer, the dependency of version release between the lower computer and the lower computer can be reduced.
Optionally, in the method, the upper computer includes a version configuration document, and the version configuration document includes a maximum version and a minimum version of the lower computer supported by the PLC engineering version, an instruction protocol configuration document, a hardware configuration document, a drive configuration document, a peripheral configuration document, and a template configuration document.
Optionally, in the above method, the instruction protocol configuration document includes a system built-in instruction, the hardware configuration document includes a CPU main body, a digital quantity expansion module, an analog quantity expansion module, an internet of things expansion module, and an expansion board, the driving configuration document includes driving configuration information, the peripheral configuration document includes peripheral configuration information, and the template configuration document includes compiling related information.
Optionally, in the method, based on the PLC engineering version, loading instructions, hardware, drivers and peripherals supported by the PLC engineering version from the version configuration document to complete loading of the PLC engineering; and acquiring template configuration from the template configuration document, compiling the PLC engineering based on the corresponding compiler, and generating a PLC engineering issuing file.
Alternatively, in the above method, the PLC engineering may be created and modified based on the version configuration document in the upper computer.
Through the version configuration document provided by the upper computer, a user can create a new PLC project or modify the PLC project according to own project requirements, and the function update of the lower computer is completed.
Optionally, in the method, the version number of the upper computer is updated after the version upgrade of the upper computer is completed, the firmware version number is updated after the firmware version upgrade of the lower computer is completed, and the PLC engineering version number is updated after the PLC engineering version upgrade is completed; and labeling the difference among each version of the upper computer, the lower computer and the PLC engineering.
According to another aspect of the present invention, there is provided a version management apparatus of a PLC system, wherein the PLC system includes an upper computer and a lower computer, the apparatus comprising: the device comprises a first judging module, a second judging module and a third judging module.
The first judging module is used for judging whether the upper computer supports the current PLC engineering version after acquiring the current PLC engineering version, if not, upgrading the upper computer version, and if so, issuing the PLC engineering to the lower computer.
And the second judging module is used for judging whether the lower computer firmware version supports the current PLC engineering version after the upper computer is connected with the lower computer, if so, issuing the PLC engineering to the lower computer firmware, and if not, upgrading the lower computer firmware version or updating the PLC engineering version and then issuing the lower computer again.
And the third judging module is used for judging whether the firmware version of the lower computer is within the range of the maximum version and the minimum version of the firmware version supported by the current issued PLC engineering, if the firmware version of the lower computer is within the range of the maximum version and the minimum version, the current PLC engineering is issued successfully, if the firmware version of the lower computer is smaller than the minimum version, the firmware version of the lower computer is upgraded, and if the firmware version of the lower computer is larger than the maximum version, the PLC engineering version is upgraded.
Optionally, the device further comprises a storage module, wherein the storage module is used for storing version information of the upper computer and version information of the lower computer by adopting a relational database, and the version information of the upper computer comprises an upper computer version number, a PLC engineering version number supported by the upper computer version number and a lower computer firmware version number; the version information of the lower computer comprises a lower computer firmware version number, and a maximum version number and a minimum version number of the lower computer firmware version supported by the PLC engineering version number.
Optionally, the device further comprises an updating module, wherein the updating module is used for updating the version number of the upper computer after the version upgrading of the upper computer is completed, updating the firmware version number after the version upgrading of the lower computer is completed, updating the PLC engineering version number after the version upgrading of the PLC engineering is completed, and marking the difference between different version numbers.
According to the scheme of the invention, whether the upper computer supports the current version of the PLC engineering is judged in the process of creating or loading the PLC engineering, if so, loading and compiling of the PLC engineering are completed, and if not, the version of the upper computer is upgraded, so that the upgraded upper computer can support the current PLC engineering, and loading and compiling of the PLC engineering are completed.
In the process of issuing the PLC engineering to the lower computer, judging whether the lower computer firmware is in the version range supported by the PLC engineering of the current version, if so, completing the issuing of the PLC engineering, and if not, upgrading the lower computer firmware or after upgrading the version of the PLC engineering, and then compiling again to complete the issuing of the PLC engineering.
Therefore, the method and the device can reduce the cost of the version management of the PLC system, independently manage the versions of the upper computer and the lower computer, reduce the dependence of the upper computer and the lower computer, and solve the problems of the function of the upper computer and the release of the firmware of the lower computer.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 shows a flow diagram of a version management method 100 of a PLC system according to one embodiment of the invention;
FIG. 2 illustrates a flow diagram of a host computer creating or loading a PLC project according to one embodiment of the invention;
FIG. 3 is a schematic flow chart of a host computer issuing a PLC project to a lower computer according to an embodiment of the invention;
fig. 4 illustrates a schematic structure of a version management apparatus 400 of a PLC system according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The upper computer in the PLC system is a computer monitoring system, the lower computer is a field execution controller, and the upper computer and the lower computer are both required to be programmed and have special development systems. The upper computer and the lower computer can ensure the normal work of the PLC system only by the firmware versions or the functions of the upper computer and the lower computer being consistent.
In order to reduce the development cost of a PLC system, reduce the dependence between an upper computer and a lower computer and improve the stability of PLC engineering, the scheme provides a version management method of the PLC system, which can independently manage the upper computer, the lower computer firmware and the PLC engineering version, mark the difference between each version, reduce the dependence between the upper computer and the lower computer, finish the version update of the PLC engineering, the upper computer and the lower computer firmware and ensure the stability and the safety of the PLC system.
Fig. 1 shows a flow diagram of a version management method 100 of a PLC system according to an embodiment of the present invention. As shown in fig. 1, the method 100 starts with step S110, where a current PLC engineering version is obtained, it is determined whether the upper computer supports the current PLC engineering version, if not, the upper computer version is upgraded, and if so, the PLC engineering is loaded and compiled.
According to one embodiment of the invention, all the PLC engineering versions and the lower computer versions supported by the version are defined in the upper computer version, and the maximum version (the latest version) and the minimum version of the lower computer firmware version supported by each PLC engineering version are defined in the upper computer version. The upper computer can create the corresponding version of the PLC engineering according to the definition, and can open and edit the corresponding version of the PLC engineering according to the supported version of the PLC engineering.
The version information of the upper computer and the version information of the lower computer can be stored by adopting a relational database, and the version information of the upper computer comprises an upper computer version number, a PLC engineering version number supported by the upper computer version number and a lower computer firmware version number; the version information of the lower computer comprises a lower computer firmware version number, and a maximum version number and a minimum version number of the lower computer firmware version supported by the PLC engineering version number.
When loading the PLC engineering, in order to ensure the consistency of the PLC engineering and the version of the upper computer, the upper computer firstly judges whether the current version of the PLC engineering to be loaded is supported, if so, the PLC engineering is directly opened, the instruction, the hardware, the driver, the peripheral equipment and the like which are stored in the version configuration file in the upper computer and used for creating or loading the PLC engineering are loaded, and a user can select the instruction, the hardware, the driver and the peripheral equipment of the corresponding version to finish the creation or loading of the corresponding version of the PLC engineering.
Fig. 2 shows a schematic flow chart of a host computer creating or loading a PLC project according to an embodiment of the present invention. As shown in fig. 2, the upper computer may create or load a PLC project, and when creating a PLC project, may select a PLC project version to be created, and then load instructions, hardware, drivers, peripherals, etc. for creating the PLC project based on the corresponding PLC project version. And adding a PLC hardware module, an instruction, a functional module and the like which are supported by the corresponding version.
The upper computer comprises a version configuration document, and the PLC engineering version which is allowed to be created or opened by the upper computer can be determined according to the version configuration document. The version configuration document of the upper computer also comprises the version range of the lower computer firmware supported by each PLC engineering version, namely the maximum version and the minimum version of the lower computer firmware.
Specifically, the version profile contains an instruction protocol profile, a hardware profile, a driver profile, a peripheral profile, and a template profile that are supported by the PLC engineering version.
The instruction protocol configuration document details all the system built-in instructions supported by the version, such as a bit logic instruction, a comparison instruction, a conversion instruction, a counter instruction, a data block instruction, a logic control instruction and the like. The hardware configuration document lists the PLC hardware supported by the version in detail and comprises hardware information such as a CPU main body, a digital quantity expansion module, an analog quantity expansion module, an Internet of things expansion module, an expansion board and the like. The driver configuration document details the driver configuration information supported by the version. The peripheral configuration document details peripheral configuration information supported by the version, such as input and output devices, storage devices, monitoring devices, programming devices, and the like. The template configuration document details the compiling related information used by the version for the user to compile the PLC engineering of the corresponding version.
When loading an existing PLC project, the upper computer first checks whether the opening of the version of the PLC project is supported. If the support is opened, the PLC engineering is normally loaded, and instructions, hardware, drivers, peripherals and the like corresponding to the support of the version are loaded based on the version of the PLC engineering, so that the user can modify the PLC engineering. And if the opening is not supported, prompting the user to update the current upper computer version so as to open the PLC engineering of the current version.
When compiling the PLC engineering, the template configuration document can be obtained based on the version of the PLC engineering, the PLC engineering is compiled based on the corresponding compiler, and the PLC engineering issuing file is generated so as to issue the compiled PLC engineering to the lower computer based on the PLC engineering issuing file.
And step S120 is executed, after the upper computer is connected with the lower computer, whether the lower computer firmware version supports the PLC engineering version is judged, if so, the PLC engineering is issued to the lower computer, and if not, the lower computer firmware version is upgraded or the PLC engineering version is updated and then issued to the lower computer again.
After the upper computer finishes loading and compiling of the PLC engineering, the lower computer needs to be connected to finish issuing of the PLC engineering. Fig. 3 is a schematic flow chart of a host computer issuing PLC engineering to a lower computer according to an embodiment of the present invention. As shown in fig. 3, after the upper computer is connected with the lower computer, the firmware version of the lower computer and the PLC engineering version currently running can be obtained through the open interface of the lower computer. The lower level opportunity automatically detects and judges whether the firmware version supports the currently issued PLC engineering version. If not, an abnormal warning is sent out, and a user is prompted to update the firmware version or to update the PLC engineering version and then to issue the PLC engineering again.
The lower computer judgment logic can effectively solve the problem of version mismatch caused by the fact that a user switches the lower computer firmware version or the PLC engineering version by himself.
And finally, executing step S130, judging whether the lower computer firmware version is within the range of the maximum version and the minimum version of the firmware version supported by the currently issued PLC project, if so, successfully issuing the current PLC project, if the lower computer firmware version is smaller than the minimum version, upgrading the lower computer firmware version, and if so, upgrading the PLC project version.
When the upper computer issues the PLC engineering to the lower computer, the maximum version and the minimum version of the firmware version of the lower computer supported by the current PLC engineering version can be obtained. Then, judging whether the lower computer firmware version is within the range of the maximum version and the minimum version of the lower computer firmware version supported by the PLC engineering, and if so, successfully issuing the PLC engineering. If the lower computer firmware version is not in the range of the lower computer firmware version supported by the PLC engineering, continuing to judge whether the lower computer firmware version is smaller than the minimum firmware version allowed by the PLC engineering.
If the lower computer firmware is smaller than the minimum firmware version allowed by the PLC engineering, the lower computer firmware is not supported and needs to be upgraded. If the firmware version of the lower computer is higher than the maximum firmware version allowed by the PLC engineering, the lower computer is not supported, the PLC engineering version needs to be updated at the moment, and the updated PLC engineering is recompiled and then issued to the lower computer.
Updating the version number of the upper computer after the version upgrading of the upper computer is completed, updating the firmware version number after the version upgrading of the lower computer is completed, and updating the PLC engineering version number after the version upgrading of the PLC engineering is completed. And labeling the difference among each version of the upper computer, the lower computer and the PLC engineering in the relational database.
According to the technical scheme provided by the invention, whether the upper computer supports the current version of the PLC engineering is judged in the process of creating or loading the PLC engineering, if so, loading and compiling of the PLC engineering are completed, and if not, the version of the upper computer is upgraded, so that the upgraded upper computer can support the current PLC engineering, and loading and compiling of the PLC engineering are completed.
In the process of issuing the PLC engineering to the lower computer, judging whether the lower computer firmware is in the version range supported by the PLC engineering of the current version, if so, completing the issuing of the PLC engineering, and if not, upgrading the lower computer firmware or after upgrading the version of the PLC engineering, and then compiling again to complete the issuing of the PLC engineering. Therefore, the method and the device can reduce the cost of the version management of the PLC system, independently manage the versions of the upper computer and the lower computer, reduce the dependence of the upper computer and the lower computer, and solve the problems of the function of the upper computer and the release of the firmware of the lower computer.
Fig. 4 illustrates a schematic structure of a version management apparatus 400 of a PLC system according to an embodiment of the present invention, and as shown in fig. 4, the version management apparatus 400 includes a first judgment module 410, a second judgment module 420, and a third judgment module 430.
The first determining module 410 may determine whether the upper computer supports the current PLC engineering version after obtaining the current PLC engineering version, if not, upgrade the upper computer version, and if so, load and compile the PLC engineering.
According to an embodiment of the present invention, the apparatus 400 further includes a storage module, where the storage module may store version information of the upper computer and version information of the lower computer by using a relational database, where the version information of the upper computer includes an upper computer version number, a PLC engineering version supported by the version number, and a lower computer firmware version; the version information of the lower computer comprises a firmware version number, and a maximum version number and a minimum version number of the lower computer firmware version supported by the PLC engineering version. And the device 400 further comprises an updating module for updating the version number in the relational database and labeling the difference between different versions after the version of the upper computer or the lower computer firmware or the PLC engineering is updated.
The first determining module 410 may determine whether the upper computer supports the current PLC engineering version according to the upper computer version information stored in the storage module. And if the software upgrade package is not supported, acquiring the software upgrade package of the upper computer from the server, writing the data of the software upgrade package into the upper computer, and updating the version number of the upper computer.
The second judging module 420 may be configured to judge whether the firmware version of the lower computer supports the current PLC engineering version after the upper computer and the upper computer are connected, for example, the upper computer may be connected to the lower computer through an RS485 bus or an RS232 bus, if so, issue the PLC engineering to the lower computer firmware, and if not, upgrade the lower computer firmware version or update the current PLC engineering version and issue the updated PLC engineering version to the lower computer again.
The third judging module 430 may obtain the minimum version and the maximum version range of the lower computer firmware version supported by the currently issued PLC engineering version, judge whether the lower computer firmware version is between the minimum version and the maximum version range, and issue the PLC engineering to the lower computer if the lower computer firmware version is between the minimum version and the maximum version. If the lower computer firmware version is smaller than the minimum firmware version supported by the PLC engineering, upgrading the lower computer firmware version, and if the lower computer firmware version is larger than the maximum firmware version supported by the PLC engineering, upgrading the PLC engineering version.
According to the version management method and device of the PLC system, the versions of the upper computer, the lower computer firmware and the PLC engineering are adjusted and upgraded in real time when the PLC engineering is loaded and issued according to the differences among different versions of the upper computer, the lower computer and the PLC engineering, so that the consistency and stability of the functions of the PLC system are ensured.
And judging whether the upper computer supports the current version of the PLC engineering or not in the process of creating or loading the PLC engineering, if so, completing the loading and compiling of the PLC engineering, and if not, upgrading the version of the upper computer, so that the upgraded upper computer can support the current PLC engineering, and completing the loading and compiling of the PLC engineering.
In the process of issuing the PLC engineering to the lower computer, judging whether the lower computer firmware is in the version range supported by the PLC engineering of the current version, if so, completing the issuing of the PLC engineering, and if not, upgrading the lower computer firmware or after upgrading the version of the PLC engineering, and then compiling again to complete the issuing of the PLC engineering.
Therefore, the method and the device can reduce the cost of the version management of the PLC system, independently manage the versions of the upper computer and the lower computer, reduce the dependence of the upper computer and the lower computer, and solve the problems of the function of the upper computer and the release of the firmware of the lower computer.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment, or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into a plurality of sub-modules.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.
Furthermore, some of the embodiments are described herein as methods or combinations of method elements that may be implemented by a processor of a computer system or by other means for performing the functions. Thus, a processor with the necessary instructions for implementing a method or a method element forms a means for implementing the method or the method element. Furthermore, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is for carrying out the functions performed by the elements for carrying out the objects of the invention.
As used herein, unless otherwise specified the use of the ordinal terms "first," "second," "third," etc., to describe a general object merely denote different instances of like objects, and are not intended to imply that the objects so described must have a given order, either temporally, spatially, in ranking, or in any other manner.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments are contemplated within the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is defined by the appended claims.

Claims (10)

1. The version management method of the PLC system comprises an upper computer and a lower computer, and is characterized by comprising the following steps:
acquiring a current PLC engineering version, judging whether the upper computer supports the PLC engineering version, if not, upgrading the upper computer version, and if so, loading and compiling the PLC engineering;
after the upper computer is connected with the lower computer, judging whether the lower computer firmware version supports the PLC engineering version, if so, issuing the compiled PLC engineering to the lower computer firmware, and if not, updating the lower computer firmware version or updating the PLC engineering version, and then, issuing the lower computer firmware again;
judging whether the lower computer firmware version is within the maximum version and the minimum version of the firmware version supported by the current issued PLC engineering, if so, successfully issuing the current PLC engineering, if the lower computer firmware version is smaller than the minimum version, upgrading the lower computer firmware version, and if the lower computer firmware version is larger than the maximum version, upgrading the PLC engineering version.
2. The version management method according to claim 1, characterized in that the method comprises:
the method comprises the steps that a relational database is used for storing version information of an upper computer and version information of a lower computer, wherein the version information of the upper computer comprises an upper computer version number, a PLC engineering version number supported by the upper computer version number and a lower computer firmware version number; the version information of the lower computer comprises a lower computer firmware version number, and a maximum version number and a minimum version number of a lower computer firmware version supported by the PLC engineering version number.
3. The version management method according to claim 1, wherein the upper computer contains a version configuration document, and the version configuration document contains a maximum version and a minimum version of a lower computer supported by a PLC engineering version, an instruction protocol configuration document, a hardware configuration document, a drive configuration document, a peripheral configuration document and a template configuration document.
4. The version management method according to claim 3, wherein the instruction protocol configuration document contains a system built-in instruction, the hardware configuration document contains configuration information of a CPU main body, a digital quantity expansion module, an analog quantity expansion module, an internet of things expansion module and an expansion board, the driving configuration document contains hardware driving configuration information, the peripheral configuration document contains peripheral configuration information, and the template configuration document contains PLC engineering compiling related information.
5. The version management method according to claim 4, wherein the step of loading and compiling PLC engineering comprises:
based on the PLC engineering version, loading instructions, hardware, drivers and peripherals supported by the PLC engineering version from the version configuration document to finish loading of the PLC engineering;
and acquiring template configuration from the template configuration document, compiling the PLC engineering based on a corresponding compiler, and generating a PLC engineering issuing file.
6. The version management method according to claim 5, characterized in that the method comprises:
updating the version number of the upper computer after the version upgrading of the upper computer is completed, updating the firmware version number after the version upgrading of the lower computer is completed, and updating the PLC engineering version number after the version upgrading of the PLC engineering is completed; and
the differences between each version of the host computer, the lower computer and the PLC project are noted.
7. The version management method according to claim 5, characterized in that the method comprises:
based on the version configuration document, a PLC project is created and modified.
8. The version management device of a PLC system, the PLC system includes host computer and lower computer, its characterized in that includes:
the first judging module is used for judging whether the upper computer supports the current PLC engineering version after acquiring the current PLC engineering version, if not, upgrading the upper computer version, and if so, loading and compiling the PLC engineering;
the second judging module is used for judging whether the lower computer firmware version supports the current PLC engineering version after the connection between the upper computer and the lower computer is established, if so, the compiled PLC engineering is issued to the lower computer firmware, and if not, the lower computer firmware version is updated or the PLC engineering version is updated and then issued to the lower computer firmware again;
and the third judging module is used for judging whether the lower computer firmware version is within the maximum version and the minimum version of the firmware version supported by the current issued PLC engineering, if the lower computer firmware version is within the maximum version and the minimum version, the current PLC engineering is issued successfully, if the lower computer firmware version is smaller than the minimum version, the lower computer firmware version is upgraded, and if the lower computer firmware version is larger than the maximum version, the PLC engineering version is upgraded.
9. The version management apparatus according to claim 8, further comprising a storage module for storing version information of an upper computer and version information of a lower computer using a relational database, the version information of the upper computer including an upper computer version number, a PLC engineering version number supported by the upper computer version number, and a lower computer firmware version number; the version information of the lower computer comprises a lower computer firmware version number, and a maximum version number and a minimum version number of a lower computer firmware version supported by the PLC engineering version number.
10. The version management device of claim 7, wherein the device further comprises:
the updating module is used for updating the version number of the upper computer after the version upgrading of the upper computer is completed, updating the firmware version number after the version upgrading of the lower computer is completed, updating the PLC engineering version number after the version upgrading of the PLC engineering is completed, and marking the difference between different version numbers.
CN202310115835.0A 2023-02-15 2023-02-15 Version management method and device of PLC system Pending CN116088411A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310115835.0A CN116088411A (en) 2023-02-15 2023-02-15 Version management method and device of PLC system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310115835.0A CN116088411A (en) 2023-02-15 2023-02-15 Version management method and device of PLC system

Publications (1)

Publication Number Publication Date
CN116088411A true CN116088411A (en) 2023-05-09

Family

ID=86210137

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310115835.0A Pending CN116088411A (en) 2023-02-15 2023-02-15 Version management method and device of PLC system

Country Status (1)

Country Link
CN (1) CN116088411A (en)

Similar Documents

Publication Publication Date Title
US10761824B2 (en) Script generation engine and mapping semantic models for target platform
US7966612B2 (en) Method, system and computer program for installing shared software components
CN102057355B (en) Synchronizing virtual machine and application life cycles
CN1174307C (en) Method, system and computer readable storage medium for automatic device driver
US8413134B2 (en) Method, system and computer program for installing software products based on package introspection
CN101937340B (en) Method and device for dynamically updating and controlling software by using patches
US20070157010A1 (en) Configuration templates for different use cases for a system
US8312446B2 (en) Dependency management when upgrading application components
US20070061818A1 (en) Detection of devices during operating system setup
CN106095620A (en) A kind of development approach of built-in Linux partition holding
US20070156715A1 (en) Tagged property files for system configurations
US20070156717A1 (en) Meta attributes of system configuration elements
US20050120344A1 (en) Optimal component installation
JP2000242598A (en) Firmware update system and its updating method
IL166169A (en) Versioning support in object-oriented programming languages and tools
US20050120331A1 (en) Hosting environment abstraction agents
US7188339B2 (en) ACPI preprocessor
CN116088411A (en) Version management method and device of PLC system
CN103064698A (en) Method and apparatus to install software automatically
US6671744B1 (en) Access control method for drive units, and a drive unit using the method
US20060248171A1 (en) Method for adapting software
US7516452B1 (en) Method and system for managing installation of software on a computer system platform
CN100533418C (en) Method and apparatus for modifying the contents of a revision identification register
CN104503789A (en) Version updating control method and ICT (information and communication technology) equipment
US20070226716A1 (en) Software system architecture and application program processing method

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