A multi-protocol communication method, apparatus and related equipment, and industrial automation system

By using the same configuration framework to generate communication configuration information in industrial automation systems and utilizing target communication modules that support multiple protocols, the problems of configuration complexity and high hardware costs when connecting different field devices are solved, achieving the effects of simplifying communication configuration and reducing costs.

CN123123483APending Publication Date: 2026-11-17SUPCON TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611606523.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-16
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In industrial automation systems, the increasing number of field devices and the access of field devices with different communication protocols leads to problems such as complex communication configuration and high hardware costs.

Method used

The same configuration framework is used to generate communication configuration information for multiple field devices, and multiple communication protocols are supported through the target communication module. The target communication protocol is determined based on the configuration information for data interaction.

Benefits of technology

It reduces the system configuration complexity and hardware cost when connecting different field devices corresponding to different communication protocols, and simplifies the communication configuration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123483A_ABST
    Figure CN123123483A_ABST
Patent Text Reader

Abstract

This application provides a multi-protocol communication method, apparatus, and related equipment and industrial automation system, relating to the field of industrial automation communication technology. The method includes: identifying a target field device among multiple field devices for data interaction, wherein the communication configuration information corresponding to each of the multiple field devices is generated by the same configuration framework; acquiring the communication configuration information of the target field device, which indicates the communication method between the target communication module and the target field device, and the target communication module supports multiple communication protocols; determining the target communication protocol corresponding to the target field device from the multiple communication protocols supported by the target communication module based on the communication configuration information; and exchanging data between the target communication module and the target field device according to the target communication protocol. This application reduces the system configuration complexity and hardware cost when different communication devices corresponding to different communication protocols are accessed by reusing the configuration framework and communication module.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of industrial automation communication technology, and in particular to a multi-protocol communication method, device and related equipment, and industrial automation system. Background Technology

[0002] In industrial automation systems, controllers exchange data with field devices to monitor and control the production process. As the types of field devices increase, the system needs to meet the communication requirements of different devices.

[0003] In related technologies, when field devices are connected to industrial automation systems, corresponding communication connections and parameter configurations need to be completed. When there are many types of communication devices, the communication connections and parameter configurations of different types of communication devices may also be different, leading to problems such as complex communication configuration and high system deployment costs. Summary of the Invention

[0004] This invention provides a multi-protocol communication method, apparatus, and related equipment and industrial automation system to reduce the system configuration complexity and hardware cost when different communication devices corresponding to different communication protocols are connected.

[0005] The embodiments of this application disclose the following technical solutions: In a first aspect, embodiments of this application provide a multi-protocol communication method, the method comprising: The target field device for data interaction is determined. The target field device is any one of a plurality of field devices. The communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework. Obtain the communication configuration information of the target field device. The communication configuration information of the target field device is used to indicate the communication method between the target communication module and the target field device. The same target communication module supports multiple communication protocols. Based on the communication configuration information, the target communication protocol corresponding to the target field device is determined from the multiple communication protocols supported by the target communication module; According to the target communication protocol, data is exchanged between the target communication module and the target field device.

[0006] In one possible implementation, the plurality of field devices includes a first type of device and a second type of device, wherein the communication protocol supported by the first type of device is different from the communication protocol supported by the second type of device, and the communication configuration information of the first type of device is generated in the following ways: Using the same configuration framework, the first type of devices are configured according to the description file corresponding to the first type of devices to obtain the communication configuration information of the first type of devices; The methods for generating communication configuration information for the second type of device include: Using the same configuration framework, the second type of device is configured according to the custom file corresponding to the second type of device to obtain the communication configuration information of the second type of device. The custom file is used to enable the same configuration framework to configure the second type of device in the same configuration method used when configuring the first type of device.

[0007] In one possible implementation, the method further includes: The communication configuration information of the target field device is written into the slave station table. The communication configuration information includes a device type identifier, which is used to characterize the type of target communication protocol corresponding to the target field device. The slave station table is used to manage the communication configuration information of different field devices corresponding to different communication protocols. The step of obtaining the communication configuration information of the target field device includes: Obtain the equipment type identifier corresponding to the target field equipment from the slave station table.

[0008] In one possible implementation, the multiple communication protocols include the PROFINET protocol and the HART-IP protocol.

[0009] In one possible implementation, the method further includes: The first operating state of the primary communication module and the second operating state of the backup communication module are determined. Both the primary communication module and the backup communication module are communication modules that support the multiple communication protocols. The primary communication module and the backup communication module are redundant to each other. When the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

[0010] In one possible implementation, the serial number range corresponding to the primary communication module and the serial number range corresponding to the backup communication module do not overlap. The step of exchanging data between the target communication module and the target field device according to the target communication protocol includes: When the target communication protocol is HART-IP and the target communication module is the backup communication module, data is exchanged between the backup communication module and the target field device according to the serial number range corresponding to the backup communication module.

[0011] Secondly, embodiments of this application disclose an industrial automation system, the system comprising a controller, a target communication module connected to the controller, and target field devices connected to the target communication module, wherein... The controller is configured to: determine the target field device for data interaction, wherein the target field device is any one of a plurality of field devices, and the communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework; acquire the communication configuration information of the target field device, which indicates the communication method between the target communication module and the target field device, wherein the same target communication module supports multiple communication protocols; determine the target communication protocol corresponding to the target field device from the plurality of communication protocols supported by the target communication module based on the communication configuration information; and exchange data between the target communication module and the target field device according to the target communication protocol.

[0012] In one possible implementation, the system further includes a backup communication module connected to the controller and a primary communication module connected to the controller. The backup communication module and the primary communication module are respectively connected to the target field device. The primary communication module and the backup communication module are redundant to each other. The target communication module is one of the primary communication module and the backup communication module. The controller is further configured to determine a first operating state of the primary communication module and a second operating state of the backup communication module, wherein both the primary communication module and the backup communication module are communication modules that support the multiple communication protocols; when the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

[0013] Thirdly, embodiments of this application provide a multi-protocol communication device, the device comprising: The determination module is used to determine the target field device for data interaction, wherein the target field device is any one of a plurality of field devices, and the communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework. The acquisition module is used to acquire the communication configuration information of the target field device. The communication configuration information of the target field device is used to indicate the communication method between the target communication module and the target field device. The same target communication module supports multiple communication protocols. The determining module is further configured to determine the target communication protocol corresponding to the target field device from the multiple communication protocols supported by the target communication module based on the communication configuration information; An interaction module is used to exchange data between the target communication module and the target field device according to the target communication protocol.

[0014] In one possible implementation, the plurality of field devices include a first type of device and a second type of device, wherein the communication protocol supported by the first type of device is different from the communication protocol supported by the second type of device, and the device further includes: a generation module; the generation module is used to configure the first type of device according to the description file corresponding to the first type of device through the same configuration framework to obtain the communication configuration information of the first type of device; The generation module is further configured to configure the second type of device according to the custom file corresponding to the second type of device through the same configuration framework to obtain the communication configuration information of the second type of device. The custom file is used to enable the same configuration framework to configure the second type of device in the same configuration method used when configuring the first type of device.

[0015] In one possible implementation, the device further includes: a writing module; The writing module is used to write the communication configuration information of the target field device into the slave table. The communication configuration information includes a device type identifier, which is used to characterize the type of the target communication protocol corresponding to the target field device. The slave table is used to manage the communication configuration information of different field devices corresponding to different communication protocols. The acquisition module is used to obtain the equipment type identifier corresponding to the target field equipment from the slave station table.

[0016] In one possible implementation, the multiple communication protocols include the PROFINET protocol and the HART-IP protocol.

[0017] In one possible implementation, the determining module is further configured to: determine a first operating state of the primary communication module and a second operating state of the backup communication module, wherein both the primary communication module and the backup communication module are communication modules that support the multiple communication protocols, and the primary communication module and the backup communication module are redundant to each other; When the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

[0018] In one possible implementation, the serial number range corresponding to the primary communication module and the serial number range corresponding to the backup communication module do not overlap, and the interaction module is used for: When the target communication protocol is HART-IP and the target communication module is the backup communication module, data is exchanged between the backup communication module and the target field device according to the serial number range corresponding to the backup communication module.

[0019] Fourthly, embodiments of this application provide a computing device, the device including a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is configured to execute the method described in any of the first aspects according to the instructions in the program code.

[0020] As can be seen from the above technical solution, this application first determines the target field device for data interaction, which is any one of multiple field devices, to clarify the field device targeted for subsequent communication configuration information acquisition and data interaction. The communication configuration information corresponding to multiple field devices is generated using the same configuration framework, enabling the communication configuration of multiple field devices to reuse the same configuration framework and reducing the need to use different configuration frameworks for configuration due to different communication protocols. Since the same target communication module supports multiple communication protocols, the communication configuration information of the target field device is further acquired, and based on this communication configuration information, the target communication protocol corresponding to the target field device is determined from the multiple communication protocols supported by the target communication module. Then, based on the target communication protocol, data is exchanged between the target communication module and the target field device, so that the communication configuration information generated using the same configuration framework can instruct the target communication module to use a target communication protocol that matches the target field device, thereby enabling the same target communication module to meet the communication needs of different field devices corresponding to different communication protocols. Therefore, by generating communication configuration information for multiple field devices through the same configuration framework, and using the communication configuration information of the target field device to connect the subsequent target communication protocol determination and data interaction, the complexity of communication configuration can be reduced by reusing the configuration framework, and the need to deploy communication modules separately due to different communication protocols can be reduced, thereby reducing the system configuration complexity and hardware cost when different field devices corresponding to different communication protocols are connected. Attached Figure Description

[0021] Figure 1 This application provides a schematic diagram of the structure of a multi-protocol communication system according to an embodiment of the present application. Figure 2 A flowchart illustrating a multi-protocol communication method provided in an embodiment of this application; Figure 3 This application provides a schematic diagram of the structure of an industrial automation system. Figure 4 This is a schematic diagram of another industrial automation system provided in an embodiment of this application; Figure 5 A schematic diagram of a multi-protocol communication device provided in this application; Figure 6This is a schematic diagram of the hardware structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0023] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate; this is merely a method of distinction used in describing objects with the same attributes in the embodiments of this application.

[0024] In this application's embodiments, "at least one" includes one or more, and "more than one" includes two or more. Unless the context clearly indicates otherwise, the terms "comprising" and "having" in this application's embodiments indicate an open-ended inclusion relationship. The technical features described in different embodiments can be combined with each other without conflict.

[0025] For ease of understanding and explanation, some of the technical terms mentioned in this application will be explained by example below.

[0026] A configuration framework can refer to the software framework in configuration software used to configure devices. It can provide the organization of device description information, configuration rules, and the generation of configuration data.

[0027] Communication configuration information refers to information used to configure communication between the communication module and field devices, and can be used to indicate the communication method between the communication module and field devices. In this embodiment, the communication configuration information may include device type identifier, data update time, communication timeout time, channel mapping information, etc. The device type identifier can be used to determine the communication protocol corresponding to the field device, enabling the communication module to use the appropriate communication protocol to interact with the field device.

[0028] Configuration software can refer to software tools used to configure and manage equipment in industrial automation systems. It can generate communication configuration information corresponding to the equipment based on the equipment description file and user configuration operations.

[0029] A description file can refer to a file used to describe equipment-related information, which may include equipment attributes, communication parameters, module configurations, or data mapping relationships, enabling configuration software to configure the corresponding equipment based on the description file. In this embodiment, the description file can be a general station description (GSD) file for PROFINET (Procedure for the Producing and Manufacturing Network) equipment. The configuration software can configure the PROFINET equipment based on the GSD file to generate corresponding communication configuration information.

[0030] A custom file refers to a device description file predefined according to the device's configuration requirements. In this embodiment, the custom file can be used to describe the communication configuration information of field devices that support communication protocols different from PROFINET.

[0031] The slave table can be a data structure used to store and manage the communication configuration information of field devices, and can be used to establish the association between field devices and their corresponding communication configuration information.

[0032] Switched redundancy (S2 redundancy) can be a redundancy protocol based on physical links, requiring field devices to have dual network cards and communicate with the master station through dual links.

[0033] R1 redundancy (redundant communication) can be a protocol stack-based redundancy protocol that requires field devices to support dual master station communication.

[0034] The Advanced Physical Layer (APL) is an Ethernet physical layer standard designed specifically for process automation, supporting intrinsically safe and long-distance communication.

[0035] Redundant communication refers to the use of additional communication paths or backup systems in industrial systems and network engineering to ensure the reliability and continuity of data transmission.

[0036] In industrial automation systems, controllers typically interact with field devices via communication modules to monitor and control the production process. When the connected field devices use different communication protocols, relevant technologies can configure communication modules corresponding to the respective protocols and complete the communication configuration of the field devices using appropriate configuration tools. However, deploying communication modules separately according to communication protocols increases the number of communication hardware components; completing the access and communication configuration separately for different types of field devices also increases the complexity of device configuration and management, resulting in high system configuration complexity and hardware costs when connecting different field devices corresponding to different communication protocols.

[0037] Based on this, this application provides a multi-protocol communication method. The method determines the target field device for data interaction, which is any one of multiple field devices, and the communication configuration information corresponding to each of the multiple field devices is generated using the same configuration framework; it acquires the communication configuration information of the target field device, which indicates the communication method between the target communication module and the target field device, wherein the same target communication module supports multiple communication protocols; based on the communication configuration information of the target field device, it determines the target communication protocol corresponding to the target field device from the multiple communication protocols supported by the target communication module; and it exchanges data between the target communication module and the target field device according to the target communication protocol.

[0038] In this way, the communication configuration information of multiple field devices is generated using the same configuration framework, which can reuse the processing functions provided by the configuration framework and reduce the need to use different configuration frameworks for configuration due to different communication protocols. Identifying the target field device and obtaining its corresponding communication configuration information allows subsequent communication protocol determination and data interaction to be performed on the field device to which data interaction is to be performed, and the communication configuration generated by the same configuration framework is connected with subsequent communication processing through the communication configuration information. Based on the communication configuration information, the target communication protocol is determined from the multiple communication protocols supported by the same target communication module, and the target communication protocol is used to interact with the target field device. This allows the same target communication module to meet the communication needs of different field devices corresponding to different communication protocols, reducing the need to deploy communication modules separately due to different communication protocols. Therefore, this application can reduce the system configuration complexity and hardware cost when different field devices corresponding to different communication protocols are connected.

[0039] See Figure 1 , Figure 1This diagram illustrates the structure of a multi-protocol communication system according to an embodiment of this application. The multi-protocol communication system 100 may include a controller 200, a target communication module 300, multiple switches 400, and multiple field devices 500. The controller 200 can establish communication connections with the target communication module 300 through network A and network B, respectively, and the target communication module 300 can establish communication connections with the multiple field devices 500 through the switches 400.

[0040] The target communication module 300 can be used to provide a communication channel between the controller 200 and the field device 500. The same target communication module 300 supports multiple communication protocols. For example, the multiple communication protocols may include the PROFINET protocol and the HART-IP (highway addressable remote transducer over internet protocol).

[0041] The switch 400 can be a network device with multiple communication ports, used to connect the target communication module 300 to multiple field devices 500, and to forward communication data between the target communication module 300 and the field devices 500. Through the switch 400, multiple field devices 500 can be connected to the same field communication network, enabling the target communication module 300 to interact with multiple field devices 500 through the network.

[0042] Field devices 500 can be field instruments or other devices in an industrial automation system, and different field devices 500 can support different communication protocols. For example, multiple field devices 500 may include field devices supporting the PROFINET protocol and field devices supporting the HART-IP protocol. The communication configuration information corresponding to each of the multiple field devices 500 can be generated using the same configuration framework. The communication configuration information corresponding to each field device 500 is used to indicate the communication method between the target communication module 300 and that field device 500.

[0043] The controller 200 can identify the target field device for data interaction, which can be any one of multiple field devices 500. The controller 200 can obtain the communication configuration information of the target field device, and based on this information, determine the target communication protocol corresponding to the target field device from the various communication protocols supported by the target communication module 300. Then, the controller 200 uses the target communication module 300 to interact with the target field device using the target communication protocol to achieve monitoring and control of the production process.

[0044] Network A and Network B can be two uplink communication networks in the multi-protocol communication system 100, used for data interaction between the controller 200 and the target communication module 300. The controller 200 and the target communication module 300 can establish communication connections via Network A and Network B respectively.

[0045] It should be noted that, Figure 1 The multiprotocol communication system 100 shown is merely an example, and the multiprotocol communication method provided in this application can also be applied to other applicable systems. The specific implementation and number of multiple field devices, the number of switches 400, and the specific network connection method can be set according to actual application requirements, and this application does not limit them.

[0046] See Figure 2 , Figure 2 This is a flowchart illustrating a multi-protocol communication method provided in an embodiment of this application. This method can be applied to... Figure 1 The multi-protocol communication system 100 shown can also be applied to other applicable multi-protocol communication systems. For ease of explanation, this embodiment applies the method to... Figure 1 The multi-protocol communication system 100 shown is used as an example. At the same time, multiple field devices 500, including field devices supporting the PROFINET protocol and field devices supporting the HART-IP protocol, are used as examples for explanation, and the controller 200 is used as the execution subject for introduction.

[0047] Figure 2 The multiprotocol communication method shown may include steps S201 to S204.

[0048] S201: Identify the target field device for which data interaction is to be performed.

[0049] The target field device is any one of multiple field devices. The communication configuration information for each of the multiple field devices is generated using the same configuration framework. This framework can be used to configure field devices corresponding to different communication protocols, obtaining the communication configuration information for each field device.

[0050] Each field device has its own communication configuration information. Depending on the communication protocols supported by different field devices, different communication protocols can be used for communication. Therefore, the controller first determines the target field device for data exchange, so as to obtain the communication configuration information corresponding to the target field device, determine the target communication protocol based on the communication configuration information, and then exchange data with the target field device.

[0051] In practical implementation, the controller can determine the target field device from multiple field devices based on data interaction requirements. For example, when it is necessary to read data from a field device or send control data to a field device, the controller can identify that field device as the target field device. Other field devices for which data interaction is to be performed can also be identified as target field devices, and subsequent steps can be executed.

[0052] Communication configuration information for multiple field devices can be generated by configuring each field device using the same configuration framework before executing this method. Therefore, after determining the target field device, the communication configuration information corresponding to the target field device, generated using this configuration framework, can be obtained.

[0053] Based on this, in one possible implementation, the multiple field devices include a first type of device and a second type of device. The communication protocols supported by the first type of device are different from those supported by the second type of device. The communication configuration information of the first type of device can be generated by configuring the first type of device according to the description file corresponding to the first type of device through the same configuration framework to obtain the communication configuration information of the first type of device. The communication configuration information of the second type of device can be generated by configuring the second type of device according to the custom file corresponding to the second type of device through the same configuration framework to obtain the communication configuration information of the second type of device. The custom file is used to configure the second type of device according to the configuration method used when configuring the first type of device.

[0054] The first type of device can be a PROFINET device that supports the PROFINET protocol, while the second type of device can be a non-PROFINET device that communicates using a communication protocol other than PROFINET. The same configuration framework can be used to configure PROFINET devices, while the second type of device uses this configuration framework for configuration through its corresponding custom file.

[0055] Description files can be provided by the equipment manufacturers of Category 1 devices. They describe the communication parameters, channel mappings, and other information of Category 1 devices, enabling the configuration framework to determine the configuration content of the device based on the description files. Custom files, on the other hand, can be created for Category 2 devices. They describe the information required for configuring Category 2 devices according to a file format that the configuration framework can recognize, allowing the configuration content of Category 2 devices to be configured through the same configuration framework.

[0056] Since the two types of devices support different communication protocols, the configuration content they need to configure may be different. By describing the configuration content of the second type of device through a custom file, the second type of device can reuse the configuration framework corresponding to the first type of device, reducing the need to use different configuration frameworks for configuration due to different communication protocols.

[0057] In practical implementation, the same configuration framework can be used to read the description file corresponding to the first type of device. Based on the content described in the description file, the channel configuration, data arrangement, etc., of the first type of device can be configured to obtain its communication configuration information. For the second type of device, the same configuration framework can be used to read its corresponding custom file. According to the configuration method provided by the configuration framework, the required configuration content of the second type of device can be configured to obtain its communication configuration information. Both types of devices use the same configuration framework for configuration, and their specific configuration content can be determined according to their respective communication requirements.

[0058] Furthermore, the second type of device can specifically be a HART-IP device that supports the HART-IP protocol. In this case, the description file corresponding to the first type of device can be a GSD file for PROFINET devices, and the custom file corresponding to the second type of device can be a custom GSD file compiled for HART-IP devices.

[0059] The custom GSD file, read by the configuration tool, describes the configuration content of the HART-IP device. The custom GSD file can be used to set the specific vendor identifier and device identifier for the HART-IP device, and describe the configuration content of the HART-IP device according to the slot structure used for PROFINET devices, enabling the configuration tool to configure the HART-IP device through the same configuration framework. The HART-IP device then receives and processes commands sent by the communication module according to the HART-IP protocol.

[0060] During configuration, a custom GSD file can be imported into a configuration tool that uses this configuration framework, and each HART command used by the HART-IP device can be configured as a corresponding sub-slot. Each HART command can correspond to one sub-slot, and the configuration information of this sub-slot can include information such as the input data length, output data length, and quality flag of the corresponding command. By establishing the correspondence between HART commands and sub-slots, the channel configuration, data arrangement, and command list of the HART-IP device can be configured in the same way as for PROFINET devices, thus obtaining the communication configuration information corresponding to the HART-IP device.

[0061] The generated communication configuration information may include the configuration information of the aforementioned sub-slots, and will be downloaded to the target communication module along with the configuration data for use by the target communication module in subsequent data interaction.

[0062] Therefore, by using the same configuration framework to configure the first type of device according to the description file and the second type of device according to the custom file, the first type of device and the second type of device that support different communication protocols can generate their respective communication configuration information in the same way. This reduces the need to use different configuration frameworks for configuration due to different communication protocols, thereby reducing the complexity of communication configuration for different field devices corresponding to different communication protocols.

[0063] S202: Obtain the communication configuration information of the target field device.

[0064] The communication configuration information of the target field devices is generated using the same configuration framework, indicating the communication method between the target communication module and the target field devices. A single target communication module supports multiple communication protocols and can use a communication protocol compatible with the corresponding field device for data interaction.

[0065] Since different field devices correspond to their own communication configuration information, after determining the target field device in step S201, it is necessary to obtain the communication configuration information corresponding to the target field device in order to provide a basis for subsequently determining the target communication protocol and conducting data interaction.

[0066] In practice, the communication configuration information corresponding to multiple field devices generated through the same configuration framework can be pre-saved. After determining the target field device, the controller can search for and read the communication configuration information corresponding to the target field device from the saved communication configuration information according to the correspondence between the field device and the communication configuration information, thus completing the acquisition operation in this step.

[0067] For example, when the target field device is a HART-IP device, the controller can read the communication configuration information corresponding to the HART-IP device generated through the same configuration framework, so as to use it for subsequent determination of the target communication protocol corresponding to the target field device and for data interaction.

[0068] Furthermore, communication configuration information can be stored in a unified management manner, which facilitates the management of communication configuration information of different field devices corresponding to different communication protocols, and obtains the corresponding communication configuration information after the target field device is determined.

[0069] Based on this, in one possible implementation, the communication configuration information of the target field device is written into the slave station table; obtaining the communication configuration information of the target field device may be: obtaining the device type identifier corresponding to the target field device from the slave station table.

[0070] The slave station table can include records corresponding to each field device. Each record is used to store the communication configuration information of the corresponding field device, so that different field devices corresponding to different communication protocols can be managed through the same slave station table.

[0071] The communication configuration information includes a device type identifier, which identifies the type of target communication protocol corresponding to the target field device. For example, the device type identifier for a PROFINET device can be used to identify the PROFINET protocol, and the device type identifier for a HART-IP device can be used to identify the HART-IP protocol. Different field devices using the same communication protocol can have the same device type identifier, and each will have its own corresponding communication configuration information in the slave station table.

[0072] In practical implementation, after configuration is complete, the generated communication configuration information can be written to the slave station table. Specifically, following a unified configuration data structure, the device type identifier and other communication configuration information of the target field device can be saved to the record corresponding to that target field device in the slave station table. The communication configuration information of other field devices can also be written to the slave station table in the same way to achieve unified management.

[0073] After determining the target field device in step S201, the controller can search for the record corresponding to the target field device in the slave station table and read the device type identifier from that record. For example, it can search for the record with the corresponding device tag number in the slave station table based on the device tag number of the target field device, and then read the device type identifier stored in that record.

[0074] The device type identifier belongs to the communication configuration information of the target field device. Through the above acquisition operation, the communication configuration information required to subsequently determine the target communication protocol can be obtained, so that the configuration management in the slave table is connected with the subsequent determination of the communication protocol.

[0075] Therefore, by writing the communication configuration information of the target field device into the slave station table, the communication configuration information of different field devices corresponding to different communication protocols can be uniformly managed using the slave station table, reducing the need to manage communication configuration information separately according to communication protocols. Furthermore, by retrieving the device type identifier corresponding to the target field device from the slave station table, since this device type identifier is used to characterize the type of target communication protocol corresponding to the target field device, the obtained device type identifier can provide a basis for subsequently determining the target communication protocol from the multiple communication protocols supported by the target communication module. This connects the unified management of communication configuration information with the subsequent determination of the communication protocol, thereby simplifying the management and retrieval of communication configuration information for different field devices corresponding to different communication protocols.

[0076] In the process industry, the HART-IP protocol can be used for data acquisition and control of smart instruments, while the PROFINET protocol can be used for real-time data interaction with field devices. In related technologies, when both HART-IP and PROFINET devices are used in a process unit, the communication modules typically support only one communication protocol. Therefore, separate communication modules supporting the corresponding protocols need to be configured to interact with these two types of field devices.

[0077] Based on this, in one possible implementation, various communication protocols include the PROFINET protocol and the HART-IP protocol.

[0078] Both PROFINET and HART-IP protocols are supported by the same target communication module. PROFINET devices can communicate with this target communication module using the PROFINET protocol, and HART-IP devices can communicate with this target communication module using the HART-IP protocol, enabling different field devices corresponding to different communication protocols to share the same communication module.

[0079] In practical implementation, the same target communication module can simultaneously implement the master station functions of both the PROFINET protocol and the HART-IP protocol, processing the data exchanged with field devices according to the corresponding communication protocols. For example, for PROFINET devices, the target communication module can provide PROFINET periodic frame communication functionality; for HART-IP devices, the target communication module can send corresponding commands and receive response data from the devices via port 5094 based on the user datagram protocol (UDP).

[0080] The communication functions corresponding to the two communication protocols mentioned above can coexist in the same target communication module. After the target communication protocol is determined based on the communication configuration information, the target communication module can use the communication function corresponding to the target communication protocol to exchange data with the target field equipment.

[0081] Therefore, by providing communication functions for both PROFINET and HART-IP protocols in the same target communication module, the communication needs of these two types of field devices can be met, reducing the need to deploy separate communication modules due to different communication protocols, thereby reducing the hardware cost when connecting different field devices corresponding to different communication protocols.

[0082] S203: Based on the communication configuration information, determine the target communication protocol corresponding to the target field device from among the various communication protocols supported by the target communication module.

[0083] The target communication protocol is the communication protocol used between the target communication module and the target field device. This target communication protocol belongs to the various communication protocols supported by the target communication module and is matched with the communication protocol used by the target field device. For different target field devices, the appropriate target communication protocol can be determined based on their corresponding communication configuration information.

[0084] Different communication protocols may have different data organization and processing rules. Since the same target communication module supports multiple communication protocols, before exchanging data with the target field device, it is necessary to determine the corresponding target communication protocol based on the communication configuration information of the target field device so that the exchanged data can be processed according to that protocol.

[0085] For example, in the aforementioned implementation where the communication configuration information includes a device type identifier, the controller can determine the communication protocol corresponding to the type represented by the device type identifier obtained in step S202 from among the various communication protocols supported by the target communication module, and use it as the target communication protocol.

[0086] For example, when the device type identifier indicates the PROFINET protocol, the controller can determine the PROFINET protocol as the target communication protocol from among the various communication protocols supported by the target communication module; when the device type identifier indicates the HART-IP protocol, the controller can determine the HART-IP protocol as the target communication protocol. For the aforementioned PROFINET devices and HART-IP devices that generate communication configuration information through the same configuration framework, the corresponding target communication protocol can be determined based on the device type identifier in their respective communication configuration information.

[0087] Therefore, communication configuration information generated using the same configuration framework can serve as the basis for determining the target communication protocol, ensuring that the device configuration is consistent with the communication protocol determination during operation, and providing a protocol basis for data interaction.

[0088] S204: Data is exchanged between the target communication module and the target field device according to the target communication protocol.

[0089] Data interaction can include the target communication module sending read commands or control data to the target field device, and receiving field data provided by the target field device. The controller can acquire field data or send control data to the target field device through the target communication module to monitor and control the production process.

[0090] The target communication protocol specifies the corresponding data organization and processing rules. After determining the target communication protocol in the above method, by adopting the communication function corresponding to the target communication protocol, the target communication module can process the interactive data according to the rules that match the target field equipment.

[0091] In its implementation, the target communication module organizes the data to be sent according to the data format of the target communication protocol and sends it to the target field device. Upon receiving data from the target field device, the target communication module parses it according to the target communication protocol to obtain the corresponding field data and then sends the field data to the controller.

[0092] For example, when the target communication protocol is the PROFINET protocol, the target communication module can send and receive PROFINET periodic frames with the PROFINET device according to the data update time determined by the configuration, so as to realize real-time input / output (I / O) data interaction.

[0093] Before interacting with HART-IP devices, the target communication module can perform device discovery by prioritizing the discovery and configuration protocol (DCP) and falling back to the address resolution protocol (ARP) to ensure compatibility with both DCP-supporting and non-DCP-supporting HART-IP devices.

[0094] When the target communication protocol is HART-IP, the target communication module can generate corresponding HART-IP data packets according to the command list and configuration cycle determined in the aforementioned configuration, and send them to the HART-IP device via port 5094 based on the UDP protocol. After receiving the response data returned by the HART-IP device, the target communication module can parse the response data and send the corresponding data to the controller according to the channel mapping and data arrangement determined in the configuration. For example, the HART command number can be determined by the configuration. When there is no output, the target communication module can continuously poll for input commands; when there is output, the target communication module can alternately send input commands and output commands.

[0095] Therefore, by using the communication configuration information generated using the same configuration framework to determine the target communication protocol, and by performing data interaction according to the determined target communication protocol, the same target communication module can provide corresponding data interaction functions according to the communication protocols corresponding to different field devices.

[0096] As can be seen from the above embodiments, this application determines the target field device for data interaction from multiple field devices and obtains the communication configuration information corresponding to the target field device, so that subsequent communication protocol determination and data interaction are based on the communication configuration information of the corresponding field device. Since the communication configuration information corresponding to multiple field devices is generated using the same configuration framework, the communication configuration of different field devices corresponding to different communication protocols can reuse the same configuration framework, reducing the need to use different configuration frameworks for configuration due to different communication protocols. Furthermore, the same target communication module supports multiple communication protocols. Based on the obtained communication configuration information, the target communication protocol corresponding to the target field device is determined from the multiple communication protocols it supports, and data is exchanged between the target communication module and the target field device according to the target communication protocol. This allows the communication configuration information to instruct the target communication module to use a communication protocol that matches the target field device, thereby enabling the same target communication module to meet the communication needs of different field devices corresponding to different communication protocols. Therefore, by using the communication configuration information generated with the same configuration framework, the determination of target field devices, the acquisition of communication configuration information, and the subsequent determination of communication protocols and data interaction can be connected. This not only reduces the complexity of communication configuration by reusing the configuration framework, but also reduces the need to deploy communication modules separately due to different communication protocols. This reduces the system configuration complexity and hardware cost when different field devices corresponding to different communication protocols are connected.

[0097] In industrial automation systems, controllers and field devices typically need to continuously exchange data, requiring continuous and reliable communication.

[0098] Based on this, in one possible implementation, a first operating state of the primary communication module and a second operating state of the backup communication module are determined; when the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

[0099] The primary communication module and the backup communication module can be two redundant communication modules, both supporting the aforementioned multiple communication protocols and capable of data interaction with corresponding field devices. Redundancy means that the two communication modules can take over the corresponding communication tasks. In this embodiment, the target communication module can be one of the primary communication module and the backup communication module.

[0100] The first operating state characterizes the current operating status of the primary communication module, and the second operating state characterizes the current operating status of the backup communication module. The operating state can be determined based on the module's fault condition, such as normal or abnormal status, or it can be determined in conjunction with the fault level. By determining and comparing the operating states of the two modules respectively, a basis can be provided for identifying the target communication module to undertake the aforementioned data interaction task.

[0101] In one specific implementation, the fault levels of the primary and backup communication modules can be determined separately based on the fault items present in each module, and the first and second operating states can be compared according to the fault levels. The values ​​corresponding to each fault item can be shown in the table below.

[0102] Table 1

[0103] For each communication module, the values ​​corresponding to each existing fault item can be summed to obtain the current fault level of that communication module. When none of the above fault items exist, the fault level of the corresponding communication module is 0.

[0104] In this judgment method, a lower fault level indicates a superior operating state. The communication module with the lower fault level can then undertake the primary communication task, while the communication module with the higher fault level serves as a backup. For the current primary and backup communication modules, if the fault level of the backup communication module is lower than that of the primary communication module, the second operating state can be determined to be superior to the first operating state. The backup communication module is then identified as the target communication module and undertakes the aforementioned data interaction task.

[0105] For example, when the primary communication module experiences both a single network port failure and a single power supply failure, its failure level is 3 + 1 = 4; when the backup communication module does not have any of the above failure items, its failure level is 0. Since the failure level of the backup communication module is lower than that of the primary communication module, it can be determined that the second operating state is superior to the first operating state, and the backup communication module is identified as the target communication module, so as to interact with the target field equipment using the target communication protocol through the backup communication module.

[0106] When the fault levels of two modules are the same, the second operating state is not considered superior to the first operating state.

[0107] In another specific implementation, the controller can determine a first operating state and a second operating state based on the fault conditions corresponding to the primary communication module and the backup communication module, respectively. These fault conditions are categorized as normal or abnormal. For example, when the first operating state of the primary communication module is abnormal, while the second operating state of the backup communication module is normal, the second operating state can be determined to be superior to the first operating state, and the backup communication module can be identified as the target communication module.

[0108] Once the backup communication module is identified as the target communication module, the communication functions corresponding to the target communication module in the aforementioned steps can be provided by the backup communication module. The controller can determine the target communication protocol from among the various communication protocols supported by the backup communication module based on the communication configuration information of the target field device. The controller then uses this target communication protocol to exchange data with the target field device through the backup communication module, ensuring that the comparison results of the operating status are incorporated into the subsequent communication protocol determination and data exchange process.

[0109] Therefore, by comparing the operating states of the redundant primary and backup communication modules, the backup communication module is selected as the target communication module when the second operating state is superior to the first. The backup module with the better operating state can then undertake the corresponding communication tasks. Since both modules support the aforementioned multiple communication protocols, the backup communication module can provide communication protocol functions corresponding to the target field device, which helps maintain the continuity of data interaction between field devices corresponding to different communication protocols and improves the reliability of multi-protocol communication.

[0110] In the above-described implementation of redundant communication, when the target communication protocol is PROFINET, S2 redundancy or R1 redundancy can be adopted according to the redundancy methods supported by the target field device and the primary and backup communication modules. Specifically, module redundancy mode can be enabled in the configuration software, and the redundancy mode corresponding to the PROFINET device can be configured to establish the corresponding redundant communication connection.

[0111] In the S2 redundancy implementation, the target field device can establish communication connections with both the primary and backup communication modules via a PROFINET communication interface. During normal operation, the communication connection between the primary communication module and the target field device is the primary connection; the communication connection between the backup communication module and the target field device is the backup connection. Both communication modules can communicate with the target field device. The output control data corresponding to the primary connection is effective on the target field device, while the output control data corresponding to the backup connection is not effective initially.

[0112] When the primary communication module fails while the backup communication module continues to operate normally, the backup communication module can be identified as the target communication module based on the comparison results of the aforementioned operating states. The existing backup connection between the backup communication module and the target field device can be switched to a primary connection, allowing the backup communication module to continue exchanging data with the target field device through this connection, and enabling the output control data corresponding to this connection to take effect on the target field device.

[0113] In the R1 redundancy implementation, the target field device can have two redundant PROFINET communication interfaces, which establish communication connections with the primary and backup communication modules respectively through corresponding field communication networks. The primary and backup communication modules can exchange real-time I / O data with the same target field device through their respective communication connections. When the primary communication module fails, but the backup communication module and its communication connection remain normal, the backup communication module can be designated as the target communication module, and it will continue to interact with the target field device through its corresponding communication connection.

[0114] Therefore, by configuring the corresponding redundancy mode for PROFINET devices, the primary communication module and the backup communication module can establish corresponding communication connections in advance. When the primary communication module fails, the backup communication module can take over the communication task using the existing communication connection, which helps to maintain the continuity of data interaction of PROFINET devices.

[0115] In the above-described implementation of redundant communication, when the target communication protocol is HART-IP, both the primary communication module and the backup communication module can interact with the same target field device. Data packets sent by the two modules can be distinguished by setting different sequence numbers.

[0116] Based on this, in one possible implementation, the serial number range corresponding to the primary communication module and the serial number range corresponding to the backup communication module do not overlap; according to the target communication protocol, the data exchange between the target communication module and the target field device can be: when the target communication protocol is the HART-IP protocol and the target communication module is the backup communication module, the data exchange between the backup communication module and the target field device is based on the serial number range corresponding to the backup communication module.

[0117] The sequence number can be a value used to identify data packets in the HART-IP data packet. In this embodiment, by giving data packets sent by the primary communication module and the backup communication module different sequence numbers, the data packets sent by the two modules can be distinguished.

[0118] The primary and backup communication modules represent their roles in redundant communication. For example, when both modules are operating normally, they can each exchange real-time I / O data with the same target field device and can each send corresponding HART-IP data packets. By setting different sequence numbers, the data packets sent by the two modules can be distinguished.

[0119] In one specific implementation, non-overlapping sequence number ranges can be assigned to the two communication modules. For example, the two sequence number ranges can be 0–0x7FFF and 0x8000–0xFFFF, respectively. When generating a HART-IP data packet, each communication module can select a sequence number from its corresponding sequence number range, fill that sequence number into the data packet, and send the data packet to the target field device. Because the two sequence number ranges do not overlap, the sequence numbers of the data packets sent by the two modules can remain different.

[0120] For example, when the sequence number range corresponding to the primary communication module is 0 to 0x7FFF and the sequence number range corresponding to the backup communication module is 0x8000 to 0xFFFF, the sequence number of a data packet sent by the primary communication module can be 0x0001, and the sequence number of a data packet sent by the backup communication module can be 0x8001. The range of the sequence number indicates which communication module sent the corresponding data packet.

[0121] In this specific implementation, the serial number range can correspond to a specific communication module, and this correspondence is maintained when its primary or backup role changes. When the backup communication module is determined as the target communication module based on the aforementioned operational status comparison results, the communication module can continue to use its corresponding serial number range to exchange data with the target field device using the HART-IP protocol.

[0122] Therefore, by having two modules participate in data interaction with the HART-IP device, the backup communication module can continue to undertake communication tasks on the basis of existing data interaction when it is identified as the target communication module. By setting different sequence numbers for the data packets sent by the two modules and using non-overlapping sequence number ranges in the specific implementation, data packets sent by different modules can be distinguished, and the correspondence between data packets and sending modules can be maintained during the change of primary and backup roles, which is beneficial to maintaining the continuity of HART-IP device communication.

[0123] This application also provides an industrial automation system. The industrial automation system includes a controller, a target communication module connected to the controller, and a target field device connected to the target communication module. The industrial automation system can be... Figure 1 The multi-protocol communication system in the text can specifically be: The controller is used to identify the target field device for data interaction. The target field device can be any one of multiple field devices, and the communication configuration information for each of these field devices is generated using the same configuration framework. It is also used to acquire the communication configuration information of the target field device. This communication configuration information indicates the communication method between the target communication module and the target field device. A single target communication module supports multiple communication protocols. Furthermore, based on the communication configuration information, the controller determines the target communication protocol corresponding to the target field device from among the multiple communication protocols supported by the target communication module, and exchanges data between the target communication module and the target field device according to the target communication protocol.

[0124] Specifically, after the controller identifies the target field device for which data interaction is required, it can obtain the communication configuration information corresponding to that target field device and determine the target communication protocol based on the communication configuration information. The target communication module can process the data to be sent according to the target communication protocol and send it to the target field device. It can also receive and process the data sent by the target field device according to the target communication protocol, thereby realizing data interaction between the controller and the target field device.

[0125] Therefore, by identifying the target field device for data interaction from multiple field devices through the controller and obtaining the communication configuration information corresponding to that target field device generated using the same configuration framework, different field devices corresponding to different communication protocols can reuse the same configuration framework. The controller further determines the target communication protocol corresponding to the target field device from among the multiple communication protocols supported by the same target communication module based on the communication configuration information, and exchanges data between the target communication module and the target field device according to the target communication protocol. This allows the same target communication module to meet the communication needs of different field devices corresponding to different communication protocols. This reduces the system configuration complexity and hardware cost when connecting different field devices corresponding to different communication protocols.

[0126] In one possible implementation, see Figure 3 , Figure 3 This is a schematic diagram of an industrial automation system provided in an embodiment of this application. The industrial automation system 300 may further include a primary communication module 330 and a backup communication module 320. The primary communication module 330 and the backup communication module 320 are respectively connected to the controller 310 and can be connected to the target field device 350 through a switch 340. The primary communication module 330 and the backup communication module 320 are redundant. The aforementioned target communication module is one of the primary communication module 330 and the backup communication module 320, and both the primary communication module 330 and the backup communication module 320 support the aforementioned multiple communication protocols.

[0127] The controller 310 is also used to determine a first operating state of the primary communication module 330 and a second operating state of the backup communication module 320, and to compare the first and second operating states. When the second operating state is better than the first operating state, the controller 310 determines the backup communication module 320 as the target communication module.

[0128] The first and second operating states can be determined based on the fault status of the corresponding communication modules. For example, the fault level of the corresponding communication module can be determined based on whether there is a configuration fault, network port fault, power supply fault, or communication fault with the field device 350, and the operating state corresponding to the communication module with the lower fault level is determined as the better operating state.

[0129] When the fault level of the backup communication module 320 is lower than that of the primary communication module 330, the controller 310 can determine that the second operating state is superior to the first operating state and designate the backup communication module 320 as the target communication module. The controller 310 can determine the target communication protocol from among the various communication protocols supported by the backup communication module 320 based on the communication configuration information of the target field device 350, and then exchange data with the target field device 350 through the backup communication module 320 according to the target communication protocol.

[0130] Therefore, by setting up a primary communication module 330 and a backup communication module 320 that both support multiple communication protocols and are redundant with each other, and determining the target communication module based on the operating status of the two, when the operating status of the primary communication module 330 is poor, the backup communication module 320 can interact with the target field device 350 according to the target communication protocol corresponding to the target field device 350, thereby improving the continuity and reliability of multi-protocol communication in the industrial automation system 300.

[0131] It should be noted that, Figure 3 The connection methods shown are illustrative examples. In practical applications, appropriate settings can be made according to system configuration and communication requirements; this application does not impose specific limitations on this.

[0132] See Figure 4 , Figure 4 This is a schematic diagram of another industrial automation system provided in an embodiment of this application. Figure 4 The industrial automation system 400 shown can... Figure 3 The industrial automation system 300 shown is further equipped with a redundant serial port 460. For Figure 4 Zhongyu Figure 3 For the same or similar structure, please refer to the aforementioned embodiments. This embodiment mainly describes the redundant serial port 460.

[0133] like Figure 4As shown, the industrial automation system 400 may include a controller 410, a backup communication module 420, a primary communication module 430, a switch 440, and multiple field devices 450. The primary communication module 430 and the backup communication module 420 are respectively connected to the controller 410 and to the multiple field devices 450 via the switch 440. The primary communication module 430 and the backup communication module 420 are connected via a redundant serial port 460. For example, the primary communication module 430 and the backup communication module 420 may use COM795-S communication modules; in this specific implementation, the communication module supports a maximum of 252 slave stations.

[0134] In one specific hardware connection method, the primary communication module 430 and the backup communication module 420 can access networks A and B respectively through their respective A network ports and B network ports. The primary communication module 430 and the backup communication module 420 can simultaneously send real-time input data and point-to-point response data via networks A and B. When network A communication fails but network B receives information normally, the primary communication module 430 and the backup communication module 420 can still simultaneously send data packets to networks A and B. Networks A and B can serve as redundant communication networks between the controller 410 and the two communication modules, where the switch 440 can be an APL field switch.

[0135] The primary communication module 430 and the backup communication module 420 can be connected to the registered jack 45 (RJ45) port of the APL field switch via their respective downlink RJ45 ports. The APL field switch can connect to multiple field devices 450 via its APL ports. The RJ45 port can serve as the Ethernet interface between the communication modules and the APL field switch; the APL field switch can communicate based on 10BASE-T1L single-pair Ethernet and can connect to field devices 450 via two-wire cables.

[0136] Multiple field devices 450 may include HART-IP over APL devices and PROFINET over APL devices. HART-IP over APL devices refer to field devices that support the HART-IP protocol and communicate using the APL physical layer, while PROFINET over APL devices refer to field devices that support the PROFINET protocol and communicate using the APL physical layer. "over APL" indicates that the corresponding communication protocol operates on top of the APL physical layer; the communication protocols used by the two types of field devices are still HART-IP and PROFINET, respectively.

[0137] The terms HART-IP and PROFINET devices are used to refer to the communication protocols they support, and do not specify the physical layer used. For example, devices using a conventional Ethernet physical layer can connect to a switch via an RJ45 port and corresponding cables; devices using an APL physical layer can connect to an APL field switch via an APL interface and a two-wire single-pair cable, enabling both communication and power supply. Therefore, HART-IP over APL devices and PROFINET over APL devices are specific implementations of HART-IP and PROFINET devices, respectively, with the main differences lying in the physical layer and the corresponding interface and cable configurations.

[0138] HART-IP and PROFINET protocols, as communication protocols running on the APL physical layer, can exchange data with the primary communication module 430 and the backup communication module 420 respectively through the same APL field network. The target field device can be any of the multiple field devices 450.

[0139] In this connection method, the data transmission path between the controller 410, the primary communication module 430 or the backup communication module 420, the APL field switch, and the target field device can sequentially include network A or network B, the downlink RJ45 port of the communication module, the RJ45 port of the APL field switch, and the APL port. The APL field switch can forward data sent by the communication module through the RJ45 port to the corresponding field device 450, and forward data sent by the field device 450 to the corresponding communication module.

[0140] The aforementioned APL field network is one specific implementation of this application. In other embodiments, the primary communication module 430 and the backup communication module 420 can also be connected to the field device 450 or other network devices via RJ45 network ports, and exchange data using the target communication protocol corresponding to the target field device.

[0141] The redundant serial port 460 is used for redundant communication between the primary communication module 430 and the backup communication module 420, enabling the two communication modules to synchronize data in real time. The data synchronized through the redundant serial port 460 can be data characterizing the operating status of the two communication modules, as well as data required to achieve redundant communication. For example, the primary communication module 430 and the backup communication module 420 can exchange their respective fault information, fault level, primary / backup roles, and communication status through the redundant serial port 460, so as to determine their operating status based on the synchronized data and provide a basis for determining the target communication module.

[0142] In one implementation, the primary communication module 430 and the backup communication module 420 can periodically send data requiring synchronization through the redundant serial port 460 at preset time intervals. In another implementation, when the operating status of a communication module or the data requiring synchronization changes, the corresponding communication module can send the changed data to another communication module through the redundant serial port 460. The receiving communication module can update its stored information based on the received data.

[0143] The redundant serial port 460 can be implemented in several ways. For example, the redundant serial port 460 can be an internal serial interface connecting the primary communication module 430 and the backup communication module 420 via a base or backplane, or it can be an external serial interface connecting the two communication modules via a separate connecting cable. The redundant serial port 460 can be implemented based on a universal asynchronous transceiver interface, an RS-422 interface, or an RS-485 interface, and its specific implementation can be determined according to the data transmission rate, transmission distance, and anti-interference requirements.

[0144] Therefore, by setting up a redundant serial port 460 between the primary communication module 430 and the backup communication module 420, the data required for redundant communication between the two communication modules can be synchronized, and a data basis can be provided for comparing their operating status and determining the target communication module, thereby improving the continuity and reliability of multi-protocol communication in the industrial automation system 400.

[0145] In the above implementation of the APL field network, the multi-protocol mixed communication and redundancy functions can be verified. Verification may include: whether PROFINET over APL devices and HART-IP over APL devices can communicate normally; whether the backup communication module can take over communication tasks when the primary communication module fails; and whether the real-time I / O data of the two types of field devices remains continuous during redundancy switching, and whether there are any abnormal fluctuations in the data trend.

[0146] First, perform an initial status verification. Check whether the controller 410, primary communication module 430, backup communication module 420, switch 440, and two types of field devices 450 are operating normally, and confirm that the redundant communication between the primary communication module 430 and the backup communication module 420 via the redundant serial port 460 is normal. In one specific implementation, the primary communication module 430 and the backup communication module 420 can use two communication cards inserted into the same base to form a 1:1 base redundancy.

[0147] Subsequently, APL multi-protocol hybrid connectivity verification was performed. PROFINET over APL devices and HART-IP over APL devices were connected to the same APL field network. Using configuration software, both types of field devices 450 were configured through the same configuration framework. After configuration, the communication status and real-time I / O data of the two types of field devices 450 were checked via controller 410 to verify whether the two types of field devices 450 could communicate normally and exchange real-time I / O data simultaneously.

[0148] For PROFINET over APL devices, a failure of the primary communication module 430 can be simulated by powering off or disconnecting it. Check whether the backup communication module 420 is identified as the target communication module and whether it can continue to exchange data with the corresponding field device 450 using the PROFINET protocol. The expected result is that the backup communication module 420 takes over the communication task, and during the takeover process, communication of the PROFINET over APL device remains continuous without data packet loss.

[0149] For HART-IP over APL devices, after restoring the initial state described above, a fault can be simulated again by powering off or disconnecting the primary communication module 430. Check whether the backup communication module 420 is identified as the target communication module and whether the backup communication module 420 can continue to exchange data with the corresponding field device 450 using the HART-IP protocol. The expected result is that the backup communication module 420 takes over the communication task, and during the takeover process, communication of the HART-IP over APL device remains continuous without data packet loss.

[0150] During the aforementioned redundancy switching test, the controller monitoring software can be used to observe the real-time I / O data and their changing trends of the two types of field devices 450 before, during, and after the switching, to check whether the data is continuous, whether there is any data loss, and whether the switching causes abnormal signal jitter.

[0151] When two types of field devices 450 can communicate normally in the same APL field network, the redundancy switching time meets the system requirements, and no data loss or abnormal signal jitter caused by the switching occurs during the switching process, it can be determined that the above multi-protocol mixed communication and redundancy function verification has passed.

[0152] It should be noted that, Figure 4The connection methods shown, as well as the specific implementation forms of the communication module models, number of switches, maximum number of slave stations, network interfaces, physical layers, redundant serial ports, data synchronization methods, and verification methods mentioned above, are all illustrative examples. In practical applications, corresponding settings can be made according to system configuration and communication requirements, and this application does not impose specific limitations on them.

[0153] The above combination Figures 1 to 4 The multiprotocol communication method and related systems are introduced below. The structure of the multiprotocol communication device and computing device provided in the embodiments of this application is described in conjunction with the accompanying drawings.

[0154] This application also provides a multi-protocol communication device. See also... Figure 5 , Figure 5 A schematic diagram of a multi-protocol communication device according to an embodiment of this application is shown. The multi-protocol communication device 510 can be applied to industrial automation systems or deployed in computing devices used for multi-protocol communication. The multi-protocol communication device 510 may include a determining module 520, an acquiring module 530, and an interaction module 540.

[0155] The determination module 520 is used to determine the target field device for data interaction, wherein the target field device is any one of a plurality of field devices, and the communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework. The acquisition module 530 is used to acquire the communication configuration information of the target field device. The communication configuration information of the target field device is used to indicate the communication method between the target communication module and the target field device. The same target communication module supports multiple communication protocols. The determining module 520 is further configured to determine the target communication protocol corresponding to the target field device from the multiple communication protocols supported by the target communication module based on the communication configuration information; The interaction module 540 is used to exchange data between the target communication module and the target field device according to the target communication protocol.

[0156] In one possible implementation, the plurality of field devices include a first type of device and a second type of device, wherein the communication protocol supported by the first type of device is different from the communication protocol supported by the second type of device, and the device further includes: a generation module; the generation module is used to configure the first type of device according to the description file corresponding to the first type of device through the same configuration framework to obtain the communication configuration information of the first type of device; The generation module is further configured to configure the second type of device according to the custom file corresponding to the second type of device through the same configuration framework to obtain the communication configuration information of the second type of device. The custom file is used to enable the same configuration framework to configure the second type of device in the same configuration method used when configuring the first type of device.

[0157] In one possible implementation, the device further includes: a writing module; The writing module is used to write the communication configuration information of the target field device into the slave table. The communication configuration information includes a device type identifier, which is used to characterize the type of the target communication protocol corresponding to the target field device. The slave table is used to manage the communication configuration information of different field devices corresponding to different communication protocols. The acquisition module 530 is used to acquire the equipment type identifier corresponding to the target field equipment from the slave station table.

[0158] In one possible implementation, the multiple communication protocols include the PROFINET protocol and the HART-IP protocol.

[0159] In one possible implementation, the determining module 520 is further configured to: determine a first operating state of the primary communication module and a second operating state of the backup communication module, wherein the primary communication module and the backup communication module are both communication modules that support the multiple communication protocols, and the primary communication module and the backup communication module are redundant to each other; When the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

[0160] In one possible implementation, the serial number range corresponding to the primary communication module and the serial number range corresponding to the backup communication module do not overlap. The interaction module 540 is used for: When the target communication protocol is HART-IP and the target communication module is the backup communication module, data is exchanged between the backup communication module and the target field device according to the serial number range corresponding to the backup communication module.

[0161] The multi-protocol communication device 510 provided in this embodiment corresponds to the above-mentioned... Figure 2 The multi-protocol communication method in the illustrated embodiment; therefore, the functions of each module and its technical effects in this embodiment can be found in the foregoing. Figures 2 to 4 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0162] Figure 6This is a schematic diagram of the hardware structure of a computing device provided in this application. Figure 6 As shown, the computing device 600 includes a processor 610, a memory 620, a communication interface 630, and a bus 640. The processor 610, memory 620, and communication interface 630 communicate via the bus 640. The bus 640 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 6 The symbol is represented by a single thick line, but this does not indicate that there is only one bus or one type of bus. The communication interface 630 is used for external communication.

[0163] It should be understood that in the embodiments of this application, the processor 610 may be a CPU, or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete device assemblies, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0164] The memory 620 may include read-only memory and random access memory, and provides instructions and data to the processor 610. The memory 620 may also include non-volatile random access memory.

[0165] The memory 620 can be volatile memory or non-volatile memory, or it can include both. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0166] The memory 620 stores executable code, and the processor 610 executes the executable code to perform the aforementioned actions. Figures 2 to 5 The method performed in the illustrated embodiment.

[0167] It should be understood that the computing device 600 in this application embodiment may correspond to the computing device in this application embodiment, and may correspond to the execution of the embodiments in this application embodiment. Figures 2 to 5 The method executed by the computing device in the illustrated method; the above and other operations or functions implemented by the computing device 600 can be realized. Figures 2 to 5 The method flow executed by the computing device in the illustrated method will not be described in detail here for the sake of brevity.

[0168] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to execute the aforementioned multi-protocol communication method.

[0169] This application also provides a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computing device, all or part of the processes or functions described in this application are generated.

[0170] The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, or data center to another website, computer, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0171] The computer program product can be a software installation package. When the aforementioned multi-protocol communication method is required, the computer program product can be downloaded and executed on a computing device.

[0172] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0173] The terminology used in the above embodiments is for the purpose of describing specific embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” refers to one, two, or more; the character “ / ” generally indicates that the preceding and following objects are in an “or” relationship. In the embodiments of this application, “simultaneously” refers to the same time period, including situations where they are at the same moment.

[0174] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0175] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A multi-protocol communication method, characterized in that, The method includes: The target field device for data interaction is determined. The target field device is any one of a plurality of field devices. The communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework. Obtain the communication configuration information of the target field device. The communication configuration information of the target field device is used to indicate the communication method between the target communication module and the target field device. The same target communication module supports multiple communication protocols. Based on the communication configuration information, the target communication protocol corresponding to the target field device is determined from the multiple communication protocols supported by the target communication module; According to the target communication protocol, data is exchanged between the target communication module and the target field device.

2. The method according to claim 1, characterized in that, The plurality of field devices include a first type of device and a second type of device. The communication protocols supported by the first type of device are different from those supported by the second type of device. The method for generating the communication configuration information of the first type of device includes: Using the same configuration framework, the first type of devices are configured according to the description file corresponding to the first type of devices to obtain the communication configuration information of the first type of devices; The methods for generating communication configuration information for the second type of device include: Using the same configuration framework, the second type of device is configured according to the custom file corresponding to the second type of device to obtain the communication configuration information of the second type of device. The custom file is used to enable the same configuration framework to configure the second type of device in the same configuration method used when configuring the first type of device.

3. The method according to claim 1, characterized in that, The method further includes: The communication configuration information of the target field device is written into the slave station table. The communication configuration information includes a device type identifier, which is used to characterize the type of target communication protocol corresponding to the target field device. The slave station table is used to manage the communication configuration information of different field devices corresponding to different communication protocols. The step of obtaining the communication configuration information of the target field device includes: Obtain the equipment type identifier corresponding to the target field equipment from the slave station table.

4. The method according to claim 1, characterized in that, The various communication protocols include the PROFINET protocol and the HART-IP protocol.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The first operating state of the primary communication module and the second operating state of the backup communication module are determined. Both the primary communication module and the backup communication module are communication modules that support the multiple communication protocols. The primary communication module and the backup communication module are redundant to each other. When the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

6. The method according to claim 5, characterized in that, The serial number range corresponding to the primary communication module and the serial number range corresponding to the backup communication module do not overlap. The step of exchanging data between the target communication module and the target field device according to the target communication protocol includes: When the target communication protocol is HART-IP and the target communication module is the backup communication module, data is exchanged between the backup communication module and the target field device according to the serial number range corresponding to the backup communication module.

7. An industrial automation system, characterized in that, The system includes a controller, a target communication module connected to the controller, and target field devices connected to the target communication module. The controller is configured to: determine the target field device for data interaction, wherein the target field device is any one of a plurality of field devices, and the communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework; acquire the communication configuration information of the target field device, which indicates the communication method between the target communication module and the target field device, wherein the same target communication module supports multiple communication protocols; determine the target communication protocol corresponding to the target field device from the plurality of communication protocols supported by the target communication module based on the communication configuration information; and exchange data between the target communication module and the target field device according to the target communication protocol.

8. The industrial automation system according to claim 7, characterized in that, The system further includes a backup communication module connected to the controller and a primary communication module connected to the controller. The backup communication module and the primary communication module are respectively connected to the target field device. The primary communication module and the backup communication module are redundant to each other. The target communication module is one of the primary communication module and the backup communication module. The controller is also used to determine a first operating state of the primary communication module and a second operating state of the backup communication module, wherein both the primary communication module and the backup communication module are communication modules that support the multiple communication protocols. When the second operating state is better than the first operating state, the backup communication module is determined as the target communication module.

9. A multi-protocol communication device, characterized in that, The device includes: The determination module is used to determine the target field device for data interaction, wherein the target field device is any one of a plurality of field devices, and the communication configuration information corresponding to the plurality of field devices is generated using the same configuration framework. The acquisition module is used to acquire the communication configuration information of the target field device. The communication configuration information of the target field device is used to indicate the communication method between the target communication module and the target field device. The same target communication module supports multiple communication protocols. The determining module is further configured to determine the target communication protocol corresponding to the target field device from the multiple communication protocols supported by the target communication module based on the communication configuration information; An interaction module is used to exchange data between the target communication module and the target field device according to the target communication protocol.

10. A computing device, characterized in that, The computing device includes a processor and memory; The memory is used to store instructions, and the processor executes the instructions stored in the memory to cause the computing device to perform the method as described in any one of claims 1 to 6.