Information processing apparatus

Abstract

The purpose of the present invention is to efficiently solve the cause of an abnormal situation when the abnormal situation occurs in a robot. An information processing device (1) according to one embodiment of the present disclosure is connected to an industrial machine (8) equipped with sensors (81, 83, 85) or to a control device (9) for controlling the industrial machine (8). An information processing device (1) is provided with: a storage unit (6) that stores first table data in which a plurality of abnormality causes are associated with a plurality of abnormality situations relating to the operation of an industrial machine (8); an abnormality monitoring unit (24) that monitors the occurrence of an abnormality in the industrial machine (8) on the basis of data output from the sensors (81, 83, 85); a cause specifying unit (25) that specifies the cause of the abnormality by referring to the first table data; and a display control unit (29) that displays, on a screen, the identified cause of the abnormal situation together with the content of the abnormal situation.

Description

Technical Field

[0001] The present invention relates to an information processing device having a function of monitoring industrial machinery. Background Art

[0002] Nowadays, robots have become indispensable equipment in factories and the like. Robots are equipped with various sensors such as visual sensors and force sensors. By using the output data of various sensors equipped by the robot, the timing of the robot's action can be determined, and the current position of the robot can be grasped. In addition, by using the output data of various sensors equipped by the robot, the occurrence of abnormal conditions of the robot can be monitored. The abnormal condition refers to a state in which the robot cannot perform the correct operation according to the action program, such as an unexpected excessive load on the robot in operation, robot vibration, and sudden stop of the robot. For example, an industrial robot with monitoring functions such as abnormality detection is known (for example, Patent Document 1). When an abnormality occurs in the robot, the operator needs to investigate the cause of the abnormality and discuss countermeasures to avoid the same abnormality from occurring again.

[0003] Until now, in order to identify the cause of an abnormality, the operator has switched various screens related to the robot's motion control provided by the robot, while checking the execution history of each job record and the output data of various sensors. In addition, the operator has formulated a countermeasure to solve the identified cause while referring to the manual, etc., and adjusted the setting information such as the robot's motion parameters, and actually operated the robot based on the adjusted setting information to confirm whether the same abnormality will not occur again.

[0004] Prior art literature Patent Literature Patent Document 1: Japanese Patent Application Publication No. 2015-229224 Summary of the invention Problem that the invention aims to solve However, when an abnormal situation occurs, the work efficiency of confirming the output data of the sensor and the execution history data while switching the various screens provided by the robot is low, which may become the main cause of delaying the determination of the cause of the abnormal situation or misdiagnosis. In addition, in order to formulate a countermeasure for solving the cause of the abnormal situation, it is necessary to investigate the instructions, academic materials, etc. after confirming the cause of the abnormal situation, so it takes a lot of time until the cause of the abnormal situation is solved. Therefore, it is desired to develop a technology that can efficiently solve the cause of the abnormal situation when an abnormal situation occurs in the robot.

[0005] Means used to solve problems An information processing device of one embodiment of the present disclosure is connected to an industrial machine equipped with a sensor or a control device for controlling the industrial machine. The information processing device comprises: a storage unit storing first table data associating a plurality of abnormal causes with a plurality of abnormal conditions related to the operation of the industrial machine; an abnormality monitoring unit monitoring the occurrence of abnormal conditions of the industrial machine based on data output from the sensor; a cause determination unit determining the cause of the abnormal condition with reference to the first table data; and a display control unit causing the determined cause of the abnormal condition to be displayed on a screen together with the content of the abnormal condition. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 This is a diagram showing a robot system including the information processing device according to the present embodiment.

[0007] Figure 2 It is shown Figure 1 A block diagram of an information processing device.

[0008] Figure 3 It is shown Figure 2 A diagram of an example of a cause identification table stored in a storage unit.

[0009] Figure 4 It is shown Figure 2 FIG. 1 is a diagram showing an example of a countermeasure determination table stored in a storage unit of .

[0010] Figure 5 It is shown Figure 2 A diagram showing an example of an execution history screen displayed on the display unit of .

[0011] Figure 6 It is shown in Figure 6 This figure shows an example of a cause confirmation screen that is displayed as a pop-up on the execution history screen of .

[0012] Figure 7 It is shown in Figure 6 This figure shows an example of the countermeasure confirmation screen that pops up on the execution history screen of .

[0013] Figure 8 It is shown that by Figure 6 FIG. 1 is a diagram showing an example of an enlarged screen that is popped up and displayed in response to a user operation on an execution history screen.

[0014] Fig. 9 It is shown in Figure 6 This is another example of the cause confirmation screen that pops up on the execution history screen.

[0015] Fig.10 It is shown Figure 1A flowchart of an example of the sequence of monitoring processing of an information processing device. DETAILED DESCRIPTION

[0016] Hereinafter, the information processing device of the present embodiment will be described with reference to the drawings. In the following description, the same reference numerals are attached to components having substantially the same function and structure, and repeated description will be given only when necessary.

[0017] The information processing device of the present embodiment is a computer device having the following functions, namely, a function of monitoring industrial machinery that operates according to an action program, a function of determining the abnormal cause of the abnormal situation and notifying the user when an abnormal situation related to the operation occurs in the industrial machinery, a function of determining a countermeasure for solving the abnormal cause of the abnormal situation occurring in the industrial machinery and notifying the user, and a function of providing the user with a screen that makes it easy to confirm the operation status of the industrial machinery. In the present embodiment, a robot device is described as an example of an industrial machinery. However, the industrial machinery may also be a machine tool, a welding device, etc., and is not limited to a robot device. Typically, the information processing device of the present embodiment is configured as follows.

[0018] like Figure 1 As shown, the information processing device 1 of this embodiment is connected to the robot device 7. The robot device 7 is composed of a robot arm mechanism 8 and a control device 9 that controls the robot arm mechanism 8. In this embodiment, the information processing device 1 is connected to the control device 9. The robot arm mechanism 8 has various sensors such as a force sensor 81 for detecting the load applied to the end effector, a visual camera 83 for photographing the workpiece W, etc., and an encoder 85 for detecting the rotation position of the motor. The types of sensors are not limited to these. The output data of the various sensors equipped on the robot arm mechanism 8 are input into the information processing device 1 of this embodiment through the control device 9.

[0019] like Figure 2 As shown, the information processing device 11 of this embodiment is configured by connecting hardware such as an operation unit 3, a display unit 4, a communication unit 5, and a storage unit 6 to a processor 2 (CPU, etc.). The information processing device 11 is provided by a personal computer, a tablet computer, a smartphone, etc.

[0020] The operation unit 3 has input devices such as a keyboard, a mouse, a jog, and a touch panel. The user can input various information into the information processing device 1 via the operation unit 3. Various information includes user operations on the execution history screen. User operations on the execution history screen include parameter selection operations, execution history selection operations, various button selection operations, etc. The display unit 4 has a display device such as an LCD (Liquid Crystal Display). The display unit 4 displays the execution history screen, pop-up screen, etc. according to the control of the display control unit 29. The communication unit 5 controls the transmission and reception of data between it and the robot device 7. Through the processing of the communication unit 5, the information processing device 1 receives action information when performing an action according to the action program 62 from the robot device 7. The action information includes information related to the action date and time, information related to the action time, sensor data obtained during the action, information to determine the action program used, event information indicating the action content, etc.

[0021] The storage unit 6 has a storage device such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive). The storage unit 6 stores in advance a monitoring program 61 for monitoring the robot device 7, an action program 62 for the robot device 7, data of a three-dimensional model 63, and data of a table 64. The data of the three-dimensional model 63 includes data of a three-dimensional model of the robot device 7 and data of a three-dimensional model of a workpiece. Typically, the data of the three-dimensional model 63 is provided by CAD data.

[0022] The data in Table 64 include data in a first table (hereinafter referred to as the "cause determination table") used when determining the abnormal cause of the abnormal situation, and data in a second table (hereinafter referred to as the "countermeasure determination table") used when determining the countermeasure for the abnormal cause. Of course, the cause determination table and the countermeasure determination table may be integrated into one table and provided.

[0023] like Figure 3As shown, the cause determination table is a table that associates multiple abnormal causes with abnormal situations related to the actions of the robot. For example, one abnormal cause is associated with one abnormal situation, just as the abnormal cause "B21" is associated with the abnormal situation "A2". There are also cases where multiple abnormal causes can be considered for one abnormal situation. Therefore, multiple abnormal causes can also be associated with one abnormal situation, just as the abnormal causes "B11", "B12", "B13", and "B14" are associated with the abnormal situation "A1". In the case where multiple abnormal causes can be considered for the abnormal situation, it is hoped that at least one abnormal cause can be determined from the multiple abnormal causes. Therefore, one cause determination condition can be associated with one abnormal cause, just as the four cause determination conditions "C11", "C12", "C13", and "C14" are associated with the four abnormal causes "B11", "B12", "B13", and "B14" respectively.

[0024] like Figure 4 As shown, the countermeasure determination table is a table that associates multiple countermeasures with multiple abnormal causes. For example, one countermeasure is associated with one abnormal cause, just as countermeasure "D11" is associated with abnormal cause "B11". Of course, there may be multiple countermeasures for one abnormal cause. Therefore, multiple countermeasures may be associated with one abnormal cause, just as countermeasures "D121" and "D122" are associated with abnormal cause "B12".

[0025] like Figure 2 As shown, the processor executes the monitoring program 61 stored in the storage unit 6, thereby enabling the information processing device 1 to function as a virtual space creation unit 21, a model configuration unit 22, a simulation execution unit 23, an abnormality monitoring unit 24, a cause determination unit 25, a countermeasure determination unit 26, an execution history creation unit 27, a display parameter setting unit 28 and a display control unit 29.

[0026] The virtual space creation unit 21 creates a virtual space on software that three-dimensionally represents the action space in which the robot device acts. The virtual space created by the virtual space creation unit 21 is displayed on the simulation display area of ​​the execution history screen created by the display control unit 29 .

[0027] The model configuration unit 22 configures a three-dimensional model of the robot device 7 (hereinafter referred to as a "robot model") and a three-dimensional model of a workpiece (hereinafter referred to as a "workpiece model") in the virtual space created by the virtual space creation unit 21 and displayed on the execution history screen. The robot model and the workpiece model are configured in the virtual space in a manner corresponding to the positional relationship between the robot and the workpiece in the actual action space.

[0028] The simulation execution unit 23 executes a simulation action for causing the robot model in the virtual space created by the virtual space creation unit 21 and displayed on the execution history screen to act in a simulated manner according to the action program 62 or according to the user's instruction via the operation unit 3. For example, the following display can be realized through the processing of the simulation execution unit 23. For example, the robot model displayed in the simulation display area of ​​the execution history screen can be animated (movie display) in synchronization with the action of the actual robot device 7. In addition, the robot model that reproduces the action of the robot device 7 when executing a task corresponding to the execution history selected by the user operation on the history screen can be animated. In addition, the output of the sensor when executing the task corresponding to the execution history selected by the user operation on the history screen can be reproduced and displayed.

[0029] The abnormality monitoring unit 24 monitors the occurrence of abnormal conditions in the robot device 7. Typically, the abnormality monitoring unit 24 determines that an abnormal condition has occurred in the robot device 7 based on output data of various sensors equipped in the robot device 7. In addition, the abnormality monitoring unit 24 can also be configured to monitor the occurrence of abnormal conditions in the robot device 7 based on setting information of sensors, setting information of the robot device 7, etc.

[0030] The cause determination unit 25 determines the abnormal cause of the abnormal situation that occurred by referring to the cause determination table. When there are multiple abnormal causes of the abnormal situation, the cause determination unit 25 determines at least one abnormal cause from the multiple abnormal causes based on the outputs of various sensors equipped by the robot device 7. For example, in the cause determination table, multiple abnormal causes "contact with obstacle", "motor abnormality" and "error in setting information" are associated with the abnormal situation "stop of robot device" of the robot device 7. For example, it is possible to determine whether the abnormal cause of the stop of the robot device 7 is "contact with obstacle" based on the output data of the force sensor and visual camera equipped by the robot device 7. Similarly, the cause determination unit 25 can determine whether the abnormal cause of the stop of the robot device 7 is "motor abnormality" based on the output data of the encoder that detects the rotation of the motor equipped by the robot device 7. When the abnormal cause of the stop of the robot device 7 is not any one of "contact with obstacle" and "motor abnormality", the cause determination unit 25 can determine that the abnormal cause is "error in setting information".

[0031] The countermeasure determination unit 26 refers to the countermeasure determination table to determine the countermeasure for solving the determined abnormal cause. For example, in the countermeasure determination table, the countermeasure "remove obstacles" is associated with the abnormal cause "contact with obstacles" of the robot device 7. In addition, the countermeasures "confirm the setting information of the motor" and "replace the motor" are associated with the abnormal cause "motor abnormality" of the robot device 7. When the abnormal cause determined by the cause determination unit 25 is "contact with obstacles", the countermeasure determination unit 26 refers to the countermeasure determination table to determine the countermeasure "remove obstacles". Similarly, when the abnormal cause determined by the cause determination unit 25 is "motor abnormality", the countermeasure determination unit 26 refers to the countermeasure determination table to determine the countermeasures "confirm the setting information of the motor" and "replace the motor".

[0032] The execution history creation unit 27 creates an execution history record including an action date and time, an action time, an event, a status, an action program, and the like. For example, an execution history record is created each time a specified task is executed. The action date and time, the action time, the event, and the like are determined based on the action information received from the robot device 7. The status includes "normal" and "abnormal". The status "normal" is added to the task that is not determined as an abnormal situation by the abnormality monitoring unit 24, and the status "abnormal" is added to the task that is determined as an abnormal situation by the abnormality monitoring unit 24. In this way, the execution history record in which an abnormal situation has occurred is distinguished from other execution history records. Of course, the execution history record in which an abnormal situation has occurred can also be automatically displayed in the detailed information display area 140, thereby being distinguished from other execution history records. In addition, the display mode of the execution history record in which an abnormal situation has occurred and other execution history records can also be changed by color, pattern, pattern, etc. In addition, the execution history record corresponding to the task in which an abnormal situation has occurred includes the abnormal cause determined by the cause determination unit 25 and the countermeasure solution determined by the countermeasure solution determination unit 26.

[0033] The display parameter setting unit 28 sets parameters displayed on the execution history screen according to the user's instruction via the operation unit 3. The parameters here include raw data of each sensor equipped in the robot device 7 and data obtained by performing predetermined processing on the raw data of each sensor.

[0034] The display control unit 29 creates an execution history screen related to the execution result of the robot device 7 executing the action program 62 in a predetermined format, and displays it on the display unit 4. Figure 5 , explaining the execution history screen created by the display control unit 29.

[0035] Figure 5 FIG. 2 shows an example of an execution history screen created by the display control unit 29. Figure 5 As shown, the execution history screen 100 includes a simulation display area 110 , an execution history display area 120 , a parameter display area 130 , a detailed information display area 140 , a PLAYBACK button 160 , and a REFRESH button 170 .

[0036] A virtual space in which a robot model and a workpiece model are arranged is displayed in the simulation display area 110. For example, the robot model displayed in the virtual space moves in synchronization with the actual movement of the robot device 7. In addition, if the playback button 160 is clicked in a state where an execution history record is selected by the user, the task corresponding to the execution history record is reproduced by simulation, and the robot model displayed in the simulation display area 110 performs the movement corresponding to the execution history record. At this time, the output of the sensor is also reproduced, and the sensor output reproduced by simulation is displayed in the parameter display area 130. For example, by selecting the execution history record in which an abnormality occurred and clicking the playback button 160, the user can confirm the movement of the robot device 7 and the output of the sensor when the abnormality occurred through simulation.

[0037] The execution history created by the execution history creating unit 27 is displayed in a list in the execution history display area 120. In the list of execution history displayed in a list, it is desirable to distinguish the execution history in which an abnormality has occurred from the other execution history. During the operation of the robot 7, the execution history screen 100 is updated regularly, and the execution history displayed in the execution history display area 120 is added one by one. The execution history screen 100 can also be updated when the user clicks the playback button 160.

[0038] The parameter display area 130 displays the parameters selected by the user in a graph format. The parameters include the time series data of the sensor and data obtained by performing a predetermined calculation process on the time series data of the sensor. The display format may be a graph format or a table format.

[0039] The detailed information of the execution history is displayed in the detailed information display area 140. The execution history corresponding to the task where the abnormal situation occurred can be automatically displayed in the detailed information display area 140, or the execution history selected by the user from the execution history list displayed in the execution history display area 120 can be displayed. If there is a task where an abnormal situation has occurred in the execution history displayed in the detailed information display area 140, a cause confirmation button 141 for confirming the details of the abnormal situation and the cause of the abnormality and a countermeasure confirmation button 143 for confirming a countermeasure for solving the cause of the abnormality are displayed.

[0040] like Figure 6As shown, when the user clicks the cause confirmation button 141 by operating the cursor 200, a cause confirmation screen 341 including text about the content of the abnormality and the cause of the abnormality is displayed as a pop-up on the execution history screen 100. In addition, the cause confirmation screen 341 may be displayed in an enlarged manner within the execution history screen 100. In addition, in the monitoring process described later, if an abnormality occurs in a predetermined task, the cause confirmation screen 341 is automatically displayed as a pop-up on the execution history screen 100. For example, Figure 6 As shown, the cause confirmation screen 341 displays the error code "0001" together with the abnormality content "Robot device 7 has stopped" and the abnormality cause "Abnormality of robot device 7" as an explanation of the error code. The user can understand the abnormality content in real time by viewing the cause confirmation screen 341.

[0041] like Figure 7 As shown in FIG. 1 , if the user clicks the countermeasure confirmation button 143 by operating the cursor 200, a countermeasure confirmation screen 343 including the text related to the countermeasure for solving the abnormality cause is popped up. In addition, the countermeasure confirmation screen 343 can also be enlarged and displayed in the execution history screen 100. For example, Figure 7 As shown, in the countermeasure confirmation screen 343, the countermeasures "Confirmation of motor setting information" and "Replacement of motor" corresponding to the error code "0001" corresponding to the abnormal content are displayed. These are displayed according to the pre-set priority. That is, the user only needs to confirm Figure 7 The countermeasure confirmation screen 343 shown here allows the user to implement countermeasures in the order of "confirmation of motor setting information" and "replacement of motor", and the user can also understand which countermeasure to start studying and implementing.

[0042] like Figure 8 As shown, when a graph displayed on the parameter display area 130 is selected by the user operating the cursor 200, an enlarged screen 330 of the selected graph is popped up on the execution history screen 100. In addition, the enlarged screen 330 can also be enlarged and displayed in the execution history screen 100. The user can examine the graph displayed on the parameter display area 130 in detail by confirming the enlarged screen 330.

[0043] like Fig. 9As shown in FIG. 1 , the type of parameter displayed in the parameter display area 130 can be changed according to the user's instruction. When the robot 7 is testing the operation program 62, there is a case where the user wants to understand the parameters that may be the main cause of abnormality. In such a case, by presetting the parameters displayed on the execution history screen 100, when an abnormality occurs, the parameters that are likely to be the cause of the abnormality can be understood in real time.

[0044] Below, refer to Fig.10 The monitoring process of the information processing device 1 according to the present embodiment will be described.

[0045] The monitoring process of the information processing device 1 is executed as a predetermined task based on the action program 62 of the robot device 7 is started. First, the information processing device 1 creates an execution history screen 100 (S11) and displays it on the display unit 4 (S12). The information processing device 1 receives action information generated by the robot device 7 as a predetermined task is completed from the robot device 7 (S13), and determines whether an abnormality has occurred based on the sensor data included in the action information (S14).

[0046] If an abnormality is detected in the task (S14; yes), the information processing device 1 determines the cause of the abnormality by referring to the cause determination table (S15). Next, the countermeasures for solving the cause of the abnormality are determined by referring to the table (S16). Then, based on the action information, the cause of the abnormality and the countermeasures received from the robot device 7, the information processing device 1 creates an execution history corresponding to the task (S17) and updates the execution history screen 100 (S18). Through the processing of step S18, the execution history created in step S17 is added to the execution history display area 120 of the execution history screen 100. In addition, in order to notify the user of the abnormality and the cause of the abnormality, the information processing device 1 pops up the cause confirmation screen 341 (S19). In addition, in the processing of step S19, the information processing device 1 can also pop up the countermeasure confirmation screen 343 and the cause confirmation screen 341 together.

[0047] In step S14, if it is not determined that an abnormal situation has occurred, that is, the task is completed normally (S14; No), the information processing device 1 creates an execution history corresponding to the task based on the action information received from the robot device 7 (S20), and updates the execution history screen 100 (S21). Through the processing of step S18, the execution history created in step S17 is added to the execution history display area 120 of the execution history screen 100.

[0048] Each time a predetermined task is executed by the robot device 7 , the processes from step S13 to step S21 are executed ( S22 ; No). When a series of tasks by the robot device 7 are completed, the monitoring process is terminated ( S22 ; Yes).

[0049] According to the information processing device 1 of this embodiment, the following effects are achieved.

[0050] The information processing device 1 of this embodiment maintains a cause determination table that associates the cause of the abnormality with the abnormal situation, and when an abnormal situation occurs in the monitored robot device 7, the cause confirmation screen 341 for notifying the user of the abnormal cause of the abnormal situation can be automatically displayed. The user can understand that an abnormal situation has occurred and can immediately confirm the abnormal cause of the abnormal situation by viewing the cause confirmation screen 341 displayed on the display unit 4. When an abnormal situation occurs, the time until the cause of the abnormal situation is confirmed can be shortened compared to the past, and the abnormal situation can be efficiently resolved.

[0051] The information processing device 1 displays a countermeasure confirmation screen 343 including a countermeasure for solving the cause of the abnormality by the user's operation on the execution history screen 100. The user can display the countermeasure confirmation screen 343 and confirm the countermeasure only by operating on the execution history screen 100. This helps to solve the abnormality efficiently.

[0052] In addition, if Figure 5 As shown, the information processing device 1 displays an execution history screen 100 that summarizes the simulation screen, the list of execution history records, the chart related to the parameters specified by the user, and the details of the execution history records. When an abnormality occurs when the robot device 7 executes a specific task, the details of the execution history records of the task are displayed in the detailed information display area 140, and a cause confirmation button 141 for confirming the cause of the abnormality and a countermeasure confirmation button 143 for confirming the countermeasure for the cause of the abnormality are displayed together with the content of the abnormality. The user can view the cause confirmation screen 341 (which is displayed as a pop-up on the execution history screen 100) by clicking the cause confirmation button 141. Figure 6 ), confirm the content and cause of the abnormal situation. Similarly, by clicking the countermeasure confirmation button 143, the user can view the countermeasure confirmation screen 343 ( Figure 7 ), confirm the countermeasures for the abnormal cause. In addition, the user can view the chart and the enlarged screen 330 of the simulation screen that are popped up on the execution history screen 100 by operating on the execution history screen 100 ( Figure 8 ), and study the cause of the anomaly in detail.

[0053] In this way, the user can confirm the execution history, the occurrence of abnormal situations, the cause of abnormal situations, the countermeasures, and conduct detailed research by simply browsing the execution history screen 100 and operating the execution history screen 100 as needed, so that the abnormal situation can be solved efficiently. In particular, the cause confirmation screen 341, the countermeasure confirmation screen 343, and the enlarged screen 330 are popped up on the execution history screen 100, so as long as the confirmation of each pop-up screen is completed, the screen can be closed to return to the execution history screen 100. Therefore, compared with the case of confirming the content while switching pages, it is more convenient to use and the abnormal situation can be solved efficiently.

[0054] As long as the output data of various sensors equipped by the robot arm mechanism 8 can be input to the information processing device 1 of this embodiment, the system structure is not limited to the above content. For example, it can be configured so that the information processing device 1 of this embodiment is connected to the robot arm mechanism 8, and the output data of various sensors are directly input to the information processing device 1 of this embodiment. In addition, the functions of the information processing device 1 of this embodiment can also be realized in the control device 9 that controls the robot arm mechanism 8.

[0055] One of the features of the information processing device 1 of this embodiment is that, when an abnormal situation occurs, the content of the abnormal situation and the cause of the abnormal situation can be notified to the user. As long as this feature can be realized in the information processing device 1, other processing does not necessarily need to be executed in the information processing device 1. For example, in this embodiment, the abnormal situation determination processing and the history record creation processing are executed in the information processing device 1. However, it is also possible to configure the robot device 7 to execute the abnormal situation determination processing and the history record creation processing, and the information processing device 1 receives the execution result.

[0056] Although the embodiments of the present disclosure have been described in detail, the present disclosure is not limited to the above-mentioned embodiments. These embodiments can be variously added, replaced, changed, partially deleted, etc. without departing from the scope of the invention, or without departing from the idea and the main purpose of the present invention derived from the contents recorded in the claims and their equivalents. For example, in the above-mentioned embodiments, the order of each action and the order of each process are shown as an example only and are not limited to this. In addition, the same is true when numerical values ​​or formulas are used in the description of the above-mentioned embodiments.

[0057] Description of Reference Numerals 100: Execution history screen, 110: Simulation display area, 120: Execution history display area, 130: Parameter display area, 140: Detailed information display area, 141: Cause confirmation button, 143: Countermeasure confirmation button, 160: Playback button, 170: Refresh button, 200: Cursor.

Claims

1. An information processing device connected to an industrial machine equipped with a sensor or a control device for controlling the industrial machine, wherein: have: a storage unit storing first table data associating a plurality of abnormality causes with abnormal conditions related to the operation of the industrial machine; an abnormality monitoring unit that monitors the occurrence of an abnormality of the industrial machine based on data output from the sensor; a cause determination unit, for determining a cause of the abnormal situation by referring to the first table data; as well as The display control unit causes the specified cause of the abnormal situation to be displayed on the display unit together with the content of the abnormal situation.

2. The information processing device according to claim 1, wherein: The display control unit causes the display unit to display the specified cause of the abnormal situation together with the content of the abnormal situation based on the occurrence of the abnormal situation.

3. The information processing device according to claim 1, wherein: The display control unit causes an execution history screen to be displayed on the display unit, and the execution history screen includes execution history information representing a history of actions performed by the industrial machinery. Through user operations on the execution history screen, the display control unit causes a screen notifying the cause of the abnormal situation together with the content of the abnormal situation to be popped up on the execution history screen.

4. The information processing device according to claim 3, wherein: The display control unit displays the execution history information in which an abnormality has occurred, distinguished from other execution history information.

5. The information processing device according to claim 3, wherein: The storage unit stores second table data in which a plurality of countermeasures for solving the abnormality cause are associated with a plurality of the abnormality causes. The information processing device further includes a countermeasure determination unit, the countermeasure determination unit referring to the second table data to determine a countermeasure for solving the abnormal situation. The display control unit displays a pop-up screen on the execution history screen for notifying a solution to the cause of the abnormality in response to a user operation on the execution history screen.

6. The information processing device according to claim 3, wherein: The display control unit displays the three-dimensional model of the industrial machine and time-series data based on the output of the sensor on the execution history screen.

7. The information processing device according to claim 6, wherein: The display control unit controls display of the three-dimensional model and the time-series data in order to reproduce the operation of the industrial machine and the output of the sensor corresponding to the execution history information selected by the user operation on the execution history screen.

8. The information processing device according to claim 3, wherein: The display control unit displays a parameter selected according to a user instruction on the execution history screen.

9. The information processing device according to claim 1, wherein: In the first table data, a plurality of the abnormal causes are associated with one abnormal condition. The cause identification unit identifies one abnormality cause of the abnormal situation from among the plurality of abnormality causes based on the output of the sensor.

Images