Drive upgrading method and device of magnetic levitation conveying system, computer equipment, readable storage medium and program product

Abstract

The invention relates to a driver upgrading method and device of a magnetic levitation conveying system, computer equipment, a readable storage medium and a program product. The method comprises the following steps: establishing communication connection with a plurality of drivers in the magnetic levitation transmission system to obtain state information of the plurality of drivers, determining a to-be-upgraded driver identifier and a matched to-be-upgraded file according to the state information, and further responding to an upgrading request instruction to upgrade the to-be-upgraded driver identifier. And upgrading the driver firmware corresponding to the matched to-be-upgraded driver identifier by adopting the to-be-upgraded file based on the upgrading process so as to realize automatic upgrading of the driver firmware needing to be upgraded in the magnetic levitation conveying system. According to the technical scheme, the requirement for manual operation can be reduced, dependence on technicians is reduced, errors caused by manual processing of upgrading in the prior art are avoided, and the upgrading efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of magnetic levitation transportation technology, and in particular to a drive upgrade method, device, computer equipment, readable storage medium and program product for a magnetic levitation transportation system. Background Art

[0002] The maglev conveying system is a technology that uses magnetic force to overcome the gravity of an object, so that the object can be suspended and transported. This technology is widely used in the field of industrial automation, especially in the transportation of materials on production lines. The driver is one of the core components of the maglev conveying system. The maglev conveying system usually communicates with the driver through the controller of the host computer to realize the control and data transmission of the maglev conveying system.

[0003] In addition to hardware support, the stable control of the maglev conveyor system also requires stable data system support. Therefore, the driver needs to be upgraded regularly or irregularly. Each production line that uses the maglev conveyor system usually requires dozens or even hundreds of drivers, each of which operates as an independent unit. In traditional technology, the upgrade process of the driver of the maglev conveyor system relies on manual processing of each driver separately, resulting in low upgrade efficiency and prone to errors. Summary of the invention

[0004] Based on this, it is necessary to provide a drive upgrade method, device, computer equipment, computer-readable storage medium and computer program product for a magnetic levitation conveying system that can improve processing efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a drive upgrade method for a magnetic levitation conveying system, the method being applied to a host computer, the method comprising:

[0006] Establishing communication connections with a plurality of drivers in the magnetic levitation conveying system and obtaining status information of the plurality of drivers;

[0007] Determine the driver identifier to be upgraded and the matching file to be upgraded according to the status information;

[0008] In response to the upgrade request instruction, the driver firmware corresponding to the matched driver identifier to be upgraded is upgraded using the file to be upgraded based on the upgrade process.

[0009] In one of the embodiments, the upgrade process-based method uses the file to be upgraded to upgrade the driver firmware corresponding to the matching driver identifier to be upgraded, including: if there are multiple driver identifiers to be upgraded that match the same file to be upgraded, determine multiple driver firmware corresponding to the multiple driver identifiers to be upgraded that match the same file to be upgraded; based on the upgrade process and the file to be upgraded, generate multiple upgrade threads to upgrade the multiple driver firmware in parallel.

[0010] In one of the embodiments, the driver firmware corresponding to the matching driver identifier to be upgraded is upgraded using the file to be upgraded based on the upgrade process, including: if there are multiple files to be upgraded that match the same driver identifier to be upgraded, determine the multiple files to be upgraded that match the same driver identifier to be upgraded; based on the multiple files to be upgraded, use multiple upgrade processes to upgrade the driver firmware corresponding to the driver identifier to be upgraded in parallel.

[0011] In one of the embodiments, the method further includes: in the process of upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, recording an upgrade log of the driver firmware.

[0012] In one of the embodiments, after upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, the method further includes: if it is determined that the driver firmware upgrade is successful, displaying prompt information of the successful driver firmware upgrade; if it is determined that the driver firmware upgrade fails, obtaining description information of the failure of the driver firmware upgrade, and displaying the description information of the failure of the driver firmware upgrade.

[0013] In one of the embodiments, after establishing the communication connection with the plurality of drivers in the magnetic levitation conveying system, the method further comprises: initializing a locking mechanism of the communication resources between the drivers to monopolize the communication resources of the drivers.

[0014] In one of the embodiments, before responding to the upgrade request instruction, the method further includes: configuring the priority of the upgrade process to the highest level, and disabling or pausing other processes except the upgrade process.

[0015] In one of the embodiments, after upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, the method further includes: unlocking the communication resources between the driver and resuming the other processes that are disabled or suspended.

[0016] In a second aspect, the present application further provides a drive upgrade device for a magnetic levitation conveying system, the device being applied to a host computer, the device comprising:

[0017] A status acquisition module is configured to establish a communication connection with a plurality of drivers in the magnetic levitation conveying system and acquire status information of the plurality of drivers;

[0018] A to-be-upgraded file determination module is configured to determine a to-be-upgraded driver identifier and a matching to-be-upgraded file according to the state information;

[0019] The upgrade processing module is configured to execute in response to the upgrade request instruction, and upgrade the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on the upgrade process.

[0020] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0021] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0022] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0023] The drive upgrade method, device, computer equipment, computer-readable storage medium and computer program product of the magnetic levitation conveying system establish communication connections with multiple drivers in the magnetic levitation conveying system to obtain status information of multiple drivers, and determine the driver identification to be upgraded and the matching files to be upgraded according to the status information, and then respond to the upgrade request instruction, and use the files to be upgraded based on the upgrade process to upgrade the driver firmware corresponding to the matching driver identification to be upgraded, thereby realizing automatic upgrade of the driver firmware that needs to be upgraded in the magnetic levitation conveying system. It can not only reduce the need for manual operation and reduce the dependence on technicians to avoid errors caused by relying on manual processing upgrades in traditional technologies, but also improve the upgrade efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0025] Figure 1 A schematic diagram of a process flow of a drive upgrade method for a magnetic levitation conveying system in one embodiment;

[0026] Figure 2 is a flowchart of a parallel upgrade process in one embodiment;

[0027] Figure 3 A schematic flow chart of a drive upgrade method for a magnetic levitation conveying system in another embodiment;

[0028] Figure 4 It is a structural block diagram of a drive upgrade device for a magnetic levitation conveying system in one embodiment;

[0029] Figure 5 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0031] In traditional technology, the upgrade process of the magnetic levitation conveying system relies on manual processing of each drive individually. When there are a large number of drives, the upgrade workload is large, resulting in low upgrade efficiency and prone to errors. In addition, upgrading each drive individually may lead to many different versions of software in the system, resulting in version incompatibility issues, increasing the risk of system failure. In addition, during the upgrade, the drives involved must be suspended from service, which is particularly disadvantageous on continuous production lines and may also lead to a decrease in overall production efficiency.

[0032] Based on this, the embodiment of the present application provides a drive upgrade method for a maglev conveying system, which is applied to a host computer of the maglev conveying system. Figure 1 As shown, in this embodiment, the method includes the following steps:

[0033] Step 102: Establish communication connections with multiple drivers in the magnetic levitation conveying system to obtain status information of the multiple drivers.

[0034] Among them, the communication connection is to form communication between connected devices through the transmission interaction of signals. Specifically, the communication connection includes wired connection and wireless connection, which is not limited in this embodiment. In this embodiment, for example, the host computer can be connected to multiple drivers in the magnetic levitation conveying system through a communication cable, so that the host computer can communicate with multiple drivers. In one scenario, the host computer and multiple drivers can also be mediated by a controller, and the controller is connected to multiple drivers in the magnetic levitation conveying system through a communication cable, and then the controller is connected to the host computer, so that the host computer can communicate with multiple drivers through the controller.

[0035] The status information of the driver may include the driver's attribute information, operation information, etc., which may cover all aspects of the driver. For example, the status information of the driver may specifically include the driver's type, driver number, stator module number to which the driver belongs (in a magnetic levitation conveying system, one or more stator modules may be included, a stator module may include one or more drivers, and a driver may include one or more channels, wherein each driver has a corresponding number to uniquely identify a driver, and each channel also has a corresponding channel number to uniquely identify a channel), the number of channels included in the driver and the corresponding channel numbers, the current version of the driver, the latest version of the driver, the current version and the latest version of each channel in the driver, etc.

[0036] In this embodiment, the host computer establishes communication connections with multiple drivers in the magnetic levitation conveying system, so that the status information of the multiple drivers can be obtained based on the communication relationship.

[0037] Step 104: Determine the driver identifier to be upgraded and the matching file to be upgraded according to the status information.

[0038] The driver identification can be used to uniquely represent the driver firmware, and the driver identification to be upgraded refers to the identification of the driver firmware that needs to be upgraded. The driver firmware in this embodiment can be a driver or a specific channel in the driver. The driver identification can be a driver number that uniquely identifies a driver, or a channel number that uniquely identifies a specific channel in a driver.

[0039] The file to be upgraded is a program file required for the driver firmware upgrade. Specifically, the file to be upgraded can be a program file for upgrading the driver that is higher than the current version of the driver, or a program file for upgrading the corresponding channel that is higher than the current version of the channel in the driver.

[0040] Since the status information of the driver includes the driver number, the current version of the driver, the latest version of the driver, the number of channels included in the driver and the corresponding channel number, the current version and the latest version of each channel in the driver, etc., the host computer can determine the driver identification to be upgraded and the matching files to be upgraded based on the status information of the multiple drivers obtained above. For example, by comparing the current version of the driver with the latest version, if the current version of a certain driver is not the latest version, it means that the driver needs to be upgraded. Therefore, the driver number of the driver can be determined as the driver identification to be upgraded, and the file to be upgraded is the program file corresponding to the latest version of the driver. Similarly, if the current version of a channel in a certain driver is not the latest version, it means that the corresponding channel in the driver needs to be upgraded. Therefore, the channel number of the corresponding channel in the driver can be determined as the driver identification to be upgraded, and the file to be upgraded is the program file corresponding to the latest version of the corresponding channel in the driver.

[0041] In one scenario, the driver identifier to be upgraded and the matching file to be upgraded can also be obtained from the outside based on actual upgrade needs. For example, after obtaining the status information of multiple drivers, the host computer can display the corresponding status information, so that the user can select the driver identifier to be upgraded and the corresponding file to be upgraded based on the displayed status information of each driver and actual needs. Then the host computer can determine the driver identifier to be upgraded and the matching file to be upgraded based on the user's selection.

[0042] Step 106 , in response to the upgrade request instruction, based on the upgrade process, the driver firmware corresponding to the matched driver identifier to be upgraded is upgraded using the file to be upgraded.

[0043] The upgrade process is an independent unit for resource allocation and scheduling of the operating system. It is an instance of the application running. The upgrade request instruction is an instruction or command for requesting the host computer to upgrade. It can be triggered by the user. For example, after the host computer determines the driver identification to be upgraded and the matching files to be upgraded according to the above steps, it can display the driver identification to be upgraded and the matching files to be upgraded, and the user confirms whether it needs to be upgraded. If the user confirms that it needs to be upgraded, it means that the corresponding upgrade request instruction is initiated to the host computer. The host computer responds to the upgrade request instruction and starts the upgrade process to use the files to be upgraded to upgrade the driver firmware corresponding to the matching driver identification to be upgraded.

[0044] In the above-mentioned drive upgrade method of the maglev conveying system, the host computer establishes a communication connection with multiple drivers in the maglev conveying system to obtain the status information of multiple drivers, and determines the driver identification to be upgraded and the matching file to be upgraded according to the status information, and then responds to the upgrade request instruction, and upgrades the driver firmware corresponding to the matching driver identification to be upgraded using the file to be upgraded based on the upgrade process, thereby realizing the automatic upgrade of the driver firmware that needs to be upgraded in the maglev conveying system. It can not only reduce the demand for manual operation and reduce the dependence on technicians, so as to avoid the errors caused by relying on manual processing upgrades in traditional technologies, but also improve the upgrade efficiency.

[0045] In an exemplary embodiment, Figure 2 As shown, in step 106, based on the upgrade process, the driver firmware corresponding to the matched driver identifier to be upgraded is upgraded using the file to be upgraded, which may specifically include:

[0046] Step 202: if there are multiple driver identifiers to be upgraded that match the same file to be upgraded, multiple driver firmwares corresponding to the multiple driver identifiers to be upgraded that match the same file to be upgraded are determined.

[0047] Specifically, if the driver identification to be upgraded in a certain magnetic levitation conveying system determined by the host computer and the matching files to be upgraded are shown in Table 1 below:

[0048]

[0049] Among them, type FI (FPGA Firmware) represents FPGA (Field Programmable Gate Array, programmable array logic) firmware, which is a program that can directly control the movement of the drive motor. Type DI (Drive Firmware) represents drive firmware, which can process information between the drive and the controller at the drive end. DI can be used to control algorithm calculations and output instructions to FI, and FI can implement specific control according to the instructions of the calculation results of DI, and feed back the operation results to DI. In the upgrade process of this embodiment, it is mainly aimed at the function implementation and version optimization of the corresponding type, and the upgrade process of each type is independent. Drive 1 represents a drive with a drive number of "1", and channel 1 represents a channel with a channel number of "1". It can be understood that each drive number or channel number is unique, and a drive or channel can be uniquely identified.

[0050] Based on this, it can be determined that the driver identification to be upgraded that matches the file to be upgraded "UpgradePackage_FI_v1.23.pkg" includes driver 1 and driver 2, that is, the file to be upgraded "UpgradePackage_FI_v1.23.pkg" has multiple matching driver identifications to be upgraded, namely driver 1 and driver 2. Therefore, the corresponding driver firmware can be determined based on multiple driver identifications to be upgraded, that is, multiple driver firmwares that need to be upgraded using the same file to be upgraded are determined. Specifically, if it is determined that the driver firmware corresponding to driver 1 is the driver with driver number "1", and it is determined that the driver firmware corresponding to driver 2 is the driver with driver number "2". It means that the multiple driver firmwares that need to be upgraded using the same file to be upgraded "UpgradePackage_FI_v1.23.pkg" include the driver numbered "1" and the driver numbered "2".

[0051] Step 204: Based on the upgrade process and the files to be upgraded, multiple upgrade threads are generated to upgrade multiple driver firmwares in parallel.

[0052] An upgrade thread is an entity in the upgrade process and is a basic unit that is independently scheduled and dispatched by the system. The upgrade threads in the same upgrade process share the address space and resources of the process. Since multiple driver firmwares need to use the same file to be upgraded, a corresponding upgrade process can be created based on the file to be upgraded, and multiple upgrade threads can be generated in the upgrade process to upgrade multiple driver firmwares in parallel.

[0053] It is understandable that the number of generated upgrade threads may be the same as the number of corresponding driver firmwares, so that one upgrade thread executes the upgrade of one driver firmware to achieve parallel upgrade of multiple driver firmwares.

[0054] Due to the limitation of the upgrade process resources by the operating system, the number of upgrade threads that can be created by an upgrade process is limited. Therefore, when the number of driver firmwares that need to be upgraded using the same file to be upgraded is large (that is, the number of driver firmwares that need to be upgraded is greater than the number of upgrade threads that can be created by the upgrade process), the driver firmwares that need to be upgraded can be upgraded in batches based on the upgrade threads that can be created by the upgrade process. For example, as shown in Table 1 above, for the upgrade of the type "feedback scale compensation table", the driver identifiers to be upgraded that match the file to be upgraded "UpgradePackage_FB_v1.20.pkg" include channels 1 to 40. That is to say, a total of 40 channels from channel 1 to channel 40 need to be upgraded using the same file to be upgraded "UpgradePackage_FB_v1.20.pkg". If the number of upgrade threads that can be created by the upgrade process is a maximum of 10 based on the limitation of the upgrade process resources by the operating system, the 10 upgrade threads can be used to upgrade channels 1 to 10 first, and after the upgrade is completed, channels 11 to 20 are upgraded, and then channels 21 to 30 and channels 31 to 40 are upgraded in sequence. Therefore, parallel upgrade based on multi-threading can improve the upgrade efficiency.

[0055] In one scenario, in order to further improve the upgrade efficiency, multiple upgrade processes can be used, and multiple upgrade threads can be created under each upgrade process for parallel upgrade. For example, in the process of upgrading 40 channels from channel 1 to channel 40 using the file to be upgraded "UpgradePackage_FB_v1.20.pkg", 4 upgrade processes can be created first, and then 10 upgrade threads can be generated under each upgrade process. Then, the 10 upgrade threads under the first upgrade process can perform the upgrade of channels 1 to 10, the 10 upgrade threads under the second upgrade process can perform the upgrade of channels 11 to 20, the 10 upgrade threads under the third upgrade process can perform the upgrade of channels 21 to 30, and the 10 upgrade threads under the fourth upgrade process can perform the upgrade of channels 31 to 40. In this process, the four upgrade processes can be executed in parallel, and the upgrade threads in each upgrade process can also be executed in parallel, which can greatly improve the upgrade efficiency.

[0056] Since in the above upgrade process, multiple upgrade threads under each upgrade process share the same file to be upgraded, or multiple upgrade processes executed in parallel share the same file to be upgraded, synchronization mechanisms (such as locks, semaphores, etc.) can also be used to ensure consistency in data transmission and status between multiple threads or processes, thereby improving the accuracy of the upgrade and avoiding the risk of version incompatibility caused by upgrade errors, which in turn leads to system failures.

[0057] In an exemplary embodiment, in step 106, based on the upgrade process, the driver firmware corresponding to the matching driver identifier to be upgraded is upgraded using the file to be upgraded, which may specifically include: if there are multiple files to be upgraded that match the same driver identifier to be upgraded, determine the multiple files to be upgraded that match the same driver identifier to be upgraded; based on the multiple files to be upgraded, use multiple upgrade processes to upgrade the driver firmware corresponding to the driver identifier to be upgraded in parallel.

[0058] Specifically, it can be seen from Table 1 above that for the driver with driver number "1", there are multiple matching files to be upgraded, including the file "UpgradePackage_FI_v1.23.pkg" of type "FI", the file "UpgradePackage_DI_v1.17.pkg" of type "DI", and the file "UpgradePackage_Para_v1.18.pkg" of type "parameter". In this embodiment, for the upgrade of the driver with driver number "1", multiple upgrade processes can be created based on the multiple files to be upgraded that need to be used, so that multiple upgrade processes are used for parallel upgrade. Among them, the number of upgrade processes is the same as the number of files to be upgraded that need to be used. For example, it can be seen from the above that the driver with driver number "1" needs to use 3 files to be upgraded, and the host computer can create 3 corresponding upgrade processes, each upgrade process processes a corresponding file to be upgraded, and the 3 upgrade processes are processed in parallel, thereby improving the upgrade efficiency.

[0059] In an exemplary embodiment, in order to avoid the stability and speed of the upgrade being affected by communication interference during the upgrade process, in step 102, after establishing a communication connection with multiple drives in the magnetic levitation conveying system, the above method may also include: initializing a locking mechanism for communication resources between each drive to monopolize the communication resources of the drive.

[0060] Among them, the locking mechanism is a mechanism for locking the communication resources between the host computer and each driver, for example, locking the communication port, thereby ensuring exclusive communication resources to avoid communication interference. It can be implemented specifically using locks, semaphores, synchronous driver notifications, etc. Specifically, the lock can be a mutex lock, which is used to protect shared resources and ensure that only one process can access the resources at the same time. In this embodiment, by using a mutex lock, it can be ensured that other processes cannot access the communication resources during the upgrade process, so that the host computer can monopolize the communication resources between each driver. The semaphore is used to control access to shared resources and can limit the number of threads that access shared resources at the same time. In this embodiment, by using a semaphore, access to communication resources can be limited during the upgrade process to ensure the exclusive use of the communication resources of each driver by the host computer. Synchronous driver notification can ensure that other processes cannot access the communication resources during the upgrade process. When the operating system adds a new processor to the hardware partition, it will send this notification to the device driver after starting the new processor and before scheduling the thread. The device driver can use this opportunity to allocate data structures and resources to ensure exclusive access to communication resources during the upgrade process.

[0061] In this embodiment, after the upper computer establishes a communication connection with multiple drivers in the magnetic levitation conveying system, it can initialize the locking mechanism of communication resources between each driver, thereby ensuring that the communication resources can be monopolized during the upgrade process to avoid communication interference, thereby further improving the upgrade speed and ensuring the stability of the upgrade.

[0062] In an exemplary embodiment, in step 106, before responding to the upgrade request instruction, the method may further include: configuring the priority of the upgrade process to the highest level, and disabling or pausing other processes except the upgrade process.

[0063] Among them, the priority can be the priority level for using communication resources. Other processes refer to processes other than the upgrade process. In this embodiment, in order to ensure that communication resources can be concentrated on the upgrade operation, before performing the upgrade operation, that is, before responding to the upgrade request instruction, the host computer can configure the priority of the upgrade process to the highest level, and disable or suspend other processes except the upgrade process, that is, temporarily disable or suspend other processes so that other processes do not occupy communication resources. And during the entire upgrade process, the priority of the upgrade process in the competition for communication resources can be ensured, and then it can be ensured that the upgrade process can monopolize communication resources to further improve the stability and speed of the upgrade, thereby shortening the upgrade time, reducing the system downtime caused by the upgrade, and thus avoiding the problem of reduced production efficiency due to the upgrade.

[0064] In an exemplary embodiment, in step 106, after upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, the method may further include: unlocking the communication resources with the driver and resuming other processes that are disabled or suspended.

[0065] Specifically, after the upgrade is completed, the host computer can also unlock the communication resources between the driver, that is, release the locked communication resources, and resume other disabled or paused processes, that is, undisable or unpause, so that other processes can use the communication resources normally.

[0066] In an exemplary embodiment, the method may further include: in the process of upgrading the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on the upgrade process, recording an upgrade log of the driver firmware.

[0067] The upgrade log may be detailed information about the upgrade process. Specifically, the upgrade log includes, but is not limited to, the upgrade time and upgrade description information. The upgrade description information may include the specific upgrade type, the driver identification of the driver firmware involved in the upgrade, the upgraded version, and the upgrade result. For example, the specific content of the upgrade log may be the information shown in Table 2 below:

[0068]

[0069] After being recorded, the above upgrade log can also be stored to serve as a basis for subsequent maintenance and review of the driver firmware.

[0070] In an exemplary embodiment, in step 106, after the driver firmware corresponding to the matching driver identifier to be upgraded is upgraded using the file to be upgraded based on the upgrade process, the method may further include: if it is determined that the driver firmware upgrade is successful, displaying prompt information that the driver firmware upgrade is successful; if it is determined that the driver firmware upgrade fails, obtaining description information of the driver firmware upgrade failure, and displaying description information of the driver firmware upgrade failure.

[0071] Specifically, in this embodiment, after the driver firmware is upgraded, the host computer can also automatically perform upgrade data detection to verify whether the new version of the corresponding driver firmware has been successfully upgraded. If it is determined that the new version of the driver firmware has been successfully installed, it means that the driver firmware has been successfully upgraded, so a prompt message indicating that the driver firmware has been successfully upgraded can be displayed.

[0072] If it is determined that the new version of the driver firmware has not been successfully installed, it means that the driver firmware upgrade has failed. Therefore, the description information of the driver firmware upgrade failure can be further obtained and displayed. For example, the description information of the failed upgrade can be that the upgrade file of the new version to be upgraded does not match the type of the driver firmware, resulting in no action after sending the upgrade request instruction. After the host computer detects this error, it can display the corresponding description information, so that the relevant personnel can re-select the correct upgrade file for upgrading based on the displayed description information of the failed upgrade, thereby improving the flexibility and interactivity of the upgrade and ensuring that the upgrade can be completed smoothly.

[0073] In an exemplary embodiment, Figure 3 As shown, the drive upgrade method of the above-mentioned magnetic levitation conveying system is further described below, which may specifically include the following steps:

[0074] Step 302, establishing communication connections with multiple drivers in the magnetic levitation conveying system, and initializing a locking mechanism for communication resources between each driver.

[0075] Specifically, after establishing communication connections with multiple drivers in the maglev conveying system, the host computer can initialize the locking mechanism of communication resources between each driver, thereby ensuring that communication resources can be exclusively occupied during the upgrade process to avoid communication interference, thereby increasing the upgrade speed and ensuring the stability of the upgrade.

[0076] Step 304: configure the priority of the upgrade process to the highest level, and disable or pause other processes except the upgrade process.

[0077] Specifically, before executing the upgrade operation, the host computer can configure the priority of the upgrade process to the highest level and disable or suspend other processes except the upgrade process, that is, temporarily disable or suspend other processes so that other processes will not occupy communication resources. In this way, during the entire upgrade process, the priority of the upgrade process in the competition for communication resources can be ensured, and then the upgrade process can be ensured to monopolize communication resources, so as to further improve the stability and speed of the upgrade and shorten the upgrade time.

[0078] Step 306: Acquire status information of multiple drivers based on the communication connection.

[0079] Specifically, the host computer establishes communication connections with multiple drivers in the magnetic levitation conveying system, and can thereby obtain status information of the multiple drivers based on the communication relationship.

[0080] Step 308: Determine the driver identifier to be upgraded and the matching file to be upgraded according to the status information.

[0081] Specifically, the host computer can determine the driver identifier to be upgraded and the matching file to be upgraded according to the status information of the multiple drivers acquired in the above steps, that is, determine the driver firmware to be upgraded and the corresponding file to be upgraded.

[0082] Step 310 : upgrading the driver firmware corresponding to the matched driver identifier to be upgraded by using the file to be upgraded based on multi-threading or multi-process.

[0083] Specifically, the host computer may upgrade the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on multi-threading or multi-process, thereby realizing concurrent upgrade of multiple driver firmwares to improve upgrade efficiency.

[0084] Step 312: During the upgrade process, record the upgrade log of the driver firmware.

[0085] Specifically, during the upgrade process, the host computer can record the upgrade log of the driver firmware as a basis for subsequent maintenance and review of the driver firmware. It can also monitor the usage of communication resources and detect and handle possible errors in a timely manner.

[0086] Step 314, after the upgrade is completed, the upgrade result is displayed, the communication resources with the driver are unlocked, and other disabled or suspended processes are resumed.

[0087] Specifically, after the upgrade is completed, the host computer can also display the upgrade result. For example, when it is determined that the driver firmware upgrade is successful, a prompt message indicating that the driver firmware upgrade is successful is displayed; when it is determined that the driver firmware upgrade fails, a description information of the driver firmware upgrade failure is obtained and the description information of the driver firmware upgrade failure is displayed.

[0088] After the upgrade is completed, the host computer can also unlock the communication resources between the driver and the host computer, that is, release the locked communication resources, and restore other processes that are disabled or paused, that is, undisable or unpause, so that other processes can use the communication resources normally. This can improve the upgrade efficiency, minimize system downtime, and enhance system security.

[0089] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0090] Based on the same inventive concept, the embodiment of the present application also provides a drive upgrade device for a magnetic levitation conveying system for implementing the drive upgrade method for the magnetic levitation conveying system involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiments of the drive upgrade device for one or more magnetic levitation conveying systems provided below can refer to the limitations of the drive upgrade method for the magnetic levitation conveying system above, and will not be repeated here.

[0091] In an exemplary embodiment, Figure 4 As shown, a drive upgrade device for a magnetic levitation conveying system is provided, the device is applied to a host computer, and the device includes: a state acquisition module 402, a file determination module 404 to be upgraded, and an upgrade processing module 406, wherein:

[0092] The state acquisition module 402 is configured to establish a communication connection with a plurality of drivers in the magnetic levitation conveying system and acquire state information of the plurality of drivers;

[0093] The to-be-upgraded file determination module 404 is configured to determine the to-be-upgraded driver identifier and the matching to-be-upgraded file according to the state information;

[0094] The upgrade processing module 406 is configured to execute in response to the upgrade request instruction, and upgrade the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on the upgrade process.

[0095] In an exemplary embodiment, the upgrade processing module is further configured to execute: if there are multiple driver identifiers to be upgraded that match the same file to be upgraded, determine multiple driver firmware corresponding to the multiple driver identifiers to be upgraded that match the same file to be upgraded; based on the upgrade process and the file to be upgraded, generate multiple upgrade threads to perform parallel upgrades on the multiple driver firmware.

[0096] In an exemplary embodiment, the upgrade processing module is further configured to execute: if there are multiple files to be upgraded that match the same driver identifier to be upgraded, determine the multiple files to be upgraded that match the same driver identifier to be upgraded; based on the multiple files to be upgraded, use multiple upgrade processes to parallelly upgrade the driver firmware corresponding to the driver identifier to be upgraded.

[0097] In an exemplary embodiment, the apparatus further includes a log recording module configured to execute: in the process of upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, recording an upgrade log of the driver firmware.

[0098] In an exemplary embodiment, the above-mentioned device also includes a display module, which is configured to execute: after upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, if it is determined that the driver firmware upgrade is successful, a prompt message of the successful driver firmware upgrade is displayed; if it is determined that the driver firmware upgrade fails, a description information of the failure of the driver firmware upgrade is obtained, and the description information of the failure of the driver firmware upgrade is displayed.

[0099] In an exemplary embodiment, the apparatus further comprises a locking module configured to execute: after establishing communication connections with a plurality of drivers in the magnetic levitation conveying system, initializing a locking mechanism for communication resources between each driver to monopolize the communication resources of the driver.

[0100] In an exemplary embodiment, the apparatus further comprises a priority configuration module configured to execute: before responding to an upgrade request instruction, configuring the priority of the upgrade process to the highest level, disabling or pausing other processes except the upgrade process.

[0101] In an exemplary embodiment, the priority configuration module is further configured to execute: after upgrading the driver firmware corresponding to the matching driver identifier to be upgraded using the file to be upgraded based on the upgrade process, unlocking the communication resources between the driver and resuming the other processes that are disabled or suspended.

[0102] Each module in the drive upgrade device of the magnetic levitation conveying system can be implemented in whole or in part by software, hardware and a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0103] In an exemplary embodiment, a computer device is provided. The computer device may be a host computer, and its internal structure diagram may be as shown in FIG. Figure 5 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a drive upgrade method for a magnetic levitation conveying system is realized. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0104] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0105] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0106] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0107] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0108] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0109] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0110] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0111] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A drive upgrade method for a magnetic levitation conveying system, characterized in that: The method is applied to a host computer, and the method comprises: Establishing communication connections with a plurality of drivers in the magnetic levitation conveying system and obtaining status information of the plurality of drivers; Determine the driver identifier to be upgraded and the matching file to be upgraded according to the status information; In response to the upgrade request instruction, the driver firmware corresponding to the matched driver identifier to be upgraded is upgraded using the file to be upgraded based on the upgrade process.

2. The method according to claim 1, characterized in that The step of upgrading the driver firmware corresponding to the matched driver identifier to be upgraded by using the file to be upgraded based on the upgrade process includes: If there are multiple driver identifiers to be upgraded that match the same file to be upgraded, determine multiple driver firmwares corresponding to the multiple driver identifiers to be upgraded that match the same file to be upgraded; Based on the upgrade process and the files to be upgraded, multiple upgrade threads are generated to upgrade the multiple driver firmwares in parallel.

3. The method according to claim 1, characterized in that The step of upgrading the driver firmware corresponding to the matched driver identifier to be upgraded by using the file to be upgraded based on the upgrade process includes: If there are multiple files to be upgraded that match the same driver identifier to be upgraded, determine the multiple files to be upgraded that match the same driver identifier to be upgraded; Based on the multiple files to be upgraded, multiple upgrade processes are used to upgrade the driver firmware corresponding to the driver identifier to be upgraded in parallel.

4. The method according to claim 1, characterized in that The method further comprises: In the process of upgrading the driver firmware corresponding to the matched driver identifier to be upgraded by using the file to be upgraded based on the upgrade process, an upgrade log of the driver firmware is recorded.

5. The method according to claim 1, characterized in that After upgrading the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on the upgrade process, the method further includes: If it is determined that the driver firmware upgrade is successful, display a prompt message that the driver firmware upgrade is successful; If it is determined that the driver firmware upgrade fails, description information of the driver firmware upgrade failure is obtained, and the description information of the driver firmware upgrade failure is displayed.

6. The method according to any one of claims 1 to 5, characterized in that: After establishing the communication connection with the plurality of drivers in the magnetic levitation conveying system, the method further comprises: Initialize the locking mechanism of the communication resources between each driver to monopolize the communication resources of the driver.

7. The method according to claim 6, characterized in that Before responding to the upgrade request instruction, the method further includes: The priority of the upgrade process is configured to be the highest level, and other processes except the upgrade process are disabled or paused.

8. The method according to claim 7, characterized in that After the driver firmware corresponding to the matched driver identifier to be upgraded is upgraded using the file to be upgraded based on the upgrade process, the method further includes: The communication resource with the driver is unlocked, and the other processes that are disabled or suspended are resumed.

9. A drive upgrade device for a magnetic levitation conveying system, characterized in that: The device is applied to a host computer, and the device comprises: A status acquisition module is configured to establish a communication connection with a plurality of drivers in the magnetic levitation conveying system and acquire status information of the plurality of drivers; A to-be-upgraded file determination module is configured to determine a to-be-upgraded driver identifier and a matching to-be-upgraded file according to the state information; The upgrade processing module is configured to execute in response to the upgrade request instruction, and upgrade the driver firmware corresponding to the matched driver identifier to be upgraded using the file to be upgraded based on the upgrade process.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.

Images