A protocol conversion gateway system and a protocol conversion method

Abstract

This application relates to a protocol conversion gateway system, which includes a guide rail, two buckles, and a protocol conversion gateway unit. The protocol conversion gateway unit includes a power supply, a first protocol gateway, a second protocol gateway, and a terminal cover plate that are sequentially installed on the guide rail. This application also relates to a protocol conversion method for a protocol conversion gateway system, including: gateway initialization and self-negotiation for master-slave interaction, data topology negotiation, and protocol communication conversion. Through the above design, this application solves the problems of chaotic data structure, abnormal data high-low bit order, and difficult screening of service data validity when users use the protocol conversion gateway. Through the implementation of custom logic master-slave and a unified conversion communication interface, free combination between different protocol gateways is achieved, and the protocol free combination function of the plug-in type protocol conversion gateway is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of gateway devices, and in particular, to a protocol conversion gateway system and a protocol conversion method. Background Art

[0002] A protocol conversion gateway is a product that converts one industrial protocol into another.

[0003] The products on the market are all integrated protocol conversion gateways. An integrated protocol conversion gateway can only support a fixed two protocols at a time, such as EtherCAT to EtherCAT. If EtherCAT needs to be converted to another protocol, a new gateway is required. In this case, the integrated protocol conversion gateway has great limitations in use and high replacement costs.

[0004] Therefore, there are defects in the prior art and it needs to be improved and developed. Summary of the Invention

[0005] Embodiments of the present application provide a protocol conversion gateway system and a protocol conversion method, which are used to solve the technical problems that the integrated protocol conversion gateway in the prior art supports few and single protocols in use, resulting in great limitations in use and high replacement costs.

[0006] Embodiments of the present application provide a protocol conversion method for a protocol conversion gateway system, including:

[0007] S1021: Initialize the gateway communication port driver, set RS485 communication, and reset the parameters of the baud rate, stop bit, and data format of the communication port;

[0008] S1022: Initialize the master-slave detection pin, perform pin polarity judgment, and the one with a high-level judgment result is the logical master station, and the one with a low-level detection result is the logical slave station, so as to confirm the logical master and slave machines during RS485 communication;

[0009] S1023: Read the communication data topology. After the logical master-slave detection is completed, both the logical host and the logical slave read the communication data topology from their respective FLASH sectors. The logical master station initiates a comparison to judge the data mapping relationship between the logical master and slave. If the communication data topology comparison is consistent, the mapping relationship between the logical master and slave is confirmed; if the communication data topology comparison is inconsistent, the device mapping with a non-empty communication data topology comparison is used as the standard; if both communication data topology comparisons are non-empty, the logical host mapping is used as the standard;

[0010] S1024: Calculate the data topology length. Through the communication data topology, the first protocol gateway and the second protocol gateway respectively calculate the protocol exchange data length generated by the data topology;

[0011] S1025: Logic master-slave protocol stack registration and its driver initialization. After initialization, the first protocol gateway and the second protocol gateway wait for the protocol master station to initiate the interaction of service data and business data. Among them, the service data is used for gateway feature modification, communication data topology modification, and parameter modification; the business data includes protocol conversion services; the business data of the protocol A master station is transmitted to the logical master request buffer of the first protocol gateway through downlink data. The first protocol gateway sends this data to the business data uplink data buffer of the second protocol gateway. The second protocol gateway sends the business data to the protocol B master station through uplink data. The business data of the protocol B master station is transmitted to the logical slave response buffer of the second protocol gateway through downlink data. The second protocol gateway sends this data to the business data uplink data buffer of the first protocol gateway. The first protocol gateway sends the business data to the protocol A master station through uplink data, thus realizing the two-way data conversion interaction between the protocol A master station and the protocol B master station.

[0012] S104: Data topology negotiation;

[0013] S106: Protocol communication conversion.

[0014] Further, the method for the first protocol gateway and the second protocol gateway to calculate the protocol exchange data length generated by the data topology is: calculate in a byte-aligned manner, and the calculation unit of the final data length is a byte.

[0015] Further, the method for data topology negotiation includes: the logical slave station re-registers the protocol stack. If the data types in the data topology negotiation cannot be matched, data types with the same number of occupied data bits are used for replacement to unify the process data length during data conversion.

[0016] Further, the data types in the data topology negotiation match according to the data topology length, and the data topology alignment method is byte alignment.

[0017] Further, the method for protocol communication conversion includes: after establishing business data communication between the protocol A master station and the first protocol gateway and between the protocol B master station and the second protocol gateway, the first protocol gateway and the second protocol gateway perform data interaction through the RS485 bus. When each protocol gateway performs business data interaction, it judges the communication status of each protocol in real time through the network diagnosis interface and the function access interface. If a communication status exception occurs, the gateway module of each protocol gateway switches the unidirectional protocol communication status to error and performs recovery processing on the communication exception status according to the user configuration.

[0018] Further, the recovery processing method at least includes one of retaining the last normal interaction data in the data buffer and clearing the data buffer, and when processing the data topology, the gateway modules of the first protocol gateway and the second protocol gateway perform abnormal operations on each topology node data, and the abnormal operation method at least includes one of endian switching and filling of abnormal data.

[0019] Further, the protocol conversion gateway system adopted by the protocol conversion method for a protocol conversion gateway system includes a guide rail, two buckles, and a protocol conversion gateway unit. The two buckles are connected to the guide rail, and the protocol conversion gateway unit is clamped between the two buckles. Its characteristics are as follows:

[0020] The protocol conversion gateway unit includes a power supply, a first protocol gateway, a second protocol gateway, and a terminal cover plate that are sequentially installed on the guide rail. RS485 communication lines are connected between the first protocol gateway, the second protocol gateway, and the terminal cover plate; the first protocol gateway is electrically connected to the protocol A master station wiring terminal, and the second protocol gateway is electrically connected to the protocol B master station wiring terminal; a terminal resistor is connected in series between the "A+" signal line and the "B-" signal line on the RS485 communication line on the terminal cover plate, and a pull-down resistor is connected in series on the GND signal line on the terminal cover plate.

[0021] Further, the first protocol gateway at least supports one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol, and the second protocol gateway at least supports one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol.

[0022] Further, the first protocol gateway and the second protocol gateway are of a plug-in structure.

[0023] Beneficial effects:

[0024] As can be seen from the above technical solutions, the present invention provides a protocol conversion gateway system. By making the first protocol gateway and the second protocol gateway into plug-in gateways and connecting the first protocol gateway and the second protocol gateway to the guide rail by snap fasteners, the conversion between different protocols is realized. It can achieve the mutual conversion between EtherCAT protocol, EtherNetIP protocol, PROFINET protocol and CC-Link protocol. The plug-in design reduces the product replacement cost, expands the application scope of the protocol conversion gateway product, and improves the conversion efficiency. The present invention also provides a protocol conversion method. By gateway initialization and data negotiation, it solves the problems of chaotic data structure, abnormal high and low bit order of data, and great difficulty in screening the validity of service data when users use the protocol conversion gateway. Through the implementation of custom logic master-slave and unified conversion communication interfaces, the free combination between different protocol gateways is realized, and the protocol free combination function of the plug-in protocol conversion gateway is achieved.

[0025] It should be understood that all combinations of the foregoing concepts and additional concepts described in greater detail below can be regarded as part of the inventive subject matter of the present disclosure as long as such concepts do not conflict with each other.

[0026] The foregoing and other aspects, embodiments and features of the teachings of the present invention can be more fully understood from the following description taken in conjunction with the accompanying drawings. Other additional aspects of the present invention, such as features and / or beneficial effects of exemplary embodiments, will be apparent in the following description or will be learned through practice of the specific embodiments according to the teachings of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The drawings are not drawn to scale with respect to true reference objects. In the drawings, each identical or nearly identical component shown in various figures may be represented by the same reference numeral. For clarity, not every component is labeled in each figure. Now, embodiments of various aspects of the present invention will be described by way of example and with reference to the drawings, wherein:

[0028] Figure 1 is a schematic structural diagram of the protocol conversion gateway system provided by an embodiment of the present application.

[0029] Figure 2 is a flowchart of data topology negotiation provided by an embodiment of the present application.

[0030] Figure 3 is a flowchart of gateway initialization provided by an embodiment of the present application.

[0031] Description of the reference numerals in the drawings:

[0032] Power supply 1; First protocol gateway 2; Second protocol gateway 3; Terminal cover plate 4; Protocol A master station wiring terminal 5; Protocol B master station wiring terminal 6. Detailed implementation manners

[0033] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the described embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. Unless otherwise defined, the technical terms or scientific terms used herein shall have the ordinary meanings as understood by those of ordinary skill in the art to which the present invention pertains.

[0034] The terms "first", "second" and similar terms used in the specification and claims of this patent application for the present invention do not denote any order, quantity or importance, but are only used to distinguish different components. Similarly, unless the context clearly indicates otherwise, singular forms such as "a", "an" or "the" and similar terms do not denote a limitation of quantity, but mean that there is at least one. The terms "comprising" or "including" and similar terms mean that the elements or items appearing before "comprising" or "including" cover the features, wholes, steps, operations, elements and / or components listed after "comprising" or "including", and do not exclude the existence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations. The terms "upper", "lower", "left", "right", etc. are only used to indicate relative positional relationships, and when the absolute position of the object being described changes, the relative positional relationship may also change accordingly.

[0035] Conventional protocol conversion gateway products are all integrated protocol conversion gateways. An integrated protocol conversion gateway can only support a fixed two protocols each time, such as EtherCAT to EtherCAT. If EtherCAT needs to be converted to other protocols, a new gateway is required. In this case, the integrated protocol conversion gateway has great limitations in use and high replacement costs.

[0036] In view of this, the present invention conceives a protocol conversion method for a protocol conversion gateway system. The protocol conversion gateway system includes a guide rail, two buckles, and a protocol conversion gateway unit. The two buckles are connected to the guide rail, and the protocol conversion gateway unit is clamped between the two buckles. The protocol conversion gateway unit includes a power supply 1, a first protocol gateway 2, a second protocol gateway 3, and a terminal cover plate that are sequentially installed on the guide rail. RS485 communication lines are connected between the first protocol gateway 2, the second protocol gateway 3, and the terminal cover plate; the first protocol gateway 2 is electrically connected to the protocol A master station terminal 5, and the second protocol gateway 3 is electrically connected to the protocol B master station terminal 6; a terminal resistor is connected in series between the "A+" signal line and the "B-" signal line on the RS485 communication line located on the terminal cover plate, and a pull-down resistor is connected in series on the GND signal line located on the terminal cover plate.

[0037] Referring to Figure 1 , the protocol conversion function is implemented by software in the first protocol gateway 2 and the second protocol gateway 3. The main control chip of the first protocol gateway 2 converts protocol A into the unified standard protocol Xbus, and transmits the converted protocol frame to the second protocol gateway 3 through the backplane bus. The second protocol gateway 3 then converts the protocol frame in Xbus into protocol B through the main control chip. The conversion between protocol A and Xbus, and between protocol B and Xbus is bidirectional and is implemented inside the single product without the need for additional interaction devices.

[0038] The first protocol gateway 2 supports at least one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol. The second protocol gateway 3 supports at least one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol, and the protocols supported by the first protocol gateway 2 and the second protocol gateway 3 can be the same or different. When they are the same, it completes the connection of the same protocol.

[0039] In some embodiments, the first protocol gateway 2 selects one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol, and the second protocol gateway 3 selects one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol. Therefore, the following conversion protocols can be obtained: the mutual conversion between the EtherCAT protocol and EtherNetIP, the mutual conversion between the EtherCAT protocol and PROFINET protocol, the mutual conversion between the EtherCAT protocol and CC-Link protocol, the mutual conversion between the EtherNetIP protocol and PROFINET protocol, the mutual conversion between the EtherNetIP protocol and CC-Link protocol, and the mutual conversion between the PROFINET protocol and CC-Link protocol.

[0040] The first protocol gateway 2 and the second protocol gateway 3 are in an insert - type structure.

[0041] The insert - type gateway adopts an insert - type structure, which is easy to use, maintain and expand. In terms of functions, in addition to the basic protocol conversion function, it can realize the free combination and use of each protocol conversion module, that is, plug - and - play. It can be extended to support a variety of insert - type IOs and a variety of communication status diagnosis functions.

[0042] The present invention conceives a protocol conversion method for a protocol conversion gateway system, including:

[0043] S102: Gateway initialization and self - negotiation for master - slave interaction.

[0044] S104: Data topology negotiation.

[0045] S106: Protocol communication conversion.

[0046] Referring to Figures 2 to 3 , the method for gateway initialization and self - negotiation for master - slave interaction includes:

[0047] S1021: Initialize the communication port driver of the gateway, set RS485 communication, and reset the parameters of the baud rate, stop bit and data format of the communication port.

[0048] Since each gateway single product of the insert - type gateway is used as a separate protocol conversion module and needs to be assembled into a kit to achieve the conversion from one protocol to another protocol, each gateway single product needs to provide a gateway standard communication interface protocol. The initialization of the communication port driver is mainly to set parameters such as the baud rate, stop bit, and data format of the communication port to ensure the communication of the communication interface. The gateway standard communication interface protocol of the embodiment of the present application is based on RS485 as the hardware. Since the RS485 communication method is half - duplex, in order to ensure the order of communication and avoid communication blocking, by introducing peripherals, the logical master - slave relationship of RS485 communication is defined.

[0049] S1022: Initialize the master - slave detection pin, perform pin polarity judgment, the one with the judgment result of high level is the logical master station, and the one with the detection result of low level is the logical slave station, so as to confirm the logical master - slave machines during RS485 communication.

[0050] The master-slave detection peripheral depends on the protocol conversion gateway system. There is a terminal cover plate 4 in the protocol conversion gateway system, which includes an RS485 communication line terminal resistor and a pull-down resistor for the master-slave detection peripheral. The gateway module of the first protocol gateway 2 or the second protocol gateway 3 can directly connect to the pull-down resistor of the detection peripheral. When the peripheral is initialized, it is configured as a default pull-up. Due to the existence of the pull-down resistor, the pull-up of the master-slave detection peripheral of the logical slave is invalid. Therefore, when performing pin polarity detection, the master-slave detection peripheral of the logical master station is detected as high level, and the master-slave detection peripheral of the logical slave station is detected as low level, thereby confirming the logical master and slave machines during RS485 communication. The terminal resistor is connected in series between the A+ and B- signal lines of RS485, and the pull-down resistor of the logical master-slave detection peripheral is connected in series to the GND signal.

[0051] S1023: Read the communication data topology. After the logical master-slave detection is completed, both the logical master and the logical slave read the communication data topology from their respective FLASH sectors. The logical master station initiates a comparison to determine the data mapping relationship between the logical master and slave. If the communication data topology comparison is consistent, the mapping relationship between the logical master and slave is confirmed; if the communication data topology comparison is inconsistent, the device mapping with non-empty communication data topology is used as the standard; if both communication data topologies are non-empty, the logical master mapping is used as the standard.

[0052] The communication data topology is default empty at the factory and is stored in the main control FLASH sectors of each gateway module. After the logical master-slave detection is completed, both the host and the slave read the communication data topology from their respective FLASH sectors. The master station initiates a comparison. Only when the communication data topology comparison is consistent can the data mapping relationship between the master and slave be confirmed. When the comparison is inconsistent, the topology that is not empty is used as the standard. If both are not empty, the logical master mapping is used as the standard. Based on this criterion, automatic communication data topology mapping can be achieved.

[0053] S1024: Calculate the data topology length. Through the communication data topology, the first protocol gateway 2 and the second protocol gateway 3 respectively calculate the length of the protocol exchange data generated by the data topology.

[0054] S1025: Register the logical master-slave protocol stack and initialize its driver. After initialization, the first protocol gateway 2 and the second protocol gateway 3 wait for the protocol master station to initiate the interaction of service data and business data. Among them, the service data is used for gateway feature modification, communication data topology modification, and parameter modification; the business data includes protocol conversion services; the business data of the protocol A master station is transmitted to the logical master request buffer of the first protocol gateway 2 through the downlink data. The first protocol gateway 2 sends this data to the business data uplink data buffer of the second protocol gateway 3. The second protocol gateway 3 sends the business data to the protocol B master station through the uplink data. The business data of the protocol B master station is transmitted to the logical slave response buffer of the second protocol gateway 3 through the downlink data. The second protocol gateway 3 sends this data to the business data uplink data buffer of the first protocol gateway 2. The first protocol gateway 2 sends the business data to the protocol A master station through the uplink data, thus realizing the two-way data conversion interaction between the protocol A master station and the protocol B master station.

[0055] The method for the first protocol gateway 2 and the second protocol gateway 3 to calculate the protocol exchange data length generated by the data topology is as follows: calculate by byte alignment, and the calculation unit of the final data length is byte.

[0056] The method of data topology negotiation includes: the logical slave re-registers the protocol stack. If the data types in the data topology negotiation cannot be matched, then use the data types with the same occupied data bits for replacement to unify the process data length during data conversion.

[0057] The conditions for triggering data topology negotiation may occur both before and during the establishment of protocol communication. Since the initialization and registration processes of each protocol are different, generally after triggering, the logical master does not need to re-register the protocol stack, and only the logical slave needs to re-register the protocol stack. For some protocols, the protocol stack needs to be re-registered. Each gateway module executes according to the protocol characteristics in terms of whether to register and the registration process.

[0058] During the process of performing data topology negotiation, the data types supported by two different protocols are not completely the same, and the data types supported by the protocol master station are not completely the same. Therefore, during the process of data topology negotiation, it is inevitable to encounter the situation where the data types cannot be matched. In the case where the data types cannot be matched, then use the data types with the same occupied data bits for replacement to finally unify the process data length during data conversion.

[0059] In the data topology negotiation, the data types match according to the data topology length, and the data topology alignment method is byte alignment.

[0060] Through communication data topology, each gateway module independently calculates the protocol exchange data length generated by the data topology. When calculating the BOOL data topology length, byte alignment is used for calculation. The calculation unit of the final data length is bytes.

[0061] The data topology has the Array feature, and the device supports arrays of various data types. The number of elements in the array can be set by the user. The data type table is shown in Table 1. Some data types support big-endian and byte swapping to solve the problem of inconsistent big-endian that may occur during the conversion of different industrial communication protocols.

[0062] Table 1: Data Type Table

[0063]

[0064] During the data topology negotiation process, the following principles are followed: the data topology length matching has the highest priority, the data topology alignment method is byte alignment, logical slave data topology client execution configuration mapping is allowed under the condition of topology length matching, and the data topology priority of the logical master gateway module is higher than that of the logical slave gateway module.

[0065] The method of protocol communication conversion includes: after establishing service data communication between the protocol A master station and the first protocol gateway 2 and between the protocol B master station and the second protocol gateway 3, data interaction is carried out between the first protocol gateway 2 and the second protocol gateway 3 through the RS485 bus. When each protocol gateway conducts service data interaction, the communication status of each protocol is judged in real time through the network diagnosis interface and the function access interface. If a communication status exception occurs, the gateway module of each protocol gateway switches the unidirectional protocol communication status to error and performs recovery processing on the communication exception status according to the user configuration.

[0066] The recovery processing method includes at least one of maintaining the last normal interaction data in the data buffer and clearing the data buffer. When processing the data topology, the gateway modules of the first protocol gateway 2 and the second protocol gateway 3 perform abnormal operations on the data of each topology node. The abnormal operation methods include at least one of big-endian swapping and filling of abnormal data.

[0067] In summary, a protocol conversion gateway system provided by an embodiment of the present application realizes the conversion between different protocols by using the first protocol gateway and the second protocol gateway as plug-in gateways and connecting the first protocol gateway and the second protocol gateway to the guide rail by means of snap connections. It can achieve the mutual conversion between EtherCAT protocol, EtherNetIP protocol, PROFINET protocol and CC-Link protocol. The plug-in design reduces the product replacement cost, expands the application scope of the protocol conversion gateway product, and improves the conversion efficiency. The present invention also provides a protocol conversion method. By means of gateway initialization and data negotiation, it solves the problems of chaotic data structure, abnormal high and low order of data, and great difficulty in screening the validity of service data when users use the protocol conversion gateway. Through the implementation of custom logic master-slave and unified conversion communication interfaces, the free combination between different protocol gateways is realized, and the protocol free combination function of the plug-in protocol conversion gateway is achieved.

[0068] Although the present invention has been disclosed above with preferred embodiments, it is not intended to limit the present invention. Those with ordinary knowledge in the technical field to which the present invention pertains can make various modifications and refinements without departing from the spirit and scope of the present invention. Therefore, the protection scope of the present invention shall be subject to that defined by the claims.

Claims

1. A protocol conversion method for a protocol conversion gateway system, characterized in that, Including: S1021: Initialize the gateway communication port driver, set RS485 communication, and reset the parameters of the baud rate, stop bit, and data format of the communication port; S1022: Initialize the master-slave detection pin, perform pin polarity judgment. The one with a high-level judgment result is the logical master station, and the one with a low-level detection result is the logical slave station, so as to confirm the logical master and slave machines during RS485 communication; S1023: Read the communication data topology. After the logical master-slave detection is completed, both the logical master station and the logical slave station read the communication data topology from their respective FLASH sectors. The logical master station initiates a comparison to judge the data mapping relationship between the logical master and slave. If the communication data topology comparison is consistent, the mapping relationship between the logical master and slave is confirmed; if the communication data topology comparison is inconsistent, the device mapping with a non-empty communication data topology comparison is used as the standard; if both communication data topology comparisons are non-empty, the logical master station mapping is used as the standard; S1024: Calculate the data topology length. Through the communication data topology, the first protocol gateway and the second protocol gateway respectively calculate the protocol exchange data length generated by the data topology; S1025: Register the logical master-slave protocol stack and initialize its driver. After initialization, the first protocol gateway and the second protocol gateway wait for the protocol master station to initiate the interaction of service data and business data. Among them, the service data is used for gateway feature modification, communication data topology modification, and parameter modification; the business data includes protocol conversion services; the business data of the protocol A master station is transmitted to the logical master station request buffer of the first protocol gateway through downlink data. The first protocol gateway sends this data to the business data uplink data buffer of the second protocol gateway. The second protocol gateway sends the business data to the protocol B master station through uplink data. The business data of the protocol B master station is transmitted to the logical slave response buffer of the second protocol gateway through downlink data. The second protocol gateway sends this data to the business data uplink data buffer of the first protocol gateway. The first protocol gateway sends the business data to the protocol A master station through uplink data, thus realizing the two-way data conversion interaction between the protocol A master station and the protocol B master station; S104: Data topology negotiation; S106: Protocol communication conversion.

2. The protocol conversion method for a protocol conversion gateway system according to claim 1, characterized in that, The method for the first protocol gateway and the second protocol gateway to respectively calculate the protocol exchange data length generated by the data topology is: calculate in a byte-aligned manner, and the calculation unit of the final data length is bytes.

3. The protocol conversion method for a protocol conversion gateway system according to claim 1, characterized in that, The method for data topology negotiation includes: the logical slave station re-registers the protocol stack. If the data types in the data topology negotiation cannot be matched, data types with the same occupied data bits are used for replacement to unify the process data length during data conversion.

4. The protocol conversion method for a protocol conversion gateway system according to claim 3, characterized in that, The data types in the data topology negotiation are matched according to the data topology length, and the data topology alignment method is byte alignment.

5. The protocol conversion method for a protocol conversion gateway system according to claim 1, characterized in that, The method for protocol communication conversion includes: after establishing service data communication between the protocol A master station and the first protocol gateway, and between the protocol B master station and the second protocol gateway, data interaction is carried out between the first protocol gateway and the second protocol gateway through the RS485 bus. When each protocol gateway conducts service data interaction, the communication status of each protocol is judged in real time through the network diagnosis interface and the function access interface. If the communication status is abnormal, the gateway module of each protocol gateway switches the unidirectional protocol communication status to error, and performs recovery processing on the communication abnormal status according to user configuration.

6. The protocol conversion method for a protocol conversion gateway system according to claim 5, characterized in that, The recovery processing method at least includes one of maintaining the last normal interaction data in the data buffer and emptying the data buffer. And when processing the data topology, the gateway modules of the first protocol gateway and the second protocol gateway perform abnormal operations on the data of each topology node. The abnormal operation method at least includes one of endian conversion and filling of abnormal data.

7. The protocol conversion method for a protocol conversion gateway system according to claim 1, the protocol conversion gateway system adopted by the protocol conversion method for a protocol conversion gateway system includes a guide rail, two buckles and a protocol conversion gateway unit, the two buckles are connected to the guide rail, and the protocol conversion gateway unit is clamped between the two buckles, characterized in that, The protocol conversion gateway unit includes a power supply, a first protocol gateway, a second protocol gateway, and a terminal cover plate sequentially installed on the guide rail. RS485 communication lines are connected between the first protocol gateway, the second protocol gateway, and the terminal cover plate; the first protocol gateway is electrically connected to the protocol A master station terminal, and the second protocol gateway is electrically connected to the protocol B master station terminal; a terminal resistor is connected in series between the "A+" signal line and the "B-" signal line on the RS485 communication line located on the terminal cover plate, and a pull-down resistor is connected in series on the GND signal line located on the terminal cover plate.

8. The protocol conversion gateway system according to claim 7, characterized in that, The first protocol gateway supports at least one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol, and the second protocol gateway supports at least one of the EtherCAT protocol, EtherNetIP protocol, PROFINET protocol, and CC-Link protocol.

9. The protocol conversion gateway system according to any one of claims 7 to 8, characterized in that, The first protocol gateway and the second protocol gateway are of a plug-in structure.

Images