CN100338539C - 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
CN100338539C
CN100338539C CN 02821012 CN02821012A CN100338539C CN 100338539 C CN100338539 C CN 100338539C CN 02821012 CN02821012 CN 02821012 CN 02821012 A CN02821012 A CN 02821012A CN 100338539 C CN100338539 C CN 100338539C
Authority
CN
China
Prior art keywords
directory
ff
server
opc
fieldbus
Prior art date
Application number
CN 02821012
Other languages
Chinese (zh)
Other versions
CN1575443A (en
Inventor
D·A·格兰泽尔
L·A·奈策尔
D·B·戈夫
Original Assignee
菲尔德巴斯基金会
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
Priority to US31409301P priority Critical
Application filed by 菲尔德巴斯基金会 filed Critical 菲尔德巴斯基金会
Publication of CN1575443A publication Critical patent/CN1575443A/en
Application granted granted Critical
Publication of CN100338539C publication Critical patent/CN100338539C/en

Links

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]
    • Y02P90/16Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS] characterised by system universality, i.e. configurability or modularity of production units
    • 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]
    • Y02P90/18Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS] characterised by the network communication

Abstract

一种新的和改良的控制系统结构,它具有用于应用软件的单个服务器接口,其通过在线提供对工厂/企业优化、操作、配置、维护和诊断应用软件所需信息的即时快速访问,而消除人工干预。 A new and improved control system architecture, it has a single server interface for application software, which is available online through the plant / enterprise optimization, operation, configuration, maintenance and diagnostics instant fast access to applications required information, and elimination of manual intervention. 该控制系统结构提供一种动态创建服务器目录以便在集成控制系统中使能自动访问的方法。 The control system architecture is provided a method for dynamically creating a directory server can automatically access the manipulation of the integrated control system. 该方法包括:访问现场总线设备的活动列表;建造/更新浏览树形结构,该浏览树形结构定义分支和叶节点组织和用于现场总线设备的命名及来自该现场总线设备的数据;把来自工作的现场总线设备中的AP目录和FF对象复制到一个FF目录中并把FF目录映射到服务器目录中。 The method comprising: accessing a list of active fieldbus devices; build / update the browser tree structure, the browse tree branch and leaf nodes define the organization and named for fieldbus devices and data from the fieldbus devices; from the copy directories and FF objects AP active fieldbus devices to a directory and the FF FF directory into the server directory maps.

Description

使用基于活动列表的动态目录提供设备信息的基金会现场总线服务器 Use providing information based on the active list of Active Directory server FOUNDATION fieldbus

本申请是2002年6月4日提交且标题为“A Block-Oriented ControlSystem”(面向块的控制系统)的美国专利申请(序列号10/160,094)的部分继续申请(CIP),而该美国专利申请是1997年8月21日提交且标题也为“A Block-Oriented Control System”(面向块的控制系统)的美国专利第6,424,892号(在下文中为“'892专利”)的延续,'892专利要求1996年8月23日提交的美国临时申请第60/024,346号的优先权。 U.S. Part Patent Application (Serial No. 10 / 160,094) of the present application is June 2002 filed May 4, and entitled "A Block-Oriented ControlSystem" (block-oriented control system) to continue to apply (CIP), and the U.S. Pat. application 1997 August 21, filed and entitled also "a block-oriented control system" (block-oriented control system) U.S. Patent No. 6,424,892 (the "hereinafter '892 patent"), a continuation of' 892 patent He asked the United States August 23, 1996 provisional application Serial No. 60 / 024,346. 本申请还是2000年6月21日提交且标题为“Block-Oriented Control System On HighSpeed Ethernet”(高速以太网上面向块的控制系统)的美国专利申请(序列号09/598,697(在下文中为“'697申请”))的部分继续申请,而该美国专利申请要求1998年6月21日提交的美国临时申请第60/139,814号的优先权。 This application is also on June 21, 2000, filed and entitled "Block-Oriented Control System On HighSpeed ​​Ethernet" (for the control system blocks the high-speed Ethernet) U.S. Patent Application (Serial No. 09 / 598,697 (hereinafter the " '697 part of the application ")) continues to apply, and the United States patent application claims the United States June 21, 1998 filed provisional application Serial No. 60 / 139,814. 本申请还要求2001年8月23日提交的美国临时申请第60/314,093号和2001年8月28日提交的美国临时申请No.60/315,067号的优先权。 This application also requires the US to US Provisional Application August 23, 2001 filed No. 60 / 314,093 and 28 August 2001, filed Provisional Application No. No. No.60 / 315,067. 所有上面提及的申请和专利被在此全文引入作为参考。 All the above mentioned patents and applications are incorporated herein by reference.

技术领域 FIELD

本发明涉及自动控制系统结构。 The present invention relates to an automatic control system architecture. 更特别地,本发明涉及工厂和企业应用软件如何访问控制系统数据,这些控制系统数据包括工厂和企业管理、操作、配置、维修以及控制系统诊断功能所需要的现场总线数据。 More particularly, the invention relates to how plant and enterprise application software, data access control system, fieldbus control system data, including data from these factories and business management, operation, configuration, maintenance and control functions required for system diagnostics.

背景技术 Background technique

自动控制系统对所有工业部门,比如过程控制、离散控制、批量控制(组合了过程和离散控制)、机器工具控制、运转控制以及机器人技术,都是至关重要的。 Automatic control systems for all industrial sectors, such as process control, discrete control, batch control (a combination of process and discrete control), machine tool control, operation control and robotics, are crucial. 在现代控制系统中最强烈的需求之一是开发和使用“开放”和“能共同操作”的系统。 In one of the most modern control system is strong demand for the development and use of "open" and "interoperable" systems. 开放的、能共同操作的系统允许不同生产商制造的控制设备在同一系统中通信与合作而不需要定制编程。 Open, interoperable system allows the control equipment manufactured by different manufacturers in the same system of communication and cooperation without custom programming.

向开放的、能共同操作的控制系统的推进是由工厂和企业管理、应用软件供应商、控制设备生产商以及终端用户所驱动的。 Open, propulsion control systems are interoperable by the factory and enterprise management, application providers, equipment manufacturers and end users control driven to. 工厂和企业管理想要开放的、能共同操作的控制系统,因为他们需要访问所有的控制系统信息以便提供优化工厂和企业操作所需的分析。 Factories and enterprises want management of open, interoperable control systems because they need access to all of the control system in order to provide the information needed to analyze and optimize plant operations business. 客户机应用软件供应商想要开放的、能共同操作的控制系统以使他们的软件可以利用运行标准操作系统并通过标准通信系统互连的标准计算机平台去访问控制系统数据。 The client application software vendors want to open, interoperable control systems so that they can use the software to run standard operating systems and interconnection systems via standard communication standard computer platform to access control system data. 控制设备生产商想要开放的、能共同操作的控制系统,因为此种系统允许他们把他们的产品销售给更多的终端用户而同时降低开发成本。 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 system, to enable them to consider not only the manufacturer to choose the best application software and control devices for their systems.

为了使控制系统成为真正开放和能共同操作的,在设备、设备中(通信系统层之上)的用户层和计算机/应用软件集成结构之间的通信系统必须被规定并被做成开放的。 For the control system to become truly open and interoperable, in the apparatus, the communication system between the devices (communication system layers above) layer and a user computer / application integration structure must be specified and made open. “现场总线”是用于描述这些类型的自动控制系统的通用术语。 "Fieldbus" is a generic term for these types of the automatic control system is described.

真正开放和能共同操作的现场总线控制系统之一是由现场总线基金会(Austin,TX)提供的FOUNDATIONTM现场总线(“FF”)系统。 One of fieldbus control system truly open and interoperable provided by the Fieldbus Foundation (Austin, TX) FOUNDATIONTM fieldbus ( "FF") system. FF用户层和低速31.25千比特/秒的现场总线(H1)在上述'892专利中被描述。 FF user layer and a low speed 31.25 kilobits / second fieldbus (H1) is described in the aforementioned '892 patent. 运行在100兆比特/秒或更高速度上的高速以太网(HSE)现场总线在上述'697申请中被描述。 Running on a 100 Mbit / second or higher-speed high-speed Ethernet (HSE) fieldbus is described in the aforementioned '697 application. '892专利和'697申请被转让给本申请的受让人。 '892 patent and the' 697 application is assigned to the assignee of this application.

H1为现场级别的控制能力和集成提供开放和能共同操作的解决方案,而HSE在通常被称为现场总线控制“骨干”网的一个很高性能通信系统上为分布式控制提供开放和能共同操作的解决方案。 H1 provides an open and interoperable solutions for field-level control capabilities and integrated, while the HSE can work together to provide an open and distributed control in a very high-performance communication systems are often referred Fieldbus control "backbone" network solutions operations. HSE控制骨干聚集来自例如H1设备这类低速控制设备和其它控制设备中的信息,该信息被使用于监督和高级控制应用中。 HSE control backbone aggregates from such a low-speed device, for example, H1 devices and other control information in the control device, this information is used for advanced monitoring and control applications. HSE控制骨干聚集来自例如HSE设备这类高速控制设备和其它子系统中的数据,并通过控制系统计算机去提供H1和HSE控制信息的访问/改变。 HSE HSE control backbone aggregates data from a device such high speed control device and other subsystems e.g., to provide access and / H1 and HSE change control information through a control system computer.

工厂/企业应用软件操作在控制系统分层结构中的“客户机”和“服务器”级。 Plant / enterprise application software operating in the control system hierarchy "client" and "server" class. 需要一个开放和能共同操作的集成的现场总线数据服务器结构(是指客户机和服务器),它将提供用于现场总线数据的“语义”(应用软件如何理解该控制系统数据)的框架和共同的规范,而不管该现场总线数据是H1或HSE数据还是其它控制数据。 Requires an open and interoperable integrated fieldbus data server architecture (refer client and server), will provide fieldbus data for "semantic" (understood how the control system application software data) and a common framework specification, regardless of whether the data is H1 fieldbus or HSE data or other control data. 在本发明之前,工厂/企业计算机上的客户机应用软件不得不人工定制并且调整从提供对现场总线或其它控制设备数据的访问的每个服务器中收到的数据,因为每个服务器对同一语义信息进行不同地识别和表示。 Prior to this invention, the client application software on the plant / enterprise computers have to manually adjust and customize the data received from each server to provide access to the site or other control device data bus, since each server on the same semantic and identification information differently expressed. 对于现代服务器的要求是消除对人工定制或者调整客户机应用软件的需要;本申请即针对这个要求。 For the requirements of modern servers is to eliminate the need for manual adjustment or customized client application software; this application that is required for this.

现有的服务器规范提供了非常有限的运行时(runtime)数据子集的自动适配,因为此数据仅仅可通过例如消息结构之类的语法来理解。 Existing server specification provides limited automatic adaptation runtime (Runtime) subsets of data, as this data is only by example message structure like the syntax to understand. 例如,来自OPC(用于过程控制的OLE)基金会(Boca Raton,FL)的OPC规范通过基本访问机制和运行时数据(例如简单的过程变量(PV)和调整点(SP))的语法的标准化来提供有限的适配。 For example, from OPC (for process control OLE) Foundation (Boca Raton, FL) OPC specifications the basic syntax and runtime data access mechanism (e.g. simple process variable (PV) and setpoint (the SP)) of standardized to provide limited adaptation. OPC规范通常足以允许称为“属性”的额外信息来定义运行时数据的“类”属性。 OPC specification generally sufficient to allow additional information called "attributes" to define "classes" attribute runtime data. 类属性包括运行时数据的“设备描述”(DD)信息,例如帮助字串、工程单元和参数标记。 Class attributes include "device description" (DD) information, for example to help string, engineering units and parameter markers runtime data. 某些DD信息很复杂,例如包含条件、菜单和方法(它们是C程序)。 Some information DD is complex, comprising e.g. conditions, menus and methods (which is C program). 另外的类属性由描述现场总线设备或其它控制设备的能力范围的“能力文件”(CF)来提供,例如:最大参数数目、参数的初始值以及最大的通信会话数目。 Further provided by the class attribute description field bus control device or other device capabilities "capabilities file" (CF2), for example: the maximum number of parameters, the initial values ​​of the parameters and the maximum number of communication sessions. 可是,虽然OPC允许服务器定义类属性,但是对于类属性并没有标准化的定义,因此限制了与客户机应用软件的互操作性以及由客户机应用软件进行的自动适配。 However, although the OPC server allows attributes define the class, but for class attributes and no standardized definition, and thus limits the client application software and interoperability automatic adaptation performed by the client application software.

另外,即使能够为服务器数据而对类属性进行标准化,客户机应用软件也需要知道运行时数据的哪个“实例”正在被类属性描述。 In addition, even if they can be standardized and client application software class attributes for the server data also need to know which "instance" data is being described runtime class property. 也就是说,类属性能告诉客户机应用软件什么类型的运行时数据正被访问;但是它们无法识别正被访问的具体数据。 In other words, the class attribute can tell the client application software is running what type of data is being accessed; but they can not identify the specific data being accessed. 实例信息能通过访问现场总线设备中的应用目录(它定位运行时数据)来被提供,但是类似于类属性,这里并没有应用目录信息的标准化定义,从而使得客户机应用软件的互操作性和自动适配是不可能的。 Examples of information by the application catalog (which is positioned runtime data) access to the fieldbus devices is provided, but is similar to class attributes, there is no standardized definition of the application and directory information, so that the client application software interoperability and automatic adaptation is not possible.

高级人/机接口(“HMI”)、趋势、资产管理、配置、维护、诊断和工厂/企业管理应用软件必须能访问运行时数据和类属性以及应用目录语义信息,这允许该软件自动地识别、翻译并处理运行时数据而不必人工介入。 Senior man / machine interface ( "HMI"), trends, asset management, configuration, maintenance, diagnostics and plant / enterprise management application software must be able to access the runtime data and class attributes and application catalog semantic information, which allows the software to automatically identify translation and data processing run-time without manual intervention. 最后,为了有效,客户机应用软件必须能够通过单个接口访问运行时数据和语义信息。 Finally, to be effective, the client application software must be able to run data and semantic information accessible through a single interface.

OPC规范不能自动和有效地支持这些高级应用,因为没有开放和能共同操作的框架或规范用于通过当前用来访问运行时数据的相同接口而提供上述语义信息给客户机软件应用。 OPC specifications can not automatically and efficiently support these advanced applications, because there is no open and interoperable framework or specification for the interface running the same current is used to access the data provided by the aforementioned semantic information to the client software application.

所需要的是用于集成的现场总线数据服务器结构的一种框架和共同规范,其可以向客户机应用软件提供简单的和复杂的运行时数据的语义。 What is needed is a framework and a common specification for an integrated field bus data server architecture that can provide simple and complex semantic runtime data to the client application software.

所需要的是用于集成的现场总线数据服务器结构的一种框架和共同规范,其迁移对现有的工厂/企业客户机应用软件,例如HMI和其它OPC软件应用的支持,同时对高级客户机应用软件(例如工厂/企业管理、配置、维护和诊断应用软件)的运行时数据的自动识别、翻译和处理所需要的语义进行标准化和集成。 What is needed is a framework and common norms for the integration of field bus data server architecture, application software migration of existing plant / corporate clients, such as support HMI and other OPC software applications, while senior client application software (such as factory / business management, configuration, maintenance and diagnostic applications) automatically recognize the semantics of runtime data translation and processing needed to be standardized and integrated.

所需要的是一种集成的现场总线数据服务器结构,它补充H1、HSE和其它现场总线结构,以便工厂/企业应用软件可以利用相应的语义信息来自动地翻译该运行时数据。 What is needed is an integrated fieldbus data server architecture that complements H1, HSE Fieldbus and other structures, to the plant / enterprise application software with the corresponding semantic information to automatically translate the runtime data.

所需要的是一种集成的现场总线数据服务器结构,它提供用于工厂/企业应用软件访问运行时数据和相应语义信息的单个接口。 What is needed is an integrated fieldbus data server architecture that provides a single interface for the plant / enterprise application software to access the runtime data and semantic information corresponding.

发明内容 SUMMARY

本发明的实施例克服了上述的以及其它的缺点。 Embodiment of the present invention overcomes the foregoing and other disadvantages. 本发明的实施例满足上述需要。 Embodiment of the present invention satisfies the above needs. 本发明的实施例提供一种新的和改良的控制系统结构,它具有用于客户机应用软件的单个服务器接口,其通过在线提供高级工厂/企业管理、操作、配置、维护和诊断应用软件对运行时数据和语义信息的即时电子访问来消除人工干预。 Embodiments of the present invention to provide a new and improved control system architecture, a single server having an interface for client application software that provides advanced facility / online management, operation, configuration, maintenance and diagnostic applications software instant electronic access runtime data and semantic information to eliminate manual intervention.

本发明的实施例在此被共同称为“集成现场总线数据服务器结构”(IFDSA)。 Embodiments of the invention are collectively referred to herein "integrated fieldbus data server architecture" (IFDSA). IFDSA提供分别用于映射'892专利和'697申请中描述的运行时数据(诸如H1和HSE现场总线设备数据)的语义信息的框架和规范,并且还为客户机应用软件定义单个接口。 IFDSA are provided for mapping '892 patent and the' run-time data (such as H1 and HSE fieldbus device data) 697 described in the application specifications and semantic information of the frame, and also to a single client application software defined interface. IFDSA框架使能对FF和其它控制设备类型的自动适配。 IFDSA enabling automatic adaptation to the frame FF and other types of control devices.

通过提供一种方法和设备来实现用于高级应用包的建立的人工干预的消除,所述方法和设备用于:访问工作FF设备的运行时“活动列表”,建造/更新一个被格式化为与从OPC基金会可获得的OPC规范兼容的标准化浏览树形结构,并且把FF目录信息(它提供用于所有FF现场总线的语义信息和其它控制设备运行时数据)映射到新的服务器目录。 Used to build advanced applications to implement the package of eliminating manual intervention, by the method and apparatus for providing a method and apparatus: "Activity List" Run FF devices when accessing work, construction / update is formatted as a compatible with the specifications, available from the OPC Foundation standardized OPC browse tree structure, and the FF directory information (which provides semantic information for all FF fieldbus and other control equipment runtime data) mapped to the new server directory. 服务器目录包含与FF目录相同的语义信息,但是被格式化为与可从OPC基金会中获得的OPC规范兼容。 FF Directory Server Directory contains the same semantic information, but is formatted to OPC Specifications available from the OPC Foundation compatible. OPC兼容的浏览树和语义信息接着被服务器透明地提供给客户机应用软件。 OPC-compatible browser tree and semantic information is then transparently by the server to the client application software.

IFSDA实现了单个接口,因为客户端的客户机应用软件不再必须使用分开的接口来访问语义信息和运行时数据.由于FF语义和运行时数据对OPC规范的映射是在通信层之上,所以这种解决方案在实施方案发展到例如web服务之类的更新的技术时仍保持有效。 IFSDA implements a single interface, because the client application client software no longer has to use separate interfaces to access runtime data and semantic information. Since FF semantic and runtime data mapping to the OPC specification is over a communications layer, so that remain valid kinds of solutions in the implementation of program development to newer technologies such as web services and the like.

附图说明 BRIEF DESCRIPTION

参考附图,从下列描述中本发明的特征和优点对本领域技术人员来说将变得显而易见,附图中类似数字是指类似项,并且:图1是示出根据本发明原理的、集成的开放和能共同操作的控制系统的可仿效实施例的框图;图2是示出根据本发明原理的、具有FF目录映射的集成现场总线数据服务器结构的可仿效实施例的框图;图3A是说明根据本发明原理的、在集成现场总线数据服务器结构的可仿效实施例中创建服务器目录来使能自动访问的可仿效方法的流程图;图3B是一张图表,说明了一个服务器目录中的可仿效的标准化浏览树形结构,并且图形地说明了从创建服务器目录来使能自动访问的方法中,建造/更新具有可仿效活动列表与设备目录的标准化浏览树形结构的步骤;图4是一张图表,说明了在FF目录中的可仿效设备和从该设备映射的、在服务器目录中的可 Referring to the drawings, features and advantages of the present invention from the following description to those skilled in the art will become apparent from the accompanying drawings in which like numerals refer to similar items, and: FIG. 1 is a diagram illustrating the principles of the invention, an integrated block diagram of and exemplary embodiment of an open and control systems interoperable; FIG. 2 is a diagram illustrating the principles of the invention, an integrated fieldbus data server architecture FF directory mapped block diagram illustrating and exemplary embodiment; FIG. 3A is according to principles of the present invention, the data bus in the integrated server architecture could follow the field to create a directory server and exemplary flowchart of a method to automatically access that the embodiment; FIG. 3B is a graph, illustrates a directory server may be follow the example of standardization browse tree structure, and graphically illustrates the server from the directory to create a method to automatically accessible, construction / update has steps could follow the list of activities and equipment directory standardized browse tree structure; Figure 4 is a graphic that can emulate the device described in the FF directory and mapped from the apparatus, the server directory may 效OPC项,并且图形地说明了从创建服务器目录来使能自动访问的方法中,作为把FF目录映射到服务器目录的步骤的一部分,把设备映射到服务器目录的OPC项的替换步骤;图5是一张图表,说明了在FF目录中的可仿效应用处理(AP)目录和从FF目录映射的、在服务器目录中的可仿效OPC项,并且图形地说明了从创建服务器目录来使能自动访问的方法中,作为把FF目录映射到服务器目录的步骤的一部分,把AP目录映射到服务器目录的OPC项中的替换步骤;图6是一张图表,说明了在FF目录中的可仿效FF对象和从FF对象映射的、在服务器目录中的可仿效OPC项,并且图形地说明了从创建服务器目录来使能自动访问的方法中,作为把FF目录映射到服务器目录的步骤的一部分,把FF对象映射到服务器目录的OPC项的替换步骤;和图7是一张图表,说明了根据本发明原理的、在OPC服 Effect OPC items, and graphically illustrates the creation server directory to a method to automatically accessible as part of the step of the FF directory mapping to the server directory, the step of replacing the OPC items mapping device to a server directory; FIG. 5 It is a chart that illustrates the FF directory and exemplary application process (AP) from the FF directory and directory map, directory server and exemplary OPC items, and graphically illustrates the directory from the server to create automatically enabled the method of access, as part of the step of mapping the FF directory into the server directory, the OPC item is mapped to the AP directory server directory in the replacing step; FIG. 6 is a graph, illustrates the directory may be emulated FF FF objects and mapped from the FF Object, and exemplary OPC items in the server directory, and graphically illustrates the creation server directory to a method to automatically accessible, as the step of the FF directory mapped to the server directory part, the FF directory objects mapped to the server the step of replacing the OPC items; and FIG. 7 is a graph, illustrates a principle of the invention, the OPC server 器中、在集成现场总线数据服务器结构的可仿效实施例的可仿效服务器目录中,客户机应用软件利用服务器浏览功能访问被映射的FF语义信息并利用服务器数据访问功能来访问与语义信息相应的运行时数据的一种可仿效方法。 Vessel, integrated fieldbus data server architecture may be emulated server directory and exemplary embodiments, the client application software using the Server Browse Function access FF semantic information is mapped using the server data access function to access corresponding to a semantic information a method of operating data may emulate method.

具体实施方式 Detailed ways

为了简洁和说明的目的,主要通过参考可仿效实施例来描述本发明,特别地是通过一个利用H1、HSE、OPC(既指客户机操作也指服务器操作)的控制系统的可仿效实现和客户机应用软件来描述。 For purposes of simplicity and illustration, by referring mainly replicable examples describe the present invention, in particular a replicable achieved and clients a utilization H1, HSE, OPC (refers to both the client operation is refers server operation) of the control system application software is described. 可是,本领域普通技术人员将很容易认识到:相同的原理同样适用于其它的、利用任意其它集成结构的实现和设计并能够在其中实现,且任意此类变化将是在未偏离本发明实际精神和范围的这种修改之内的。 However, those of ordinary skill in the art will readily recognize: the same principles are equally applicable to other, by any other implementation and design of the integrated structure and can be implemented therein, and any such variations will be practical without departing from the present invention the spirit and scope of this change within the. 更明确地,本领域普通技术人员将很容易认识到:在可仿效实施中应用到OPC的原理同样适用于非OPC实现。 More specifically, those skilled in the art will readily recognize: applications could follow the implementation of the OPC principle also applies to non-OPC implementation.

I.IFDSA概览参见图1,集成控制系统结构的示例100被示出,在此,标准以太网设备130被用来把HSE链接设备110、HSE设备120和工厂/企业计算机190互连到以太网140。 I.IFDSA Overview Referring to Figure 1, an exemplary integrated configuration of the control system 100 is shown, in this case, a standard Ethernet device 130 is used to HSE Linking Devices 110, 120 and HSE devices plant / enterprise computer 190 interconnected to Ethernet 140. HSE链接设备110进而又利用H1网络150连接到H1设备170。 HSE Linking Device 110 in turn is connected to the network 150 using H1 H1 device 170. 客户机应用软件180运行于工厂/企业计算机190上。 The client application software 180 runs on the facility / 190 computer. 服务器软件可以运行于工厂/企业计算机190、HSE链接设备110或HSE设备120上。 Server software can run on the plant / enterprise computer 190, the HSE HSE linking device 110 or device 120. 客户机应用软件190还可以运行于HSE链接设备110或HSE设备120上。 The client application software 190 can run on device 110 or link 120 HSE HSE devices. 实际的硬件和软件配置将取决于特定的应用需要。 The actual hardware and software configurations will depend upon the specific application needs. 然而,可以使用除了如图1所示的可仿效拓扑之外的网络拓扑、设备或配置,并且这样的变化将处在不偏离本发明的实际精神和范围的这种修改之内。 However, the network topology may be used, or the device may be arranged in addition to emulate the topology shown in Figure 1, and such variations will be within without departing from the true spirit and scope of the invention of such modifications.

根据本发明原理的实施例的IFDSA组件如图2所示。 The assembly 2 shown in FIG. IFDSA embodiment according to the principles of the present invention. IFDSA被设计成例如利用H1、HSE、OPC和客户机应用软件去满足集成的高性能分布式制造和过程控制环境的功能需求。 IFDSA be designed, for example using H1, HSE, OPC client applications, and to meet high performance integrated manufacturing and process control functions distributed environment requirements. IFDSA允许从各种H1、HSE和其它的控制与测量设备、由不同厂商制造的客户机应用软件和服务器软件来构造分布式的自动化系统。 IFDSA allows the various H1, HSE and other control and measurement equipment manufactured by different vendors client application and server software to construct the distributed automation system. IFDSA是通过已经适应于H1、HSE和OPC环境特性的结构组件来描述的。 IFDSA been adapted by H1, HSE and structural components described environmental characteristics of OPC.

在下面的公开内容中引用的各种协议和标准在此处附件I里列出的手册和规范中被详细描述,它们可从现场总线基金会(总部设在Texas,Austin的一个非盈利组织)公开地获得。 In the following disclosure reference manuals and specifications of various protocols and standards listed in Annex I to here is described in detail, they are available from the Fieldbus Foundation (a non-profit organization headquartered in Texas, Austin's) publicly available. 通过呼叫512-794-8890或者登陆www.fieldbus.org,可以定购该规范和手册。 By calling 512-794-8890 or visit www.fieldbus.org, which can be ordered specifications and manuals. 因此这些手册和规范每一个各自的当前版本在此被整体引入作为参考。 Thus these manuals and specifications of each of the respective current version of the entirety is herein incorporated by reference. 在下面更详细地描述IFDSA的每一结构组件(如图2所示)。 Each of the structural components IFDSA (shown in FIG. 2) is described below in more detail.

II.IFDSA组件图2说明了IFDSA 50的一个可仿效实施例。 2 illustrates II.IFDSA assembly 50 may emulate a IFDSA embodiment. 正如所示出的,IFDSA 50最好包括OPC160和现场总线设备280(例如,H1设备170和HSE设备120-参见图1)。 As shown, IFDSA 50 preferably comprises OPC160 and Fieldbus Devices 280 (e.g., H1 and HSE devices 120- device 170 Referring to FIG. 1). OPC160的功能和组件可以被合并到单个OPC160计算机中或者被扩展到多个OPC160计算机中。 OPC160 functions and components may be combined into a single computer or OPC160 be extended to a plurality of computers OPC160. OPC160最好经由现场总线网络290与现场总线设备280通信(例如,H1网络150和以太网140-参见图1)。 290280 OPC160 best communication via the field bus network and Fieldbus devices (e.g., H1 Ethernet network 150 and 140- see Figure 1).

在示出的实施例中,OPC160最好包括客户机应用软件180和OPC客户机210。 In the embodiment illustrated, OPC160 preferably include a client application software 180 and OPC client 210. 客户机应用软件180使用OPC客户机210来访问OPC服务器220中的信息。 Client Application Software 180 uses the OPC client 210 to access information from the OPC server 220. OPC客户机210和OPC服务器220可以位于单个计算机中,或者,它们可能在通信网上的分开的计算机中(客户机和服务器之间的通信网未在图2中示出)。 OPC clients and OPC servers 210 may be located in a single computer 220, or they may be (a communication network between a client and a server are not shown in FIG. 2) in a separate computer in the communication network.

运行在OPC160中的客户机应用软件180可以包括各种软件(例如,作为分开的程序或者同一软件的分开的模块)。 Running the client application software 180 may include OPC160 in a variety of software (e.g., as separate modules or the same software program separate). 例如,客户机应用软件180可以包括人/机接口应用软件181、维护/诊断应用软件182、配置应用软件183以及其它工厂/企业应用软件184。 For example, the client application software 180 may include a human / machine interface application software 181, maintenance / diagnostic applications 182, 183, and other application software to configure factory / enterprise application software 184. 优选实施例定义了要被包括在其它工厂/企业应用软件184中的现有的客户机应用软件。 Preferred embodiments are defined to be included in an existing client application software in other plant / enterprise application software 184.

再次参见如图2所示的实施例,第二OPC160计算机最好包括OPC服务器220和FF服务器模块230。 Embodiment 2 Referring again to the embodiment shown in FIG, preferably comprising a second OPC160 OPC server computer 220 and the FF Server Module 230. OPC服务器220例如可以是一个虚拟服务器,并且最好包括一个服务器浏览功能270。 OPC server 220 may be, for example, a virtual server, and preferably including a Server Browse Function 270. 优选地,在OPC服务器220(更明确地说是服务器浏览功能270)和OPC客户机210之间启用并保持通信。 Preferably, the OPC server 220 (more specifically a Server Browse Function 270) is enabled and maintaining communication between the client 210 and the OPC. FF服务器模块230最好包括FF目录240、映射功能250和服务器目录260。 FF FF Server Module 230 preferably comprises a directory 240, a directory server 250, and a mapping function 260. 优选地也在OPC服务器220(更明确地说是服务器浏览功能270)和FF服务器模块230(更明确地说是服务器目录)之间启用并保持通信。 And preferably also enable maintaining communication OPC (more specifically a Server Browse Function 270) and the FF Server Module 230 (more specifically a directory server) between the server 220.

III.IFDSA目录映射继续参考图2中说明的实施例,FF服务器模块230优选地监视活动列表400,它代表现场总线设备280中的工作的现场总线设备。 III.IFDSA directory mapping continues embodiment described with reference to FIG. 2, the FF Server Module 230 preferably monitors activity list 400, which represents the active fieldbus devices 280 fieldbus devices. 在优选实施例中,按照附件I中的且可从现场总线基金会中获得的FF规范来创建活动列表400。 In a preferred embodiment according to the FF Specifications in Appendix I and available from the Fieldbus Foundation to create an event list 400. 活动列表400识别FF服务器模块230可用的现场总线设备280。 Active list identifying Fieldbus devices 280,400 FF Server Module 230 available. 对于活动列表400中列出的每个设备,有一个厂商特定的标识符的相应列表,称为对象词典(OD)索引(OD索引在图2中未示出)。 For each active device list 400 listed specific list of identifiers corresponding to a vendor, called an object dictionary (OD) index (OD index in FIG. 2 not shown). OD索引在现场总线设备280中具有相应的运行时对象。 OD index runtime objects having a respective Fieldbus device 280. 设备中的可仿效运行时对象在'892申请中被描述并且包括:资源块对象、转换器块对象、功能块对象、趋势对象、视图对象、链接对象、告警对象、系统时间对象、功能块调度对象和网络业务对象。 Objects that can be described in the '892 application, to emulate the runtime apparatus and comprising: a resource block object, converter block objects, function block objects, trend objects, view objects, link objects, alert objects, the system time of the object, function block schedule network objects and business objects.

虽然厂商可以定义另外的运行时对象,但是优选地通过附件I中引用的FF规范来将运行时对象定义为FF对象。 While vendors can define additional runtime objects, but preferably by the FF Specifications in Annex I to the referenced object definitions FF runtime object. 在任一情况中,上面所提及并且在'892申请(以及附件I中列出的FF规范)中描述的DD和CF技术最好被用于描述运行时对象。 In either case, mentioned above, and (FF and specifications listed in Annex I) in the '892 application DD and CF are described in the art is preferably used to describe the runtime objects. DD和CF文件扩展了设备中每个对象的描述,控制系统需要该描述来翻译包括人机接口功能(诸如校准和诊断)在内的现场总线设备中的数据的含意。 DD and CF files expanded description of each object in the device, the control system needs to translate the meaning of data including the human interface functions (such as calibration and diagnostics) including the Fieldbus device is described.

DD/CF文件可以按照ASCII文本或者任何标准化程序设计语言(比如C、C++或者SmallTalk)来写出。 DD / CF files can be written in accordance with the ASCII text or any standardized programming language (such as C, C ++ or SmallTalk). 在优选实施例中,DD文件按照DD语言(DDL)来编写,而CF文件是如附件I中列出的并且可以从现场总线基金会中获得的FF规范所描述的ASCII文本文件。 In a preferred embodiment, according to DD DD file language (DDL) to write, and CF files are ASCII text files and available from the Fieldbus Foundation as listed in Annex I FF Specifications described.

FF目录240最好由称为活动列表的所有现场总线设备280的列表以及包含在每个FF设备中的AP目录构成。 FF Directory 240 is preferably composed of all Fieldbus devices called active list 280 and a list of directories contained in each AP FF device configuration. 可以通过侦听FF网络业务来构造该活动列表,或者可以从包含该活动列表的现场总线设备280中读取它。 The event list may be constructed by listening to network traffic FF, or it may be read from Fieldbus Devices 280 containing the active list. AP目录由FF服务器模块230经由现场总线网络290从该现场总线设备现场总线设备280中读取,或者可以通过读取CF文件(DD和CF文件被提供给每个FF现场总线设备)而本地获取AP目录。 AP Directory 230 290 read by the FF server module via a network from the Fieldbus field devices Fieldbus bus device 280, or by reading files CF (DD and CF files are provided to each FF fieldbus device) acquired from local AP directory.

OD索引被使用作为FF协议服务中的一个关键属性来访问运行时对象。 OD index is used as the FF protocol services in a key property to access running object. 因此,客户机应用软件180可以通过从FF目录240中获取运行时数据的相应OD索引来访问现场总线设备280中的该运行时数据。 Thus, the client application software 180 may access the data bus device to the operating site through the corresponding OD 280 index obtaining operating data from the FF Directory 240.

OPC160将运行时对象建模为“OPC项”。 OPC160 runtime object modeling as "OPC item." OPC项由包含厂商特定的名称的“项ID”来识别。 OPC items identified by the "item ID" contains vendor-specific names. OPC服务器220中的OPC项经由服务器浏览功能270被呈送给OPC客户机210。 OPC server 220 OPC items via the server browse function 270 is presented to the OPC client 210. 服务器浏览功能270允许OPC服务器220在按照OPC规范构造的树形结构中定位OPC项。 Server Browse Function 270 to the OPC Server 220 is positioned in the tree structure the OPC Item per OPC Specifications constructed. OPC客户机210使用服务器浏览功能270来定位所关心的项。 OPC client server 210 using the browser function 270 items of interest to locate.

当前,没有标准化分支和叶节点组织或者使用于服务器浏览功能270中的ID命名,因此,在没有浏览树以及其中的每个OPC项的人工翻译的情况下,OPC客户机210不能定位所关心的OPC项。 Currently, there is no standardization organizations or branches and leaf nodes used in naming the server browse function ID 270, and therefore, in the absence of human translation browse tree and each OPC item therein, the client 210 can not locate OPC interest OPC items. 这阻止OPC客户机210自动访问和处理OPC服务器220中的OPC项。 This prevents OPC items 210 OPC clients to access and automatic processing OPC server 220.

为了解决这个问题,IFDSA 50提供一个标准服务器目录260,创建它来代表FF目录240。 To solve this problem, IFDSA 50 provides a standard directory server 260, it was created to represent the FF Directory 240. 服务器目录包含与FF目录240相同的对象语义信息,但是它被映射来与OPC对象相兼容。 FF Directory Server Directory contains the same semantic information of the object 240, but it is mapped to an object compatible with OPC. 服务器目录260中的标准化浏览树形结构261定义分支和叶节点组织以及现场总线设备160的命名,以使服务器浏览功能270能通过服务器目录260中的OPC兼容的语义信息来定位它的、现场总线设备280和它们的数据的表示。 Server Directory 260 261 standardized browse tree structure defines a branch and leaf node organization and naming Fieldbus device 160 to the server that the OPC compatible semantic information browsing server directory 260 to locate it by 270, the fieldbus presentation device 280 and their data. 一旦被定位,则OPC兼容的语义信息和数据值(如果有的话)被经由服务器浏览功能270和相关的OPC160服务而透明地提供给客户机应用软件180。 Once positioned, the OPC compatible semantic information and data values ​​(if any) are transparently provided to the client application software 270 via the server browse function and related services 180 OPC160.

映射功能250把现场总线设备280的活动列表400和应用处理(AP)目录信息通过一个自动产生的OPC访问路径名称和/或一个完全合格的项ID(以下称为OPC项引用)而映射到服务器目录260。 Mapping function 250 Fieldbus devices 280 active list 400 and the application process (AP) to access directory information via the OPC path name and / or a Fully Qualified Item ID automatically generated (hereinafter referred to as OPC Item reference) mapped to the server 260 directory. 按照附件I列出的并且可从现场总线基金会中获得的手册或规范来编写AP目录。 In accordance with and available from the Fieldbus Foundation specifications manual or listed in Annex I to write the AP directory. OPC访问路径名称定义了通过服务器浏览功能270到FF目录240的服务器特定的路径。 OPC defines the access path name server 270 through the Server Browse Function 240 to the FF directory particular path. OPC完全合格的项ID是一个到表示FF目录240中的相应运行时对象的项的句柄。 OPC Fully Qualified Item ID is a handle to the item representing the object in the respective operating time of the FF Directory 240. OPC访问路径、OPC完全合格的项ID以及服务器浏览功能是按照OPC规范编写并且从OPC基金会可得。 OPC access path, OPC fully qualified item ID and server browsing capabilities and are prepared in accordance with OPC specification from the OPC Foundation can be obtained.

图3A说明了创建服务器目录260来使能自动访问的方法300的实施例。 3A illustrates the directory server 260 to create a method to Example 300 to automatically access. 正如所看到的,当集成控制系统供电310时方法300开始,并且它包括如下步骤:访问现场总线设备280的活动列表400,步骤320;建造/更新标准化的浏览树形结构261,步骤330;把来自工作的现场总线设备280中的AP目录和FF对象复制到FF目录240中,步骤340;把FF目录240映射到服务器目录260中,步骤350;判定这里是否有一个活动列表400变化,步骤360;并且,如果是,则重复步骤330-360;而如果否,则重复步骤360。 As can be seen, when the integrated control system method 300 begins 310 when the power supply, and it comprises the following steps: 280 active fieldbus devices access list 400, step 320; build / update a standardized browser tree structure 261, step 330; copy the AP directories and FF objects fieldbus device from the work 280 in the FF directory 240, step 340; the FF directory 240 is mapped to server directory 260, step 350; determines whether here is a list 400 changes an event, step 360; and, if so, repeating steps 330-360; and if not, step 360 is repeated.

最好使用在附件I的FF规范中定义且可从现场总线基金会获得的协议服务来执行访问步骤320。 It is preferably used and may be defined in step 320 to perform access from the Fieldbus Foundation protocol service obtained in the FF Specifications in Annex I. 建造/更新步骤330最初用从现场总线设备280中读取的活动列表400设备标识信息来构造标准化的浏览树形结构261。 Construction / the first list 400 updated in step 330 with the device identification information read from the active fieldbus devices 280 to construct the tree structure 261 standardized browser.

最好使用在附件I的FF规范中定义且可从现场总线基金会中获得的协议服务来执行步骤330中的信息的读取。 Preferably used are defined in the FF Specifications in Annex I of the protocol service and available from the Fieldbus Foundation reading information is performed in step 330. (对于由此步骤访问数据的更详细描述,请参见图3B和下面的图3B的相应描述。)最好这样来执行复制步骤340:1)使用在附件I的FF规范中定义并且可从现场总线基金会中获得的协议服务来读取与活动列表400中的工作设备相应的现场总线设备280的AP目录和FF对象,并且把该数据放置在缓冲器中,和2)把数据从缓冲器复制到FF目录240。 (For a more detailed description whereby the step of accessing data, see corresponding Figure 3B and described below in FIG. 3B.) Is preferably performed so that the replication step 340: 1) in Annex I and as defined in the FF Specifications available from the field fieldbus Foundation protocol services to reads obtained in the active list 400 and the working device AP directory objects corresponding FF fieldbus devices 280, and this data is placed in the buffer, and 2) data from the buffer copy to the FF directory 240. 映射步骤350通过为每个设备把一个AP目录以及包含在FF目录240中的每个FF对象映射到服务器目录260中的OPC项,来把FF目录240中的数据映射到服务器目录260。 Mapping step for each device 350 through the directory and AP contained in a FF FF Directory 240 for each object is mapped to the OPC Item in the server directory 260, the map data to the FF Directory 240 into the Server Directory 260. 对于此步骤的更详细说明以及把这些映射到OPC项的替换步骤,请参见图4-6和下面的它们的相应说明。 For a more detailed description of this procedure and the corresponding description of these alternative steps mapped to OPC items, see Figure 4-6 and below thereof.

继续参考图3A,判定步骤360动态地判定活动列表400中是否有变化。 With continued reference to Figure 3A, decision step 360 determines dynamically whether there are changes in the active list 400. 步骤360使用与步骤320相同的协议来访问活动列表400,然后把刚刚获得的该活动列表的新拷贝与前一拷贝进行比较并判定自从步骤360的上一次执行以来哪些现场总线设备已经添加到现场总线设备280中或从中删除。 Step 360 uses the same steps of the protocol 320 to access the active list 400, then the new copy of the list of activities just won compared with a previous copy and determination since the first execution of step 360 which fieldbus devices have been added to the site 280 bus device or remove. 因此,判定步骤360使IFDSA 50能够把FF目录240动态地映射到服务器目录260。 Thus, it is determined in step 360 that the IFDSA 50 to FF Directory 240 can be dynamically mapped to Server Directory 260.

图3B说明了具有可仿效标准化浏览树形结构261的一个可仿效服务器目录260,并且图示说明了建造/更新步骤330的实施例。 3B illustrates emulate a standardized browser 261 having a tree structure, a directory may be emulated server 260, and illustrates the build / update procedure of Example 330. 正如所示出的,对于现场总线设备280中的每个工作的现场设备,该标准化浏览树形结构261包括一个活动列表目录262入口以及一个设备目录263入口,该每个工作的现场设备由一个活动列表目录262入口明确地引用,如图中所示,或者被隐含地引用为活动列表目录262入口的子节点或属性(未示出)。 As shown, the field device to the field bus device 280 in each job, the normalized browse tree structure 261 includes a list of active directory entry 262 and a device directory entry 263, each of the field device consists of a working event list directory 262 entry explicitly recited, as shown in FIG., or the referenced child nodes or attributes for the active list directory 262 entry implicitly (not shown).

参见图2和3B,优选地,服务器目录260结构与FF目录240结构的组织相匹配。 Referring to FIGS. 2 and 3B, the organizational structure is preferably 240, the server directory structure of the FF Directory 260 match. FF目录240中的每个AP目录引用由一个开始OD索引和多个对象组成。 FF Directory 240 directory referenced by each AP OD start index and a plurality of objects. 在优选实施例中,该设备标识信息(例如,设备ID、现场总线网络地址、物理设备标记和其它相关数据)提供允许客户机自动识别现场总线设备280的语义信息。 In a preferred embodiment, the device identification information (e.g., device ID, a fieldbus network address, a physical device tag and other related data) provided to allow a client to automatically identify the Fieldbus device 280 is the semantic information. 它最好是从使用在附件I中并且可从现场总线基金会中获得的、FF规范中定义的协议服务的现场总线设备280被读取的,并且优选地,利用自动产生的项ID/路径、按照以下两个方式之一被映射到服务器目录260中:1.在被映射到服务器目录260时、FF目录240中的每个AP目录引用由识别包含该对象的分支的一个开始OPC项引用组成,且该对象的子对象被表示为在此分支之下的项。 It is preferably available from Appendix I and in the Fieldbus Foundation, Fieldbus device protocol services defined in the FF Specifications 280 is read, and is preferably, automatically generated using the item ID / path according to one of the following two ways are mapped to server directory 260: 1 when is mapped to the directory server 260, the FF directory 240 each AP directory reference in a start OPC items identified by the branch that contains the object reference composition, and a child of the object is represented as an item under this branch. 在该分支之下的各项的浏览顺序保持该OD索引按照在FF规范中对AP目录内表示的对象所定义的顺序;或者2.在被映射到服务器目录260时、在FF目录240中的每个AP目录入口可以由相应OPC项的OPC项引用组成。 Under the navigation order of the sequence of the branch is maintained OD indexed by the AP Directory objects shown in the FF Specifications as defined above; or 2. When the server is mapped to the directory 260 in the FF Directory 240 each AP directory entry may be composed of OPC items referenced by the corresponding OPC items. 在这种情况下,服务器目录260中的FF子对象由它们自己的、与该子对象对应的OPC项的OPC项引用表示。 In this case, the FF directory server sub-object 260 is represented by their own, the child object corresponding to OPC Item OPC Item references.

如图4所示,方法300的优选实施例的映射步骤350把活动列表入口242从FF目录240映射到服务器目录260中。 The mapping step 350 of embodiment Live List Entry 242 240 mapped from the FF Directory into the server directory 260 as shown in FIG Preferably, method 300 embodiment 4. FF目录240中的可仿效活动列表入口242和可仿效的OPC项262a、262b和262c与下面描述的替换映射选项对应。 FF Directory 240 and exemplary list of events and the inlet 242 may emulate the OPC Items 262a, 262b and 262c to the alternative mapping options described below correspond. 对于每个映射选项,自动地产生OPC项ID和路径(图上未示出)。 For each mapping options, the OPC Item ID is automatically generated and path (not shown in the figure).

映射选项1,把活动列表入口242映射到由OPC浏览和读取服务访问的分支和叶节点的一个树形结构。 Mapping Option 1, Live List Entry 242 mapped into a tree structure browsing and reading services accessed by OPC branch and leaf nodes. 活动列表入口242最好包括识别位于现场总线设备280中的设备并与其通信所需要的设备识别信息。 Live List Entry 242 preferably includes a device identification information for identifying Fieldbus devices 280 located in the equipment needed for communication therewith. OPC项262包括按照OPC规范来格式化为OPC项的已映射的设备识别信息,并且OPC项262a包括按照OPC规范来格式化为OPC项的该设备的已映射的设备目录信息或者引用;和映射选项2,把活动列表入口242映射到由OPC数值读取服务访问的单个结构化的OPC项。 OPC Item per OPC Specifications 262 includes the device identification information is formatted mapped OPC items, and the OPC Item 262a includes a device directory information is formatted according to the specifications of the OPC device is mapped OPC items or references; and mapping option 2, mapping the Live list entry 242 to a single structured OPC value read by the service access OPC items. OPC项262b包括设备识别信息以及该设备的已映射设备目录信息或者对它的一个引用,其按照OPC规范被格式化并映射到一个OPC数值。 OPC Item 262b includes device identification information and device mapped Device Directory information or a reference to it, which is formatted and mapped to an OPC value in accordance with the OPC specification. 因此,该设备目录或者对它的一个引用被包括在表示该设备的浏览树项的数值中,和映射选项3,把活动列表入口242映射到OPC获取属性服务访问的单个结构化的OPC项属性。 Thus, the device directory or a reference to it is included in the OPC property tree browser item numerical representation of the device, and mapping Option 3, mapping the Live List Entry 242 to obtain the attributes of the service access OPC single structured . OPC项262c包括设备识别信息以及该设备的已映射设备目录信息或者到它的一个引用,其按照OPC规范被格式化并映射到OPC属性。 OPC Item 262c includes device identification information and the device with a reference to directory information, or mapped to the device, it is formatted and mapped to OPC Properties per OPC Specifications.

图5说明了在FF目录240中的可仿效AP目录244和在服务器目录260中、从AP目录244中映射的可仿效OPC项264a、264b和264c。 Figure 5 illustrates the FF Directory 240 and exemplary AP Directory 244 and 260 in the server directory, from the AP Directory 244 and exemplary OPC Items Mapping 264a, 264b and 264c. 在一个优选实施例中,AP目录244可以是三个AP目录中的任何一个:即通常所说的功能块应用处理(“FBAP”)目录、系统管理信息库(“SMIB”)目录、网络管理信息库(“NMIB”)目录或者任何其它按照附件I中列出的且可以从现场总线基金会中获得的手册或规范来编写的AP目录。 In a preferred embodiment, three AP Directory AP Directory 244 may be any one of: a functional block known as the application processing ( "FBAP") directory, the system management information base ( "SMIB") directories, network management information Base ( "NMIB") or any other directory and in accordance with Annex I listed can be obtained from the fieldbus Foundation specifications in the manual written in AP or directory. 正如所示的,该AP目录244最好包括:如在附件I中的且可以从现场总线基金会中获得的FF规范中定义的报头、目录入口(例如,复合对象引用和复合列表引用)。 As shown, the AP Directory 244 preferably comprises: a header such as the FF Specifications and are available from the Fieldbus Foundation in Annex I is defined in the directory entry (e.g., the composite and the composite list of object references cited). 该OPC项264a、264b和264c与下面描述的替换映射选项对应。 The OPC Items 264a, 264b and 264c to the alternative mapping options described below correspond.

如图5所示,方法300的优选实施例的映射步骤350通过构造OPC项引用的三个替换映射选项或步骤来把AP目录244从FF目录240映射到服务器目录260中。 5, the mapping step 350 of the preferred embodiment of a method 300 for mapping the AP Directory 244 240 from the FF Directory 260 into the Server Directory OPC Items configured by three alternative mapping options or steps referenced. 对于所有的映射选项,自动地产生该OPC项ID和路径(图上未示出)。 For all mapping options, the automatically generating the OPC Item ID and Path (not shown on the figure). AP目录映射选项或步骤是:映射选项1,把AP目录244映射到OPC浏览和读取服务访问的分支和叶节点的一个树形结构。 AP directory mapping options or steps are: 1 mapping options, the AP 244 is mapped to a directory tree structure OPC Browse and Read access service branch and leaf nodes. OPC项264a包括映射到OPC项报头阵列的AP目录244报头信息和映射到格式化为OPC规范的OPC项引用的AP目录244入口;映射选项2,把AP目录244映射到OPC数值读取服务访问的单个结构化OPC项。 OPC Item 264a includes a mapping to the OPC item headers array AP Directory 244 header information and mapped to the AP Directory formatted to OPC items on OPC Specification referenced 244 inlet; Mapping Option 2, the AP Directory 244 is mapped to OPC value read service access single structured OPC items. OPC项264b包括AP目录报头和目录入口,它们按照OPC规范被格式化并被映射到一个OPC数值;和映射选项3,把AP目录244映射到OPC获取属性服务访问的单个结构化OPC项属性。 OPC Item 264b includes AP Directory Header and directory entries, which are formatted and mapped to an OPC value per OPC Specifications; and Mapping Option 3, mapping the AP Directory 244 to obtain the attributes of the service access OPC single structured OPC Item property. OPC项262c包括AP目录报头和目录入口,它们按照OPC规范被格式化并被映射到OPC属性。 OPC Item 262c includes AP Directory Header and directory entries, which are formatted and mapped to OPC Properties per OPC Specifications. 优选地,OCP项数值被设置为“空。”图6说明了在FF目录240中的可仿效FF对象246和在服务器目录260中的可仿效OPC项266a和266b,可仿效OPC项266a和266b与下面描述的且从FF对象246映射的替换映射选项相应。 Preferably, OCP entry value is set to "empty." Figure 6 illustrates the FF Directory 240 and exemplary FF Object 246 and the Server Directory 260 and exemplary OPC Items 266a and 266b, and exemplary OPC Items 266a and 266b the following description and from the alternative mapping options FF Object 246 corresponding mapping. 在优选实施例中,FF对象246是按照在附件I中列出的且可以从现场总线基金会中获得的手册或规范编写的任意对象。 In a preferred embodiment, FF Object 246 is prepared in accordance with any object listed in Appendix I and available from the Fieldbus Foundation manuals or specifications. FF对象246最好包括一个对象值,该对象值可以是运行时数据;一个对象DD,它可选地包含用于FF对象的DD;和一个对象CF,它可选地包含用于FF对象的CF。 FF Object 246 preferably includes a target value, the target value may be a runtime data; DD an object, which optionally contain FF DD for the object; and an object CF2, which optionally contains objects FF CF. OPC项266a和266b与下面描述的替换映射选项对应。 OPC Items 266a and 266b described below with alternative option corresponds to the mapping.

如图6所示,方法300的优选实施例的映射步骤360通过构造OPC项引用的两个替换映射选项或步骤来把FF对象246从FF目录240映射到服务器目录260中。 6, the mapping step 300 of the preferred embodiment of a method 360 to 246,240 FF Object mapping from the FF Directory 260 into the Server Directory OPC Items configured by two alternative mapping options or steps referenced. 对于两个映射选项,自动地产生OPC项ID和路径(图上未示出)。 For two mapping options, the OPC Item ID is automatically generated and path (not shown in the figure). 该FF对象映射选项或步骤是:映射选项1,利用OPC浏览和读取服务访问的分支和叶节点的一个树形结构而把FF对象246映射到OPC项266a。 The FF target mapping options or steps are: 1 mapping options, a tree using the OPC browse and read access of service branch and leaf nodes of the object and the FF 246 is mapped to OPC items 266a. OPC项266a包括映射到OPC项值的FF对象246的运行时对象值以及映射到被格式化为OPC规范的OPC项引用结构的FF对象246 DD和CF语义信息。 OPC Item 266a includes a target value of the operating mapped to the OPC Item Value of FF Object 246 when being formatted and mapped to OPC Specification OPC item reference object structure 246 FF DD and CF semantic information. 因此,每个FF对象246的语义信息由子项表示。 Thus, the semantic information of each FF Object 246 is represented by a child. 它们的每个成分在树中可以被表示为它们的子项;和映射选项2,把FF对象246映射到单个结构化OPC项266b,在此,FF对象246的运行时对象值被映射到OPC值读取服务访问的OPC项值,并且DD/CF语义信息被映射到OPC获取属性服务访问的OPC项属性。 Each component thereof may be represented in the tree as a child thereof; and Mapping Option 2, mapping the FF Object 246 to a single structured OPC Item 266b, in this operation FF target value when the object 246 is mapped to the OPC OPC value read service access key value, and DD / CF semantic information is mapped to OPC item properties OPC obtain service access.

参见图2和3A以及图4-6,对本领域技术人员来说很明显,IFDSA 50和方法300的替换实施例要消除FF目录240以及修改步骤340而把来自现场总线设备280中的AP目录和FF对象直接映射在服务器目录261中。 Referring to FIGS. 2 and 3A and 4-6, it is apparent to those skilled in the art, embodiments IFDSA 50 and 300 of the alternative methods to eliminate the step of modifying the FF Directory 240 and 340 from the AP Directory Fieldbus devices 280 and FF objects directly mapping the directory server 261. 对本领域技术人员来说也很明显的是:如果DD/CF文件的一个本地拷贝可用(例如硬盘或CD-ROM),则不需要从现场总线设备280中读出FF对象240中的对象DD和对象CF,并且一个替换实施例包括从这种本地拷贝中读取对象DD和对象CF。 The skilled artisan is also evident: if a local copy of the DD / CF files available (e.g., a hard disk or CD-ROM), the object is not necessary to read the object DD FF 240 from the Fieldbus devices 280 and Object CF, and an alternative embodiment the object comprises reading and DD objects from the local copy of this CF.

IV.IFDSA单个客户机应用软件接口现在参见图7,IFDSA 50的优选实施例提供单个接口,以便使客户机应用软件180通过OPC客户机210而访问现场总线设备280的运行时数据和语义信息。 IV.IFDSA single client application software interfaces now to Figure 7, a preferred embodiment IFDSA 50 provides a single interface to enable access to the client application software 180 running Fieldbus devices 280 and data semantic information via the OPC client 210. 通过OPC服务器220中的服务器浏览功能270来提供服务器目录中的H1、HSE和其它控制设备语义信息的位置。 Provided by the server directory H1 OPC Server Browse Function 220 in the server 270, HSE and other control devices semantic information location. 正如在上面的第I-III部分中所述的,FF服务器模块230支持OPC服务器220中的服务器浏览功能270。 As described in the first part I-III above, FF Server Module 230 supports the Server Browse Function 220 in OPC Server 270. 现场总线设备280运行时数据可以通过与语义信息相同的OPC客户机210接口而被提供给客户机应用软件180。 Fieldbus Devices 280 runtime data may be provided to the client application software 180 by the same semantic information OPC Client 210 interfaces.

OPC客户机210可以从OPC服务器220中的服务器数据访问功能271获得运行时数值数据。 OPC client 210 may obtain numerical data 271 from a server running OPC data access server 220. FF服务器模块230使用在附件I中且从现场总线基金会中可获得的FF规范中定义的协议服务来访问现场总线设备280运行时数值数据。 FF Server Module 230 uses protocol service and available from the Fieldbus Foundation defined in the FF Specifications in Appendix I to access the numerical data bus device 280 operating site. 由FF服务器模块230访问的现场总线设备280运行时数值数据对服务器数据访问功能271的映射由可以从OPC基金会中获得的OPC规范来定义。 Numerical data defined by OPC Specifications available from the OPC Foundation functional map data access server 271 is executed by the Fieldbus devices 230 FF Server Module 280 access.

新IFDSA 50的优选实施例支持现有应用软件的迁移,它被包括在其它工厂/企业应用软件184中,因为现有的应用软件只使用服务器数据访问功能271并且这个功能未被IFDSA 50改变。 Preferred embodiments of the new IFDSA 50 supports migration of existing application software, which is included in other plant / enterprise application software 184, since the existing application software uses the data access server 271 and the function is not changed IFDSA 50. 本发明包括现有应用软件与IFDSA 50中新的客户机应用软件180的迁移和共存。 The present invention includes the existing application software and IFDSA 50 new client application software 180 of migration and coexistence.

Claims (11)

1.一种动态地创建一个用于过程控制的OLE服务器目录,简称OPC服务器目录的方法,以便允许在集成控制系统中由运行在一个服务器上的客户应用自动访问一个或者多个现场总线设备,该方法包括步骤:(a)访问现场总线设备的活动列表,其中:所述活动列表表示在该集成控制系统中工作的现场总线设备;(b)建造/更新一个浏览树形结构,其中:所述浏览树形结构定义分支和叶节点组织、用于现场总线设备的命名和来自现场总线设备的数据;(c)把来自工作的现场总线设备中的应用处理AP目录和基金会现场总线FF对象复制到一个FF目录中,以使该FF目录具有与所述工作的现场总线设备相应的对象语义;和(d)把FF目录映射到OPC服务器目录中,其中该FF目录中的对象语义被映射到标准化格式的OPC服务器目录中,该OPC服务器目录是可通过运行在服务器上的客户机应用 An OLE server to dynamically create a directory for process control, a method referred to as OPC server directory, so as to permit integrated control system run by the client application on a server to automatically access one or more Fieldbus devices, the method comprising the steps of: (a) accessing a list of active fieldbus devices, wherein: the active list indicates fieldbus devices operating in the integrated control system; (b) build / update a browse tree structure, wherein: the said browse tree structure defines a branch and leaf node organization, used to name devices and fieldbus data from fieldbus devices; (c) application of the fieldbus device from the working process in the AP directories and FF objects FOUNDATION fieldbus FF copied to a directory, so that the FF has a corresponding directory object semantics fieldbus devices with the work; and (d) mapping the FF directory into the server directory OPC, wherein the object semantics in the FF directory is mapped OPC server directory to a standardized format, a directory of the OPC server by running on a client server applications 件来自动访问的。 Pieces automatically accessed.
2.权利要求1的方法,还包括如下步骤:在执行访问步骤之前向该集成控制系统供电。 The method of claim 1, further comprising the step of: prior to the step of performing integrated control system access power.
3.权利要求1的方法,还包括步骤:(e)判定在所述活动列表中是否存在改变,其中,当一个工作的现场总线设备被从集成控制系统中删除或者添加到集成控制系统时指示一个改变。 The method of claim 1, further comprising the step of: (e) determines whether there is a change in the active list, wherein, when a work indicates fieldbus device is removed from the integrated control system or to the integrated control system a change.
4.权利要求3的方法,还包括步骤:如果在所述活动列表中判定有一个改变,则重复步骤(a)-(d);以及如果在所述活动列表中判定没有改变,则重复步骤(e)。 And if it is determined there is no change in the activity list, repeating step; (d) - if it is determined in the event there is a change in the list, repeating steps (a): The method of claim 3, further comprising the step of (e).
5.权利要求1的方法,其中:服务器是一个OPC服务器,并且映射步骤把对象语义映射到OPC对象。 The method of claim 1, wherein: the server is an OPC server, and the mapping step maps the semantic object to the OPC objects.
6.权利要求5的方法,其中:映射步骤为每个现场总线设备把AP目录和包含在该FF目录中的每个FF对象映射到OPC服务器目录中。 The method of claim 5, wherein: the step of mapping each object for each FF fieldbus device and the AP Directory contained in the FF directory mapped to the OPC server directory.
7.权利要求1的方法,其中:映射步骤从FF目录中把用于每个现场总线设备的、包括至少以下之一的设备识别数据映射到OPC服务器目录中,即:链接/分段ID、节点ID、设备ID以及PD标记数据。 The method of claim 1, wherein: the mapping step from the FF directory for each fieldbus device, including device identification data is mapped to at least one of the following to the OPC server directory, namely: link / segment ID, node ID, device ID and tag data PD.
8.权利要求1的方法,其中:映射步骤从FF目录中把用于每个现场总线设备的AP目录映射到OPC服务器目录中。 The method of claim 1, wherein: the mapping step from the FF directory AP Directory for each fieldbus device mapped to the OPC server directory.
9.权利要求1的方法,其中:映射步骤从FF目录中把FF对象映射到OPC服务器目录中。 9. The method of claim 1, wherein: the mapping step maps FF FF directory objects in the directory server to the OPC.
10.权利要求1的方法,其中:建造/更新步骤用从现场总线设备中读取的活动列表设备标识信息构造浏览树形结构。 10. The method of claim 1, wherein: the construction / updating step of reading from the active fieldbus devices in the list of device identification information configured browse tree structure.
11.权利要求1的方法,其中:复制步骤包括如下步骤:读取所述活动列表中工作的现场总线设备的AP目录和FF对象;把来自AP目录和FF对象的数据放入一个缓冲器中;和把来自缓冲器的数据复制到FF目录。 11. The method of claim 1, wherein: the step of copying comprises the steps of: reading the AP directories and FF objects fieldbus devices operating in the active list; data from the AP directories and FF objects loaded into a buffer ; and copying the data from the buffer to the FF directory.
CN 02821012 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using a live-list-based dynamic directory CN100338539C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US31409301P true 2001-08-23 2001-08-23

Publications (2)

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

Family

ID=23218519

Family Applications (2)

Application Number Title Priority Date Filing Date
CN 02821012 CN100338539C (en) 2001-08-23 2002-08-23 Foundation fieldbus server providing device information using a live-list-based dynamic directory
CN 200610094503 CN100470426C (en) 2001-08-23 2002-08-23 Foundation fieldbus server for providing device information using dynamic directory

Family Applications After (1)

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

Country Status (5)

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

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 (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
US8868732B2 (en) * 2011-05-31 2014-10-21 General Electric Company Systems and methods for facilitating communication with foundation fieldbus linking devices
US8937555B2 (en) * 2011-05-31 2015-01-20 General Electric Company Systems and methods to overlay behaviors on foundation fieldbus alerts
US8994545B2 (en) 2011-05-31 2015-03-31 General Electric Company Systems and methods for alert device removal
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)
DE102013218566A1 (en) * 2013-09-17 2015-03-19 Robert Bosch Gmbh Communication module for a field bus

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU1849397A (en) * 1996-02-06 1997-08-28 Fisher-Rosemount Systems, Inc. System and method for managing a transaction database of records of changes to field device configurations
US6094600A (en) 1996-02-06 2000-07-25 Fisher-Rosemount Systems, Inc. System and method for managing a transaction database of records of changes to field device configurations
US5805442A (en) 1996-05-30 1998-09-08 Control Technology Corporation Distributed interface architecture for programmable industrial control systems
ES2367247T3 (en) 1999-06-21 2011-10-31 Fieldbus Foundation System control blocks oriented high-speed Ethernet.

Also Published As

Publication number Publication date
DE02768655T1 (en) 2004-10-21
CN100470426C (en) 2009-03-18
EP1419420A1 (en) 2004-05-19
HK1074258A1 (en) 2008-08-08
CN1575443A (en) 2005-02-02
CN1924747A (en) 2007-03-07
WO2003019304A1 (en) 2003-03-06

Similar Documents

Publication Publication Date Title
CN1764877B (en) Method for launching applications
EP1580631B1 (en) Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming
JP6194252B2 (en) Process control system
CN1961288B (en) Methods and apparatus for accessing process control data
CN102323785B (en) Flexible Function Block
US8230443B2 (en) Supervisory process control and manufacturing information system application having a layered architecture
US6654759B1 (en) Method for access via various protocols to objects in a tree representing at least one system resource
US7840293B2 (en) Caching identifications and associated production database guids for expedited acquisition of linking information contained within multiple distinct production database tables
US20060224361A1 (en) Remotely monitoring/diagnosing distributed components of a supervisory process control and manufacturing information application from a central location
CN103279088B (en) Graphical programming language editing and reporting tools
JP5253277B2 (en) How to integrate a user-defined custom function block to process a control system incorporated in a process plant
US6266726B1 (en) Process control system using standard protocol control-of standard devices and non-standard devices
US7317952B2 (en) Managing field devices having different device description specifications in a process control system
US20020184360A1 (en) Methods and apparatus for managing devices without network attachments
US9483035B2 (en) Method for integrating at least one field device into a network of automation technology
US20150039112A1 (en) Supervisory process control and manufacturing information system application having an extensible component model
US20020156872A1 (en) Systems and methods for transmitting motion control data
EP1364259B1 (en) A method and apparatus for generating an application for an automation control system
EP0522590B1 (en) Communication device for factory automation network
US20050071209A1 (en) Binding a workflow engine to a data model
JP4908219B2 (en) Configurable plc and scada based control system, and method
US7003527B1 (en) Methods and apparatus for managing devices within storage area networks
US20070078956A1 (en) Embedding controllers and devices with data to facilitate up-to-date control and configuration information
EP1580630A2 (en) Controller with agent functionality
CA2332009C (en) System and methods for object-oriented control of diverse electromechanical systems using a computer network

Legal Events

Date Code Title Description
C06 Publication
C10 Entry into 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
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