Robot system management equipment, medium and product

Abstract

The invention discloses robot system management equipment, a medium and a product, and relates to the field of robot development, in the equipment, a standard mirror image module is used for configuring a template of a robot system and constructing a standard mirror image; the virtual machine management server storage module is used for building a server virtual machine management platform based on a virtual machine management system; a standard mirror image and a developed robot system are stored on the basis of the server virtual machine management platform; the robot system migration module is used for migrating a robot system based on a hard disk cloning system or a virtual machine management system; the robot application module is used for deploying a virtual machine management system on a robot upper computer, accessing a local area network and controlling a corresponding robot based on the robot system migrated from the virtual machine management server storage module; and the developer debugging module is used for debugging the migrated robot system. According to the invention, the compatibility of robot system management and the debugging efficiency can be improved, and the operation cost of an enterprise is reduced.

Description

Technical Field

[0001] The present application relates to the field of robot development, and in particular to a robot system management device, medium and product. Background Art

[0002] In an era of rapid technological advancement, breakthroughs in artificial intelligence, big data, and sensors are profoundly transforming the field of robotics. Robots have moved from science fiction into reality, finding widespread application in diverse fields such as industry, healthcare, and logistics. With improvements in the precision and efficiency of robotic production, robots are now assisting in delicate medical surgeries and accelerating cargo sorting in logistics. However, with the increasing differentiation of their functions, managing diverse robotic systems has become a challenge.

[0003] Robots are widely used in various scenarios, mainly through the collaborative work of a host computer and a slave computer. The host computer is like an "intelligent hub", using algorithms and strategies to plan complex paths and develop detailed operational procedures based on task requirements. For example, in a logistics warehouse, the optimal route is planned based on factors such as the location of goods and the order of transportation. The slave computer is the "execution unit", responsible for chassis motion control, receiving instructions from the host computer, and accurately controlling hardware such as motors and drivers to achieve stable movement of the robot, complete forward and turning movements, and provide real-time feedback of motion data, helping the host computer to adjust instructions in a timely manner to ensure efficient execution of tasks. However, each robot is only compatible with one system, which brings challenges to actual management.

[0004] Traditional robot system management frameworks primarily utilize a "one-to-one" configuration model. Specifically, each robot system with a specific function is equipped with dedicated robot hardware. When building a fleet of robots to perform various tasks, different robot systems are pre-assigned to the corresponding robots based on the task type. For example, in a comprehensive logistics park, robots responsible for cargo handling are equipped with a handling system, while robots performing sorting tasks are equipped with a sorting system. These systems are closely linked to the robot hardware and cannot be modified at will.

[0005] This traditional model has numerous drawbacks. From a cost perspective, as business expands, new specialized robotic systems continue to emerge. Each new system requires the purchase of new robotic hardware. Not only is the procurement cost high, but ongoing equipment maintenance also requires significant manpower and material resources. Furthermore, numerous robots occupy significant space, significantly increasing operating costs.

[0006] In terms of system migration and compatibility, systems cannot be migrated between different robots. Once a robot is assigned a specific system, it can only perform specific tasks. For example, in a logistics park, if a robot originally used for cargo handling is temporarily needed to perform sorting tasks, its system cannot be switched and it must be idle. A dedicated sorting robot must be deployed, severely limiting the robot's flexibility, resulting in a waste of robot hardware resources and preventing its full potential from being realized.

[0007] Debugging robot systems is extremely challenging due to the difficulty of migration and low compatibility of traditional methods. Debugging is confined to the robot itself, which not only consumes a significant amount of time connecting and adapting the robot to the debugging environment, but also makes it difficult to promptly back up and migrate the debugged version of the robot system. If problems arise during debugging, previous debugging results are difficult to quickly restore, impacting overall work progress.

[0008] A systematic and comprehensive literature search revealed a patent for "A Wireless Cluster Management System for Mobile Robots" in the field of robot management technology. This system primarily consists of a central management computer, server, input device, display device, and multiple mobile robots equipped with loading and unloading bodies, cameras, microprocessors, clients, and controllers. Cluster management of multiple mobile robots is achieved through a single wireless access point, improving the convenience and centralization of robot management. However, this system has significant drawbacks. From a cost perspective, each robot system is tightly bound to the mobile robot. As business expands and functionality is refined, new robots must be deployed for each new function, significantly increasing hardware procurement, equipment maintenance, and site occupancy costs. Furthermore, the system is not portable, making it difficult for robots assigned to specific systems to switch functions, and compatibility between different systems is extremely poor. Furthermore, debugging requires debugging of the corresponding functional system on the corresponding robot, making it extremely difficult. These drawbacks severely limit the multifunctional application of robot hardware and hinder its full potential.

[0009] The patent "A method for rapid deployment of efficient practical training software based on virtual machines" is mainly used for the rapid deployment of software in colleges and universities. By creating a mother machine template that includes multimedia teaching student-side software and virtual machine management software, and transmitting the mother machine template to other physical computers through network simultaneous transmission, each student machine contains the student side and virtual machine management software, thereby creating a separate virtual machine for each practical training software for practical training, while ensuring the system unification of all student machines. This solution is more targeted at the storage and management of robot systems, so only the virtual machine management software is installed on the server side to store and manage standard images and specific function robot systems; secondly, the migration of the robot system between the server storage side, the robot testing side, and the developer development side only includes the system containing the specific function software, and does not include the migration of the virtual machine management software itself.

[0010] The patent "A design method for a robot cloud platform based on ROS" mainly sets up the cloud platform into three layers: the basic layer, the platform layer, and the service layer according to the functional level. Then, the three servers of the control node, the computing node, and the storage node of the basic layer are configured. When the robot needs computing resources, the cloud host configuration can be customized according to the task requirements, and the platform layer is requested to allocate a cloud host. Then, the Ubuntu image is transferred to the image management system using the web interface. The Ubuntu image is then used to install the operating system for the cloud host, and general software and the robot application development environment are installed. The cloud host then obtains data from the robot through network communication, consumes computing resources to process the data, and then sends the control instructions back to the robot through network communication. In addition, each time a new cloud host is opened, it must be reinstalled and configured;

[0011] The patent, "A DevOps-Based Apparatus and Method for Automated Production, Testing, and Release of Virtual Machine Images for a Cloud Platform," primarily implements an image production environment container, including automated image building tools and automated image testing tools. The patent, "A Software-Defined Cloud Desktop System and Cloud Desktop Configuration Process Management Method," primarily restructures virtual machine control methods, designing and modifying the data, application, control, and data layers of the virtual machine management platform. The goal is to develop a new virtual machine management process and cloud desktop system. This solution, however, primarily focuses on utilizing a virtual machine management system to store and manage standard images and robotic system virtual machines, and is unrelated to the design of the virtual machine management system.

[0012] Based on the above existing technology, there are the following deficiencies:

[0013] (1) Under the traditional "one-to-one" configuration model, the addition of new functional systems has led to an increase in the purchase of robot hardware, which has brought about problems such as high procurement and maintenance costs and large site occupation, significantly increasing the operating costs of enterprises.

[0014] (2) There is no migration between different robot systems. The functions of the robot are fixed after the system is set, resulting in limited flexibility of use, waste of hardware resources, and poor system compatibility.

[0015] (3) Due to the difficulty of migration and low compatibility, the robot system debugging can only be carried out on the main body. There are problems such as time-consuming connection adaptation, difficulty in backing up and migrating the debug version, and difficulty in recovering the results, which affect the progress of work.

[0016] Therefore, based on the above problems, there is an urgent need to provide a new robot system management architecture to improve the compatibility and debugging efficiency of robot system management and reduce enterprise operating costs. Summary of the Invention

[0017] The purpose of this application is to provide a robot system management device, medium and product that can improve the compatibility and debugging efficiency of robot system management and reduce enterprise operating costs.

[0018] To achieve the above objectives, this application provides the following solutions:

[0019] In a first aspect, the present application provides a robot system management device, the robot system management device comprising:

[0020] The standard image module is used to configure the robot system template and build a standard image; the standard image is used to provide a template for R&D personnel to develop a new robot system;

[0021] The virtual machine management server storage module is used to build a server virtual machine management platform based on the virtual machine management system; and store standard images and developed robot systems based on the server virtual machine management platform;

[0022] The robot system migration module is used to migrate the robot system based on the hard disk cloning system or the virtual machine management system;

[0023] The robot application module is used to deploy a virtual machine management system on the robot host computer, access the local area network via wireless, and control the corresponding robot based on the robot system migrated from the virtual machine management server storage module;

[0024] Developer debugging module, used to debug the migrated robot system.

[0025] Optionally, the robot system is used to provide various ROS function packages, VPN services, remote desktop services and graphics card support services.

[0026] Optionally, the virtual machine management server storage module includes: a mobile hard disk storage unit and a virtual machine storage unit;

[0027] The mobile hard disk storage unit is used to obtain an image based on the underlying system image and store it based on the mobile hard disk;

[0028] The virtual machine storage unit is used to obtain an image based on the underlying system image and store it in the virtual machine generated based on the virtualization platform.

[0029] Optionally, the robot system migration module specifically includes: a physical migration unit and a network migration unit;

[0030] The physical migration unit is used to clone the robot system in the form of a mirror image between the server virtual machine hard disk, the robot host computer hard disk and the developer's mobile hard disk through the network using a mobile hard disk cloning system; the server virtual machine hard disk is used to store the standard image in the virtual machine management server storage module and the developed robot system;

[0031] The network migration unit is used to add two virtual machine management systems, namely the virtual machine management server storage module and the robot application module, as nodes to the same cluster and perform migration in the web management interface of the virtual machine management system.

[0032] Optionally, the developer debugging module includes: a physical debugging unit and a network debugging unit;

[0033] The physical debugging unit is used to clone the robot host computer hard disk to the developer's mobile hard disk through the hard disk cloning system. The developer debugs the robot system according to the mobile hard disk. After the debugging is completed, the debugged robot system is migrated back to the robot host computer by cloning.

[0034] The network debugging unit is used by developers to debug and test the robot system according to the web interface of the virtual machine management system deployed on the robot host computer.

[0035] In a second aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the robot system management device when executed by a processor.

[0036] In a third aspect, the present application provides a computer program product, comprising a computer program, which implements the robot system management device when executed by a processor.

[0037] According to the specific embodiments provided in this application, this application has the following technical effects:

[0038] This application provides a robot system management device, medium and product. By using the virtualization technology of the virtual machine management system, the robot system is stored and managed in the form of a virtual machine, effectively improving the efficiency of robot system management and reducing management costs. With the help of virtual machine management system migration technology and hard disk cloning technology, the robot system can be quickly migrated between the server storage end, the robot application end, and the developer debugging end, significantly improving the application and debugging efficiency of the robot system and enhancing the migration adaptability of the robot to various systems. Relying on migration technology and virtual machine management network service technology, developers can quickly obtain the robot system to be debugged and start work. After debugging is completed, the system can be easily migrated back to the robot end for testing, greatly improving the debugging efficiency of the robot system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0040] Figure 1 This is a schematic diagram of the structure of a robot system management device in one embodiment of the present application;

[0041] Figure 2 Management-migration architecture diagram for robot systems;

[0042] Figure 3 This is a diagram showing the relationship between Ubuntu images, standard images, and robot systems;

[0043] Figure 4 This is a diagram of the physical migration operation. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0045] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0046] In an exemplary embodiment, Figure 1 and Figure 2As shown, a robot system management device is provided, which includes: a standard image module, a virtual machine management server storage module, a robot system migration module, a robot application module and a developer debugging module;

[0047] The standard image module is used to configure the robot system template and build a standard image; the standard image is used to provide a template for R&D personnel to develop a new robot system;

[0048] The virtual machine management server storage module is used to build a server virtual machine management platform based on the virtual machine management system; it also stores standard images and developed robot systems based on the server virtual machine management platform; the developed robot systems are stored in the form of virtual machines on the virtual machine management server, facilitating centralized management of all robot systems and enabling timely cloning and migration operations when needed. The server virtual machine management platform integrates the server's internal memory, graphics card, hard disk and other hardware resources through the virtual machine management system, allocates hardware resources according to actual needs, and creates virtual machines with corresponding hardware configurations;

[0049] The robot system migration module is used to migrate the robot system based on the hard disk cloning system or the virtual machine management system;

[0050] The robot application module is used to deploy a virtual machine management system on the robot host computer, access the local area network via wireless, and control the corresponding robot based on the robot system migrated from the virtual machine management server storage module;

[0051] The developer debugging module is used to debug the migrated robot system.

[0052] The standard image module is also used to provide various ROS function packages, VPN services, remote desktop services and graphics card support services.

[0053] As a specific embodiment, the virtual machine management server storage module includes: a mobile hard disk storage unit and a virtual machine storage unit;

[0054] The mobile hard disk storage unit is used to obtain an image based on the underlying system image and store it on the mobile hard disk. The specific storage process is as follows:

[0055] Get an empty mobile hard disk and a USB flash drive that meet the storage requirements, download the ubuntu-22.04.1-desktop-amd64.iso image from the Ubuntu system official website, and Figure 3As shown; burn the image to a USB flash drive to make it into a USB boot disk, then insert the empty mobile hard disk and the USB boot disk into the same computer, restart the computer, enter the BIOS boot interface and choose to boot from the mobile hard disk, then enter the empty mobile hard disk and follow the prompts of the boot disk to install it; then unplug the USB boot disk, restart the computer, enter the BIOS boot interface and still choose to boot from the mobile hard disk, then install the required software, such as github desktop, Vscode, Feishu, Clion and other basic general software, you can store the standard image as a general system template in the form of a mobile hard disk, and support cloning and migration of standard images through a hard disk cloning system similar to hard disk cloning.

[0056] The virtual machine storage unit is used to obtain an image based on the underlying system image and store it in a virtual machine generated by the virtualization platform. The specific storage process is as follows:

[0057] First, launch the virtualization platform, download the ubuntu-22.04.1-desktop-amd64.iso image from the Ubuntu system's official website, and upload it to a virtualized hard drive on the virtualization platform. Here, we'll use a local drive as an example. Then, create a virtual machine on the virtualization platform. After setting the target storage node, VM ID, and name, choose to use the ubuntu-22.04.1-desktop-amd64.iso image on the local drive. Select the desired robot system configuration, disk storage location, and disk size, as well as the slots, cores, and memory size. Configure the virtual bridge to connect to the server's direct network port. Click Create. After the virtual machine is created, launch it. Follow the prompts to install Ubuntu and the required software, such as GitHub Desktop, Vscode, Feishu, and Clion. Then, shut down the virtual machine and change the virtual machine format to a template. This completes the standard image creation process. The virtualization platform also supports cloning and migration of standard images.

[0058] The robot system migration module specifically includes: a physical migration unit and a network migration unit;

[0059] like Figure 4 As shown, the physical migration unit is used to use the mobile hard disk cloning system to clone the robot system in the form of a mirror image between the server virtual machine hard disk, the robot host computer hard disk, and the developer's mobile hard disk through the network, thereby realizing system migration between the server storage end, the robot application end, and the developer's debugging end; the server virtual machine hard disk is used to store the standard image in the virtual machine management server storage module and the developed robot system;

[0060] The network migration unit is used to add the two virtual machine management systems (VMMS)—the VM management server storage module and the robot application module—to the same cluster as nodes and perform the migration within the VMMS's web management interface. The migrated VMs are then delivered directly to the robot host computer, allowing the robot system in the VM to directly interact with the robot host computer and, ultimately, the entire robot hardware. Developers can also debug and test the robot system directly within the web interface.

[0061] The virtual machine management system's built-in clustering technology allows one virtual machine management system to be installed on the server and another virtual machine management system to be installed on the robot's host computer. These two systems are located on the same local area network, creating a PVE cluster. This allows for rapid migration of virtual machines with robot systems between the server and the robot. Furthermore, the robot's virtual machine management system only has one virtual machine, which is directly connected to all interfaces on the host computer and can directly affect the entire robot.

[0062] The developer debugging module includes: physical debugging unit and network debugging unit;

[0063] The physical debugging unit is used to clone the robot host computer hard disk to the developer's mobile hard disk through the hard disk cloning system. The developer debugs the robot system according to the mobile hard disk. After the debugging is completed, the debugged robot system is migrated back to the robot host computer by cloning.

[0064] The network debugging unit is used by developers to debug and test the robot system according to the web interface of the virtual machine management system deployed on the robot host computer.

[0065] This application uses virtualization technology (virtual machine management system) to call server hardware resources, create or clone standard mirror virtual machines that have been configured with specific resources, and use them to centrally develop, store, and manage diverse robot systems; uses virtualization technology to call the hardware resources of the robot host computer, runs the robot system migrated from the server storage end, and directly applies the system to the robot slave computer and even the entire robot; uses the migration and hard disk cloning technology of the virtual machine management server to achieve rapid cloning and migration of the robot system between the server storage end, the robot application end, and the developer debugging end; based on the migration technology, the robot system is quickly migrated to the virtual machine management server, after which the developer can directly debug the robot system in the web interface of the virtual machine management server, and quickly migrate the debugged robot system back to the robot host computer for testing.

[0066] The following describes physical migration and network migration using specific examples:

[0067] When using a physical migration method, identify the robot system to be tested and debugged. Connect the hard drive equipped with the hard drive cloning system to the robot host computer. Next, the virtual machine corresponding to the robot system on the server activates the hard drive cloning system and, through remote cloning, transfers and clones the virtual machine's hard drive data to the robot host computer. After cloning is complete, start the robot to verify the normal operation of the robot system and assess its functionality and stability. If debugging the robot system is required, connect both the hard drive of the hard drive cloning system and the developer's removable hard drive to the robot host computer. Use the hard drive cloning system to clone the robot system from the robot host computer to the removable hard drive. The developer connects the removable hard drive to their own computer and chooses to boot the system from the removable hard drive, allowing them to debug the robot system. After debugging is complete, use the same process to clone the debugged system back to the robot host computer for subsequent testing and verification. After testing is complete, connect the hard drive equipped with the hard drive cloning system to the robot host computer again. The virtual machine corresponding to the robot system on the server restarts the hard drive cloning system and, through remote cloning, clones the robot host computer's hard drive data to the server virtual machine. At this point, the robot system is uniformly stored and managed in the server in the form of a virtual machine, which is convenient for subsequent calls and maintenance.

[0068] When migrating via the network, determine the target robot system to be tested and debugged. On the server storage side, clone the virtual machine storing the corresponding robot system to create a new virtual machine, which is then migrated to the virtual machine management system on the robot's host computer. After the migration is complete, connect all devices on the robot's host computer to the virtual machine containing the corresponding robot system using direct-to-connect technology, enabling the robot system in the virtual machine to directly control the lower computers and the entire robot hardware. Next, start the robot and conduct a comprehensive test of the robot system's operational status to determine whether it is functioning properly, including whether all functions are implemented and whether it operates smoothly. If debugging is required, developers simply log in to the web interface of the robot's host computer's virtual machine management system to debug the robot system in the virtual machine. During debugging, they can adjust and optimize system parameters and functional modules as needed. After debugging is complete, rerun the robot system for testing to verify that the debugged system's performance and functionality meet requirements. Once the testing process is complete, perform operations on the web interface of the robot's host computer's virtual machine management system to migrate the virtual machine back to the virtual machine management system on the server storage side. This operation enables unified storage and management of the tested robot system, facilitating centralized maintenance, updates, and subsequent reuse.

[0069] Taking a large-scale logistics warehouse with multiple robots as an example, the application of each module is explained in detail:

[0070] In a large-scale logistics warehouse with multiple robots, robots of different configurations are needed to perform tasks such as moving, sorting, and transportation. There are several wheeled robots in the warehouse. According to the traditional management method, the robot system is bound to the robot of a specific configuration, and there is a lack of unified storage and management of various robot systems. Therefore, the device provided by this application is used;

[0071] Install a virtual machine management system on the warehouse server and build a server virtual machine management platform. First, create a standard image, download the image from the Ubuntu system official website and upload it to the virtual hard disk, create a virtual machine and configure the system and software, such as installing the logistics robot's dedicated path planning and cargo identification software, and then set it as a template. When there is a new task requirement, clone the corresponding robot system virtual machine based on the template.

[0072] A virtual machine management system is deployed on the robot's host computer, connected to the local area network via a wireless relay module. When a sorting task is required, the server migrates the robot system virtual machine corresponding to the task to the robot's host computer. Using network migration, the virtual machine is quickly migrated to the host computer through the virtual machine management system's web interface. Direct connection is then used to connect the robot's lower computer's motors, sensors, and other hardware. Once the robot is powered on, it accurately identifies the goods and completes the sorting task according to system instructions.

[0073] If the robot's sorting accuracy is low during operation, the system needs to be debugged. Developers can use network debugging to log in to the web interface of the robot's host computer's virtual machine management system and adjust the parameters of the cargo recognition algorithm. After adjustments, run the robot again for testing to see if the sorting accuracy improves. If the results are not satisfactory, continue debugging until the requirements are met.

[0074] After debugging and completing tasks, the robot system virtual machines are migrated back to the server storage. The server centrally stores and manages these systems, regularly backing up data to facilitate subsequent queries, updates, and maintenance. If new logistics tasks are required, the corresponding systems can be migrated and used from the server at any time, thereby improving the efficiency of robot system development, deployment, and debugging, and reducing operating costs.

[0075] In an exemplary embodiment, a computer-readable storage medium is provided, storing a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0076] In an exemplary embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0077] 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.

[0078] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented 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 memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may 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 may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0079] The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may include, but are not limited to, general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic units, data processing logic units based on quantum computing, and the like.

[0080] In this application, all actions to obtain signals, information or data are carried out in compliance with the relevant data protection laws and policies of the country where they are located and with the authorization given by the owner of the corresponding device.

[0081] The technical features of the above embodiments can 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 specification.

[0082] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above examples is only intended to help understand the method and core concept of this application. At the same time, for those skilled in the art, based on the concept of this application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A robot system management device, characterized in that: The robot system management device includes: The standard image module is used to configure the robot system template and build a standard image; the standard image is used to provide a template for R&D personnel to develop a new robot system; The virtual machine management server storage module is used to build a server virtual machine management platform based on the virtual machine management system; and store standard images and developed robot systems based on the server virtual machine management platform; The robot system migration module is used to migrate the robot system based on the hard disk cloning system or the virtual machine management system; The robot application module is used to deploy a virtual machine management system on the robot host computer, access the local area network via wireless, and control the corresponding robot based on the robot system migrated from the virtual machine management server storage module; Developer debugging module, used to debug the migrated robot system.

2. The robot system management device according to claim 1, characterized in that: The robot system is used to provide various ROS function packages, VPN services, remote desktop services and graphics card support services.

3. The robot system management device according to claim 1, characterized in that: The virtual machine management server storage module includes: a mobile hard disk storage unit and a virtual machine storage unit; The mobile hard disk storage unit is used to obtain an image based on the underlying system image and store it based on the mobile hard disk; The virtual machine storage unit is used to obtain an image based on the underlying system image and store it in the virtual machine generated based on the virtualization platform.

4. The robot system management device according to claim 1, characterized in that: The robot system migration module specifically includes: a physical migration unit and a network migration unit; The physical migration unit is used to clone the robot system in the form of a mirror image between the server virtual machine hard disk, the robot host computer hard disk and the developer's mobile hard disk through the network using a mobile hard disk cloning system; the server virtual machine hard disk is used to store the standard image in the virtual machine management server storage module and the developed robot system; The network migration unit is used to add two virtual machine management systems, namely the virtual machine management server storage module and the robot application module, as nodes to the same cluster and perform migration in the web management interface of the virtual machine management system.

5. The robot system management device according to claim 1, characterized in that: The developer debugging module includes: physical debugging unit and network debugging unit; The physical debugging unit is used to clone the robot host computer hard disk to the developer's mobile hard disk through the hard disk cloning system. The developer debugs the robot system according to the mobile hard disk. After the debugging is completed, the debugged robot system is migrated back to the robot host computer by cloning. The network debugging unit is used by developers to debug and test the robot system according to the web interface of the virtual machine management system deployed on the robot host computer.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the robot system management device according to any one of claims 1 to 5 is implemented.

7. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the robot system management device according to any one of claims 1 to 5 is implemented.

Images