WO2016087149A1

WO2016087149A1 - Method for overwriting a non-volatile memory of a field device

Info

Publication number: WO2016087149A1
Application number: PCT/EP2015/075501
Authority: WO
Inventors: Immanuel Vetter; Niels DONKERS; Endre LÀZÁR
Original assignee: Endress+Hauser Gmbh+Co. Kg
Priority date: 2014-12-04
Filing date: 2015-11-03
Publication date: 2016-06-09
Also published as: DE102014117905A1

Abstract

The invention relates to a method for overwriting a non-volatile memory of a field device with an application-specific firmware, wherein the method comprises the following steps: a. preparing an operating device for overwriting the non-volatile memory, wherein a device description file, which describes the entirety of the functionalities of the field device, is made available on the operating device; b. deriving/selecting a subset of functionalities from the entirety of the functionalities that is available for the field device, which functionalities are described in the device description file, c. creating an application-specific firmware on the basis of the subset of functionalities, d. overwriting the non-volatile memory of the field device with the application-specific firmware, such that the field device can perform an application-specific task on the basis of the application-specific firmware written into the non-volatile memory.

Description

Method for overwriting a non-volatile memory of a

field device

The invention relates to a method for overwriting a non-volatile memory of a field device.

In automation technology, in particular in process automation technology, field devices are often used which serve to detect and / or influence process variables. Sensors for measuring process variables include fill level gauges, flowmeters, pressure and temperature measuring devices, pH redox potential measuring devices, conductivity meters, etc., which record the respective process variables level, flow, pressure, temperature, pH or conductivity. Actuators, such as valves or pumps, are used to influence process variables

Flow of a liquid in a pipe section or the level can be changed in a container. Field devices are in principle all devices that are used close to the process and the

provide or process process-relevant information. In the context of the invention, field devices are thus understood to mean, in particular, also remote I / Os, radio adapters or in general devices which are arranged on the field level. A variety of such field devices is manufactured and sold by the company Endress + Hauser. In modern process plants, communication between at least one higher-level unit and the field devices generally takes place via a bus system, such as Profibus® PA, Foundation Fieldbus® or HART®. The bus systems can be designed both wired and wireless. The higher-level unit is used for process control, process visualization, process monitoring and commissioning and operation of the field devices and is also referred to as a configuration / management system. Programs based on parent

Units run independently, are for example the operating tool or operating program FieldCare the company group Endress + Hauser, the Pactware operating tool, Fisher-Rosemount AMS operating tool or Siemens PDM operating tool. Operator tools integrated into control system applications include Siemens' PCS7, ABB's Symphony, and Emerson's Delta V. The term 'operation of field devices' in particular the configuration and parameterization of field devices, but also the diagnosis for the early detection of errors to the

Field devices or understood in the process.

Such field devices in this case include electronics with a computing unit, for example. A microprocessor on which or runs a firmware that is used for controlling and regulating the field device. This firmware is created by the field device manufacturers and corresponding to the field device

embedded. The firmware includes all possible functionalities of the field device, completely independent of what application-specific tasks are later considered with the field device.

The field device is thus supplied by the field device manufacturers with a firmware that is completely overloaded for later use. In order to configure a field device which is to be integrated in a process plant for its intended function (also called parametrizing), the operating tools or operating devices or also operating programs already described above are used. Since not all field devices offer the same functionality, especially with field devices from different field device manufacturers, these diverge

Functionalities, on the part of the field device manufacturers for each field device, a so-called device description or device description file (Engl.

Device Description; short: DD). This device description file describes all device functions and thus includes the entirety of the

Functionalities of the respective field device. The device description file can be stored in the field device or on an external data medium. An operator panel extracts the data for configuration or parameterization of the

Field device required information from the device description file. This makes it possible to use different field devices from different manufacturers across platforms with a single operator panel.

To create a common descriptive language for creating such device description files for field devices, the Fieldbus Foundation (FF), the HART Communication Foundation (HCF) and the

Profibus user organization (PNO) a uniform electronic

Device Description Language (EDDL). The EDDL or the corresponding Electronic Device Description EDD is defined in the standard IEC 61804-2.

In order to simplify the flexible use of the field devices in different systems, the measured values must already be processed in the field device by means of extensive functions. This requirement is essentially determined by a full, i. the totality of

Realized functionalities of a field device-containing firmware, which is typically extended over time with additional features.

This leads to the fact that the firmware is relatively large in terms of their memory requirements and thus an appropriate memory must be present in the field device.

In addition, a large firmware (with a lot of functionality) also requires a faster computing power, which in turn leads to an increased energy demand, which is very limited in field devices, especially in two-wire field devices or battery-powered field devices. Alternatively, while maintaining the "current" computing power, processing a relatively large firmware results in a reduction in processing speed

Create field device resources saving firmware and overwrite this in a field device. The object is achieved by a method for overwriting a non-volatile memory of a field device with a

application-specific firmware, the method comprising the following steps:

a. Prepare a HMI device to overwrite the non-volatile memory, where on the HMI device

Device Description File (English: Device Description) is made available, which is a set of functionalities of the

Field device describes;

b. Deriving / selecting a subset of functionalities from the totality of the field device available

Functionalities described in the device description file, c. Creation of an application-specific firmware on the basis of

Subset of functionalities;

d. Overwriting the application-specific firmware in the non-volatile memory of the field device, so that the field device based on the written into the non-volatile memory

application specific firmware is capable of a

perform application-specific task.

According to the invention for a specific purpose or

Use case firmware created. For this purpose, a device description file describing the field device with regard to all its functionalities is used, and the functionalities required for the specific application or use case are filtered out and then a

application-specific firmware created.

The term "firmware" generally refers to a program or software that has functions for controlling and regulating the

Field device contains.

In contrast to the known from the prior art modular software strategies that describe a full firmware, the firmware according to the teaching of the invention by adapting to a reduced specific application or application. This offers the advantage that the one needed for the application-specific firmware

Memory requirement is reduced. In addition, even the

Execution speed compared to running a

full firmware increased.

According to an advantageous embodiment of the invention

Method is provided that a check of the overwriting of the application-specific firmware in the non-volatile memory of the field device is performed.

According to a further advantageous embodiment of the method according to the invention, it is provided that a smartphone or a portable computer, in particular a tablet, is used as the operating device.

According to a further advantageous embodiment of the method according to the invention, it is provided that at least the method step of

Overwriting the application-specific firmware in the non-volatile memory during commissioning of the field device in one

Automation system is performed. In particular, it is provided that at the time of commissioning and before overwriting the

application-specific firmware in the non-volatile memory no firmware has been written to the non-volatile memory.

The term commissioning refers to the first intended use of the field device. This typically takes place when integrating the field device in an existing automation system.

According to a further advantageous embodiment of the method according to the invention it is provided that make available to the

Device description file on the HMI device

Communication connection is established to a server and the

Device description file from the server to the HMI device

is downloaded. In particular, it is provided that a check and / or update of the application-specific firmware is performed is, in which case an information about the application-specific firmware from the field devices is read out, based on the information, an assignment of the used for creating the application-specific firmware device description file is performed and used to create the application-specific firmware

Device description file is performed with the device description file or device description files on the server and in the event that on the server a new or more recent

Device description file is present, a new application-specific

Firmware is created based on the new or current device description file and in the non-volatile memory of the field device

is overwritten.

In accordance with a further advantageous embodiment of the method according to the invention, it is provided that the application-specific firmware is generated via a linker which compiles object files which were generated via a compiler.

The invention will be explained in more detail with reference to the following drawings. It shows:

1 is a schematic representation of the prior art,

Fig. 2: a schematic representation of the invention.

Figure 1 shows a schematic representation of the prior art. The basic structure of field devices 2 is essentially always the same. These include a sensor and / or actuator unit 8 for measuring or setting a process variable, an I / O unit 9 for connecting the field device to a field bus, an input / output unit 10, for example a touch screen, for obtaining information from the fieldbus Field devices 2 read or enter and a main electronics 1 1, which produces the necessary electrical connections between the individual units and performs the necessary control and / or regulation of the individual units. For this purpose, the main electronics 1 1 a Computing unit 12 on which a firmware is executed, which was previously written in a non-volatile memory of the field device.

On the part of the field device manufacturer, a complete firmware 3a is generated, which controls and controls the field device 2 for all of its

Functions regardless of the later application-specific task. This full-scale firmware 3a, which maps all functionalities of the field device 2, is in turn written by the field device manufacturer into the non-volatile memory 1 of the field device 2. Upon delivery of the field device 2 are thus all possible functionalities, ie the entirety of the functionalities 6 of the field device 2 fixed. In other words, the set of field device 2 available

Functionalities support the entire principal scope of the field device 2, regardless of the intended purpose. The field device 2 with all its functionalities is then configured or parameterized after commissioning in an automation system to the application-specific task, so that usually only a fraction of the

Functionalities is actively used. Since the subset of the functionalities used 7 can be very different and the respective function should be as general as possible, almost every function has an extensive parameter set by means of which the respective function can be configured. For example, a flowmeter has the functionality "measure mass", the

Functionality "Measure density" and / or "Measure temperature". By means of specific parameters, these functionalities can be activated or deactivated on the one hand, but can also be configured accordingly in the case that they are activated. Thus, to come back to the previous example, it can be assumed that a specific

Flow meter for an application-specific task measures the mass and density, whereas the temperature is not measured. For this application-specific task, the full firmware 3a, in which all three functionalities are implemented, is overloaded. In FIG. 1, this assignment of functionality and parameters or

Parameter set indicated in the right box, in which, for example, the

Functionality a has the parameters a1 and a2. In this case, for example, the functionality a "measure temperature" represent and on the parameter a1, this can be activated, whereas via the parameter a2 whose unit, for example. Kelvin or degrees Celsius, is set.

Fig. 2 shows a schematic representation of the invention. Here, the essential structure of the field device is the same as previously described.

According to the invention, however, the firmware differs in the non-volatile memory is different. This is adapted to an application-specific task.

The method according to the invention for writing the application-specific firmware into the non-volatile memory 1 of the field device 2 comprises the following steps: a. Prepare an operating device 4 for overwriting the non-volatile memory 1. For this purpose, on the HMI device 4 a

Device description file 5 made available, for example, in which this is downloaded by means of the operating device 4 from a server on which the latest device description files are provided by the field device manufacturer. It is also conceivable, however, that these are manually, i. from an operator on the HMI device 4 is played.

The device description file 5 includes, as described above, all device functions and thus the entirety of the functionalities 6 of the respective field device 2, which were known or possible at the time of creation of the device description file 5 for the corresponding field device 2. Since the hardware of the various field devices or field device types normally differs, there are also different ones for each field device or field device type

Device description files 5. Accordingly, it is available make sure that the device description file 5 on the HMI device 4 to ensure that a matching to the field device 2

Device description file 5 is made available. This can take place either manually, ie in which the operator based on his knowledge of the field device 2, the corresponding

Device description file 5 makes available or in which an automatic detection, for example. By electronic readout of an identification code of the field device is performed. This

Identification code can, for example, represent the serial number of the field device 2, and is typically stored on a so-called "Electronic Name Plate" (ENP for short) of the field device 2. The ENP also represents a non-volatile memory, in which for the corresponding field device 2 b. The next step of the method according to the invention provides that a subset of functionalities 7 from the one described in FIG

Device description file 5 described entirety of

Functionalities 6 is selected or derived, the

Configuration of the field device 2 for a specific

Purpose or for the application-specific use of the field device 2 are required. c. In the subsequent step, an application-specific firmware 3b is created on the basis of the previously selected or derived subset of functionalities 7. In this case, according to the selection made previously, the application-specific firmware 3b has only a part of the functionalities in the device description file 5

described functionalities and is therefore, as far as their size or memory requirements, significantly lower than a well-known from the prior art full-scale firmware 3a, all described in a device description file 5 functionalities

reflects.

In the next step, the application-specific firmware 3b is written into the non-volatile memory 1 of the field device 2, so that the field device 2 is able to perform an application-specific task on the basis of the application-specific firmware 3b written in the non-volatile memory 1. e. In one of the inventive method in terms of

Increasing the security advantageous optional step, a check of the overwriting of the application-specific firmware in the non-volatile memory of the field device 2 is performed.

Typically, this adaptation of firmware 2 will be on-site, i. during commissioning of the field device in an automation system instead. In this case, the field device points to performing the

inventive method still no firmware on or no firmware has been written to the non-volatile memory.

For transmitting or "flashing" as it is also called, it is advantageous if a portable computer or a smartphone is used as the operating device 4. Examples of such a portable computer is a tablet or even a laptop.

In addition to performing the procedure when commissioning the

Field device, it is also conceivable that the method also in advance, i. before the field device 2 is integrated into the automation system, is carried out and / or that a part of the method step is performed before the actual startup of the field device 2 and a part thereafter.

Furthermore, it has proved to be particularly advantageous if a

Checking and / or updating the application-specific firmware 3b is performed. For this purpose, after establishing a connection to the field device 2 by means of the control unit 4, an information on the application-specific firmware 3b, for example. A version number, read from the field devices 2. This information may, for example, also be stored in the ENP or written in the application-specific firmware 3b be easy to read out. Based on this information, an association of the device description file 5 used to create the application-specific firmware 3b can be performed. Subsequently, via the operating device 4, a check used to create the application-specific firmware 3b

Device description file, with the server located on the

Device description files 5 and in the event that the server is a new or more recent device description file, a new application-specific firmware based on the new or

current device description file. This is then in turn overwritten in the non-volatile memory of the field device 2.

Regarding the creation of the application-specific firmware 3b

wherein the application specific firmware 3b via a linker, the

Object files created by a compiler are generated. As a linker understood a computer program that brings together individual program module to an executable program.

LIST OF REFERENCE NUMBERS

Non-volatile memory

field device

firmware

control unit

Device description file

Totality of functionalities

Subset of functionalities

Sensor and / or actuator unit

I / O unit

Input / output unit

server

Claims

claims

1 . Method for overwriting a non-volatile memory (1) of a field device (2) with an application-specific firmware (3b), the method comprising the following steps:

a. Preparing an operating device (4) for overwriting the non-volatile memory (1), wherein on the operating device (4) a

Device Description File (English: Device Description) is made available that a whole of the functionalities (6) of the

Field device (2) describes;

b. Deriving / selecting a subset of functionalities (7) from the totality of the totality available for the field device (2)

Functionalities (6) in the device description file (5)

are described

c. Creating an application specific firmware (3b) based on the subset of functionalities (7);

d. Overwriting the application specific firmware (3b) in the

non-volatile memory (1) of the field device (2), so that the field device (2) is capable of using the application-specific firmware (3b) written in the non-volatile memory (1)

perform application-specific task.

2. The method of claim 1, wherein a check of the overwriting of the application-specific firmware (3b) in the non-volatile memory (1) of the field device (2) is performed.

3. The method of claim 1 and / or 2, wherein a smartphone or a portable computer, in particular a tablet, is used as the operating device (4).

4. The method of claim 3, wherein at least the step of overwriting the application-specific firmware (3b) in the non-volatile memory (1) during commissioning of the field device (2) is performed in an automation system.

5. The method of claim 4, wherein at the time of commissioning and before overwriting the application-specific firmware (3b) in the non-volatile memory (1) no firmware in the non-volatile memory (1) has been written.

6. The method according to one or more of the preceding claims, wherein for making available the device description file (5) on the operating unit (4) a communication link to a server (1 1) is established and the device description file (5) from the server (1 1) is downloaded to the HMI device (4).

7. The method of claim 6, wherein a review and / or

Updating the application-specific firmware (3b) is carried out, for which purpose information about the application-specific firmware (3b) is read out of the field device (2), wherein based on the information, an assignment of the device description file (5) used to create the application-specific firmware (3b) and the device description file (5) used for creating the application-specific firmware (3b) is executed with the device description file or device description files located on the server (11) and in the event that a new one is created on the server (11) or more recent device description file is present, a new

application specific firmware (3b) based on the new or

current device description file is created and overwritten in the non-volatile memory (1) of the field device (2).

8. The method according to one or more of the preceding claims, wherein the application-specific firmware (3b) via a linker, which compiles object files that were created via a compiler is generated.