DE102021120177A1 - Method for changing calculation data of a field device - Google Patents

Abstract

The invention relates to a method for changing calculation data, in particular of a field device (10). The method has the following steps: sending an interpretable text (22) to the field device (10), the interpretable text (22) having an identification of the calculation data to be changed and a calculation rule; receiving, by the field device (10), the interpretable text (22) and storing the text (22) in a first memory area (12) of the field device (10); converting, by a compiler (14), the interpretable text (22) into a code which can be read by the field device (10); andstoring the machine-readable code in a second memory area (16) of the field device (10).

Description

field of invention

The invention relates to a method for changing calculation data, in particular of a field device. Furthermore, the invention relates to a program element, a computer-readable medium, a compiler, a field device and a use.

background

When automating systems, field devices containing measurement sensors are often used. Examples can include devices for level measurement, limit level determination, flow rate measurement, temperature measurement, pressure measurement and/or other field devices. In at least some cases it may be useful to change certain measurement parameters and/or certain procedures. This can result in an update of all or at least large parts of the field device software. It would be desirable to only have to change small parts of the field device software for an update of measurement parameters in order to be able to carry out such updates at short notice more flexibly and with less effort.

Summary

It is the object of the invention to provide a method with which an update of only parts of the field device software is made possible. This object is solved by the subject matter of the independent patent claims. Further developments of the invention result from the dependent claims and the following description.

• senden eines interpretierbaren Textes an das Feldgerät, wobei der interpretierbare Text eine Identifikation der zu ändernden Berechnungsdaten und eine Berechnungsvorschrift aufweist;
• empfangen, durch das Feldgerät, des interpretierbaren Textes und speichern des Textes in einem ersten Speicherbereich des Feldgeräts;
• wandeln, durch einen Compiler, des interpretierbaren Textes in einen von dem Feldgerät maschinenlesbaren Code;
• speichern des maschinenlesbaren Codes in einem zweiten Speicherbereich des Feldgeräts; und
• während einer Berechnung des Feldgeräts, springen zu dem zweiten Speicherbereich und ausführen des maschinenlesbaren Codes.

One aspect relates to a computer-implemented method for changing calculation data of a field device. The procedure has the following steps:

• sending an interpretable text to the field device, the interpretable text having an identification of the calculation data to be changed and a calculation rule;
• receiving, by the field device, the interpretable text and storing the text in a first memory area of the field device;
• convert, by a compiler, the interpretable text into code machine-readable by the field device;
• storing the machine-readable code in a second memory area of the field device; and
• during a computation of the field device, jump to the second memory area and execute the machine-readable code.

$$\text{FLOW\_1 :=CURRENT\_8*2}\text{.3}$$

Calculation data of a field device can include, for example, parameterization data, calculation constants, calculation parameters, extensions of linearization curves, special parameters, extensions of function parameters, extensions of application parameters, extensions of procedures, bug corrections and/or other data which include a measurement and/or an evaluation of a measurement result of the field device. An interpretable text is a text that is set up so that it can be read by people, ie not machine code, but for example a text containing readable characters of the ASCII code (ASCII: American Standard Code for Information Interchange) and/or others codes included. Examples can be instructions that can be read by interpreters and/or compilers, for example: $$\text{DIST\_1 :=ECHO\_1*3}\text{.7}$$

$$\text{FLOW\_1 :=CURRENT\_8*2}\text{.3}$$

The interpretable text may include elements of a standardized interpreter and/or compiler syntax, and/or a proprietary syntax. The examples shown make it clear that the identifier or an identification - such as "DIST_1", "ECHO_1", etc. - should be "known" to the field device, i.e. that this refers to information on a defined memory area of the field device. The interpretable text can be created, for example, using an editor on a computer. After creation, the interpretable text can, for example, be checked for certain rules, for example whether the defined syntax is adhered to, whether the identifiers, the calculation rules, etc. are defined, and/or other checks. The checks can include a simulation and/or an emulation of the interpretable text in order to enable testing or debugging before the calculation rule or calculation rule of the interpretable text runs on and/or controls or otherwise influences a real field device.

Sending the interpretable text to the field device can be wired or wireless. For example, protocols or interfaces such as 4..20mA protocols, e.g. HART (Highway Addressable Remote Transducer), Profibus PA (Profibus for Process Automation), FF (Foundation Fieldbus), a two-wire Ethernet (e.g. APL [Advanced Physical Layer ]), and others are used, and/or wireless protocols such as LoRa (Long Range), NB-loT (NarrowBand loT), LTE-M (Long Term Evolution for Machines), or telephony protocols such as LTE, GSM, GPRS , UMTS, 2G, 3G, 4G, 5G, and/or others, and/or devices that support these protocols.
The interpretable text is basically readable; however, it can be encrypted, especially for sending.

The field device is set up to support at least one of the protocols mentioned and to receive the interpretable text. In the case of an encrypted text, it can perform a decryption after receiving it. After receiving, the interpretable text is stored in a first memory area of the field device. The conversion of the interpretable text by a compiler can be triggered by receiving and/or by a dedicated command. The compiler converts the interpretable text into code that can be machine-read by the field device. The compiler can be set up to convert the interpretable text "on the fly", i.e. there can be embodiments in which there is no dedicated first memory area in the field device, but instead the interpretable text is forwarded directly to the compiler. The compiler may further be configured to output an error code, e.g., to a display associated with the field device and/or to the device that sent the interpretable text. The error code can include, for example, an indication of a syntax error, an unknown or undefined identification, incorrect or dangerous semantics (which could, for example, disrupt operations of the field device) and/or other messages.

After the interpretable text has been recognized as error-free, converted into machine-readable code and stored in a second memory area of the field device, the (new) machine-readable code can be used for calculations, for control and/or more. In this way, a function, a parameter, in particular a measurement parameter, and/or certain procedures or extensions can be updated in a simple and intuitive manner without having to change the entire field device software. In many cases, the changes can be limited to a small part of the field device software; in particular, the basic software of the field device does not have to be changed in many cases. This can help make an update faster, reduce the likelihood of an error from the update, and/or reduce field device "downtime" during the update.

In many embodiments, the method has the further step of jumping to the second memory area by means of a jump instruction during a calculation of the field device and executing the machine-readable code. The code in the second memory area can then, for example, comprise a calculation which is carried out, for example, during a measurement. In the delivery state, for example, this memory area can only contain one return. A simple and reliable implementation of a modified calculation (etc.) can thus be implemented.

In some embodiments, the branch instruction is only transferred to the second memory area after the machine-readable code has been completely stored in the second memory area of the field device. In the meantime - especially during the update period - the "old" code can continue to be used. The "old" code can, for example, be deleted after the update. These steps can further reduce the downtime of the field device for the update.

In some embodiments, the interpretable text has a syntax from JavaScript, Basic, graphical, possibly memory-optimized programming languages and/or XML. This means that changes to the parameters (etc.) can be made particularly intuitively. Furthermore, by “following” and/or using a known syntax, compilers, interpreters, simulators and/or emulators can be implemented in a simpler way, which can convert the interpretable text into machine-readable code and/or test it outside of a field device.

In some embodiments, sending the interpretable text includes encrypting the text. The update can thus advantageously be protected against unauthorized access, in particular during transmission.

In some embodiments, the interpretable text is received via a wireless interface of the field device. For example, the wireless interface can be configured as a radio module configured to support wireless protocols such as LoRa (Long Range), NB-loT (NarrowBand loT), LTE-M (Long Term Evolution for Machines), or telephony protocols such as e.g. LTE, GSM, GPRS, UMTS, 2G, 3G, 4G, 5G, and/or other short-range protocols such as Bluetooth, or also RFID-based protocols such as NFC (RFID: Radio-Frequency Identification, NFC: Near Field Communication).

In some embodiments, jumping to the second memory area occurs from one of the following locations in field device software: from an input block, from a linearization block, from a scaling block, and/or from a function block. This means that various parts of the field device software can be supported or replaced in a targeted manner.

In some embodiments, a jump back from the second memory area takes place either to a subsequent address of the address of the jump or to a predefined jump label. Entire blocks of field device software can thereby be bypassed or (as a result) changed.

In some embodiments, the compiler is arranged in a third memory area of the field device. The compiler can thus advantageously be part of the field device software and/or be supplied with the field device.

One aspect relates to a field device that is set up to carry out a method as described above and/or below.

One aspect relates to the use of a field device as described above and/or below for fill level measurement, limit level determination, flow rate measurement, pressure measurement and/or temperature measurement.

One aspect relates to a compiler for a field device as described above and/or below.

One aspect relates to a program element which, when it is executed on a field device as described above and/or below and/or on another processing unit, instructs the field device and/or the processing unit to carry out the method as described above and/or below.

One aspect relates to a computer-readable medium on which the program element described herein is stored.

For further clarification, the invention is described using the embodiments shown in the figures. These embodiments are meant to be exemplary only and not limiting.

character list

• 1 schematisch ein Feldgerät gemäß einer Ausführungsform;
• 2 ein Flussdiagramm mit einem Verfahren gemäß einer Ausführungsform;
• 3 schematisch ein Feldgerät gemäß einer weiteren Ausführungsform;
• 4 schematisch ein Feldgerät gemäß einer weiteren Ausführungsform.

It shows:

• 1 schematically a field device according to an embodiment;
• 2 a flow chart with a method according to an embodiment;
• 3 schematically a field device according to a further embodiment;
• 4 schematically a field device according to a further embodiment.

Detailed Description of Embodiments

1 12 schematically shows a field device 10 according to an embodiment. The field device 10 is set up to receive a text 22 that can be interpreted. The interpretable text 22 can be created on a computer 20 using an editor, for example. The computer 20 can be embodied, for example, as a server, as a mobile device - for example as a laptop, tablet or smartphone - and/or as another type of computer. The interpretable text 22 may be encoded, for example, in ASCII and/or some other human-readable form. The interpretable text 22 may have a syntax that is similar or at least partially the same as common programming languages—eg, compilable and/or interpretable programming languages. The interpretable text 22 can be compiled, simulated, and/or emulated, for example, on the computer 20 and/or another computer, for example to test and/or debug the interpretable text 22 . The interpretable text 22 can, for example, be transmitted wirelessly to the field device 10 and received by it. In particular, the interpretable text 22 can be encrypted during the transmission.

The field device 10 that receives the interpretable text 22 can store the text 22 in a first memory area 12 . A compiler 14, which can be installed on the field device 10, for example, can convert the interpretable text 22 into code that the field device 10 can machine-read. In doing so, compiler 14 may be configured to output an error code, e.g., to a display associated with field device 10 and/or to the device (e.g., computer 20) that sent interpretable text 22. The error code can include, for example, an indication of a syntax error, an unknown or undefined identification, incorrect or dangerous semantics (which could, for example, disrupt operations of the field device) and/or other messages. After the conversion, the machine-readable code can be stored in a second memory area 16 of the field device 10 . The second memory area 16 can be connected to field device software 18, e.g. in such a way that the field device software 18 has dedicated locations where a branch is made to the second memory area 16 in order to execute the machine-readable code stored there.

2 FIG. 4 shows a flow diagram 40 with a method according to an embodiment. In a step 41, an interpretable text 22 (see e.g 1 ) sent to the field device 10. The interpretable text 22 includes an identification of the calculation data to be changed, for example an identifier, and a calculation rule. In a step 42 the interpretable text 22 is passed through received by the field device 10 and stored in a first memory area 12 of the field device 10 . In a step 43, the interpretable text 22 is converted by a compiler 14 into a code that the field device 10 can machine-read and, in a step 44, is stored in a second memory area 16 of the field device 10. In an optional step 45, a jump or branch is made to the second memory area 16 (machine instruction BRANCH) and the machine-readable code is executed. Step 45 can be performed multiple times, e.g. B. with each calculation of the field device 10. The step 45 can represent the productive use of the changed code to a certain extent.

3 FIG. 1 schematically shows a field device 10 according to a further embodiment. The field device 10 preferably has different function blocks, each with a different processing sequence or processing routine. The physical variable P, which was detected, for example, by a sensor (not shown) of the field device 10, is available at a device input. The sensor can be set up, for example, to measure the fill level, to determine the limit level, to measure the flow rate, to measure the pressure and/or to measure the temperature. This variable P is forwarded via a program sequence c, for example, to a first function block or module (input) E or processed by this module. The output of the module E can be supplied to a function block (linearization) L, for example via a further program sequence d. A program sequence e can then forward the output values to a function block (scaling) S. Its output values can be routed via a program flow f to a function block (basic function) F1, and finally, via a program flow g, to a function block (output) A. The values of A can be sent via a program flow h to the output interface T of the field device 10 to get redirected. Here the calculated or otherwise processed value can be further processed, transmitted and/or processed in some other way by a downstream system - eg PLC (programmable logic controller), PLS (process control system), etc. The transmission can take place wirelessly and/or by wire, eg to a computer 20 and/or another device.

The field device 10 can have another interface, e.g. a service interface - which can be embodied as a radio interface F, for example - between the field device 10 and an operating program on a computer 20. An interpretable text or program element 22 is transmitted to the field device 10 by the operating program . This program element is transferred to compiler C 14 via program flow j. The compiler C 14 converts the program element 22 and forwards it to a memory area 16 of the device software W via program flow i in a form that can be read by the field device 10 and is software-executable. The device software W has basic software 18 which can branch to the memory area 16 . The device software W can thus intervene accordingly in the program sequence of the field device 10 using the interpretable text or the program element 22 . For this purpose, the software can use suitable intervention points, e.g. using the paths k, I, m and/or n. This allows the information contained in the program element 22 to be embedded in the software sequence of the field device 10 .

4 FIG. 1 schematically shows a field device 10 according to a further embodiment. An interpretable text or program element 22 is transmitted to the field device 10, for example in the way shown in FIG 3 sketched. The interpretable text or program element 22 is passed to compiler C 14 via program flow j. The compiler C 14 converts the program element 22 into machine-readable code and forwards it to the device software, shown here as an extended function F2. The extended function F2 can contain, for example, program supplements and/or information for integrating (eg entry points) these program supplements at a suitable point in the program flow. The function F2 can thus intervene in a program flow e, skip the modules S and F1 and branch to a program flow g, so that this new information from the function block output A can be further processed. In this example, the function block scaling S and the function block basic function F1 are bridged in terms of process and replaced by function F2. The field device 10 thus receives a modified, for example expanded functionality, which is identified in this example with function block F2.

Reference List

10

field device

12

first storage area

14

compiler c

16

second storage area

18

field device software

20

computer

22

interpretable text

40

flow chart

41-45

steps

at

Program run or interface between modules

A

output block

E

input block

F1

Function block (basic function)

F2

Function Block (Advanced)

L

linearization block

P

input (physical)

S

scaling block

T

output (interface)

W

device software

Claims (15)

Computer-implemented method for changing calculation data of a field device (10), with the steps: sending an interpretable text (22) to the field device (10), the interpretable text (22) having an identification of the calculation data to be changed and a calculation rule; receiving, by the field device (10), the interpretable text (22) and storing the text (22) in a first memory area (12) of the field device (10); converting, by a compiler (14), the interpretable text (22) into code machine-readable by the field device (10); and storing the machine-readable code in a second memory area (16) of the field device (10). procedure after claim 1 , with the further step: during a calculation of the field device (10), jump, by means of a jump command, to the second memory area (16) and execute the machine-readable code. procedure after claim 2 , wherein the branch command is only transferred to the second memory area (16) after the machine-readable code has been completely stored in the second memory area (16) of the field device (10). A method according to any one of the preceding claims, further comprising the step of: simulate and/or emulate the interpretable text (22) and/or the machine-readable code before sending the text (22) to the field device (10), Method according to one of the preceding claims, wherein the interpretable text (22) has a syntax of JavaScript, Basic, and/or XML. A method as claimed in any preceding claim, wherein sending the interpretable text (22) includes encrypting the text (22). Method according to one of the preceding claims, wherein the interpretable text (22) is received via a wireless interface of the field device (10). Method according to one of the preceding claims, wherein the jump to the second memory area (16) takes place from one of the following locations of a field device software (18): from an input block (E), from a linearization block (L), from a scaling block (S), and/or from a function block (F1, F2). Method according to one of the preceding claims, wherein a jump back from the second memory area (16) takes place either to a subsequent address of the address of the jump or to a predefined jump label. Method according to one of the preceding claims, wherein the compiler (14) is arranged in a third memory area of the field device (10). Field device (10) which is set up to carry out a method according to one of the preceding claims. Use of a field device (10) according to claim 11 for level measurement, limit level determination, flow rate measurement, pressure measurement and/or temperature measurement. Compiler (14) for a field device (10). claim 11 . Program element, which if it is on a field device (10). claim 11 and/or is executed on another processing unit, the field device (10) and/or the processing unit instructs the method according to one of Claims 1 until 10 to perform. Computer-readable medium on which a program element according to the preceding claim is stored.

Images