FIELD DEVICE AND METHOD FOR STARTING UP AN INDUSTRIAL AUTOMATION NETWORK

Abstract

A field device and method for starting up an industrial automation network, wherein to allow virtual start-up of at least one field device, an field device integration package is provided, whose user interface plug-in has an extension that allows a software tool to access a simulation model for the behavior of the at least one field device, and upon virtual start-up, the simulation model is used to reproduce the response of the field device, where a process model or interfacing of an external process model via a co-simulation coupling can also be used to stimulate the reproduced field device behavior, and where because the models with the FDI package are provided by the field device manufacturer, correct simulation and hence minimization of the risks upon start-up of industrial installations can be expected.

Claims

1.-5. (canceled)

6. A method for starting an industrial automation network with a plurality of field devices which are interconnected to one another by a network for data communication, wherein a configuration and parameterization of the plurality of field devices located in the automation network is performed by a software tool, the method comprising: providing a field device integration package including a user interface plug-in having an extension via though which access to a simulation model for behavior of at least one field device occurs for the software tool; and starting the at least one field device virtually via the software tool, the behavior of the at least one field device being simulated via the simulation model.

7. The method as claimed in claim 6, wherein access to a simulation model for a process is additionally made possible for the software tool by the extension of the user interface plug-in.

8. The method as claimed in claim 7, wherein the simulation model for a process contains prefabricated stimulation patterns and is stored in the user interface plug-in.

9. The method as claimed in claim 7, wherein access to the simulation model for the process occurs via a co-simulation coupling, through which a process model that is unstored in the user interface plug-in, is linked to the model for the field device behavior.

10. The method as claimed in claim 8, wherein access to the simulation model for the process occurs via a co-simulation coupling, through which a process model that is unstored in the user interface plug-in, is linked to the model for the field device behavior.

11. A field device, comprising: a processor; and a field device integration package including a user interface plug-in having an extension through which access by a software tool to a simulation model for behavior of the field device occurs.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The invention, as well as its embodiments and advantages, is explained in greater detail below with reference to the drawings, in which exemplary embodiments of the invention are presented, and in which:

[0018] FIG. 1 shows a block diagram of an industrial installation in accordance with the invention;

[0019] FIG. 2 shows a structure of an FDI package in accordance with the invention;

[0020] FIG. 3 shows a UML (Unified Modeling Language) class diagram of an FDI package; and

[0021] FIG. 4 is a flowchart of the method in accordance with the invention.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

[0022] FIG. 1 shows an automation technology installation in which a process 1 is controlled by an automation network 2. In the automation network 2 are an engineering station 3, an FDI server 4 and field devices 5, 6 and 7, which are connected to each other for data communication by an Ethernet-based communication network 8. The FDI concept is bus-neutral. As a result, the data communication network 8 can involve any given network, e.g., with a PROFIBUS, PROFINET, HART or FF protocol. The field devices 5, 6 and 7 are process-related components, such as a stored-program controller, which is frequently just referred to as a controller, a measurement transducer for detecting a physical variable in the process 1 to be automated, e.g., a pressure, or an adjustment element for influencing the process 1 as a function of the detected physical variable, e.g., a closed-loop control valve. A configuration and parameterization of the field devices located in the automation network is performed by the software tool 9 during the startup. FDI packages, the information content of which a software tool 9 that runs on an engineering station 3 can access as FDI client, are stored on the FDI server 4 in each case for the field devices 5, 6 and 7. Stored in the FDI packages, as will be explained in greater detail below, are models for the behavior of the field devices 5, 6 and 7 and also models for part aspects of the process, accessible for the software tool 9. In order to keep the risk of any errors that might occur in the operating phase of the process technology installation as low as possible, a simulation is performed based on these models by the software tool 9 in a startup phase preceding the operating phase. The installation is thus started up virtually and without a real process 1 running.

[0023] For improved clarity, FIG. 1 shows the software tool 9 drawn in as a block on an engineering station 3. This is not to be understood as the software tool 9 only being able to be run on one processing unit. Naturally, the software tool 9 can be subdivided in one realization into different sub-tasks, which can then run on different processing units, also called stations.

[0024] In a known way, an FDI package 20 in accordance with FIG. 2 contains a Device Definition 21, a User Interface Description 22 and a Business Logic 23, which correspond to the FDI concept. Stored in the user interface plug-in 24 is a simulation model created by the manufacturer of the respective field device for the behavior of the field device. The model cannot be changed by the user and should thus be correct. In addition, different models for process simulation, through which a stimulation for the behavior model of the field device can be created, are provided in the user interface plug-in 24.

[0025] FIG. 3 shows a UML class diagram to illustrate an extension 20 of a conventional user interface plug-in 31, which forms an element of a conventional FDI package 32. A user interface plug-in 34 expanded by a field device behavior model 33 here inherits all significant characteristics and methods of the conventional user interface plug-in 31 because, in the exemplary embodiment shown, the operator interface of the field device is to possess the same appearance during a virtual startup as it does during a conventional startup. The model 33, which is stored in the user interface plug-in 34 of the FDI package 32, serves to simulate the field device behavior during the startup of an automation network. To create a stimulation in the simulation of the field device behavior, on the one hand, there is a simulatable process model 35 available, which is likewise provided in the extension 30 of the user interface plug-in 34 and, on the other hand, there is a co-simulation coupling 36, which makes it possible to link in the external process model or an external simulator. The co-simulation coupling 36 can link in an external simulator for a process simulation via an OPC coupling 37 or via a shared memory 38. This makes it possible to incorporate further and, under some circumstances, very comprehensive process models into the simulation. On the side of the field device behavior model 38, the process model 35 and the co-simulation coupling 36 possess the same interface.

[0026] The advantages that are obtained by the invention are briefly re-summarized advance testing under real conditions of the automation technology components installed, called field devices here, is possible, minimization of critical states in the real startup of an industrial installation, models for simulation of the device behavior come from the manufacturer and should thus be correct, process models are able to be coupled to PLS and SCADA functions, no change of the PLS or SCADA is necessary, therefore simple implementation in existing engineering systems, and consistent use of field device models in startup.

[0027] FIG. 4 is a flowchart of a method for starting an industrial automation network (2) with a plurality of field devices (5, 6, 7) which are interconnected to one another by a network (8) for data communication, where a configuration and parameterization of the plurality of field devices (5, 6, 7) located in the automation network (2) is performed by a software tool (9). The method comprises providing a field device integration (FDI) package (20, 32) including a user interface plug-in (24, 34) having an extension (30) via though which access to a simulation model (33) for behavior of at least one field device (5, 6, 7) occurs for the software tool (9), as indicated in step 410. Next, the at least one field device (5, 6, 7) is started virtually via the software tool (9), with the behavior of the at least one field device (5, 6, 7) being simulated via the simulation model (33) as indicated in step 420.

[0028] While there have been shown, described and pointed out fundamental novel features of the invention as applied to a preferred embodiment thereof, it will be understood that various omissions and substitutions and changes in the form and details of the methods described and the devices illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.