CN1575443A - Foundation fieldbus server providing device information using a live-list-based dynamic directory - Google Patents

Foundation fieldbus server providing device information using a live-list-based dynamic directory Download PDF

Info

Publication number
CN1575443A
CN1575443A CNA028210123A CN02821012A CN1575443A CN 1575443 A CN1575443 A CN 1575443A CN A028210123 A CNA028210123 A CN A028210123A CN 02821012 A CN02821012 A CN 02821012A CN 1575443 A CN1575443 A CN 1575443A
Authority
CN
China
Prior art keywords
server
catalogue
field bus
bus device
control system
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.)
Granted
Application number
CNA028210123A
Other languages
Chinese (zh)
Other versions
CN100338539C (en
Inventor
D·A·格兰泽尔
L·A·奈策尔
D·B·戈夫
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 CN1575443A publication Critical patent/CN1575443A/en
Application granted granted Critical
Publication of CN100338539C publication Critical patent/CN100338539C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total 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], computer integrated manufacturing [CIM]
    • G05B19/41845Total 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], computer integrated manufacturing [CIM] characterised by system universality, reconfigurability, modularity
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/31From computer integrated manufacturing till monitoring
    • G05B2219/31135Fieldbus
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/31From computer integrated manufacturing till monitoring
    • G05B2219/31169Object manager contains client, control and communication and start and planning server
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/32Operator till task planning
    • G05B2219/32129Select program for specified machine from library, file server
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/33Director till display
    • G05B2219/33148CLS client server architecture, client consumes, server provides services
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/33Director till display
    • G05B2219/33152Server has organisation, tree data to access user data, client sends also both
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/34Director, elements to supervisory
    • G05B2219/34263OLE object linking and embedding, OPC ole for process control
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

A new and improved control system architecture with a single server interface for application software that eliminates manual intervention by providing online, immediate access to information needed for plant/enterprise optimization, operation, configuration, maintenance and diagnostic application software. The control system architecture provides a method of dynamically creating a server directory to enable automatic access in an integrated control system. The method includes accessing a live list of fieldbus devices, building/updating a browse tree structure, the browse tree structure defining a branch and leaf node organization and naming for and data from the fieldbus devices, copying AP directories and FF objects from active fieldbus devices into a FF directory and mapping the FF Directory into the server directory.

Description

Use provides the foundation fieldbus server of facility information based on the dynamic catalogue of effort scale
The application is that submission on June 4th, 2002 and title are the U.S. Patent application (sequence number 10/160 of " A Block-Oriented ControlSystem " (block-oriented control system), 094) part continuation application (CIP), and this U.S. Patent application is to submit on August 21st, 1997 and title also is the United States Patent (USP) the 6th of " A Block-Oriented Control System " (block-oriented control system), 424, the continuity of No. 892 (be " ' 892 patents hereinafter "), the right of priority that No. the 60/024th, 346, the U.S. Provisional Application of ' 892 patent requirement submission on August 23rd, 1996.The application submitted on June 21st, 2000 and title is the U.S. Patent application (sequence number 09/598 of " Block-Oriented Control System On HighSpeed Ethernet " (block-oriented control system on the Fast Ethernet), 697 (are hereinafter " ' 697 application ")) part continuation application, and this U.S. Patent application requires the right of priority of No. the 60/139th, 814, the U.S. Provisional Application submitted on June 21st, 1998.The application also requires No. the 60/314th, 093, U.S. Provisional Application of submitting to August 23 calendar year 2001 and the U.S. Provisional Application No.60/315 that submits to August 28 calendar year 2001, No. 067 right of priority.All above mentioned applications and patent are incorporated herein by reference in full at this.
Technical field
The present invention relates to the automatic control system structure.More particularly, the present invention relates to how access control system data of factory and enterprise application software, these control system data comprise factory and business administration, operation, configuration, maintenance and the needed fieldbus data of control system diagnostic function.
Background technology
Automatic control system such as process control, discrete control, control in batches (having made up process and discrete control), machine tools control, running control and Robotics, all is vital to all industrial sectors.One of the strongest demand is exploitation and uses open to the outside world and the system of " can co-operate " in modern control system.The opertaing device of opening, interoperable system allows different manufacturers to make is communicated by letter in same system and is not needed customization to programme with cooperation.
Driven by factory and business administration, Application Software Provider, opertaing device manufacturer and terminal user to propelling that open, interoperable control system.Open, interoperable control system are wanted in factory and business administration, provide because they need visit all control system information to optimize factory and the required analysis of enterprise's operation.That the client application software vendor is wanted is open, interoperable control system be so that their software can utilize operation standard operation system and the criterion calculation machine platform by the communications systems standard interconnection to go the access control system data.The opertaing device manufacturer wants open, interoperable control system, because this kind system allows them that their production marketing is given more terminal user and reduced cost of development simultaneously.The terminal user wants open, interoperable control system, and only best application software and opertaing device are selected by the system for them so that they can not consider the manufacturer.
In order to make control system become real opening and interoperable, the communication system in equipment, equipment between the client layer of (on the communication system layer) and computing machine/application software integrated morphology must be prescribed and be made into open." fieldbus " is the generic term that is used to describe the automatic control system of these types.
One of real opening and interoperable field bus control system are by fieldbus foundation (Austin, the FOUNDATION that TX) provides TMFieldbus (" FF ") system.The fieldbus (H1) of FF client layer and low speed 31.25 kilobits/second is described in the patent of ' 892 above-mentioned.Fast Ethernet (HSE) fieldbus that operates on 100 mbit/or the more speed is described in the application of ' 697 above-mentioned.' 892 patent and ' 697 application are transferred to the application's assignee.
H1 is for other control ability of field level and integratedly provide open and interoperable solution, and HSE provides opening and interoperable solution for distributed control on the high performance communication system very much being commonly called one of Fieldbus Control " backbone " net.HSE controls key the gathering from the information in for example this class low speed opertaing device of H1 equipment and other opertaing device, and this information is used in supervision and the Advanced Control application.HSE control is key to be assembled from the data in for example this class High-speed Control equipment of HSE equipment and other subsystem, and goes to provide the visit/change of H1 and HSE control information by the control system computing machine.
Factory/enterprise application software operates in " client computer " and " server " level in the control system hierarchy.Need an opening and interoperable integrated fieldbus data server architecture (being meant client-server), it will be provided for the framework of fieldbus data " semanteme " (how application software understands this control system data) and common standard, and no matter this fieldbus data is H1 or HSE data or other control data.Before the present invention, the have to artificial customization and adjust the data of receiving from each server to the visit of fieldbus or other opertaing device data is provided of client application software on factory/enterprise computer is because each server is differently discerned same semantic information and represented.Requirement for modern server is the needs of eliminating artificial customization or adjustment client application software; The application is promptly at this requirement.
(runtime) data subset was adaptive automatically when existing server standard provided very limited operation, because this is according to only understanding by the grammer of for example message structure and so on.For example, (Boca Raton, it is limited adaptive that the standardization of OPC standard FL) by the grammer of basic access mechanism and runtime data (for example simple process variable (PV) and adjustment point (SP)) provides from OPC (OLE that is used for process control) foundation.The extraneous information that the OPC standard is enough to allow to be called " attribute " usually defines " class " attribute of runtime data.Generic attribute comprises (DD) information of runtime data " device description ", for example helps word string, engineering unit and parameter tags.Some DD information is very complicated, for example comprises condition, menu and method (they are c programs).Other generic attribute (CF) is provided by " the ability file " of the limit of power of describing field bus device or other opertaing device, for example: the initial value of maximum number of parameters, parameter and maximum communication session number.,, do not have standardized definition for generic attribute though OPC allows server definition generic attribute, thus limited with the interoperability of client application software and by client application software carry out adaptive automatically.
In addition, promptly allow to server data carries out standardization to generic attribute, which " example " that client application software also needs to know runtime data is described by generic attribute.That is to say that the generic performance tells that the runtime data of what type of client application software is just accessed; But they can't discern just accessed concrete data.Example information can be provided by the application directory (data during its positioning trip) in the visit field bus device, but be similar to generic attribute, here the not standardization of application directory information definition, thus make client application software interoperability and adaptive automatically be impossible.
Senior people/machine interface (" HMI "), trend, asset management, configuration, maintenance, diagnosis and factory/business administration application software must be able to be visited runtime data and generic attribute and application directory semantic information, and this allows this software automatically to discern, translate and handles runtime data and needn't manually get involved.At last, for effectively, client application software must be visited runtime data and semantic information by individual interface.
The OPC standard can not be automatically and is supported these senior application effectively, because the same-interface that does not have open and interoperable framework or standard to be used for visiting by current usefulness runtime data provides above-mentioned semantic information to use to client software.
Needed is a kind of framework and the common specification that is used for integrated fieldbus data server architecture, and it can provide the semanteme of simple and complicated runtime data to client application software.
Needed is a kind of framework and the common specification that is used for integrated fieldbus data server architecture, its migration is to existing factory/corporate client machine application software, the for example support of HMI and other OPC software application, the needed semanteme of automatic identification, translation and processing to the runtime data of higher order client application software (for example factory/business administration, configuration, maintenance and diagnostic application software) carries out standardization and integrated simultaneously.
Needed is a kind of integrated fieldbus data server architecture, and it replenishes H1, HSE and other fieldbus structure, so that factory/enterprise application software can utilize corresponding semantic information automatically to translate this runtime data.
Needed is a kind of integrated fieldbus data server architecture, and it is provided for the individual interface of factory/enterprise application software visit runtime data and corresponding semantic information.
Summary of the invention
Embodiments of the invention have overcome above-mentioned and other shortcoming.Embodiments of the invention satisfy above-mentioned needs.Embodiments of the invention provide a kind of new and control system structure improvement, it has the individual server interface that is used for client application software, and it eliminates manual intervention by online senior factory/business administration, operation, configuration, maintenance and the diagnostic application software of providing to the instant electronic access of runtime data and semantic information.
Embodiments of the invention are called " integrated fieldbus data server architecture " (IFDSA) jointly at this.IFDSA provides the framework and the standard of the semantic information that is respectively applied for the runtime data of describing in mapping ' 892 patent and ' 697 application (such as H1 and HSE field bus device data), and is client application software definition individual interface.The IFDSA framework enabled is adaptive automatically to FF and other opertaing device type.
The elimination of the manual intervention of the foundation by providing a kind of method and apparatus to realize to be used for senior application bag, described method and apparatus is used for: during the operation of visit work FF equipment " effort scale ", one of construction/renewal is formatted as and browses tree structure from the standardization of the obtainable OPC standard of OPC foundation compatibility, and FF directory information (it is provided for semantic information and other opertaing device runtime data of all FF fieldbus) is mapped to new server directory.Server directory comprises the semantic information identical with the FF catalogue, but is formatted as and the OPC standard compatibility that can obtain from the OPC foundation.The browse tree of OPC compatibility and semantic information are followed serviced device and are offered client application software pellucidly.
IFSDA has realized individual interface, because the client application software of client no longer must use interface separately to visit semantic information and runtime data.Because FF semanteme and runtime data are on communication layers to the mapping of OPC standard, so this solution is still remained valid when embodiment develops into the technology of for example renewal of web service and so on.
Description of drawings
With reference to the accompanying drawings, the features and advantages of the present invention will become apparent for a person skilled in the art from following description, and similar numeral is meant similar terms in the accompanying drawing, and:
Fig. 1 be illustrate in accordance with the principles of the present invention, the block diagram of the imitated embodiment of integrated opening and interoperable control system;
Fig. 2 is the block diagram of imitated embodiment that illustrates in accordance with the principles of the present invention, has the integrated fieldbus data server architecture of FF catalogue mapping;
But Fig. 3 A illustrates in accordance with the principles of the present invention, creates server directory to enable the process flow diagram of the exemplary approach of visit automatically in the imitated embodiment of integrated fieldbus data server architecture;
Fig. 3 B is a chart, illustrated that the standardization exemplary in the server directory browses tree structure, and illustrated from creating server directory to enable the automatic method of visiting that construction/renewal has the step that tree structure is browsed in the standardization that can imitate effort scale and facility inventory figure;
Fig. 4 is a chart, illustrated in the FF catalogue the equipment imitated and from imitated OPC item this device map, server directory, and illustrated from creating server directory figure and enabled the automatic method of visiting, as a part that the FF catalogue is mapped to the step of server directory, the replacement step of device map to the OPC item of server directory;
Fig. 5 is a chart, illustrated that but exemplary application in the FF catalogue is handled (AP) catalogue and from FF catalogue imitated OPC item mapping, server directory, and illustrated from creating server directory figure and enabled the automatic method of visiting, as a part that the FF catalogue is mapped to the step of server directory, the AP catalogue is mapped to the replacement step in the OPC item of server directory;
Fig. 6 is a chart, illustrated in the FF catalogue imitated FF object and from the imitated OPC item FF object map, server directory, and illustrated from creating server directory figure and enabled the automatic method of visiting, as a part that the FF catalogue is mapped to the step of server directory, the replacement step of FF object map to the OPC item of server directory; With
Fig. 7 is a chart, illustrated in accordance with the principles of the present invention, in opc server, in the server directory imitated of the imitated embodiment of integrated fieldbus data server architecture, but client application software utilizes the mapped FF semantic information of server function of browse visit and utilize the server data access function to visit a kind of exemplary approach with the corresponding runtime data of semantic information.
Embodiment
For simplicity and illustrative purposes, mainly, utilize the realization imitated and the client application software of the control system of H1, HSE, OPC (both having referred to that client actions also referred to server operation) to describe by one in particular by with reference to imitating embodiment to describe the present invention.; those of ordinary skills are easy to recognize: identical principle realization and design that be equally applicable to other, that utilize any other integrated morphology also can realize, and this type of variation will be within this modification that does not depart from practicalness of the present invention and scope arbitrarily therein.More clearly, those of ordinary skills will be easy to recognize: can imitate the principle that is applied to OPC in the enforcement to be equally applicable to non-OPC realization.
The I.IFDSA general view
Referring to Fig. 1, the example 100 of integrated control system structure is illustrated, and at this, standard ethernet equipment 130 is used to a HSE chained device 110, HSE equipment 120 and factory/enterprise computer 190 and is interconnected to Ethernet 140.HSE chained device 110 and then utilize H1 network 150 to be connected to H1 equipment 170 again.Client application software 180 runs on factory/enterprise computer 190.Server software can run on factory/enterprise computer 190, HSE chained device 110 or the HSE equipment 120.Client application software 190 can also run on HSE chained device 110 or the HSE equipment 120.Actual hardware and software configuration will be depended on specific application need.Yet, can use network topology, equipment or configuration except imitated topology as shown in Figure 1, and such variation will be within this modification that does not depart from practicalness of the present invention and scope.
The IFDSA assembly of embodiment as shown in Figure 2 in accordance with the principles of the present invention.IFDSA is designed to for example utilize H1, HSE, OPC and client application software to remove to satisfy the integrated high-performance distributed manufacturing and the functional requirement of process control environment.IFDSA allows from various H1, HSE and other control and measuring equipment, constructs distributed automated system by the client application software and services device software of different vendor's manufacturing.IFDSA describes by the construction package that is adapted to H1, HSE and OPC environmental characteristics.
Be described in detail in handbook that variety of protocol of quoting in the disclosure below and standard are listed in the annex I herein and the standard, they can obtain publicly from fieldbus foundation (general headquarters are located at Texas, the non-profit organization of Austin).By calling out 512-794-8890 or landing www.fieldbus.org, can order this standard and handbook.Therefore these handbooks and each current version separately of standard are incorporated herein by reference by integral body at this.Be described in greater detail below each construction package (as shown in Figure 2) of IFDSA.
The II.IFDSA assembly
Fig. 2 has illustrated that one of IFDSA50 can be imitated embodiment.As shown, IFDSA50 preferably includes OPC160 and field bus device 280 (for example, H1 equipment 170 and HSE equipment 120-are referring to Fig. 1).The function of OPC160 and assembly can be integrated in the single OPC160 computing machine or be extended in a plurality of OPC160 computing machines.OPC160 is preferably via fieldbus networks 290 communicate by letter with field bus device 280 (for example, H1 network 150 and Ethernet 140-are referring to Fig. 1).
In the illustrated embodiment, OPC160 preferably includes client application software 180 and OPC client computer 210.The information that client application software 180 uses OPC client computer 210 to visit in the opc server 220.OPC client computer 210 and opc server 220 can be arranged in single computing machine, perhaps, they may the computing machine that separates on communication network in (communication network between the client-server is not shown in Figure 2).
Operate in client application software 180 among the OPC160 and can comprise the various softwares module of separating of program of separating or same software (for example, as).For example, client application software 180 can comprise people/machine Application of Interface software 181, maintenance/diagnostic application software 182, configuring application software 183 and other factory/enterprise application software 184.Preferred embodiment has defined the existing client application software that will be included in other factory/enterprise application software 184.
Refer again to embodiment as shown in Figure 2, the 2nd OPC160 computing machine preferably includes opc server 220 and FF server module 230.0PC server 220 for example can be a virtual server, and preferably includes a server function of browse 270.Preferably, between opc server 220 (the server function of browse 270 of more clearly saying so) and OPC client computer 210, enable and keep communication.FF server module 230 preferably includes FF catalogue 240, mapping function 250 and server directory 260.Preferably also between opc server 220 (the server function of browse 270 of more clearly saying so) and FF server module 230 (server directory of more clearly saying so), enable and keep communication.
The mapping of III.IFDSA catalogue
Continue with reference to embodiment illustrated in fig. 2, FF server module 230 is surveillance operation tabulation 400 preferably, and it represents the field bus device of the work in the field bus device 280.In a preferred embodiment, come activity of constructing tabulation 400 according among the annex I and FF standard that can from fieldbus foundation, obtain.The field bus device 280 that effort scale 400 identification FF server modules 230 can be used.For each equipment of listing in the effort scale 400, the respective list of the specific identifier of manufacturer is arranged, be called object dictionary (OD) index (the OD index is not shown in Fig. 2).Object when the OD index has corresponding operation at the scene in the bus apparatus 280.Object exists and is described in the application of ' 892 and comprises during the operation imitated in the equipment: Resource Block object, converter block object, functional block object, trend object, view object, linked object, alarm object, system time object, functional block scheduler object and Network object.
Object when though manufacturer can define other operation, preferably by the FF standard quoted among the annex I during with operation object definition be the FF object.In arbitrary situation, above mentioned and DD that in ' 892 application (and FF standard of listing among the annex I), describe and CF technology object when preferably being used to describe operation.DD and CF file extent the description of each object in the equipment, control system needs this to describe the connotation of translating in the field bus device that comprises human interface function's (such as calibration and diagnosis) of data.
The DD/CF file can write out according to ASCII text or any standardization programing language (such as C, C++ or SmallTalk).In a preferred embodiment, the DD file is write according to DD language (DDL), and the CF file is the described ASCII text file of FF standard as listing among the annex I and can obtain from fieldbus foundation.
FF catalogue 240 preferably is made of the tabulation of all field bus devices 280 that are called effort scale and the AP catalogue that is included in each FF equipment.Can construct this effort scale by intercepting the FF Network, perhaps can from the field bus device 280 that comprises this effort scale, read it.The AP catalogue is read from this field bus device field bus device 280 via fieldbus networks 290 by FF server module 230, perhaps can this locality obtains the AP catalogue by reading CF file (DD and CF file are provided for each FF field bus device).
The OD index is used as a determinant attribute in the FF protocol service and visits when operation object.Therefore, client application software 180 can visit this runtime data in the field bus device 280 by the corresponding OD index that obtains runtime data from FF catalogue 240.
Object modeling was " an OPC item " when OPC160 will move.The OPC item is discerned by " ID " that comprise the specific title of manufacturer.OPC item in the opc server 220 is via server function of browse 270 gives OPC client computer 210.Server function of browse 270 allows opc server 220 location OPC item in according to the tree structure of OPC standard structure.OPC client computer 210 uses server function of browse 270 to locate the item of being concerned about.
Current, do not have standardization branch and leaf node tissue or be used in ID name in the server function of browse 270, therefore, under the situation of the human translation that does not have browse tree and each OPC item wherein, OPC client computer 210 can not be located the OPC item of being concerned about.This stops the OPC item in 210 automatic visits of OPC client computer and the processing opc server 220.
In order to address this problem, IFDSA50 provides a standard server catalogue 260, creates it and represents FF catalogue 240.Server directory comprises the object semantic information identical with FF catalogue 240, but it mappedly comes and OPC object compatibility mutually.The name of tree structure 261 definition branches and leaf node tissue and field bus device 160 is browsed in standardization in the server directory 260 so that server function of browse 270 can by the semantic information of the OPC compatibility in the server directory 260 locate it, the expression of field bus device 280 and their data.In case be positioned, then the semantic information of OPC compatibility is pellucidly offered client application software 180 via server function of browse 270 with relevant OPC160 service with data value (if any).
Mapping function 250 is mapped to server directory 260 to the effort scale 400 of field bus device 280 and application processing (AP) directory information by an OPC access path title that produces automatically and/or a complete qualified item ID (quoting hereinafter referred to as the OPC item).Handbook or standard that list according to annex I and that can obtain from fieldbus foundation are write the AP catalogue.OPC access path title has defined by the server specific path of server function of browse 270 to FF catalogue 240.The handle of the item of object when the item ID that OPC is fully qualified is a corresponding operation in expression FF catalogue 240.OPC access path, item ID and server function of browse that OPC is qualified fully are to write and can get from the OPC foundation according to the OPC standard.
Fig. 3 A has illustrated that creating server directory 260 enables the embodiment of the method 300 of visit automatically.Just as can be seen, when integrated control system method 300 beginnings 310 time of powering, and it comprises the steps: to visit the effort scale 400 of field bus device 280, step 320; Standardized tree structure 261, the step 330 browsed of construction/renewal; From work field bus device 280 in the AP catalogue and the FF object tools in FF catalogue 240, step 340; FF catalogue 240 is mapped in the server directory 260 step 350; Whether judge has an effort scale 400 to change step 360 here; And, if, repeating step 330-360 then; And if not, then repeating step 360.
Preferably use in the FF of annex I standard definition and can carry out accessing step 320 from the protocol service that fieldbus foundation obtains.Construction/step of updating 330 uses effort scale 400 equipment identification informations that read from field bus device 280 to construct the standardized tree structure 261 of browsing at first.
The protocol service of preferably using in the FF of annex I standard definition and can obtaining from fieldbus foundation is come the reading of information in the execution in step 330.(, see also the corresponding description of Fig. 3 B and following Fig. 3 B for the more detailed description of step visit data thus.) preferably carry out copy step 340:1 like this) and use in the FF of annex I standard definition and the protocol service that can from fieldbus foundation, obtain read with effort scale 400 in the AP catalogue and the FF object of the corresponding field bus device 280 of working equipment, and these data are placed in the impact damper and 2) data are copied to FF catalogue 240 from impact damper.Mapping step 350 by for each equipment an AP catalogue and be included in the OPC item of each FF object map in the server directory 260 in the FF catalogue 240, come the data map in the FF catalogue 240 is arrived server directory 260.Being described in more detail and, seeing also the respective description of Fig. 4-6 and following they for this step these replacement step that is mapped to the OPC item.
Continue with reference to figure 3A, determination step 360 dynamically judges in the effort scale 400 whether change.Step 360 uses the agreement identical with step 320 to visit effort scale 400, then the new copy of this effort scale that has just obtained and previous copy is compared and has judged which field bus device has added in the field bus device 280 or therefrom deleted since the execution of the last time of step 360.Therefore, determination step 360 makes IFDSA50 dynamically be mapped to server directory 260 to FF catalogue 240.
Fig. 3 B has illustrated to have and can imitate standardization to browse of tree structure 261 can to imitate server directory 260, and illustrated the embodiment of construction/step of updating 330.As shown, field apparatus for each work in the field bus device 280, this standardization is browsed tree structure 261 and is comprised an effort scale catalogue 262 inlets and facility inventory 263 inlets, the field apparatus of this each work is quoted clearly by an effort scale catalogue 262 inlets, as shown in FIG., perhaps impliedly be cited as the child node or the attribute (not shown) of effort scale catalogue 262 inlets.
Referring to Fig. 2 and 3B, preferably, the tissue of server directory 260 structures and FF catalogue 240 structures is complementary.Each AP catalogue in the FF catalogue 240 is quoted by a beginning OD index and a plurality of object and is formed.In a preferred embodiment, this equipment identification information (for example, device id, fieldbus networks address, physical equipment mark and other related data) provides the semantic information that allows client computer to discern field bus device 280 automatically.It preferably is read from the field bus device 280 of the protocol service using among annex I and can obtain from fieldbus foundation, define in the FF standard, and preferably, utilize the item ID/ path that produces automatically, be mapped in the server directory 260 according to one of following two modes:
1. each the AP catalogue when being mapped to server directory 260, in the FF catalogue 240 is quoted a beginning OPC item that comprises the branch of this object by identification and is quoted and form, and the subobject of this object is represented as the item under this branch.Browsing order every under this branch keeps this OD index according to the defined order of representing in to the AP catalogue in the FF standard of object; Perhaps
2. each the AP directory entry when being mapped to server directory 260, in FF catalogue 240 can be quoted by the OPC item of corresponding OPC item and form.In this case, the FF subobject in the server directory 260 by they, the OPC item of the OPC item corresponding with this subobject quotes expression.
As shown in Figure 4, the mapping step 350 of the preferred embodiment of method 300 is mapped to effort scale inlet 242 server directory 260 from FF catalogue 240.The effort scale imitated inlet 242 in the FF catalogue 240 and OPC item 262a exemplary, 262b and 262c are corresponding with the replacement mapping option that describes below.For each mapping option, automatically produce OPC item ID and path (not shown on the figure).
The mapping option one, effort scale inlet 242 is mapped to by OPC browses and read the branch of service access and a tree structure of leaf node.Effort scale inlet 242 preferably includes identification and is arranged in the equipment of field bus device 280 and communicates with the devices needed identifying information.OPC item 262 comprises the device identifying information that has shone upon that is formatted as the OPC item according to the OPC standard, and OPC item 262a comprise according to the OPC standard be formatted as the OPC item this equipment the facility inventory information of having shone upon or quote; With
Mapping option 2, effort scale inlet 242 is mapped to the OPC item that is read the single structureization of service access by OPC numerical value.OPC item 262b comprises the directory information of mapped device of device identifying information and this equipment or its one quoted, and it is formatted and be mapped to an OPC numerical value according to the OPC standard.Therefore, this facility inventory or its one is quoted in the numerical value of the browse tree item that is included in this equipment of expression and
Mapping option 3, effort scale inlet 242 is mapped to the OPC item attribute of the single structureization of OPC getattr service access.OPC item 262c comprises the directory information of mapped device of device identifying information and this equipment or quotes to its one that it is according to the OPC cannonical formatization and be mapped to the OPC attribute.
Fig. 5 has illustrated the imitated AP catalogue 244 in FF catalogue 240 and imitated OPC item 264a, the 264b and the 264c that shine upon in server directory 260, from AP catalogue 244.In a preferred embodiment, AP catalogue 244 can be any one in three AP catalogues: promptly usually said functional block is used and handle (" FBAP ") catalogue, system management messages storehouse (" SMIB ") catalogue, network management information storehouse (" NMIB ") catalogue or any AP catalogue that other is write according to handbook of listing among the annex I and can obtain or standard from fieldbus foundation.As shown in, this AP catalogue 244 preferably includes: as header, the directory entry (for example, composite object is quoted with compound tabulation and quoted) that defines in annex I and the FF standard that can obtain from fieldbus foundation.This OPC item 264a, 264b and 264c are corresponding with the replacement mapping option that describes below.
As shown in Figure 5, three of quoting by structure OPC item of the mapping step 350 of the preferred embodiment of method 300 replace the mapping options or step is mapped to AP catalogue 244 server directory 260 from FF catalogue 240.For all mapping options, automatically produce this OPC item ID and path (not shown on the figure).AP catalogue mapping option or step are:
The mapping option one, AP catalogue 244 is mapped to OPC browses and read the branch of service access and a tree structure of leaf node.OPC item 264a comprises AP catalogue 244 header information that are mapped to OPC item header array and is mapped to AP catalogue 244 inlets that the OPC item that is formatted as the OPC standard is quoted;
Mapping option 2, AP catalogue 244 is mapped to the single structure OPC item that OPC numerical value reads service access.OPC item 264b comprises AP catalogue header and directory entry, and they are formatted and be mapped to an OPC numerical value according to the OPC standard; With
Mapping option 3, AP catalogue 244 is mapped to the single structure OPC item attribute of OPC getattr service access.OPC item 262c comprises AP catalogue header and directory entry, and they are formatted and be mapped to the OPC attribute according to the OPC standard.Preferably, OCP item numerical value is set to " sky.”
Fig. 6 has illustrated imitated FF object 246 in FF catalogue 240 and imitated OPC item 266a and the 266b in server directory 260, can imitate OPC item 266a and 266b and describe below and corresponding from the replacement mapping option of FF object 246 mappings.In a preferred embodiment, FF object 246 is any objects of writing according to handbook of listing in annex I and can obtain from fieldbus foundation or standard.FF object 246 preferably includes an object value, and this object value can be a runtime data; An object DD, it comprises the DD that is used for the FF object alternatively; With an object CF, it comprises the CF that is used for the FF object alternatively.OPC item 266a and 266b are corresponding with the replacement mapping option that describes below.
As shown in Figure 6, two of quoting by structure OPC item of the mapping step 360 of the preferred embodiment of method 300 replace the mapping options or step is mapped to FF object 246 server directory 260 from FF catalogue 240.For two mapping options, automatically produce OPC item ID and path (not shown on the figure).This FF object map option or step are:
The mapping option one, utilize OPC to browse and read the branch of service access and a tree structure of leaf node and FF object 246 is mapped to OPC item 266a.Object value and FF object 246 DD and the CF semantic information that are mapped to the OPC item reference structure that is formatted as the OPC standard when OPC item 266a comprises the operation of the FF object 246 that is mapped to OPC item value.Therefore, the semantic information of each FF object 246 is represented by subitem.Their each composition can be represented as their subitem in tree; With
Mapping option 2, FF object 246 is mapped to single structure OPC item 266b, at this, object value is mapped to the OPC item value that the OPC value reads service access during the operation of FF object 246, and the DD/CF semantic information is mapped to the OPC item attribute of OPC getattr service access.
Referring to Fig. 2 and 3A and Fig. 4-6, for a person skilled in the art clearly, the alternative embodiment of IFDSA 50 and method 300 will be eliminated FF catalogue 240 and modify steps 340 and directly being mapped in the server directory 261 from AP catalogue in the field bus device 280 and FF object.A local copy of DD/CF file also it is apparent that for a person skilled in the art: if can be used (for example hard disk or CD-ROM), then do not need from field bus device 280, to read object DD and object CF in the FF object 240, and an alternative embodiment comprises reading object DD and object CF from this local copy.
The single client application software interface of IV.IFDSA
Referring now to Fig. 7,, the preferred embodiment of IFDSA 50 provides individual interface, so that make client application software 180 visit the runtime data and the semantic information of field bus device 280 by OPC client computer 210.Provide H1, HSE in the server directory and the position of other opertaing device semantic information by the server function of browse 270 in the opc server 220.As described in the superincumbent 1-III part, the server function of browse 270 that FF server module 230 is supported in the opc servers 220.Field bus device 280 runtime datas can be provided for client application software 180 by OPC client computer 210 interfaces identical with semantic information.
OPC client computer 210 can obtain the service hours Value Data from the server data access function the opc server 220 271.FF server module 230 uses the protocol service that defines in the obtainable FF standard in annex I and from fieldbus foundation to visit field bus device 280 service hours Value Datas.Define by the OPC standard that can from the OPC foundation, obtain by the mapping of the field bus device 280 service hours Value Datas of FF server module 230 visit server data access function 271.
The migration of the existing application software of the preferred embodiment support of new IFDSA 50, it is included in other factory/enterprise application software 184, because existing application software only uses server data access function 271 and this function not to be changed by IFDSA 50.The present invention includes the migration and the coexistence of client application software 180 new among existing application software and the IFDSA 50.

Claims (20)

1. dynamically create a server directory so that enable the method for the automatic visit in the integrated control system for one kind, the method comprising the steps of:
(a) effort scale of visit field bus device, wherein: described effort scale is illustrated in the field bus device of working in this integrated control system;
(b) tree structure is browsed in one of construction/renewal, wherein: describedly browse tree-like organization definition branch and leaf node tissue, be used for the name of field bus device and from the data of field bus device;
(c) handling in (" AP ") catalogue and foundation fieldbus (" FF ") object tools to the FF catalogue, so that this FF catalogue has and the corresponding object semanteme of the field bus device of described work from the application in the field bus device of work; With
(d) the FF catalogue is mapped in the server directory, wherein the object semanteme in this FF catalogue is mapped in the server directory of standardized format, and this server directory is to visit automatically by the client application software that operates on the server.
2. the method for claim 1 also comprised the steps: before carrying out accessing step to this integrated control system power supply.
3. the method for claim 1 also comprises step:
(e) judge in described effort scale, whether there is change, wherein, change of indication when the field bus device of a job is deleted from integrated control system or added integrated control system to.
4. the method for claim 3 also comprises step:
If in described effort scale, judge a change, then repeating step (a)-(d) arranged; And
If in described effort scale, do not judge to change, then repeating step (e).
5. the process of claim 1 wherein: server is that OLE (" OPC ") server and a mapping step that is used for process control arrives the OPC object to the object Semantic mapping.
6. the method for claim 5, wherein: mapping step for each field bus device the AP catalogue be included in each FF object map in this FF catalogue to the OPC item.
7. the process of claim 1 wherein: mapping step from the FF catalogue be used for each field bus device, be mapped to server directory such as the device identification data of link/segmentation ID, node ID, device id and PD flag data.
8. the process of claim 1 wherein: mapping step is mapped to server directory to the AP catalogue that is used for each field bus device from the FF catalogue.
9. the process of claim 1 wherein: mapping step from the FF catalogue the FF object map in server directory.
10. the process of claim 1 wherein: construction/step of updating uses the effort scale equipment identification information structure that reads from field bus device to browse tree structure.
11. the process of claim 1 wherein: copy step comprises the steps:
Read the AP catalogue and the FF object of the field bus device of working in the described effort scale;
Putting into an impact damper from the data of AP catalogue and FF object; With
Data from impact damper are copied to the FF catalogue.
12. an integrated control system, be provided for client application software, to the semanteme of field bus device and the individual interface of runtime data, described integrated control system comprises:
The field bus device of a plurality of work;
A fieldbus networks, wherein: this fieldbus networks connects the field bus device of described work; With
A server is used, and it is communicated by letter with the field bus device of described work via fieldbus networks and functionally is connected with it, comprising:
The FF server module, wherein: this FF server module is by fieldbus networks and institute
State the field bus device communication of work;
The server function of browse, wherein: this server function of browse is used to the location and is used for this
The semantic information of the field bus device of work; With
The server data access function, wherein: the server data access function provides described
During the operation of working site bus apparatus and the visit of semantic information.
13. the integrated control system of claim 12 also comprises:
Client application, it is with the server application communication and operationally be connected with it, and it comprises:
Client application software; With
Client computer, it also operationally is connected with it with the client application software communication, and communicates by letter with server function of browse and server data access function, and wherein: client application software is by described client access semantic information and runtime data.
14. the integrated control system of claim 13, wherein: client application software comprises following one or more application software: people/machine Application of Interface software; Maintenance/diagnostic application software; And configuring application software.
15. the integrated control system of claim 12, wherein: the field bus device of work comprises one or more equipment of following type: H1 equipment; HSE equipment; Perhaps other field bus device.
16. the integrated control system of claim 12, wherein: it is an opc server that server is used.
17. the integrated control system of claim 13, wherein: client application is an OPC client computer.
18. the integrated control system of claim 12, wherein: the FF server module comprises:
The FF catalogue, wherein: this FF catalogue comprises the object semanteme of the field bus device of described work;
Mapping function, wherein: mapping function is in object Semantic mapping to a server directory in the FF catalogue; With
Server directory, wherein: this server directory comprises the object semanteme from the field bus device in the FF catalogue, it is according to mapped with the form of client application softwarecompatible and can be visited automatically by client application software by client computer.
19. the integrated control system of claim 18, wherein: server directory comprises:
Browse tree structure, wherein: describedly browse tree-like organization definition branch and leaf node tissue, and be used for the name of field bus device and their object.
20. one kind client application software is by the semanteme of individual interface visit field bus device and the method for runtime data in integrated control system, described method comprises step:
The server function of browse is provided, and wherein: the server function of browse provides the visit to the semantic data of the field bus device that is used for work;
The server data access function is provided, and wherein: the server data access function provides the visit to the runtime data of the field bus device of this work;
A client computer of communicating by letter with the server data access function with the server function of browse is provided; With
Client application software is by this semantic data of this client access and runtime data.
CNB028210123A 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using a live-list-based dynamic directory Expired - Fee Related CN100338539C (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US31409301P 2001-08-23 2001-08-23
US60/314,093 2001-08-23

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CNB2006100945035A Division CN100470426C (en) 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using dynamic directory

Publications (2)

Publication Number Publication Date
CN1575443A true CN1575443A (en) 2005-02-02
CN100338539C CN100338539C (en) 2007-09-19

Family

ID=23218519

Family Applications (2)

Application Number Title Priority Date Filing Date
CNB2006100945035A Expired - Fee Related CN100470426C (en) 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using dynamic directory
CNB028210123A Expired - Fee Related CN100338539C (en) 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using a live-list-based dynamic directory

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CNB2006100945035A Expired - Fee Related CN100470426C (en) 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using dynamic directory

Country Status (5)

Country Link
EP (1) EP1419420A1 (en)
CN (2) CN100470426C (en)
DE (1) DE02768655T1 (en)
HK (1) HK1074258A1 (en)
WO (1) WO2003019304A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102346461A (en) * 2011-06-02 2012-02-08 陕西盛田能源服务有限公司 Remote visual intelligent control system and method for multi-heat source system of remote visual control system (RVCS)
CN102809956A (en) * 2011-05-31 2012-12-05 通用电气公司 Systems and methods to overlay behaviors on foundation fieldbus alerts
CN102854858A (en) * 2011-05-31 2013-01-02 通用电气公司 Systems and methods for facilitating communication with foundation fieldbus linking devices

Families Citing this family (9)

* 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
US7853431B2 (en) 2006-09-29 2010-12-14 Fisher-Rosemount Systems, Inc. On-line monitoring and diagnostics of a process using multivariate statistical analysis
CN101610386B (en) * 2009-06-30 2011-06-22 中兴通讯股份有限公司 Method for displaying terminal list and device thereof
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
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
DE102013218566A1 (en) * 2013-09-17 2015-03-19 Robert Bosch Gmbh Communication module for a fieldbus device

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
DE69726764T2 (en) * 1996-02-06 2004-10-07 Fisher Rosemount Systems Inc System for managing field devices

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102809956A (en) * 2011-05-31 2012-12-05 通用电气公司 Systems and methods to overlay behaviors on foundation fieldbus alerts
CN102854858A (en) * 2011-05-31 2013-01-02 通用电气公司 Systems and methods for facilitating communication with foundation fieldbus linking devices
CN102809956B (en) * 2011-05-31 2017-03-01 通用电气公司 The system and method that behavior is superimposed on foundation fieldbus warning
CN102854858B (en) * 2011-05-31 2017-07-28 通用电气公司 System and method for promoting to communicate with foundation fieldbus linked set
CN102346461A (en) * 2011-06-02 2012-02-08 陕西盛田能源服务有限公司 Remote visual intelligent control system and method for multi-heat source system of remote visual control system (RVCS)

Also Published As

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

Similar Documents

Publication Publication Date Title
US7146230B2 (en) Integrated fieldbus data server architecture
CN1120606C (en) Glient-server system for maintaining application preferences in hierarchical data structure
US7343605B2 (en) System and method for communicating between software applications, particularly MES (manufacturing execution system) applications
CN106293820B (en) Exploitation test O&M integral system
CN100338539C (en) Foundation fieldbus server providing device information using a live-list-based dynamic directory
CN105830049A (en) Automated experimentation platform
EP0889422A2 (en) Global file system-based system and method for rendering devices on a cluster globally visible
CN1550084A (en) System and method for integrating and managing network services in a data centre
CN1527984A (en) Database system and method for industrial automation services
CN101621405A (en) Distributed type management monitoring system, monitoring method and establishing method thereof
KR101957771B1 (en) Method for web service by apparatus for managing factories in internet of things
CN1305611A (en) System and methods for object-oriented control of diverse electromechanical systems using computer network
CN102254021A (en) Method for constructing database based on virtual machine management system
Jiang et al. Design of software-defined gateway for industrial interconnection
US20160182304A1 (en) Integration method and system
CN115482334A (en) Method and system for constructing digital twin body
CN102402218A (en) Intelligent industrial network monitoring system
EP1506478B1 (en) Exchange infrastructure system and method
CN111711695B (en) Distributed equipment management system based on cloud platform
Cavalieri et al. Realising interoperability between opc ua and ocf
CN115396335B (en) Industrial wireless network equipment access IPv6 test system and method based on micro-service
CN101030271B (en) Persistent inquiry method for resource service object
CN101635711A (en) Programmable character communication method
Schachinger et al. Model-driven integration of building automation systems into Web service gateways
CN100344114C (en) Access method and realizing method for network apparatus

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1074258

Country of ref document: HK

C14 Grant of patent or utility model
GR01 Patent grant
REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1074258

Country of ref document: HK

CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20070919

Termination date: 20170823

CF01 Termination of patent right due to non-payment of annual fee