DE02768655T1 - FOUNDATION FIELDBUS SERVER WITH ACCESS TO DEVICE INMORATION THROUGH A LIVE LIST-BASED, DYNAMICALLY GENERATED DIRECTORY - Google Patents

Abstract

A method of dynamically establishing a server directory to enable automatic access to an integrated control system, the method comprising the following steps:
(a) accessing a current list (live list) of fieldbus devices, the current list representing active fieldbus devices in the integrated control system;
(b) creating / updating a browse tree structure, the browse tree structure defining a branch and leaf node organization that determines the fieldbus devices and data from the fieldbus devices;
(c) Copying application process ("AP") directories and Foundation Fieldbus ("FF") objects from active fieldbus devices into an FF directory so that the FF directory has object semantics that describe the active fieldbus Devices; and
(d) mapping the FF directory into the server directory, the object semantics in the FF directory being mapped into the server directory in a standardized format that is automatically accessible by client application software running on a server.

Claims (18)

Process for the dynamic creation of a server directory, to enable automatic access to an integrated tax system, the method comprising the following steps: (a) Access on a current list (Live List) of the fieldbus (English: fieldbus) devices, whereby the current list of active fieldbus devices in the integrated control system represents; (b) Build / update a browse tree structure, where the browse tree structure a branch and leaf node organization that defines the fieldbus devices and data from the fieldbus devices certainly; (c) Copy Application Process ("AP") directories and Foundation Fieldbus ("FF") objects from active Fieldbus devices into an FF directory, so that the FF directory has an object semantics that the active Fieldbus devices corresponds; and (d) mapping the FF directory into the server directory, where the object semantics in the FF directory in the server directory is mapped in a standardized format that is automatically generated by Client application software, running on a server accessible is. The method of claim 1, further following Step has: Start-up of the integrated control system before running of the access step. The method of claim 1, further following Step has: (e) Determine if there is a change in the current list, with a change displayed when a active fieldbus device is removed from or added to the integrated control system. The method of claim 3, further comprising the following Steps comprises: if there is a change found in the current list, Repeating steps (a) - (d); and  if no change is determined in the current list, repeating the step (E). The method of claim 1, wherein the server is an OLE for process control (process control) ("OPC") server is and the mapping step maps the object semantics to OPC objects. The method of claim 5, wherein the imaging step for each Fieldbus device an AP directory and each FF object contained in the FF directory maps to OPC elements. The method of claim 1, wherein the imaging step Device identification data such as link / segment ID, node ID, device ID, and PD tag data for each Fieldbus device maps from the FF directory to the server directory. The method of claim 1, wherein the imaging step an AP directory for each Fieldbus device maps from the FF directory to the server directory. The method of claim 1, wherein the imaging step Maps FF objects from the FF directory to the server directory. The method of claim 1, wherein the forming / updating step is the browse tree forms part of the fieldbus devices Read device identification information the current list. The method of claim 1, wherein the copying step does the following: Read the AP directories and FF objects of the active fieldbus devices in the current list; Providing data from the AP directories and FF objects in a buffer; and Copy the data from the buffer in the FF directory. Integrated control system that has a single interface ready for Client application software with semantic and runtime data for fieldbus devices, the having: a plurality of active fieldbus devices; on Fieldbus network, the fieldbus network connecting the active fieldbus devices; and  a server application that is connected to and operationally connected is with the active fieldbus devices via the fieldbus network, with: an FF server module, where the FF server module with the active fieldbus devices through the fieldbus network communicating; a server browse function, the server browse Function is used to provide semantic information for the active Fieldbus Unit to locate; and a server data access function, the Server data access function Access to runtime and semantic information for the active fieldbus devices supplies. The integrated control system of claim 12, further comprising: a client application in communication with and operatively connected to the server application and comprising: client application software; and a client that is in communication with and operatively connected to the client application software and in communication with the server browser se function and the server data access function is available, the client application software accessing the semantic information and the runtime data by the client. 14. The integrated control system of claim 13, wherein the client application software comprises one or more of the following: human / machine interface application software; Maintenance / diagnostics application software; and configuration application software. The integrated control system of claim 12, wherein the active fieldbus devices include one or more of the following types of devices: H1 devices; HSE devices; or other fieldbus devices. The integrated control system of claim 12, wherein the server application is an OPC server. The integrated control system of claim 13, wherein the client application is an OPC client. The integrated control system of claim 12, wherein the FF server module Includes:  on FF directory, where the FF directory object semantics of the active Fieldbus Unit includes; a mapping function, the mapping function Maps object semantics in the FF directory to a server directory; and the server directory, the server directory object semantics of the fieldbus devices from the FF directory included in one with the client application software compatible format and is depicted by the client application software automatically accessible by the client is. 19. The integrated control system of claim 18, wherein the server directory includes: a Browser tree structure, the browser tree structure being a branch and Sheet node organization and naming for the fieldbus devices and their objects Are defined. Method of accessing client application software, in an integrated control system, based on semantic and runtime data for fieldbus devices a single interface that does the following: Provide a server browse function, the server browse function being accessed to semantic data for the active fieldbus devices providing; Providing a server data access function, the server data access function providing access to runtime data for the active Fieldbus devices; Provide a client in communication with the server browse function and the Server data access function; and Access the client application software on the semantic data and the client runtime data by the client.