EtherNet / IP modular information identification method and equipment

Abstract

The invention relates to the technical field of industrial network communication, and provides an EtherNet / IP modular information identification method, which performs modular information identification on a slave station and a sub-slave station through a preset equipment description file. Therefore, the method comprises the following steps of: importing a corresponding file mixed package into a master station equipment module through a controller; when the matching is unsuccessful, slave station equipment information is obtained according to the EDS file, and the logic station information in the XML file with the logic station information is used for replacing the sub-module information in sequence; slave station equipment information is matched with the XML file with logic station information, communication is executed according to description of the XML file with the logic station information, and then all submodules under the slave station are sequentially identified according to the logic station information. The method supports the dynamic adjustment of the number of the logic stations according to the network topology, achieves the flexible recognition and control of the substation equipment through the dynamic import of the mixed package containing the equipment information and the description of the logic stations, and improves the deployment efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of industrial network communication, and specifically to an EtherNet / IP modular information recognition method and device. Background Art

[0002] As Figure 1 shown, the three major mainstream industrial Ethernet protocols include EtherCAT, Ethernet / IP, and Profinet. Among them, Ethernet / IP is an application layer protocol on TCP / IP, adopting the standard Ethernet layer protocols and the Common Industrial Protocol (CIP), establishing communication between nodes through a specific connection, adopting a star topology structure, and the number of nodes is not limited. The EtherNet / IP protocol has been widely used in industrial fields due to its characteristics such as openness, high transmission speed, strong compatibility, and strong real-time performance. Although the EtherNet / IP protocol is open-source and there are a variety of related products, it has to face an embarrassing problem in the industrial automation market where distributed control systems are increasingly popular: compared with the EtherCAT and Profinet protocols, its solutions in Rack (rack) and SubModule (sub-module) technologies cannot be promoted among major automation equipment manufacturers. On the one hand, the reason is that the transition of the EtherNet / IP protocol from a centralized control system to a distributed control system is slow. On the other hand, the device description files supporting the EtherNet / IP protocol products, that is, the EDS file specification requirements and coding difficulty are high, and except for a few large companies, many devices supporting the EtherNet / IP protocol products do not provide device description files supporting the products. This leads to the situation that most controllers of the EtherNet / IP protocol can only reach the slave station itself when identifying, configuring, and controlling EtherNet / IP slave stations, and cannot identify the sub-modules mounted under the slave station. In this way, on the one hand, it is impossible to determine whether the sub-module has an abnormality when a failure occurs, and at the same time, it is also impossible to timely detect illegally mounted sub-modules. In this way, it is impossible to upgrade the sub-module, nor to perform process data expansion and mapping on the sub-module.

[0003] In this regard, in the prior art, the invention patent "A Method for Visualizing the Configuration of a Coupler Expansion Module on a Keyence Platform" with the patent publication number CN117706983A provides a method for visualizing the configuration of a coupler expansion module on a Keyence platform. Specifically, it includes creating a spreadsheet file, filling in the manufacturer information in the spreadsheet file, creating XML files for the coupler and the expansion module, and describing the information in the XML files, establishing a connection bridge and an input / output address table for the coupler and the expansion module, setting the starting address, offset address, and data type of the digital quantity module and the analog quantity module, and searching for the address in the XML file, connecting the coupler and the expansion module together through the connection bridge, and then implementing automatic allocation of the expansion module address through an address calculation method. At the same time, in order to avoid address preemption, the starting address of the analog quantity is set further back, solving the problem that the configuration of the expansion module is fixed and inconvenient to change due to the cumbersome calculation in the traditional method, and also solving the problem that the address of the Ethernet / IP coupler configuration is difficult to identify on the Keyence platform.

[0004] However, although this patent aims to solve the addressing problem, due to writing issues, some content is misdescribed. For example, in the EtherNet / IP scenario, the professional translation of Rack should be "rack". In the EtherNet / IP scenario, there are often multiple modules, such as input / output modules or communication modules, installed on the rack. The rack is used to accurately present the positions and connection status of these physical modules. In the comparative document, it is translated as "connection bridge", apparently misinterpreting it as "Remote Attachment Connection Kit (RACK)". Based on such an incorrect description, the technical solution in the comparative document is not expressed completely and accurately and cannot be implemented. Further, even if the solution described in the comparative document can be implemented, when the hanging position of the sub-module on the slave station changes, or after the configuration of the slave station itself changes, the original settings cannot respond quickly and adjust automatically. This will cause the master station to not find the sub-module on the slave station, or even if it can sense the existence of the sub-module, it cannot establish a connection. In such a situation, in the prior art, it is often necessary to rewrite the XML file, which affects work efficiency. Summary of the Invention

[0005] The object of the present invention is to provide an EtherNet / IP modular information recognition method, which, without departing from the EtherNet / IP protocol, provides a solution for identifying and controlling the devices loaded on the slave station for EtherNet / IP-related products, enabling modular information recognition of the slave station and sub-slave stations through a preset device description file.

[0006] To achieve the above object, an EtherNet / IP modular information recognition method of the present invention uses an EtherNet / IP controller. The specific recognition steps are as follows: import the corresponding EDS-XML file mixed package into the EtherNet / IP master device module through the EtherNet / IP controller; the EDS-XML file mixed package contains at least one EDS file and multiple XML files, and at least one of the XML files contains logical station information; first, determine whether the device information recorded in the EDS file in the EDS-XML file mixed package is consistent with the device information in one of the XML files; if they are consistent, parse the successfully matched EDS file and XML file. Determine the process data communication information from the EDS file, and determine the modular information recognition path and service data communication path of the slave station from the XML file; if all file parsing is normal, further parse the Rack information supported under this slave device. If the Rack described in the XML file of the slave station is consistent with the slave Rack, parse the PDO and SDO information access paths of all matchable Rack slave stations, and mount all supported slave stations to the corresponding slave path; when the match is unsuccessful, first obtain the slave device information according to the EDS file, and sequentially replace the logical station information in the XML file with the logical station information until the last sub-module information that cannot establish communication in the slave station; match the slave device information with the XML file with the logical station information, perform communication according to the description of the XML file with the logical station information, and then sequentially identify all sub-modules under this slave station according to the information of the logical station. If a slave station information that cannot be matched is encountered during the logical station recognition process, skip this sub-module and continue to execute downward until there is no slave station information response.

[0007] Preferably, the EtherNet / IP controller is equipped with an input interface. Before performing the recognition step, a recognition requirement is sent to the EtherNet / IP controller through the input interface; the EtherNet / IP controller filters the XML files according to the recognition requirement and obtains the output result according to the recognition requirement. In this way, in some cases, it is not necessary to fully parse the complete file, which can reduce the probability of recognition errors and improve the communication efficiency at the same time.

[0008] Preferably, the method for producing the EDS-XML file hybrid package is as follows: obtain the EDS file from the equipment supplier and create the XML file by oneself according to the technical documentation and relevant standards of the equipment; the XML file includes different versions of XML files for each upgrade and XML files with different amounts of information recorded in the same version; and generate an XML file with logical stations based on the latest version of the XML file. The number of logical stations recorded in the XML file with logical stations is determined by the topological combination and is always less than or equal to the number of Slots. Although this will result in a relatively large EDS-XML file hybrid package, in the actual usage process, it is not necessary to parse all the files in the EDS-XML file hybrid package, so it has little impact on the overall process time.

[0009] Preferably, when there are multiple logical stations in the XML file, the number of logical station numbers is the same as the number of physical station numbers of the device, and the station number value of the logical station is obtained by offset accumulation of the number of logical stations, which is convenient for identification and management in later applications.

[0010] Preferably, the EDS-XML file hybrid package automatically generates a file directory according to the files in the package before packaging. Through the file directory, the files to be decompressed can be found more quickly and accurately.

[0011] Preferably, the specific steps for the EtherNet / IP master station device module to perform file matching are as follows: unpack the EDS-XML file hybrid package, extract the EDS file and perform the import operation; find multiple relevant XML files from the file directory according to the identification requirements, and parse the XML files to extract the basic device information; compare the basic device information with the EDS. If an abnormality is found, an abnormality is prompted, the EDS file import is performed again and the XML file is replaced; if it is normal, continue to parse the rack information; traverse and match the rack file information. If an abnormality is found, an abnormality is prompted, the EDS file import is performed again and the XML file is replaced; if it is normal, generate the Slot scan path and the EtherNet / IP protocol specification message, and at this time, start to parse the device extension information path.

[0012] Preferably, when all the extracted basic information of the expansion device does not match, re-execute the EDS file import and replace the XML file. If the expansion device information is absent or normal, generate the access path of the expansion device information and the EtherNet / IP protocol specification message and start parsing the device parameter information. If the parameter device information is absent or normal, generate the access path of the device parameter information and the EtherNet / IP protocol specification message and perform the parsing of the device alarm information; if it is abnormal, prompt the abnormality, re-execute the EDS file import and replace the XML file; if the device alarm information is absent or normal, generate the access path of the device alarm information and the EtherNet / IP protocol specification message and perform the parsing of the process data tag information; if it is abnormal, prompt the abnormality, re-execute the EDS file import and replace the XML file; if the process data tag information is normal, the parsing is completed, if it is absent or abnormal, prompt the abnormality, re-execute the EDS file import and replace the XML file.

[0013] The above two-stage parsing steps are actually optimized designs for different judgment requirements.

[0014] Preferably, when all the corresponding XML files are abnormal, collect the abnormal information, parse the XML file with a logical station, modify the XML file with a logical station according to the abnormal information, and generate the access path of the device parameter information and the EtherNet / IP protocol specification message according to the XML file with a logical station. The XML file with a logical station exists in the initial EDS-XML file mixed package, but it cannot be directly used and needs to be modified according to the feedback of the abnormal information before it can be truly applied.

[0015] Preferably, based on the recognition requirements, the parsing paths of different types of XML files are different: to obtain the slave device information, it is necessary to parse at least the access path of the expansion device information from the slave device XML file; to determine whether there is a sub-module, it is only necessary to parse the rack information from the rack device XML file.

[0016] The present invention also includes an electronic device, including a processing unit and a storage unit. The processing unit is provided with an EtherNet / IP controller with an input interface. The storage unit records the EtherNet / IP modular information recognition method, and the EtherNet / IP modular information recognition method is executed by the processing unit.

[0017] Due to the adoption of the described technical solution, the EtherNet / IP modular information recognition method proposed by the present invention introduces the concept of logical stations, supports the dynamic adjustment of the number of logical stations according to the network topology, and the logical station numbers strictly correspond to the physical station numbers, adapting to complex network structures. Through the dynamically generated and parsed EDS-XML hybrid package, the recognition of slave station devices can be achieved without pre-setting device description files. By dynamically importing the EDS-XML hybrid package containing device information and logical station descriptions, the flexible recognition and control of slave station devices are realized, significantly improving the deployment efficiency and applicability.

[0018] Furthermore, the present invention further enhances the robustness of the system through dynamic matching and multi-layer exception handling mechanisms: it supports differential processing in full-match, partial-match, and non-match scenarios, can automatically replace logical station information, parse alarm information, and generate access paths to ensure the integrity of process data.

[0019] In addition, the present invention also relates to electronic devices, and the overall solution of the hardware integrated design exceeds the prior art in terms of versatility, flexibility, fault tolerance, and integration, and is particularly suitable for the scenario of dynamic expansion of devices in complex industrial networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings are used to provide a further understanding of the present invention, and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention, but do not constitute a limitation to the present invention. In the drawings: Figure 1 is a schematic diagram of the comparison of the recognition capabilities of the three major industrial Ethernet protocols for slave device sub-modules in the prior art.

[0021] Figure 2 is a schematic diagram of the working process of an EtherNet / IP modular information recognition method of the present invention.

[0022] Figure 3 is a schematic diagram of the file parsing comparison process of an EtherNet / IP modular information recognition method of the present invention.

[0023] Figure 4 is a schematic diagram of the SDO object acquisition and configuration in an EtherNet / IP modular information recognition method of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0024] The following describes the preferred embodiments of the present invention with reference to the drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0025] In order to clearly express the content involved in the present invention, first, the meanings of some abbreviations involved in the present invention are explained.

[0026] First, the concept of a logical station is introduced in the present invention. The logical station corresponds to the concept of a physical station. A physical station refers to a communication node that objectively exists in a physical sense in an entity topology; while a logical station is a conceptual communication node that does not objectively exist but is subjectively defined.

[0027] The logical station does not depend on specific hardware, but abstracts and encapsulates the functions of physical devices through software to form a flexibly configurable virtual node, which is very suitable for application in the scenarios described in the present invention. A physical station can contain at least one and at most an unlimited number of logical stations. The total resources occupied by a physical station are always an integer multiple of the resources of a single logical station. If it is not an integer multiple, it is rounded up. The multiple relationship between the physical station and the logical station follows the following rules: calculate the multiple relationship in 4 quadrants of 2 dimensions of uplink and downlink data, digital quantity and analog quantity data, and take the maximum.

[0028] Different from a Slot, a logical station, as a virtual device, occupies Slots. The number of Slots is fixed by the description of the Rack file, while the number of logical stations is flexibly combined according to the topology, but is always less than or equal to the number of Slots.

[0029] Taking the EtherNet / IP plug-in coupler and the plug-in IO module XB6S-3200 produced by the applicant himself as an example: The XB6S-3200 module is a 32-point digital input module, and the PDO resources it occupies are 4 Bytes of uplink digital quantity, 0 Byte of downlink digital quantity, and 0 Bytes of uplink and downlink analog quantity. When defining the resource size of a logical station as 2 Bytes for both uplink and downlink digital quantities, XB6S-3200 occupies 2 logical stations; when defining the resource size of a logical station as 4 Bytes for both uplink and downlink digital quantities, XB6S-3200 occupies 1 logical station.

[0030] The number of logical stations is restricted by factors such as the number of Slots, PDO data allocation, and the total length of PDO data. Therefore, the number of physical stations under a set of topologies is also affected by such factors. The resource size occupied by a logical station in communication is dynamically fixed, that is, the resource size of a logical station can be dynamically adjusted by the description of the XML file, but the resource size of logical stations of a series of devices should be kept fixed and consistent. Considering the performance-resource ratio, usually the number of logical stations in a device does not exceed 4.

[0031] Secondly, the relationship between slave stations, sub-slave stations, and sub-modules needs to be explained. Slave stations are directly connected to the controller and must use the Ethernet / ip protocol. Sub-slave stations, as the next layer below slave stations, can use some proprietary bus protocols. Since the node resources of the controller are generally limited, such an operation can, on the one hand, reduce costs and, on the other hand, save nodes (Slots). A sub-module can be understood as a device connected to a sub-slave station, that is, a device connected to a sub-slave station. According to different requirements, sometimes we only need to detect that there is a device on the sub-slave station, while sometimes we need to communicate with and manage the devices on the sub-slave station. The degree of generating extended access paths is different under different requirements.

[0032] The description of EtherNet / IP devices includes two description files: the EDS file and the XML file. EDS file: The EDS (Electronic Data Sheet) file, that is, the electronic data sheet file, is a file used to describe the various parameters and functions of Ethernet / IP products, such as sensors, drivers, controllers, etc. in industrial Ethernet devices. It is essentially a text file that stores the detailed information of the device in a specific format. This file is usually provided by the device vendor.

[0033] XML file: The XML (Extensible Markup Language) file is usually used to describe information such as the configuration, capabilities, and data structure of the device. The part of the XML file involved in the present invention can be generated after the configuration software on other devices reads the device information and then copied for use. But most XML files are created by technicians according to the technical documents and relevant standards of the device.

[0034] The XML file is used for the secondary description of slave station information, especially for the description of sub-module information. Compared with the device information contained in the EDS file, the XML file description is more detailed. The XML file includes three types of files: The Rack file is used to describe the slot information under this rack; the slave station file, which includes the basic device information, rack and slot information, and extended object model information; the sub-module file: includes the basic device information, rack and slot information, and extended object model information. In the present invention, different contents are also included respectively during the process of making the same type of XML file, and different XML files are generated according to possible requirements.

[0035] The present invention also relates to PDO mapping and SDO mapping. In the description object of the XML file, the extended object model information mainly includes PDO and SDO information. The core application scenario of the solution of the present invention is the industrial automation field. In industrial communication in the industrial automation field, the main types of interaction data between the controller and the slave device are PDO and SDO data. Therefore, only by breaking through the rules of these two types of data interaction from the controller to the slave to the sub-slave, the present invention has practical application significance.

[0036] PDO mapping: PDO is used for fast transmission of real-time data between devices and is a periodic or event-triggered data exchange method. PDO mapping is to map specific application objects in the device, such as sensor measurement values and actuator control parameters, into the PDO. The data transmission has real-time and high efficiency. In an industrial automation production line, data such as temperature and pressure collected by sensors in real time can be quickly transmitted to the controller through PDO mapping, and the controller can make timely responses and controls to achieve real-time monitoring and control of the device.

[0037] SDO mapping: SDO is used for parameter setting and non-periodic data access of the device. SDO mapping is to establish an association between device parameter objects, such as configuration parameters of the working mode and baud rate of the device, and the SDO. It provides a flexible way to access any object in the device object dictionary. During the device debugging phase, engineers can read and modify the configuration parameters of the device through SDO mapping to meet the actual application requirements.

[0038] Such as Figure 1As shown, the three major mainstream industrial Ethernet protocols in the prior art include EtherCAT, Ethernet / IP, and Profinet. With the increasingly fierce competition in the industrial automation market, the market has higher and higher requirements for the cost, ease of use, and maintainability of industrial Ethernet devices. Therefore, more and more automation device manufacturers choose to mount sub-modules under the protocol slave station. The main reason for automation device manufacturers to mount sub-modules under the protocol slave station is to achieve function expansion, enabling the device to meet more complex industrial control scenarios. For example, the device may originally only have basic digital input and output functions. By mounting sub-modules, analog I / O functions can be added, enabling the acquisition and control of analog signals such as temperature, pressure, and flow, which greatly expands the application scope of the device. At the same time, this method provides a high degree of flexibility. Manufacturers can configure the device by mounting sub-modules with different functions according to the personalized needs of different users. Just like an industrial robot controller mounts sub-modules such as vision recognition or end effector control to enhance the versatility and competitiveness of the device in the market. In terms of system integration, devices with mounted sub-modules can better integrate into the industrial automation system, and as multi-functional nodes, they can effectively interact with other slave station devices, master station devices, and upper-level monitoring systems for information and action coordination, making the system integration process more convenient and improving the overall performance of the system. In addition, from the perspective of cost control and device upgrade and optimization, manufacturers can first produce the core module, and then mount sub-modules according to the market and user order situations to achieve different function levels, avoiding the production of multiple complete devices with different complexities and reducing the production cost. Moreover, during the subsequent use of the device by users, the device performance can be optimized and upgraded by replacing or adding sub-modules without having to replace the entire device, saving the cost and resources of device replacement.

[0039] However, mounting sub-modules in such automated equipment brings various security risks. From the perspective of data security, the communication link and data interaction factors become complex due to the sub-modules. If there are vulnerabilities in the communication protocol or software of the sub-module, data leakage may occur. For example, hackers attack the communication interface between the sub-module and the master station, stealing sensitive production data such as product formulas and process parameters, damaging the enterprise's intellectual property rights and trade secrets. In terms of the safe operation of the equipment, the failure or malicious control of the sub-module may lead to the risk of equipment out-of-control, and in high-speed and high-precision equipment, it may even trigger serious safety accidents; moreover, the complex sub-module configuration may also cause misoperations. Due to improper software logic or parameter settings, the equipment responds incorrectly to control signals and performs incorrect actions at the wrong time. In the field of network security, each sub-module may become an entry point for malicious attacks, and the existence of sub-modules increases the difficulty of security updates. The update cycles and methods of sub-modules from different suppliers are different, making it difficult to ensure timely installation of security patches, and the equipment is easily exposed to security risks for a long time. Currently, under the EtherCAT and ProfiNet protocols, the slave device can identify sub-modules, which can effectively reduce these risks, while under the EtherNet / IP protocol, the slave device cannot identify sub-modules.

[0040] In response to this, the present invention provides a method for identifying EtherNet / IP modular information, which uses an EtherNet / IP controller. The EtherNet / IP controller is provided with an input interface, such as Figure 2As shown in the figure, the specific identification steps are as follows: Submit an identification requirement to the EtherNet / IP controller through the input interface; the EtherNet / IP controller filters the XML files according to the identification requirement, obtains the output result according to the identification requirement, and imports the corresponding EDS-XML file mixed package into the EtherNet / IP master station device module; the EDS-XML file mixed package contains at least one EDS file and multiple XML files, and at least one of the XML files contains logical station information; First, determine whether the device information recorded in the EDS file in the EDS-XML file mixed package is consistent with the device information in one of the XML files; if they are consistent, parse the successfully matched EDS file and XML file. Determine the process data communication information from the EDS file, and determine the modular information identification path and service data communication path of the slave station from the XML file. If all file parsing is normal, further parse the Rack information supported under this slave device. If the Rack supported described in the XML file of the slave station is consistent with the slave Rack, parse the PDO and SDO information access paths of all matchable Rack slave stations, and mount all supported slave stations to the corresponding slave station paths; when the matching is unsuccessful, first obtain the slave device information according to the EDS file, and replace the logical station information in the XML file with the logical station information in turn until the last sub-module information that cannot establish communication in the slave station; match the slave device information with the XML file with the logical station information, execute communication according to the description of the XML file with the logical station information, and then identify all sub-modules under this slave station in turn according to the information of the logical station. If slave station information that cannot be matched is encountered during the logical station identification process, this sub-module will be skipped and the process will continue until there is no slave station information response.

[0041] The method for making the EDS-XML file mixed package is as follows: Obtain the EDS file from the device supplier, and create the XML file by yourself according to the technical documentation and relevant standards of the device; the XML file includes different versions of XML files for each upgrade and XML files with different amounts of information recorded in the same version; and generate an XML file with a logical station based on the latest version of the XML file. The number of logical stations recorded in the XML file with a logical station is based on the topology combination and is always less than or equal to the Slot number. When there are multiple logical stations in the XML file, the number of logical station numbers is the same as the number of physical station numbers of the device, and the station number value of the logical station is accumulated by offsetting the number of logical stations. The EDS-XML file mixed package automatically generates a file directory according to the files in the mixed package before packaging.

[0042] As Figure 3As shown in the figure, the specific steps for the EtherNet / IP master device module to perform file matching are as follows: Unzip the EDS-XML file mixed package, extract the EDS file and perform the import operation; find multiple relevant XML files from the file directory according to the recognition requirements, and parse the XML files to extract the basic device information; compare the basic device information with the EDS. If an abnormality is found, an abnormality is prompted, and the EDS file import is restarted and the XML file is replaced; if it is normal, continue to parse the rack information; traverse and match the rack file information. If an abnormality occurs, an abnormality is prompted, and the EDS file import is restarted and the XML file is replaced; if it is normal, generate the Slot scan path and the EtherNet / IP protocol specification message, and at this time, start to parse the extended device information path. When all the extracted extended device basic information matches abnormally, restart the EDS file import and replace the XML file; if there is no extended device information or it is normal, generate the extended device information access path and the EtherNet / IP protocol specification message and start to parse the device parameter information. If the parameter device information is absent or normal, generate the device parameter information access path and the EtherNet / IP protocol specification message; if it is abnormal, perform the device alarm information parsing. When all the corresponding XML files are abnormal, collect the abnormal information, parse the XML file with the logical station, modify the XML file with the logical station according to the abnormal information, and generate the device parameter information access path and the EtherNet / IP protocol specification message according to the XML file with the logical station. After the XML file with the logical station generates the device parameter information access path and the EtherNet / IP protocol specification message, perform the process data label information processing: parse the process data label information; if there is no abnormality in the process data label information, the process ends; if it is abnormal, an abnormality is prompted, and at this time, the information recognition fails. Based on the recognition requirements, the parsing paths of different types of XML files are different: To obtain the slave device information, it is necessary to parse at least to the extended device information access path from the slave device XML file; to determine whether there is a sub-module, it is only necessary to parse the rack device XML file to the rack information.

[0043] It should be noted that the present invention has the step of putting forward the recognition requirement to the EtherNet / IP controller through the input interface. This is because due to different recognition requirements, the actual recognition degree requirements are also different. This difference can be further explained in the specific implementation manner.

[0044] The present invention does not provide a definite usage model for the EtherNet / IP object model, but rather provides a relatively vague usage model, that is, it defines a set of usage rules for the object model without fixing the objects used under the rules. In the EtherNet / IP object model, some objects have fixed their specific usage scenarios and meanings as protocol standards. The object model usage rules of this invention are only applicable to the objects that are open for use in the protocol. This can make the application development under the solution of this invention more convenient and fast, the application is also more extensive, and the application in the EtherNet / IP communication network is also more secure, that is, it conforms to the object model specification of the EtherNet / IP protocol and can avoid possible conflicts in the application of object models among different EtherNet / IP devices.

[0045] Based on a kind of EtherNet / IP modular information recognition method recorded in the present invention, the present invention can further realize the identification and management of sub-modules in subsequent specific embodiments, so as to realize further functions.

[0046] Embodiment 1: Background of the implementation of the sub-module upgrade compatibility function and the basic upgrade compatibility function: When the EtherNet / IP controller cannot recognize the sub-module under the slave station, the EtherNet / IP controller cannot perceive the functional design and its compatibility issues of the module, and even the user cannot intuitively perceive the differences after the sub-module upgrade or the differences in functions during use. Therefore, in the past sub-module upgrades, generally additional solutions or tools were required to reflect the differences between the new and old versions of the sub-module. From the user usage level and the device operation level, compatibility issues could not be considered.

[0047] In the technical solution provided by the present invention, the product version of the sub-module is strictly bound to the XML version. Therefore, when the EtherNet / IP controller recognizes the sub-module, the corresponding version information will also be matched. With this technical basis, a solution to the compatibility problem of sub-module upgrades is also available. In the present invention, non-critical iterations of the sub-module are first considered. At this time, only the software version of the sub-module is updated, and the functional differences of the module itself are not significant. Generally, it is an upgrade such as bug fixing and performance improvement. At this time, the version iteration of the sub-module is limited to the software version, and the XML file itself does not need to be modified, and there is no compatibility problem at this time. When there are significant functional changes or iterations in the sub-module that require modifying the XML file for adaptation, the product version in the sub-module device information can be iterated, and the corresponding XML file can be iterated accordingly to keep the product version consistent with the XML version, and the XML is installed in the EtherNet / IP master upper computer. When recognizing the sub-module, match the product version and XML version of the sub-module and match a series of information such as PDO and SDO, such asFigure 4 As shown, even if information such as the model number and product code of the sub-module is the same, it can be distinguished by the version information, thus realizing the compatibility upgrade of sub-modules of the same model. If there are indeed sub-modules that cannot be recognized, the logical station information in the XML file with logical station information is used to sequentially replace the unrecognized sub-modules in the slave station, so as to ensure communication based on the information of the logical station. In this embodiment, traversing and matching the rack file information is sufficient to support the upgrade behavior.

[0048] Embodiment 2: Expansion logic of process data volume: In the protocol specification of the EtherNet / IP protocol, the maximum PDO data volume for opening a CIP I / O connection with the general Forward Open instruction is 504 Bytes. In some special application scenarios, 504 Bytes of data volume is far from enough. For example, the intervention of special function sub-modules such as some motion control and serial communication causes a sharp increase in the process data volume of CIP I / O. To solve this problem, the EtherNet / IP protocol also specifies the Large Forward Open connection opening command. Under this command, the total data volume of CIP I / O can reach 65535 Bytes. When this connection instruction is supported, the problem of data volume expansion in the EtherNet / IP link can be solved.

[0049] Mapping logic of process data volume: In the modular solution, when using Large Forward Open to expand the process data, the PDO mapping logic of each sub-module is different from the processing measures of the Forward Open instruction. When expanding the process data volume, the basic idea is still to regard the overall process data as a whole. The difference is that in the original ForwardOpen instruction, a fixed maximum of 504 Bytes of data volume is treated as a whole, while in the expansion instruction, the total process data resources actually occupying the logical station quantity are treated as a fixed maximum quantity as a whole. That is to say, under different topologies, the size of the overall data volume is different. At this time, the partitioning of digital process data and analog process data is no longer allocated according to a fixed ratio, but according to the actual resource occupation quantity of the logical station. Correspondingly, in this embodiment, a complete sub-module identification process needs to be completed.

[0050] It should be noted that in the field of industrial Internet, logical station is a widely used technology. Its core goal is to aggregate scattered industrial equipment, data flow and control logic into a whole. However, in the scenario involved in the present invention, that is, most of the EtherNet / IP protocol controllers can only reach the slave station itself when identifying, configuring and controlling the EtherNet / IP slave station, and cannot identify the sub-module mounted on the slave station, the existing technology cannot configure the logical station normally. The present invention obtains sufficient information for configuring the logical station through the feedback after the failure of the previous EDS-XML file mixed package configuration, thereby configuring the XML file with the logical station information. In this way, the above-mentioned technical effect can be achieved.

[0051] Although the present invention is disclosed as above with preferred embodiments, it is not intended to limit the scope of the present invention. Any person of ordinary skill in the art can make some improvements without departing from the scope of the present invention, that is, all equivalent improvements made in accordance with the present invention should be covered by the scope of the present invention. In the description of this specification, the description of reference terms "an embodiment / method", "some embodiments / methods", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment / method or example are included in at least one embodiment / method or example of the present application. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment / method or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments / methods or examples in a suitable manner. In addition, without contradicting each other, a person of ordinary skill in the art can combine and combine the different embodiments / methods or examples described in this specification and the features of different embodiments / methods or examples.

[0052] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0053] Those skilled in the art should understand that the above embodiments are only for the purpose of clearly illustrating the present disclosure, and are not intended to limit the scope of the present disclosure. For those skilled in the art, other changes or modifications may be made based on the above disclosure, and these changes or modifications are still within the scope of the present disclosure.

Claims

1. An EtherNet / IP modular information recognition method, characterized in that An EtherNet / IP controller is adopted. The specific identification steps are as follows: import the corresponding EDS-XML file mixed package into the EtherNet / IP master device module through the EtherNet / IP controller; the EDS-XML file mixed package contains at least one EDS file and multiple XML files, and at least one of the XML files contains logical station information; first, judge whether the device information recorded in the EDS file in the EDS-XML file mixed package is consistent with that in one of the XML files; if they are consistent, parse the successfully matched EDS file and XML file; if all files are parsed normally, further parse the Rack information supported under this sub-module. If the Rack supported described in the XML file of the slave sub-station is consistent with the slave station Rack, parse the PDO and SDO information access paths from all the XMLs of the Rack slave sub-stations that can be matched, and mount all the supported slave sub-stations to the corresponding slave station paths; when the matching is unsuccessful, first obtain the slave station device information according to the EDS file, and sequentially replace the information of the first sub-module that cannot establish communication in the slave station with the logical station information in the XML file with logical station information until the information of the last sub-module that cannot establish communication in the slave station. Match the slave station device information with the XML file with logical station information, execute communication according to the description of the XML file with logical station information, and then sequentially identify all sub-modules under this slave station according to the information of the logical station. If the information of a slave sub-station that cannot be matched is encountered during the identification of the logical station, skip this sub-module and continue to execute downward until there is no response from the slave sub-station information.

2. The EtherNet / IP modular information recognition method according to claim 1, characterized in that The EtherNet / IP controller is equipped with an input interface. Before executing the identification steps, an identification requirement is sent to the EtherNet / IP controller through the input interface; the EtherNet / IP controller filters the XML files according to the identification requirement and obtains the output result according to the identification requirement.

3. The EtherNet / IP modular information recognition method according to claim 1 or 2, characterized in that The method for making the EDS-XML file mixed package is as follows: obtain the EDS file from the device supplier, and create the XML file by yourself according to the technical documentation and relevant standards of the device; the XML file includes different versions of XML files for each upgrade and XML files with different amounts of information recorded in the same version; and generate an XML file with a logical station based on the latest version of the XML file. The number of logical stations recorded in the XML file with a logical station is based on the topology combination and is always less than or equal to the Slot number.

4. The EtherNet / IP modular information recognition method according to claim 3, characterized in that When there are multiple logical stations in the XML file, the number of logical station numbers is the same as the number of physical station numbers of the device, and the station number value of the logical station is accumulated by offset from the number of logical stations.

5. The EtherNet / IP modular information recognition method according to claim 3, wherein Before packaging, the EDS-XML file mixed package automatically generates a file directory according to the files in the mixed package.

6. The EtherNet / IP modular information recognition method according to claim 5, characterized in that The specific steps for the EtherNet / IP master device module to perform file matching are as follows: Unzip the EDS-XML file mixed package, extract the EDS file and perform the import operation; find multiple relevant XML files from the file directory according to the recognition requirements, and parse the XML files to extract the basic device information; compare the basic device information with the EDS. If an abnormality is found, an abnormality is prompted, the EDS file import is re-executed and the XML file is replaced; if it is normal, continue to parse the rack information; traverse and match the rack file information. If an abnormality occurs, an abnormality is prompted, the EDS file import is re-executed and the XML file is replaced. If it is normal, generate the Slot scan path and the EtherNet / IP protocol specification message, and at this time start to parse the device extension information path.

7. The method for identifying EtherNet / IP modular information according to claim 6, characterized in that, When all the extracted extended device basic information matches abnormally, re-execute the EDS file import and replace the XML file; if the extended device information is absent or normal, generate the extended device information access path and the EtherNet / IP protocol specification message and start to parse the device parameter information. If the parameter device information is absent or normal, generate the device parameter information access path and the EtherNet / IP protocol specification message and perform the device alarm information parsing; if it is abnormal, an abnormality is prompted, the EDS file import is re-executed and the XML file is replaced; if the device alarm information is absent or normal, generate the device alarm information access path and the EtherNet / IP protocol specification message and perform the process data label information parsing; if it is abnormal, an abnormality is prompted, the EDS file import is re-executed and the XML file is replaced; if the process data label information is normal, the parsing is completed. If it is absent or abnormal, an abnormality is prompted, and the EDS file import is re-executed and the XML file is replaced.

8. The method for EtherNet / IP modular information recognition according to claim 7, characterized in that, When all the corresponding XML files are abnormal, collect the abnormal information, parse the XML file with the logical station, modify the XML file with the logical station according to the abnormal information, and generate the device parameter information access path and the EtherNet / IP protocol specification message according to the XML file with the logical station.

9. The EtherNet / IP modular information recognition method according to claim 5, wherein Based on the recognition requirements, the parsing paths of different types of XML files are different: To obtain the slave device information, it is necessary to parse at least to the extended device information access path from the slave device XML file; to determine whether there is a sub-module, it is only necessary to parse the rack information from the rack device XML file.

10. An electronic device, characterized in that: It includes a processing unit and a storage unit. The processing unit is provided with an EtherNet / IP controller with an input interface. The storage unit records the EtherNet / IP modular information recognition method as described in any one of claims 1-9, and the EtherNet / IP modular information recognition method is executed by the processing unit.

Images