EP1612630B1 - Erweiterbares Datentransformationssystem - Google Patents

Erweiterbares Datentransformationssystem Download PDF

Info

Publication number
EP1612630B1
EP1612630B1 EP05013987.2A EP05013987A EP1612630B1 EP 1612630 B1 EP1612630 B1 EP 1612630B1 EP 05013987 A EP05013987 A EP 05013987A EP 1612630 B1 EP1612630 B1 EP 1612630B1
Authority
EP
European Patent Office
Prior art keywords
data
protocol
automation
transformation component
target
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.)
Active
Application number
EP05013987.2A
Other languages
English (en)
French (fr)
Other versions
EP1612630A1 (de
Inventor
David M. Callaghan
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.)
Rockwell Automation Technologies Inc
Original Assignee
Rockwell Automation Technologies Inc
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 Rockwell Automation Technologies Inc filed Critical Rockwell Automation Technologies Inc
Publication of EP1612630A1 publication Critical patent/EP1612630A1/de
Application granted granted Critical
Publication of EP1612630B1 publication Critical patent/EP1612630B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • G05B19/0423—Input/output
    • 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/20—Pc systems
    • G05B2219/23—Pc programming
    • G05B2219/23014—Conversion of ASCII scripting language to machine code
    • 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/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25204—Translate between different communication protocols
    • 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/32142—Define device, module description using xml format file

Definitions

  • the present invention relates generally to industrial control systems, and more particularly toward transformation of industrial device data format or protocol to facilitate device interoperability.
  • Industrial controllers are special-purpose computers utilized for controlling industrial processes, manufacturing equipment, and other factory automation, such as data collection or networked systems.
  • the industrial controller having an associated processor (or processors), measures one or more process variables or inputs reflecting the status of a controlled system, and changes outputs effecting control of such system.
  • the inputs and outputs may be binary, ( e.g. , on or off), as well as analog inputs and outputs assuming a continuous range of values.
  • I/O input/output
  • I/O modules serve as an electrical interface to the controller and may be located proximate or remote from the controller including remote network interfaces to associated systems.
  • Inputs and outputs may be recorded in an I/O table in processor memory, wherein input values may be asynchronously read from one or more input modules and output values written to the I/O table for subsequent communication to the control system by specialized communications circuitry (e.g. , back plane interface, communications module).
  • Output modules may interface directly with one or more control elements, by receiving an output from the I/O table to control a device such as a motor, valve, solenoid, amplifier, and the like.
  • a logic processor such as a Programmable Logic Controller (PLC) or PC-based controller.
  • PLC Programmable Logic Controller
  • Programmable Logic Controllers are programmed by systems designers to operate manufacturing processes via user-designed logic programs or user programs.
  • the user programs are stored in memory and generally executed by the PLC in a sequential manner although instruction jumping, looping and interrupt routines, for example, are also common.
  • Associated with the user program are a plurality of memory elements or variables that provide dynamics to PLC operations and programs. These variables can be user-defined and can be defined as bits, bytes, words, integers, floating point numbers, timers, counters and/or other data types to name but a few examples.
  • Document DE 101 38 533 A1 relates to the conversion of project data and/or project planning data of an automation project into a standardized metadata language, particularly XML. Conversion of proprietary format into an XML format allows the data to be read, processed, etc. by disparate computer programs associated with the project.
  • Document WO 03/105 194 A1 is concerned with an integrated manufacturing system (eCenter) which allows collection, propagation, storage, distribution, and transformation of data to different parties associated with the eCenter.
  • the eCenter acts as an intermediary between tools located at a fabricator (FAB) and the original equipment manufacturer (OEM), where the OEM is located remotely to the FAB.
  • FAB fabricator
  • OEM original equipment manufacturer
  • the eCenter generates proprietary data from the tool allowing for e-diagnostics of the tool by the FAB and the OEM.
  • the data con be formatted in the form of XML to allow the data to be analyzed by disparate computer systems associated with the eCenter.
  • Document DE 102 51 502 A1 relates to a process control/process monitoring system where distance over which field devices can be connected is limited by such factors as data transmission distance, data transmission rates, operating environment, etc.
  • a plurality of disparate field buses may be used to connect a variety of field devices across the system and a gateway device can be employed to connect the disparate buses together.
  • the use of a field device (sensor) is disclosed in this document that incorporates two communications interfaces facilitating conversion of data from one field bus communication protocol to another.
  • Document US 2003/014500 discloses a transactional data communications system and method which communicates information within an enterprise having a process control system and a plurality of information technology systems that are communicatively coupled to the process control system via a web services interface and a transactional information server.
  • the system and method generates transactional process control information and formats the transactional process control information based on an extensible markup language input schema to form formatted transactional process control information.
  • the system and method sends the formatted transactional process control information to the transactional information server via the web services interface and maps the formatted transactional process control information to an extensible markup language output schema associated with one of the plurality of information technology systems to form mapped transactional process control information.
  • the system and method then sends the mapped transactional process control information to the one of the plurality of information technology systems.
  • a transformation gateway component can be employed.
  • the transformation gateway component can be utilized as part of a separate service or device to provide a common interface for industrial control device communication.
  • the transformation gateway can provide core data protocol transformations, for instance from type A to type B.
  • the transformation gateway component can employ text based scripts that perform the transformation utilizing web based technologies such as XML (eXtensible Mark-up Language), XSL (eXtensible Stylesheet Language) and XSLT (eXtensible Stylesheet Language Transformation) as well as respective execution subsystems (e.g ., XSLT processor).
  • XML eXtensible Mark-up Language
  • XSL eXtensible Stylesheet Language
  • XSLT eXtensible Stylesheet Language Transformation
  • respective execution subsystems e.g ., XSLT processor
  • the transformation gateway component can be employed as a network service.
  • the communication transformation can be scaled to meet requirements of a myriad of devices needing such a service.
  • the transformation component can be employed on a separate device rather than as a network service.
  • the device can then be employed to map data between different automation device vendors so that each device can utilize and understand the meaning of data values in their own respective local data formats.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a server and the server can be a component.
  • One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
  • the present invention may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof.
  • article of manufacture (or alternatively, "computer program product”) as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.
  • computer readable media can include but is not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips%), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)...), smart cards, and flash memory devices (e.g., card, stick).
  • System 100 includes a transformation gateway component 110 and two automation devices 120 and 130.
  • Transformation gateway component 110 (also referred to herein as simply transformation component 110) facilitates communication between automation device 120 (e.g., source device) and automation device 130 (e.g., target device).
  • Automation devices 120 and 130 can include any one of a plurality of industrial processes and machines.
  • an automation device can be a programmable logic controller (PLC) or an industrial machine under control of the PLC.
  • PLC programmable logic controller
  • Industrial machines can include but are not limited to pumps providing fluid transport, fans, conveyor systems, compressors, gearboxes, motion control and detection devices, sensors, screw pumps, and mixers, as well as hydraulic and pneumatic machines driven by motors.
  • motors can be combined with other components, such as valves, pumps, furnaces, heaters, chillers, conveyor rollers, fans, compressors, gearboxes, and the like, as well as with appropriate motor drives to form industrial machines and actuators.
  • an electric motor could be combined with a motor drive providing variable electrical power to the motor, as well as with a pump, whereby the motor rotates the pump shaft to create a controllable pumping system.
  • Transformation component 110 aids communication and interaction amongst automation devices 120 and 130 that utilize differing data protocols.
  • Automation devices can contain an internal or local data format to efficiently process data in accordance with their primary function. In most instances, different device vendors or manufacturers utilize a proprietary data format, which prohibits easy interaction and interoperability of devices across manufacturers. Moreover, even automation devices made by a single manufacturer or provided by a single vendor can often have differing data protocols.
  • Transformation component 110 facilitates translating between multiple protocols to enable a multitude of automation devices to easily interact without forcing production and storage of customized executable code for each different protocol. Rather than forcing each automation device to house translating code for a myriad of disparate data protocols, the transformation component 110 can act as an intermediary between automation devices 120 and 130, for example.
  • the transformation component 110 translates or transforms the data to a target protocol and then transmits the newly formatted data to device 130.
  • the transformation component 110 can simply transform data to an intermediate format that can be accessed and utilized by a plurality of automation devices.
  • Fig. 2 illustrates a transformation component 110 in accordance with an aspect of the present invention.
  • transformation component 110 can include a receiver component 210, a translating component 220, and an output component 230.
  • Receiver component 210 receives or retrieves communication data from an automation device and determines the target device and associated protocol. The receiver component then passes the message and any calculated or determined data to the translating component 220.
  • Translating component utilizes such information to produce communications in accordance with the protocol employed by one or more target devices.
  • Such translation can comprise a simple one-to-one protocol mapping and/or other modifications or data transformations (e.g., scaling values, adding signed bit, language translations).
  • the translated communication can subsequently be passed to the output component 220, which transmits the data to the target device(s) or alternatively makes such data available to be retrieved.
  • automation device communications or data can be marked-up or schematized to aid in translation.
  • metadata can be associated with data to describe information format and relations (e.g ., hierarchical structure).
  • the transformation component 110 can then utilize the provided metadata to facilitate data translation.
  • the translated data or communication can be produced utilizing markups associated with the target device.
  • ASCII text scripts can be employed by the transformation component 110 to perform translation.
  • text scripts can utilize the schematized source data and translation information to translate data to a particular format or protocol employed by one or more target devices.
  • XML extensible Markup Language
  • XSL extensible Stylesheet Language
  • XSLT eXtensible Stylesheet Language Transform
  • a device's data can be schematized with an appropriate markup.
  • Translation information specifying a particular protocol can be retrieved or provided in an XSL stylesheet.
  • the XSL stylesheet can be specified and written as a general set of rules that map an input domain to an expected output domain.
  • XSLT can perform language transformations utilizing an XSLT processor, for example.
  • the transformation gateway component 110 can utilize XML, XSL, and XSLT to transform from one protocol to another. It should also be noted that the transformation component 110 can enable two disparate control platforms to communicate using relative or local data tags.
  • an automation device can present a message or communication to the transformation gateway component 110 that is to be distributed to many other devices. Additionally or alternatively, many automation devices can utilize the transformation gateway component 110 to aggregate and/or report out information to a single device.
  • Fig. 3 depicts a data transformation system 300 in accordance with an aspect of the subject invention.
  • Transformation system 300 comprises a plurality of automation devices 310 (AUTOMATION DEVICE 1 through AUTOMATION DEVICE N , where N is an integer greater than or equal to one), network 320, and transformation component 110.
  • One or more automation devices 310 can seek to communicate or otherwise read data from one or more other automation devices. As discussed supra , problems can prevent such communications when automation devices 310 utilize different data protocols. To solve these communications problems transformation component 110 can be employed.
  • Transformation component 110 can receive data from a first device formatted according to a first protocol and translate the information into a common middle protocol (e.g., an XML document) which can be provided/made available and understood by other devices employing various disparate data protocols.
  • transformation component 110 can be employed as a network service accessible by a plurality of automation devices 310.
  • data to be communicated to at least one other automation device can be transmitted via a communications link to a network 320 and then to transformation component 110 which can translate the data and make it accessible to one or more target automation devices 310.
  • the target automation devices 310 can then utilize such data as if it was received/retrieved from a device using the same data format or protocol.
  • Fig. 4 illustrates a data transformation system 400.
  • a middle or intermediate format or protocol can be employed to facilitate data transformation.
  • Transformation component 110 receives source data 410 from an automation device.
  • This source data can be schematized or marked up to describe the structure and nature of particular data.
  • the source data can be an XML document.
  • the transformation component can then generate the middle or intermediate protocol data 420, which can also be an XML document.
  • Processor component 430 can receive or retrieve the middle protocol data 420 and translate such data into a target protocol 440 associated with a particular automation device(s).
  • the processor component 430 can be an XSLT processor that can translate the middle protocol XML document to the format used by the target or receiving device(s).
  • the processor component 430 can be an XSLT processor that can translate the middle protocol XML document to the format used by the target or receiving device(s).
  • middle protocol data 420 there are actually two translations one from source data 410 to middle protocol data 420 and another from middle protocol data 420 to target protocol 440.
  • both translations could be executed by transformation component 110.
  • some devices could employ the middle protocol internally thereby relieving the need for two translations.
  • network 320 encompasses communication networks such as local area networks (LANs), metropolitan area networks (MANs), or wide area networks (WANs).
  • LANs are peer-to-peer networks that are optimized for moderated size geographic area which enable communications between networked devices via a single physical medium.
  • LANs are normally owned and used by a single individual or organization.
  • MANs are networks that are optimized for geographical areas larger than those covered by a LAN but smaller than those covered by a WAN.
  • a MAN provides a means of communications ranging from several blocks ( e . g . a university campus) to an entire city.
  • MANs may be owned and operated by a single individual or organization, but are generally utilized by many different individuals and organizations.
  • WANs are communication networks that span a large geographic area (e.g., nationwide, worldwide) and generally consist of the several interconnected LANs and MANs.
  • the largest known WAN known today is the Internet.
  • LAN technologies include Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet/IEEE 1102.3, Token Ring/IEEE 1102.5, physical connection topologies such as bus, tree, ring, and star, and the like.
  • WAN technologies include, but are not limited to, point-to-point links, circuit-switching networks like Integrated Services Digital Networks (ISDN) and variations thereon, packet switching networks, T1 networks, and Digital Subscriber Lines (DSL).
  • ISDN Integrated Services Digital Networks
  • DSL Digital Subscriber Lines
  • the communication links between the automation devices 310 and the network 320 can be either wired, wireless or any combination thereof.
  • the devices 310 and network 320 can be connected via twisted pair, coaxial cable, optical fiber, or power lines.
  • devices 310 can communicate with network 320 utilizing IEEE 802.11a or IEEE 802.11b standards, Bluetooth technology, and satellite, for example.
  • Fig. 5 illustrates another data transformation system 500 in accordance with an aspect of the present invention.
  • the transformation component 110 can be embodied in a network service (as described previously) it can also be part of a separate gateway apparatus.
  • System 500 depicts an exemplary implementation of a transformation component embodied within a gateway apparatus.
  • System 500 comprises transformation gateway component 110, two automation devices 120 and 130, as well as a network 320, and a protocol database 510.
  • automation device 120 and automation device 130 desire to exchange information, but operate using distinct data protocols.
  • transformation component 110 is employed to facilitate translation there between. Transformation component 110 receives or retrieves data from device 120. In accordance with an aspect of the invention, it can be an XML document.
  • data transmission is not limited to the XML format.
  • the transmission can include any type of binary data.
  • an XML document is employed, however, the document can then be converted to proper format and order for the target device 130.
  • an extensible stylesheet language transformation can be applied to translate a source XML document into a target document.
  • a stylesheet can be applied to a source XML document to produce the target.
  • a stylesheet describes the format of the target device. If the transformation component does not have the stylesheet for a particular communication protocol, it can be retrieved from a protocol database 510 via network 320.
  • Protocol database 320 contains stylesheets or other formatting files or information.
  • the network 320 can be a LAN, MAN, or WAN.
  • Connection to the network 320 can be either via wire (e.g ., twisted pair, coaxial cable, optical fiber, power line) or wirelessly (e.g ., using IEEE 802.11a and/or IEEE 802.11b standards, Bluetooth technology, satellite).
  • wire e.g ., twisted pair, coaxial cable, optical fiber, power line
  • wirelessly e.g ., using IEEE 802.11a and/or IEEE 802.11b standards, Bluetooth technology, satellite.
  • transformation gateway component can be integrated into automation devices themselves.
  • the devices could download formatting information and execute the translation to an alternative protocol without aid from another apparatus or service.
  • a data transformation methodology 600 is illustrated in accordance with an aspect of the present invention.
  • data is received or retrieved from an automation device.
  • the data can be schematized or marked-up with metadata to describe, among other things, relationships between data.
  • the device data can be specified as an XML document.
  • the received data is translated into an alternate format. Translation can consist of applying a format or template associated with the protocol of a target device. For instance, a stylesheet associated with a target device can be applied by an XSLT processor to produce appropriately formatted and structured data.
  • the translated or formatted data can be transferred or outputted to a second target device.
  • Fig. 7 illustrates a method of transformation data 700 in accordance with an aspect of the subject invention.
  • data is received or retrieved from a first source automation device.
  • the data can be formatted as an XML document, for example.
  • the target device and associated communication protocol is determined.
  • a determination is made as to whether translation information is stored locally.
  • Translation information specifies the format of the output to a second target device.
  • such translation information can be embodied in an XSL stylesheet. If the information is not local, then at 740 it can be downloaded, for instance, from a network database located proximate or remote from the source and target automation devices. Thereafter, the method can proceed at 760.
  • translation information is local, then it is simply retrieved at 750.
  • the translation information is applied to the received data to translate the data into a format in accordance with the target device's communication protocol. For instance, an XSLT processor can be employed to generate an appropriate document from the source XML document and the stylesheet.
  • the translated data is transferred or retrieved by one or more target automation devices for further processing.
  • Fig. 8 depicts yet another data transformation methodology in accordance with an aspect of the subject invention.
  • source data is received from a first automation device.
  • the source data can be schematized and formatted as an XML document.
  • the source data is then translated or transformed into a middle or intermediate data protocol at 820.
  • This middle data format or protocol is then provided to one or more target devices at 830. For example, such data can be made available for download over a network connection.
  • the middle data protocol is translated into the target format or protocol utilized by a particular device. For example, a device needing to access data provide by a first automation device can access the data provided in an intermediate format and then translate that to the particular format utilized by such a device for use and/or manipulation.
  • the invention discloses a system and method of facilitating communication and interaction amongst automation devices that employ disparate data protocols.
  • an extensible transformation gateway component is employed to provide translations and also act as a middle protocol amongst a plurality of automation devices.
  • the transformation component can be integrated into gateway device or apparatus, the transformation component can also be employed as a network service thereby increasing the scalability of the system.

Claims (25)

  1. Verfahren für einen Informationsaustausch in einem Automatisierungssystem mit einer Vielzahl von Automatisierungsgeräten (310), wobei die Vielzahl der Automatisierungsgeräte unterschiedliche Datenprotokolle verwenden, mit den Schritten:
    Empfangen (810) von Quelldaten (410) an einer Transformationskomponente (110) von einem ersten Automatisierungsgerät (120) der Vielzahl der Automatisierungsgeräte in Übereinstimmung mit einem Quelldatenprotokoll, das mit dem ersten Automatisierungsgerät verknüpft ist;
    Übersetzen (820) der Quelldaten in ein intermediäres Datenprotokoll (420) an der Transformationskomponente;
    Ermitteln, an der Transformationskomponente, eines zweiten Automatisierungsgerätes (130) der Vielzahl der Automatisierungsgeräte als Zielgerät und eines Datenprotokolls, das mit dem zweiten Automatisierungsgerät (130) verknüpft ist, als Zieldatenprotokoll;
    Erhalten, an der Transformationskomponente, von Übersetzungsinformationen, die ein Format in Übereinstimmung mit Zieldatenprotokoll spezifizieren;
    Anwenden, an der Transformationskomponente, der erhaltenen Übersetzungsinformationen auf die empfangenen Daten in dem intermediären Protokoll, um die Daten in das Zielprotokoll (440) zu übersetzen, das durch das zweite Automatisierungsgerät verwendet wird; und
    Transferieren (830) der übersetzten Daten in dem Zieldatenprotokoll von der Transformationskomponente an das zweite Automatisierungsgerät (130).
  2. Verfahren nach Anspruch 1, wobei das Erhalten der Übersetzungsinformationen eine Feststellung umfasst, ob die Übersetzungsinformationen lokal gespeichert sind; und ein Herunterladen der Übersetzungsinformationen von einer Netzwerkdatenbank, wenn festgestellt wird, dass die Übersetzungsinformationen nicht lokal gespeichert sind.
  3. Verfahren nach Anspruch 1 oder 2, wobei die Quelldaten (410) schematisiert sind und als XML-Dokument formatiert sind.
  4. Verfahren nach einem der Ansprüche 1 bis 3, wobei das Übersetzen des Quelldatenprotokolls in das intermediäre Datenprotokoll (420) die Verwendung von XLST umfasst.
  5. Verfahren nach einem der Ansprüche 1 bis 4, wobei das zur Verfügungstellen (830) der übersetzten Daten an zumindest ein zweites Automatisierungsgerät (130) eine zur Verfügungstellung der übersetzten Daten für das Herunterladen über eine Netzwerkverbindung (320) umfasst.
  6. Verfahren nach einem der Ansprüche 1 bis 5, wobei das Übersetzen der Quelldaten (410) in ein intermediäres Datenprotokoll (420) eine Erzeugung eines XML-Dokuments in Übereinstimmung mit einer Formatvorlage, die Einzelheiten des intermediären Datenprotokolls angibt, umfasst.
  7. Verfahren nach Anspruch 6, wobei die Formatvorlage aus einer Netzwerkdatenbank (510) abgerufen wird.
  8. Verfahren nach einem der Ansprüche 1 bis 7, wobei die Transformationskomponente (110) als Netzwerkservice (320) verwendet werden kann, auf den die Vielzahl der Automatisierungsgeräte (310) zugreifen kann.
  9. Verfahren nach einem der Ansprüche 1 bis 8, wobei jedes der Vielzahl der Automatisierungsgeräte (310) ein programmierbarer Logikkontroller, PLC, oder eine Industriemaschine unter Steuerung einer PLC ist.
  10. Verfahren nach einem der Ansprüche 1 bis 9, wobei der Empfangsschritt (830) ein Herunterladen der Daten über eine Netzwerkverbindung (320) umfasst.
  11. Verfahren nach einem der Ansprüche 1 bis 10, wobei die Übersetzungsinformationen eine Formatvorlage sind, die die Struktur und das Format des Zielprotokolls spezifiziert.
  12. Verfahren nach einem der Ansprüche 1 bis 11, wobei das erste Automatisierungsgerät (120) und das zweite Automatisierungsgerät (130) auf unterschiedlichen Steuerplattformen sitzen.
  13. Computerlesbares Medium, auf dem computerausführbare Anweisungen gespeichert sind, um das Verfahren nach einem der Ansprüche 1 bis 12 auszuführen.
  14. Erweiterbares Datentransformationssystem zur Verwendung mit einem industriellen Steuersystem, das eine Vielzahl von Automatisierungsgeräten (320) umfasst, wobei die Vielzahl der Automatisierungsgeräte unterschiedliche Datenprotokolle verwenden, umfassend:
    eine Transformationskomponente (110), die dazu eingerichtet ist, Quelldaten (410) von zumindest einem ersten Automatisierungsgerät (120) der Vielzahl der Automatisierungsgeräte in Übereinstimmung mit einem Quelldatenprotokoll, das mit dem ersten Automatisierungsgerät (120) verknüpft ist, zu empfangen, die Quelldaten in ein intermediäres Datenprotokoll (420) zu übersetzen, ein zweites Automatisierungsgerät (130) der Vielzahl der Automatisierungsgeräte als Zielgerät und ein Datenprotokoll, das mit dem zweiten Automatisierungsgerät (130) verknüpft ist, als Zieldatenprotokoll zu bestimmen, Übersetzungsinformationen, die ein Format in Übereinstimmung mit dem Zieldatenprotokoll spezifieren, zu erhalten, und die erhaltenen Übersetzungsinformationen auf die empfangenen Daten in dem intermediären Protokoll anzuwenden, um die Daten in das Zielprotokoll (440) zu übersetzen, das durch das zweite Automatisierungsgerät verwendet wird; und
    Mittel zur Transferierung (830) der übersetzten Daten in dem Zieldatenprotokoll von der Transformationskomponente an das zweite Automatisierungsgerät (130).
  15. System nach Anspruch 14, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, festzustellen, ob die Übersetzungsinformationen lokal gespeichert sind, und die Übersetzungsinformationen von einer Netzwerkdatenbank herunterzuladen, wenn festgestellt wird, dass die Übersetzungsinformationen nicht lokal gespeichert sind.
  16. System nach Anspruch 14 oder 15, wobei die Quelldaten (410) schematisiert und als XML-Dokument formatiert sind.
  17. System nach einem der Ansprüche 14 bis 16, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, XSLT für die Übersetzung des Quelldatenprotokolls in das intermediäre Datenprotokoll (420) zu verwenden.
  18. System nach einem der Ansprüche 14 bis 17, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, die übersetzten Daten für das Herunterladen über eine Netzwerkverbindung (320) zur Verfügung zu stellen.
  19. System nach einem der Ansprüche 14 bis 18, wobei das Übersetzen der Quelldaten (410) in ein intermediäres Datenprotokoll (420) die Erzeugung eines XML-Dokuments in Übereinstimmung mit einer Formatvorlage umfasst, die Details des intermediären Datenprotokolls spezifiziert.
  20. System nach Anspruch 19, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, die Formatvorlage aus einer Netzwerkdatenbank (510) abzurufen.
  21. System nach einem der Ansprüche 14 bis 20, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, als Netzwerkservice (320) verwendet zu werden, auf den die Vielzahl der Automatisierungsgeräte (310) zugreifen kann.
  22. System nach einem der Ansprüche 14 bis 21, wobei jedes der Vielzahl der Automatisierungsgeräte (310) ein programmierbarer Logikkontroller, PLC, oder eine Industriemaschine unter Steuerung einer PLC ist.
  23. System nach einem der Ansprüche 14 bis 22, wobei die Transformationskomponente (110) des Weiteren dazu eingerichtet ist, die Quelldaten über eine Netzwerkverbindung (320) herunterzuladen.
  24. System nach einem der Ansprüche 14 bis 23, wobei die Übersetzungsinformationen eine Formatvorlage sind, die die Struktur und das Format des Zielprotokolls spezifiziert.
  25. System nach einem der Ansprüche 14 bis 24, wobei das erste Automatisierungsgerät (120) und das zweite Automatisierungsgerät (130) auf unterschiedlichen Steuerplattformen sitzen.
EP05013987.2A 2004-06-29 2005-06-28 Erweiterbares Datentransformationssystem Active EP1612630B1 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US88017704A 2004-06-29 2004-06-29

Publications (2)

Publication Number Publication Date
EP1612630A1 EP1612630A1 (de) 2006-01-04
EP1612630B1 true EP1612630B1 (de) 2015-02-25

Family

ID=34993252

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05013987.2A Active EP1612630B1 (de) 2004-06-29 2005-06-28 Erweiterbares Datentransformationssystem

Country Status (1)

Country Link
EP (1) EP1612630B1 (de)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102006038696B4 (de) * 2006-08-18 2012-05-03 Dematic Gmbh System und Verfahren zur Steuerung einer fördertechnischen Anlage mit einer Kommunikationsvorrichtung zur Umwandlung von Daten zwischen unterschiedlichen Datenformaten
US8276186B2 (en) * 2008-01-22 2012-09-25 Honeywell International Inc. System and method for synchronizing security settings of control systems
US8885665B2 (en) 2011-05-31 2014-11-11 General Electric Company Systems and methods for foundation fieldbus alerts
US20120310373A1 (en) * 2011-05-31 2012-12-06 General Electric Company Systems and methods for alert capture and transmission
US8994545B2 (en) 2011-05-31 2015-03-31 General Electric Company Systems and methods for alert device removal
US8856302B2 (en) 2011-05-31 2014-10-07 General Electric Company Systems and methods for foundation fieldbus alerts
EP2533113B1 (de) 2011-06-10 2018-08-08 Siemens Aktiengesellschaft Verfahren zum Betrieb eines Automatisierungsgerätes
JP5942446B2 (ja) * 2012-02-01 2016-06-29 オムロン株式会社 サポート装置およびサポートプログラム
TWI588636B (zh) * 2015-12-01 2017-06-21 亞智科技股份有限公司 用於控制工業設備的方法以及控制工業設備的系統
US10621195B2 (en) 2016-09-20 2020-04-14 Microsoft Technology Licensing, Llc Facilitating data transformations
US10706066B2 (en) 2016-10-17 2020-07-07 Microsoft Technology Licensing, Llc Extensible data transformations
US10776380B2 (en) 2016-10-21 2020-09-15 Microsoft Technology Licensing, Llc Efficient transformation program generation
US11163788B2 (en) 2016-11-04 2021-11-02 Microsoft Technology Licensing, Llc Generating and ranking transformation programs
US11170020B2 (en) 2016-11-04 2021-11-09 Microsoft Technology Licensing, Llc Collecting and annotating transformation tools for use in generating transformation programs
CN110568806B (zh) * 2019-10-25 2022-05-06 上海电气集团股份有限公司 伺服驱动器以及伺服驱动系统

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030014500A1 (en) * 2001-07-10 2003-01-16 Schleiss Trevor D. Transactional data communications for process control systems

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10138533A1 (de) * 2000-12-15 2002-07-11 Siemens Ag Bereitstellung von Projekt- und/oder Projektierungsdaten eines Automatisierungsprojekts in einem durch eine standardisierte Meta-Sprache, insbesondere XML, definiertem Format
AU2003265227A1 (en) * 2002-03-12 2003-12-22 Ils Technology, Inc. Diagnostic system and method for integrated remote tool access, data collection, and control
DE10251502A1 (de) * 2002-11-04 2004-06-09 Endress + Hauser Gmbh + Co. Kg Feldgerät für die Prozessautomatisierung zum Erfassen und/oder Beeinflussen einer Prozessvariablen mit mindestens zwei Kommunikationsschnittstellen

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030014500A1 (en) * 2001-07-10 2003-01-16 Schleiss Trevor D. Transactional data communications for process control systems

Also Published As

Publication number Publication date
EP1612630A1 (de) 2006-01-04

Similar Documents

Publication Publication Date Title
EP1612630B1 (de) Erweiterbares Datentransformationssystem
US10338551B2 (en) P and ID and control system synchronization
JP5030584B2 (ja) ＭＯＤＢＵＳデバイスネットワーク及びＦｉｅｌｄｂｕｓデバイスネットワークとともに使用するためのインターフェイスモジュール
US7467018B1 (en) Embedded database systems and methods in an industrial controller environment
EP3042254B1 (de) Systeme und verfahren zur virtualisierung einer speicherprogrammierbaren steuerung
US8156232B2 (en) Network communications in an industrial automation environment
US8266602B2 (en) Apparatus and method for converting between device description languages in a process control system
GB2484008B (en) Methods and apparatus to manage process data
US11531381B2 (en) Smart functionality for discrete field devices and signals
US9124445B2 (en) Apparatus for integrating device objects into a superordinated control unit
EP1691245A1 (de) Komponentenbasierte Automatisierung
JP2019145149A (ja) プロセス制御システム内のデバイスと通信するための方法、有形の製品、及びプロセス制御システム内のフィールドデバイスと通信するための装置
CN103988477A (zh) 用于服务自动化技术的至少一个现场设备的装置
EP3101489A1 (de) Verfahren und vorrichtung zur konfigurierung eines verfahrenssteuerungssystems mit eine, elektronischen beschreibungssprachskript
Vadi et al. Induction motor control system with a Programmable Logic Controller (PLC) and Profibus communication for industrial plants—An experimental setup
WO2018165902A1 (zh) 一种通信协议解析代码自动生成方法及系统
WO2016107981A1 (en) Method, system, computer program and computer program product for industrial automation system
CA3035599C (en) Systems and methods for discovering configurations of legacy control systems
CN106959674A (zh) 一种半导体工艺配方的管理系统和方法
EP2649755B1 (de) Dynamische host-profile für optionsmodule
Diedrich et al. Function block applications in control systems based on IEC 61804
WO2014204635A1 (en) Cyber-physical systems programmable logic controller
US20050086663A1 (en) Automation object and method for writing information into an automation object
JP4776602B2 (ja) コントローラ用のプログラミング装置、コントローラ及びコントローラ管理システム
EP3923099B1 (de) Verfahren und vorrichtung zur ermöglichung des zugriffs auf prozessdaten einer lebensmittelproduktionsanlage

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: A1

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

AX Request for extension of the european patent

Extension state: AL BA HR LV MK YU

17P Request for examination filed

Effective date: 20060608

AKX Designation fees paid

Designated state(s): DE FR GB IT

17Q First examination report despatched

Effective date: 20071024

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602005045871

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G05B0019418000

Ipc: G05B0019042000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAC Information related to communication of intention to grant a patent modified

Free format text: ORIGINAL CODE: EPIDOSCIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: G05B 19/042 20060101AFI20141023BHEP

INTG Intention to grant announced

Effective date: 20141107

INTG Intention to grant announced

Effective date: 20141114

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB IT

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602005045871

Country of ref document: DE

Effective date: 20150409

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602005045871

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20151126

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230404

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20230523

Year of fee payment: 19

Ref country code: FR

Payment date: 20230523

Year of fee payment: 19

Ref country code: DE

Payment date: 20230523

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230523

Year of fee payment: 19