JP2005534123A - Computer system for configuring firmware for automation equipment - Google Patents

Abstract

The present invention relates to a computer system for configuring firmware for an automation device, where the firmware includes a packet (202), and the system includes a data bank (100) that includes a copy of the automation device firmware data model (102). And input means (106) for materializing entities of the data model and processor means (108) for generating packets for execution of the actualized entities.

Description

  The present invention relates to a method and a computer program for such a configuration.

  From the prior art, so-called open drive regulators and methods for generating software for open drive regulators are known. A drive regulator is understood as a converter device and its software for operating an electric or hydraulic actuator, for example a motor. Particularly known from the prior art are so-called intelligent drives for central and non-central automation. The various components of the facility then take on the task of process control and adjustment in a hierarchical structure.

  For example, the servo converter informs the management system of the corresponding adjustment data via a direct route. If multiple regulators are present in the station, they are connected to each other via a communication bus that serves as a direct data exchange.

  Intelligent drives are also used for special adjustment and control tasks, for example in printing and winding technology. The intelligent drive therefore provides a function that is matched to the application needs by the operation software. For these application-specific requirements, the intelligent drive provides a library of various adjustment and control elements. In that case it is the usual modules of general adjustment and automation technology, process regulators, technology regulators, monitoring / diagnostic algorithms and start-up senders.

  From the prior art, in particular from the corresponding functional description of the manufacturer service document (issued in October 2000), the Siemens drive regulator SIMODRIVE is known. These regulators include drive functions such as limiting for speed / position detection with / without synchronous and asynchronous motors, speed adjustment, operational alarm / alarm response, and four-quadrant current circuit adjustment including diagnostic functions. .

  A method and a device for generating a control program are known from DE 4013960 A1. A control program for controlling a machine tool or a robot includes an actuator program, a step program, and a logic program. The actuator program defines the input / output relationship of each actuator based on the basic operation pattern. The step program defines the stepwise operation of the actuator, and the logic program defines logical conditions such as interlock conditions. The disadvantage of this method is that the actuator program is created in the first step based on the operation or actuation pattern of the actuator, the actuator operation must be created, and the step program is generated based on it. . This method is relatively inflexible, expensive, and unsuitable for distributed and open systems.

  From DE-A 19907604 A1 a graphic user interface is known for starting, installing, configuring and parameterizing a conversion device. Quantities such as operating data and motor characteristic data can be input to the control unit. A parameter set for electronic control that can be parameterized from these values is calculated in the control unit. A graphical user interface indicates these quantities and parameter sets to the user. The disadvantage in that case is that it is only possible to parameterize the firmware given in advance to the topology, but it is not possible to configure the topology of the firmware itself.

  From US Pat. No. 5,516,441 a method for graphically programming a user program in an automated device is known. For this method, there is a firmware that exists on the automation device and that allows the user program created in the graphic to be loaded into the automation technology. In this case, it is disadvantageous that the software development of firmware variation and matching is not supported.

  The present invention provides an improved computer system and corresponding method for configuring firmware for automated equipment.

  The object of the invention is solved by the features of the corresponding independent claims. Preferred embodiments of the invention are given in the dependent claims.

  The present invention allows for efficient configuration of firmware for automated devices, especially with consideration for firmware expansion and changeability. In doing so, it is particularly advantageous that the firmware can be configured to be expandable and scalable with respect to an automated device, for example a drive system.

  This is particularly advantageous for matching and variation development supported by the division of firmware into obvious entities in the drive system. Thereby, the development, extension and care of the software can be distributed, i.e. advantageously carried out by third parties such as manufacturers and OEM customers, for example. At that time, both removal and addition of entities are supported.

  According to the present invention, the firmware configuration is based on a firmware configuration data model, from which a possible firmware topology is generated. The firmware is structured modularly. That is, it consists of so-called packets represented by corresponding entities in the data model.

  Entities can be associated with attributes and other entities such as “alarm blocks” and “parameter blocks” in a preferred manner. Thereby, the relationship between packets and the characteristics of individual packets can be captured. In addition, firmware expansion with new packets is supported. This is because the relationship between existing packets is explicitly visible. Upon packet removal, it can be ensured that no firmware configuration that is not executable or translatable occurs.

  According to a preferred embodiment of the invention, the data model is copied into the data bank. For this purpose, for example, Microsoft Access is suitable. The data bank is thus programmed so that it contains a copy of the automation device's firmware data model.

  The data model entity is then materialized to determine the desired firmware configuration by entering data into the data bank. As a result, a corresponding firmware topology then occurs, i.e., a packet is generated to execute the actualized entity based on the input of data to the databank for actualizing the entity. Preferably each of the packets has an interface so that the various packets can work together and thus form executable software.

  According to a preferred embodiment of the invention, the functions of the individual packets can be embodied after the execution of the actualized entity, i.e. the generation of the firmware topology, i.e. by the packets and their interfaces, respectively. An “envelope” is available for use that can still be embodied.

  According to another preferred embodiment of the present invention, access to the data bank and the data model replicated therein is required for declaring and modifying the data model entity and for the realization of the entity. This is done via a graphical operator interface that allows the data to be entered into the data bank.

  Furthermore, it is particularly advantageous in the present invention that changes in firmware that do not match the data model can be prevented. This is because a corresponding selection of non-matching configurations is not possible at all based on the data model being copied in the data bank.

  Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 shows a computer system for configuring firmware for an automated device. The computer system has a data bank 100 that serves to duplicate the data model of the firmware packet. For example, the data model 102 defines firmware packets for various functions such as current regulators, speed regulators, diagnostic systems, and the like. Firmware packets are stored in the database 104. An example for the data model 102 is further described in detail with reference to FIG.

  Data bank 100 may be accessed via usage interface 106. It is then a graphical usage interface that allows a graphical selection of the configuration based on the data model 102 copied to the data bank 100.

  Through the usage interface 106, those entities, their attributes, and their relationships are picked to determine the firmware configuration for a given application. This is also called realization of the entity of the data model. Data necessary for realization is stored in the database 104.

  After realization, the post processor 108 accesses the database 104 to generate the firmware fragment 110 corresponding to the actual entity of the data model. At that time, for each packet, such firmware fragment 110 having an interface is generated to communicate with other firmware fragments 110. Based on this mutual communication possibility of firmware fragments, executable software is created.

  Alongside firmware fragment 110, post processor 108 also creates online documentation 112 and offline documentation 114 by accessing the corresponding documentation text blocks associated with the entities and chaining them together as documentation. obtain.

  FIG. 2 shows one example for the data model of firmware configuration 200. This firmware configuration consists of n packets 202. Conversely, each packet 202 may belong to a firmware configuration 200 of several meters.

  The packet 202 may be a packet unrelated to the adjustment type (attribute 204). An example of a packet that is independent of the type of adjustment is a firmware function that must be present independent of the adjustment function for an automated device, such as a specific alarm and its similar functions.

  In addition, the attribute 202 corresponds to the packet 202 to indicate that it is an axial packet that is independent of the adjustment type, ie, a firmware packet that relates to one particular axis but is independent of the adjustment type. Can be attached. One example is a firmware packet for the realization of various axis numbers.

  Further, an attribute 208 can be associated with the packet 202. It is an axial packet related to the adjustment type, i.e. a packet relating to the adjustment of a particular axis. In this case it may be, for example, a current regulator, a speed regulator or a position regulator or other regulators in a cascade adjustment.

  In addition, the data model includes an entity alert block 210. Packet 202 then includes a number n of alarm blocks 210. On the other hand, the alarm block 210 may belong to several m different packets 202.

  The data model further includes a parameter block 212 correspondingly associated with the entity for the packet 202.

  Entity Alarm block 210 is further associated with an entity for individual alarm 214 and an entity for parameter block 212 is associated with an entity for individual parameter 216. Further, the entity for alert 214 is associated with the entity for parameter 216 and is also associated with the entity for packet 202.

2 is a diagram for explaining a computer system according to the present invention for configuring firmware. 2 is a diagram of a data model for automation device firmware configuration.

Explanation of symbols

100 Data Bank 102 Data Model 104 Database 106 Usage Interface 108 Post Processor 110 Firmware Fragment 112 Online Documentation 114 Offline Documentation 200 Firmware Configuration 202 Packet 204 Attribute 206 Attribute 208 Attribute 210 Alert Block 212 Parameter Block 214 Alert 216 Parameter

Claims (10)

A computer system for configuring firmware for an automation device, wherein the firmware includes a packet (202),
A data bank (100) containing a copy of the automation device firmware data model (102);
Input means (106) for materializing the entity of the data model;
A computer system comprising processor means (108) for generating a packet for execution of the actualized entity;   The computer system according to claim 1, wherein the automation device is an actuator.   The computer system of claim 1 or 2, wherein the data model includes a first entity for a firmware packet, a second entity for an alert block (210), and a third entity for a parameter block (212).   A first attribute (204) for packets whose data model is independent of the adjustment type, a second attribute (206) for axial packets that are independent of the adjustment type, and a third attribute for axial packets related to the adjustment type. 4. The computer system according to claim 1, further comprising:   5. A computer system as claimed in any one of the preceding claims, wherein the processor means is configured to generate an interface for each packet.   The computer system according to any one of the preceding claims, wherein the processor means is configured to generate on-line documentation (112) and / or off-line documentation (114).   The computer system according to claim 1, wherein the input means has a graphic user interface.   The computer system of claim 7, wherein the graphical user interface is configured to input changes to the data model copied to the data bank. A method for configuring firmware for an automated device, where the firmware includes a packet and includes the following steps:
A copy of the data model (102) of the firmware of the automation device in the data bank (110);
Input of the data model entity realization (106),
Generation of packets for execution of the actualized entity (108)
A firmware configuration method for an automation device having:   A digital memory medium having program means for configuring firmware for an automation device, in particular a computer program product, a diskette, a CD-ROM or a semiconductor memory, the firmware comprising a packet (202), the program means comprising data A digital memory medium configured to copy a firmware data model to a bank (100), to input the realization of an entity of the data model, and to generate a packet for execution of the actualized entity.

Images