EP2492765A2 - Extraktion einer FOUNDATION-Feldbusvorrichtunginformation zur verbesserten Vorrichtungsauswahl und Datenvalidierung - Google Patents

Extraktion einer FOUNDATION-Feldbusvorrichtunginformation zur verbesserten Vorrichtungsauswahl und Datenvalidierung Download PDF

Info

Publication number
EP2492765A2
EP2492765A2 EP12156539A EP12156539A EP2492765A2 EP 2492765 A2 EP2492765 A2 EP 2492765A2 EP 12156539 A EP12156539 A EP 12156539A EP 12156539 A EP12156539 A EP 12156539A EP 2492765 A2 EP2492765 A2 EP 2492765A2
Authority
EP
European Patent Office
Prior art keywords
file
extracting
data
live data
report
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.)
Withdrawn
Application number
EP12156539A
Other languages
English (en)
French (fr)
Other versions
EP2492765A3 (de
Inventor
Abhik Banerjee
Guruprasad Vishwanath Karkala
Raghavendra Rao Perampalli Nekkar
Kiran Kumar Somavarapu
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.)
General Electric Co
Original Assignee
General Electric Co
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 General Electric Co filed Critical General Electric Co
Publication of EP2492765A2 publication Critical patent/EP2492765A2/de
Publication of EP2492765A3 publication Critical patent/EP2492765A3/de
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32114—Part type selection, for simultaneous processing
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32144—Define device description using dd files

Definitions

  • the subject matter disclosed herein relates to industrial automation protocols and more particularly to systems and methods for parsing foundation fieldbus device description files for device selection and data validation.
  • Foundation fieldbus is a digital serial industrial automation protocol, two-way communication system that interconnects "field" equipment such as sensors and actuators.
  • Foundation fieldbus provides integration of high-speed controllers (having host systems software) (e.g., programmable logic controllers (PLC) and distributed control system (DCS) controllers), H1 device subsystems via a linking device, data servers and workstations.
  • An H1 device is any Intelligent Field device such as temperature transmitters, pressure transmitters, and different types of actuators, which communicate to the PLC or DCS controllers (via a linking device) through Foundation Fieldbus protocols.
  • a linking device is an interface module between the H1 device (e.g.: sensors, actuators etc) and PLC or DCS controllers.
  • the linking device performs various functions such as synchronizing communication between various H1 devices.
  • a device description (DD) file is a driver file used by the Host System to communicate with the H1 devices via the controllers (PLC or DCS) and linking device.
  • Each H1 device comes with different versions of DD files.
  • the DD files provide various information about the H1 Device that includes, but is not limited to, the different types of blocks and their quantity, initial values and supported ranges for different parameters of the blocks menus, methods and visualization elements, block instantiation details and capability levels of the H1 device.
  • Blocks are software that defines functionality, features and behaviors of the H1 device. Host system software reads this information from DD files provided by manufacturer for communicating with the H1 devices.
  • DD files are typically in a binary format, from which H1 device functionality and block data can be extracted.
  • a method for extracting and reporting a foundation fieldbus device description file for device selection and data validation can include obtaining the DD file for an intelligent field device (H1 device), extracting device information from the DD file, reading live data generated by the H1 device and generating a report including compliant values and functionality of the H1 device.
  • H1 device intelligent field device
  • a computer program product extracting and reporting a foundation fieldbus device description (DD) file for device selection and data validation.
  • the computer program product can include a computer readable medium having instructions for causing a computer to implement a method, the method including obtaining the DD file for an intelligent field device (H1 device), extracting device information from the DD file, reading live data generated by the H1 device and generating a report including compliant values and functionality of the H1 device.
  • H1 device intelligent field device
  • a system for extracting and reporting a foundation fieldbus device description file for device selection and data validation can include a processor configured to obtain the DD file for an intelligent field device (H1 device), extract supported and unsupported functionality of the H1 device, extract supported blocks and function parameters of the supported blocks, read live data generated by the H1 device, export the live data to an export file, generate a report including compliant values and functionality of the H1 device and compare the compliant values from the report and the live data from the export file.
  • H1 device intelligent field device
  • FIG. 1 illustrates a high level block diagram of an example system 100 for extracting device information from foundation fieldbus DD files for device selection and data validation.
  • the system 100 can include a controller 105 and Workstations.
  • the controller 105 is coupled to a linking device 110 that provides an interface between the controller 105 and an H1 device 115.
  • the controller 105 can be any control hardware such as PLC and DCS controllers.
  • the controller 105 can also be any suitable hardware controller.
  • a tool in the host system 106 e.g., via a workstation 109) is implemented to configure and develop application logic that is downloaded to the controller 105.
  • the host system 106 supports foundation fieldbus technology and implements an example tool 107 to generate a comprehensive report 108 to display all the foundation fieldbus features of the H1 device 115 by extracting device information from the DD file 116 and comparing the DD file values with the values of the device displayed in the host system.
  • the DD file 116 is provided by the device manufacturer and has a series of information in a binary format which is processed by host system 106 in order to monitor and control the H1 device 115.
  • the DD file 116 includes blocks (their types and quantity), initial values/actual values for various parameters in the blocks, their supported range, supported DD menus and methods, block Instantiation details and capability levels, and other information related to fieldbus devices as known in the art.
  • the host system 106 reads this information from DD files 106 provided by manufacturer for communicating with the H1 device 115.
  • the tool 107 can be an integral part of the host system 106 and generates the comprehensive report 108 show to the user various specific features of the system 100 including but not limited to: the link master (via the linking device 110), multiple capability levels, block instantiation, transducer blocks, standard blocks, custom blocks, profile custom function blocks, conditionals, methods, menus, visualizations, and multi-bit alerts.
  • This information can further be compared against the extracted DD file 116 report giving the exact comparison between different H1 devices (e.g., the H1 device 115) and the host system 106.
  • the report 108 can be embedded in the host system 106, which the user can use to make a comparative study of the various devices that can be procured and also have an idea of the various foundation fieldbus features that the device can support.
  • the comprehensive report 108 includes various features that each fieldbus device (e.g., the H1 device 115) supports and the compatibility with the host system 106.
  • the report 108 aids the user in procuring an improved fieldbus set up.
  • data actually collected and processed from the DD file 116 in the H1 device 115 in the field can be compared to data that the host system 106 displays.
  • the H1 device 115 is qualified in the field, the H1 device 115 has to be compliant with the host system 106, the user depends on the value that is being displayed in the host system 106 and uses the data being displayed to control and monitor the H1 device 115.
  • data in the DD file 116 is accessible, currently it must be manually parsed to extract the data.
  • the systems and methods described herein provide the end user with the comprehensive report 108 about the various features that the different measurement device supports and their compatibility with the host system, this will help them in procuring an improved fieldbus set up.
  • the systems and methods described herein automatically extract the data and compare the data to actual measured values from the H1 device 115.
  • the tool 107 extracts the configuration information available in DD file 116 and information that is required for the validation and device qualification of the H1 device 115 is extracted using the tool 107 to be stored in a valid format in a specified location on the host system 106.
  • the comprehensive report 108 also aids the device tool 107 that helps during the device qualification and validation by directly reading the data from the DD file 116 then comparing actual values being displayed in the host system 106.
  • the validation of the host system 106 with respect to each of the supported field devices e.g., the H1 device 115
  • the validation of the data which the H1 device 115 is currently processing is done only by viewing the values that were displayed in the host system 116 and compared against the device manual or the standard document.
  • the tool 107 provides an option to the end user to view the value of various function parameters of the H1 device that are to be compared as against the host values measured from the H1 device 115.
  • a user can select the specific features that the user wants to use to compare the values between the DD file 116 value and the host system 106 values.
  • the controller 105 can be any suitable hardware for controlling the system 100.
  • FIG. 2 illustrates a system 200 for extracting device information from foundation fieldbus DD files for device selection and data validation, illustrating a generalized example controller.
  • the methods described herein can be implemented in software (e.g., firmware), hardware, or a combination thereof.
  • the methods described herein are implemented in software, as an executable program, and is executed by a special or general-purpose digital computer, such as a personal computer, workstation, minicomputer, or mainframe computer.
  • the system 200 therefore includes general-purpose computer 201.
  • the computer 201 includes a processor 205, memory 210 coupled to a memory controller 215, and one or more input and/or output (I/O) devices 240, 245 (or peripherals) that are communicatively coupled via a local input/output controller 235.
  • the input/output controller 235 can be, but is not limited to, one or more buses or other wired or wireless connections, as is known in the art.
  • the input/output controller 235 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications.
  • the local interface may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
  • the processor 205 is a hardware device for executing software, particularly that stored in memory 210.
  • the processor 205 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computer 201, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions.
  • CPU central processing unit
  • auxiliary processor among several processors associated with the computer 201
  • semiconductor based microprocessor in the form of a microchip or chip set
  • macroprocessor or generally any device for executing software instructions.
  • the memory 210 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), disk, diskette, cartridge, cassette or the like, etc.).
  • RAM random access memory
  • EPROM erasable programmable read only memory
  • EEPROM electronically erasable programmable read only memory
  • PROM programmable read only memory
  • tape compact disc read only memory
  • CD-ROM compact disc read only memory
  • disk diskette
  • cassette or the like etc.
  • the memory 210 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory 210 can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the processor
  • the software in memory 210 may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions.
  • the software in the memory 210 includes the extracting methods (including the tool 107 and report 108 from FIG. 1 ) described herein in accordance with example embodiments and a suitable operating system (OS) 211.
  • the OS 211 essentially controls the execution of other computer programs, such the extracting systems and methods as described herein, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.
  • the extracting methods described herein may be in the form of a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed.
  • a source program then the program needs to be translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory 210, so as to operate properly in connection with the OS 211.
  • the extracting methods can be written as an object oriented programming language, which has classes of data and methods, or a procedure programming language, which has routines, subroutines, and/or functions.
  • a conventional keyboard 250 and mouse 255 can be coupled to the input/output controller 235.
  • Other output devices such as the I/O devices 240, 245 may include input devices, for example but not limited to a printer, a scanner, microphone, and the like.
  • the I/O devices 240, 245 may further include devices that communicate both inputs and outputs, for instance but not limited to, a network interface card (NIC) or modulator/demodulator (for accessing other files, devices, systems, or a network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, and the like.
  • the I/O devices can include the linking device 110 and the H1 device 115 from FIG. 1 .
  • the system 200 can further include a display controller 225 coupled to a display 230.
  • the system 200 can further include a network interface 260 for coupling to a network 265.
  • the network 265 can be an IP-based network for communication between the computer 201 and any external server, client and the like via a broadband connection.
  • the network 265 transmits and receives data between the computer 201 and external systems.
  • network 265 can be a managed IP network administered by a service provider.
  • the network 265 may be implemented in a wireless fashion, e.g., using wireless protocols and technologies, such as WiFi, WiMax, etc.
  • the network 265 can also be a packet-switched network such as a local area network, wide area network, metropolitan area network, Internet network, or other similar type of network environment.
  • the network 265 may be a fixed wireless network, a wireless local area network (LAN), a wireless wide area network (WAN) a personal area network (PAN), a virtual private network (VPN), intranet or other suitable network system and includes equipment for receiving and transmitting signals.
  • LAN wireless local area network
  • WAN wireless wide area network
  • PAN personal area network
  • VPN virtual private network
  • the software in the memory 210 may further include a basic input output system (BIOS) (omitted for simplicity).
  • BIOS is a set of essential software routines that initialize and test hardware at startup, start the OS 211, and support the transfer of data among the hardware devices.
  • the BIOS is stored in ROM so that the BIOS can be executed when the computer 201 is activated.
  • the processor 205 When the computer 201 is in operation, the processor 205 is configured to execute software stored within the memory 210, to communicate data to and from the memory 210, and to generally control operations of the computer 201 pursuant to the software.
  • the extracting methods described herein and the OS 211 are read by the processor 205, perhaps buffered within the processor 205, and then executed.
  • the methods can be stored on any computer readable medium, such as storage 220, for use by or in connection with any computer related system or method.
  • aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • the extracting methods described herein can implemented with any or a combination of the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • a user can collect various DD files and load them onto the respective controller (e.g., the controller 105).
  • the user can also install the host system 106 on the controller to plan the foundation fieldbus devices that need to be procured (e.g., the H1 device 115).
  • the host system 106 can read the DD file 116.
  • Information regarding various features that are supported by the corresponding H1 device 115 is extracted.
  • the extracted information is then consolidated in a form of the understandable report 108 (as compared with extracted binary data that is currently available), which displays the set of supported/not supported features.
  • the end user views the report 108 to decide on if the H1 device 115 suffices any predetermined requirements.
  • a validation team or device qualification team can also use the same report 108 to validate the host system 106 and qualify a device to be used by the user.
  • FIG. 3 illustrates a flow chart of a method 300 for extracting device information from foundation fieldbus DD files for device selection and data validation in accordance with example embodiments.
  • the host system 106 obtained the DD file 116 for the H1 device 115.
  • DD files such as DD file 115 include several versions and include various sub-files including, but not limited to .ffo, .sys, .cff, .sy5 and ff5 files.
  • the host system 106 extracts the binary DD file 116.
  • the host system 106 extracts device information from the file via the extracting tool 107 and extracts the functionality and blocks supported by the H1 device 115.
  • the host system 106 identifies the functionality supported by the H1 device 115.
  • the types of functionality that the H1 device 115 can support can include but is not limited to: menus and methods, block instantiation, capability level, conditions, visualization (i.e., charts and graphs), enhanced function blocks, profiled custom block, custom blocks, multi-bit alerts and link master (via the linking device 110).
  • the host system 106 identifies the blocks that the H1 device 115 supports.
  • the host system 106 further identifies the block functionality supported by the blocks identified at block 320. Function parameters of each of the supported block can include but is not limited to initial values of each function parameter and a valid range of each function parameter.
  • the host system 106 further reads and displays live values from the H1 device 115.
  • the host system can export to live data into a file, such as an XML file.
  • a validation team or a host qualification team can export the live data via the host system 106.
  • the host system 106 can further generate the report 108 at block 340.
  • the report can include supported and unsupported functionally identified at block 315.
  • the report 108 can further include the block functionality identified at blocks 320, 325.
  • FIG. 4 illustrates an example of a report format 400 that can be generated at block 340.
  • a user can refer to the generated report 108 to improve the fieldbus devices (e.g., H1 device 115) and is fully informed of the various features that the manufacturer of the devices offers.
  • the generated report 108 and the data in the exported file at block 335 are compared.
  • the host system 106 is compliant with the H1 device 115, which can then be qualified. If the report 108 and the live data fail comparison at block 350, then at block 360 the host system 106 is not compliant with the H1 device 115, which is not qualified. The user can then make whatever adjustments to the host system 106 and the H1 device 115 as necessary to achieve compliance.
  • Technical effects include but are not limited to giving an end user a concise report of all foundation fieldbus features that corresponding DD files of the measurement device supports.
  • the report enables a user to choose an efficient combination of devices by knowing the functionality and compatibility of various devices with the host system.
  • the user can compare selection of various combinations and choose affordable combinations that meet all requirements of a given system.
  • the host system can play a facilitating role to the end user in the foundation fieldbus device selection and planning process.
  • the systems and methods described herein can also aid validation and device qualification teams to be more stringent during the validation and devices qualification phases that make the host system more robust against the qualified devices.
  • the device that is qualified by the host system is compliant with the host and the fieldbus standard. The user can then use the device with the compliant host and rely on the data for the control and monitor of the device.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Stored Programmes (AREA)
  • Programmable Controllers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Alarm Systems (AREA)
EP12156539.4A 2011-02-24 2012-02-22 Extraktion einer FOUNDATION-Feldbusvorrichtunginformation zur verbesserten Vorrichtungsauswahl und Datenvalidierung Withdrawn EP2492765A3 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/033,838 US20120221126A1 (en) 2011-02-24 2011-02-24 Extraction of a foundation fieldbus device information for enhanced device selection and data validation

Publications (2)

Publication Number Publication Date
EP2492765A2 true EP2492765A2 (de) 2012-08-29
EP2492765A3 EP2492765A3 (de) 2014-12-31

Family

ID=45656440

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12156539.4A Withdrawn EP2492765A3 (de) 2011-02-24 2012-02-22 Extraktion einer FOUNDATION-Feldbusvorrichtunginformation zur verbesserten Vorrichtungsauswahl und Datenvalidierung

Country Status (4)

Country Link
US (1) US20120221126A1 (de)
EP (1) EP2492765A3 (de)
JP (1) JP2012185817A (de)
CN (1) CN102650877A (de)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120239168A1 (en) * 2011-03-16 2012-09-20 General Electric Company Virtual communication relationship information extraction, availability determination and validation from foundation fieldbus device description files
DE102012102516A1 (de) * 2012-03-23 2013-09-26 Endress + Hauser Gmbh + Co. Kg Verfahren zum Bedienen eines Feldgerätes
US10812967B2 (en) * 2018-03-29 2020-10-20 Honeywell International Inc. Wireless field devices having embedded device description data

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5974391A (en) * 1994-07-12 1999-10-26 Fujitsu Limited Device and method for project management
JP3690289B2 (ja) * 2001-02-19 2005-08-31 ティアック株式会社 光ディスク装置
US7062718B2 (en) * 2001-08-14 2006-06-13 National Instruments Corporation Configuration diagram which graphically displays program relationship
US7013232B2 (en) * 2001-08-15 2006-03-14 National Insurance Corporation Network-based system for configuring a measurement system using configuration information generated based on a user specification
DE10147706A1 (de) * 2001-09-27 2003-04-10 Endress & Hauser Gmbh & Co Kg Verfahren zum Bedienen eines Feldgerätes
US7054695B2 (en) * 2003-05-15 2006-05-30 Fisher-Rosemount Systems, Inc. Field maintenance tool with enhanced scripts
CN100549884C (zh) * 2003-12-04 2009-10-14 霍尼韦尔国际公司 用于在控制系统和多个受控设备之间传送设备描述的系统和方法
US8464168B2 (en) * 2005-10-05 2013-06-11 Invensys Systems, Inc. Device home page for use in a device type manager providing graphical user interfaces for viewing and specifying field device parameters
US8527888B2 (en) * 2006-04-11 2013-09-03 Invensys Systems, Inc. Method and supporting configuration user interfaces for streamlining installing replacement field devices
US8799793B2 (en) * 2005-10-05 2014-08-05 Invensys Systems, Inc. Tool for creating customized user interface definitions for a generic utility supporting on-demand creation of field device editor graphical user interfaces
US20070078540A1 (en) * 2005-10-05 2007-04-05 Invensys Systems, Inc. Utility for comparing deployed and archived parameter value sets within a field device editor
US8782539B2 (en) * 2005-10-05 2014-07-15 Invensys Systems, Inc. Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters
DE102005063162A1 (de) * 2005-12-30 2007-10-31 Codewrights Gmbh Verfahren zum Testen von Gerätebeschreibungen für Feldgeräte der Automatisierungstechnik
CN100454854C (zh) * 2007-02-16 2009-01-21 北京航空航天大学 分布式网络化即插即用测控系统
US8660108B2 (en) * 2007-04-13 2014-02-25 Hart Communication Foundation Synchronizing timeslots in a wireless communication protocol
JP5024624B2 (ja) * 2008-02-26 2012-09-12 横河電機株式会社 フィールド機器管理装置、フィールド機器管理システム、フィールド機器管理方法、コンピュータプログラム、記録媒体
US8914783B2 (en) * 2008-11-25 2014-12-16 Fisher-Rosemount Systems, Inc. Software deployment manager integration within a process control system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Also Published As

Publication number Publication date
CN102650877A (zh) 2012-08-29
JP2012185817A (ja) 2012-09-27
US20120221126A1 (en) 2012-08-30
EP2492765A3 (de) 2014-12-31

Similar Documents

Publication Publication Date Title
JP6879961B2 (ja) プロセスデータを表示するための方法および装置、及び機械アクセス可能媒体
US11435728B2 (en) I/O virtualization for commissioning
JP7298976B2 (ja) プロセス制御システム内のデバイスと通信するための方法、有形の製品、及びプロセス制御システム内のフィールドデバイスと通信するための装置
US10663956B2 (en) Configuration in process plant using I/O-abstracted field device configurations
US9398097B2 (en) Method for servicing a field device
WO2017031033A1 (en) Augmented reality-based wiring, commissioning and monitoring of controllers
JP6624008B2 (ja) エンジニアリングツール連携装置、エンジニアリングツール連携方法、エンジニアリングツール連携プログラム及び記録媒体
JP5895906B2 (ja) プロセス制御装置及びシステム並びにその健全性判定方法
US9733628B2 (en) System and method for advanced process control
WO2016025223A1 (en) Cloud computing system and method for advanced process control
EP2813909B1 (de) Bedarfsabhängige Vorrichtungsvorlagen zur Integration von Vorrichtungen in eine Verarbeitungsanlage
US20190025807A1 (en) Device information providing apparatus, device information providing method, and storage medium
EP2492765A2 (de) Extraktion einer FOUNDATION-Feldbusvorrichtunginformation zur verbesserten Vorrichtungsauswahl und Datenvalidierung
JP5293061B2 (ja) 機器管理プログラム及び機器管理システム
JP6176341B2 (ja) プロセス制御装置及びシステム並びにその健全性判定方法
JP2006318102A (ja) フィールド機器管理装置およびフィールド機器管理方法
KR20140122414A (ko) 검증 프로세스 관리 시스템 및 방법
WO2019198221A1 (ja) データ処理装置、データ処理方法及びプログラム
US9336181B2 (en) Retrieval of measured values, diagnostic information or device parameters
US20120239168A1 (en) Virtual communication relationship information extraction, availability determination and validation from foundation fieldbus device description files
US10401803B2 (en) Apparatus and method for computer code adjustments in an industrial machine
US20090150196A1 (en) Systems, methods and computer program products for business transformation of business performance indicators
WO2014080491A1 (ja) プログラマブル表示器

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: G05B 19/042 20060101AFI20141127BHEP

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20150701