Industrial ethernet communication method and system

Abstract

This invention provides an industrial Ethernet communication method and system, applied to a network system comprising a master control device and multiple device nodes, and specifically to the application layer of the TCP / IP five-layer model. The method includes: establishing a management channel and a working channel for data transmission; the management channel is used for the master control device and each device node to broadcast their respective device configuration information; the working channel is used for each device node to report its own device status and for the master control device to send control commands to each device node; in the working channel, when each device node reports its own device status, a data frame initiated by one device node passes through other device nodes sequentially before returning to the master control device, and each of the other device nodes, acting as multiplexing device nodes, sequentially adds its own device data information to the data frame. This invention does not involve hardware layer modifications, and the multiplexing of data streams significantly improves bandwidth utilization, effectively enhancing the communication performance of industrial Ethernet.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to an industrial Ethernet communication method and system. Background Technology

[0002] As traditional manufacturing enterprises transform towards automated and intelligent manufacturing, the Industrial Internet is rapidly emerging worldwide. Within the technological architecture of the Industrial Internet, devices are increasingly using industrial Ethernet for communication.

[0003] Currently, mainstream industrial Ethernet systems either involve hardware layer modifications, such as EtherCAT, which use unique, dedicated Ethernet controllers instead of general-purpose traditional Ethernet controllers; or software layer modifications, such as TCP / UDP / IP transmission, without changing the hardware layer, which uses general-purpose traditional Ethernet controllers, such as Ethernet / IP.

[0004] Hardware-modified industrial Ethernet, such as EtherCAT, has the disadvantage of higher implementation costs because it uses dedicated hardware, requiring specialized chips to handle the protocol, and necessitates separate network deployment, resulting in higher network equipment prices. Compared to industrial Ethernet based on TCP / UDP / IP transmission (such as Ethernet / IP), hardware costs are significantly higher.

[0005] Industrial Ethernet based on TCP / UDP / IP transmission (such as Ethernet / IP) has the disadvantage that data streams are not reusable. Data sent by the master device is routed to each device node, and the device nodes then send data back to the master device. Individual device nodes cannot add data, and both device nodes and the master device are constantly sending and receiving data, thus consuming more bandwidth.

[0006] Therefore, how to improve the performance of industrial Ethernet at low cost has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0007] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide an industrial Ethernet communication method and system for improving the communication performance of industrial Ethernet.

[0008] To achieve the above and other related objectives, this invention provides an industrial Ethernet communication method applied to a network system comprising a master control device and multiple device nodes, and the method is applied to the application layer of the TCP / IP five-layer model. The method includes: establishing a management channel and a working channel for data transmission; the management channel is used for the master control device and each device node to broadcast their respective device configuration information; the working channel is used for each device node to report its own device status and for the master control device to send control commands to each device node; wherein, in the working channel, when each device node reports its own device status, a data frame initiated by one device node passes through other device nodes sequentially before returning to the master control device, and each of the other device nodes, acting as multiplexing device nodes, sequentially adds its own device data information to the data frame.

[0009] In one embodiment of the present invention, the management channel for broadcasting device configuration information to the master control device and each device node includes: after establishing a network connection, the master control device and each device node respectively send heartbeat packets to a fixed multicast address; wherein, the heartbeat of each device node contains the hardware configuration information of the device; after receiving the heartbeat packet of the device node, the master control device sends a unicast packet to the corresponding device node, and the unicast packet is used to configure the parameters of the device node.

[0010] In one embodiment of the present invention, when the master control device sends control instructions to each of the device nodes, the data frame sent contains control instructions for multiple device nodes, and the control instructions flow through each of the device nodes in sequence, with each device node sequentially acquiring the corresponding control instructions.

[0011] In one embodiment of the present invention, the header of the data frame includes an opcode, which is used to indicate whether the data frame is a data frame in which each of the device nodes reports its own status to the master control device or a data frame in which the master control device sends control commands to each of the device nodes.

[0012] In one embodiment of the present invention, the data frame includes a data recording segment for recording the data length of the data information added by each device node; when each device node receives the data frame, it detects the current data length of the data recording segment after adding its own data information, and if the current data length is less than or equal to a data length threshold, it acts as a reused device node; if the current data length is greater than the data length threshold, it does not act as a reused device node and does not add its own data information to the data frame.

[0013] In one embodiment of the present invention, for a device node that is not used as a multiplexing device node, the device node initiates a new data frame separately to report the status of the device itself.

[0014] In one embodiment of the present invention, the header of the data frame further includes a number of multiplexed device nodes, a number of device nodes to be multiplexed, and a number of device nodes that do not report their own status. When a device node receives the data frame, it modifies the corresponding number in the number of multiplexed device nodes, the number of device nodes to be multiplexed, or the number of device nodes that do not report their own status.

[0015] In one embodiment of the present invention, the master control device determines the distance between itself and the device node that initiated the data frame based on the sum of the corresponding numbers in the multiplexing device node number byte, the number of device nodes to be multiplexed byte, and the number of device nodes that do not report their own status; the master control device determines the communication network topology formed by each device node based on the distance between itself and the device node that initiated the data frame.

[0016] To achieve the above and other related objectives, the present invention also provides an industrial Ethernet communication system, comprising: a master control device and multiple device nodes; the master control device and the multiple device nodes communicate using the industrial Ethernet communication method described above; wherein, each device node, serving as a multiplexed device node, is configured with at least a first network interface card (NIC) and a second NIC; the first NIC is used to receive data frames including control commands and initiate data frames, and the second NIC is used to receive data frames reporting the device's own status and send data frames including control commands.

[0017] In one embodiment of the present invention, a device node that is not used as a multiplexing device node is configured at the communication end of a network system composed of the master control device and multiple device nodes.

[0018] As described above, the industrial Ethernet communication method and system of the present invention have the following beneficial effects:

[0019] (1) The industrial Ethernet communication method of the present invention is applied to the application layer in the TCP / IP five-layer model without involving hardware layer modification. Taking advantage of the small amount of data in each communication in industrial communication, the data stream is reused to greatly improve the bandwidth utilization and effectively improve the communication performance of industrial Ethernet.

[0020] (2) The present invention has lower hardware requirements for communication equipment, which significantly reduces the implementation cost of communication equipment;

[0021] (3) The main control device of the present invention can identify the topology of the entire network based on the received data frames. Attached Figure Description

[0022] Figure 1The diagram shown is a schematic flowchart of an industrial Ethernet communication method according to an embodiment of the present invention.

[0023] Figure 2 The diagram shown is a schematic of the TCP / IP five-layer model in an industrial Ethernet communication method according to an embodiment of the present invention.

[0024] Figure 3 This diagram illustrates a communication method in an embodiment of the present invention, where a device node reports its status to a master device in an industrial Ethernet communication method.

[0025] Figure 4 This diagram illustrates a communication method in which a master control device sends control commands to a device node in an industrial Ethernet communication method according to an embodiment of the present invention.

[0026] Figure 5 The diagram shown is a schematic of an industrial Ethernet communication system according to an embodiment of the present invention.

[0027] Figure 6 The diagram shown is a structural schematic of a device node in an industrial Ethernet communication system according to an embodiment of the present invention.

[0028] Figure 7 This is a schematic diagram illustrating another structural design of a device node in an industrial Ethernet communication system according to one embodiment of the present invention.

[0029] Component designation explanation

[0030] 100 Industrial Ethernet Communication System

[0031] 110 Main Control Equipment

[0032] 11, 12, Equipment Nodes

[0033] Equipment nodes 21 and 22

[0034] Device nodes 1, 2, N, M

[0035] 101 First Network Card

[0036] 102 Second network card Detailed Implementation

[0037] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, unless otherwise specified, the following embodiments and features described therein can be combined with each other.

[0038] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0039] This embodiment provides an industrial Ethernet communication method and system based on TCP / UDP / IP transmission, using a general-purpose Ethernet controller, resulting in low hardware costs. Simultaneously, the data stream can be dynamically multiplexed. Multiplexing refers to using a single data stream: a device node initiates a data frame on the network, and this single data frame may pass through each device node sequentially. As it passes through each device node, data relevant to that current device node is either dropped or carried over, until the last device node. This single data stream significantly improves bandwidth utilization and substantially enhances the communication performance of industrial Ethernet.

[0040] The following will describe in detail the principles and implementation methods of the industrial Ethernet communication method and system of the present invention, so that those skilled in the art can understand the concept of the present invention without creative effort.

[0041] Figure 1 The diagram shown illustrates the principle flowchart of an industrial Ethernet communication method according to one embodiment of the present invention. Figure 1 As shown, this embodiment provides an industrial Ethernet communication method, which is applied to a network system consisting of a master control device 110 and multiple device nodes. The method is applied to the application layer of the TCP / IP five-layer model. The industrial Ethernet communication method includes the following steps S100 and S200.

[0042] Step S100: Establish a management channel and a working channel for data transmission; the management channel is used for the main control device and each device node to broadcast their respective device configuration information, and the working channel is used for each device node to report its own device status and for the main control device 110 to send control commands to each device node.

[0043] In step S200, when each device node reports its own status in the working channel, a data frame initiated by one device node passes through other device nodes in sequence and returns to the master control device 110. Each of the other device nodes, as multiplexing device nodes, adds its own data information to the data frame in sequence.

[0044] The industrial Ethernet communication method of this embodiment will be described in detail below.

[0045] Step S100: Establish a management channel and a working channel for data transmission; the management channel is used for the main control device and each device node to broadcast their respective device configuration information, and the working channel is used for each device node to report its own device status and for the main control device 110 to send control commands to each device node.

[0046] The industrial Ethernet communication method in this embodiment is applied to the application layer of the TCP / IP five-layer model, as shown in the schematic diagram of the TCP / IP five-layer model. Figure 2 As shown, the TCP / IP five-layer model from bottom to top

[0047] like Figure 1 As shown, in this embodiment, the communication protocol formed by the industrial Ethernet communication method is officially called the Ethernet Component Network protocol, or ECN protocol for short. The ECN protocol is based on the TCP / UDP / IP protocol and resides in the application layer of the TCP / IP five-layer model. Because the ECN protocol is located in the application layer of the TCP / IP five-layer model, it does not involve hardware layer modifications, resulting in lower hardware requirements for all devices and ultimately lower implementation costs.

[0048] In this embodiment, a management channel and a working channel are established for data transmission. The management channel is used for the main control device and each device node to broadcast their respective device configuration information. The working channel is used for each device node to report its own device status and for the main control device 110 to send control commands to each device node.

[0049] In this embodiment, the ECN protocol runs through TCP / UDP port 17731. There are two port addresses: one is used to manage the device, namely the Manager Channel (MCHAN), such as using the multicast address "228.0.0.1"; the other is used for work scheduling and status reporting, namely the Work Channel (WCHAN), such as using the multicast address "239.250.236.1".

[0050] Specifically, in this embodiment, the management channel for broadcasting device configuration information to the main control device and each device node includes: after establishing a network connection, the main control device 110 and each device node respectively send heartbeat packets to a fixed multicast address; wherein, the heartbeat of each device node contains the hardware configuration information of the device; after receiving the heartbeat packet of the device node, the main control device 110 sends a unicast packet to the corresponding device node, and the unicast packet is used to configure the parameters of the device node.

[0051] In other words, in this embodiment, the management channel is used in the same way as ordinary application layer protocols, employing common multicast and unicast technologies. After the master control device 110 and device nodes connect to the network, they both send their own heartbeat packets to a fixed multicast address. The heartbeat of a device node contains information such as the device's hardware configuration. Simultaneously, the master control device 110 can also be used to configure the parameters of the device nodes. After collecting the heartbeat packets from the device nodes, the master control device 110 sends unicast packets to the corresponding device nodes to configure their parameters. The working channel is used by each device node to report its own status and by the master control device 110 to send control commands to the device nodes.

[0052] In step S200, when each device node reports its own status in the working channel, a data frame initiated by one device node passes through other device nodes in sequence and returns to the master control device 110. Each of the other device nodes, as multiplexing device nodes, adds its own data information to the data frame in sequence.

[0053] Figure 3 This diagram illustrates a communication method in an industrial Ethernet communication system according to an embodiment of the present invention, where a device node reports its status to a master control device 110. Specifically, in this embodiment, as shown... Figure 3 As shown, in the working channel, when each of the device nodes (device node 1, device node 2, ..., device node N) reports the status of its own device, the data frame initiated by one of the device nodes (e.g., device node N) passes through the other device nodes (device node 1, device node 2, ...) in sequence and returns to the master control device 110. The other device nodes, as multiplexing device nodes, add the data information of the device itself to the data frame in sequence.

[0054] Industrial communication is characterized by its small data volume, primarily consisting of digital and analog signals. Due to this characteristic, the working channel can utilize multiplexed data streams to improve bandwidth utilization. This means that the transmitted data packets are multiplexed by multiple device nodes. Multiplexing refers to using a single data stream: one device node initiates a data frame on the network, and this single data frame may pass through each device node sequentially. As it passes through each device node, data relevant to that node is either dropped or carried over until the last device node. Therefore, the industrial Ethernet communication method in this embodiment leverages the small data volume of each communication in industrial communication, significantly improving bandwidth utilization through data stream multiplexing.

[0055] Specifically, such as Figure 3As shown, when reporting device status, one device node initiates a data frame. This data frame passes through each device node in turn, and each device node modifies the data frame in turn, that is, it adds its own data to the available byte stream of the data frame. Finally, it returns to the master control device 110. In this way, a data frame can report the information of multiple device nodes, without each device node needing to send a separate data frame to the master control device 110. This is data stream multiplexing, which greatly improves bandwidth utilization.

[0056] In this embodiment, for a device node that is not used as a multiplexing device node, the device node initiates a new data frame to report the status of the device itself.

[0057] In this embodiment, if a device node's hardware does not support multiplexing, meaning this device node may not be able to receive the data frame, or although it may be able to receive it, it may choose not to receive the data frame due to insufficient hardware performance. In this case, it needs to initiate a separate data frame when reporting its device status. Therefore, the ECN protocol in this embodiment has the characteristics of dynamic multiplexing and hardware compatibility.

[0058] Figure 4 This diagram illustrates a communication method in which a master control device 110 sends control commands to device nodes in an industrial Ethernet communication method according to an embodiment of the present invention. In this embodiment, as... Figure 4 As shown, when the master control device 110 sends control commands to each of the device nodes (device node 1, device node 2, ..., device node N), the data frame sent contains control commands for multiple device nodes. The control commands flow through each device node in sequence, and each device node that flows through the commands obtains the corresponding control commands in sequence.

[0059] In this embodiment, when the master control device 110 sends a control command, it also combines control commands for multiple device nodes (device node 1, device node 2, ..., device node N) in a data frame. The control command passes through each device node in sequence. When it passes through a device node, the corresponding device node obtains its own data, thus receiving the control command for this device node.

[0060] For this downlink data stream, each device node must be able to receive and process data frames. Downlink data stream functionality is a common application-layer network protocol function.

[0061] In this embodiment, the header of the data frame includes an opcode, which is used to indicate whether the data frame is a data frame in which each device node reports its own status to the master control device 110 or a data frame in which the master control device 110 sends control commands to each device node.

[0062] In other words, the header of the ECN protocol in this embodiment defines an opcode using several bytes. The information in this opcode indicates whether a data stream is uplink or downlink, whether it is a control stream or a status stream, whether it is multiplexed or single-use, etc. When a device node in this path receives a data stream, it can know whether it is an uplink data stream reporting status or a downlink data stream receiving control commands, and also know whether this data stream can be multiplexed, etc.

[0063] In this embodiment, the data frame includes a data record segment for recording the data length of the data information added by each device node. When each device node receives the data frame, it detects the current data length of the data record segment after adding its own data information. If the current data length is less than or equal to a data length threshold, it is used as a reused device node. If the current data length is greater than the data length threshold, it is not used as a reused device node and does not add its own data information to the data frame.

[0064] Ethernet frames must be less than 1500 bytes long. This is determined by the physical characteristics of Ethernet, and this 1500-byte length is called the link layer's MTU (Maximum Transmission Unit). If the length exceeds 1500 bytes, the IP layer needs to reassemble the datagrams, which reduces communication efficiency. Therefore, multiplexing should avoid exceeding 1500 bytes. The ECN protocol's data record segment records the data length of each node (when each node appends its own data, it appends the length and other information of this data to the beginning of this segment). Multiplexing is possible when the length is less than 1500 bytes; otherwise, it is not possible, and the device node along the path needs to initiate a new data frame.

[0065] When a device node reports its device status, if a passing device node finds that the length exceeds 1500 characters after adding its own status information, it will not reuse the data frame. Although it will not reuse the data frame, it will modify the data frame passed through.

[0066] In this embodiment, the header of the data frame also includes bytes representing the number of multiplexed device nodes (nvalid), bytes representing the number of device nodes to be multiplexed (npending), and bytes representing the number of device nodes that do not report their own status (nbypass). That is, in this embodiment, the header of the ECN protocol has three bytes: nvalid, npending, and nbypass, which represent the number of multiplexed device nodes, the number of nodes not being multiplexed and waiting to be sent, and the number of nodes that do not have a status to report, respectively.

[0067] When a device node receives a data frame, it modifies the corresponding number in the byte for the number of multiplexed device nodes, the byte for the number of device nodes to be multiplexed, or the byte for the number of device nodes that do not report their own status.

[0068] Specifically, each device node needs to modify one of these three bytes when passing through the data stream. If the data stream needs to be reused, modify nvalid and add 1 to the original value. If the total length of the data stream in the path plus the length of the data to be sent by this device node exceeds 1500 bytes, then it is not reused, but the npending byte needs to be modified and added 1 to the original value. If the device node in the path does not need to report its status, then modify nbypass and add 1 to the original value.

[0069] In this embodiment, the master control device 110 determines the distance between itself and the device node that initiated the data frame based on the sum of the corresponding numbers in the multiplexing device node number byte, the number of device nodes to be multiplexed byte, and the number of device nodes that do not report their own status; the master control device 110 determines the communication network topology formed by each device node based on the distance between itself and the device node that initiated the data frame.

[0070] When the data frame passes through each device node and finally returns to the master control device 110, the master control device 110 can determine the distance between the device node that first initiated the data frame and the master control device 110 based on the sum of three data points: the number of multiplexed device nodes (nvalid), the number of device nodes to be multiplexed (npending), and the number of device nodes that do not report their own status (nbypass)). For example, if the sum of the three numbers is 7, it means that there are 6 device nodes between the device node that initially initiated the data frame and the master control device 110. Similarly, each device node will have the opportunity to initiate a data frame, thus allowing the master control device 110 to know the topology of all device nodes. Therefore, in this embodiment, the master control device 110 can identify the topology of the entire network based on the received data frames.

[0071] This embodiment also provides an industrial Ethernet communication system 100. Figure 5 The diagram shown is a schematic of an industrial Ethernet communication system 100 according to one embodiment of the present invention. Figure 5As shown, in this embodiment, the industrial Ethernet communication system 100 includes: a master control device 110 and multiple device nodes (device node 11, device node 12, ..., device node N, device node 21, device node 22, ..., device node M); the master control device 110 and the multiple device nodes communicate using the industrial Ethernet communication method described above. The industrial Ethernet communication method has been described in detail above and will not be repeated here. Figure 6 This is a schematic diagram illustrating the structure of a device node in an industrial Ethernet communication system 100 according to an embodiment of the present invention. Figure 6 As shown, the device node, which serves as a multiplexing device node, is configured with a first network interface card (NIC) 101 and a second NIC 102; the first NIC 101 is used to receive data frames including control commands and initiate data frames, and the second NIC 102 is used to receive data frames reporting the device's own status and send data frames including control commands.

[0072] Figure 7 This is a schematic diagram illustrating another structural configuration of a device node in an industrial Ethernet communication system 100 according to one embodiment of the present invention. Figure 7 As shown, a device node that is not used as a multiplexing device node is only configured with a first network interface card (NIC) 101 to receive data frames including control commands and initiate data frames. Without a second NIC 102, it cannot receive the uplink device status stream, meaning it does not support the multiplexing of uplink data frames. Device nodes without a second NIC 102 can only be placed at the end of the network topology, thus not affecting the downlink multiplexing of control command streams.

[0073] In this embodiment, the device nodes that are not used as multiplexing device nodes are configured at the communication end of the network system composed of the main control device 110 and multiple device nodes.

[0074] In summary, the industrial Ethernet communication method of this invention is applied to the application layer of the TCP / IP five-layer model without involving hardware layer modifications. Utilizing the characteristic of small data volumes in industrial communication, data stream multiplexing significantly improves bandwidth utilization and effectively enhances the communication performance of industrial Ethernet. This invention also places lower hardware requirements on communication equipment, significantly reducing implementation costs. Furthermore, the main control device 110 can identify the entire network topology based on received data frames. Therefore, this invention effectively overcomes the various shortcomings of existing technologies and possesses high industrial applicability.

[0075] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. An industrial Ethernet communication method, characterized in that, The method is applied to a network system comprising a master control device and multiple device nodes, and is applied to the application layer of the TCP / IP five-layer model. The method includes: A management channel and a working channel are established for data transmission; the management channel is used for the main control device and each device node to broadcast their respective device configuration information, and the working channel is used for each device node to report its own status and for the main control device to send control commands to each device node. In the working channel, when each device node reports its own status, a data frame initiated by one device node passes through other device nodes in sequence and returns to the master control device. Each of the other device nodes, as multiplexing device nodes, adds its own data information to the data frame in sequence. The data frame contains a data record segment for recording the data length of the data information added by each device node. When each device node receives the data frame, it detects the current data length of the data record segment after adding its own data information. If the current data length is less than or equal to a data length threshold, it is used as a reused device node. If the current data length is greater than the data length threshold, it is not used as a reused device node and does not add its own data information to the data frame.

2. The industrial Ethernet communication method according to claim 1, characterized in that, The management channel is used by the main control device and each device node to broadcast their respective device configuration information, including: After establishing a network connection, the master control device and each of the device nodes send heartbeat packets to a fixed multicast address; wherein, the heartbeat of each device node contains the hardware configuration information of the device; After receiving the heartbeat packet from the device node, the master control device sends a unicast packet to the corresponding device node. The unicast packet is used to configure the parameters of the device node.

3. The industrial Ethernet communication method according to claim 1, characterized in that, When the master control device sends control commands to each of the device nodes, the data frame sent contains control commands for multiple device nodes. The control commands flow through each device node in sequence, and each device node receives the corresponding control command in sequence.

4. The industrial Ethernet communication method according to claim 1 or 3, characterized in that, The header of the data frame contains an opcode, which indicates whether the data frame is a data frame from each device node to the master control device reporting the status of the device itself or a data frame from the master control device to each device node sending a control command.

5. The industrial Ethernet communication method according to claim 1, characterized in that, For device nodes that are not used as reused device nodes, the device node initiates a new data frame to report the status of the device itself.

6. The industrial Ethernet communication method according to claim 1 or 5, characterized in that, The header of the data frame also includes bytes for the number of multiplexed device nodes, bytes for the number of device nodes to be multiplexed, and bytes for the number of device nodes that do not report their own status. When a device node receives the data frame, it modifies the corresponding number in the byte for the number of multiplexed device nodes, the byte for the number of device nodes to be multiplexed, or the byte for the number of device nodes that do not report their own status.

7. The industrial Ethernet communication method according to claim 6, characterized in that, The master control device determines the distance between itself and the device node that initiated the data frame based on the sum of the corresponding numbers in the multiplexing device node count byte, the number of device nodes to be multiplexed byte, and the number of device nodes that do not report their own status byte; the master control device determines the communication network topology formed by each device node based on the distance between itself and the device node that initiated the data frame.

8. An industrial Ethernet communication system, characterized in that, include: A main control device and multiple device nodes; the main control device and multiple device nodes communicate using the industrial Ethernet communication method as described in any one of claims 1 to 7. The device node, which serves as a multiplexing device node, is configured with at least a first network interface card (NIC) and a second NIC. The first NIC is used to receive data frames including control commands and initiate data frames reporting the device's own status. The second NIC is used to receive data frames reporting the device's own status and send data frames including control commands.

9. The industrial Ethernet communication system according to claim 8, characterized in that, Device nodes that are not used as multiplexing device nodes are configured at the communication end of a network system consisting of the main control device and multiple device nodes.

Images