EP1419420A1 - Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct - Google Patents

Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct

Info

Publication number
EP1419420A1
EP1419420A1 EP02768655A EP02768655A EP1419420A1 EP 1419420 A1 EP1419420 A1 EP 1419420A1 EP 02768655 A EP02768655 A EP 02768655A EP 02768655 A EP02768655 A EP 02768655A EP 1419420 A1 EP1419420 A1 EP 1419420A1
Authority
EP
European Patent Office
Prior art keywords
server
directory
fieldbus
opc
application software
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP02768655A
Other languages
German (de)
English (en)
Inventor
David A. Glanzer
Lee A. Neitzel
Donald B. Goff
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fieldbus Foundation
Original Assignee
Fieldbus Foundation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fieldbus Foundation filed Critical Fieldbus Foundation
Publication of EP1419420A1 publication Critical patent/EP1419420A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/41845—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by system universality, reconfigurability, modularity
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31135—Fieldbus
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31169—Object manager contains client, control and communication and start and planning server
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32129—Select program for specified machine from library, file server
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/33—Director till display
    • G05B2219/33148—CLS client server architecture, client consumes, server provides services
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/33—Director till display
    • G05B2219/33152—Server has organisation, tree data to access user data, client sends also both
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/34—Director, elements to supervisory
    • G05B2219/34263—OLE object linking and embedding, OPC ole for process control
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention relates to automatic control system architecture. More particularly, the present invention relates to how plant and enterprise application software accesses control system data including fieldbus data, needed for plant and enterprise management, operation, configuration, maintenance, and diagnostic functions of the control system.
  • Client Application Software suppliers want open, interoperable control systems so that their software can access the control system data using standard computer platforms running standard operating systems, and interconnected by standard communication systems.
  • Control device manufacturers want open, interoperable control systems because such systems allow them to sell their products to more end users while reducing development costs.
  • End users want open, interoperable control systems so that they can select the best application software and control devices for their system regardless of the manufacturer.
  • FF fieldbus
  • HI 31.25 kilobits/second fieldbus
  • HSE High Speed Ethernet
  • HSE provides the open and interoperable solution for field level control capability and integration
  • HSE provides the open and interoperable solution for distributed control on a very high performance communication system typically called a fieldbus control "backbone" network.
  • the HSE control backbone aggregates information from lower speed control devices, e.g., the HI devices and other control devices, which is used in supervisory and advanced control applications.
  • the HSE control backbone aggregates data from high-speed control devices, e.g., HSE devices and other subsystems, and provides access/change of HI and HSE control information by control system computers.
  • the plant/enterprise application software operates at the "client" and "server” levels in the control system hierarchy.
  • An open and interoperable integrated fieldbus data server architecture meaning client and server is needed that will provide a framework and common specification for the "semantics" (how the application software understands the control system data) of fieldbus data, whether it is HI or HSE data, or other control data.
  • client application software on the plant/enterprise computers had to be manually customize and adapt data received from each server that provided access to fieldbus or other control device data because each server identified and represented the same semantic information differently.
  • a requirement for modern servers is to eliminate the need to manually customize or adapt client application software; the present application addresses this requirement.
  • Some DD information is complex, for example containing conditionals, menus, and methods (which are C programs).
  • Additional class attributes are provided by "Capability Files" (CF) that describe the range of capability of the fieldbus device or other control device, e.g. maximum number of parameters, initial values of parameters, and maximum number of communication sessions.
  • CF Capability Files
  • OPC allow servers to define class attributes, there is no standardized definition for class attributes, thus limiting interoperability with, and automatic adaptation by, client application software Further, even if class attributes could be standardized for server data, the client application software also needs to know which "instance" of the runtime data is being described by the class attributes.
  • class attributes can tell the client application software what type of runtime data is being accessed, but they cannot identify the specific data that is being accessed.
  • Instance information can be provided by accessing application directories (which locate the runtime data) in the fieldbus devices, but like class attributes, there is no standardized definition of the application directory information making interoperability and automatic adaptation of the client application software impossible.
  • HMI Advanced Human/Machine Interface
  • trending asset management, configuration, maintenance, diagnostic and plant/enterprise management application software must have access to runtime data and the class attributes and application directory semantic information that allows the software to automatically identify, interpret, and process the runtime data without manual intervention.
  • client application software must be able to access the runtime data and the semantic information through a single interface.
  • the OPC Specification is unable to automatically and efficiently support these advanced applications because there is no open and interoperable framework or specification for providing the above described semantic information to the client software applications through the same interface that is currently used to access runtime data.
  • What is needed is a framework and a common specification for an integrated fieldbus data server architecture that can provide semantics of runtime data, both simple and complex, to the client application software.
  • What is needed is a framework and a common specification for an integrated fieldbus data server architecture that migrates support for existing plant/enterprise client application software, e.g., HMI and other OPC software applications, while standardizing and integrating the semantics needed for automatic identification, interpretation, and processing of runtime data by advanced client application software, e.g., plant/enterprise management, configuration, maintenance, and diagnostics application software.
  • Embodiments of the present invention overcome the shortcomings described above and otherwise. Embodiments of the present invention satisfy the above-described needs. Embodiments of the present invention provide a new and improved control system architecture with a single server interface for Client Application Software that eliminates manual intervention by providing online, immediate electronic access to the runtime data and semantic information by advanced plant/enterprise management, operation, configuration, maintenance and diagnostic application software.
  • the embodiments of the present invention are collectively referred to herein as the
  • IFDSA Integrated Fieldbus Data Server Architecture
  • the elimination of manual intervention for setup of advanced application packages is achieved by providing a method and apparatus for accessing the runtime "live list" of active FF devices and building/updating a Standardized Browse Tree Structure formatted to be compatible OPC Specifications available from the OPC Foundation and mapping FF Directory information (which provides the semantic information for all FF fieldbus and other control device runtime data) into a new Server Directory.
  • the Server Directory contains the same semantic information as the FF Directory, but is formatted to be compatible OPC Specifications available from the OPC Foundation.
  • the OPC- compatible browse tree and semantic information is then provided to the client application software transparently by the servers.
  • the EFSDA achieves a single interface because the Client Application Software at the client no longer has to use separate interfaces to access semantic information and runtime data. Since the mapping of FF semantic and runtime data to OPC Specifications is above the communication layers, this solution remains valid as implementations evolve to newer technologies, e.g., web services. BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram showing an exemplary embodiment of an integrated open and interoperable control system in accordance with the principles of the present invention
  • FIG. 2 is a block diagram showing an exemplary embodiment of an integrated fieldbus data server architecture with FF Directory Mapping in accordance with the principles of the present invention
  • FIG. 3A is a flowchart illustrating an exemplary method of creating a Server Directory to enable automatic access in an exemplary embodiment of an integrated fieldbus data server architecture in accordance with the principles of the present invention
  • FIG. 3B is a diagram illustrating an exemplary Standardized Browse Tree Structure in the Server Directory and graphically illustrating a step of building/updating the Standardized Browse Tree Structure with exemplary Live List and Device Directories, from the method of creating a Server Directory to enable automatic access;
  • FIG. 4 is a diagram illustrating an exemplary device in a FF Directory and exemplary OPC Items, mapped from the device, in the Server Directory, and graphically illustrating alternative steps of mapping the device into the OPC Item in the Server
  • FIG. 5 is a diagram illustrating an exemplary Application Process (AP) Directory in the FF Directory and exemplary OPC Items, mapped from the FF Directory, in the Server Directory, and graphically illustrating alternative steps of mapping the AP Directory into the Server Directory OPC Items as part of the step of mapping the FF directory into the Server Directory from the method of creating a Server Directory to enable automatic access;
  • AP Application Process
  • FIG. 6 is a diagram illustrating an exemplary FF Object in the FF Directory and exemplary OPC Items, mapped from the FF Object, in the Server Directory, and graphically illustrating alternative steps of mapping the FF Objects into the Server Directory OPC Items as part of the step of mapping the FF Directory into the Server
  • FIG. 7 is a diagram illustrating an exemplary method of Client Application Software accessing mapped FF semantic information using the Server Browse Function, and accessing runtime data, corresponding to the semantic information, using the Server Data Access Function, in an OPC server in an exemplary server directory of an exemplary embodiment of an integrated fieldbus data server architecture in accordance with the principles of the present invention.
  • FIG. 1 an example of an integrated control system architecture 100 is shown where standard Ethernet equipment 130 is used to interconnect HSE Linking Devices 110, HSE Devices 120, and Plant/Enterprise Computers 190 to Ethernet Network 140.
  • the HSE Linking Devices 110 in turn connect to HI Devices 170 using HI Networks 150.
  • Client Application Software 180 runs on the Plant/Enterprise Computers 190.
  • Server software may run on Plant/Enterprise Computers 190, HSE Linking Device 110 or HSE Device 120.
  • Client Application Software 190 may also run on HSE Linking Device 110 or HSE Device 120.
  • the actual hardware and software configuration will depend on the particular application needs. However, network topology, devices or configuration other than the exemplary topology shown in FIG. 1 may be used, and such variations would be within such modifications that do not depart from the true spirit and scope of the present invention.
  • IFDSA components in accordance with an embodiment of the principles of the present invention are shown in FIG. 2.
  • IFDSA is designed to meet the functional needs of the integrated, high performance distributed manufacturing and process control environments, e.g., utilizing HI, HSE, OPC and Client Application Software.
  • IFDSA permits distributed automation systems to be constructed from various HI, HSE, and other control and measurement devices, client application software and server software manufactured by different vendors.
  • IFDSA is described by architecture components that have been adapted to the specifics of HI, HSE and OPC environments.
  • FIG. 2 illustrates an exemplary embodiment of the IFDSA 50.
  • the IFDSA 50 preferably comprises OPC 160 and Fieldbus Devices 280 (e.g., HI Devices 170 and HSE Devices 120 - See FIG. 1).
  • the functions and components of OPC 160 may be combined into a single OPC 160 computer or spread among multiple OPC 160 computers.
  • OPC 160 preferably communicates with the Fieldbus Devices 280 via Fieldbus Networks 290 (e.g., HI Networks 150 and Ethernet Networks 140 - see FIG. 1).
  • OPC 160 preferably includes Client Application Software 180 and an OPC Client 210.
  • Client Application Software 180 uses OPC Client 210 to access information in an OPC Server 220.
  • OPC Client 210 and OPC Server 220 can reside in a single computer or they may be in separate computers on a communication network (the communication network between the client and server is not shown in FIG. 2).
  • the Client Application Software 180 running in OPC 160 may include a variety of software (e.g., as separate programs or separate modules of the same software).
  • the Client Application Software 180 may include Human/Machine Interface Application Software 181, Maintenance/Diagnostics Application Software 182, Configuration Application Software 183, and Other Plant/Enterprise Application Software 184.
  • the preferred embodiment defines existing client application software to be included in Other Plant/Enterprise Application Software 184.
  • a second OPC 160 computer preferably includes an OPC Server 220 and a FF Server Module 230.
  • the OPC Server 220 may be a virtual server, for example, and preferably includes a Server Browse Function 270. Communications are preferably enabled and maintained between the OPC Server 220, specifically the Server Browse Function 270, and the OPC Client 210.
  • the FF Server Module 230 preferably includes a FF directory 240, a Mapping Function 250, and Server Directory 260. Communications are also preferably enabled and maintained between the OPC Server 220, specifically the Server Browse Function 270, and the FF Server Module 230, specifically the Server Directory. III. IFDSA DIRECTORY MAPPING
  • the FF Server Module 230 preferably monitors a Live List 400 that represents the active fieldbus devices in Fieldbus Devices 280.
  • Live List 400 is created in accordance with the FF Specifications in Appendix I and available from the Fieldbus Foundation.
  • Live List 400 identifies Fieldbus Devices 280 available to FF Server Module 230.
  • OD Indexes Object Dictionary (OD) Indexes (OD Indexes not shown in FIG. 2).
  • OD Indexes have corresponding runtime objects in the Fieldbus Devices 280.
  • Exemplary runtime objects in a device are described the '892 application and include a resource block object, transducer block objects, function block objects, trend objects, view objects, link objects, alert objects, system time objects, function block schedule objects, and network traffic objects.
  • the runtime objects are preferably defined as FF Objects by the FF Specifications referenced in Appendix I, although a vendor can define additional runtime objects.
  • DD and CF technology mentioned above and described in the '892 application (and the FF Specifications listed in Appendix I) are preferably used to describe the runtime objects.
  • DD and CF files extend the descriptions of each object in a device that is needed for a control system to interpret the meaning of the data in the fieldbus device, including the human interface functions, such as calibration and diagnostics.
  • the DD/CF files can be written in ASCII text or any standardized programming language, such as C, C++, or SmallTalk.
  • DD files are written in the DD Language (DDL) and CF files are ASCII text files as described by the FF Specification listed in Appendix I and available from the Fieldbus Foundation.
  • DDL DD Language
  • CF files are ASCII text files as described by the FF Specification listed in Appendix I and available from the Fieldbus Foundation.
  • the FF Directory 240 is preferably composed of the list of all Fieldbus Devices 280, called the Live List, and the AP directories contained in each FF device.
  • the Live List may be constructed by listening to FF network traffic, or it may be read from Fieldbus Devices 280 that contain it.
  • AP directories are read by the FF Server Module 230 from the Fieldbus Devices Fieldbus Devices 280 via the Fieldbus Networks 290, or the AP Directories can be obtained locally by reading the CF file (The DD and CF files are provided with every FF fieldbus device).
  • the OD Index is used as a key attribute in FF protocol services to access the runtime objects. Consequently, Client Application Software 180 can access runtime data in the Fieldbus Devices 280 by obtaining their corresponding OD indexes from the FF
  • OPC 160 models runtime objects as "OPC Items".
  • OPC Items are identified by "Item IDs" that contain vendor-specific names.
  • OPC Items in the OPC Server 220 are presented to the OPC Clients 210 via a Server Browse Function 270.
  • the Server Browse Function 270 allows the OPC Server 220 to locate OPC Items in a tree structure that is constructed per the OPC specifications.
  • the OPC Client 210 uses the Server Browse Function 270 to locate items of interest.
  • OPC Client 210 cannot locate OPC Items of interest without manual interpretation of the browse tree and each OPC Item in it. This precludes OPC Clients 210 from automatically accessing and processing OPC Items in the OPC Server 220.
  • the IFDSA 50 provides a standard Server Directory 260 that is created to represent the FF Directory 240.
  • the Server Directory contains the same object semantic information as the FF Directory 240, but is mapped to be compatible with OPC objects.
  • the Standardized Browse Tree Structure 261 in the Server Directory 260 defines the branch and leaf node organization and naming for the Fieldbus Devices 160 so that the Server Browse Function 270 can locate its representation of Fieldbus Devices 280 and their data through the OPC compatible semantic information in Server Directory 260. Once located, the OPC compatible semantic information and data values (if any) are provided to the Client Application Software 180 transparently using via the Server Browse Function 270 and related OPC 160 services.
  • the Mapping Function 250 maps the Fieldbus Devices 280 Live List 400 and Application Process (AP) Directory information to the Server Directory 260 with an automatically generated OPC Access Path Name and/or a Fully Qualified Item ID, referred to below as the OPC Item Reference.
  • the AP Directory is written in accordance with the manuals or specifications listed in Appendix I and available from the Fieldbus Foundation.
  • the OPC Access Path name defines the server-specific path through the Server Browse Function 270 to the FF Directory 240.
  • the OPC Fully Qualified Item ID is a handle to the item representing a corresponding Runtime Object in the FF Directory 240.
  • the OPC Access Path, OPC Fully Qualified Item ID and Server Browse Function are written in accordance with OPC Specifications and available from the OPC Foundation.
  • FIG. 3 A illustrates an embodiment of a method 300 of creating a Server Directory
  • the method 300 starts when the integrated control system powers-up 310 and includes the steps of: Accessing the Live List 400 of Fieldbus Devices 280, step 320; Building/Updating the Standardized Browse Tree Structure 261, step 330; Copying AP Directories and FF Objects from active Fieldbus Devices 280 into the FF Directory 240, step 340; Mapping the FF Directory 240 into the
  • Server Directory 260 step 350; determining if there is a Live List 400 change, step 360; and, if yes, repeating steps 330-360, and if no, repeating step 360.
  • the access step 320 preferably is performed using protocol services defined in the FF Specifications in Appendix I and available from the Fieldbus Foundation.
  • the building/updating step 330 initially builds the Standardized Browse Tree Structure 261 with Live List 400 Device Identification information read from Fieldbus Devices 280.
  • the reading of information in step 330 preferably is performed using protocol services defined in the FF Specifications in Appendix I and available from the Fieldbus Foundation. (Please see FIG.
  • the copying step 340 is preferably performed by 1) reading the AP Directories and FF Objects of Fieldbus Devices 280 corresponding to active devices in the Live List 400 using protocol services defined in the FF Specifications in Appendix I and available from the Fieldbus Foundation and placing the data in a buffer, and 2) copying the data from the buffer to the FF Directory 240.
  • the mapping step 350 maps the data in FF Directory 240 to the Server Directory 260 by mapping, for each device, an AP Directory, and each FF Object contained in the FF Directory 240 to OPC Items in the Server Directory 260. Please see FIGs. 4-6 and their corresponding description below for more detailed descriptions of this step and alternative steps of mapping these to OPC Items.
  • the determining step 360 dynamically determines if there is a change in the Live List 400.
  • Step 360 uses the same protocol as Step 320 to access Live List 400 and then compares the new copy of the Live List just obtained with the previous copy and determines which fieldbus devices have been added or removed from Fieldbus Devices 280 since the last execution of Step 360.
  • the determining step 360 therefore, enables the IFDSA 50 to dynamically map the FF Directory 240 to the Server Directory 260.
  • FIG. 3B illustrates an exemplary Server Directory 260 with an exemplary Standardized Browse Tree Structure 261 and graphically illustrates an embodiment of the build/update step 330.
  • the Standardized Browse Tree Structure 261 includes a
  • the Server Directory 260 structure preferably matches the organization of the FF Directory 240 Structure.
  • Each AP Directory reference in the FF Directory 240 is composed of a Starting OD Index and a number of objects.
  • the Device Identification information e.g., DevicelD, Fieldbus Network Address, Physical Device Tag, and other related data, provides semantic information that allows clients to automatically identify Fieldbus Devices 280.
  • Each AP Directory reference in the FF Directory 240 as mapped to Server Directory 260 is composed of a Starting OPC Item Reference that identifies the branch that contains the object and the sub-objects of the object are represented as item beneath this branch.
  • the browses order of the items beneath the branch preserves the OD Index ordering as defined in the FF Specifications for the object represented in the AP Directory; or
  • Each AP Directory entry in FF Directory 240 as mapped to Server Directory 260 can be composed of an OPC Item Reference of the corresponding OPC Item.
  • FF sub-objects in the Server Directory 260 and are represented by their own OPC Item Reference of the
  • OPC Item that corresponds to the sub-object.
  • the mapping step 350 of the preferred embodiment of the method 300 maps the Live List Entry 242 from the FF Directory 240 into the Server Directory 260.
  • Exemplary Live List Entry 242 in the FF Directory 240 and exemplary OPC Items 262a, 262b, and 262c, correspond to the alternative mapping options described below.
  • the OPC Item ID and Path are automatically generated.
  • the Live List Entry 242 preferably includes Device Identification information needed to identify and communicate with the device that is located in Fieldbus Devices 280.
  • OPC Item 262 includes the mapped Device Identification information formatted as an OPC Item per OPC Specifications, and the OPC Item 262a includes the device's mapped Device Directory information or a reference, formatted as an OPC Item per OPC Specifications; and
  • OPC Item 262b includes Device Identification information and the device's mapped Device Directory information or a reference to it, formatted and mapped to an OPC Value per OPC Specifications. Accordingly, the Device Directory or a reference to it is included in the value of the Browse Tree item that represents the device, and Mapping Option 3. mapping the Live List Entry 242 to a single structured OPC Item Property accessed by the OPC Get Property service.
  • OPC Item 262c includes Device Identification information and the device's mapped Device
  • FIG. 5 illustrates an exemplary AP Directory 244 in the FF Directory 240 and exemplary OPC Items 264a, 264b and 264c, mapped from the AP Directory 244, in the Server Directory 260.
  • the AP Directory 244 can be any one of three AP Directories known as the Function Block Application Process ("FBAP") Directory, the System Management Information Base (“SMIB”) Directory, the Network Management Information Base (“NMIB”) Directory or any other AP Directory that is written in accordance with the manuals or specifications listed in Appendix I and available from the Fieldbus Foundation.
  • FBAP Function Block Application Process
  • SIB System Management Information Base
  • NMIB Network Management Information Base
  • the AP Directory 244 preferably includes Header, Directory Entries (e.g., Composite Object References and, and Composite List References) as defined in the FF Specifications in Appendix I and available from the Fieldbus Foundation.
  • the OPC Items 264a, 264b and 264c correspond to the alternative mapping options described below.
  • the mapping step 350 of the preferred embodiment of the method 300 maps the AP Directory 244 from the FF Directory 240 into the Server Directory 260 by three alternative mapping options or steps that structure the OPC Item References. For all mapping options, the OPC Item ID and Path (not shown on figure) are automatically generated.
  • the AP Directory mapping options or steps are: Mapping Option 1, mapping the AP Directory 244 to a tree structure of branches and leaf nodes accessed by the OPC Browse and Read service.
  • OPC Item 264a includes AP Directory 244 Header information mapped to an OPC Item Header Array, and AP Directory 244 Entries mapped to OPC Item References formatted to OPC Specifications;
  • Mapping Option 2 mapping the AP Directory 244 to a single structured OPC
  • OPC Item accessed by the OPC Value Read service includes the AP Directory Header and the Directory Entries formatted and mapped to an OPC Value per OPC Specifications; and Mapping Option 3, mapping the AP Directory 244 to a single structured OPC Item Property accessed by the OPC Get Property service.
  • OPC Item 262c includes AP Directory Header and the Directory Entries formatted and mapped to
  • the OCP Item Value is preferably set to
  • FIG. 6 illustrates an exemplary FF Object 246 in the FF Directory 240 and exemplary OPC Items 266a and 266b, corresponding to the alternative mapping options described below and mapped from the FF Object 246, in the Server Directory 260.
  • the FF Objects 246 are any object written in accordance with the manuals or specifications listed in Appendix I and available from the Fieldbus Foundation.
  • the FF Objects 246 preferably include an object value that can be runtime data, an Object DD that optionally contains the DD for the FF object, and an Object CF, that optionally contains the CF for the FF object.
  • the OPC Items 266a and 266b correspond to the alternative mapping options described below.
  • mapping step 350 of the preferred embodiment of the method 300 maps the FF Object 246 from the FF Directory 240 into the Server Directory
  • mapping options For both mapping options, the OPC Item ID and Path (not shown on figure) are automatically generated.
  • the FF Object mapping options or steps are:
  • OPC Item 266a includes the runtime Object Value of FF Object 246 mapped to the OPC Item Value, and FF Object 246 DD and CF semantic information mapped to OPC Item reference structures formatted to OPC Specifications. Accordingly, the semantic information for each FF Object 246 is represented by sub items. Each of their components may be represented as their sub items in the tree; and
  • an alternate embodiment of IFDSA 50 and method 300 is to eliminate the FF Directory 240 and modify step 340 to directly map AP Directories and FF Objects from Fieldbus Devices 280 in Server Directory 261. It also apparent to anyone skilled in the art that the Object DD and Object CF in FF Object 240 does not need to be read from Fieldbus Devices 280 if a local copy of the DD/CF files are available (e.g., hard disk or CD-ROM) and that an alternate embodiment includes reading the Object DD and Object CF from such a local copy.
  • DD/CF files e.g., hard disk or CD-ROM
  • IFDSA Single Client Application Software Interface provides a single interface for Client Application Software 180 access to Fieldbus Devices 280 runtime data and semantic information through OPC Client 210.
  • the location of the HI, HSE and other control device semantic information in Server Directory is provided through the Server Browse Function 270 in OPC Server 220.
  • FF Server Module 230 supports the Server Browse Function 270 in OPC Server 220 as described in Sections I- III above.
  • the Fieldbus Devices 280 runtime data can be provided to Client Application Software 180 though the same OPC Client 210 interface as the semantic information.
  • OPC Client 210 can obtain the runtime value data from the Server Data Access
  • FF Server Module 230 accesses Fieldbus Devices 280 runtime value data using protocol services defined in the FF Specifications in Appendix I and available from the Fieldbus Foundation.
  • the mapping of Fieldbus Devices 280 runtime value data accessed by FF Server Module 230 to the Server Data Access Function 271 is defined by OPC Specifications available from the OPC Foundation.
  • a preferred embodiment of the new IFDSA 50 supports migration of existing application software, which is included in Other Plant/Enterprise Application Software 184 because existing application software only uses Server Data Access Function 271 and this function is unchanged by IFDSA 50. This invention includes the migration and coexistence of existing application software with new Client Application Software 180 in the IFDSA 50.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention porte sur une architecture nouvelle et améliorée de système de commande présentant une interface avec un serveur unique pour logiciels d'application éliminant les interventions manuelles en fournissant un accès immédiat en ligne aux informations relatives aux logiciels d'application nécessaires pour assurer l'optimisation, le fonctionnement la configuration, l'entretien et les diagnostics d'installations ou d'entreprises. L'architecture du système de commande comporte un procédé de création dynamique d'un répertoire de serveur donnant un accès automatique à un système de commande intégré. Le procédé consiste: à accéder en direct à une liste de dispositifs de bus domotiques; à créer/actualiser une arborescence de navigation comportant une organisation de noeuds de branches et de feuilles; à nommer les bus domotiques et les données en émanant; à copier les répertoires AP et les objets FF des dispositifs de bus domotiques dans un répertoire FF; et à faire correspondre le répertoire FF au répertoire du serveur.
EP02768655A 2001-08-23 2002-08-23 Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct Ceased EP1419420A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US31409301P 2001-08-23 2001-08-23
US314093P 2001-08-23
PCT/US2002/026696 WO2003019304A1 (fr) 2001-08-23 2002-08-23 Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct

Publications (1)

Publication Number Publication Date
EP1419420A1 true EP1419420A1 (fr) 2004-05-19

Family

ID=23218519

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02768655A Ceased EP1419420A1 (fr) 2001-08-23 2002-08-23 Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct

Country Status (5)

Country Link
EP (1) EP1419420A1 (fr)
CN (2) CN100338539C (fr)
DE (1) DE02768655T1 (fr)
HK (1) HK1074258A1 (fr)
WO (1) WO2003019304A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8073967B2 (en) 2002-04-15 2011-12-06 Fisher-Rosemount Systems, Inc. Web services-based communications for use with process control systems
US7676287B2 (en) * 2004-03-03 2010-03-09 Fisher-Rosemount Systems, Inc. Configuration system and method for abnormal situation prevention in a process plant
US8014880B2 (en) 2006-09-29 2011-09-06 Fisher-Rosemount Systems, Inc. On-line multivariate analysis in a distributed process control system
CN101610386B (zh) * 2009-06-30 2011-06-22 中兴通讯股份有限公司 一种展示终端列表的方法及装置
US8977372B2 (en) 2011-05-12 2015-03-10 General Electric Company System and method for cycle time visualization
US9927788B2 (en) 2011-05-19 2018-03-27 Fisher-Rosemount Systems, Inc. Software lockout coordination between a process control system and an asset management system
US8868732B2 (en) * 2011-05-31 2014-10-21 General Electric Company Systems and methods for facilitating communication with foundation fieldbus linking devices
US8856302B2 (en) 2011-05-31 2014-10-07 General Electric Company Systems and methods for foundation fieldbus alerts
US8994545B2 (en) 2011-05-31 2015-03-31 General Electric Company Systems and methods for alert device removal
US8937555B2 (en) * 2011-05-31 2015-01-20 General Electric Company Systems and methods to overlay behaviors on foundation fieldbus alerts
CN102346461A (zh) * 2011-06-02 2012-02-08 陕西盛田能源服务有限公司 一种rvcs多热源系统远程可视化智能控制系统及方法
DE102013218566A1 (de) * 2013-09-17 2015-03-19 Robert Bosch Gmbh Kommunikationsmodul für ein Feldbusgerät

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5819086A (en) * 1995-06-07 1998-10-06 Wall Data Incorporated Computer system for creating semantic object models from existing relational database schemas
JP4260221B2 (ja) * 1996-02-06 2009-04-30 フィッシャー−ローズマウント システムズ， インコーポレイテッド フィールドデバイスコンフィギュレーションへのチェンジのレコードのトランザクションデーターベースを管理する為のシステム及び方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO03019304A1 *

Also Published As

Publication number Publication date
CN1575443A (zh) 2005-02-02
WO2003019304A1 (fr) 2003-03-06
CN100470426C (zh) 2009-03-18
DE02768655T1 (de) 2004-10-21
CN100338539C (zh) 2007-09-19
CN1924747A (zh) 2007-03-07
HK1074258A1 (en) 2005-11-04

Similar Documents

Publication Publication Date Title
US7146230B2 (en) Integrated fieldbus data server architecture
US10054935B2 (en) Apparatus and method for web-based tool management
JP5782215B2 (ja) プロセス制御システムに関連する情報にアクセスする機器および方法
EP3709227B1 (fr) Système et procédé de communication interopérable d'un composant de système d'automatisation avec de multiples sources d'informations
EP1327348B1 (fr) Procede et systeme de configuration a distance de serveurs d'acces de donnees de procedes
EP1299780B1 (fr) Gestion d'outils automatisee dans un environnement multiprotocole
Delsing et al. Migration of industrial process control systems into service oriented architecture
US8028049B1 (en) Apparatus and method for web-based tool management
EP0463764A2 (fr) Système et procédé de gestion d'ordinateur avec un agent commun
US20120109383A1 (en) Dynamically extensible and automatically configurable building automation system and architecture
US20070075916A1 (en) Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters
KR101080434B1 (ko) Ｆｄｔ／ｄｔｍ과 ｅｄｄｌ 기반의 디바이스 통합을 위한 ｏｐｃ ｕａ 서버
JPH11126104A (ja) 標準インターフェースを提供するための装置
KR101957771B1 (ko) IoT 기반의 공장 통합 관리 장치에 의한 웹 서비스 방법
WO2003019304A1 (fr) Serveur de creation d'un serveur de bus domotiques fournissant des informations sur des dispositifs au moyen d'un repertoire dynamique base sur une liste en direct
KR102021180B1 (ko) Opc ua 표준 상호운용성 시험 장치 및 방법
CN113039498A (zh) 在工业系统网络中调试现场设备的方法
WO2003065238A1 (fr) Dispositif de surveillance par langage de balisage generalise
CN114077633A (zh) 一种基于opc ua的多源异构数控系统监控服务器
US7499936B2 (en) Generic SNMP proxy
JP2004126817A (ja) 設定ツール装置及びプログラム製品
Barth et al. Configurable Mapping of EtherCAT field-level devices to OPC UA
KR20210066595A (ko) 이기종 레거시 프로토콜과의 연동을 위한 스마트공장 엣지디바이스
CN101896884B (zh) 用于传递数据的方法和系统
Kapsalis et al. Web gateway: a platform for industry services over Internet

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20040220

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

EL Fr: translation of claims filed
DET De: translation of patent claims
REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20120207