CN112763251A - Mobile robot testing method and device - Google Patents
Mobile robot testing method and device Download PDFInfo
- Publication number
- CN112763251A CN112763251A CN202110048311.5A CN202110048311A CN112763251A CN 112763251 A CN112763251 A CN 112763251A CN 202110048311 A CN202110048311 A CN 202110048311A CN 112763251 A CN112763251 A CN 112763251A
- Authority
- CN
- China
- Prior art keywords
- robot
- mobile robot
- test
- detection result
- test file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 123
- 238000001514 detection method Methods 0.000 claims abstract description 71
- 238000000034 method Methods 0.000 claims abstract description 35
- 238000003860 storage Methods 0.000 claims abstract description 32
- 230000002159 abnormal effect Effects 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 20
- 238000005259 measurement Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 230000008878 coupling Effects 0.000 description 5
- 238000010168 coupling process Methods 0.000 description 5
- 238000005859 coupling reaction Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 239000000428 dust Substances 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M99/00—Subject matter not provided for in other groups of this subclass
- G01M99/005—Testing of complete machines, e.g. washing-machines or mobile phones
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B25—HAND TOOLS; PORTABLE POWER-DRIVEN TOOLS; MANIPULATORS
- B25J—MANIPULATORS; CHAMBERS PROVIDED WITH MANIPULATION DEVICES
- B25J19/00—Accessories fitted to manipulators, e.g. for monitoring, for viewing; Safety devices combined with or specially adapted for use in connection with manipulators
- B25J19/0095—Means or methods for testing manipulators
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
- G01M99/00—Subject matter not provided for in other groups of this subclass
- G01M99/008—Subject matter not provided for in other groups of this subclass by doing functionality tests
Abstract
The application is applicable to the technical field of mobile robots and provides a method and a device for testing the functional state of a mobile robot, wherein the method comprises the following steps: detecting whether a robot test file exists in a set storage space of the mobile robot; when the robot test file exists, running the robot test file to detect the mobile robot; and sending the robot detection result to an upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report. Therefore, the automatic test process for the robot is realized, the manpower test cost can be reduced, and the test efficiency of the robot is improved.
Description
Technical Field
The application belongs to the technical field of mobile robots, and particularly relates to a mobile robot testing method and device.
Background
With the continuous development of industrial automation process and modern technology level, the mobile robot technology is also continuously updated iteratively. The robot needs to test the mobile robot regularly or irregularly in order to complete a specified task well, and during mass production of the mobile robot, the mobile robot needs to detect the completion of assembly so as to ensure good performance in the actual working process.
In the related art at present, the performance of the mobile robot is usually detected by adopting a manual observation test mode, the time required for manual observation is very long, a large amount of manpower is consumed, the subjective judgment of workers is relied on, errors are easy to occur, the efficiency is low, and the related test results are not convenient to manage.
In view of the above problems, no better solution is available in the industry.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for testing a mobile robot, so as to at least solve the problems in the prior art that a manual testing robot is prone to error, low in efficiency, and difficult to manage a test result.
A first aspect of an embodiment of the present application provides a mobile robot testing method, including: detecting whether a robot test file exists in a set storage space of the mobile robot; when the robot test file exists, running the robot test file to detect the mobile robot; and sending the robot detection result to an upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
A second aspect of the embodiments of the present application provides a mobile robot testing apparatus, including: a test file detection unit configured to detect whether a robot test file exists in a set storage space of the mobile robot; a mobile robot detection unit configured to run the robot test file to detect the mobile robot when the robot test file exists; and the detection result sending unit is configured to send the robot detection result to the upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
A third aspect of embodiments of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, in which a computer program is stored, which, when executed by a processor, implements the steps of the method as described above.
A fifth aspect of embodiments of the present application provides a computer program product, which, when run on an electronic device, causes the electronic device to implement the steps of the method as described above.
Compared with the prior art, the embodiment of the application has the advantages that:
according to the embodiment of the application, the mobile robot can detect and call the robot test file in the set storage space to detect the mobile robot, corresponding detection results are sent to the upper computer, and the robot abnormal standard file in the upper computer is verified, so that a corresponding robot test report is obtained. Therefore, various performances of the mobile robot can be automatically tested, the labor test cost can be reduced, the robot test efficiency is improved, and a robot test report can be effectively stored in the upper computer.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 shows a flow diagram of an example of a mobile robot testing method according to an embodiment of the application;
FIG. 2 shows a signal interaction diagram of an example of a mobile robot testing method according to an embodiment of the application;
FIG. 3 shows a flow diagram of an example of burn-in testing of a mobile robot according to an embodiment of the application;
FIG. 4 shows a block diagram of an example of a mobile robotic testing device according to an embodiment of the present application;
fig. 5 is a schematic diagram of an example of an electronic device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In particular implementations, the electronic devices described in embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers having touch sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the devices described above are not portable communication devices, but are computers having touch-sensitive surfaces (e.g., touch screen displays).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may include one or more other physical user interface devices such as a physical keyboard, mouse, and/or joystick.
Various applications that may be executed on the electronic device may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the terminal can be adjusted and/or changed between applications and/or within respective applications. In this way, a common physical architecture (e.g., touch-sensitive surface) of the terminal can support various applications with user interfaces that are intuitive and transparent to the user.
Fig. 1 shows a flow chart of an example of a mobile robot testing method according to an embodiment of the application. Regarding the execution subject of the method of the embodiment of the present application, it may be a mobile robot.
As shown in fig. 1, in step 110, it is detected whether a robot test file exists in a set storage space of the mobile robot. Here, the mobile robot may trigger a file detection operation for the set storage space upon receiving a user operation, and may also autonomously trigger (e.g., periodically or aperiodically) a file detection operation for the set storage space.
In step 120, when the robot test file exists, the robot test file is run to detect the mobile robot. Furthermore, if the robot test file does not exist in the setting storage space, it may indicate that the robot does not need to perform a test operation but may perform an operation procedure corresponding to the operation mode.
In step 130, the robot detection result is sent to the upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
According to the embodiment of the application, the mobile robot can be tested by utilizing the robot test file in the set storage space, and the robot test result can be effectively verified by combining the robot abnormal standard file in the upper computer, and a corresponding robot test report can be obtained through automatic evaluation.
Fig. 2 shows a signal interaction diagram of an example of a mobile robot testing method according to an embodiment of the present application.
As shown in fig. 2, in step 210, the upper computer 20 may import the robot test file 210 into the mobile robot 10. In some cases, a tester may define test items (e.g., a battery, radar, and code wheel of a mobile robot, etc.) in a robot test file by programming operations on an upper computer to generate a corresponding robot test file.
In step 220, the mobile robot 10 may detect whether a robot test file exists in the set storage space according to the power-on command. In this way, when the mobile robot 10 is powered on, the detection operation for the robot test file can be automatically triggered.
In some embodiments, the mobile robot may execute a restart operation when the robot test file is successfully written into the set storage space, and automatically trigger a detection operation for the robot test file when the mobile robot is started, so as to implement a full-process automatic test operation for the mobile robot after the robot test file is written into the mobile robot.
In step 230, the mobile robot 10 performs a test according to the robot test file and generates a corresponding robot detection result. Here, the robot detection result may include detection results of multiple dimensions, for example, detection results for different components in the robot.
In step 240, the robot test file may be deleted after the mobile robot 10 has completed the robot detection process. Therefore, after the mobile robot completes the test, the local test file can be automatically deleted, the coupling of the program can be reduced, and the local storage space of the mobile robot can be released.
In step 250, the mobile robot 10 transmits the robot detection result to the upper computer 20.
In step 260, the upper computer 20 may verify the robot detection result by using the robot abnormal standard file and generate a corresponding robot test report. Here, the robot abnormality standard file may be a standard for evaluating an abnormality of one or more specific parts in the robot, such as an excessive motor current or an insufficient battery voltage of the mobile robot, or the like.
In step 270, the upper computer 20 performs a malfunction warning operation when the robot detection result is abnormal. Here, various failure alarm manners, such as an alarm manner of sound, flashing light, and the like, may be employed. Therefore, when the robot is detected to be abnormal, the user can be reminded to pay attention to the tested mobile robot in an alarm mode, the user can find out the fault robot in time and maintain the fault robot conveniently, and the qualification rate of the mobile robot is guaranteed.
In some embodiments, the robot anomaly criteria file includes a plurality of component failure criteria that may be used to evaluate whether a failure condition exists for a corresponding one or more components. Accordingly, the robot detection result comprises a plurality of part detection results corresponding to the robot test file, and the state of the robot is determined by comprehensively considering the detection conditions of different parts in the robot, so that the reliability of the test result is guaranteed.
In an example of the embodiment of the present application, the component failure criterion may be uniquely corresponding to a component in the mobile robot, and the upper computer may further check a corresponding first component detection result by using the first component failure criterion, and when the component identification information corresponding to the first component detection result and the failure information corresponding to the first component abnormality criterion are matched, record the component identification information corresponding to the first component detection result and the failure information in the robot test report.
For example, corresponding component failure standards may exist for different components in the robot, for example, the component failure standards corresponding to the dust box sensor and the motor of the robot may be different, whether the motor has a failure may be identified by detecting the current of the motor, whether the dust box sensor has a failure may be identified by the trigger condition of the dust box sensor, and the like.
In another example of an embodiment of the present application, the component failure criterion may correspond to a combination of a plurality of components in the mobile robot. Specifically, the upper computer may further verify the corresponding combined plurality of second component detection results by using the second component failure standard, and record failure information corresponding to the second component failure standard in the robot test report when each of the second component detection results meets the second component failure standard.
For example, when a specific fault information of the mobile robot cannot be determined by the sensing signals of a single component, the sensing signals of a plurality of components of the mobile robot can be considered together for identification. Specifically, the part detection result may be a sensor signal, and the combined plurality of second part detection results may be a combination of an inertia measurement result, a code wheel speed signal, and a motor current, and accordingly, if the respective detection results of the above combination each satisfy a respective part failure criterion, it may be determined that the mobile robot has robot slip failure information.
Fig. 3 shows a flowchart of an example of burn-in testing of a mobile robot according to an embodiment of the application.
As shown in fig. 3, in step 310, the mobile robot that has been assembled is connected to an upper computer of the factory. At this time, the upper computer may transmit an instruction to the mobile robot device to generate a test file in the storage space of the mobile robot.
In step 320, the mobile robot after the installation is transported to the treadmill test stand by the transfer device.
In step 330, after the mobile robot is placed in the test stand, the mobile robot power-on key is triggered to perform automatic testing, and the robot detection result is recorded.
Specifically, after the mobile robot is started, a detection program can be automatically started, the machine is detected to be a test file, and if the machine is detected to be a test file, the program can carry out automatic test; if no test file exists, the mobile robot enters a normal working mode.
In addition, after the mobile robot completes detection, the mobile robot can delete the test file, so that the coupling of the program is reduced, and the performance loss is reduced.
In step 340, after the mobile robot completes the test, the robot detection result is sent to the upper computer for analysis and storage by the upper computer. Specifically, after the upper computer obtains the report, the upper computer can read the data and compare the data with normal data, if the data are abnormal, the type and the abnormal field of the robot can be prompted to be repaired later, and if the data are not abnormal, a test report corresponding to the serial number of the robot can be generated and stored.
Table 1 exemplary robot anomaly criteria file
As shown in table 1, the robot anomaly criteria file may include a plurality of component failure criteria, each component failure criteria having a mapping relationship with sensor identification, component failure detection type, and failure information. Specifically, the component failure detection types of the robot may be classified into a single type or a combined type. In the single type, only a single component in the mobile robot needs to be detected, and the component can be compared with a corresponding component fault standard, so as to identify whether the mobile robot has corresponding fault information, for example, when the inertial measurement unit is detected to have a problem of too large relevant declination, the mobile robot can be determined not to be placed on a horizontal ground. In the combination type, the upper computer may comprehensively consider the detection results of a plurality of components in the mobile robot and compare the detection results with corresponding component fault criteria, so as to identify whether the mobile robot has corresponding fault information, for example, when it is detected that the code wheel speed is lower than a first set threshold value and the motor current is lower than a second set threshold value, it may be determined that the mobile robot runs slowly.
It should be noted that, in the component failure criteria of the corresponding combination type as in table 1, the order of the detection components for the combination may not be distinguished, for example, in the "robot jogging" failure, the code wheel or the motor may be detected first, or both may be detected simultaneously, which may not affect the result of failure recognition.
In some cases, once the mobile robot enters the testing process, the mobile robot may generate a test report that may record information such as the time of the test, the results of the test, and the associated sensor data.
Through the embodiment of the application, the mobile robot can be automatically tested, whether the mobile robot needs to have abnormal conditions or not can be judged according to the sensor numerical value detection, the automatic detection of the robot and the informatization and intellectualization of a factory are efficiently realized, the cost is reduced while the efficiency and the accuracy are improved, and the human resource consumption is saved.
Fig. 4 is a block diagram illustrating an example of a mobile robot testing apparatus according to an embodiment of the present application.
As shown in fig. 4, the mobile robot testing apparatus 400 includes a test file detecting unit 410, a mobile robot detecting unit 420, and a detection result transmitting unit 430.
The test file detecting unit 410 is configured to detect whether a robot test file exists in a set storage space of the mobile robot.
The mobile robot detection unit 420 is configured to run the robot test file to detect the mobile robot when the robot test file exists.
The detection result sending unit 430 is configured to send the robot detection result to the upper computer, so that the upper computer verifies the robot detection result by using a preset robot anomaly standard file, and generates a corresponding robot test report.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
Fig. 5 is a schematic diagram of an example of an electronic device according to an embodiment of the present application. As shown in fig. 5, the electronic apparatus 500 of this embodiment includes: a processor 510, a memory 520, and a computer program 530 stored in the memory 520 and executable on the processor 510. The processor 510, when executing the computer program 530, implements the steps in the above described mobile robot testing method embodiments, such as the steps 110 to 130 shown in fig. 1. Alternatively, the processor 510, when executing the computer program 530, implements the functions of the modules/units in the above-mentioned device embodiments, such as the functions of the units 410 to 430 shown in fig. 4.
Illustratively, the computer program 530 may be partitioned into one or more modules/units that are stored in the memory 520 and executed by the processor 510 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 530 in the electronic device 500. For example, the computer program 530 may be divided into a test file detection program module, a mobile robot detection program module, and a detection result sending program module, and each program module has the following specific functions:
the test file detection program module is configured to detect whether a robot test file exists in a set storage space of the mobile robot;
the mobile robot detection program module is configured to run the robot test file to detect the mobile robot when the robot test file exists;
the detection result sending program module is configured to send the robot detection result to the upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
The electronic device 500 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing devices. The electronic device may include, but is not limited to, a processor 510, a memory 520. Those skilled in the art will appreciate that fig. 5 is only an example of an electronic device 500 and does not constitute a limitation of the electronic device 500 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the electronic device may also include input-output devices, network access devices, buses, etc.
The Processor 510 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 520 may be an internal storage unit of the electronic device 500, such as a hard disk or a memory of the electronic device 500. The memory 520 may also be an external storage device of the electronic device 500, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 500. Further, the memory 520 may also include both an internal storage unit and an external storage device of the electronic device 500. The memory 520 is used for storing the computer programs and other programs and data required by the electronic device. The memory 520 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/electronic device and method may be implemented in other ways. For example, the above-described apparatus/electronic device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The above units can be implemented in the form of hardware, and also can be implemented in the form of software.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A mobile robot testing method, comprising:
detecting whether a robot test file exists in a set storage space of the mobile robot;
when the robot test file exists, running the robot test file to detect the mobile robot;
and sending the robot detection result to an upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
2. The method of claim 1, wherein said detecting whether a robot test file exists in a set storage space of the mobile robot comprises:
detecting whether a robot test file exists in the set storage space or not according to a starting instruction of the mobile robot;
and, after completing the test operation for the mobile robot, the method further comprises:
and deleting the robot test file.
3. The method of claim 2, wherein before detecting whether a robot test file exists in the set storage space according to a start instruction of the mobile robot, the method further comprises:
receiving a robot test file from the upper computer, and writing the robot test file into a set storage space;
and when the robot test file is successfully written into the set storage space, executing restarting operation.
4. The method of claim 1, wherein the upper computer is further configured to perform a robot fault alert operation when an anomaly in the robot detection result is identified using the robot anomaly criteria file.
5. The method of claim 1, wherein the robot anomaly criteria file includes a plurality of component failure criteria, and the robot test results include a plurality of component test results corresponding to the robot test file,
the upper computer is further configured to verify a corresponding first component detection result by using a first component fault standard, and when the first component detection result is matched with the first component detection result, record component identification information corresponding to the first component detection result and fault information corresponding to the first component abnormal standard in the robot test report.
6. The method of claim 5, wherein the host computer is further configured to verify the respective combined plurality of second component detection results using a second component failure criterion, and to record failure information corresponding to the second component failure criterion in the robot test report when each of the second component detection results meets the second component failure criterion.
7. The method of claim 6 wherein said part detection result is a sensor signal, wherein said combined plurality of second part detection results is a combination of an inertial measurement, a code wheel speed signal and a motor current, and wherein said second part failure criteria corresponds to failure information that is robot slip failure information.
8. A mobile robot testing device, comprising:
a test file detection unit configured to detect whether a robot test file exists in a set storage space of the mobile robot;
a mobile robot detection unit configured to run the robot test file to detect the mobile robot when the robot test file exists;
and the detection result sending unit is configured to send the robot detection result to the upper computer, so that the upper computer verifies the robot detection result by using a preset robot abnormal standard file and generates a corresponding robot test report.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to any of claims 1-7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110048311.5A CN112763251A (en) | 2021-01-14 | 2021-01-14 | Mobile robot testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110048311.5A CN112763251A (en) | 2021-01-14 | 2021-01-14 | Mobile robot testing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112763251A true CN112763251A (en) | 2021-05-07 |
Family
ID=75700554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110048311.5A Pending CN112763251A (en) | 2021-01-14 | 2021-01-14 | Mobile robot testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112763251A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114425787A (en) * | 2021-12-21 | 2022-05-03 | 深圳优地科技有限公司 | Control method and device for robot automatic test, server and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170277614A1 (en) * | 2016-03-25 | 2017-09-28 | Adlink Technology Inc. | Intelligent test robot system |
| CN107972070A (en) * | 2017-11-29 | 2018-05-01 | 上海新时达机器人有限公司 | Test method, test system and the computer-readable recording medium of robot performance |
| CN109324601A (en) * | 2018-11-09 | 2019-02-12 | 上海机器人产业技术研究院有限公司 | The test platform of robot controller or control system based on hardware in loop |
| CN111190825A (en) * | 2019-12-28 | 2020-05-22 | 深圳市优必选科技股份有限公司 | Automatic test method, system and robot |
| CN111198790A (en) * | 2019-12-23 | 2020-05-26 | 深圳市优必选科技股份有限公司 | Robot testing method, robot testing device and robot |
| CN111829583A (en) * | 2020-07-03 | 2020-10-27 | 珠海格力智能装备有限公司 | Robot testing method and device |
-
2021
- 2021-01-14 CN CN202110048311.5A patent/CN112763251A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170277614A1 (en) * | 2016-03-25 | 2017-09-28 | Adlink Technology Inc. | Intelligent test robot system |
| CN107972070A (en) * | 2017-11-29 | 2018-05-01 | 上海新时达机器人有限公司 | Test method, test system and the computer-readable recording medium of robot performance |
| CN109324601A (en) * | 2018-11-09 | 2019-02-12 | 上海机器人产业技术研究院有限公司 | The test platform of robot controller or control system based on hardware in loop |
| CN111198790A (en) * | 2019-12-23 | 2020-05-26 | 深圳市优必选科技股份有限公司 | Robot testing method, robot testing device and robot |
| CN111190825A (en) * | 2019-12-28 | 2020-05-22 | 深圳市优必选科技股份有限公司 | Automatic test method, system and robot |
| CN111829583A (en) * | 2020-07-03 | 2020-10-27 | 珠海格力智能装备有限公司 | Robot testing method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114425787A (en) * | 2021-12-21 | 2022-05-03 | 深圳优地科技有限公司 | Control method and device for robot automatic test, server and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10387239B2 (en) | Detecting memory failures in the runtime environment | |
| US8291379B2 (en) | Runtime analysis of a computer program to identify improper memory accesses that cause further problems | |
| US20130030753A1 (en) | Testing system and method using same | |
| US7293204B2 (en) | Computer peripheral connecting interface system configuration debugging method and system | |
| CN102928690B (en) | For the method for detecting abnormality of electron device | |
| CN111949457A (en) | Server fault chip detection method and device | |
| CN105045714A (en) | Method and device for testing starting duration of application software and terminal | |
| CN110188013A (en) | A kind of log read-write capability test method, device and electronic equipment and storage medium | |
| CN104239174A (en) | BMC (baseboard management controller) remote debugging system and method | |
| CN113832663B (en) | Control chip fault recording method and device and control chip fault reading method | |
| CN112763251A (en) | Mobile robot testing method and device | |
| CN106021024A (en) | Method for reminding response stopping of user terminal, and user terminal | |
| CN110879701B (en) | Workflow visual configuration method, server, system and medium | |
| CN108520063B (en) | Event log processing method and device and terminal equipment | |
| CN115422091B (en) | Firmware debugging method and device, electronic equipment and storage medium | |
| US20190004903A1 (en) | Data Restoration Method and Apparatus, and Terminal | |
| CN110941549A (en) | Memory leak detection method, device, medium and electronic equipment | |
| US20140258793A1 (en) | Detecting system and method for motherboard | |
| CN102750234B (en) | The control method of memorizer and controller | |
| US20210216429A1 (en) | Diagnostic system | |
| CN113741985A (en) | Method, device and equipment for cold start of system after BIOS (basic input output System) upgrade and readable medium | |
| CN112912855A (en) | Starting-up detection method, starting-up detection device and mobile terminal | |
| EP3557422A1 (en) | Method for accessing code sram, and electronic device | |
| CN111078550A (en) | Software testing method and device, computer device and storage medium | |
| CN111209146A (en) | RAID card aging test method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210507 |
|
| RJ01 | Rejection of invention patent application after publication |