Mine-used tethered device system based on UDP communication and firmware upgrading method thereof
Patent Information
- Application Number
- CN202611235232.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-14
- Publication Date
- 2026-10-16
AI Technical Summary
当升级文件较大时,需要将文件拆分为大量数据帧依次发送,效率低下
[0016]本申请的技术方案中,矿用系设备系统利用UDP协议的IP直接寻址能力,省去CAN升级中复杂的BOOT编址流程,每个从站设备通过IP地址唯一标识,主站可直接与目标设备进行点对点通讯;并且本申请不仅简化升级流程,取消沿线供电时序控制、同步等待模式设置与解除等复杂环节,降低系统复杂度,而且还支持同时并发升级多个设备,提升批量升级效率。因此本申请能够提高矿用设备系统中设备固件升级的工作效率。
Smart Images

Figure CN122933418A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of mining equipment technology, and in particular to a mining equipment system based on UDP communication and its firmware upgrade method. Background Technology
[0002] The existing mining equipment system includes a master station and multiple slave stations. The master station communicates with each slave station, and each slave station is equipped with an intelligent terminal with a microcontroller as the core controller for intelligent control of the mine equipment at its corresponding location.
[0003] Firmware upgrades for mining equipment systems are a critical aspect of system maintenance. Traditional microcontroller upgrade methods primarily include serial port upgrades and CAN bus upgrades. While serial port upgrades are simple to implement, they only support point-to-point communication, hindering networked batch upgrades and limiting transmission distance. Although CAN bus upgrades support multi-node networking, their physical layer speed is limited to a maximum of 1Mbps due to the design of the CAN protocol, with industrial applications commonly using 250kbps to 500kbps. Furthermore, each CAN message frame can only carry a maximum of 8 bytes of data. When the upgrade file is large, it needs to be split into numerous data frames and sent sequentially, resulting in low efficiency.
[0004] In summary, existing mining equipment systems suffer from low firmware upgrade efficiency. Summary of the Invention
[0005] This application provides a mining equipment system based on UDP communication and its firmware upgrade method, which is used to improve the efficiency of firmware upgrades in mining equipment systems.
[0006] Specifically, this application provides a mining equipment system based on UDP communication, including a master station device and multiple slave station devices. The master station device is communicatively connected to the multiple slave station devices and exchanges information via the UDP protocol. The master station device is configured to: Obtain the firmware upgrade file and the device to be upgraded from the slave devices; The firmware upgrade file is split into multiple data packets, and a system reboot command is sent to the device to be upgraded so that the device to be upgraded enters the upgrade mode. Send a synchronization wait mode to the device to be upgraded to keep it in the wait-for-upgrade state, and send the data packet to each device to be upgraded in sequence; Send a version number command to the device to be upgraded to determine the integrity of the firmware upgrade file received by the device to be upgraded; The slave device is configured as follows: After receiving the system restart command, it enters upgrade mode; after receiving the synchronization wait mode, it remains in a wait-for-upgrade state; and after receiving the data packet, it performs a firmware upgrade based on the data packet. Upon receiving the version number command, the system calculates the full packet checksum of the received data packet and sends it to the master station device so that the master station device can verify the integrity of the firmware upgrade file received by the device to be upgraded.
[0007] Furthermore, before splitting the firmware upgrade file into multiple data packets, the master station device is also used to: obtain the standard MD5 value of the firmware upgrade file and calculate the actual MD5 value of the firmware upgrade file; The firmware upgrade file is determined to have been tampered with based on the standard MD5 value and the actual MD5 value. If not, the firmware upgrade file is split into multiple data packets.
[0008] Further, the master station device sequentially sends the data packet to each of the devices to be upgraded, including: Generate description information for the data packet and send the description information to the device to be upgraded; After receiving confirmation from the device to be upgraded, the data packet is sent to the device to be upgraded, and the data packet is verified with the device to be upgraded.
[0009] Furthermore, the description information includes the device type, upgrade type, total number of data packets, current data packet index, data packet size, and upgrade mode of the corresponding data packet.
[0010] Furthermore, according to claim 1, the mining equipment system based on UDP communication is characterized in that, after verifying the integrity of the firmware upgrade file received by the device to be upgraded, the master station device sends a synchronization release command to the device to be upgraded, so that the device to be upgraded exits the waiting-for-upgrade state.
[0011] Furthermore, after verifying the completeness of the firmware upgrade file received by the device to be upgraded, the master station device is also used to: if the firmware upgrade device does not fully receive the firmware upgrade file, determine whether the device to be upgraded has failed to upgrade, and generate a reason for the failure of the device to be upgraded.
[0012] Furthermore, during the process of the master station device sending the data packets to each of the devices to be upgraded in sequence, the upgrade progress percentage of the devices to be upgraded is calculated based on the number of data packets that have been successfully sent, and the percentage is displayed on the interface.
[0013] Furthermore, before obtaining the firmware upgrade file, the master station device is also used to: receive the device information of the slave station device and store it in the device information table. The device information includes the line name, device ID, device type, IP address, and sub-expansion board flag of the corresponding slave station device.
[0014] Furthermore, after obtaining the device information, the master station device is also used to: verify the validity of the IP address of the slave station device, and after the verification is passed, store the device information of the slave station device into the device information mapping table.
[0015] This application also provides a firmware upgrade method for a mining equipment system based on UDP communication as described in any of the above claims, comprising the following steps: The master station device obtains the firmware upgrade file and the device to be upgraded from the slave station devices, splits the firmware upgrade file into multiple data packets, and sends a system restart command to the device to be upgraded; The slave device enters upgrade mode after receiving the system restart command; The master station device sends a synchronization waiting mode to the device to be upgraded, and the device to be upgraded remains in a waiting state after receiving the synchronization waiting mode. The master station device sends multiple data packets sequentially to each device to be upgraded, and the device to be upgraded performs firmware upgrade based on the data packets after receiving them; The master station device sends a version number command to the device to be upgraded. After receiving the version number command, the device to be upgraded calculates the full packet check value of the received data packet and sends it to the master station device. After receiving the full packet verification value, the master station device determines the integrity of the firmware upgrade file received by the device to be upgraded based on the full packet verification value.
[0016] In the technical solution of this application, the mining equipment system utilizes the direct IP addressing capability of the UDP protocol, eliminating the complex BOOT addressing process in CAN upgrades. Each slave device is uniquely identified by its IP address, and the master station can directly communicate point-to-point with the target device. Furthermore, this application not only simplifies the upgrade process by eliminating complex steps such as power supply timing control along the line and setting and deactivating synchronous waiting modes, thus reducing system complexity, but also supports simultaneous concurrent upgrades of multiple devices, improving batch upgrade efficiency. Therefore, this application can improve the efficiency of firmware upgrades in mining equipment systems.
[0017] The above and other objects, advantages and features of this application will become more apparent to those skilled in the art from the following detailed description of specific embodiments of this application in conjunction with the accompanying drawings. Attached Figure Description
[0018] The following sections will describe some specific embodiments of this application in detail by way of example and not limitation, with reference to the accompanying drawings. The same reference numerals in the drawings denote the same or similar parts or components. Those skilled in the art should understand that these drawings are not necessarily drawn to scale. In the drawings: Figure 1 This is a schematic diagram of a mining equipment system based on UDP communication according to an embodiment of this application; Figure 2 This is a flowchart of a firmware upgrade process performed on a master station device according to an embodiment of this application. Detailed Implementation
[0019] In the relevant technology of this application, the mining equipment system comprises a master station device and several slave station devices, and the master station device and each slave station device are connected via a CAN bus to form a multi-master-slave bus network topology. The firmware upgrade process for slave station devices in the mining equipment system can be divided into three stages: Phase 1: Device Addressing and Initialization. Since the CAN bus lacks an address allocation mechanism similar to IP, a short bus address must be assigned to each slave device before upgrading it using a specific addressing protocol. A common practice is for the master device to send addressing request frames sequentially. Upon receiving the frame, the slave device replies with its own identification information. The master device then assigns a unique ID to its corresponding slave device and records its device type based on this identification information. This process typically involves powering on / off or resetting the device to ensure the addressing sequence.
[0020] Phase Two: Firmware Data Transmission. The master device splits the firmware upgrade file into multiple data packets of fixed length. Each data packet is then further split into multiple data frames according to the maximum payload of a CAN frame. These data frames are then encapsulated and sent sequentially. The data packet transmission process involves three command interactions: First, a description frame is sent to the slave devices, including metadata such as the data packet number and the total number of data packets. Then, the content of each data packet is transmitted to each slave device frame by frame. Finally, a CRC check frame is sent to the slave devices to confirm the integrity of the transmitted data packets. If the check fails, a retransmission mechanism is triggered to resend the data packets.
[0021] Phase 3: Upgrade Completion Confirmation. After transmitting all data packets, the master device initiates a full packet CRC check of the firmware upgrade file to the slave device. The slave device calculates the complete CRC value written into the firmware upgrade file and sends it back to the master device. The master device compares this complete CRC value with the full packet CRC value of the firmware upgrade file to verify the firmware upgrade file of the slave device. After the verification passes, the slave device exits the upgrade mode and jumps to the new firmware.
[0022] In CAN bus-based mining equipment systems, firmware upgrades have the following drawbacks: Low transmission rate: The typical CAN bus rate is 250kbps~500kbps, and only 8 bytes of valid data are transmitted per frame. Taking a 256KB upgrade file as an example, it needs to be split into about 370,000 CAN messages, and the transmission time is several minutes or even longer.
[0023] The addressing process is complex: a complete device addressing process must be executed before each upgrade: broadcast restart → clear address → wait for addressing request for each device → assign address → turn on power to the next device. This involves complex timing control and power management, and the process is time-consuming and easily interrupted by hardware failure.
[0024] Strong topology dependency: CAN upgrades rely on a cascaded power supply topology along the line. Devices are powered on and addressed sequentially in a chain structure. A single point of failure will prevent subsequent devices from being addressed. Complex synchronization waiting mechanism: During the upgrade process, devices need to maintain a synchronization waiting mode. After the upgrade is completed, devices need to be restarted one by one according to their addresses from largest to smallest, making the process cumbersome.
[0025] Lack of direct addressing capability: The CAN bus has no IP addressing capability and can only identify devices through short addresses (1~255) after addressing, which makes management inconvenient.
[0026] The following reference Figures 1 to 2 This application describes a mining equipment system based on UDP communication and its firmware upgrade method according to embodiments of the present application. In the description of this embodiment, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" and "second" may explicitly or implicitly include at least one of that feature, that is, include one or more of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. When a feature "includes or contains" one or more of the features it encompasses, unless otherwise specifically described, this indicates that other features are not excluded and may be further included.
[0027] In the description of this embodiment, the terms "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.
[0028] Please refer to this document. Figure 1 , Figure 1 This is a schematic diagram of a mining equipment system based on UDP communication according to an embodiment of this application. The mining equipment system includes a master station device and multiple slave station devices. The controllers of both the master station device and the slave station devices are microcontrollers. The controller of the master station device is communicatively connected to each slave station device and exchanges information with each slave station device through the UDP protocol. That is, the controller of the master station device and the controller of each slave station device are configured with corresponding IP addresses, and the master station device exchanges information through the IP addresses of each slave station device.
[0029] In this embodiment, the method for the master station device to perform firmware upgrades on the slave station device is as follows: Figure 2 As shown, it includes the following steps: Step S101: Obtain the firmware upgrade file and obtain the device to be upgraded from the slave devices; Step S102: Split the firmware upgrade file into multiple data packets and send a system reboot command to the device to be upgraded so that the device to be upgraded can enter the upgrade mode; Step S103: Send a synchronization wait mode to the device to be upgraded to keep it in the wait-for-upgrade state, and send data packets to each device to be upgraded in sequence; Step S104: Send a version number command to the device to be upgraded to verify the integrity of the firmware upgrade file received by the device to be upgraded.
[0030] In step S101 above, the master station device is equipped with a data transmission interface, such as an HTTP interface, which is used to send firmware upgrade files and slave devices that need to be upgraded to the master station device through the data transmission interface, and to designate the slave devices as the devices to be upgraded.
[0031] In step S102 above, the firmware upgrade file can be split into multiple data packets according to a preset data length. The preset data length is 1024 bytes, that is, the firmware upgrade file is split into multiple data packets of 1024 bytes each. The data length of the last data packet may be less than the preset data length.
[0032] In this embodiment, the system restart command specifies the restart mode as "synchronous waiting mode" and the upgrade type as "maintaining the master station application". The master station device can send a system restart command to the device to be upgraded based on its IP address. After receiving the system restart command, the device to be upgraded enters upgrade mode to wait for subsequent upgrade instructions and returns a feedback message to the master station device indicating that the system restart command was successfully received. Upon receiving this feedback message, the master station device determines that the system restart command was successfully sent. If it does not receive this feedback message within 1 second, it resends the system restart command to the device to be upgraded. If no feedback message is received after sending the system restart command 10 times consecutively, it is determined that it cannot send the system restart command to the device to be upgraded and will not continue to send the system restart command.
[0033] In step S103 above, the master station device can send a synchronization wait command to the device to be upgraded based on its IP address. After receiving the synchronization wait command, the device to be upgraded enters a waiting upgrade state to ensure that it will not reset due to watchdog timeout or other reasons during the process of sending the firmware upgrade file to the device to be upgraded. The master station device then returns a feedback message indicating that the synchronization wait command was successfully received. After receiving this feedback message, the master station device determines that the synchronization wait command was successfully sent. If it does not receive the feedback message within 1 second, it resends the synchronization wait command to the device to be upgraded. If it does not receive feedback message after sending the synchronization wait command 15 times consecutively, it determines that it cannot send the synchronization wait command to the device to be upgraded and will not continue to send the synchronization wait command.
[0034] After the master station device determines that the synchronization waiting command has been successfully sent, it sends data packets to the slave devices in the order specified in the firmware upgrade file. After receiving the data packets, the device to be upgraded restores the firmware upgrade file based on the received data packets and performs a firmware upgrade based on the firmware upgrade file, thereby realizing the firmware upgrade of the slave devices in the mining equipment system.
[0035] In step S104 above, the master station device can perform CRC verification on the firmware upgrade file to generate a standard CRC verification value for the firmware upgrade file, and send a version number command to the device to be upgraded according to the IP address of the device to be upgraded; after receiving the version number command, the device to be upgraded restores the firmware upgrade file according to the received data packet, performs CRC verification on the firmware upgrade file to generate its actual CRC verification value, and then sends the actual CRC verification value to the master station device.
[0036] After sending a version number command to the device to be upgraded, if the master station does not receive an actual CRC checksum from the device to be upgraded within 5 seconds, it considers the version number command sending to the device to be upgraded a failure. If the version number command fails to be sent to the device to be upgraded 10 times consecutively, it will no longer send version number command failures to the device to be upgraded. If an actual CRC checksum is received from the device to be upgraded, it is compared with the standard CRC checksum. If they match, it is determined that the firmware upgrade file received by the device to be upgraded is complete and the firmware upgrade of the device to be upgraded is successful; if they do not match, it is determined that the firmware upgrade file received by the device to be upgraded is incomplete and the firmware upgrade of the device to be upgraded has failed.
[0037] In this embodiment, the mining equipment system utilizes the direct IP addressing capability of the UDP protocol, eliminating the complex BOOT addressing process in CAN upgrades. Each slave device is uniquely identified by its IP address, allowing the master station to directly communicate point-to-point with the target device. Furthermore, this embodiment not only simplifies the upgrade process by eliminating complex steps such as power supply timing control along the line and setting and deactivating synchronous waiting modes, reducing system complexity, but also supports simultaneous concurrent upgrades of multiple devices, improving batch upgrade efficiency. Therefore, this application can improve the efficiency of firmware upgrades in mining equipment systems.
[0038] In some embodiments of this application, before splitting the firmware upgrade file into multiple data packets, the master station device also obtains the standard MD5 value of the firmware upgrade file and calculates the actual MD5 value of the firmware upgrade file. Then, it determines whether the firmware upgrade file has been tampered with based on the standard MD5 value and the actual MD5 value. If not, the firmware upgrade file is split into multiple data packets.
[0039] In this embodiment, the MD5 value refers to the hash value calculated using the MD5 message digest algorithm. The MD5 message digest algorithm is a widely used cryptographic hash function that can generate a 128-bit hash value to ensure the consistency of information transmission.
[0040] This embodiment verifies whether the received firmware upgrade file has been tampered with by using the MD5 value, which can improve the accuracy of the received firmware upgrade file and thus improve the accuracy and reliability of firmware upgrades for slave devices.
[0041] In some embodiments of this application, taking one data packet as an example, the method by which the master station device sequentially sends the data packet to the device to be upgraded includes: First, the master station device generates a description of the data packet and sends the description to the device to be upgraded; after receiving the description, the device to be upgraded sends a confirmation message to the master station device. If the master station does not receive confirmation information from the device to be upgraded, it determines that the data packet description information has failed to be received and sends the data packet description information to the device to be upgraded again; if the data packet description information fails to be sent 10 times in a row, the master station will stop sending the data packet description information to the device to be upgraded. If the host device receives an acknowledgment from the device to be upgraded, it generates a standard CRC checksum for the data packet and sends the data packet and its standard CRC checksum to the device to be upgraded. Upon receiving the data packet, the slave device calculates the actual CRC checksum and compares it with the standard CRC checksum. If they match, the slave device replies with an acknowledgment to the host device. Upon receiving this acknowledgment, the host device considers the data packet to have been successfully sent; otherwise, it considers the data packet transmission a failure. If the data packet transmission fails 10 times consecutively, the host device will no longer send the data packet to the device to be upgraded.
[0042] In this embodiment, the CRC checksum of the data packet is calculated using the CRC check algorithm. The CRC algorithm is a cyclic redundancy check algorithm, a fast algorithm that generates a short, fixed-length checksum based on data such as network data packets or computer files. It is mainly used to detect or verify errors that may occur after data transmission or storage. CRC utilizes the principles of division and remainders to achieve error detection, and has advantages such as clear principles and simple implementation.
[0043] In this embodiment, the master station device sends a description of the data packet to the device to be upgraded before sending the data packet to the device to be upgraded, which can ensure the accuracy and reliability of the data packet transmission.
[0044] In some embodiments of this application, the description information of the data packet includes the device type, upgrade type, total number of data packets, current data packet index, data packet size, and upgrade mode.
[0045] In some embodiments of this application, after the master station device verifies the integrity of the firmware upgrade file received by the device to be upgraded, it sends a synchronization release command to the device to be upgraded via the device's IP address, so that the device to be upgraded exits the waiting-for-upgrade state.
[0046] In some embodiments of this application, after the master station device verifies the integrity of the firmware upgrade file received by the device to be upgraded, it is further configured to: if the firmware upgrade device does not fully receive the firmware upgrade file, determine whether the device to be upgraded has failed to upgrade, and generate a reason for the failure of the device to be upgraded, which includes data packet sending timeout, data packet verification failure, and no response from the device to be upgraded.
[0047] In some embodiments of this application, during the process of the master station device sending data packets to each device to be upgraded in sequence, the upgrade progress percentage of the device to be upgraded is calculated based on the number of data packets that have been successfully sent, and the percentage is displayed on the interface.
[0048] For example, assuming the firmware upgrade file is split into N data packets, if the nth data packet is successfully sent to the device to be upgraded, the upgrade progress percentage of the device is n / N×100%.
[0049] In some embodiments of this application, before obtaining the firmware upgrade file, the master station device is further configured to: receive device information of the slave station device and store it in a device information table, wherein the device information includes the line name, device ID, device type, IP address, and sub-expansion board flag of the corresponding slave station device.
[0050] In some embodiments of this application, after the master station device obtains the device information of the slave station device, it is further used to: perform a validity check on the IP address of the slave station device, and after the check passes, store the device information of the slave station device into the device information mapping table.
[0051] The flowchart provided in this embodiment is not intended to indicate that the operations of the method will be performed in any particular order, or that all operations of the method are included in every case. Furthermore, the method may include additional operations. Within the scope of the technical concept provided by the method in this embodiment, additional variations can be made to the above method.
[0052] It should be understood that in some embodiments, the components may be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods may be implemented using software or firmware stored in memory and executed by a suitable instruction execution system.
[0053] Therefore, those skilled in the art should recognize that although many exemplary embodiments of this application have been shown and described in detail herein, many other variations or modifications conforming to the principles of this application can be directly determined or derived from the disclosure of this application without departing from the spirit and scope of this application. Thus, the scope of this application should be understood and construed as covering all such other variations or modifications.
Claims
1. A mining equipment system based on UDP communication, characterized in that, It includes a master station device and multiple slave station devices, wherein the master station device is communicatively connected to the multiple slave station devices and exchanges information via the UDP protocol, wherein the master station device is configured to: Obtain the firmware upgrade file and the device to be upgraded from the slave devices; The firmware upgrade file is split into multiple data packets, and a system reboot command is sent to the device to be upgraded so that the device to be upgraded enters the upgrade mode. Send a synchronization wait mode to the device to be upgraded to keep it in the wait-for-upgrade state, and send the data packet to each device to be upgraded in sequence; Send a version number command to the device to be upgraded to determine the integrity of the firmware upgrade file received by the device to be upgraded; The slave device is configured as follows: After receiving the system restart command, it enters upgrade mode; after receiving the synchronization waiting mode, it remains in the waiting upgrade state; and after receiving the data packet, it performs firmware upgrade according to the data packet. as well as Upon receiving the version number command, the system calculates the full packet checksum of the received data packet and sends it to the master station device so that the master station device can verify the integrity of the firmware upgrade file received by the device to be upgraded.
2. The mining equipment system based on UDP communication according to claim 1, characterized in that, Before splitting the firmware upgrade file into multiple data packets, the master station device is also used to: obtain the standard MD5 value of the firmware upgrade file and calculate the actual MD5 value of the firmware upgrade file. The firmware upgrade file is determined to have been tampered with based on the standard MD5 value and the actual MD5 value. If not, the firmware upgrade file is split into multiple data packets.
3. The mining equipment system based on UDP communication according to claim 1, characterized in that, The master station device sequentially sends the data packet to each of the devices to be upgraded, including: Generate description information for the data packet and send the description information to the device to be upgraded; After receiving confirmation from the device to be upgraded, the data packet is sent to the device to be upgraded, and the data packet is verified with the device to be upgraded.
4. The mining equipment system based on UDP communication according to claim 3, characterized in that, The description information includes the device type, upgrade type, total number of data packets, current data packet index, data packet size, and upgrade mode of the corresponding data packet.
5. The mining equipment system based on UDP communication according to claim 1, characterized in that, After verifying the integrity of the firmware upgrade file received by the device to be upgraded, the master station device sends a synchronization release command to the device to be upgraded, so that the device to be upgraded exits the waiting-for-upgrade state.
6. The mining equipment system based on UDP communication according to claim 1, characterized in that, After verifying the integrity of the firmware upgrade file received by the device to be upgraded, the master station device is further configured to: if the firmware upgrade device does not fully receive the firmware upgrade file, determine whether the device to be upgraded has failed to upgrade, and generate a reason for the failure of the upgrade.
7. The mining equipment system based on UDP communication according to claim 1, characterized in that, As the master station device sequentially sends the data packets to each device to be upgraded, it calculates the upgrade progress percentage of each device based on the number of data packets that have been successfully sent and displays it on the interface.
8. The mining equipment system based on UDP communication according to claim 1, characterized in that, Before obtaining the firmware upgrade file, the master station device is also used to: receive the device information of the slave station device and store it in the device information table. The device information includes the line name, device ID, device type, IP address, and sub-expansion board flag of the corresponding slave station device.
9. The mining equipment system based on UDP communication according to claim 8, characterized in that, After obtaining the device information, the master station device is further configured to: perform a validity check on the IP address of the slave station device, and store the device information of the slave station device into the device information mapping table after the verification is successful.
10. A firmware upgrade method for a mining equipment system based on UDP communication as described in any one of claims 1-9, characterized in that, Includes the following steps: The master station device obtains the firmware upgrade file and the device to be upgraded from the slave station devices, splits the firmware upgrade file into multiple data packets, and sends a system restart command to the device to be upgraded; The slave device enters upgrade mode after receiving the system restart command; The master station device sends a synchronization waiting mode to the device to be upgraded, and the device to be upgraded remains in a waiting state after receiving the synchronization waiting mode. The master station device sends multiple data packets sequentially to each device to be upgraded, and the device to be upgraded performs firmware upgrade based on the data packets after receiving them; The master station device sends a version number command to the device to be upgraded. After receiving the version number command, the device to be upgraded calculates the full packet check value of the received data packet and sends it to the master station device. After receiving the full packet verification value, the master station device determines the integrity of the firmware upgrade file received by the device to be upgraded based on the full packet verification value.