CN114237196A - Split robot fault processing method and device, terminal equipment and medium - Google Patents
Split robot fault processing method and device, terminal equipment and medium Download PDFInfo
- Publication number
- CN114237196A CN114237196A CN202111349156.7A CN202111349156A CN114237196A CN 114237196 A CN114237196 A CN 114237196A CN 202111349156 A CN202111349156 A CN 202111349156A CN 114237196 A CN114237196 A CN 114237196A
- Authority
- CN
- China
- Prior art keywords
- alarm
- robot
- fault
- split
- split robot
- 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
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Manipulator (AREA)
Abstract
The invention discloses a fault processing method, a fault processing device, terminal equipment and a medium for a split robot, wherein the method comprises the following steps: acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot; acquiring an alarm condition in an alarm example; judging whether the split robot has a fault or not according to the equipment information and the alarm condition; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot. By adopting the invention, the fault processing time of the robot can be shortened, and the convenience and the practicability of the fault processing of the robot are improved.
Description
Technical Field
The invention relates to the technical field of automation, in particular to a split robot fault processing method, a split robot fault processing device, terminal equipment and a medium.
Background
With the continuous improvement of the application scale of the robot, the dispatching of all split robots in one place is realized at present. The split robots include, for example, a robot having a mobile chassis as a lower body (may be simply referred to as a lower body robot or a chassis robot) and a robot having a custom upper deck as an upper body (may be simply referred to as an upper body robot), so as to cope with different scenes and functions. The upper body robot can be one or more cabins, and can also be a garbage recycling device and the like. When the task is executed, the scheduling system calls a lower body robot and an upper body robot combination according to different requirements, robot state positions and the like, and then executes the corresponding task.
In practical application, as the number of split robots in a place increases, the failure of the lower body robot in moving in a complex environment and the failure probability of the upper body robot increase, which both result in the failure of the robot in executing tasks. And the engineer will not find and deal with the problem until after the customer feedback, which results in a significant increase in the time to deal with the robot malfunction. Based on this, how to monitor and warn the fault of the robot is an important problem which needs to be solved at present.
Disclosure of Invention
The embodiment of the application provides a split robot fault processing method, and solves the technical problems that in the prior art, the fault processing time is too long when a robot fault is notified by manual alarm, and the like.
In one aspect, the present application provides a method for handling a fault of a split robot according to an embodiment of the present application, where the method includes:
acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot;
acquiring an alarm condition in an alarm example;
judging whether the split robot has a fault or not according to the equipment information and the alarm condition;
and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot.
Optionally, before obtaining the alarm condition in the alarm example, the method further includes:
configuring different alarm templates for different alarm types;
generating an alarm example corresponding to the alarm type according to the alarm template;
the alarm types are in one-to-one correspondence with the alarm templates, and the alarm examples comprise alarm conditions with different alarm indexes.
Optionally, the determining, according to the device information and the alarm condition, whether the split robot has a fault includes:
judging whether the split robot has a fault or not by judging whether the equipment information meets the corresponding alarm condition or not;
when the equipment information meets the corresponding alarm condition, determining that the split robot has a fault;
and when the equipment information does not meet the corresponding alarm condition, determining that the split robot has no fault.
Optionally, the method further comprises:
and when the split robot has no fault, the upper cabin of the robot which belongs to the same type as the split robot is dispatched to replace the split robot.
Optionally, the performing, by the split robot, an alarm process indicated by the target alarm type includes any one of:
when the target alarm type is an emergency alarm type, stopping the operation of the split robot, and immediately sending the equipment information of the split robot to a corresponding maintenance platform so as to perform fault maintenance on the split robot;
when the target alarm type is an important alarm type, sending the equipment information of the split robot to a corresponding maintenance platform to wait for fault maintenance of the split robot;
and when the target alarm type is a warning type, sending the equipment information of the split robot to a corresponding maintenance platform to remind the split robot of a fault.
Optionally, the device information further comprises at least one of: and the part index data, the equipment operation data and the motion trail data of the split robot.
Optionally, the method further comprises:
receiving an error fault code related to the target alarm type, wherein the error fault code is used for indicating that the split robot executes the re-operation of the target instruction again;
and executing the re-operation indicated by the target instruction again according to the indication of the error fault code.
In another aspect, the present application provides a split robot fault handling apparatus according to an embodiment of the present application, the apparatus including:
the acquisition module is used for acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot;
the obtaining module is further configured to obtain an alarm condition in an alarm example;
the judging module is used for judging whether the split robot has a fault or not according to the equipment information and the alarm condition;
and the alarm module is used for determining a target alarm type corresponding to the equipment information and carrying out alarm processing indicated by the target alarm type on the split robot if the judgment module judges that the split robot has a fault.
For the content that is not described or not illustrated in the embodiments of the present application, reference may be made to the related description in the foregoing method embodiments, and details are not repeated here.
On the other hand, the present application provides a terminal device according to an embodiment of the present application, where the terminal device includes: a processor, a memory, a communication interface, and a bus; the processor, the memory and the communication interface are connected through the bus and complete mutual communication; the memory stores executable program code; the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the split robot fault handling method as described above.
On the other hand, the present application provides a computer-readable storage medium storing a program that executes the split robot fault handling method as described above when the program runs on a terminal device, through an embodiment of the present application.
One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: the method comprises the steps of obtaining equipment information of the split robot and alarm conditions in an alarm example, and then judging whether the split robot has a fault or not according to the equipment information and the alarm conditions; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot. In the above scheme, this application can carry out fault judgment to the components of a whole that can function independently robot based on the equipment information of components of a whole that can function independently robot and the condition of reporting an emergency and asking for help or increased vigilance that preset, with it is right when components of a whole that can function independently robot breaks down the components of a whole that can function independently robot carries out the processing of reporting an emergency and asking for help or increased vigilance of corresponding target type, and the engineer's of being convenient for is hierarchical/categorised maintenance robot, has shortened the fault handling time of robot, has promoted robot fault handling's convenience and practicality.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a split robot fault handling method according to an embodiment of the present application.
Fig. 2 is a schematic structural diagram of a split robot fault handling device according to an embodiment of the present application.
Fig. 3 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a split robot fault processing method, and solves the technical problems that in the prior art, the fault processing time is too long when a robot fault is notified by manual alarm, and the like.
In order to solve the technical problems, the general idea of the embodiment of the application is as follows: acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot; acquiring an alarm condition in an alarm example; judging whether the split robot has a fault or not according to the equipment information and the alarm condition; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot.
In order to better understand the technical solution, the technical solution will be described in detail with reference to the drawings and the specific embodiments.
First, it is stated that the term "and/or" appearing herein is merely one type of associative relationship that describes an associated object, meaning that three types of relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Fig. 1 is a schematic flow chart of a method for handling a fault of a split robot according to an embodiment of the present disclosure. The method as shown in fig. 1 comprises the following implementation steps:
s101, obtaining equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot.
The device information in the present application refers to performance data for describing the split robot, which may include, but is not limited to, any one or a combination of more than one of the following: heartbeat data of the split robot, index data of all hardware components forming the split robot, current motion trail data of the split robot, current equipment operation data of the split robot and the like. In practical applications, the device information of the split robots is usually in the form of a configuration file (e.g., a log, etc.), the device information of the split robots in the configuration file can be obtained in the present application, the number of the split robots is not limited in the present application, and the present application is illustrated below by using one split robot as an example, but is not limited in the present application.
The method provided by the embodiment of the application can be applied to terminal equipment, such as a smart phone, a platform computer, a gateway service and the like, can also be applied to a server which is established with data interaction with the terminal equipment, and can also be applied to a system which is composed of the terminal equipment and the server, and the method is not limited herein. For example, the acquisition agent may be deployed on a gateway service that receives the device information of the split robot in advance, and the gateway service of the present application may receive the device information reported by the split robot, and the like, through the acquisition agent.
S102, acquiring an alarm condition in the alarm example.
The number of the alarm examples and the number of the alarm conditions in the alarm examples are not limited, and may be one or more. In some possible embodiments, different alarm templates may be configured for different alarm types in advance, where the alarm types correspond to the alarm templates one to one. Further, the present application generates corresponding alarm examples according to different alarm templates, specifically, the alarm examples include respective alarm conditions of different alarm indexes, and the present application may configure a corresponding alarm threshold for each alarm index in the alarm examples to form corresponding alarm conditions.
S103, judging whether the split robot has a fault or not according to the equipment information and the alarm condition.
In a specific embodiment, the present application may determine whether the split robot has a fault by determining whether the device information satisfies an alarm condition in a corresponding alarm example. Specifically, when the device information satisfies the corresponding alarm condition, it may be determined/considered that the split robot has a fault, and the step S104 is continuously performed. Otherwise, determining that the split robot has no fault, and ending the process.
And S104, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot.
Several possible embodiments are described below with respect to step S104.
In a specific embodiment, when the target alarm type is an emergency alarm type, the method and the system can immediately stop the operation of the split robot, and immediately send the equipment information of the split robot to a corresponding maintenance platform/engineer in the form of message, voice and vibration so as to perform corresponding fault maintenance on the split robot. In a specific implementation, for example, the application may send the device information and the determined fault information of the split robot to an after-sales team of the corresponding device platform or automatically submit an after-sales work order in the form of a repair work order, so as to perform fault repair on the split robot, and the like, which is not limited in the invention.
In another specific embodiment, when the target alarm type is an important alarm type, the method and the system can immediately send the equipment information of the split robot to a corresponding maintenance platform/engineer in a message and vibration square mode so as to perform corresponding fault maintenance on the split robot.
In another specific embodiment, when the target alarm type is a warning type, the method and the system can send the device information of the split robot to a corresponding maintenance platform/engineer in a message form to remind the split robot of a fault.
Some alternative embodiments to which the present application is directed are described below.
In some optional embodiments, when it is determined that the split robot has no fault, other robots belonging to the same type as the split robot may be scheduled to go to the cabin to replace the split robot to work, so as to ensure smooth completion of the work task of the robot.
In some optional embodiments, after determining the target alarm type, the present application may further send an error fault code corresponding to the alarm level, where the error fault code is used to characterize/instruct the split robot to perform the re-operation of the target instruction again (e.g., the last task instruction, etc.). Correspondingly, after the error fault code is detected/received, the corresponding re-operation indicated by the target instruction is executed again according to the indication of the error fault code.
By implementing the embodiment of the application, the split robot is judged whether a fault occurs or not according to the equipment information and the alarm condition in the alarm example by acquiring the equipment information and the alarm condition of the split robot; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot. In the above scheme, this application can carry out fault judgment to the components of a whole that can function independently robot based on the equipment information of components of a whole that can function independently robot and the condition of reporting an emergency and asking for help or increased vigilance that preset, with it is right when components of a whole that can function independently robot breaks down the components of a whole that can function independently robot carries out the processing of reporting an emergency and asking for help or increased vigilance of corresponding target type, and the engineer's of being convenient for is hierarchical/categorised maintenance robot, has shortened the fault handling time of robot, has promoted robot fault handling's convenience and practicality.
Based on the same inventive concept, another embodiment of the present application provides a device and a terminal device corresponding to the split robot fault handling method in the embodiment of the present application.
Fig. 2 is a schematic structural diagram of a split robot fault handling device according to an embodiment of the present disclosure. The apparatus 20 shown in fig. 2 comprises: an acquisition module 201, a judgment module 202 and an alarm module 203. Wherein:
the acquiring module 201 is configured to acquire device information of the split robot, where the device information at least includes heartbeat data of the split robot;
the obtaining module 201 is further configured to obtain an alarm condition in an alarm example;
the judging module 202 is configured to judge whether the split robot has a fault according to the device information and the alarm condition;
the alarm module 203 is configured to determine a target alarm type corresponding to the device information and perform alarm processing indicated by the target alarm type on the split robot if the determining module 202 determines that the split robot has a fault.
Optionally, the apparatus further comprises a configuration module 204 and a processing module 205, wherein:
the configuration module 204 is further configured to configure different alarm templates for different alarm types;
the processing module 205 is further configured to generate an alarm example corresponding to the alarm type according to the alarm template;
the alarm types are in one-to-one correspondence with the alarm templates, and the alarm examples comprise alarm conditions with different alarm indexes.
Optionally, the determining module 202 is specifically configured to:
judging whether the split robot has a fault or not by judging whether the equipment information meets the corresponding alarm condition or not;
when the equipment information meets the corresponding alarm condition, determining that the split robot has a fault;
and when the equipment information does not meet the corresponding alarm condition, determining that the split robot has no fault.
Optionally, the processing module 205 is further configured to:
and when the split robot has no fault, the upper cabin of the robot which belongs to the same type as the split robot is dispatched to replace the split robot.
Optionally, the alarm module 203 is specifically configured to execute any one of the following:
when the target alarm type is an emergency alarm type, stopping the operation of the split robot, and immediately sending the equipment information of the split robot to a corresponding maintenance platform so as to perform fault maintenance on the split robot;
when the target alarm type is an important alarm type, sending the equipment information of the split robot to a corresponding maintenance platform to wait for fault maintenance of the split robot;
and when the target alarm type is a warning type, sending the equipment information of the split robot to a corresponding maintenance platform to remind the split robot of a fault.
Optionally, the device information further comprises at least one of: and the part index data, the equipment operation data and the motion trail data of the split robot.
Optionally, the processing module 205 is further configured to:
receiving an error fault code related to the target alarm type, wherein the error fault code is used for indicating that the split robot executes the re-operation of the target instruction again;
and executing the re-operation indicated by the target instruction again according to the indication of the error fault code.
By implementing the embodiment of the application, the split robot is judged whether a fault occurs or not according to the equipment information and the alarm condition in the alarm example by acquiring the equipment information and the alarm condition of the split robot; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot. In the above scheme, this application can carry out fault judgment to the components of a whole that can function independently robot based on the equipment information of components of a whole that can function independently robot and the condition of reporting an emergency and asking for help or increased vigilance that preset, with it is right when components of a whole that can function independently robot breaks down the components of a whole that can function independently robot carries out the processing of reporting an emergency and asking for help or increased vigilance of corresponding target type, and the engineer's of being convenient for is hierarchical/categorised maintenance robot, has shortened the fault handling time of robot, has promoted robot fault handling's convenience and practicality.
Please refer to fig. 3, which is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device 30 shown in fig. 3 includes: at least one processor 301, a communication interface 302, a user interface 303, and a memory 304, wherein the processor 301, the communication interface 302, the user interface 303, and the memory 304 may be connected by a bus or by other means, and the embodiment of the present invention is exemplified by being connected by the bus 305. Wherein the content of the first and second substances,
The communication interface 302 may be a wired interface (e.g., an ethernet interface) or a wireless interface (e.g., a cellular network interface or using a wireless local area network interface) for communicating with other terminals or websites. In this embodiment of the present invention, the communication interface 302 is specifically configured to obtain device information and the like.
The user interface 303 may specifically be a touch panel, including a touch screen and a touch screen, for detecting an operation instruction on the touch panel, and the user interface 303 may also be a physical button or a mouse. The user interface 303 may also be a display screen for outputting, displaying images or data.
The Memory 304 may include Volatile Memory (Volatile Memory), such as Random Access Memory (RAM); the Memory may also include a Non-Volatile Memory (Non-Volatile Memory), such as a Read-Only Memory (ROM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, HDD), or a Solid-State Drive (SSD); the memory 304 may also comprise a combination of the above-described types of memory. The memory 304 is used for storing a set of program codes, and the processor 301 is used for calling the program codes stored in the memory 304 and executing the following operations:
acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot;
acquiring an alarm condition in an alarm example;
judging whether the split robot has a fault or not according to the equipment information and the alarm condition;
and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot.
Optionally, before acquiring the alarm condition in the alarm example, the processor 301 is further configured to:
configuring different alarm templates for different alarm types;
generating an alarm example corresponding to the alarm type according to the alarm template;
the alarm types are in one-to-one correspondence with the alarm templates, and the alarm examples comprise alarm conditions with different alarm indexes.
Optionally, the determining, according to the device information and the alarm condition, whether the split robot has a fault includes:
judging whether the split robot has a fault or not by judging whether the equipment information meets the corresponding alarm condition or not;
when the equipment information meets the corresponding alarm condition, determining that the split robot has a fault;
and when the equipment information does not meet the corresponding alarm condition, determining that the split robot has no fault.
Optionally, the processor 301 is further configured to:
and when the split robot has no fault, the upper cabin of the robot which belongs to the same type as the split robot is dispatched to replace the split robot.
Optionally, the performing, by the split robot, an alarm process indicated by the target alarm type includes any one of:
when the target alarm type is an emergency alarm type, stopping the operation of the split robot, and immediately sending the equipment information of the split robot to a corresponding maintenance platform so as to perform fault maintenance on the split robot;
when the target alarm type is an important alarm type, sending the equipment information of the split robot to a corresponding maintenance platform to wait for fault maintenance of the split robot;
and when the target alarm type is a warning type, sending the equipment information of the split robot to a corresponding maintenance platform to remind the split robot of a fault.
Optionally, the device information further comprises at least one of: and the part index data, the equipment operation data and the motion trail data of the split robot.
Optionally, the processor 301 is further configured to:
receiving an error fault code related to the target alarm type, wherein the error fault code is used for indicating that the split robot executes the re-operation of the target instruction again;
and executing the re-operation indicated by the target instruction again according to the indication of the error fault code.
Since the terminal device described in this embodiment is a terminal device used for implementing the method for handling the fault of the split robot in this embodiment, based on the method for handling the fault of the split robot described in this embodiment, a person skilled in the art can understand the specific implementation manner of the terminal device in this embodiment and various variations thereof, so that a detailed description of how the terminal device implements the method in this embodiment is omitted here. The terminal device used by a person skilled in the art to implement the method for processing information in the embodiment of the present application is within the scope of the protection intended by the present application.
The technical scheme in the embodiment of the application at least has the following technical effects or advantages:
the method comprises the steps of obtaining equipment information of the split robot and alarm conditions in an alarm example, and then judging whether the split robot has a fault or not according to the equipment information and the alarm conditions; and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot. In the above scheme, this application can carry out fault judgment to the components of a whole that can function independently robot based on the equipment information of components of a whole that can function independently robot and the condition of reporting an emergency and asking for help or increased vigilance that preset, with it is right when components of a whole that can function independently robot breaks down the components of a whole that can function independently robot carries out the processing of reporting an emergency and asking for help or increased vigilance of corresponding target type, and the engineer's of being convenient for is hierarchical/categorised maintenance robot, has shortened the fault handling time of robot, has promoted robot fault handling's convenience and practicality.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A split robot fault handling method is characterized by comprising the following steps:
acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot;
acquiring an alarm condition in an alarm example;
judging whether the split robot has a fault or not according to the equipment information and the alarm condition;
and if so, determining a target alarm type corresponding to the equipment information, and performing alarm processing indicated by the target alarm type on the split robot.
2. The method of claim 1, wherein before obtaining the alarm condition in the alarm instance, the method further comprises:
configuring different alarm templates for different alarm types;
generating an alarm example corresponding to the alarm type according to the alarm template;
the alarm types are in one-to-one correspondence with the alarm templates, and the alarm examples comprise alarm conditions with different alarm indexes.
3. The method according to claim 1, wherein the determining whether the split robot has a fault according to the equipment information and the alarm condition comprises:
judging whether the split robot has a fault or not by judging whether the equipment information meets the corresponding alarm condition or not;
when the equipment information meets the corresponding alarm condition, determining that the split robot has a fault;
and when the equipment information does not meet the corresponding alarm condition, determining that the split robot has no fault.
4. The method of claim 3, further comprising:
and when the split robot has no fault, the upper cabin of the robot which belongs to the same type as the split robot is dispatched to replace the split robot.
5. The method according to claim 1, wherein the performing the alarm processing indicated by the target alarm type on the split robot comprises any one of:
when the target alarm type is an emergency alarm type, stopping the operation of the split robot, and immediately sending the equipment information of the split robot to a corresponding maintenance platform so as to perform fault maintenance on the split robot;
when the target alarm type is an important alarm type, sending the equipment information of the split robot to a corresponding maintenance platform to wait for fault maintenance of the split robot;
and when the target alarm type is a warning type, sending the equipment information of the split robot to a corresponding maintenance platform to remind the split robot of a fault.
6. The method of claim 1, wherein the device information further comprises at least one of: and the part index data, the equipment operation data and the motion trail data of the split robot.
7. The method of claim 1, further comprising:
receiving an error fault code related to the target alarm type, wherein the error fault code is used for indicating that the split robot executes the re-operation of the target instruction again;
and executing the re-operation indicated by the target instruction again according to the indication of the error fault code.
8. A split robot fault handling device, the device comprising:
the acquisition module is used for acquiring equipment information of the split robot, wherein the equipment information at least comprises heartbeat data of the split robot;
the obtaining module is further configured to obtain an alarm condition in an alarm example;
the judging module is used for judging whether the split robot has a fault or not according to the equipment information and the alarm condition;
and the alarm module is used for determining a target alarm type corresponding to the equipment information and carrying out alarm processing indicated by the target alarm type on the split robot if the judgment module judges that the split robot has a fault.
9. A terminal device, characterized in that the terminal device comprises: a processor, a memory, a communication interface, and a bus; the processor, the memory and the communication interface are connected through the bus and complete mutual communication; the memory stores executable program code; the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, for executing the split robot fault handling method of any one of claims 1 to 7.
10. A computer-readable storage medium characterized by storing a program that executes the split robot fault handling method according to any one of claims 1 to 7 when the program is run on a terminal device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111349156.7A CN114237196A (en) | 2021-11-15 | 2021-11-15 | Split robot fault processing method and device, terminal equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111349156.7A CN114237196A (en) | 2021-11-15 | 2021-11-15 | Split robot fault processing method and device, terminal equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114237196A true CN114237196A (en) | 2022-03-25 |
Family
ID=80749392
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111349156.7A Pending CN114237196A (en) | 2021-11-15 | 2021-11-15 | Split robot fault processing method and device, terminal equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114237196A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111091263A (en) * | 2019-10-24 | 2020-05-01 | 北京云迹科技有限公司 | Fault detection method, handheld device and mobile terminal |
| CN111694710A (en) * | 2020-06-10 | 2020-09-22 | 浪潮商用机器有限公司 | Method, device and equipment for monitoring faults of substrate management controller and storage medium |
| CN112395124A (en) * | 2020-11-17 | 2021-02-23 | 中国建设银行股份有限公司 | Robot abnormity control method and device in cluster environment |
| CN112477828A (en) * | 2020-11-24 | 2021-03-12 | 深圳裹动智驾科技有限公司 | Automatic driving vehicle, emergency braking method thereof and robot |
| CN113001590A (en) * | 2021-03-22 | 2021-06-22 | 深圳市普渡科技有限公司 | Robot fault recovery method, device, equipment and computer readable storage medium |
| WO2021128915A1 (en) * | 2019-12-25 | 2021-07-01 | 苏宁云计算有限公司 | Smart device monitoring method and apparatus |
| CN113568812A (en) * | 2021-07-29 | 2021-10-29 | 北京奇艺世纪科技有限公司 | State detection method and device for intelligent robot |
-
2021
- 2021-11-15 CN CN202111349156.7A patent/CN114237196A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111091263A (en) * | 2019-10-24 | 2020-05-01 | 北京云迹科技有限公司 | Fault detection method, handheld device and mobile terminal |
| WO2021128915A1 (en) * | 2019-12-25 | 2021-07-01 | 苏宁云计算有限公司 | Smart device monitoring method and apparatus |
| CN111694710A (en) * | 2020-06-10 | 2020-09-22 | 浪潮商用机器有限公司 | Method, device and equipment for monitoring faults of substrate management controller and storage medium |
| CN112395124A (en) * | 2020-11-17 | 2021-02-23 | 中国建设银行股份有限公司 | Robot abnormity control method and device in cluster environment |
| CN112477828A (en) * | 2020-11-24 | 2021-03-12 | 深圳裹动智驾科技有限公司 | Automatic driving vehicle, emergency braking method thereof and robot |
| CN113001590A (en) * | 2021-03-22 | 2021-06-22 | 深圳市普渡科技有限公司 | Robot fault recovery method, device, equipment and computer readable storage medium |
| CN113568812A (en) * | 2021-07-29 | 2021-10-29 | 北京奇艺世纪科技有限公司 | State detection method and device for intelligent robot |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107948744B (en) | Interface detection method, interface detection device, and computer-readable storage medium | |
| CN109359031B (en) | Multi-device application program testing method and device, server and storage medium | |
| CN111897671A (en) | Failure recovery method, computer device, and storage medium | |
| CN111143167B (en) | Alarm merging method, device, equipment and storage medium for multiple platforms | |
| CN108510086A (en) | Failure counte-rplan determine method and device | |
| CN110275992B (en) | Emergency processing method, device, server and computer readable storage medium | |
| CN112025703B (en) | Robot self-diagnosis method, device and system | |
| CN112702184A (en) | Fault early warning method and device and computer-readable storage medium | |
| CN111130867B (en) | Intelligent household equipment alarm method and device based on Internet of things | |
| CN109462699A (en) | The control method of the Doze mode of mobile terminal | |
| CN115437339A (en) | Remote diagnosis method and device, electronic equipment and storage medium | |
| CN111158806A (en) | Interface display method and device, computer equipment and storage medium | |
| CN114237196A (en) | Split robot fault processing method and device, terminal equipment and medium | |
| CN113076073A (en) | Pose display method and device for working machine and electronic equipment | |
| CN110391955B (en) | Network data preprocessing method, device, equipment and readable storage medium | |
| US9342805B2 (en) | Method and system for generating an integration model | |
| CN114244681A (en) | Equipment connection fault early warning method and device, storage medium and electronic equipment | |
| CN111077859B (en) | Production process control method, device and system | |
| CN113997708A (en) | Control method and device of printing control instrument | |
| CN114723191A (en) | Operation and maintenance method and device and electronic equipment | |
| CN112925658A (en) | Bridging method and device | |
| CN110009420A (en) | The ticket system and ticket drawing method of value-added service | |
| CN115333916B (en) | Network element alarm information processing method, device and storage medium in communication network | |
| CN104573504B (en) | A kind of method and apparatus for running application in iOS related systems | |
| CN114637564B (en) | Data visualization method and device, electronic equipment and storage medium |
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 |