Method and system for managing industrial switches

Abstract

This application relates to the field of communication technology, and in particular to a management method and system for industrial switches. The method includes: acquiring characteristic information and configuration information of each industrial Ethernet switch to generate its own switch file; modeling the switch based on the switch file to generate a corresponding switch model; compiling each switch model and inputting it into a PLC controller, so that the PLC controller outputs management messages to control each industrial switch; wherein the management messages are obtained by the PLC controller processing based on the switch model. The management method of this application can manage the functions and parameters of industrial switches through an Ethernet / IP bus, effectively reducing management costs.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a management method and system for an industrial switch. Background Technology

[0002] Industrial Ethernet switches are specifically designed to meet the flexible and ever-changing needs of industrial applications, providing a cost-effective industrial Ethernet communication solution. Existing industrial switches are generally managed through the following methods:

[0003] First, management via serial port. This method connects via serial port, and the switch provides a menu-driven console interface or command-line interface through the serial port, allowing management of the switch via corresponding buttons or command lines.

[0004] Second, management can be done via the web. This method involves managing the switch through a web browser. The switch is accessed via an IP address, which then pops up a corresponding web page for management.

[0005] Third, management via network management software. This method uses the SNMP (Simple Network Management Protocol) to manage the switches. By simply installing SNMP network management software on a network management station, industrial switches on the local area network can be managed. Summary of the Invention

[0006] In view of the above-mentioned technology, this application proposes a management method and system for industrial switches.

[0007] This application provides a management method for an industrial switch, applied to a host computer, including:

[0008] Obtain the characteristic and configuration information of each industrial Ethernet switch to generate its own switch file;

[0009] Based on the switch file, perform switch modeling to generate the corresponding switch model;

[0010] Each of the aforementioned switch models is compiled and input into the PLC controller, so that the PLC controller outputs management messages to control each of the aforementioned industrial switches;

[0011] The management message is obtained by the PLC controller based on the switch model.

[0012] Furthermore, in the above-described management method for industrial switches, the management message includes relevant data such as the version data of the industrial switch, communication cycle, IP parameters, port mode, temperature, redundancy, load, power supply, and voltage.

[0013] Another embodiment of this application also proposes a management method for an industrial switch, applied to a switch, the method comprising:

[0014] Obtain the management message output by the PLC controller in the above method, and unpack it to obtain the management data;

[0015] Determine whether the management data is non-process data;

[0016] If so, the application object for each connection is configured based on the management data.

[0017] Furthermore, in the above-described management method for industrial switches, configuring the application object for each connection based on the management data includes:

[0018] The management data is parsed to obtain configuration information for various types and the corresponding IDs for the configuration information;

[0019] Based on the ID of the configuration information, the configuration information is transmitted to the corresponding application object for configuration, wherein each application object corresponds to one of the IDs.

[0020] Furthermore, the aforementioned management method for industrial switches also includes:

[0021] Back up the management data and / or the configuration information, and use the backed-up data to perform subsequent reconfiguration or configuration update operations after the exception ends.

[0022] Furthermore, the aforementioned management method for industrial switches also includes:

[0023] The management messages are periodically acquired and unpacked to obtain test data for each test.

[0024] Verify that the length of the test data is correct each time;

[0025] If correct, transmit the received information to the application object;

[0026] Receive the response message from the application object;

[0027] Based on the unpacked response message and the test data, feedback data is obtained;

[0028] The feedback data is packaged and transmitted to the PLC controller.

[0029] Furthermore, in the above-described management method for industrial switches, obtaining feedback data based on the unpacked response message and the test data includes:

[0030] Determine whether the test data is process data;

[0031] If it is process data, then determine whether the process data is compliant;

[0032] If compliant, feedback data is obtained based on the unpacked response message and the test data.

[0033] Furthermore, the aforementioned management method for industrial switches also includes:

[0034] The test data, the response message, and the feedback data are stored to buffer the input and output of the response message, the test data, and the feedback data.

[0035] Furthermore, the aforementioned management method for industrial switches also includes:

[0036] Back up the test data, and when the anomaly ends, directly call the previously backed-up data for subsequent management steps.

[0037] Another embodiment of this application also proposes an industrial switch management system, including: an industrial switch, a host computer, and a PLC controller;

[0038] The host computer acquires the feature information and configuration information of each industrial switch and generates its own switch file; it performs switch modeling based on the switch file to generate the corresponding switch model; and it compiles each switch model and inputs it into the PLC controller.

[0039] The PLC controller outputs management messages based on the switch model to control each of the industrial switches.

[0040] The embodiments of this application have the following beneficial effects:

[0041] This application proposes an industrial switch management method that allows for the management of industrial switches' functions and parameters, such as IP addresses, port parameters, and device information, via Ethernet / IP fieldbus (industrial Ethernet). Furthermore, it expands the application scenarios of traditional industrial switches to the Ethernet / IP fieldbus (industrial Ethernet) domain, enabling networking of robots, robotic arms, and intelligent manufacturing equipment. Additionally, because this method is implemented using a software protocol stack, it aligns with the mainstream market trend of software-based management, effectively reducing management costs. Attached Figure Description

[0042] To more clearly illustrate the technical solutions of this application, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of this application and should not be considered as a limitation on the scope of protection of this application. In the various drawings, similar components are numbered similarly.

[0043] Figure 1 A schematic diagram of the first module of a management method for an industrial switch according to some embodiments of this application is shown;

[0044] Figure 2 A first flowchart illustrating a management method for an industrial switch according to some embodiments of this application is shown;

[0045] Figure 3 The illustration shows an application scenario diagram of the management method for industrial switches according to some embodiments of this application;

[0046] Figure 4 A second flowchart illustrating a management method for an industrial switch according to some embodiments of this application is shown;

[0047] Figure 5 A schematic diagram of the second module of a management method for an industrial switch according to some embodiments of this application is shown;

[0048] Figure 6 A third flowchart illustrating a management method for an industrial switch according to some embodiments of this application is shown;

[0049] Figure 7 A schematic diagram of the third module of an industrial switch management method according to some embodiments of this application is shown;

[0050] Figure 8 A schematic diagram of the structure of an industrial switch management system according to some embodiments of this application is shown. Detailed Implementation

[0051] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0052] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0053] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.

[0054] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0055] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0056] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0057] Typically, several early and widely used fieldbuses, such as Controller Area Network (CAN) and RS485, have slow transmission speeds and small data packets per frame. However, with the development of industrial automation from low-speed to high-speed, from low-precision to high-precision, and from centralized control to distributed control, new requirements have been placed on the transmission speed and data volume of fieldbuses.

[0058] Therefore, this application proposes a new management method for industrial switches to achieve the management of industrial switches.

[0059] Please refer to Figure 1 This is a schematic diagram of a module for a management method of an industrial switch proposed in an embodiment of this application. Exemplarily, this management method for an industrial switch is applied to a switch managed and configured via the Ethernet / IP protocol.

[0060] In some implementations, such as Figure 2 As shown, a management method for an industrial switch, applied to a host computer, includes:

[0061] S110 acquires the characteristic and configuration information of each industrial Ethernet switch to generate its respective switch file.

[0062] S120, based on the switch file, performs switch modeling to generate the corresponding switch model.

[0063] Ethernet / IP is a modern, standard industrial Ethernet protocol. It is based on the Common Industrial Protocol (CIP). Industrial switches, also known as industrial Ethernet switches, are Ethernet switching devices used in industrial control applications. Due to the openness, wide application, and low cost of its network standard, and the use of the transparent and unified TCP / IP protocol, Ethernet has become the primary communication standard in industrial control. The application scenarios for industrial Ethernet switches differ significantly from those for ordinary Ethernet switches. Industrial Ethernet switches are primarily used in industrial environments, harsh conditions, and situations requiring high interference resistance.

[0064] Specifically, the host computer contains files for writing Electronic Data Sheets (EDS), which are mainly used to model the equipment, describe its characteristics, and form them into tables of a certain format. The host computer also includes Studio5000 software, which is a programming configuration software that integrates debugging, alarming, and programming of Programmable Logic Controllers (PLCs) and related equipment.

[0065] After the host computer obtains the feature information and configuration information of the industrial Ethernet switch, it uses the EDS file to form a corresponding EDS table file. This EDS table file is then transferred to the Studio5000 software. The Studio5000 software uses the EDS table file to perform simulation modeling of the industrial switch, generating the corresponding switch model. The feature information and configuration information include the industrial switch's port mode, IP parameters, and bandwidth, among other things.

[0066] S130: Compile each switch model and input it into the PLC controller, so that the PLC controller can output management messages to control each industrial switch. The management messages are obtained by the PLC controller based on the switch model.

[0067] Specifically, the PLC controller has functions such as learning MAC addresses, forwarding data frames, connecting different networks, and dividing local area networks. This allows for the configuration of the PLC controller and the switch module generated by Studio5000 software. The management messages include information such as the industrial switch version data, communication cycle, IP parameters, port mode, temperature, redundancy, load, power supply, and voltage.

[0068] Furthermore, such as Figure 3 As shown, industrial switches can also be configured by connecting robotic arms, human-machine interfaces, servo drivers, IO control devices, etc., to expand the application scenarios of the method in this application.

[0069] Another embodiment of this application also proposes a management method for industrial switches, such as... Figure 4 As shown, the method, applied to a switch, includes:

[0070] S210: Obtain the management message output by the PLC controller in the above method, and unpack it to obtain management data.

[0071] S220, determine whether the management data is non-process data.

[0072] S230, if so, then configure the application object for each connection based on the management data.

[0073] Specifically, non-process data refers to data that is not real-time and is used only in specific situations, such as parameter configuration or data display. This type of data does not have communication cycle requirements; for example, a PLC controller sends a non-process data message to a switch but does not need to worry about when the data packet will be replied to. The application objects refer to external automation equipment connected to the switch, such as robots and sensors.

[0074] In some implementations, the management method for industrial switches includes configuring the application objects for each connection based on management data, including:

[0075] Parse the management data and obtain various types of configuration information and their corresponding IDs.

[0076] Based on the ID of the configuration information, the configuration information is transmitted to the corresponding application object for configuration. Each application object corresponds to an ID.

[0077] Specifically, after obtaining the management data, it is parsed to obtain the configuration information and corresponding IDs of various application objects. The configuration information is then transmitted to the corresponding application object via the ID for configuration operations. This configuration information includes temperature, IP address, and port mode, among other things.

[0078] In some implementations, the management method for industrial exchange also includes:

[0079] Back up management data and / or configuration information, and use the backed-up data to perform subsequent reconfiguration or configuration update operations after the anomaly has ended.

[0080] Specifically, industrial switches may encounter malfunctions or power outages during operation, so it is necessary to back up the data and then reconfigure or update the configuration after normal operation is restored.

[0081] Exemplary, such as Figure 5 As shown, the switch program includes a socket interface 231, a data processing unit 232, a data routing unit 233, several application objects 234, and a backup unit 235.

[0082] The data processing unit 232 is used to obtain the management messages output by the PLC controller through the socket interface 231, unpack them to obtain management data, and transmit them to the data routing unit 233. The data processing unit 232 performs both message unpacking and data encapsulation.

[0083] The data routing unit 233 first verifies whether the received management data is non-process data, then parses it, finds the ID corresponding to each configuration data, and transmits the corresponding configuration data to each corresponding application object 234 according to the ID.

[0084] Application object 234 performs read, write, and process operations on the received configuration information, then configures itself based on the configuration information, and transmits the generated first response message to data processing unit 232 to obtain an encapsulated first response message, which is then fed back to the PLC controller via socket interface 231. The first response message includes information such as application object 234 has completed configuration to notify the PLC controller that configuration is complete. Backup unit 235 is used to back up the data in data processing unit 232.

[0085] In some implementations, such as Figure 6 As shown, the management methods for industrial exchange also include:

[0086] S310 periodically acquires management messages and unpacks them to obtain test data for each instance.

[0087] S320 verifies that the length of the test data is correct for each test.

[0088] S330, if correct, transmit the received information to the application object.

[0089] S340 receives the response message from the application object.

[0090] S350 obtains feedback data based on the unpacked response message and test data.

[0091] The S360 encapsulates the feedback data and transmits it to the PLC controller.

[0092] Specifically, this method primarily detects whether the entire link is functioning correctly. Therefore, the PLC controller needs to continuously send test data to the switch and receive feedback data. The feedback data is used to determine whether the entire link is functioning correctly. The cycle time can be 10ms, but other values ​​are not limited here.

[0093] In some implementations, the management method for industrial switches obtains feedback data based on the unpacked response messages and test data, including:

[0094] Determine whether the test data is process data.

[0095] If it is process data, then determine whether the process data is compliant.

[0096] If compliant, feedback data is obtained based on the unpacked response message and test data.

[0097] Specifically, the process data involves periodic request-response communication. For example, with a set communication cycle of 10ms, the PLC controller will send specified data every 10ms, and the corresponding application object needs to respond within 10ms. In the industrial control field, this is generally understood as real-time communication. The response message is the reply sent by the application object to the industrial switch.

[0098] In some implementations, the management method for industrial switches also includes:

[0099] Store test data, response messages, and feedback data to buffer the input and output of response messages, test data, and feedback data.

[0100] Specifically, since some modules need to both input and output corresponding data when processing data, in order to reduce conflicts, the data needs to be temporarily cached and input / output is performed sequentially to reduce conflicts and improve efficiency.

[0101] In some implementations, the management method for industrial switches also includes:

[0102] Back up the test data, and when the anomaly ends, directly call the last backed-up data for subsequent management steps.

[0103] Specifically, industrial switches may encounter malfunctions or power outages during operation, so it is necessary to back up the data and then reconfigure or update the configuration after normal operation is restored.

[0104] Exemplary, such as Figure 7As shown, the switch program may also include an interface 361, an I / O data unit 362, a function set unit 363, a notification unit 364, a user layer 365, a user return interface 366, a converter 367, a maintenance unit 368, and a buffer unit 369.

[0105] I / O data unit 362 is used to periodically obtain the management messages output by the PLC controller through interface interface 361 and unpack them to obtain management data.

[0106] The notification unit 364 is used to verify whether the length of the management data is correct when the I / O data unit 362 receives the management data. If it is correct, it sends a received information to the user layer 365 to indicate that the management data has been received, and also transmits the management data to the function set unit 363.

[0107] User layer 365 transmits user data to adapter 367 via a return interface upon receiving received information. Adapter 367 encapsulates the user data to obtain a response message and transmits it to function set unit 363. Function set unit 363 determines whether the management data from I / O data unit 362 is process data. If so, it further determines whether it is compliant. If compliant, it obtains feedback data based on the management data and the unpacked response message and transmits it to I / O data unit 362 to obtain encapsulated feedback data, which is then fed back to the PLC controller via interface 361. Maintenance unit 368 backs up the data in I / O data unit 362 and, after an exception occurs, can directly call the previously backed-up data through I / O data unit 362 for subsequent processing. Buffer unit 369 stores data received by function set unit 363.

[0108] This application proposes an industrial switch management method that integrates traditional industrial switches with Ethernet / IP fieldbus (industrial Ethernet). This allows for function and parameter management of the industrial switches, such as IP address, port parameters, and device information, through software like Studio5000 and RSLinx Classic. Furthermore, it expands the application scenarios of traditional industrial switches to the Ethernet / IP fieldbus (industrial Ethernet) domain, enabling networking of robots, robotic arms, and intelligent manufacturing equipment. Additionally, because this method is implemented using a software protocol stack, it aligns with the mainstream market trend of software-based management, effectively reducing management costs.

[0109] Another embodiment of this application also proposes an industrial switch management system 400, such as... Figure 8 As shown, system 400 includes: industrial switch 410, host computer 420 and PLC controller 430.

[0110] The host computer 420 acquires the feature information and configuration information of each industrial switch 410 and generates its own switch file; it models the switches based on the switch files to generate corresponding switch models; it compiles each switch model and inputs it into the PLC controller 430. The PLC controller 430 outputs management messages to control each industrial switch 410 based on the switch models.

[0111] It is understood that the method steps in this embodiment correspond to the industrial switch management method in the above embodiments. The options of the above industrial switch management method are also applicable to this embodiment, and will not be described again here.

[0112] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0113] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0114] If the aforementioned functions are implemented as software functional modules 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 this application, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0115] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A management method for an industrial switch, characterized in that, Applications in host computers include: Obtain the characteristic and configuration information of each industrial Ethernet switch to generate its own switch file; Modeling the switch based on the switch file to generate the corresponding switch model includes: using an Electronic Data Sheet (EDS) file to form a corresponding EDS table file from the feature information and the configuration information, and then transferring the EDS table file to the programming configuration software, so that the programming configuration software can perform simulation modeling of the industrial switch based on the EDS table file to generate the corresponding switch model. Each of the aforementioned switch models is compiled and input into the PLC controller, so that the PLC controller outputs management messages to control each of the aforementioned industrial switches; The management message is obtained by the PLC controller based on the switch model.

2. The management method for industrial switches according to claim 1, characterized in that, The management message includes the industrial switch's version data, communication cycle, IP parameters, port mode, temperature, redundancy, load, power supply, and voltage data.

3. A management method for an industrial switch, characterized in that, Applied to a switch, the method includes: Obtain the management message output by the PLC controller in the method described in any one of claims 1 to 2, and unpack it to obtain management data; Determine whether the management data is non-process data; If so, the application object for each connection is configured based on the management data.

4. The management method for industrial switches according to claim 3, characterized in that, The configuration of the application object for each connection based on the management data includes: The management data is parsed to obtain various types of configuration information and the corresponding IDs for each configuration information. Based on the ID of the configuration information, the configuration information is transmitted to the corresponding application object for configuration, wherein each application object corresponds to one of the IDs.

5. The management method for industrial switches according to claim 3, characterized in that, Also includes: Back up the management data and / or the configuration information, and use the backed-up data to perform subsequent reconfiguration or configuration update operations after the exception ends.

6. The management method for an industrial switch according to claim 3, characterized in that, Also includes: The management messages are periodically acquired and unpacked to obtain test data for each test. Verify that the length of the test data is correct each time; If correct, transmit the received information to the application object; Receive the response message from the application object; Based on the unpacked response message and the test data, feedback data is obtained; The feedback data is packaged and transmitted to the PLC controller.

7. The management method for an industrial switch according to claim 6, characterized in that, The feedback data obtained based on the unpacked response message and the test data includes: Determine whether the test data is process data; If it is process data, then determine whether the process data is compliant; If compliant, feedback data is obtained based on the unpacked response message and the test data.

8. The management method for an industrial switch according to claim 6, characterized in that, Also includes: The test data, the response message, and the feedback data are stored to buffer the input and output of the response message, the test data, and the feedback data.

9. The management method for an industrial switch according to claim 6, characterized in that, Also includes: Back up the test data, and when the anomaly ends, directly call the previously backed-up data for subsequent management steps.

10. An industrial switch management system, characterized in that, include: Industrial switches, host computers, and PLC controllers; The host computer acquires the feature information and configuration information of each industrial switch and generates its own switch file; it performs switch modeling based on the switch file to generate a corresponding switch model; it compiles each switch model and inputs it into the PLC controller; wherein, the switch modeling based on the switch file includes: using an Electronic Data Sheet (EDS) file to form a corresponding EDS table file from the feature information and the configuration information, and then transmitting the EDS table file to a preset programming configuration software, so that the preset programming configuration software can perform simulation modeling of the industrial switch based on the EDS table file to generate a corresponding switch model; The PLC controller outputs management messages based on the switch model to control each of the industrial switches.

Images