Monitoring device and robot monitoring system

Abstract

The purpose of the present invention is to propose a technology capable of monitoring changes in information related to production work with a robot by a worker. This monitoring device 10 according to the present embodiment comprises: a first receiving means 15 that receives an execution history that includes the starting date and time and the ending date and time of predetermined production work, from a robot control device 50 for controlling a robot in accordance with a production program for causing a robot to execute the production work; a second receiving means 15 that receives a change history that includes the date and time when the production program or a variable was changed by a person; and a determination means 123 that compares the change history with the execution history, thereby determining whether or not the timing when the production program or the variable was changed by a person was during the production work.

Description

Technical Field

[0001] Embodiments of the present invention relate to a monitoring device and a robot monitoring system having a function of monitoring changes in information related to the production work of a robot.

Background Art

[0002] Many robots are used in factory production lines. Monitoring the operating status of these robots is an important technology from the perspective of maintaining manufacturing efficiency and quality. For example, technologies for monitoring the operating status of a large number of robots located remotely are known (for example, Patent Document 1). However, the conventional technology monitors the occurrence of abnormalities such as robot failures by a preset monitoring algorithm and notifies the robot management responsible person, the system management responsible person, etc. of the occurrence of abnormalities.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the monitoring algorithm does not take into account the change work by the operator. Therefore, the monitoring program cannot detect changes in the robot program, changes in variables such as the operating speed, and changes in system variables by the operator, and the robot management responsible person and the system management responsible person cannot know these changes by the operator. However, changes made by the operator can be a factor that causes abnormalities in the robot's production work, whether they are made correctly or not. Therefore, the robot management responsible person and the system management responsible person should recognize changes made by the operator as a risk of abnormality occurrence. Against this background, a technology that can monitor changes in information related to the production work of a robot by an operator is desired. [Means for solving the problem]

[0005] The monitoring device according to this embodiment includes: a first receiving means that receives an execution history including the start date and time and end date and time of a production operation from a robot control device that controls a robot according to a production program that causes the robot to perform a predetermined production operation; a second receiving means that receives a change history including the date and time when the production program or variables were manually changed; and a determination means that determines whether the timing of the manual change of the production program or variables occurred during a production operation by querying the change history against the execution history. [Brief explanation of the drawing]

[0006] [Figure 1] Figure 1 shows a robot monitoring system including a monitoring device according to this embodiment. [Figure 2] Figure 2 is a functional block diagram of the robot control device shown in Figure 1. [Figure 3] Figure 3 shows an example of a production program stored in the robot control device shown in Figure 1. [Figure 4] Figure 4 shows an example of an execution history management table stored in the robot control device shown in Figure 1. [Figure 5] Figure 5 shows an example of a change history management table stored in the robot control device shown in Figure 1. [Figure 6] Figure 6 is a functional block diagram of the monitoring device according to this embodiment. [Figure 7] Figure 7 shows an example of a change history management table stored in the monitoring device shown in Figure 6. [Figure 8] Figure 8 shows an example of a notification screen provided to a user terminal from the monitoring device according to this embodiment. [Figure 9] Figure 9 is a flowchart showing an example of the monitoring process procedure by the monitoring device according to this embodiment. [Figure 10]Figure 10 shows another example of a production program stored in the robot control device shown in Figure 1. [Modes for carrying out the invention]

[0007] The monitoring device according to this embodiment will be described below with reference to the drawings. In the following description, components having substantially the same function and configuration will be denoted by the same reference numerals, and redundant explanations will be given only when necessary.

[0008] The monitoring device according to this embodiment is a computer device having a function to determine whether information related to the robot's production work, such as a production program for executing a predetermined production task on the robot and variables used in the production program, has been manually modified during the robot's production work, and a function to notify a pre-configured user terminal that information related to the robot's production work has been manually modified during the production work.

[0009] In this embodiment, "information related to the robot's production work" includes information directly related to the robot's operation, such as information related to the production program and setting information for variables used in the production program. Variables used in the production program include operating speed, waiting time, movement type, interpolation type, etc. Changes to the production program include changes, additions, and deletions of operation commands and changes, additions, and deletions of teaching positions. Operation commands include movement commands, gripping commands, welding commands, and waiting commands, etc. "Information related to the robot's production work" is not limited to information directly related to the robot's operation, but broadly includes various types of information that affect the robot's overall production work. Such information includes system variables inside the robot control device, such as variables related to data transmission and reception. In this embodiment, "variable" refers not only to numerical values ​​but also to strings and other things that can be treated as numerical values ​​or codes inside the robot control device.

[0010] In this embodiment, "robot production work in progress" means that the production program is being executed. The robot is also considered to be in production work when it is stationary in accordance with a standby command included in the production program. Furthermore, if the robot's production work is interrupted at an intermediate step and then resumed from that step, the period during which the robot's production work is interrupted is also considered to be in production work. On the other hand, when the robot is made to repeatedly perform production work, the interval between production tasks is typically not included in the robot's production work. Of course, the interval between production tasks may also be treated as being included in the production work.

[0011] In this embodiment, an identifier is written to the production program in order to obtain the start and end dates and times of production work performed by the robot. The identifier records the date and time at the time it is read, and may be the execution command itself, or it may be a marker for other programs to record the date and time. In this embodiment, the identifier is referred to as a command.

[0012] Figure 1 shows a robot monitoring system 1 including a monitoring device 10 according to this embodiment. The robot monitoring system 1 includes a robot 40, a robot control device 50 that controls the robot 40, and a monitoring device 10 connected to the robot control device 50 via the Internet 90. A user terminal 80 operated by a user who is responsible for managing the robot 40 is connected to the robot control device 50 and the monitoring device 10 via the Internet 90 or the like.

[0013] The user terminal 80 is a computer device having the function of displaying a notification screen provided by the monitoring device 10, the function of displaying a control screen for the robot 40 provided by the robot control device 50, and the function of transmitting various information entered according to user operations on the user terminal 80 to the robot control device 50. The user terminal 80 is provided by a smartphone, tablet, PC, etc. For example, the various information provided from the user terminal 80 to the robot control device 50 includes information related to the production work of the robot 40 and information on its changes, information on adding identifiers to the production program, information on deleting identifiers described in the production program, and information on modifying identifiers described in the production program.

[0014] Figure 2 is a block diagram showing the functions of the robot control device 50. As shown in Figure 2, the robot control device 50 is configured by connecting hardware such as an operation unit 53, a display unit 54, a communication unit (first and second receiving means) 55, and a storage unit 56 to a processor 52 such as a CPU. The robot control device 50 is provided by a general information processing terminal such as a PC or tablet.

[0015] The operation unit 53 has input devices such as a keyboard, mouse, and jog dial. The input devices may be provided by a touch panel shared with the display unit 54, or by a dedicated operation device (pendant) of the robot control device 50. The user can input information related to the production work of the robot 40 and information on its changes, information on adding identifiers to the production program, information on deleting identifiers described in the production program, and information on modifying identifiers described in the production program to the robot control device 50 via the operation unit 53.

[0016] The operation unit 53 has an interrupt button for interrupting the production operation of the robot 40. The interrupt button may be implemented by software. The robot control device 50 controls the robot 40 in accordance with the operation of the interrupt button by the user. Specifically, when the interrupt button is pressed, the robot control device 50 interrupts the production operation of the robot 40, and when the interrupt button is pressed again, the robot control device 50 resumes the interrupted production operation of the robot 40.

[0017] The display unit 54 has a display device such as an LCD and displays a control screen or the like. The communication unit 55 controls the transmission and reception of data with the monitoring device 10 and the user terminal 80. Through the processing of the communication unit 55, the robot control device 50 can receive various information from the user terminal 80. Also, the robot control device 50 can transmit the execution history data managed in the execution history management table and the change history data managed in the change history management table to the monitoring device 10.

[0018] The storage unit 56 has a storage device such as an HDD or an SSD. The storage unit 56 stores a monitoring program for the robot control device, a production program for causing the robot 40 to execute a production operation, variables used in the production program, and system variables related to the internal processing of the robot control device 50. Also, the storage unit 56 stores an execution history management table and a change history management table.

[0019] FIG. 3 shows an example of a production program. As shown in FIG. 3, the production program is provided in text format and describes operation commands line by line in accordance with the order of processes. The operation commands include a movement command to a taught position, a gripping command to grip a workpiece, a release command to release the workpiece, a welding command, and a standby command. For example, the command "Ich [1]" described in the second line of the production program indicates a movement command to the taught position "1". The command "Taiki" described in the eighth line indicates a standby command.

[0020] In this embodiment, the production program contains a record command for recording date and time information. Typically, the record command is written at a position that is read before the first operation command of the production program and at a position that is read after the last operation command has been read. Specifically, the second line of the production program is the first operation command. Therefore, the command "KAI-SHI-CHIJI" (start date and time), which records date and time information along with a code that identifies the start date and time, is written on the first line, which is read before the first operation command. Similarly, the tenth line of the production program is the last operation command. Therefore, the command "SHU-RYOU-CHIJI" (end date and time), which records date and time information along with a code that identifies the end date and time, is written on the eleventh line, which is read after the last operation command.

[0021] As shown in Figure 2, when the monitoring program for the robot control device stored in the memory unit 56 is executed by the processor 52, the robot control device 50 functions as a production program modification unit 521, a system variable modification unit 522, an execution history update unit 523, and a change history update unit 524.

[0022] The production program modification unit 521 modifies the production program and the variables used in the production program according to the change information regarding the production work of the robot 40 that is input via the operation unit 53 and the communication unit 55.

[0023] The system variable modification unit 522 modifies the system variables according to the system variable modification information input via the operation unit 53 and the communication unit 55.

[0024] The execution history update unit 523 reads the identifiers described in the production program, creates a record summarizing the product ID, date and time, code, robot name, and program name, and adds it to the execution history management table.

[0025] Figure 4 shows an example of an execution history management table. The execution history management table manages the production start date and time and production end date and time for robot 40. As shown in Figure 4, one record in the execution history management table manages the product ID to individually identify the product being produced, the code to individually identify the identifier written in the production program, the date and time, the robot name to individually identify the robot 40 used, and the program name to individually identify the program used.

[0026] For example, the product ID is production target information used to individually identify the production target, and in cases where production work is repeated, it corresponds to the number of repetitions. The code "1001" is a code that identifies the start date and time, and the code "2001" is a code that identifies the end date and time. Therefore, the date and time "2022 / 01 / 03 10:11:33" corresponding to product ID "001" and code "1001" indicates the production start date and time of the first product produced. The date and time "2022 / 01 / 03 10:13:21" corresponding to product ID "001" and code "2001" indicates the production end date and time of the first product produced. In other words, the period from the date and time "2022 / 01 / 03 10:11:33" to the date and time "2022 / 01 / 03 10:13:21" means that the robot was in the middle of production work.

[0027] The change history update unit 524, upon receiving change information related to production work performed by the robot 40 via the operation unit 53 or the communication unit 55, creates a record summarizing the change date and time, robot name, change code, and change details, and adds it to the change history management table. The change history management table manages the change date and time when information related to production work performed by the robot 40 is changed. Specifically, as shown in Figure 5, one record in the change history management table manages the change No., change date and time, robot name to individually identify the target robot 40, change code to individually identify the changed item, and specific change details.

[0028] Figure 6 is a block diagram showing the functions of the monitoring device 10. As shown in Figure 6, the robot control device 50 is configured by connecting hardware such as a communication unit 15 and a storage unit 16 to a processor 12 such as a CPU. The monitoring device 10 is typically provided by a server device.

[0029] The communication unit 15 controls the transmission and reception of data between the robot control device 50 and the user terminal 80. Through the processing of the communication unit 15, the monitoring device 10 can receive execution history data and change history data from the robot control device 50. The monitoring device 10 can also send a notification screen created by the notification screen creation unit 124 to the user terminal 80.

[0030] The storage unit 16 has a storage device such as an HDD or SSD. The storage unit 16 stores a monitoring program for the monitoring device. The storage unit 16 also stores an execution history management table (see Figure 4) and a change history management table (see Figure 7).

[0031] When the monitoring program for the monitoring device stored in the memory unit 16 is executed by the processor 12, the monitoring device 10 functions as an execution history update unit 121, a change history update unit 122, a determination unit (determination means) 123, and a notification screen creation unit 124.

[0032] The execution history update unit 121 adds the execution history data received from the robot control device 50 to the execution history management table. The execution history management table is the same as the one held by the robot control device 50 shown in Figure 4, so its explanation is omitted.

[0033] The change history update unit 122 adds the change history data received from the robot control device 50 to the change history management table, and also adds a production work in progress flag to the change history according to the determination result of the determination unit 123 described later. Figure 7 shows an example of a change history management table stored in the monitoring device 10. As shown in Figure 7, the change history management table managed by the monitoring device 10 is the same as the change history management table managed by the robot control device 50, with the item "production work in progress flag" added. The production work in progress flag indicates whether the corresponding change was made during production work. Here, a production work in progress flag of "0" indicates that the change was not made during production work, and a production work in progress flag of "1" indicates that the change was made during production work.

[0034] The determination unit 123 determines whether the timing of the change in information related to the robot 40's production work occurred during production work by querying the change history against the execution history. For example, the change date and time for change No. "1" in the change history management table shown in Figure 7 is "2022 / 01 / 03 / 09:05". When the execution history management table held in the monitoring device 10 is queried, the change date and time "2022 / 01 / 03 / 09:05" is a date and time before production started. Therefore, the determination unit determines that the change corresponding to change No. "1" was not made during production work. As a result, the production work flag "0", indicating that the change was not made during production work, is written to the record corresponding to change No. "1".

[0035] The change date and time for change No. "3" in the change history management table shown in Figure 7 is "2022 / 01 / 03 / 10:23". When the execution history management table held in the monitoring device 10 is queried, the change date and time "2022 / 01 / 03 / 10:23" is the date and time during the production work for product ID "002". Therefore, the determination unit determines that the change corresponding to change No. "3" was made during production work. As a result, the production work flag "1", indicating that the change was made during production work, is written to the record corresponding to change No. "1".

[0036] The notification screen creation unit 124 creates a notification screen to notify the user that information related to the production work of the robot 40 has been changed. Figure 8 shows an example of a notification screen displayed on the user terminal 80. As shown in Figure 8, the notification screen includes information indicating that information related to the production work of the robot 40 has been changed during production, the name of the robot that was changed, the product ID, the change code indicating the changed item, and the specific details of the change. By viewing the notification screen, the user can understand that information related to the production work of the robot 40 has been changed during production, as well as the products being produced at the time of the change, the changed item, and the specific details of the change.

[0037] Figure 8 is a flowchart showing an example of the monitoring process procedure by the monitoring device 10. As shown in Figure 8, the monitoring process by the monitoring device 10 is delayed until the reception of the execution history begins, in other words, until the robot control device 50 begins controlling the robot 40 (S11; NO). Once the reception of the execution history begins (S11; YES), the monitoring process by the monitoring device 10 begins. The monitoring device 10 receives the execution history (S12) and adds the received execution history to the execution history management table (S13). When the monitoring device 10 receives the change history (S14; YES), it queries the execution history management table for the change history and determines whether the change indicated by the change history is during production work by the robot 40. If it determines that the change is during production work by the robot 40 (S15; YES), the monitoring device 10 adds the received change history to the change history management table with the production work flag set to "1" (S16). Then, the monitoring device 10 creates a notification screen (S17) and sends the created notification screen to the user terminal 80 (S18). If it determines that the change is not in production work by the robot 40 (S15; NO), the monitoring device 10 adds the received change history to the change history management table with the production work flag set to "0" (S19).

[0038] The processes S12 through S19 are repeatedly executed until the reception of the execution history is completed, in other words, until the control of the robot 40 by the robot control device 50 is completed (S20; NO). Once the reception of the execution history is completed (S20; YES), the monitoring process by the monitoring device 10 is completed.

[0039] The monitoring device 10 according to this embodiment provides the following effects. The monitoring device 10 according to this embodiment can determine whether information related to the robot 40's production work has been changed during the robot 40's production work, based on the execution history and change history provided by the robot control device 50. This allows the user to understand changes in information related to the robot 40's production work during the robot 40's production work, which are particularly likely to lead to production defects. The monitoring device 10 can also send a notification screen to the user terminal informing them that changes have been made during production work. This notification screen includes text information indicating that changes were made during production work, as well as the robot name, product ID, changed item, and content. The risk of production defects varies depending on the changed item and content. For example, changes to the production program and variables directly related to the robot 40's production work carry a higher risk of production defects than changes to system variables. Furthermore, users may manage multiple robots 40. By being able to understand the changed items and content via the notification screen, users can address issues with a high risk of production defects first, and efficiently manage the overall production work of multiple robots 40. Furthermore, by keeping track of the products being produced and the robots performing the production tasks at the time of the change, it becomes possible to quickly determine which robot caused the problem and which product the problem originated from when a product malfunction occurs.

[0040] In this embodiment, in order to obtain the start and end dates and times of the robot 40's production work, as shown in Figure 3, a start command is written in the production program at a position that is read before the first operation command, and an end command is written at a position that is read after the last operation command. As a result, the production work of the robot 40 can be defined by the date and time output by the start command and the date and time output by the end command, and by referring to this, it is possible to determine whether the information related to the robot 40's production work was changed during the production work. However, it is also possible to obtain the start date and time or end date and time of at least one of the multiple processes that make up the production program. For example, in order to obtain the start date and time of each of the multiple processes that make up the production program, as shown in Figure 10, a command to obtain the date and time is written in the line between each line of operation commands written in the order of the processes. As a result, not only the start and end dates and times of the production work but also the start date and time (end date and time) of each process can be obtained, and it is possible to determine whether the information related to the robot 40's production work was changed during the production work and to identify in which process the change was made. By understanding which stage of the production process a change was made at, users can analyze and understand the risk of production defects in more detail.

[0041] The monitoring device 10 according to this embodiment has a function to create a notification screen to notify the user that information related to the robot 40's production work has been changed during production work, and to send it to the user terminal 80. However, regardless of whether production work is in progress or not, changes to information related to the robot 40's production work can pose a risk of production defects depending on the robot 40 and the content of the production work. Therefore, the monitoring device 10 may be configured to create a notification screen to notify the user that information related to the robot 40's production work has been changed, regardless of whether production work is in progress or not, and to send it to the user terminal 80.

[0042] In this embodiment, the monitoring program installed in the robot control device 50 and the monitoring device 10 may be distributed by recording it on removable media, or by downloading it to a user's computer via a network.

[0043] While embodiments of this disclosure have been described in detail, this disclosure is not limited to the individual embodiments described above. These embodiments can be added, replaced, modified, partially deleted, etc., in any way that does not depart from the spirit of the invention or the idea and spirit of the invention derived from the claims and their equivalents. For example, the order of operations and processes in the embodiments described above are shown as examples only and are not limited thereto. The same applies when numerical values ​​or mathematical formulas are used in the description of the embodiments described above. [Explanation of Symbols]

[0044] 10...Monitoring device, 12...Processor, 121...Execution history update unit, 122...Change history update unit, 123...Determination unit, 124...Notification screen creation unit, 15...Communication unit, 16...Storage unit.

Claims

1. A first receiving means receives an execution history, including the start date and time and end date and time of the production work, from a robot control device that controls the robot according to a production program that causes the robot to perform a predetermined production work, A second receiving means that receives a change history from the robot control device, including the date and time when the production program or variables were manually modified. A determination means that determines whether the timing of the manual modification of the production program or variable occurred during the production work by querying the execution history for the change history, Means for notifying the user that the production program or variables have been manually changed during the production work of the robot, A monitoring device equipped with the following.

2. The execution history includes production target information for individually identifying production targets, The monitoring device according to claim 1, further comprising a means for identifying the production target when the change is made during the production work of the robot, based on the production target information.

3. The aforementioned production process consists of multiple steps, The first receiving means receives from the robot control device the start date and time and end date and time of the production work, along with the execution history including the start date and time and end date and time of the process, The monitoring device according to claim 1, wherein the determination means identifies one of the multiple processes constituting the production work in which the production program or variables have been manually modified, by querying the change history with the execution history.

4. A robot control device that controls the robot according to a production program that causes the robot to perform a predetermined production task, The robot control device is connected to a monitoring device, The monitoring device includes a first receiving means for receiving an execution history including the start date and time and the end date and time of the production work, A second receiving means for receiving a change history including the date and time when the production program or variables were manually modified, A determination means that determines whether the timing of the manual modification of the production program or variable occurred during the production work by querying the execution history for the change history, A robot monitoring system comprising means for notifying the user that the production program or variables have been manually changed during the robot's production work.

Images