Method for analyzing operation data of robot, and robot capable of implementing same

Abstract

The present disclosure relates to collection and analysis of operation data of a robot, such as driving data and battery data, for verifying the operability of the robot deployed and used at a site, and may provide a robot comprising a user interface board and a navigation board, wherein: the user interface board includes a robot platform, an operation data analyzer, and a communication agent; and the operation data analyzer receives operation data of the robot from the robot platform, receives an error signal from the robot platform when an error occurs in the robot, analyzes the operation data to identify a cause of the error, and transmits an analysis result including the identified cause of the error to a control server through the communication agent.

Description

Method for analyzing robot operation data and robot capable of implementing the same

[0001] The present disclosure relates to a method for analyzing operating data of a robot, such as driving data and battery data, and a robot capable of implementing the same.

[0002] Robots were developed for industrial use and have played a role in factory automation. Recently, the scope of robot application has expanded, with developments in logistics, medical, and aerospace robots, as well as domestic robots for everyday use. Some of these robots are capable of autonomous navigation.

[0003] Typically, robot development involves simultaneously implementing both the hardware that composes the robot and the software that controls it. Even after a fully developed robot is deployed in the field, its operational performance may still require ongoing verification.

[0004] The purpose of the present disclosure is to provide a method for collecting and analyzing operating data of a robot, such as driving data and battery data, to verify the operability of a robot deployed and used in a field, and a robot capable of implementing the method.

[0005] In order to achieve the above object, the present disclosure provides a robot including a user interface board and a navigation board, wherein the user interface board includes a robot platform, a motion data analyzer, and a communication agent, wherein the motion data analyzer receives motion data of the robot from the robot platform, receives an error signal from the robot platform when an error occurs in the robot, analyzes the motion data to identify the cause of the error, and transmits an analysis result including the identified cause of the error to a control server through the communication agent.

[0006] The robot further includes a motion data database, and the motion data analyzer can store the motion data and the error signal in the motion data database.

[0007] The above motion data includes driving data and battery data, and the driving data includes at least one of driving status information, driving speed information, location information, and driving success / failure information, and the battery information may include at least one of timestamp information, SOC (state of charge) information, SOH (state of health) information, voltage information, and charging information.

[0008] The above analysis results may include the above motion data.

[0009] The above motion data analyzer receives driving assistance data from the navigation board, the driving assistance data includes at least one of an image captured at the time of occurrence of the error and a local map at the time of occurrence of the error, and the analysis result may further include the driving assistance data.

[0010] The above motion data analyzer can, when the error occurs, transmit the error signal to the control server through the communication agent, receive a serial number corresponding to the error from the control server through the communication agent, and then start analyzing the motion data.

[0011] The above analysis results may include the above serial number.

[0012] When the user interface board is powered on, the motion data analyzer can initialize the data analysis function.

[0013] The above motion data analyzer can receive the robot's driving start signal and the driving end signal from the robot platform, and analyze the motion data after the driving end signal.

[0014] The above motion data analyzer can store the driving start signal and the driving end signal in the motion data database.

[0015] In addition, to achieve the above object, the present disclosure may provide a method for analyzing operation data of a robot, including a user interface board and a navigation board, wherein the user interface board includes a robot platform, a motion data analyzer, and a communication agent, the method including a step of the motion data analyzer receiving motion data of the robot from the robot platform, a step of the motion data analyzer receiving an error signal from the robot platform when an error occurs in the robot, a step of the motion data analyzer analyzing the motion data to identify a cause of the error, and a step of the motion data analyzer transmitting an analysis result including the identified cause of the error to a control server through the communication agent.

[0016] The effects of a robot operation data analysis method according to the present disclosure and a system capable of implementing the same are described as follows.

[0017] According to at least one of the embodiments of the present disclosure, there is an advantage in that the operational data of a robot deployed in a field can be analyzed and utilized for software updates to improve robot performance by preventing operational errors, thereby further enhancing the operability of the robot in the field.

[0018] FIG. 1 is a block diagram showing components constituting a robot according to one embodiment of the present disclosure.

[0019] Figure 2 is a flowchart for performing robot movement according to one embodiment of the present disclosure.

[0020] FIG. 3 illustrates a robot operation data analysis system according to one embodiment of the present disclosure.

[0021] FIG. 4 illustrates a robot and a control server according to one embodiment of the present disclosure.

[0022] FIG. 5 is a block diagram of a user interface board and a navigation board of a robot according to an embodiment of the present disclosure.

[0023] Figure 6 is a flowchart regarding the operation of the motion data analyzer of Figure 5.

[0024] Figure 7 is a flowchart of the signal processing flow in the robot and control server of Figure 5.

[0025] Figures 8 and 9 illustrate the control front-end user interface provided by the control server of Figure 5.

[0026] Figure 10 is a graph of the driving failure rate before and after application of the robot operation data collection and analysis of the present disclosure.

[0027] Hereinafter, embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Regardless of the drawing numbers, identical or similar components will be given the same reference numbers and redundant descriptions thereof will be omitted. The suffixes "module" and "part" used for components in the following description are assigned or used interchangeably only for the convenience of writing the specification, and do not in themselves have distinct meanings or roles. In addition, when describing the embodiments disclosed in this specification, if it is determined that a specific description of a related known technology may obscure the gist of the embodiments disclosed in this specification, a detailed description thereof will be omitted. In addition, the attached drawings are only intended to facilitate easy understanding of the embodiments disclosed in this specification, and the technical ideas disclosed in this specification are not limited by the attached drawings, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and technical scope of the present invention.

[0028] These components may each be implemented as separate individual hardware modules, or may be implemented as two or more hardware modules, or two or more components may be implemented as one hardware module, and in some cases, they may also be implemented as software.

[0029] Terms that include ordinal numbers, such as first, second, etc., may be used to describe various components, but the components are not limited by these terms. These terms are used solely to distinguish one component from another.

[0030] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0031] Singular expressions include plural expressions unless the context clearly indicates otherwise.

[0032] In this specification, terms such as “include” or “have” are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in the specification, but should be understood not to exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

[0033] Referring to FIG. 1, components constituting a robot according to an embodiment of the present disclosure will be described. FIG. 1 is a block diagram showing components constituting a robot according to an embodiment of the present disclosure.

[0034] A robot (1000) may include a sensing module (100) that senses a moving object or a fixed object placed externally, a map storage unit (200) that stores various types of maps, a moving unit (300) that controls the movement of the robot, a functional unit (400) that performs a predetermined function of the robot, a communication unit (500) that transmits and receives information about a map or a moving object, a fixed object, or an external changing situation with another robot or a server, and a control unit (900) that controls each of these components.

[0035] Although Figure 1 depicts the robot's configuration hierarchically, this represents the robot's components logically. The physical configuration may differ. Specifically, a single physical component may contain multiple logical components, or multiple physical components may implement a single logical component.

[0036] The sensing module (100) senses external objects such as obstacles and provides the sensed information to the control unit (900). In one embodiment, the sensing module (100) may include a Lidar sensing unit (110) that calculates the material and distance of external objects such as walls, glass, and metallic doors from the current position of the robot using the intensity of the signal and the time (speed) of reflection. In addition, the sensing module (100) may include a temperature sensing unit (120) that calculates temperature information of objects placed within a certain distance from the robot (1000). One embodiment of the temperature sensing unit (120) includes an infrared sensor that detects the temperature of objects placed within a certain distance from the robot (1000), particularly, the body temperature of people. When the temperature sensing unit (120) is configured with an infrared array sensor, the temperature of an object can be sensed without contact. When an infrared sensor or infrared array sensor constitutes the temperature sensing unit (120), it can provide key information for determining whether a moving object is a person.

[0037] In addition, the sensing module (100) may further include a depth sensing unit (130) and a vision sensing unit (140) that calculate depth information between the robot and an external object in addition to the sensing units described above.

[0038] The depth sensing unit (130) may include a depth camera. The depth sensing unit (130) can determine the distance between the robot and an external object, and in particular, when combined with the lidar sensing unit (110), the sensing accuracy of the distance between the external object and the robot can be increased.

[0039] The vision sensing unit (140) may include a camera. The vision sensing unit (140) may capture images of objects surrounding the robot. In particular, the robot may distinguish between images of fixed objects that do not change much, and images of moving objects, to identify whether an external object is a moving object.

[0040] In addition, a plurality of auxiliary sensing units (145), such as thermal sensing units and ultrasonic sensing units, may be arranged. These auxiliary sensing units provide auxiliary sensing information necessary for generating maps or sensing external objects. In addition, these auxiliary sensing units also sense external objects while the robot is moving and provide information.

[0041] The sensing data analysis unit (150) analyzes information sensed by multiple sensing units and transmits the information to the control unit (900). For example, when an object placed externally is detected by multiple sensing units, each sensing unit may provide information on the characteristics and distance of the object. The sensing data analysis unit (150) may combine these values ​​to produce a calculation and transmit the result to the control unit (900).

[0042] The map storage unit (200) stores information about objects placed in a space where the robot moves. The map storage unit (200) may include a fixed map (210) that stores information about fixed objects that do not change or are placed in a fixed manner among the objects placed in the entire space where the robot moves. One fixed map (210) may be included depending on the space. Since the fixed map (210) contains only objects with the lowest change in the space, when the robot moves in the space, it can sense more objects than the objects indicated in the map (210).

[0043] The fixed map (210) essentially stores location information of fixed objects, and may additionally include characteristics of the fixed objects, such as material information, color information, or other height information. This additional information allows the robot to more easily identify changes in the fixed objects.

[0044] Additionally, the robot can sense its surroundings while moving, generate a temporary map (220), and compare it with a previously stored fixed map (210) of the entire space. As a result of the comparison, the robot can determine its current location.

[0045] The moving unit (300) is a means for moving the robot (1000) like a wheel, and moves the robot (1000) according to the control of the control unit (900). At this time, the control unit (900) can check the current location of the robot (1000) in the area stored in the map storage unit (200) and provide a movement signal to the moving unit (300). The control unit (900) can create a path in real time or create a path during the movement process using various pieces of information stored in the map storage unit (200).

[0046] The moving unit (300) may include a driving distance calculation unit (310) and a driving distance correction unit (320). The driving distance calculation unit (310) may provide information on the distance traveled by the moving unit (300). In one embodiment, the unit may provide the cumulative distance traveled by the robot (1000) starting from a specific point. Alternatively, the unit may provide the cumulative distance traveled in a straight line after the robot (1000) rotates from a specific point. Alternatively, the unit may provide the cumulative distance traveled by the robot (1000) from a specific time.

[0047] Additionally, according to one embodiment of the present disclosure, the driving distance calculation unit (310) can provide information on the moving distance within a certain unit as well as the accumulated distance. The driving distance calculation unit (310) can calculate the distance in various ways depending on the characteristics of the moving unit (300). If the moving unit (300) is a wheel, the driving distance can be calculated by counting the number of rotations of the wheel.

[0048] The driving distance correction unit (320) corrects the distance information calculated by the driving distance calculation unit (310) when the distance calculated by the driving distance calculation unit (310) is different from the distance information calculated by the sensing module (100) of the actual robot (1000). In addition, when an error accumulates in the driving distance calculation unit (310), the control unit (900) or the moving unit (300) can be notified to change the driving distance calculation logic of the driving distance calculation unit (310).

[0049] The functional unit (400) refers to providing specialized functions of the robot. For example, in the case of a cleaning robot, the functional unit (400) includes components necessary for cleaning. In the case of a guide robot, the functional unit (400) includes components necessary for guidance. In the case of a security robot, the functional unit (400) includes components necessary for security. The functional unit (400) may include various components depending on the function provided by the robot, and the present invention is not limited thereto.

[0050] The control unit (900) of the robot (1000) can create or update a map in the map storage unit (200). In addition, the control unit (900) can identify information on an object provided by the sensing module (100) during the driving process, distinguish whether the object is a moving object or a fixed object, and control the driving of the robot (1000).

[0051] In summary, when the control unit (900) of the robot (1000) senses an object placed externally by the sensing module (100), the control unit (900) can identify a moving object among the sensed objects based on characteristic information of the sensed object, and set the current position of the robot based on information sensed by the sensing module as a fixed object, excluding the moving object.

[0052] Hereinafter, with reference to FIG. 2, a robot movement operation according to an embodiment of the present disclosure will be described. FIG. 2 is a flowchart for performing a robot movement operation according to an embodiment of the present disclosure.

[0053] A global path planning may be established for the above robot (1000) to move to a target location. Here, global path planning refers to planning a path that can quickly travel from a starting location to a target location while avoiding collisions with obstacles based on an obstacle map.

[0054] The above global path plan may be established by a control system (or control server) (5000 in FIG. 3) and received by the robot (1000). Alternatively, the above global path plan may be established by the robot (1000) based on information regarding a target location received from the control server and map information of a site (e.g., a logistics center, etc.) where the robot (1000) operates. The map information may include an obstacle map indicating obstacles (and / or movable spaces) within the site. The obstacle map may include information regarding not only static obstacles but also dynamic obstacles.

[0055] Next, the robot (1000) (i.e., the control unit (900)) can establish a local path planning [S22]. The local path planning is to locally regenerate a path using sensor information sensed in real time by the sensor module (100) to avoid obstacles or moving obstacles that are not listed in the obstacle map when the robot (1000) moves along the global path.

[0056] Next, the robot (1000) can move to the target location based on the global path plan and the local path plan through the moving part (300) [S23].

[0057] A system for collecting and analyzing the operation data of the robot (1000) operated in the field will be further described with reference to FIG. 3. FIG. 3 illustrates a robot operation data analysis system according to one embodiment of the present disclosure.

[0058] In Figure 3, three robots (1000-1, 1000-2, 1000-3) are shown operating on site, but of course, more or fewer robots (1000) can be operated.

[0059] Each robot (1000-1, 1000-2, 1000-3) can collect its own motion data and transmit (or upload) it to the data server (3000). The motion data refers to data related to the motion of the robot, and may include, for example, driving data and battery data. Of course, the motion data may also include other data (for example, obstacle detection data, etc.).

[0060] The above driving data may include, for example, at least one of driving status information, driving speed information, location information, and information on whether driving was successful (i.e., whether an error occurred).

[0061] The above driving status information is information about whether the robot (1000-1, 1000-2, 1000-3) is currently driving or resting or stopped, whether it has received a driving command, and whether it has completed executing the driving command. The driving speed information is information about the speed at which the robot (1000-1, 1000-2, 1000-3) is driving, and may correspond to wheel speed, for example. The position information is information about the current position of the robot (1000-1, 1000-2, 1000-3). The driving success information is information about whether the robot (1000-1, 1000-2, 1000-3) has successfully driven to the task target location within a predetermined time according to its task. The driving success information may be understood as information about whether an error occurred, and may mean information about an error that occurred when an error occurred.

[0062] The above battery data may include at least one of timestamp information, state of charge (SOC) information, state of health (SOH) information, voltage information, and charging information.

[0063] The above timestamp information is time information indicating the battery usage record of the robot (1000-1, 1000-2, 1000-3), and may include, for example, information such as charging start time, charging end time, discharge start time, and discharge end time. The SOC information is information about the current charging state or the amount of electricity charged of the battery of the robot (1000-1, 1000-2, 1000-3). The SOH information is information about the health state of the battery of the robot (1000-1, 1000-2, 1000-3), that is, information about how healthy the current state is compared to the initial state of the battery. The voltage information is information about the current voltage of the battery of the robot (1000-1, 1000-2, 1000-3), and the charging information is information about whether the battery of the robot (1000-1, 1000-2, 1000-3) is charged.

[0064] The above data server (3000) can collect and store motion data for each robot (1000-1, 1000-2, 1000-3).

[0065] The above analysis server (3000) can analyze whether the robot (1000-1, 1000-2, 1000-3) is operating normally based on the above operation data. That is, the analysis server (3000) can analyze whether the driving according to the task of the robot (1000-1, 1000-2, 1000-3) is operating normally, and can analyze whether the battery status according to the task of the robot (1000-1, 1000-2, 1000-3) is normal.

[0066] The above analysis server (3000) can transmit the analysis results for the robots (1000-1, 1000-2, 1000-3) to the control server (5000). The control server (5000) can provide the analysis results to a user (or robot operator) through a control front-end user interface.

[0067] The user can perform quality / performance improvement work on the robot (1000-1, 1000-2, 1000-3) based on the analysis results. The quality / performance improvement can be performed through a software update of the robot (1000-1, 1000-2, 1000-3).

[0068] However, when the motion data of the robot (1000-1, 1000-2, 1000-3) is collected through the data server (3000) and analyzed through the analysis server (3000), the motion data of the robot (1000-1, 1000-2, 1000-3) for a certain period of time (e.g., 1 day) may be accumulated and stored in the data server (3000), and the analysis server (3000) may analyze the accumulated motion data and transmit the analysis result to the control server (5000). In this case, when there is an abnormal motion of the robot (1000-1, 1000-2, 1000-3), it may be difficult to immediately identify the abnormal motion, and the abnormal motion may be identified after the certain period of time (e.g., 1 day) has elapsed.

[0069] Hereinafter, with reference to FIG. 4, it will be described that the collection and analysis of the motion data is performed within each robot (1000) itself, and the analysis results of the motion data are directly provided to the control server (5000). FIG. 4 illustrates a robot and a control server according to one embodiment of the present disclosure.

[0070] Each of the above robots (1000) may be equipped with a motion data analyzer (920). The motion data analyzer (920) may be implemented in hardware, software, or a hybrid form thereof.

[0071] The above motion data analyzer (920) can collect motion data of the robot (1000) in real time and, when a motion error occurs, analyze the motion error based on the collected data and transmit it to the control server (5000).

[0072] The configuration and operation of the above motion data analyzer (920) will be further described with reference to FIGS. 5 to 7. FIG. 5 is a block diagram of a user interface board and a navigation board of a robot according to an embodiment of the present disclosure, FIG. 6 is a flowchart regarding the operation of the motion data analyzer of FIG. 5, and FIG. 7 is a flowchart regarding the signal processing flow in the robot and control server of FIG. 5.

[0073] As shown in Fig. 5, the robot (1000) may be equipped with a user interface board (1000A) and a navigation board (1000B).

[0074] The above user interface board (UI board) (1000A) is primarily intended for communication between a user (or robot operator) and the robot (1000A), and may be responsible for outputting information to be provided to the user, providing a menu for receiving user commands, and receiving user commands input through manipulation of the menu. Software for this purpose may be mounted on the user interface board (1000A).

[0075] The above navigation board (navigation board) (1000B) is a board that is mainly responsible for the driving of the robot (1000), and can control the robot (1000) to move from a starting position to a target position while avoiding collisions with obstacles based on an obstacle map and sensor information sensed in real time by the sensor module (100). Software for this purpose may be installed in the navigation board (1000B).

[0076] The above navigation board (1000B) can collect the driving data. In addition, the driving data can be collected every time a specific speed is reached and / or at specific time intervals.

[0077] The above user interface board (1000A) may include a robot platform (910), a motion data analyzer (920), a motion data DB (210), and a communication agent (510).

[0078] The above robot platform (910) is a module for managing the overall situation of the robot (1000) and can perform at least some of the functions of the control unit (900) described above.

[0079] The above motion data analyzer (920) can collect motion data of the robot (1000) in real time and, when a motion error occurs, analyze the motion error based on the collected data and transmit it to the control server (5000).

[0080] The above motion data analyzer (920) can perform a data collection function, a data upload function, a data analysis function, a communication setup function with the robot platform (910), etc.

[0081] As described in FIG. 3, each robot can collect its own motion data and transmit it to the data server (3000). The data collection and data upload functions are intended for this purpose. That is, the motion data analyzer (920) according to FIG. 5 can perform the data collection and data upload functions of FIG. 3 as is, while additionally performing the data analysis function. The data analysis function will be discussed in more detail later.

[0082] The above motion data analyzer (920) may be implemented within the control unit (900) or may be implemented as a separate module.

[0083] The above motion data database (DB) (210) can store the motion data collected for the data analysis function. As described above, the motion data can include driving data and battery data.

[0084] The above communication agent (510) is a module for the user interface board (1000A) to communicate with the control server (front end) (5000). The above communication agent (510) may also be implemented by the communication unit (500).

[0085] Hereinafter, with reference to FIG. 6, the data analysis function of the motion data analyzer (920) will be examined in more detail.

[0086] When the user interface board (1000A) is powered on, the motion data analyzer (920) can initialize the data analysis function [S61, S62].

[0087] When the robot (1000) starts to drive, the motion data analyzer (920) can recognize the start of driving of the robot (1000) by receiving a driving start signal from the robot platform (910) [S63].

[0088] When an error occurs during the driving of the robot (1000), the motion data analyzer (920) can recognize the occurrence of an error in the robot (1000) by receiving an error code from the robot platform (910) [S64].

[0089] When the driving of the robot (1000) ends, the motion data analyzer (920) can recognize the end of driving of the robot (1000) by receiving a driving end signal from the robot platform (910) [S65].

[0090] After the above robot (1000) has finished driving, the motion data analyzer (920) can proceed with and complete the analysis of the error that occurred [S66, S67].

[0091] The signal processing flow in the robot (1000) and the control server of FIG. 5 related to motion data collection and analysis will be further described with reference to FIG. 7.

[0092] The above robot platform (910) transmits a driving start signal to the motion data analyzer (2000) when the robot (1000) starts driving according to its own mission, and the motion data analyzer (2000) can record the start of driving of the robot (1000) in the motion data DB (210) [S71-1, S71-2].

[0093] The above robot platform (910) transmits the motion data to the motion data analyzer (2000) while the robot (1000) is driving, and the motion data analyzer (2000) can record the motion data in the motion data DB (210) [S72-1, S72-2].

[0094] The robot platform (910) transmits an error signal including an error code to the motion data analyzer (2000) when an error occurs during the driving of the robot (1000), and the motion data analyzer (2000) can record the error signal in the motion data DB (210) [S73-1, S73-2]. In addition, the motion data analyzer (2000) can send the error signal to the communication agent (74) [S74].

[0095] The above robot platform (910) transmits a driving end signal to the motion data analyzer (2000) when the driving of the robot (1000) is finished, and the motion data analyzer (2000) can record the driving end of the robot (1000) in the motion data DB (210) [S75-1, S75-2].

[0096] The motion data analyzer (2000) that received the above error signal can request and receive driving assistance data from the navigation board (1000B) [S76, S77]. The driving assistance data can include at least one of an image captured at the time of the error occurrence and a local map at the time of the error occurrence.

[0097] Meanwhile, the communication agent (500) can transmit the error signal to the control server (5000) [S78].

[0098] Then, the communication agent (500) can receive the sequential number of the error from the control server (5000) [S78] and send an analysis request signal for the error together with the error code and sequential number to the motion data analyzer (2000).

[0099] Then, the motion data analyzer (2000) can analyze the motion data to identify the error in response to the analysis request signal [S81]. That is, the motion data analyzer (2000) can analyze the motion data to identify the cause of the error.

[0100] The above-described motion data analyzer (2000) can transmit the analysis results for the error to the control server (5000) via the communication agent (500) [S82, S83]. The analysis results may include the cause of the error. In addition, the analysis results may further include at least a portion of the motion data and the driving assistance data. In addition, the analysis results may further include the serial number.

[0101] Accordingly, the user (or robot operator) can monitor the analysis results in real time through the control front-end user interface of the control server (5000), and perform quality / performance improvement work of the robot (1000) based on the analysis results.

[0102] The above control server (5000) may store the analysis results in its own database [S84].

[0103] Meanwhile, if no error occurs during the driving of the robot (1000), steps S73-1, S73-2, S74, and S76 to S83 may not be performed.

[0104] Hereinafter, with reference to FIGS. 8 and 9, the analysis results provided to a user (or robot operator) through the control front-end user interface of the control server (5000) will be described. FIGS. 8 and 9 illustrate the control front-end user interface provided by the control server of FIG. 5.

[0105] The above front-end user interface (5010) can provide the user with information regarding at least one of the driving result failure, driving start time, driving end time, driving time, driving distance, expected distance, average speed, number of route changes, and driving destination through individual driving information items (5110).

[0106] The above front-end user interface (5010) can provide the user with information about the movement path and speed during movement on the path map through the movement path and speed items (5120).

[0107] The above front-end user interface (5010) can provide information on speed by section to the user through the speed by section graph item (5130).

[0108] The front-end user interface (5010) may provide the user with a driving video and a local map at a specific speed (e.g., a low speed due to an error occurrence) through an image and local map item (5140) when a low speed error occurs. The driving video and local map may correspond to an image captured at the time of the error occurrence in step S77 and a local map at the time of the error occurrence, respectively.

[0109] The above user (or robot operator) can utilize the information provided through the front-end user interface to update software to improve robot performance, thereby further enhancing the operability of the robot in the field.

[0110] Hereinafter, improvements according to the present disclosure will be examined with reference to FIG. 10. FIG. 10 is a graph showing the driving failure rate before and after application of the robot operation data collection and analysis method of the present disclosure.

[0111] As shown in Fig. 10, before the application of the robot operation data collection and analysis of the present disclosure, the driving failure rate was 0.23% on average, but after the application of the robot operation data collection and analysis of the present disclosure, the driving failure rate was confirmed to be 0.14%, an improvement of approximately 40%.

[0112] The present invention described above can be implemented as computer-readable code on a medium having a program recorded thereon. Computer-readable media include all types of recording devices that store data that can be read by a computer system. Examples of computer-readable media include hard disk drives (HDDs), solid-state disks (SSDs), silicon disk drives (SDDs), ROMs, RAMs, CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, etc., and also include media implemented in the form of carrier waves (e.g., transmission via the Internet). Therefore, the above detailed description should not be construed as limiting in all respects, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present invention are intended to be included in the scope of the present invention.

Claims

1. Includes a user interface board and a navigation board, The above user interface board includes a robot platform, a motion data analyzer, and a communication agent. The above motion data analyzer, Receive robot motion data from the above robot platform, When an error occurs in the above robot, an error signal is received from the above robot platform, To determine the cause of the error, the above operation data is analyzed. A robot that transmits analysis results including the cause of the error identified above to the control server through the communication agent.

2. In paragraph 1, Including more motion data databases, The above motion data analyzer A robot characterized by storing the above motion data and the above error signal in the motion data database.

3. In paragraph 1, The above motion data includes driving data and battery data, The above driving data includes at least one of driving status information, driving speed information, location information, and driving success / failure information. A robot characterized in that the battery information includes at least one of timestamp information, SOC (state of charge) information, SOH (state of health) information, voltage information, and charging information.

4. In paragraph 1, A robot characterized in that the above analysis results include the above motion data.

5. In paragraph 4, The above motion data analyzer receives driving assistance data from the navigation board, The above driving assistance data includes at least one of an image captured at the time of occurrence of the error and a local map at the time of occurrence of the error, A robot characterized in that the above analysis results further include the driving assistance data.

6. In paragraph 1, The above motion data analyzer, When the above error occurs, the error signal is transmitted to the control server through the communication agent, A robot characterized in that it receives a serial number corresponding to the error from the control server through the communication agent and then initiates analysis of the motion data.

7. In paragraph 6, A robot characterized in that the above analysis results include the above serial number.

8. In paragraph 1, A robot characterized in that when the user interface board is powered on, the motion data analyzer initializes the data analysis function.

9. In the second paragraph, the motion data analyzer Receive the driving start signal and the driving end signal of the above robot from the fraud robot platform, A robot characterized by analyzing the motion data after the above driving end signal.

10. In the 9th paragraph, the motion data analyzer A robot characterized in that the driving start signal and the driving end signal are stored in the motion data database.

11. A method for analyzing operation data of a robot, comprising a user interface board and a navigation board, wherein the user interface board comprises a robot platform, a motion data analyzer, and a communication agent. A step in which the above motion data analyzer receives motion data of the robot from the robot platform; A step in which the above motion data analyzer receives an error signal from the robot platform when an error occurs in the robot; A step of analyzing the motion data by the motion data analyzer to determine the cause of the error; and A method for analyzing operation data of a robot, comprising: a step in which the operation data analyzer transmits analysis results including the identified cause of error occurrence to the control server through the communication agent.

12. In paragraph 11, The above robot further includes a motion data database, A method for analyzing operation data of a robot, characterized in that it further includes a step of the operation data analyzer storing the operation data and the error signal in the operation data database.

13. In paragraph 11, The above motion data includes driving data and battery data, The above driving data includes at least one of driving status information, driving speed information, location information, and driving success / failure information. A method for analyzing operation data of a robot, characterized in that the battery information includes at least one of timestamp information, SOC (state of charge) information, SOH (state of health) information, voltage information, and charging information.

14. In paragraph 11, A method for analyzing operation data of a robot, characterized in that the analysis result includes the operation data.

15. In paragraph 14, The above motion data analyzer further includes a step of receiving driving assistance data from the navigation board; The above driving assistance data includes at least one of an image captured at the time of occurrence of the error and a local map at the time of occurrence of the error, A method for analyzing operating data of a robot, characterized in that the analysis result further includes the driving assistance data.

16. In paragraph 11, The above motion data analyzer comprises a step of transmitting the error signal to the control server through the communication agent when the error occurs; A method for analyzing operation data of a robot, characterized in that the operation data analyzer receives a serial number corresponding to the error from the control server through the communication agent and then executes an analysis step of the operation data.

17. In paragraph 16, A method for analyzing robot operation data, characterized in that the analysis result includes the serial number.

18. In paragraph 11, A method for analyzing operation data of a robot, further comprising: a step of initializing a data analysis function of the operation data analyzer when the user interface board is powered on; 19. In paragraph 12, The above motion data analyzer comprises a step of receiving a driving start signal and a driving end signal of the robot from a fraud robot platform; A method for analyzing operation data of a robot, characterized in that the operation data analyzer executes an analysis step of the operation data after the driving end signal.

20. In paragraph 19, A method for analyzing operation data of a robot, characterized in that the method further includes a step of the motion data analyzer storing the driving start signal and the driving end signal in the motion data database.

Images