Ethercat bus device communication configuration method and system

Abstract

The application discloses an EtherCAT bus device communication configuration method and system, and relates to the technical field of bus communication, which comprises the following steps: under the premise of ensuring the connection of an EtherCAT bus device and the existence of an ESI file, starting an EtherCAT bus tool, scanning a bus to generate a topology file and a topology graph, selecting a device or a number which needs to generate a configuration file according to the topology graph, scanning and displaying a device communication data structure, and saving preview content to the configuration file; if there is no device information, generating a configuration file by using the ESI file, selecting a device type, screening a communication group for the configuration file, screening and updating the communication group for a multi-communication group device, providing SDO group insertion and PDO group SDO deletion functions, and after generating the configuration file, modifying and checking, including PDO screening, SDO adding and automatic checking and error correction. The application can quickly and accurately generate a communication file of an EtherCAT device, realizes device configuration and adaptation, reduces the misoperation behavior in manual operation, and can add different PDO groups according to needs and increase SDO to a PDO communication group.

Description

Technical Field

[0001] The present invention relates to the field of bus communication technology, and in particular to an EtherCAT bus device communication configuration method and system. Background Art

[0002] Fieldbuses, as the foundation of automated communication, connect production processes and control devices to each other, as well as to higher-level control and management layers. In the field of bus communication, EtherCAT (Ethernet Control and Automation Technology) is a highly flexible real-time industrial Ethernet protocol. EtherCAT uses the same physical and data link layers. The master sends data, and data frames pass through each device node in turn. Device nodes can only forward data frames and read or write data specific to that device node. This data transmission and read / write mode significantly improves bus bandwidth utilization and reduces transmission latency. Before a host computer can communicate with a device, device communication configuration is often required to ensure accurate data communication.

[0003] The current EtherCAT bus device communication configuration method mainly relies on manual configuration, which is not only inefficient but also prone to errors. Common problems include: complex topology, diverse device types, inconsistent data group configuration, and lack of automated error correction mechanisms. These problems increase the difficulty of device debugging and maintenance and extend the system debugging cycle. Deficiencies of existing technologies: Low manual configuration efficiency: The current configuration method mainly relies on manual operation and lacks support from automated tools, resulting in low configuration efficiency; prone to errors: During the manual configuration process, errors are prone to occur in device connection, data structure selection, and configuration file generation, increasing the difficulty of debugging; lack of automated checking and error correction: The existing methods lack automated checking and error correction functions, making it difficult to detect and correct configuration errors in a timely manner; no support for simulation testing: It is difficult to perform simulation testing without actual device connection, which increases the risk and cost of debugging. Summary of the Invention

[0004] Based on the above-mentioned shortcomings of the prior art, the purpose of the present invention is to provide an EtherCAT bus device communication configuration method and system to solve the above-mentioned technical problems.

[0005] To achieve the above object, the present invention provides the following technical solution: a method for configuring EtherCAT bus device communication, comprising:

[0006] S1: Ensure that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer;

[0007] S2: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology diagram containing bus devices based on the topology file; in the device selection interface, select the device or number for which the configuration file needs to be generated based on the topology diagram, and scan the bus communication data structure of the selected device to display it in the data box and preview box; save the preview content to the configuration file;

[0008] S3: In the absence of device information obtained through bus scanning, the configuration file is generated using the ESI file provided by the device manufacturer;

[0009] S4: When selecting the device type, confirm whether the device is an IO device or a servo drive device;

[0010] S5: When the device has more than one communication group, filtering the device communication group so that the selected communication group and its data structure are used for the configuration file;

[0011] S6: For a device having multiple RxPDO communication groups or TxPDO communication groups, the RxPDO communication group or TxPDO communication group is filtered, and the selected RxPDO communication group or TxPDO communication group and data structure are updated to the display box;

[0012] S7: Provides the function of inserting SDO groups, allowing users to add selected SDOs to the PDO group and delete SDOs in the PDO group;

[0013] S8: After the configuration file is generated, it provides modification and inspection functions, including re-screening of PDOs, re-adding of SDOs, and automatic inspection and error correction of the configuration file. The configuration file can be saved after confirmation.

[0014] The present invention is further configured such that step S2 also includes S21: in the device selection interface, clicking the scan device button to scan the bus communication data structure of the selected numbered device, and displaying relevant information in the data box and the preview box.

[0015] The present invention is further configured such that step S5 further includes S51: searching for the definition of the corresponding SDO in the ESI file by inputting the SDO address, and adding it to the PDO communication after confirmation to meet different control purposes and data requirements.

[0016] The present invention is further configured such that the method provides software implementation, including a Windows operating system version and a Linux operating system version, which are applicable to different operating system environments.

[0017] The present invention is further configured such that after the configuration file is generated, the PDO can be revoked for re-screening and the SDO can be deleted for re-adding by providing a modification function, and the configuration file can be automatically displayed for error correction by utilizing a check function.

[0018] The present invention is further configured such that the method also provides a simulation usage function, in which the generation and use of a communication configuration file is simulated only through an ESI file without actually connecting to an EtherCAT bus device.

[0019] The present invention also provides an EtherCAT bus device communication configuration system, the system comprising:

[0020] Connection module: Ensures that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer;

[0021] First generation module: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology diagram containing bus devices based on the topology file; in the device selection interface, select the device or number for which to generate a configuration file based on the topology diagram, and scan the bus communication data structure of the selected device to display it in the data box and preview box; save the preview content to the configuration file;

[0022] The second generation module: in the absence of device information obtained through bus scanning, the configuration file is generated using the ESI file provided by the device manufacturer;

[0023] Select type module: When selecting the device type, confirm whether the device is an IO device or a servo drive device;

[0024] A first filtering module: when a device has more than one communication group, filtering the device communication group so that the selected communication group and its data structure are used for the configuration file;

[0025] The second screening module: for a device with multiple RxPDO communication groups or TxPDO communication groups, screening the RxPDO communication groups, and being able to update the selected RxPDO communication group and its data structure to the display box;

[0026] Insert module: provides the function of inserting SDO groups, allowing users to add selected SDOs to PDO groups and delete SDOs in PDO groups;

[0027] Modification and inspection module: After the configuration file is generated, it provides modification and inspection functions, including re-screening of PDO, re-adding of SDO, and automatic inspection and error correction display of the configuration file, and saves the file after confirmation.

[0028] The present invention provides an EtherCAT bus device communication configuration method and system. The method ensures that an EtherCAT bus device is connected on the bus or has an ESI file provided by a device manufacturer; starts an EtherCAT bus tool, selects a configuration file generation function, scans the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generates a topology map containing bus devices based on the topology file; in a device selection interface, selects a device or number for which a configuration file needs to be generated based on the topology map, scans the bus communication data structure of the selected device to display it in a data box and a preview box; saves the preview content to the configuration file; in the absence of device information obtained through bus scanning, generates a configuration file using the ESI file provided by the device manufacturer; when selecting a device type, confirms whether the device is an IO device or a servo drive device; when a device has more than one communication group, filters the device communication group so that the selected communication group and its data are displayed in the data box and the preview box; The data structure is used for configuring a configuration file; for a device with multiple RxPDO communication groups or TxPDO communication groups, the RxPDO communication groups or TxPDO communication groups are filtered, and the selected RxPDO communication group or TxPDO communication group and the data structure can be updated to the display box; a function of inserting an SDO group is provided, allowing the user to add a selected SDO to the PDO group, and to delete the SDO in the PDO group; after the configuration file is generated, a modification and inspection function is provided, including re-screening of PDOs, re-addition of SDOs, and automatic inspection and error correction display of the configuration file, and the configuration file is saved after confirmation. The beneficial effects produced include: an EtherCAT bus device communication configuration method proposed by the present invention can quickly and accurately generate a communication file for an EtherCAT device, can realize rapid device configuration and adaptation, reduce erroneous operation behaviors in human operation, and can add different PDO groups as needed, and add SDOs to the PDO communication group.

[0029] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without inventive efforts. In the drawings:

[0031] Figure 1A flowchart of an EtherCAT bus device communication configuration method is shown as an exemplary embodiment of the present invention;

[0032] Figure 2 This is a device topology connection diagram interface diagram illustrating an EtherCAT bus device communication configuration method according to an exemplary embodiment of the present invention;

[0033] Figure 3 This is an interface diagram of a PDO communication group screening method for configuring communication of an EtherCAT bus device, shown as an exemplary embodiment of the present invention;

[0034] Figure 4 This is a diagram illustrating an interface for defining a search object for an EtherCAT bus device communication configuration method according to an exemplary embodiment of the present invention;

[0035] Figure 5 This is an interface diagram of inserting an SDO object into a PDO group of an EtherCAT bus device communication configuration method according to an exemplary embodiment of the present invention;

[0036] Figure 6 A pop-up interface diagram of selecting a device type in a method for configuring EtherCAT bus device communication according to an exemplary embodiment of the present invention;

[0037] Figure 7 This is a diagram illustrating an interface for selecting a device group in an EtherCAT bus device communication configuration method according to an exemplary embodiment of the present invention;

[0038] Figure 8 A flowchart of a PDO group screening method for configuring communication of an EtherCAT bus device is shown as an exemplary embodiment of the present invention;

[0039] Figure 9 A flowchart of inserting an SDO group of an EtherCAT bus device communication configuration method according to an exemplary embodiment of the present invention is shown;

[0040] Figure 10 The present invention is a schematic structural diagram of an EtherCAT bus device communication configuration system according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0041] The following describes the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the various details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.

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

[0043] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring the embodiments of the present invention.

[0044] Example 1

[0045] A method for configuring EtherCAT bus device communication, such as Figure 1 Shown, including:

[0046] S1: Ensure that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer;

[0047] S2: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology map containing the bus devices based on the topology file. By automatically scanning the bus and generating a topology file and a topology map containing the connection structure of all devices, users can intuitively view the connection status of bus devices, which helps to quickly identify and select the devices that need to be configured; Figure 2The device topology connection diagram interface shown in the figure shows the connection structure of all devices in the bus, which is convenient for users to intuitively select the devices that need to be configured; in the device selection interface, the device or number for which the configuration file needs to be generated is selected according to the topology diagram, and the bus communication data structure of the selected device is scanned to display in the data box and preview box; the present invention is further configured so that step S2 also includes S21: in the device selection interface, by clicking the scan device button to scan the bus communication data structure of the device with the selected number, and display the relevant information in the data box and preview box. Save the preview content to the configuration file, and the user can directly select the device or number to be configured on the topology diagram through the device selection interface. The system will automatically scan and display the bus communication data structure of the selected device, simplifying the process of device selection and data acquisition; Figure 4 The interface diagram for searching object definitions is shown; it allows users to search and confirm specific communication objects when generating configuration files.

[0048] S3: In the absence of device information obtained through bus scanning, use the ESI file provided by the device manufacturer to generate a configuration file; specifically, in some cases, the EtherCAT bus tool may not be able to obtain detailed device information by scanning the bus. This usually occurs when the device has not yet been connected to the bus or the device cannot be identified by the bus tool; to solve this problem, the ESI (EtherCAT Slave Information) file provided by the device manufacturer can be used. The ESI file is an XML file containing detailed device information. It is provided by the device manufacturer. The user can import the ESI file into the EtherCAT bus tool, and the tool will generate the device configuration file based on the information in the ESI file. Using the ESI file provided by the device manufacturer can solve the problem of not being able to obtain device information through bus scanning, thereby improving the compatibility and flexibility of the system.

[0049] S4: When selecting the device type, confirm whether the device is an IO device or a servo drive device; Figure 6 The pop-up interface diagram of selecting device type is shown. Figure 6 A pop-up window for selecting the device type is displayed. When configuring the device, the user needs to select the device type based on the actual situation. The interface provides two buttons, "Servo Device" and "IO or Other Device". The user selects according to the actual connected device type to ensure the accuracy of the device type information in the configuration file. By clarifying the device type, the device type information in the configuration file is ensured to be consistent with the actual device, thereby improving the accuracy of the configuration file.

[0050] S5: When the device has more than one communication group, filter the device communication group so that the selected communication group and its data structure are used for the configuration file; the present invention is further configured such that step S5 also includes S51: searching for the definition of the corresponding SDO in the ESI file by inputting the SDO address, and adding it to the PDO communication after confirmation to meet different control purposes and data requirements. Figure 7 As shown in the interface diagram of selecting device group, Figure 7 An interface for selecting devices is displayed. When the scanned file contains multiple devices, the user can select a device from which to generate a configuration file. The interface lists all scanned devices, and detailed information such as the name, EtherCAT type, version information, and product code of each device are displayed in the list. The user can select one of the devices and click the "Confirm" button to continue generating the configuration file. By providing a detailed device list, the user can accurately select the device to be configured based on actual needs and device information, ensuring the pertinence and accuracy of the configuration file. Detailed information such as the device name, type, version, and product code are provided, allowing users to quickly identify and select the required device and avoid misoperation.

[0051] S6: For a device with multiple RxPDO communication groups or TxPDO communication groups, filter the RxPDO communication group or TxPDO communication group, and be able to update the selected RxPDO communication group or TxPDO communication group and data structure to the display box; Figure 3 As shown in the interface diagram for filtering PDO communication groups, users can select the reserved TxPDO or RxPDO group number and add, delete or insert SDO groups. The selected PDO group and its data structure will be updated in real time in the display box, providing the function of selecting and filtering RxPDO or TxPDO communication groups. Users can flexibly configure different communication groups according to the specific needs of the device, which improves the flexibility and adaptability of the configuration. Figure 3 The user can easily add, delete or insert SDO groups through the interface, making the configuration of PDO communication groups more intuitive and convenient; Figure 8 The flowchart for filtering PDO groups shown in the figure includes the following steps: importing ESI files, selecting device types, selecting device groups, filtering PDO groups (including RxPDO and TxPDO), and finally confirming the filtering results. Through the above logic, the selection and filtering of multiple RxPDO and TxPDO communication groups are supported, which meets the configuration requirements of different devices and application scenarios, improves the versatility and applicability of the system, and can be accurately configured through this step for both simple and complex devices, ensuring the compatibility and scalability of the system.

[0052] S7: Provides the function of inserting SDO groups, allowing users to add selected SDOs to the PDO group and delete SDOs in the PDO group; Figure 5 As shown in the Insert SDO Object to PDO Group interface, users can select available SDOs on the left side of the interface and add them to the selected PDO group on the right side, or delete SDOs from the selected PDO group; Figure 9 The flowchart for inserting an SDO group is shown in the figure. The specific steps include: selecting Insert SDO Group in the PDO Filtering interface, displaying writable SDOs and readable SDOs, adding SDOs to the RxPDO group or TxPDO group as needed, and confirming the addition or closing. By using the SDO Group Insertion function, users can flexibly add the selected SDO to the corresponding PDO group according to specific needs, ensuring that the configuration file can accurately reflect the communication requirements of the device.

[0053] S8: After the configuration file is generated, it provides modification and inspection functions, including re-screening PDOs, re-adding SDOs, and automatic configuration file inspection and error correction display. The configuration file is saved after confirmation. Specifically, after generating the configuration file, the user can re-screen PDOs as needed to ensure that the PDO group configuration meets the latest requirements or modifications. After the configuration file is generated, the user can re-add or delete SDOs to ensure the accuracy and completeness of the SDO configuration. The system provides automatic configuration file inspection function to identify and correct errors in the configuration. Inspection includes but is not limited to data consistency, parameter correctness, and communication settings. After confirming the modification and inspection results, the user can save the final configuration file to ensure the validity and reliability of the configuration file.

[0054] The present invention is further configured as follows: the method provides software implementation, including Windows operating system version and Linux operating system version, which is applicable to different operating system environments. Specifically, the software tool provides Windows operating system version and Linux operating system version to ensure that it can run in different operating system environments. Windows and Linux are two common operating systems that cover most application environments of industrial automation and control systems, ensuring the wide applicability of the software.

[0055] The present invention is further configured such that after the configuration file is generated, the PDO can be revoked for re-screening and the SDO can be deleted for re-adding by providing a modification function, and the configuration file can be automatically displayed for error correction by utilizing a check function.

[0056] The present invention is further configured such that the method also provides a simulation usage function. In the absence of an actual connection to an EtherCAT bus device, the generation and use of a communication configuration file is simulated only through an ESI file. Specifically, the software tool provides a simulation function. Even in the absence of an actual connection to an EtherCAT bus device, the user can use this function to generate and test the configuration file. Through the ESI file simulation, the user can import the ESI (EtherCAT Slave Information) file provided by the device manufacturer. The software will simulate and generate a communication configuration file based on the information in the ESI file. The user can test and verify the generated configuration file in a simulation environment to ensure the correctness and integrity of the configuration file.

[0057] Example 2

[0058] See also Figure 10 , the exemplary EtherCAT bus device communication configuration system includes:

[0059] Connection module: Ensures that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer;

[0060] First generation module: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology diagram containing bus devices based on the topology file; in the device selection interface, select the device or number for which to generate a configuration file based on the topology diagram, and scan the bus communication data structure of the selected device to display it in the data box and preview box; save the preview content to the configuration file;

[0061] The second generation module: in the absence of device information obtained through bus scanning, the configuration file is generated using the ESI file provided by the device manufacturer;

[0062] Select type module: When selecting the device type, confirm whether the device is an IO device or a servo drive device;

[0063] A first filtering module: when a device has more than one communication group, filtering the device communication group so that the selected communication group and its data structure are used for the configuration file;

[0064] The second screening module: for a device with multiple RxPDO communication groups or TxPDO communication groups, screening the RxPDO communication groups, and being able to update the selected RxPDO communication group and its data structure to the display box;

[0065] Insert module: provides the function of inserting SDO groups, allowing users to add selected SDOs to PDO groups and delete SDOs in PDO groups;

[0066] Modification and inspection module: After the configuration file is generated, it provides modification and inspection functions, including re-screening of PDO, re-adding of SDO, and automatic inspection and error correction display of the configuration file, and saves the file after confirmation.

[0067] It should be noted that the EtherCAT bus device communication configuration system provided in the above embodiment and the EtherCAT bus device communication configuration method provided in the above embodiment are based on the same concept. The specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here. In actual applications, the EtherCAT bus device communication configuration system provided in the above embodiment can, as needed, allocate the above functions to different functional modules, i.e., divide the internal structure of the system into different functional modules to complete all or part of the functions described above. This is not a limitation herein.

[0068] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. 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 a wired (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0069] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0070] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0071] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0072] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0073] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0074] In the several embodiments provided in this application, it should be understood that the disclosed system can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0075] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0076] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0077] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0078] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for configuring EtherCAT bus device communication, characterized in that: include: S1: Ensure that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer; S2: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology diagram containing bus devices based on the topology file; in the device selection interface, select the device or number for which the configuration file needs to be generated based on the topology diagram, and scan the bus communication data structure of the selected device to display it in the data box and preview box; save the preview content to the configuration file; S3: In the absence of device information obtained through bus scanning, the configuration file is generated using the ESI file provided by the device manufacturer; S4: When selecting the device type, confirm whether the device is an IO device or a servo drive device; S5: When the device has more than one communication group, filtering the device communication group so that the selected communication group and its data structure are used for the configuration file; S6: For a device having multiple RxPDO communication groups or TxPDO communication groups, the RxPDO communication group or TxPDO communication group is filtered, and the selected RxPDO communication group or TxPDO communication group and data structure are updated to the display box; S7: Provides the function of inserting SDO groups, allowing users to add selected SDOs to the PDO group and delete SDOs in the PDO group; S8: After the configuration file is generated, it provides modification and inspection functions, including re-screening of PDOs, re-adding of SDOs, and automatic inspection and error correction of the configuration file. The configuration file can be saved after confirmation.

2. The EtherCAT bus device communication configuration method according to claim 1, wherein: Step S2 also includes S21: in the device selection interface, clicking the Scan Device button to scan the bus communication data structure of the selected numbered device, and displaying relevant information in the data box and the preview box.

3. The EtherCAT bus device communication configuration method according to claim 1, wherein: Step S5 also includes S51: searching for the definition of the corresponding SDO in the ESI file by inputting the SDO address, and adding it to the PDO communication after confirmation to meet different control purposes and data requirements.

4. The EtherCAT bus device communication configuration method according to claim 1, wherein: The software implementation forms of the method include Windows operating system version and Linux operating system version, which are suitable for different operating system environments.

5. The EtherCAT bus device communication configuration method according to claim 1, wherein: After the configuration file is generated, the modification function can be used to cancel PDOs for re-screening, delete SDOs for re-adding, and the check function can be used to automatically display error corrections on the configuration file.

6. An EtherCAT bus device communication configuration method according to any one of claims 1 to 5, characterized in that: This method also provides a simulation function, which simulates the generation and use of communication configuration files only through ESI files without actually connecting to EtherCAT bus devices.

7. An EtherCAT bus device communication configuration system, characterized in that: include: Connection module: Ensures that the EtherCAT bus device is connected to the bus or has the device ESI file provided by the device manufacturer; First generation module: Start the EtherCAT bus tool, select the configuration file generation function, scan the bus to generate a topology file containing the topological connection structure of all devices in the bus, and generate a topology diagram containing bus devices based on the topology file; in the device selection interface, select the device or number for which to generate a configuration file based on the topology diagram, and scan the bus communication data structure of the selected device to display it in the data box and preview box; save the preview content to the configuration file; The second generation module: in the absence of device information obtained through bus scanning, the configuration file is generated using the ESI file provided by the device manufacturer; Select type module: When selecting the device type, confirm whether the device is an IO device or a servo drive device; A first filtering module: when a device has more than one communication group, filtering the device communication group so that the selected communication group and its data structure are used for the configuration file; The second screening module: for a device with multiple RxPDO communication groups or TxPDO communication groups, screening the RxPDO communication groups, and being able to update the selected RxPDO communication group and its data structure to the display box; Insert module: provides the function of inserting SDO groups, allowing users to add selected SDOs to PDO groups and delete SDOs in PDO groups; Modification and inspection module: After the configuration file is generated, it provides modification and inspection functions, including re-screening of PDO, re-adding of SDO, and automatic inspection and error correction display of the configuration file, and saves the configuration file after confirmation.

Images