Method to store programs for operator interface and the management of automation machines and/or plants and corresponding software product, or project format for the execution of the method

Abstract

Project format, suitable to define functions and/or characteristics of an operator interface device or of a PLC of an operating machine, more generally of an industrial device. The project format comprises a base layer and a plurality of additional layers disposed in order on the base layer from the oldest to the newest.

Claims

1. A programmable device, comprising an operator interface stored in a memory for operating an industrial machine, wherein the programmable device is configured to: retrieve a project program from the memory, wherein the project program corresponds to a project format, wherein the project format comprises: a base layer configured to control a first set of functionalities of the operator interface; and a plurality of additional layers, wherein the plurality of additional layers is disposed in a chronological order on the base layer, and wherein each additional layer of the plurality of additional layers is configured to be created dynamically at runtime during execution of the project program; execute the project program; complete execution of the project program; and re-execute the project program, wherein the plurality of additional layers is configured to be dynamically modified at runtime during the re-execution of the project program.

2. The programmable device of claim 1, wherein each additional layer of the plurality of additional layers is associated with an operating step for developing the operator interface.

3. The programmable device of claim 1, wherein each additional layer of the plurality of additional layers is associated with a functional subset of the first set of functionalities of the operator interface.

4. The programmable device of claim 1, wherein a first additional layer of the plurality of additional layers comprises a plurality of operating steps for developing the operator interface disposed in parallel.

5. The programmable device of claim 1, wherein the base layer cannot be modified by another group of developers.

6. The programmable device of claim 1, wherein at least one additional layer of the plurality of additional layers comprises a temporary modification.

7. The programmable device of claim 1, wherein at least one additional layer of the plurality of additional layers comprises a permanent modification.

8. A system for programming a control system for operating an industrial machine, comprising: a processor; and a memory communicatively coupled to the processor, wherein the memory having stored therein computer executable instructions that, when executed by the processor, cause the processor to: retrieve a project program from a storage, wherein the project program corresponds to a project format, wherein the project format comprises: a base layer configured to control a first set of functionalities of an operator interface; and a plurality of additional layers, wherein the plurality of additional layers is disposed in a chronological order on the base layer, and wherein each additional layer of the plurality of additional layers is configured to be created dynamically at runtime during execution of the project program; execute the project program; complete execution of the project program; and re-execute the project program, wherein the plurality of additional layers is configured to be dynamically modified at runtime during the re-execution of the project program.

9. The system of claim 8, wherein each additional layer of the plurality of additional layers is associated with an operating step for developing the operator interface.

10. The system of claim 8, wherein each additional layer of the plurality of additional layers is associated with a functional subset of the first set of functionalities of the operator interface.

11. The system of claim 8, wherein a first additional layer of the plurality of additional layers comprises a plurality of operating steps for developing the operator interface disposed in parallel.

12. The system of claim 8, wherein the base layer cannot be modified by another group of developers.

13. The system of claim 8, wherein at least one additional layer of the plurality of additional layers comprises a temporary modification.

14. The system of claim 8, wherein at least one additional layer of the plurality of additional layers comprises a permanent modification.

15. A method, comprising: retrieving, via a processor, a project program from a storage, wherein the project program corresponds to a project format, wherein the project format comprises: a base layer configured to control a first set of functionalities of an operator interface; and a plurality of additional layers, wherein the plurality of additional layers is disposed in a chronological order on the base layer, and wherein each additional layer of the plurality of additional layers is configured to be created dynamically at runtime during execution of the project program; and executing, via the processor, the project program; completing, via the processor, execution of the project program; and re-executing, via the processor, the project program, wherein the plurality of additional layers is configured to be dynamically modified at runtime during the re-execution of the project program.

16. The method of claim 15, wherein each additional layer of the plurality of additional layers is associated with an operating step for developing the operator interface.

17. The method of claim 15, comprising modifying at least one additional layer of the plurality of additional layers, wherein the modification is temporary.

18. The method of claim 15, comprising modifying at least one additional layer of the plurality of additional layers, wherein the modification is permanent.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) These and other characteristics of the present invention will become apparent from the following description of some embodiments, given as a non-restrictive example with reference to the attached drawings wherein:

(2) FIG. 1 shows a software product, or project format, according to the storage method of the state of the art;

(3) FIG. 2 schematically shows an embodiment of a software product, or project format, according to the storage method of the present invention;

(4) FIG. 3 shows an embodiment of a software product, or project format, according to the storage method of the present invention, wherein some levels are positioned parallel on the same layer.

(5) To facilitate comprehension, the same reference numbers have been used, where possible, to identify identical common elements in the drawings. It is understood that elements and characteristics of one embodiment can conveniently be incorporated into other embodiments without further clarifications.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

(6) The following detailed description is provided by way of example and does not exhaust possible harmless variants or Implementations of the invention.

(7) Embodiments of the present invention concern a project format 10, comprising a base layer 11 and a plurality of additional layers 12.

(8) The base layer 11, in this specific non-restrictive case, includes the main functionalities of the operator interface and serves as a platform for the plurality of additional layers 12 which will progressively optimize the HMI for the specific application.

(9) The plurality of additional layers 12 is disposed on the base in correct, chronologically sequential order, from the oldest to the newest. Each additional layer 12 represents a modification to the operator interface and produces one or more variations of the project with respect to the previous layers.

(10) By way of example, according to a possible solution, each additional layer 12 is associated with an operating step of developing the operator interface.

(11) It should be noted that the present invention does not refer only to the operating steps described above, given by way of example.

(12) According to the invention, the inventive idea can be extended to other development cycles, since the additional layers 12 can be associated with any operating step of the development of the HMI.

(13) A similar argument can be made if the present invention is used for PLC modifications or updates.

(14) Even if the additional layers 12 are designed and disposed sequentially over the base layer 11, the present invention provides the possibility of modifying the base layer 11, or the previous additional layers 12, with a certain degree of flexibility, maintaining the additional layers 12 above unchanged or requiring minimal modifications thereto.

(15) According to a further possible solution, the additional layers 12 already designed cannot be modified by other designers.

(16) The project format 10 thus structured allows to develop different projects, for example HMI but not only, starting from the same base 11.

(17) This approach guarantees the maximum re-use of the various design steps, at the same time ensuring a high flexibility in the development of the operator interface.

(18) According to a possible solution, the project format 10 allows to construct at any moment an additional modification layer 12 above the others, and then delete it.

(19) According to a further possible solution, each additional layer 12 of the project 10 does not involve the modification of the entire set of functionalities of the operator interface, but refers only to a functional subset present therein. The layers 12 thus defined, which belong to the same operating step of the development of the HMI, are positioned parallel on the same layer of the software product 10.

(20) According to a further possible solution, the present invention allows to make both temporary modifications and also persistent modifications, in order to allow the project format 10 to adapt to the different circumstances defined by the specific application case. The project format 10 of the present invention allows to save the modifications with respect to the previous situation of any element of the project, or a functional subset thereof.

(21) According to the present invention, the project format 10 allows to describe a plurality of variations between the layers that the project consists of. In particular, the variations can refer to modifications implemented with respect to the previous project layers and can be created, eliminated or modified during the development of the operator interface. In this regard, a development or storage method can be associated with the project format 10 suitable to interpret said variations and develop the complete project version. The development method according to the present invention provides to start from the base 11 and to progressively dispose the additional layers 12 referring to said variations.

(22) According to a possible embodiment, the storage method according to the invention is suitable to manage layers that insist on independent parts of the project, but which are associated with the same operating step, and which are disposed parallel on the same layer of the project format 10.

(23) The storage method according to the invention is able to understand, through the plurality of variations, whether the modification associated with a determinate layer is significant or not. In fact, in the case of repeated variations it is necessary to simplify the modifications that are overwritten or invalidated by the subsequent ones.

(24) In particular, the method allows to determine whether the modifications introduced are not invalidated by the modifications present in an additional upper layer, so that only the variations significant for the project in its entirety are preserved.

(25) Furthermore, the storage method also intervenes in the case in which the designers modify the base layer 11 or the lower additional layers 12, managing to resolve possible conflicts in the additional layers 12 above.

(26) It is clear that modifications and/or additions of parts may be made to the software product, and to the corresponding storage method, as described heretofore, without departing from the field and scope of the present invention.

(27) It is also clear that, although the present invention has been described with reference to some specific examples, a person of skill in the art shall certainly be able to achieve many other equivalent forms, having the characteristics as set forth in the claims and hence all coming within the field of protection defined thereby.

(28) In the following claims, the sole purpose of the references in brackets is to facilitate reading: they must not be considered as restrictive factors with regard to the field of protection claimed in the specific claims.