EP2589187A1 - Adaptation automatisée à différents protocoles éthernet industriels - Google Patents

Adaptation automatisée à différents protocoles éthernet industriels

Info

Publication number
EP2589187A1
EP2589187A1 EP11735608.9A EP11735608A EP2589187A1 EP 2589187 A1 EP2589187 A1 EP 2589187A1 EP 11735608 A EP11735608 A EP 11735608A EP 2589187 A1 EP2589187 A1 EP 2589187A1
Authority
EP
European Patent Office
Prior art keywords
protocol
data packet
industrial ethernet
ethernet
header
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
EP11735608.9A
Other languages
German (de)
English (en)
Inventor
Marco Colucci
Joachim Probst
Jochen Stinus
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.)
Endress and Hauser Flowtec AG
Original Assignee
Endress and Hauser Flowtec AG
Flowtec AG
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 Endress and Hauser Flowtec AG, Flowtec AG filed Critical Endress and Hauser Flowtec AG
Publication of EP2589187A1 publication Critical patent/EP2589187A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/403—Bus networks with centralised control, e.g. polling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/407—Bus networks with decentralised control
    • H04L12/413—Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40228—Modbus
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/4026—Bus for use in automation systems

Definitions

  • the invention relates to a method for configuring a field device according to the preamble of claim 1 and to a field device for connection to a field bus according to the preamble of claim 9.
  • field devices are often used to detect and / or influence process variables.
  • Examples of such field devices are level gauges, mass flowmeters, pressure and temperature measuring devices, etc., which detect the corresponding process variables level, flow, pressure or temperature as sensors.
  • field devices are all devices that are used close to the process and that provide or process process-relevant information.
  • a variety of such field devices is manufactured and sold by the company Endress + Hauser.
  • the object of the invention is to make it possible to adapt a field device to different Industrial Ethernet protocols. This object is achieved by the features specified in claims 1 and 9.
  • a method according to the invention is designed to configure a field device which is connected to a field bus, wherein the field bus is designed for I ndial Ethernet protocols.
  • the method includes the steps of analyzing a data packet transmitted on the fieldbus; the determination of an Industrial Ethernet protocol used in the data packet; and the automatic activation of a suitable for the determined Industrial Ethernet protocol protocol stack.
  • the method according to the invention for configuring the field device makes it possible for the field device to recognize the respectively used Industrial Ethernet protocol and automatically adjust to it by activating a protocol stack suitable for the respective Industrial Ethernet protocol. This considerably simplifies the handling of the variety of Industrial Ethernet derivatives currently available on the market. Since the adaptation of the field device to the respective protocol is performed automatically by the field device, errors in setting a suitable Industrial Ethernet protocol are avoided and the operating personnel are relieved.
  • Another advantage is that a single version of a particular field device can cover all major Industrial Ethernet protocols. It is therefore no longer necessary to offer a field device matched to this protocol with a suitable software version for each industrial Ethernet protocol. As there is only one device version and one software version that can be used for all major Industrial Ethernet protocols, the distribution of field devices as well as warehousing and software updates are significantly simplified.
  • the type field in the Ethernet header of a data packet is next evaluated to distinguish the various I ndustrial Ethernet protocols. If it follows from the type information that it is If the data packet is an Internet Protocol packet, then the port numbers used by the packet are evaluated. The evaluation results in the Industrial Ethernet protocol used. According to an advantageous embodiment, the Industrial Ethernet protocol is one of the following: EtherNet / IP, Modbus TCP, EtherCAT, PROFI NET, Powerlink.
  • a protocol stack suitable for this Industrial Ethernet protocol from various stored protocol stack components can be assembled on the side of the field device and subsequently activated. It takes advantage of the fact that some protocol layers are the same for many common Industrial Ethernet protocols, and that the required protocol stacks can be compiled at least into a number of subdivided versions of the rotocollstack components. As a result, the effort for providing a plurality of different protocol stacks is significantly reduced.
  • FIG. 1 shows an overview of a fieldbus system according to the invention
  • 3A shows a first variant of the transmission of data of an Industrial Ethernet protocol, in which the data is transmitted directly via Ethernet;
  • 3B shows a second variant of the transmission of data of an Industrial Ethernet protocol, in which the data is transmitted via TCP / IP or UDP / IP;
  • 4A shows a first Ethernet frame for transmitting EtherCAT data, the EtherCAT data being transmitted directly via Ethernet;
  • 4B shows a second Ethernet frame for transmitting EtherCAT data, the EtherCAT data being transmitted via UDP / IP;
  • 5 shows an overview of the different levels of the OSI layer model
  • 6 shows the data structure of an IP header
  • FIG. 7A shows the data structure of a UDP datagram
  • Fig. 7B shows the data structure of a TCP header
  • FIG 9 shows the structure of a field device according to the invention.
  • FIG. 1 shows an overview of a fieldbus system with three field devices 1, 2, 3, which are connected to a host computer 5 via a field bus 4.
  • conventional fieldbus systems such as Profibus, Fieldbus (FF) or HART have been used in previous fieldbus systems, in modern implementations increasingly Industrial Ethernet protocols are used.
  • FF Fieldbus
  • Industrial Ethernet protocols are used.
  • a large number of different Industrial Ethernet derivatives are used in industrial environments, for example PROFINET, EtherNet / IP, Modbus TCP, EtherCAT, Powerlink etc. It is not that one of the many Industrial Ethernet protocols particularly strong on the market.
  • the present invention provides a field device which supports various Industrial Ethernet protocols and which is capable of intercepting the fieldbus, automatically analyzing the Industrial Ethernet protocol used on the fieldbus and accordingly a suitable protocol stack for the relevant Industrial Ethernet protocol.
  • Ethernet frames For all Industrial Ethernet protocols, data is transmitted on the fieldbus using Ethernet frames.
  • the structure of an Ethernet frame is shown in FIG. This structure is defined in the IEEE 802.3 standard.
  • the destination MAC address 7 is specified first, then the source MAC address 8 is specified.
  • the MAC addresses are identifiers associated with a particular device hardware and a one-to-one Identify the relevant device hardware.
  • a VLAN tag 9 may be specified in the Ethernet header which indicates to which virtual LAN (Local Area Network) the Ethernet frame 6 belongs. If no different virtual LANs are defined in the system, the transmission of a VLAN tag is unnecessary.
  • Type field 10 specifies the type of Ethernet frame 6, the so-called "Ethertype.” For example, Ethernet frames in which data is transmitted in accordance with the Internet Protocol (IP) are identified with the Ethertype 0x0800. Headers are the actual payload data 1 1. In this case, the length of the user data 1 1 transmitted in an Ethernet frame 6 is variable, the entire Ethernet frame 6 can have a length between 64 bytes and 1518 bytes PAD pad 12, followed by a CRC (Cyclic Redundancy Check) checksum 13. PAD pad 12 includes so-called padding bytes, which are padding bytes used to populate the data field to a required minimum size.
  • CRC Cyclic Redundancy Check
  • the Ethernet frame 6 shown in FIG. 2 is used in all industrial Ethernet protocols as a basic unit for data transmission on the fieldbus.
  • the Ethernet header 14 is first transmitted, and the Ethernet header 14 is immediately followed by the data 1 5 of the respective Industrial Ethernet protocol.
  • the data 15 of the respective Industrial Ethernet protocol are transmitted in the user data field of the Ethernet frame. Since the Ethernet layer forms the levels 1 and 2 of the OSI layer model, this means that the data 15 of the Industrial Ethernet protocol are transmitted at level 3 (network layer) of the OSI layer model.
  • the PED and CRC fields 16 are transmitted.
  • the first variant shown in Figure 3A in which the data of the respective Industrial Ethernet protocol are transmitted on the OSI level 3, is used, for example, in the Industrial Ethernet protocol "Powerlink.”
  • the transmission of the data of the respective Industrial Ethernet protocol can also be carried out according to the second variant shown in Fig.
  • an Ethernet header 17 is transmitted.
  • the Ethernet header 17 is not directly followed by the user data of the respective Industrial Ethernet protocol, but instead additional protocol layers are introduced, after which an I P header 18, ie a header of the Internet Protocol, is transmitted following the Ethernet header 17, to which then a TCP (Transmission Control Protocol) or UDP (User Datagram Protocol) Header 19 follows, depending on whether the data transmission is to take place via TCP / IP or UDP / IP.After the two headers 18 and 19 then begins the over Tragu ng the data 20 of the respective Iustrustrial Ethernet protocol. At the conclusion of the Ethernet frame, the PED and CRC fields 21 are transmitted.
  • TCP is a connection-oriented protocol, which means that a data connection is established between sender and receiver. This enables reliable data transmission, which can detect and correct transmission errors.
  • UDP is a connectionless protocol with less administrative overhead compared to TCP. As a result, the network load on UDP is lower than on TCP, and higher data throughput can be achieved.
  • the advantage of using TCP / IP or UDP / IP for data transmission is that common hardware components that are also used in the infrastructure of the Internet can be used for routing and switching the data packets. In contrast to the first variant shown in FIG.
  • the level 3 of the OSI layer is Model formed by the Internet Protocol (IP), and the level 4 of the OSI model is through TCP or UDP formed.
  • IP Internet Protocol
  • TCP Transmission Control Protocol
  • UDP User Data Protocol
  • the second variant of the data transmission via TCP / IP or UDP / IP shown in FIG. 3B is used, for example, in the Industrial Ethernet protocols EtherNet / IP and Modbus TCP. These two Industrial Ethernet protocols use Internet Protocol (IP) as the basis. With EtherNet / IP, data can be transmitted via TCP / IP as well as UDP / IP. With Modbus TCP, the data is transmitted exclusively via TCP / IP.
  • IP Internet Protocol
  • Industrial Ethernet protocols that use both Ethernet frames of the type shown in Figure 3A and Ethernet frames of the type shown in Figure 3B.
  • These Industrial Ethernet protocols include, for example, the Industrial Ethernet protocols EtherCAT and PROFINET.
  • These two Industrial Ethernet protocols use both Ethernet frames according to the first variant, in which the data of the respective Industrial Ethernet protocol are transmitted directly in the user data field of the Ethernet frame, as well as Ethernet frames according to the second variant, in which the Transmission of the data of the respective Industrial Ethernet protocol via the intermediate layers TCP / IP or UDP / IP takes place.
  • the corresponding Ethernet frames are shown in FIGS. 4A and 4B for both variants of the data transmission. Both variants are used in EtherCAT.
  • the EtherCAT data is transmitted directly as user data of the Ethernet frame 22.
  • the Ethernet frame 22 shown in FIG. 4A corresponds to the first variant shown in FIG. 3A.
  • the Ethernet frame 22 consists of an Ethernet header 23, which includes the destination MAC address 24, the source MAC address 25 and the Ethertype 26.
  • the user data 27 are transmitted.
  • an EtherCAT-specific header 28 is first transmitted, which comprises the length 29, a reserved bit 30 and a type information 31.
  • EtherCAT commands and data 32 are transmitted.
  • a PAD pad and a CRC checksum 33 are transmitted.
  • EtherCAT commands and data are transmitted directly in the user data field.
  • it is an Ethernet frame with a dedicated Ethertype, namely 0x88A4.
  • the value 0x88A4 in the type field 10 of the Ethernet frame clarifies that EtherCAT data and commands are transmitted in the user data field of the Ethernet frame.
  • FIG. 4B shows an Ethernet frame 34 used for this purpose.
  • the Ethernet frame 34 comprises an Ethernet header 35 with a destination MAC address 36, a source MAC address 37 and an Ethertype 38.
  • an IP header 39 and a UDP In this respect, the Ethernet frame 34 corresponds to the second transmission variant shown in FIG. 3B.
  • the payload data 41 comprises an EtherCAT-specific header 42, in which the length and the type of the following EtherCAT commands and data are specified, followed by the EtherCAT commands and data 43.
  • a PAD Filling field and a CRC checksum 44 transferred.
  • Ethernet frame 34 In the Ethernet frame 34 shown in FIG. 4B, the transmission of the EtherCAT commands and data takes place via UDP / IP, that is via the Internet Protocol.
  • the Ethernet frame 34 is an IP packet. This is indicated by the value 0x0800 in the type field 10 of the Ethernet frame (see Fig. 2).
  • FIG. 5 again shows an overview of which levels of the OSI layer model the data transmission takes place in the various Industrial Ethernet protocols.
  • an Ethernet layer 46 serves as the basis for data transmission.
  • the Ethernet layer 46 forms the layers 1 and 2 (physical layer and data link layer) of the OSI layer model.
  • the Powerlink protocol 47 is directly based on the Ethernet layer 46. This corresponds to the first transmission variant shown in FIG. 3A.
  • the EtherCAT protocol 48 and in the PROFINET protocol 49 there are frames which are transmitted directly to the Ethernet layer 46.
  • the data transmission takes place completely at level 3 (network layer) of the OSI network. Layer model.
  • the EtherCAT protocol 48 and in the PROFINET protocol 49 the data transmission takes place at least partly on level 3.
  • an Internet Protocol layer 50 can be set up on the Ethernet layer 46 as level 3, onto which a TCP or UDP layer 51 is then set up as level 4 (transport layer). This corresponds to the second transmission variant shown in FIG. 3B.
  • the respective Industrial Ethernet protocol is then transmitted on level 5 of the OSI layer model, via TCP / IP or via UDP / IP.
  • the two protocols EtherNet / IP 52 and Modbus TCP 53 are transmitted at level 5 of the OSI model.
  • the EtherNet / IP 52 protocol can be transmitted via TCP / IP as well as via UDP / IP.
  • the Modbus TCP 53 protocol is only transmitted via TCP / IP.
  • the protocols PROFINET 48 and EtherCAT 49 can be transmitted not only at level 3, but also at level 5 of the OSI model, as illustrated in FIG.
  • the PROFINET 48 protocol can be transmitted via TCP / IP as well as via UDP / IP.
  • the EtherCAT 49 protocol is only transmitted via UDP / IP.
  • a field device is designed to evaluate the data traffic transmitted on the fieldbus and to determine the Industrial Ethernet protocol used there.
  • the field device can then set its own Industrial Ethernet protocol according to the Industrial Ethernet protocol used on the fieldbus.
  • the field device for example, activate a suitable protocol stack.
  • the field device first accesses the Ethernet header of an Ethernet frame transmitted on the fieldbus.
  • the structure of the Ethernet frame has already been illustrated in FIG.
  • the Ethernet frame 6 includes a type field 10 in which the type of the The Ethertype can be used to distinguish whether the Ethernet frame currently being transmitted on the fieldbus uses the Internet Protocol (IP) for data transmission or any other type of Ethernet frame If the Ethernet frame uses the Internet Protocol, this is indicated by the value 0x0800 in the type field 10 of the Ethernet header.
  • IP Internet Protocol
  • the Type field 10 is a value other than 0x0800, then it is not an I P packet.
  • the value stored in the Type field 10 can be used to immediately identify which protocol is being used at level 3 of the OSI layer model. For example, if the Type field 10 of the Ethernet header is 0x88AB, then level 3 uses the Powerlin k protocol, which is a Powerlink packet. On the other hand, if type field 10 is 0x88A4, then it is a package that uses the Level 3 EtherCAT protocol. If, on the other hand, the value 0x8892 in type field 10 is a PROFINET packet, the level 3 PROFINET protocol is used.
  • the Ethernet frame is not an IP packet, it can be determined by means of the type field 10 which Industrial Ethernet protocol is used.
  • the value 0x88AB is a Powerlink packet
  • 0x88A4 is an EtherCAT packet
  • the value 0x8892 is a PROFINET packet.
  • the Ethernet frame is an I P packet
  • no statement can be made about the I ndustrial Ethernet protocol used.
  • the analysis of the Ethernet frame continues. For this, the IP header following the Ethernet header is analyzed. For version 4 of the Internet Protocol (I Pv4), such an I p header is shown in FIG.
  • I Pv4 Internet Protocol
  • the I P header includes a version field 57, an IHL (IP Header Length) field 58, a TOS (Type of Service) field 59, a Total Length Field 60, an identification field 61, various flags 62, a fragment offset 63, a TTL (time-to-live) field 64, a protocol field 65 and a header checksum 66.
  • the IP Header a source address 67, a destination address 68 and additional information 69 ("Options and Padding").
  • Protocol field 65 which is transmitted as byte 9 of the IP header (where the numbering of the bytes starts with byte 0).
  • Protocol field 65 designates the follow-up protocol, ie the protocol following the Internet protocol at the next higher level, to which the user data transported in the IP packet belongs. For example, if the IP packet contains a TCP packet, then in the Protocol field 65 of the IP header is the value 6 for the TCP protocol. In contrast, if the IP packet contains a UDP packet, the protocol field 65 of the I P header contains the value 17 for the protocol UDP. Since RFC3232, these values have been set by the IANA (Internet Assigned Numbers Authority) in an online database for protocol numbers.
  • IANA Internet Assigned Numbers Authority
  • IPv6 In the IP header of version 6 of the Internet Protocol (IPv6), there is also a field which specifies the protocol that follows at the next higher level and corresponds to the Protocol field 65, however, it says "Next Header.”
  • the permissible values are in In the version IPv6, the same as in the version IPv4
  • the information as to whether TCP or UDP is used as a follow-up protocol can then be used to properly read out the UDP datagram or the TCP header, in particular the information as to whether UDP or TCP is used as a follow-up protocol to determine the source port and the destination port of the I P packet, as illustrated below with reference to Figures 7A and 7B, the port numbers of the source port and destination port permit dan n the determination of the Industrial Ethernet protocol used.
  • Fig. 7A shows the structure of a UDP datagram.
  • the UDP datagram includes a field 70 for the source port in which the port number is specified on the sender side.
  • the UDP datagram includes a destination port field 71 indicating the port number on the receiver side.
  • field 72 is the length of the UDP datagram, and in box 73 a checksum is transmitted. Subsequently, the user data 74 are transmitted.
  • the port numbers on the sender and receiver sides can therefore be obtained by reading fields 70 and 71 of the UDP datagram.
  • TCP can be used as the transmission protocol at level 4 of the OSI layer model.
  • Fig. 7B shows the structure of a TCP header.
  • the TCP header includes a field 75 for the source port, a destination port field 76, a sequence number field 77, and an acknowledgment number field 78.
  • the TCP header comprises a field "Data Offset” 79, a reserve field 80, a series of flags 81, a field "Window” 82, a checksum field 83, an "Urgent Pointer” 84 and an option field 85 Connection to the option field 85, the transmission of the user data 86 begins.
  • the source port and the destination port of the IP packet can be determined. Where the source port is the port number on the sender side, while the destination port is the port number on the receiver side.
  • These port numbers are characteristic of the Industrial Ethernet protocol used. Therefore, an evaluation of these port numbers enables the determination of the Industrial Ethernet protocol used both in the example of a UDP datagram shown in FIG. 7A and in the example of a TCP header shown in FIG. 7B.
  • the evaluation of the port numbers thus obtained can be done, for example, on the basis of the following overview:
  • the above table shows that the port numbers used are specific to the particular Industrial Ethernet protocol used.
  • an IP packet which is indicated by the Ethertype 0x0800
  • it is therefore possible to determine which Industrial Ethernet protocol for the data transmission by evaluating the port numbers of the source port and the destination port the field bus is used.
  • the assignment of the port numbers to the corresponding Industrial Ethernet protocol can be carried out by means of simultaneous assignment of links.
  • FIG. 8A shows the method according to the invention for the automatic selection of a suitable Industrial Ethernet protocol in the form of a flow chart.
  • step 87 the Ethertype of the Ethernet frame is evaluated based on the type field in the Ethernet header. If the Ethertype is not equal to 0x0800, then it is an Ethernet frame with a dedicated Ethertype. In In this case, the Ethertype allows you to draw conclusions about the Industrial Ethernet protocol used.
  • the used Industrial Ethernet protocol can be determined in step 88 based on the Ethertype.
  • step 89 the protocol stack associated with the determined Industrial Ethernet protocol is then activated on the side of the field device.
  • the Ethernet Frame is an IP packet.
  • byte 9 of the IP header is read out in the next step 90, in order to determine the subsequent protocol, that is to say the protocol following at the next higher level on the Internet Protocol. If the value 6 is in byte No. 9 of the IP header, then the follow-up protocol is TCP, if there is the value 17, then it is UDP.
  • the respective header of the following protocol is accessed, for example the TCP header or the UDP header, in order to determine the ports of the port and destination port of the IP packet.
  • These port numbers are specific to the Industrial Ethernet protocol used.
  • the Industrial Ethernet protocol used can be determined on the basis of the port numbers.
  • the industrial Ethernet protocol belonging to the port numbers can be determined by means of an allocation table.
  • step 93 the protocol stack associated with the determined Industrial Ethernet protocol is then activated on the side of the field device.
  • the user data transmitted in the data packet can also be analyzed to determine the Industrial Ethernet protocol used.
  • the payload data is checked for protocol-specific structures contained therein, in particular on at least one of: Commands, objects, services, addresses, blocks, etc. that are typical of the Industrial Ethernet protocol used.
  • Fig. 8B a modified flow is shown for such "hybrid" installations where two or more different Industrial Ethernet protocols are used side by side.
  • a first step 94 the destination MAC address of the Ethernet frame is compared with the field device's own MAC address to find out if the Ethernet frame is addressed to the field device.
  • step 95 waits for the next Ethernet frame. If, on the other hand, the destination MAC address of the Ethernet frame matches the own MAC address of the field device, then it is clear that the considered Ethernet frame is addressed to the field device. Only in this case will the Industrial Ethernet protocol used in the Ethernet frame be determined. As soon as it is certain that the considered Ethernet frame is addressed to the own field device, the used Industrial Ethernet protocol is determined. The process corresponds to the steps shown in FIG. 8A. In step 96, the Ethertype of the Ethernet frame is evaluated on the basis of the type field in the Ethernet header.
  • step 97 the Ethertype is used to determine the Industrial Ethernet protocol used.
  • step 98 the protocol stack for the determined Industrial Ethernet protocol is then activated on the side of the field device.
  • the Ethernet Frame is an IP packet.
  • byte # 9 of the IP header is read out in step 99 so as to determine the protocol following the Internet Protocol (for example, UDP or TCP).
  • the port numbers of the source port and the destination port of the IP packet are read out.
  • the respective header of the follow-up protocol is accessed, for example, the TCP header or the UDP header.
  • the Industrial Ethernet protocol used is determined on the basis of the thus determined port numbers.
  • step 102 the appropriate protocol stack is then activated on the side of the field device.
  • FIG. 9 shows how the appropriate protocol stack can be compiled and activated on the side of the field device 103. Preferably, this can be done using a modular system of different protocol stack components that are put together properly.
  • the field device 103 comprises a processor unit 104, a volatile main memory 105 and a nonvolatile memory 106, for example a flash memory.
  • nonvolatile memory 106 various protocol stack components are stored in addition to the operating software 107.
  • nonvolatile memory 106 includes an Ethernet layer 108, a UDP / IP stack 109, a TCP / IP stack 110 and the Industrial Ethernet protocol levels for EtherNet / IP 1 1 1, Modbus TCP 1 12, EtherCAT 1 13, PROFINET 1 14, Powerlink 1 15 etc. stored.
  • a configuration unit 16 which runs in the main memory 105 analyzes the Ethernet frames transmitted on the field bus.
  • the configuration unit 1 16 determines the Industrial Ethernet protocol used in the Ethernet frames with the aid of the method shown in FIGS. 8A and 8B. Subsequently, a protocol stack suitable for the determined protocol is compiled. For this purpose, the various required protocol stack components are loaded from the non-volatile memory 1 06 in the main memory 1 05. The protocol stack compiled in the main memory 105 is activated.
  • the configuration unit 16 determines that the Ethernet frames use the Modbus TCP protocol.
  • the configuration unit 1 16 loads from the nonvolatile memory 106 the Ethernet layer 108, the TCP / IP stack 110 and the protocol level to Modbus TCP 1 12. From these components The required Modbus TCP stack 1 17 can be modularly assembled. Subsequently, the so assembled Modbus TCP stack 1 17 is activated, and the field device can communicate via Modbus TCP on the fieldbus.
  • the modular composition of the required protocol stacks offers the advantage that the storage requirements for the stack components needed to compile the protocol stacks for a large number of different Industrial Ethernet protocols can be kept within reasonable limits. This makes it possible to implement a field device with reasonable effort, which can automatically adjust to a large number of different Industrial Ethernet protocols.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Communication Control (AREA)

Abstract

L'invention concerne un procédé de configuration d'un appareil de terrain qui est relié à un bus de terrain, le bus de terrain étant conçu pour des protocoles Ethernet industriels, le procédé comprenant les étapes suivantes: analyse d'un paquet de données transmis par le bus de terrain; détermination d'un protocole Ethernet industriel appliqué dans le paquet de données; activation automatique d'une pile de protocoles appropriée pour le protocole Ethernet industriel déterminé.
EP11735608.9A 2010-07-01 2011-06-20 Adaptation automatisée à différents protocoles éthernet industriels Withdrawn EP2589187A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102010030811A DE102010030811A1 (de) 2010-07-01 2010-07-01 Automatisierte Adaption an verschiedene Industrial Ethernet Protokolle
PCT/EP2011/060185 WO2012000813A1 (fr) 2010-06-30 2011-06-20 Adaptation automatisée à différents protocoles éthernet industriels

Publications (1)

Publication Number Publication Date
EP2589187A1 true EP2589187A1 (fr) 2013-05-08

Family

ID=44484119

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11735608.9A Withdrawn EP2589187A1 (fr) 2010-07-01 2011-06-20 Adaptation automatisée à différents protocoles éthernet industriels

Country Status (4)

Country Link
US (1) US20130208724A1 (fr)
EP (1) EP2589187A1 (fr)
DE (1) DE102010030811A1 (fr)
WO (1) WO2012000813A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070589A (zh) * 2016-12-30 2017-08-18 国网浙江省电力公司电力科学研究院 一种基于面向对象协议与传统协议的电能表自适应方法、装置及电能表

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102009027168B4 (de) * 2009-06-24 2021-01-21 Endress+Hauser SE+Co. KG Verfahren zum Ermitteln einer übermittelten Telegramm-Datenlänge
DE102011117083A1 (de) * 2011-10-27 2013-05-02 Volkswagen Aktiengesellschaft Slave-Steuergerät und Verfahren zur Programmierung eines Slave-Steuergeräts
EP2713563B1 (fr) * 2012-09-28 2017-08-02 Siemens Aktiengesellschaft Système de communication industriel pouvant fonctionner de manière redondante, appareil de communication et procédé de fonctionnement redondant d'un système de communication industriel
DE102013103242B4 (de) * 2013-03-28 2021-06-24 Phoenix Contact Gmbh & Co. Kg Feldgerät, Kommunikations-Chip und Verfahren zum Zugreifen auf ein Feldgerät
CN103780427A (zh) * 2014-01-17 2014-05-07 加弘科技咨询(上海)有限公司 基于fpga生成多协议错误管理报文的方法及系统
DE102014108455A1 (de) * 2014-06-16 2015-12-17 Beckhoff Automation Gmbh Verfahren zum Betreiben eines Netzwerks
EP3056953A1 (fr) * 2015-02-11 2016-08-17 Siemens Aktiengesellschaft Dispositif de terrain autarcique pour la surveillance à distance d'un système d'automatisation
KR101632835B1 (ko) * 2015-04-14 2016-06-23 엘에스산전 주식회사 Plc 시스템의 프로토콜 자동 설정 방법
CN105978896A (zh) * 2016-06-24 2016-09-28 天津瑞能电气有限公司 一种工业以太网从站转Modbus主站的通信装置
DE102016221690A1 (de) 2016-11-04 2018-05-09 Audi Ag Verfahren zum Übertragen von Datenpaketen zwischen einem Ethernet und einem Bussystem in einem Kraftfahrzeug sowie Gatewayvorrichtung und Kraftfahrzeug
DE102017208831A1 (de) * 2017-05-24 2018-11-29 Wago Verwaltungsgesellschaft Mbh Verarbeitung von Prozessdaten
CN109426302B (zh) * 2017-08-30 2022-05-20 西门子（中国）有限公司 一种数据分析设备和方法
EP3462256A1 (fr) * 2017-09-29 2019-04-03 Wachendorff Automation GmbH & Co. KG Configuration d'un système de mesure connecté à un système de bus
EP3620877A1 (fr) * 2018-09-06 2020-03-11 Siemens Aktiengesellschaft Procédé de simulation d'une installation technique, appareil, système, programme informatique et produit programme informatique
DE102019114305A1 (de) * 2019-05-28 2020-12-03 Beckhoff Automation Gmbh Datenübertragungsverfahren, Datenstruktur, Automatisierungsnetzwerk und Entsperrer
CN112448924A (zh) * 2019-08-30 2021-03-05 北京东土科技股份有限公司 一种兼容多种协议的报文处理方法、系统及交换设备
DE102020203732B4 (de) 2020-03-23 2022-01-05 Lenze Se Elektrisches Steuergerät
CN111970230B (zh) * 2020-06-24 2023-03-31 格创东智(深圳)科技有限公司 基于云端识别的工业现场协议自动解析的方法及系统
KR102347881B1 (ko) * 2020-08-21 2022-01-05 장진욱 자동 프로토콜 설정을 지원하는 태양광 발전을 위한 모니터링 장치 및 이의 자동 프로토콜 설정 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6665725B1 (en) * 1999-06-30 2003-12-16 Hi/Fn, Inc. Processing protocol specific information in packets specified by a protocol description language
US20070112961A1 (en) * 2003-05-28 2007-05-17 Schneider Electric Industries Sas Access control system for automation equipment
US20100040075A1 (en) * 2006-12-01 2010-02-18 Phoenix Contact Gmbh & Co. Kg Method for operating an ethernet-capable field-bus device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5613096A (en) * 1994-11-04 1997-03-18 Canon Information Systems, Inc. Network protocol sensor
US7274706B1 (en) * 2001-04-24 2007-09-25 Syrus Ziai Methods and systems for processing network data
EP1522178B1 (fr) * 2002-06-25 2008-03-12 PR Electronics A/S Procede et adaptateur de detection de protocole dans un reseau a bus de terrain
US20050228509A1 (en) * 2004-04-07 2005-10-13 Robert James System, device, and method for adaptively providing a fieldbus link
JP4530806B2 (ja) * 2004-11-05 2010-08-25 富士通株式会社 パケット伝送装置
DE102004055308A1 (de) * 2004-11-16 2006-05-18 Endress + Hauser Flowtec Ag Funkeinheit für ein Feldgerät der Automatisierungstechnik
DE202005012013U1 (de) * 2005-07-30 2006-12-14 Weidmüller Interface GmbH & Co. KG Verteilersystem als Teil eines Ethernet-Netzwerks
DE102007050941A1 (de) * 2007-10-23 2009-04-30 Phoenix Contact Gmbh & Co. Kg Verfahren zum Übertragen von Daten in einem Kommunikationsnetz, Sende- und Empfangsvorrichtung für ein Kommunikationsnetz

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6665725B1 (en) * 1999-06-30 2003-12-16 Hi/Fn, Inc. Processing protocol specific information in packets specified by a protocol description language
US20070112961A1 (en) * 2003-05-28 2007-05-17 Schneider Electric Industries Sas Access control system for automation equipment
US20100040075A1 (en) * 2006-12-01 2010-02-18 Phoenix Contact Gmbh & Co. Kg Method for operating an ethernet-capable field-bus device

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107070589A (zh) * 2016-12-30 2017-08-18 国网浙江省电力公司电力科学研究院 一种基于面向对象协议与传统协议的电能表自适应方法、装置及电能表

Also Published As

Publication number Publication date
DE102010030811A1 (de) 2012-01-05
WO2012000813A1 (fr) 2012-01-05
US20130208724A1 (en) 2013-08-15

Similar Documents

Publication Publication Date Title
EP2589187A1 (fr) Adaptation automatisée à différents protocoles éthernet industriels
EP2625822B1 (fr) Procédé pour configurer un ou plusieurs appareils dans un réseau de communication basé sur ethernet
EP2676409B1 (fr) Boucles de trajets mpls au niveau réacheminement pour réseaux mpls sans connexion
WO2016119956A1 (fr) Dispositif d'accès à des appareils au moyen d'un pilote de communication générique
DE102004052075A1 (de) Knoten für ein Bus-Netzwerk, Bus-Netzwerk und Verfahren zum Konfigurieren des Netzwerks
DE102019114303B3 (de) Verfahren zum Erfassen von Netzwerkteilnehmer in einem Automatisierungsnetzwerk und Automatisierungsnetzwerk
WO2020239285A1 (fr) Procédé de routage de télégrammes dans un réseau d'automatisation, structure de données, réseau d'automatisation et répartiteur de réseau
WO2015117749A1 (fr) Module de bus de terrain, commande de machine et procédé de paramétrage d'un module de bus de terrain, notamment sécurisé
EP3092748B1 (fr) Procédé et système pour le diagnostic de perturbations de transmission dans un réseau selon le standard opc ua
EP3051779A1 (fr) Procédé d'identification de liaison avec sécurité de fonctionnement et système de communication
DE102005037376B3 (de) Verfahren zur Stempelung beliebiger Ethernet-Frames in Verbindung mit Standard-Ethernet
WO2005013020A1 (fr) Procede pour adapter automatiquement un appareil de champ d'automatisation des processus, apte aux bus, au protocole de bus utilise dans le bus de champ
DE102018129813A1 (de) Datenübertragungsverfahren und Automatisierungskommunikationsnetzwerk
EP4035315A1 (fr) Réseau d'automatisation et procédé de transmission de données dans un réseau d'automatisation
DE102007043707B4 (de) Kommunikationssystem
WO2021028186A1 (fr) Distributeur de réseau, réseau d'automatisation et procédé de transmission de données dans un réseau d'automatisation
EP2506503A1 (fr) Réseau d'automatisation doté de composants de système de gestion
WO2020048868A1 (fr) Procédé pour la simulation d'une installation technique, appareil, système, programme informatique et produit programme informatique
DE102013215029B4 (de) Verfahren zur Datenkommunikation in einem Netzwerk sowie Netzwerk
EP4070530B1 (fr) Procédé de transmission cyclique de données entre des abonnés de communication sur un canal de transmission de données et système de transmission de données
BE1031167B1 (de) WLAN-fähiges Endgerät, WLAN-fähige Basisstation und Kommunikationssystem umfassend eine WLAN-fähige Basisstation und mehrere WLAN-fähige Endgeräte
DE10250201B4 (de) Verfahren und Vorrichtung zum Austausch von Daten mittels einer Tunnelverbindung
WO2009118289A1 (fr) Procédé pour faire fonctionner un appareil de communication et appareil de communication correspondant
EP2226694A1 (fr) Appareil de programmation et procédé destiné au paramétrage d'une liaison de communication entre des composants d'automatisation dans un agencement d'automatisation industriel
DE102019217626A1 (de) Maschine und Verfahren zum Schutz von Geräten in einem Feldbusnetzwerk

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20121122

AK Designated contracting states

Kind code of ref document: A1

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

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20140131

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