Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
  • G06F8/64—Retargetable
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment

Definitions

• the invention relates to a method for installing control software for a machine in the tobacco processing industry with a plurality of machine components, which represents a specific configuration from a comprehensive set of principally possible machine components for the machine, the control software comprising a plurality of software components assigned to the machine components, wherein the method is performed using an installation computer program installed on an installation computer.
• the invention further relates to a corresponding software package for the control software.
• Different components of a machine in the tobacco processing industry are controlled with respectively assigned software components.
• machine components can optionally be provided or not; appropriate software components may be required.
• machine components are subject to changes in the course of time, which often require an adjustment of the corresponding software components.
• the machine user When installing software components, the machine user must therefore ensure that he / she installs the right software components in the right combination for the respective machine.
• updated software components are required, for example as a result of a machine rebuild, retrofitting, changed spare parts or a software update.
• the installation, administration and monitoring of the required software components is complex and demanding.
• the object of the invention is to simplify the installation, administration and monitoring of the software components required in each case and to avoid restrictions on machine operation due to outdated or unsuitable software components.
• the installation method provides, in particular, the following steps: setting up access for the installation computer program to a software component collection which includes all possible software components corresponding to all principally possible machine components for the machine; Establishing installation computer program access to target configuration data describing a target configuration of the machine; automatically selecting the software components to be installed from the software component collection based on the target configuration data using the installation computer program; and automatic installation of the selected software components.
• the invention lies in a separation between the super-individual software component collection and the individual target configuration data record.
• An essential part of the invention is a software component collection that includes all possible software components corresponding to all principally possible machine components for the machine, ie including all equipment alternatives, equipment options and changes to machine and / or software components. This means that the software component collection is highly redundant, since only a fraction of all software components contained are actually required or can be used at all in a special machine.
• This part of the software components which is required according to the individual configuration of a particular machine, is described by means of target configuration data. Using the installation software, which has access to both the software component collection and the target configuration data, the software components to be installed are automatically selected from the software component collection on the basis of the target configuration data and installed automatically.
• control software It is no longer necessary for the user to determine or select the software components to be installed, which increases the risk of installing unsuitable software components. reduced or excluded components for a particular machine.
• the management and monitoring of the control software is very simple, since for a certain machine type only a predetermined collection of software components is required instead of an individual compilation of software components for each individual machine.
• Each updated software component collection is then preferably compatible with each previous software component collection.
• each updated software component collection includes each previous software component collection in a functional manner, so that every machine that could be operated with a previous software component collection, ie also a machine with outdated machine components, can also be operated with the updated software component collection.
• a software component collection may therefore contain, for a machine component, a plurality of software components with different dates of origin corresponding, for example, to different spare parts in the machine component. This example illustrates that a plurality of software components in a software component collection can be assigned to a machine component.
• Each software component collection is preferably present in a uniform form, preferably on a uniform data carrier. This increases the clarity for the operator, since he only has to manage a software data carrier for the machine. Furthermore, each software component collection is preferably provided with a marking, such as the creation date or a version number. This simplifies handling, since the operator and the software installation program can compare different software component collections on the basis of the identification and can determine the most current version at first glance.
• Access by the installation computer program to an updated software component collection is set up as required, in particular in the event of changes or retrofitting of machine components.
• the installation computer program can determine that updated software components are required and, if necessary, request an updated software component collection.
• Access by the installation computer program to an updated software component collection can also be expedient if the target configuration remains unchanged, for example for a software update for improved software components.
• the target configuration data are available as a uniform target configuration data record, preferably on a uniform data carrier. This significantly improves handling since, in addition to the software component collection, the operator only needs the target configuration data record, that is to say only two data carriers in total, for the software installation. Independent access to the software component collection and the target configuration data record is preferably set up, since independent access to the software component collection is expediently provided for a software update, for example. This particularly reduces the effort for the software or machine manufacturer.
• the target configuration data record preferably includes a unique machine identification of the machine to be configured. This can reduce the risk of software being incorrectly installed on the wrong machine.
• the target configuration data record preferably includes an indication of the required software component collection. This allows a quick check whether an updated software component collection is needed.
• the target configuration data record preferably contains information about operating and / or functional features of machine and / or software components. This allows the machine manufacturer, for example, to release certain performance features or functions of a machine component when required.
• FIG. 1 is a schematic drawing of an installation computer system for a cigarette production machine
• FIG. 3 is a schematic drawing of a target configuration data storage area
• FIG. 4 is a schematic drawing of a further installation computer system for a cigarette production machine
• FIG. 6 shows a schematic drawing of an updated target configuration data storage area.
• a cigarette production machine 10 has a plurality of machine components 20, 23, ..., for example a nozzle gluing device 20 and a laser 23 for cigarette testing.
• Corresponding memory areas 30, 33, ... are assigned to the machine components 20, 23, ... in the cigarette production machine 10 for storing corresponding software components for controlling the machine components 20, 23, ....
• An installation computer 11 is assigned to the cigarette production machine 10 or comprises one.
• the installation computer 11 is connected to the memory areas 30, 33, ... for software components for data transmission.
• the installation computer 11 has a memory area 15 for an installation computer program, which controls the installation computer 11 to carry out a software installation process.
• the installation computer 11 is connected to a terminal 16 for communication with a machine operator.
• the installation computer system 11, 16 is therefore preferably identical to an already provided computer system which controls the operation of the machine 10 by an operator, for example by means of a graphical user interface for a screen 17 of the terminal 16. Operator inputs can be made, for example, by means of a touch-sensitive screen 17.
• the installation software is preferably an assistant software, ie the operator is guided in a predetermined sequence through a sequence of screen displays in order to simplify operation. Remote actuation of the installation computer 11, for example by the machine manufacturer, is also conceivable.
• the installation computer 11 contains a memory 110 for unambiguous identification of the associated machine 10, in the present example the machine number “344”.
• the memory 110 for the machine identification can also be arranged in the machine 10, for example.
• the installation computer 11 is connected to a memory area 13 for software components and a memory area 14 for configuration data for data transmission.
• the software component and configuration data storage areas 13, 14 can be provided in the installation computer 11, preferably on a hard disk or an optical data carrier. However, this is not absolutely necessary.
• the software component storage area 13 contains a software component collection with software components 40-43, ..., namely a software component 40 for the nozzle gluing device 20, a software component 41 for one that is possible in principle in the machine 10, but here roller gluing device that is not implemented, a software component 42 for a filter ventilation measuring device that is possible in principle in the machine 10, but not implemented here, one Software component 43 for the laser 23, etc., stored.
• the software component collection 40-43, ... therefore contains software components for all possible machine components in the machine 10, although the machine 10, for example, does not need the software components 41, 42 for a roller gluing device or a filter ventilation measuring device.
• Each software component 40-43 comprises an identifier 400, 410, 420, 430, ..., which identifies the associated machine component.
• the content "20" of the identifier 400 means that the software component 40 is assigned to the machine component 20.
• Each software component 40-43 also includes a version number 401, 411, 421, 431, ..., which represents the status of the respective software component. For example, software component 42 with version number "3" is more current than an earlier software component (for the same machine component) with version number "2".
• each software component 40-43 comprises an area 402, 412, 422, 432 with the actual control software for the respectively assigned machine components, and preferably software that is expedient for the operation or operation of the corresponding machine components, for example online help software , Documentation software, graphic display software and / or source software.
• the software components 40-43 for example in the area 402, 412, 422, 423, may also contain information relating to the installation process, for example the route within the machine 10, by which the software components 40-43 go to the corresponding memory areas 30-33 reach.
• a field 130 is also provided in the software component memory area 13, in which a uniform version identifier, which reflects the status of the software component collection 40-43,... Is stored, in the present example the version number “5”.
• configuration data units 50-53 which describe the configuration of the machine 10 are stored.
• a configuration data unit 50, 53 is provided, each comprising a designation 500, 530 for the corresponding machine component.
• the content "43" of the identifier 530 means that the configuration data unit 53 is assigned to the Mader software component 43 and therefore (see field 430) to the machine component 23.
• the configuration data units 50, 53 comprise a field 501, 531 in which, for example the number “1” indicates that the respective machine component 20, 23 is contained in the machine 10.
• this information can also be stored in other ways.
• the configuration data storage area 14 in the present case also includes configuration data units 510, 520 for machine components which are possible in principle but are not contained in the particular machine 10.
• the corresponding fields 511, 521 indicate this, for example, by means of the number “0” contained therein.
• the configuration data storage area 14 contains a field 140 which contains a unique identifier for the machine to be configured, here for example the machine number “344”, and a field 141 which contains the information as to which minimum version of a software component collection the corresponding machine configuration requires. In the present case, a software component collection of version "5" or higher is required.
• the configuration data storage area 14 contains a field 142 which designates a uniform identifier of the machine configuration defined by means of the configuration data in the configuration data storage area 14. In the present example, the configuration has the configuration number "1" for the machines "344".
• the installation computer program in the installation computer 11 provides access to the software component storage area 13 and the configuration data storage area 14.
• the machine identifier 140 stored in the configuration data storage area 14 is compared with the machine identifier stored in the installation computer 11 in the memory 110. In the event of a mismatch, a warning for the operator would be displayed on the screen 17 and confirmation of the operator would be requested as to whether the installation should nevertheless take place.
• the minimum version of a software component collection from the field 141 of the configuration data storage area 14 is then compared with the version information in the field 130 of the software component storage area 13. In the present example, the version “5” of the software component collection satisfies the minimum requirement according to field 141 of the configuration data storage area 14.
• the target configuration is then determined using the information in the configuration data storage area 14, which in the present case comprises, for example, the nozzle gluing device 20 and the laser 23.
• the operator can then preferably be given the opportunity to change the target configuration manually. This can be useful, for example, in order to be able to convert the machine to a desired target configuration in partial steps. For example, the operator can be asked in a corresponding screen mask on the screen 17 whether he accepts the target configuration read out from the configuration data storage area 14 or wishes to make a change.
• Another screen mask is displayed which shows the current target configuration with the option of deactivating selected software components (for example by setting fields 501 or 531 to "0") or activating additional software components (for example by setting fields 511 or 521 to “1").
• These changes are expediently not stored directly in the configuration data storage area 14, but are first temporarily stored in a buffer.
• a button can be provided in a screen mask in order to restore the target configuration stored in the configuration data storage area 14.
• the actual software installation is now carried out automatically by the installation program.
• the selected software components 40, 43 are stored in the configuration data storage area 14 and loaded into the storage areas 30, 33 provided for this purpose, in order to be installed from there in the corresponding machine components 20, 23. Further information on the part of the operator regarding the memory areas 30, 33 or the way in which the software gets there is not necessary, because the installer does this automatically based on the information in the software component collection. If necessary, the previous software components for the machine components 20, 23 are deleted accordingly.
• the machine identifier 140 stored in the configuration data storage area 14 deviates from the machine identifier stored in the installation computer 11 in the memory 110, the machine identifier 140 stored in the configuration data storage area 14 can be transferred to the memory 110 of the installation computer 11. This is particularly important for the initial commissioning or configuration of a machine.
• the software configuration to be installed can be compared with the actual machine configuration. If, for example, it is determined that, due to a change by the operator, a software component 41, 42 is to be installed for a machine component that is not present in the machine 10, this can be done to display a warning on the screen 17 or to block the installation of the software component 41, 42 lead.
• the target configuration data record 14 can preferably also contain details of operational and / or functional features of machine and / or software components.
• the intended machine speed or production speed is specified in a field 143 of the target configuration data record 14.
• the operating mode or component function to be implemented in the machine 10 can be set by means of the target configuration data set 14.
• Additional functions or features, such as performance features, can be activated by the machine manufacturer as required. Such features can be protected, i.e. they cannot be changed manually by the operator or the machine user, for example via the terminal 17.
• FIGS. 4 to 6 exemplarily describe the case of a change that requires the installation of updated software components. It is assumed that in In comparison to machine 10 from FIG. 1, machine 10 from FIG. 4 has a different configuration, namely includes an additional filter ventilation measuring device 22. Furthermore, it is assumed that an improved version "2" has been created for the software component 40, which is also to be used in the machine 10 according to FIG. 4.
• the software manufacturer usually the machine manufacturer, therefore first creates the updated software component collection shown in FIG. 5, in which the improved software component 40A contains the improved software in the area 402A.
• Field 401 shows the changed version number "2" of the improved software component 40A.
• the software component collection with the improved software component 40A contains the version number "6" which is entered in the field 180.
• the software component collection with the version number “6” is stored on a uniform data carrier 18, preferably an optical data carrier, for example a CD-ROM, and transmitted to the machine user.
• the machine manufacturer also creates the updated target configuration data record shown in FIG. 6.
• the field 521 contains a "1" for the newly installed filter ventilation measuring device 22.
• the field 192 contains the configuration number "2" for the machine configuration changed compared to the configuration with the configuration number "1".
• the minimum version is "6" for the software component collection is indicated, since the improved version "2" of the software component 40 was not yet included in the version "5" of the software component collection (see FIG. 2).
• the machine number "344" in field 190 remains unchanged.
• the changed target configuration data record is stored on a uniform data carrier 19, preferably an optical data carrier, for example a CD-ROM, and transmitted to the machine user.
• the software component collection with the version number "6" and / or the changed target configuration data record can also be transmitted in another way, for example by means of online access by the machine user to a computer of the machine manufacturer.
• the target configuration data can also be changed manually, for example by means of entries in the terminal 17, in particular by service personnel.
• the machine user provides the installation computer 11 with access to the changed target configuration data record, for example by inserting the data carrier 19 into a corresponding drive.
• the installation computer program on the installation computer 11 can be started automatically, if necessary.
• the machine identifier 190 stored in the configuration data storage area 19 is compared with the machine identifier stored in the memory 110 of the installation computer 11.
• a warning for the operator would be displayed on the screen 17 and confirmation of the operator would be requested as to whether the installation should nevertheless take place.
• the operator is requested to confirm the target configuration stored on the data carrier 19.
• This can include, for example, the display of the previous configuration number "1" from field 142 and the new target configuration number "2" from field 192.
• the previous machine configuration and the new target configuration can be displayed on the data carrier 19 in accordance with the target configuration data record on request.
• the content of the data carrier 19 is preferably first copied to a corresponding memory area 19A arranged in the installation computer so that the actual software installation process can run within the installation computer 11.
• this safety measure is not absolutely necessary; instead, the installation can also be carried out directly from the data carrier 19.
• the storage area 19A is a target target configuration data storage area.
• the information in the memory area 19A is therefore preferably kept unchanged (until a further updated configuration data record is stored) in order to enable installation at any time without using the data carrier 19.
• the required minimum version of the software component collection from the field 191 of the configuration data storage area 19A with the version information is be compared in field 130 of software component storage area 13.
• the version specification “5” in field 130 of software component memory area 13 is lower than the required minimum version “6” according to field 191 of configuration data memory area 19A. Therefore, the operator is alerted to the need for an updated software component collection, for example, by displaying the contents of fields 130 and 191, and is prompted to establish access to an updated software component collection. This can be done, for example, by inserting the data carrier 18 into an appropriate drive. The operator can then be asked to confirm the acceptance of the updated software component collection, for example by specifying the contents of fields 130 (previous version) and 180 (updated version).
• the content of the data carrier 18 is preferably first copied to a corresponding memory area 18A arranged in the installation computer as a security measure.
• this security measure is not absolutely necessary; instead, the installation can also be carried out directly from the data carrier 18.
• the storage area 18A is a target software component storage area.
• the information in the memory area 18A is therefore preferably kept unchanged (until a further updated software component collection is saved) in order to enable installation at any time without using the data carrier 18.
• the operator can preferably be given the opportunity to manually change the target configuration in the target configuration memory 19A. For example, the operator can be asked in a corresponding screen mask on the screen 17 whether he accepts the target configuration read out from the configuration data storage area 19A or wishes to make a change. If the operator confirms a change request by means of the terminal, a further screen mask is displayed which shows the current target configuration with the possibility of deactivating selected software components, for example by setting field 521 to "0" if the filter ventilation measuring device 22 is not yet in the machine 10 is installed, or to activate additional software components. These changes are expediently not stored directly in the configuration data storage area 19 A. stores, but initially cached in a buffer. For example, a button can be provided in a screen mask in order to restore the target target configuration stored in the configuration data storage area 19A.
• the software component 42 from the software component memory area 18A is stored in the software component memory area 13 and loaded into the memory area 32 of the corresponding machine component 22 provided for this purpose.
• the software component 42 from the software component memory area 13 could also be used, because it has remained unchanged, but this would have to be checked additionally.
• the software component 40A For the further relevant software components 40, 43, their version numbers in the fields 401, 431 of the software component memory area 13 are compared with the corresponding version information in the fields 401, 431 of the updated software component memory area 18A. This check results in an updated version of software component 40A (entry “2” in field 401 of updated software component memory area 18A compared to entry “1” in field 401 of previous software component memory area 13). Accordingly, the software component 40A from the updated software component storage area 18A is stored in the software component storage area 13 and loaded into the storage area 30 provided for this purpose in the corresponding machine component 20. The unchanged software component 43 does not have to be reinstalled, which reduces the time required for the installation.
• the software configuration to be installed can be compared with the actual machine configuration (see description of Fig. 1-3).
• the content of the updated software component storage area 18A can be transferred into the software component storage area 13 and the content of the updated configuration data storage area 19A into the configuration data storage area 14, at least insofar as there are changes.
• a pure software update with unchanged machine configuration can be achieved by establishing access to the updated software component collection with the version number “6”, for example by inserting the software component data carrier 18 in a corresponding drive. This allows the updated software component 40A to be installed instead of the previous software component 40 can be achieved.
• the installation computer program can also be started manually without access to an updated software component collection or an updated target configuration data record, for example in order to produce an intended target configuration by manually changing the configuration data record stored in the installation computer.

Applications Claiming Priority (2)

Publications (1)

Family

ID=34683273

Family Applications (1)

Country Status (1)

Cited By (2)

Citations (2)

• 2004
  • 2004-10-28 WO PCT/EP2004/012348 patent/WO2005059740A1/de active Application Filing

Patent Citations (2)

Similar Documents

Legal Events