Robot diagnosis apparatus and diagnosis method thereof

Abstract

To provide a robot diagnostic device and its diagnostic method for confirming a normal communication state and operability for each module before assembling the whole robot.SOLUTION: The robot diagnosis device includes a memory configured to store computer-executable instructions, a communication unit configured to support communication with a server, and at least one processor configured to access the memory and execute the computer-executable instructions, wherein the at least one processor is configured to, upon receiving a database stored in the server, identify a target task including monitoring of the robot and testing of the robot, identify an option group including a first option related to a type of the robot and a second option related to a connection between the robot and the processor, and perform diagnosis of the robot based on the target task and the option group.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a robot diagnostic device and a diagnostic method thereof, and more particularly to a robot diagnostic device and a diagnostic method thereof for diagnosing a robot based on various communication standards and database structures for each type of robot. [Background technology]

[0002] There is no diagnostic tool that can be applied to robots, like OBD (On-Board Diagnostics) for vehicles. In particular, a device or system that can diagnose robots is needed that reflects the various communication standards and database (DB) structures that vary by manufacturer or robot.

[0003] To solve these problems, it is necessary to develop a technology for diagnosing robots based on various communication standards and database structures according to the type of robot. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2022-128579 Summary of the Invention [Problem to be solved by the invention]

[0005] The present invention has been made in consideration of the above-mentioned conventional problems, and an object of the present invention is to provide a robot diagnostic device and diagnostic method for checking whether each module is in a normal communication state and operates properly before assembling the entire robot. [Means for solving the problem]

[0006] In order to achieve the above object, one aspect of the present invention provides a robot diagnostic device comprising: a memory storing computer-executable instructions; a communication unit supporting communication with a server; and at least one processor accessing the memory and executing the instructions, wherein the at least one processor, upon receiving a database stored in the server, identifies a target task including robot monitoring and robot testing, identifies an option group including a first option regarding the type of the robot and a second option regarding connection between the robot and the processor, and performs a diagnosis of the robot based on the target task and the option group.

[0007] The at least one processor may receive the database from the server via ethernet communication and identify the target task from the database. If the at least one processor identifies the target task, it may identify the option group paired with the target task. If the at least one processor cannot identify the target task, it may receive a format for generating the target task from a user, and if it generates the target task using the format, it may store the target task in the database and transmit the database to the server via the Ethernet communication. The at least one processor may provide the user with an interface implemented based on the command stored in the memory, and may receive the format via the interface. The at least one processor may receive the first option and the second option from the user via the interface, and may identify common information regarding communication, detailed information regarding data packages for each communication standard, and predetermined information regarding monitoring based on the second option. When a diagnosis of the robot is performed based on the target task and the option group, the at least one processor may transmit a diagnosis result of the robot via the interface. The at least one processor may provide port information for coupling with the robot based on the target task and the option group. When the target task is monitoring the robot, the at least one processor may perform diagnostics of data included in a communication standard relating to a connection between the robot and the processor according to the first option and the second option. When the target task is a test of the robot, the at least one processor may obtain a result regarding the movement operation of the robot according to the first option and the second option, and provide the obtained result to a user.

[0008] In order to achieve the above object, one aspect of the present invention provides a robot diagnosis method for a robot control device including at least one processor, which includes the steps of: when receiving a database stored in a server, identifying a target task including monitoring and testing the robot; identifying an option group including a first option regarding the type of the robot and a second option regarding a connection between the robot and a processor included in a device that diagnoses the robot; and performing a diagnosis of the robot based on the target task and the option group.

[0009] Identifying the target task may include receiving the database from the server via ethernet communication, and identifying the target task from the database. Identifying the target task may include, if the target task is identified, identifying the option group paired with the target task. The step of identifying the target task may include a step of receiving a format for generating the target task from a user if the target task cannot be identified; a step of storing the target task in the database if the target task is generated using the format; and a step of transmitting the database to the server via the Ethernet communication. The step of receiving the format may include providing an interface implemented based on a command stored in a device for diagnosing the robot to the user, and receiving the format through the interface. The step of receiving the format may include the steps of receiving the first option and the second option from the user via the interface, and identifying common information regarding communication, detailed information regarding data packages for each communication standard, and predetermined information regarding monitoring based on the second option. The step of performing a diagnosis of the robot may include transmitting a diagnosis result of the robot via the interface when a diagnosis of the robot is performed based on the target task and the option group. The step of performing a diagnosis of the robot may include providing port information regarding a connection with the robot based on the target task and the option group. The step of performing a diagnosis of the robot may include, when the target task is monitoring the robot, performing a diagnosis of data included in a communication standard relating to a connection between the robot and the processor according to the first option and the second option. The step of performing diagnosis of the robot may include, when the target task is a test of the robot, obtaining a result regarding the movement operation of the robot according to the first option and the second option, and providing the obtained result to a user. [Effects of the Invention]

[0010] The effects of the robot diagnostic device and method according to the present invention will be described below.

[0011] According to the present invention, by identifying a target task from a database stored in a server and performing a diagnosis of a robot based on the target task and an option group, it is possible to confirm whether each module is in a normal communication state and operational status before assembling the entire robot.

[0012] In addition, according to the present invention, by providing information to a user or requesting input through an interface implemented based on commands stored in a memory, the efficiency of a user's robot diagnostic operation during the robot development process can be increased.

[0013] In addition, various other effects are provided that can be directly or indirectly grasped through this specification. [Brief explanation of the drawings]

[0014] [Figure 1] 1 is a block diagram of a robot diagnostic device according to an embodiment of the present invention; [Figure 2] 1 is a flowchart illustrating a robot diagnosis method according to an embodiment of the present invention. [Figure 3]4 is a flowchart illustrating an operation of performing a robot diagnosis in a robot diagnosis device according to an embodiment of the present invention. [Figure 4] 10 is a flowchart illustrating a method for receiving a database from a server in a robot diagnostic device according to an embodiment of the present invention. [Figure 5] FIG. 1 is a diagram showing an example of a database including target tasks of the present invention. [Figure 6] FIG. 10 illustrates an example of an interface for database selection when a program containing code or instructions for performing robot diagnostic operations is executed. [Figure 7] FIG. 10 is a diagram illustrating an example of an interface related to database generation. [Figure 8] FIG. 10 is a diagram illustrating an example of an interface related to database generation. [Figure 9] FIG. 10 is a diagram illustrating an example of an interface related to database generation. [Figure 10] FIG. 10 is a diagram illustrating an example of an interface related to database generation. [Figure 11] FIG. 10 is a diagram illustrating an example of an interface related to database generation. [Figure 12] FIG. 10 is a diagram illustrating an example of a relationship between target tasks and option groups identified by a robot diagnostic device according to an embodiment of the present invention. [Figure 13] 10 is a diagram illustrating an example of providing port information related to a connection with a robot in a robot diagnosis device according to an embodiment of the present invention. FIG. [Figure 14] 10 is a diagram illustrating an example of an interface for requesting input of an option group. [Figure 15] FIG. 10 is a diagram showing an example of an interface that outputs a robot diagnosis result. [Figure 16] FIG. 1 is a diagram illustrating a computer system relating to a robot diagnostic device or a robot diagnostic method according to an embodiment of the present invention. [Figure 17]1 is a diagram showing a robot diagnostic system relating to a robot diagnostic device or a robot diagnostic method according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, specific examples of embodiments of the present invention will be described in detail with reference to the drawings.

[0016] When assigning reference numerals to components in each drawing, it should be noted that the same numerals are used for the same components whenever possible, even if they appear in different drawings. Furthermore, when describing embodiments of the present invention, if a detailed description of related known structures or functions is deemed to hinder understanding of the present invention, such detailed description will be omitted. In particular, while various embodiments of the present specification will be described with reference to the drawings, this is not intended to limit the technology described herein to specific embodiments, but should be understood to include various modifications, equivalents, and / or alternatives of the present invention. In describing the drawings, similar reference numerals are used for similar components.

[0017] When describing components of embodiments of the present invention, terms such as "first," "second," "A," "B," "(a)," and "(b)" may be used. These terms are intended only to distinguish the component from other components and do not limit the nature, order, or sequence of the components. Furthermore, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as meanings consistent with the meanings they have in the context of the relevant art, and should not be interpreted as idealized or overly formal unless expressly defined herein. For example, terms such as "first," "second," "primary," or "secondary" used herein may modify various components regardless of order and / or importance, and are used only to distinguish one component from another, not to limit the corresponding component. For example, a first user device and a second user device refer to different user devices regardless of order or importance. For example, a first component may be named a second component, and similarly, a second component may be named instead of a first component, without departing from the scope of the invention as described herein.

[0018] In this specification, the terms "have," "can have," "include," or "can include" indicate the presence of a relevant feature (e.g., a value, function, operation, or component such as a part) and do not exclude the presence of additional features.

[0019] When referring to a component (e.g., a first component) being "operatively or communicatively coupled with" or "connected to" another component (e.g., a second component), it should be understood that the component may be directly coupled to the other component or may be coupled through another component (e.g., a third component). On the other hand, when referring to a component (e.g., a first component) being "directly coupled with" or "directly connected to" another component (e.g., a second component), it should be understood that there is no other component (e.g., a third component) between the component and the other component.

[0020] As used herein, the expression "configured to" may be used in place of, for example, "suitable for," "having the capacity to," "designed to," "adapted to," "made to," or "capable of," depending on the context.

[0021] The term "configured to" does not necessarily mean "specifically designed to" hardware. Instead, in some contexts, the phrase "device configured to" means that the device is "capable of" performing, in conjunction with other devices or components. For example, the phrase "a processor configured to perform A, B, and C" may refer to a dedicated processor (e.g., an embedded processor) for performing the operations, or a general-purpose processor (e.g., a CPU or application processor) that performs the operations by executing one or more software programs stored in a memory device. Terms used herein are used solely to describe particular embodiments and are not intended to limit the scope of other embodiments. The singular includes the plural unless the context clearly dictates otherwise. Terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art described herein. Among the terms used in this specification, terms defined in a general dictionary shall be interpreted to have the same or similar meaning as the meaning they have in the context of the related art, and shall not be interpreted to have an ideal or excessively formal meaning unless expressly defined in this specification. In some cases, even terms defined in this specification cannot be interpreted to exclude the embodiments of this specification.

[0022] As used herein, expressions such as "A or B," "at least one of A and / or B," or "one or more of A and / or B" include all possible combinations of the items listed together. For example, "A or B," "at least one of A and B," or "at least one of A or B" refer to all cases where (1) at least one A is included, (2) at least one B is included, or (3) at least one A and at least one B are included. Furthermore, when describing components of embodiments of the present invention, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, or C," and "at least one of A, B, C, or any combination thereof" each include any one of the items listed together in the phrase, or all possible combinations thereof. In particular, a phrase such as "at least one of A, B, C, or any combination thereof" includes A or B or C or combinations thereof such as AB or ABC.

[0023] Hereinafter, an embodiment of the present invention will be described in detail with reference to FIGS.

[0024] FIG. 1 is a block diagram of a robot diagnostic device according to an embodiment of the present invention.

[0025] The robot diagnostic device 100 according to this embodiment includes a processor 110, a memory 120 including an instruction code 122, and a communication unit .

[0026] The robot diagnostic device 100 is a device for diagnosing a robot. For example, the robot diagnostic device 100 diagnoses a robot by providing a user with information contained in a database stored in a server 140. The robot diagnostic device 100 requests the user to input information contained in the database in order to diagnose the robot. The robot diagnostic device 100 performs a diagnosis of the robot based on the input information and provides the user with the results obtained. The robot diagnostic device 100 manages the database stored in the server 140 via Ethernet communication and directly connects to the robot 150 via a communication input / output terminal to perform monitoring diagnosis and operation tests.

[0027] The processor 110 executes software to control at least one other component (e.g., a hardware or software component) coupled to the processor 110. The processor 110 also performs various other data processing or calculation functions. For example, the processor 110 stores a database in the memory 120.

[0028] For reference, the processor 110 performs all operations performed by the robot diagnostic device 100. Therefore, for convenience of explanation, the operations performed by the robot diagnostic device 100 will be mainly described as operations performed by the processor 110 in this specification. Also, for convenience of explanation, the processor 110 will mainly be described as a single processor in this specification, but is not limited thereto. For example, the robot diagnostic device 100 includes at least one processor. Each of the at least one processor can perform all operations related to the robot diagnostic operation.

[0029] The memory 120 temporarily and / or permanently stores various data and / or information required to perform robot diagnostic operations, for example, the memory 120 stores a database.

[0030] The communication unit 130 supports communication between the robot diagnostic device 100 and the server 140. For example, the communication unit 130 includes one or more components that enable communication between the robot diagnostic device 100 and the server 140. For example, the communication unit 130 includes a short-range wireless communication unit, a microphone, etc. Here, short-range communication technologies include, but are not limited to, wireless LAN (Wi-Fi), Bluetooth (registered trademark), ZigBee (registered trademark), Wi-Fi Direct (WFD), ultra-wideband (UWB), infrared data association (IrDA), Bluetooth (registered trademark) Low Energy (BLE), and near field communication (NFC).

[0031] FIG. 2 is a flowchart illustrating a robot diagnostic method according to an embodiment of the present invention.

[0032] In this embodiment, in step 210, when a processor (e.g., processor 110 in FIG. 1) receives the database stored on a server (e.g., server 140 in FIG. 1), it identifies target tasks, including monitoring a robot (e.g., robot 150 in FIG. 1) and testing the robot.

[0033] The target task includes information for diagnosing or testing the robot, or instructions for performing the diagnosis or testing of the robot. Specifically, for the sake of convenience in this specification, robot diagnosis and robot monitoring are described as the same operation. Robot testing includes, but is not limited to, a test related to the robot's movement, a test related to the communication status between the robot and a server or device (e.g., device 100 in FIG. 1), or a test related to the robot's hardware or software. For example, robot testing includes a BMS (battery management system) test and a motor test, and robot diagnosis includes communication monitoring and fault diagnosis.

[0034] The processor identifies, via the target task, at least one of the name, type, rule, or any combination thereof of a diagnosis or test to be applied to the robot. That is, the processor performs, via the target task, a diagnosis of the robot, a robot operation test, a test on the robot's communication status, or a diagnosis on the robot's hardware. That is, the target task includes information on what operation the processor must perform on the robot.

[0035] For example, if the target task is robot monitoring, the processor diagnoses data included in a communication standard related to the connection between the robot and the processor according to the first and second options. Alternatively, if the target task is robot testing, the processor obtains results related to the movement operation of the robot according to the first and second options and provides the obtained results to the user. The provision of the results will be described later with reference to FIG. 15.

[0036] In step 230, the processor identifies an option group including a first option related to the type of robot and a second option related to the connection between the robot and the processor. For example, the first option indicates information related to the type of robot. The second option indicates information related to the connection between the robot and the processor and the communication standard. The processor identifies the option group to perform diagnostics and testing of the robot. The processor performs the target task described in step 220 (e.g., diagnostics and testing of the robot) based on the information included in the option group.

[0037] In step 250, the processor performs a diagnosis of the robot based on the target task and the option group. For example, the processor identifies the diagnosis and test to be performed on the robot through the target task. After identifying the diagnosis and test, the processor identifies the information included in the option group. The processor determines the type of the robot based on the first option and determines the coupling standard between the robot and the processor based on the second option. When the type of robot and the coupling standard are determined, the processor performs a diagnosis of the robot based on monitoring and testing the robot included in the target task.

[0038] FIG. 3 is a flowchart illustrating an operation of performing a robot diagnosis in a robot diagnosis device according to an embodiment of the present invention.

[0039] In step 305, a processor (e.g., processor 110 in FIG. 1) according to this embodiment identifies a database (DB) stored in a server (e.g., server 140 in FIG. 1) via Ethernet communication. For example, the processor provides the identified database to a user via a program interface including code or instructions for performing the operations of FIG. 2. Illustratively, the user checks the database information provided to the interface via an LCD (Liquid Crystal Display) monitor.

[0040] The processor checks whether or not there is a database required for diagnosis and testing in step 310. For example, when the processor receives the database, it checks whether or not there is a database required for diagnosis and testing of the robot by identifying target tasks including monitoring the robot and testing the robot.

[0041] If the processor does not identify a database required for diagnosis and testing in step 315, the processor creates a new database. If the processor creates a database, the processor stores the database on the server. A more detailed description of step 315 is provided below in FIG. 4.

[0042] The processor selects and / or identifies a robot type and a test type in step 320. For example, the processor provides a user with an interface implemented based on instructions stored in the memory. The user inputs a first option and a second option through the provided interface. The user can additionally input a robot type and a test type through the provided interface. Step 320 will be described in detail below with reference to FIG. 12. The information input by the user is applied to the operation of generating the database identified by the processor.

[0043] In step 325, the processor identifies the communication standard selection, hardware port selection, and connection with the robot required for diagnosis and testing. Specifically, when the processor identifies the target task, it identifies an option group (i.e., a first option and a second option) paired with the target task. For example, when the user inputs the second option, the processor identifies the communication standard selection. The user selects a hardware port for connection between the robot and the processor.

[0044] If the second option is selected by the user, the processor identifies common information related to communication, detailed information related to data packages for each communication standard, and predetermined information related to monitoring based on the second option. The information input or selected by the user is applied to the operation of generating the identified database by the processor. A detailed description of step 325 will be provided below with reference to FIG. 13.

[0045] The processor generates an interface based on the database generated from the information entered or selected by the user in step 330. For example, the processor outputs the interface generated based on the generated database via an LCD monitor.

[0046] The processor performs a diagnosis of the robot in step 335. For example, if the user clicks (or inputs) a diagnosis of the robot via the touch function of the LCD monitor, the processor performs a diagnosis of the robot. When the diagnosis of the robot is performed based on the target task and option group, the processor transmits the diagnosis result of the robot via the interface.

[0047] FIG. 4 is a flowchart illustrating a method for receiving a database from a server in a robot diagnostic device according to an embodiment of the present invention.

[0048] A processor according to this embodiment (e.g., processor 110 in FIG. 1 ) outputs a list of databases received from a server in step 405. For example, the processor receives at least one database from the server, each of which stores target tasks for a robot.

[0049] In step 410, the processor checks whether or not there is a database required for diagnosis and testing. For example, when the processor receives the database, the processor checks whether or not there is a database required for diagnosing and testing the robot by identifying a target task including monitoring the robot and testing the robot. Illustratively, if the target task is a first diagnosis (e.g., communication status diagnosis), the processor checks whether or not there is a database related to the first diagnosis among the at least one database.

[0050] If the processor identifies a database related to the first diagnosis (e.g., the content included in the target task) in step 415, the processor checks the target task included in the identified database. That is, the user selects a desired database from at least one database. The processor determines whether the target task is included in the database selected by the user. If the target task is included in the database selected by the user, the processor performs step 320 described in FIG. 3.

[0051] If the processor is unable to identify the target task in step 420, the processor receives a format for generating the target task from the user, where the format indicates a database format. The processor receives the format from the user via the interface.

[0052] The processor identifies the newly created database in step 425. For example, if the processor created the target task via formatting, it stores the target task in the database in step 430. The processor transmits the database to the server via Ethernet communication.

[0053] FIG. 5 is a diagram showing an example of a database including target tasks of the present invention.

[0054] 5 shows the structure of a database directory stored in a server (e.g., server 140 in FIG. 1). For example, the directory structure includes major categories, medium categories, and minor categories. The major categories are categories related to robot types, the medium categories are categories related to diagnosis or testing (i.e., target tasks), and the minor categories are categories related to databases for each communication standard used in the target tasks. Illustratively, the database includes, by major category, information about a first robot 510 and information about a second robot 520. The database includes, by medium category, a first target task 511, a second target task 513, and a third target task 515 of the first robot 510.

[0055] Due to the nature of robots, there are many different types of robots, and the communication standards for each robot make it impossible to perform various tasks with a single database. For example, even if the same communication method is used, the communication speed protocol may differ. Therefore, the database is categorized by the robot developed, and includes tasks such as testing and diagnosis for each robot.

[0056] Depending on the target task, various data communications may be required, or a single data communications method may be used. In this case, the processor uses DBC (Database CAN) in cases such as CAN (Controller Area Network) communications, where a standard database exists, since the database structure differs depending on the communication method. In contrast, if a standard database does not exist, the processor uses an XML-based DB. Since general-purpose monitoring programs can only check numerical data, the processor stores diagnostic data in the database. If the data cannot be stored in a standard database (e.g., DBC for CAN communications), the processor stores the required information for each target task using Add XML (Extensible Markup Language) (e.g., additional DB).

[0057] FIG. 6 is a diagram showing an example of an interface for database selection when a program containing code or instructions for performing the operation of robot diagnosis is executed.

[0058] Referring to Figure 6, Figure 6 shows an interface for database selection when a program including code or instructions for performing the operations of Figure 2 is executed. For example, a processor (e.g., processor 110 in Figure 1) provides a database list 630 received from a server (e.g., server 140 in Figure 1). A user checks database list 630 through the interface. If the required database is not found, the user clicks create new button 610. If the required database is found, the user clicks select button 620.

[0059] 7 to 11 are diagrams showing examples of interfaces related to database generation.

[0060] 7, a processor according to this embodiment (e.g., processor 110 in FIG. 1) provides an interface for creating a new database. When a robot type and a communication standard are selected via the interface, the processor provides a data label corresponding to the selected communication standard. For example, in the case of CAN communication, the CAN DBC database standard is used, and in the case of EtherCAT communication, the EtherCAT XML database standard is used. In contrast, RS485 / 422 / 232 communication does not have a predefined database standard, and for the sake of convenience, the present invention will be described using the XML standard.

[0061] To generate a database, the processor provides common information related to communications (e.g., general tab), detailed information related to data packages for each communication standard (e.g., data tab), and predetermined information related to monitoring (e.g., advanced tab) via an interface. When the user fills in the data values ​​according to each database standard and then presses the store button, the database is generated. The generated database is stored in the server via Ethernet communication.

[0062] 8, the processor provides an interface for adding messages for each communication standard. For example, a message for each communication standard may include a communication ID, a name, whether transmission / reception is possible, a data size, a format, etc. A user edits detailed data for each ID (e.g., CAN ID) via an edit signal.

[0063] 9, when the second option is CAN communication, the processor provides an interface for editing detailed data of the CAN communication. For example, in the case of CAN communication, a user adds signal data included in each ID and edits the details through edit detail.

[0064] 10, the processor provides an interface for editing data settings according to a communication standard. For example, in the case of the CAN communication standard, the user sets the data type, size, initial value range, etc., which are compatible with the communication standard.

[0065] Referring to Figure 11, the processor provides predetermined information related to monitoring through an interface. For example, the predetermined information related to monitoring is displayed in the advanced tab of the interface. The predetermined information is generated for each ID and detailed signal created in the data tab. When the user inputs the predetermined information, the processor matches the data of each signal from numbers to letters.

[0066] For example, if a user inputs "Robot type Hotel Delivery" in the first setting 1110, "LED position-Wheel" in the second setting 1120, and "Situation Alarm" in the third setting 1130, the processor will not provide an interface in the form of "(0, 2), (1, 3), (2, 2)", but will provide an interface in the form of "Robot type Hotel Delivery, LED position Wheel, Situation Alarm".

[0067] FIG. 12 is a diagram showing an example of the relationship between target tasks and option groups identified by the robot diagnostic device according to an embodiment of the present invention.

[0068] 12, the processor provides a selection of a robot type and a test type via an interface. The user selects a robot based on the database structure according to the required database in step 310 of FIG. 3, and selects a target task for the selected robot. The processor provides a first selection menu 1210 to receive the robot type from the user. The processor provides a second selection menu 1220 to receive the target task from the user.

[0069] FIG. 13 is a diagram illustrating an example of providing port information related to connection with a robot in a robot diagnostic device according to an embodiment of the present invention.

[0070] A processor according to this embodiment (e.g., processor 110 in FIG. 1) provides port information for connection with robot 150 based on a target task and an option group. For example, a user selects a communication standard 1310 required for diagnosis and testing. The user selects a hardware port 1320 suitable for diagnosing and testing robot 150 according to the selected communication standard.

[0071] 13, the robot 150 stores information about a hardware port 1320 for each communication type. For example, in the case of CAN communication, the hardware port 1320 is a D-SUB 9-pin connector and includes a JST 4-pin connector. In the case of EtherCAT communication, the hardware port 1320 is a LAN cable, and in the case of RS communication, the hardware port 1320 is mainly a D-SUB 9-pin connector. However, the hardware port 1320 is not limited thereto and may be other ports desired by each manufacturer or user.

[0072] FIG. 14 is a diagram showing an example of an interface for requesting input of an option group.

[0073] When a processor according to this embodiment (e.g., processor 110 in FIG. 1) cannot identify a target task, it receives a format for generating the target task from a user. When the processor generates the target task via the format, it stores the target task in a database. To receive the format, the processor provides the user with an interface shown in FIG. 14.

[0074] The processor provides, via the interface, a robot selection menu 1410 and a communication standard menu 1420 corresponding to the selected robot. For example, when a user selects "Robot1" via the robot selection menu 1410, the processor provides a target task related to "Robot1." When a user selects "TASK-1" from the target tasks related to "Robot 1," the processor determines "TASK-1" as the target task. The processor provides the communication standard menu 1420 related to the determined target task.

[0075] FIG. 15 is a diagram showing an example of an interface for outputting the robot diagnosis results.

[0076] When the target task is robot monitoring, the processor according to this embodiment (e.g., processor 110 in FIG. 1) diagnoses data included in a communication standard relating to the connection between the robot and the processor according to the first and second options. Alternatively, when the target task is robot testing, the processor obtains results relating to the movement operation of the robot according to the first and second options and provides the obtained results to a user.

[0077] 15, the processor provides the user with an interface for outputting the robot diagnosis results. The interface for outputting the results includes an Rx value, in which the period and data value are monitored according to the received value, a Tx value, in which the datA and period can be changed to a desired value and transmitted, and a data value, including the range and format specified when the database was created.

[0078] FIG. 16 is a diagram showing a computer system relating to a robot diagnostic device or a robot diagnostic method according to an embodiment of the present invention.

[0079] Referring to FIG. 16, a computer system 1600 relating to a robot diagnostic device or a robot diagnostic method includes at least one processor 1610, memory 1630, a user interface input device 1640, a user interface output device 1650, storage 1660, and a network interface 1670, all connected via a bus 1620.

[0080] The processor 1610 is a central processing unit (CPU) or a semiconductor device that executes processing based on instructions stored in the memory 1630 and / or storage 1660. The memory 1630 and storage 1660 may include various types of volatile or non-volatile storage media. For example, the memory 1630 may include a read only memory (ROM) and a random access memory (RAM).

[0081] Thus, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware executed by processor 1610, in a software module, or in a combination of the two. The software module may reside in a storage medium (i.e., memory 1630 and / or storage 1660) such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, or a CD-ROM.

[0082] An exemplary storage medium may be coupled to the processor 1610 such that the processor 1610 reads information from, and writes information to, the storage medium. Alternatively, the storage medium may be integral to the processor 1610. The processor and the storage medium may reside in an custom integrated circuit (ASIC). The ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0083] FIG. 17 is a diagram showing a robot diagnostic system relating to a robot diagnostic device or a robot diagnostic method according to an embodiment of the present invention.

[0084] 17, FIG. 17 illustrates a robot diagnostic system 1700 relating to a robot diagnostic device (e.g., robot diagnostic device 100 of FIG. 1) or a robot diagnostic method according to an embodiment. For example, the robot diagnostic system 1700 includes a monitoring LCD module 1710, a communication processor module 1720, a communication input / output terminal 1730, a monitoring test software module 1740, and a database (DB) 1750 for each communication standard. The robot diagnostic system 1700 communicates with a server 1760 via the communication processor module 1720. The robot diagnostic system 1700 is connected to a robot 1770 via the communication input / output terminal 1730. For reference, the robot diagnostic system 1700 can perform all the same operations as the robot diagnostic device. Therefore, the operations of the robot diagnostic device described with reference to FIGS. 1 to 17 can also be performed in the same way for the robot diagnostic system 1700.

[0085] The above description is merely an illustrative example of the technical concept of the present invention, and various modifications and variations are possible by those skilled in the art without departing from the essential characteristics of the present invention.

[0086] The above-described embodiments may be implemented using hardware components, software components, and / or a combination of hardware and software components. For example, the devices, methods, and components described herein may be implemented using a general-purpose computer or a special-purpose computer, such as a processor, controller, arithmetic logic unit (ALU), digital signal processor, microcomputer, field programmable gate array (FPGA), programmable logic unit (PLU), microprocessor, or other device capable of executing and responding to instructions. The processing device executes an operating system (OS) and software applications running on the OS. The processing device also responds to the execution of software to access, store, manipulate, process, and generate data. For ease of understanding, a single processing device may be described; however, those skilled in the art will recognize that a processing device may include multiple processing elements and / or multiple types of processing elements. For example, a processing device may include multiple processors or one processor and one controller. Other processing configurations are also possible, such as parallel processors.

[0087] Software includes computer programs, code, instructions, or a combination of one or more of these, which configure a processing device to operate as desired or, independently or collectively, instruct the processing device. The software and / or data may be permanently or temporarily embodied in some type of machine, component, physical device, virtual device, computer storage medium or device, or transmitted signal wave to be interpreted by the processing device or to provide instructions or data to the processing device. The software may be distributed across computer systems connected by a network and stored or executed in a distributed manner. The software and data may be stored on a computer-readable recording medium.

[0088] The method according to the present invention may be embodied in the form of program instructions executed by various computer means and recorded on a computer-readable recording medium. The computer-readable recording medium may include, alone or in combination, program instructions, data files, data structures, etc. The program instructions recorded on the recording medium may be specially designed and constructed for the present invention or may be well known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include not only machine language code, such as that produced by a compiler, but also high-level language code executed by a computer using an interpreter, etc.

[0089] The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, or vice versa.

[0090] Although the present embodiment has been described above with reference to limited drawings, those skilled in the art may apply various technical modifications and variations thereto. For example, suitable results may be achieved even if the described techniques are performed in a different order than described, and / or the components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted by other components or equivalents.

[0091] Accordingly, other implementations, other embodiments, and equivalents of the claims are within the scope of the claims.

[0092] Therefore, the embodiments disclosed in this specification are for illustrative purposes only and are not intended to limit the technical idea of ​​the present invention. The scope of protection of the present invention should be interpreted by the claims, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of the present invention. [Explanation of symbols]

[0093] 100 Robot diagnostic equipment 110, 1610 processors 120, 1630 memory 122 Imperative 130 Communications Department 140, 1760 servers 150, 1770 Robot 510, 520 1st and 2nd robots 511~515 1st~3rd target tasks 610 New generation button 620 Select button 630 Database List 11:10~11:30 1st~3rd settings 1210, 1220 1st and 2nd selection menu 1310 communication standard 1320 hardware port 1410 Robot Selection Menu 1420 Communication Standards Menu 1600 Computer Systems 1620 Bus 1640 User Interface Input Device 1650 User Interface Output Device 1660 Storage 1670 Network Interface 1700 Robot Diagnostic System 1710 Monitoring LCD Module 1720 Communications Processor Module 1730 Communication input / output terminal 1740 Monitoring Test Software Module 1750 Communication Standard Database (DB)

Claims

1. A memory that stores computer-executable instructions; a communication unit that supports communication with the server; at least one processor that accesses the memory and executes the instructions; The at least one processor Upon receiving the database stored on the server, identifying target tasks including monitoring a robot and testing the robot; identifying an option group including a first option relating to a type of the robot and a second option relating to a coupling between the robot and the processor; A robot diagnostic device for diagnosing the robot based on the target task and the option group.

2. The at least one processor receiving the database from the server via Ethernet communication; 2. The robot diagnostic device according to claim 1, wherein the target task is identified from the database.

3. The robot diagnostic device according to claim 2 , wherein the at least one processor, when identifying the target task, identifies the option group paired with the target task.

4. The at least one processor If the target task cannot be identified, receiving a format for generating the target task from a user; When the target task is generated via the format, the target task is stored in the database; 3. The robot diagnostic device according to claim 2, wherein the database is transmitted to the server via the Ethernet communication.

5. The at least one processor providing the user with an interface implemented based on the command stored in the memory; 5. The robot diagnostic device according to claim 4, wherein the format is received via the interface.

6. The at least one processor receiving the first option and the second option from the user via the interface; The robot diagnostic device of claim 5, wherein common information regarding communication, detailed information regarding data packages for each communication standard, and predetermined information regarding monitoring are identified based on the second option.

7. 7. The robot diagnostic device of claim 6, wherein the at least one processor transmits a diagnosis result of the robot through the interface when the diagnosis of the robot is performed based on the target task and the option group.

8. The robot diagnostic device according to claim 1 , wherein the at least one processor provides port information relating to a connection with the robot based on the target task and the option group.

9. 2. The robot diagnostic device of claim 1, wherein the at least one processor, when the target task is monitoring the robot, performs diagnosis of data included in a communication standard related to a connection between the robot and the processor according to the first option and the second option.

10. The at least one processor If the target task is a test of the robot, obtain a result regarding the movement behavior of the robot according to the first option and the second option; 2. The robot diagnostic device according to claim 1, wherein the acquired results are provided to a user.

11. 1. A robot diagnostic method for a robot controller including at least one processor, comprising: Upon receiving the database stored on the server, identifying target tasks including monitoring the robot and testing the robot; identifying a group of options including a first option relating to a type of the robot and a second option relating to a coupling between the robot and a processor included in a device for diagnosing the robot; and performing a diagnosis of the robot based on the target task and the option group.

12. The step of identifying a target task comprises: receiving the database from the server via Ethernet communication; and identifying the target task from the database.

13. The robot diagnosis method of claim 12 , wherein the step of identifying the target task includes the step of identifying the option group paired with the target task when the target task is identified.

14. The step of identifying a target task comprises: receiving a format for generating the target task from a user when the target task cannot be identified; If the target task is generated through the format, storing the target task in the database; The robot diagnostic method of claim 12, further comprising: transmitting the database to the server via the Ethernet communication.

15. The step of receiving the format includes: providing an interface implemented based on commands stored in the robot diagnostic device to the user; and receiving the format via the interface.

16. The step of receiving the format includes: receiving the first option and the second option from the user via the interface; and identifying common information related to communication, detailed information related to data packages for each communication standard, and predetermined information related to monitoring based on the second option.

17. 17. The robot diagnosis method of claim 16, wherein the step of performing the diagnosis of the robot includes transmitting a diagnosis result of the robot through the interface when the diagnosis of the robot is performed based on the target task and the option group.

18. 12. The robot diagnosis method of claim 11, wherein performing the diagnosis of the robot further comprises providing port information regarding a connection with the robot based on the target task and the option group.

19. 12. The robot diagnosis method of claim 11, wherein the step of performing the diagnosis of the robot includes, when the target task is monitoring the robot, performing a diagnosis of data included in a communication standard related to a connection between the robot and the processor according to the first option and the second option.

20. The step of performing diagnosis of the robot includes: If the target task is a test of the robot, obtaining a result regarding a movement operation of the robot according to the first option and the second option; and providing the obtained results to a user.

Images