Monitoring device

Abstract

This monitoring device is provided with: a monitoring unit that monitors the occurrence of abnormalities in each of a plurality of industrial machines; a calculation unit that calculates a priority order for the industrial machine in which the abnormality has occurred on the basis of the number of remaining days from the current date to the date on which the maintenance work needs to be performed; and a display unit that displays graphic symbols indicating a predetermined number of industrial machines in which the priority is higher from among the industrial machines in which the abnormality has occurred. The display is performed in a display mode different from the graphic symbols indicating the industrial machines other than the predetermined number of industrial machines with the upper priority and the graphic symbols indicating the industrial machines with no abnormality in the industrial machines in which the abnormality has occurred.

Description

Technical Field

[0001] This disclosure relates to a monitoring device that functions to monitor industrial machinery such as robots. Background Technology

[0002] A robot monitoring system is known to monitor operational statuses such as predictive maintenance (using algorithms to predict malfunctions of robots already installed in production plants, etc.), preventive maintenance (notifying users of replacement schedules for items such as batteries mounted on robots), and the occurrence of robot malfunctions. To notify system administrators or equipment managers that the robot's operational status has changed, the robot monitoring system displays information related to the monitored robot on a system-specific user interface. For example, Patent Document 1 discloses a method for configuring and displaying information related to the monitored robot on a map based on its location. According to this method, users can immediately determine the location of robots that have malfunctioned. However, especially when there are many monitored robots, displaying a large amount of information on the map makes it difficult to grasp the information related to the robots that have malfunctioned, and sometimes it is difficult to determine which robot should be prioritized for investigation or maintenance.

[0003] Existing technical documents Patent documents Patent Document 1: Japanese Patent Application Publication No. 2005-107671 Summary of the Invention The problem the invention aims to solve The aim is to propose a technique to suppress the reduction in operability of maintenance tasks performed by users.

[0004] means for solving problems The monitoring device disclosed herein includes: a monitoring unit for monitoring the occurrence of abnormalities in each of a plurality of industrial machines; a calculation unit for calculating the priority order of industrial machines that have experienced abnormalities based on the number of days remaining from the current date until the date when maintenance work needs to be carried out; and a display unit for displaying graphic symbols representing a predetermined number of industrial machines with a higher priority among those that have experienced abnormalities in a different display mode than graphic symbols representing industrial machines with a higher priority than the predetermined number of industrial machines with abnormalities and graphic symbols representing industrial machines that have not experienced abnormalities. Attached Figure Description

[0005] Figure 1 A diagram illustrating a robot monitoring system including the monitoring device of this embodiment.

[0006] Figure 2 for Figure 1 Hardware configuration diagram of the monitoring device.

[0007] Figure 3 for Figure 1 Functional block diagram of the monitoring device.

[0008] Figure 4 To show Figure 3 A diagram showing an example of an exception history management form stored in the storage department.

[0009] Figure 5 To show Figure 3 An example of a monitoring screen displayed on the display unit.

[0010] Figure 6 To show Figure 3 The image shows an example of a display settings screen displayed on the display unit.

[0011] Figure 7 To show Figure 3 An example of a screen displaying the maintenance days setting.

[0012] Figure 8 A flowchart illustrating an example of the sequence of monitoring processes performed by the monitoring device in this embodiment.

[0013] Figure 9 To show Figure 3 Other examples of monitoring screens displayed on the display unit.

[0014] Figure 10 To show in Figure 9 The image shows the status of the cursor pointing to the first robot icon on the monitoring screen.

[0015] Figure 11 To show in Figure 9 The image shows the status of the cursor pointing to the second robot icon on the monitoring screen. Detailed Implementation

[0016] Hereinafter, the monitoring device of this embodiment will be described with reference to the accompanying drawings. In the following description, the same reference numerals are used for constituent elements that have substantially the same function and configuration, and the description will be repeated only where necessary.

[0017] The monitoring device of this embodiment (hereinafter referred to as the monitoring device) is a computer device with the function of monitoring the occurrence of robot malfunctions and the function of prompting the user to indicate which robots have malfunctioned. A feature of the monitoring device is that it assigns a priority order to the maintenance of malfunctioning robots, distinguishing between robots with higher priority, robots with lower priority, and robots that were not originally malfunctioning, and then prompting the user accordingly. By browsing the screen displayed on the monitoring device, the user can see which robots have a higher maintenance priority and intuitively understand which robot should be maintained first. Therefore, even when the number of operators is limited, efficient robot maintenance can be achieved.

[0018] In this embodiment, the terms are defined as follows.

[0019] Robot: A robot is an example of industrial machinery that is monitored. Industrial machinery is not limited to robots; it can also include machine tools, welding equipment, servo guns, etc.

[0020] Robot Icon: A robot icon is a graphic symbol that roughly represents a robot. An identification number is attached to the robot icon to identify it. When the cursor is hovered over a robot icon, it is determined whether the robot corresponding to that icon meets certain conditions. If the conditions are met, an exception message is displayed via a text pop-up.

[0021] Anomaly: An anomaly indicates a state requiring maintenance of industrial machinery. For robots, maintenance-required states include those where, although currently operating normally, the robot or its manufactured parts may malfunction if left unattended. Such states correspond to predictions of impending failure of robot components or the arrival of replacement periods for robot components. Of course, maintenance-required states can also include those where robot components have malfunctioned, indicating the robot is no longer functioning properly.

[0022] Priority: Priority indicates the order in which maintenance work should be performed on robots that have experienced malfunctions. Higher priority means higher maintenance priority and maintenance work should be performed as soon as possible. Typically, priority is calculated based on the number of days remaining from the current date to the target deadline.

[0023] Maintenance work: Maintenance work includes all the work required from the occurrence of an anomaly to the completion of the actual maintenance work performed by the personnel, the scheduling of personnel, the adjustment of schedules, the ordering of parts, and the work requiring internal company approval. Alternatively, maintenance work can refer only to the actual maintenance work performed by the personnel.

[0024] Maintenance days: Maintenance days are the number of days required for maintenance work. Typically, maintenance days include the actual time spent on maintenance work performed by personnel and the time required for various tasks up to the start of maintenance work. Recommended values ​​for maintenance days are pre-registered by maintenance companies, etc., but can also be set by the user. The maintenance days recommended by maintenance companies, etc., are, for example, the actual number of days spent on maintenance work performed by personnel. In this embodiment, the pre-registered maintenance days are distinguished as the initial value for maintenance days and the set value for maintenance days set by the user. When no distinction is needed, only the maintenance days are recorded.

[0025] Absolute Deadline Date: An absolute deadline date is the absolute deadline by which maintenance work must be performed. An absolute deadline date is defined as the date on which it is predicted that the robot will experience certain problems, or may actually malfunction, if maintenance work is not performed before that date.

[0026] Target Deadline: The target deadline is the date on which maintenance work needs to be commenced. The target deadline is a date that takes into account the number of maintenance days; typically, it is set as a date that traces back the number of maintenance days from the absolute deadline. Therefore, if maintenance work can begin before the target deadline, problems arising from the absolute deadline during the maintenance work can be reliably avoided. The target deadline is clearly distinguished from the absolute deadline.

[0027] Maintenance grace period: The maintenance grace period is the number of days from the date the anomaly occurred to the absolute deadline.

[0028] Typically, surveillance devices are configured as follows.

[0029] like Figure 1 As shown, the robot monitoring system 1 includes multiple robots 3 as monitoring targets and a monitoring device 2 for monitoring the occurrence of abnormalities in the multiple robots 3. The multiple robots 3 are connected to the monitoring device 2 via a network 10 such as a local area network or the Internet. Furthermore, in this embodiment, the multiple robots 3 are connected to the monitoring device 2. However, the configuration of the robot monitoring system 1 is not limited to this. For example, it could be configured such that an information processing device for collecting data from the multiple robots 3 installed in a factory is installed in each factory, and multiple information processing devices corresponding to the multiple factories are connected to the monitoring device.

[0030] like Figure 2 As shown, the monitoring device 2 is configured such that hardware such as an input device 12, a display device 13, a communication device 14, and a storage device 15 are connected to a processor 11, such as a CPU (central processing unit), via a data control bus. The input device 12 is implemented using a keyboard, mouse, or jog. Users can input various information into the monitoring device 2 via the input device 12. The display device 13 is implemented using an organic EL (Organic Electroluminescence) display, an LCD (Liquid Crystal Display), or the like. The display device 13 displays various images under the control of the processor 11. The communication device 14 performs data transmission and reception between the monitoring device 2 and multiple robots 3 under the control of the processor 11. The storage device 15 is implemented using an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. The storage device 15 stores a monitoring program that monitors the occurrence of anomalies in the robots 3 and displays information related to the anomaly status of the robots 3.

[0031] like Figure 3 As shown, the processor 11 executes the monitoring program stored in the storage device 15, thereby enabling the monitoring device 2 to function as an input unit 21, a display unit 22, a data receiving unit 23, a storage unit 24, a monitoring unit 25, a screen generation unit 27, a display quantity setting unit 28, a display item setting unit 29, a maintenance days setting unit 30, and a judgment unit 31.

[0032] Input section 21 consists of Figure 2 The input device 12 shown is functional. The input unit 21 inputs user operations via the input device 12 to the monitoring device 2. For example, the input unit 21 inputs display screen switching instructions, display quantity setting instructions, display item setting instructions, text format setting instructions, maintenance days setting instructions, and selection instructions for specific robot icons displayed on the screen to the monitoring device 2.

[0033] Display unit 22 consists of Figure 2 The functions of the display device 13 shown are realized. The display unit 22 displays the monitoring screen, display setting screen, and maintenance day setting screen generated by the screen generation unit 27. Details of these screens will be described later.

[0034] Data receiving unit 23 consists of Figure 2The communication device 14 shown is functionally implemented. The data receiving unit 23 receives sensor data from the robot 3 as information needed to diagnose whether an anomaly has occurred, and receives the factory ID (Identity) of the factory and the robot ID of the robot 3.

[0035] Storage unit 24 consists of Figure 2 The storage device 15 shown implements the following functions. The storage unit 24 stores various information required for the processing of the monitoring program (monitoring processing). For example, the storage unit 24 stores an anomaly history management table summarizing information related to anomalies that have occurred with the robot 3. Additionally, the storage unit 24 stores multiple diagnostic programs corresponding to various diagnostic functions. Furthermore, the storage unit 24 stores the maintenance grace period days, initial values ​​for maintenance days, and set values ​​for maintenance days for each of the various diagnostic functions. Additionally, the storage unit 24 stores format data and material data of screens generated by the screen generation unit 27, such as monitoring screens, display setting screens, and maintenance day setting screens. For example, the material data includes data related to the robot icon, data related to the first marker, and data related to the second marker.

[0036] The monitoring unit 25 monitors for the occurrence of abnormalities in the robot 3. Specifically, the monitoring unit 25 has multiple diagnostic functions for diagnosing abnormalities in the robot 3. These multiple diagnostic functions are implemented by executing multiple diagnostic programs stored in the storage unit 24.

[0037] For example, the monitoring unit 25 diagnoses the deterioration status of the reducer based on sensor data received from the encoder equipped on the robot 3 using a function to diagnose reducer deterioration. Furthermore, when the deterioration status of the reducer exceeds a threshold, the monitoring unit 25 diagnoses that the robot 3 has malfunctioned.

[0038] For example, the monitoring unit 25, through its battery replacement notification function, diagnoses the arrival of the battery replacement period based on the number of days elapsed since the last replacement date or the operating time of robot 3 since the last replacement. Furthermore, based on the arrival of the battery replacement period, the monitoring unit 25 diagnoses that robot 3 has malfunctioned.

[0039] Multiple diagnostic functions include diagnosing motor torque, diagnosing arc welding status, diagnosing servo guns, notifying users to replace cables, and notifying users to replace grease. If the monitoring unit 25 diagnoses an anomaly in robot 3, the robot ID of robot 3, the anomaly content, the corresponding anomaly code, and the date and time of the anomaly are recorded in the anomaly history management table.

[0040] The calculation unit 26 calculates the priority order based on the number of days remaining from the current date to the target deadline. Specifically, the calculation unit 26 calculates the remaining days by subtracting the initial value of the maintenance days from the maintenance grace period and the number of days elapsed since the date the anomaly occurred, and then calculates the priority order in ascending order of remaining days. If the remaining days are the same, the priority order is determined by the length of the maintenance days. Specifically, if the remaining days are the same, the priority order is determined by the length of the maintenance days in descending order. Furthermore, if the maintenance days are set by the user, the calculation unit 26 replaces the initial value of the maintenance days with the set value to calculate the remaining days.

[0041] The screen generation unit 27 uses the format data and material data stored in the storage unit 24 to generate a monitoring screen for notifying the user of the occurrence of an anomaly in robot 3, a display setting screen for accepting user settings related to display, a maintenance day setting screen for accepting user settings of maintenance days, and a pop-up screen containing text containing detailed information related to the anomaly. The pop-up screen is generated when the judgment unit 31 has made a positive judgment. The pop-up screen contains detailed information related to the anomaly that has occurred in robot 3. Robot 3 is the robot corresponding to the robot icon that has been positively judged. The screen generated by the screen generation unit 27 is displayed on the display unit 22.

[0042] The display quantity setting unit 28 sets the display quantity based on user operations on the display setting screen. The display quantity corresponds to a predetermined quantity in the priority order, and is the number of robot icons displayed using a display method indicating high maintenance priority. The display item setting unit 29 sets the display items based on user operations on the display setting screen. The display items are detailed information related to anomalies, such as anomaly content, anomaly code, maintenance method, and remaining days. The maintenance days setting unit 30 sets the maintenance days setting value based on user operations on the maintenance days setting screen. The judgment unit 31 determines whether the robot 3 represented by the robot icon meets the predetermined conditions when the cursor is aligned with the robot icon displayed on the monitoring screen. Specifically, the judgment unit 31 determines that the predetermined conditions are met when the robot 3 corresponding to the robot icon is in a priority order that is separately set for anomaly content, anomaly code, maintenance method, and remaining days. Figure 6 When displaying objects with abnormal content, abnormal code, maintenance method, and remaining days, robots 3 in the top 10 priority positions are judged to meet the specified conditions, while robots 3 in the 11th priority position or below are judged to not meet the specified conditions.

[0043] Figure 4An example of an anomaly history management table is shown. This table manages information related to robot 3, where anomalies have occurred. For example, the table associates the factory ID, robot ID, anomaly content, anomaly code, anomaly occurrence date and time, maintenance status, and a unique history ID that identifies the anomaly occurrence. The anomaly content indicates the diagnostic function that diagnosed the anomaly in robot 3. The anomaly code is the code that identifies the anomaly content. The maintenance status indicates whether maintenance has been performed; "Maintained" indicates maintenance has been performed, and "Not Maintained" indicates maintenance has not been performed. When the monitored unit 25 diagnoses an anomaly in robot 3, the factory ID, robot ID, anomaly content, anomaly code, anomaly occurrence date and time, and maintenance status are recorded in the anomaly history management table. Initially, the maintenance status is recorded as "Not Maintained." Upon receiving input indicating that maintenance has been performed, the maintenance status is updated from "Not Maintained" to "Maintained."

[0044] The following is for reference Figure 5 This describes the monitoring screen displayed by the display unit 22. Figure 5 Here is an example of a surveillance video. Figure 5 The monitoring screen 110 shown is displayed when "Factory 1" is clicked on in the navigation tree 200 that is continuously set in each screen of the monitoring website. Monitoring screen 110 is used to alert the user to the occurrence of abnormalities in the robot 3 configured in the factory corresponding to "Factory 1". For example, as... Figure 5 As shown, the monitoring screen 110 displays multiple robot icons 115, each corresponding to one of the multiple robots 3. These robot icons 115 are positioned in multiple locations corresponding to the actual layout information. Figure 5 In the monitoring screen 110 shown, the multiple robot icons 115 are displayed in the same way. This indicates that the multiple robots 3 configured in the factory corresponding to "Factory 1" are not malfunctioning.

[0045] The following is for reference Figure 6 This describes the display settings screen displayed on the display unit 22. Figure 6 This shows an example of a settings screen. Figure 6 The display settings screen 120 shown is displayed when the "Display Settings" option in the navigation tree 200 is clicked. The display settings screen 120 is a screen for accepting display-related conditions from the user, such as the number of items to be displayed, the items to be displayed, and the text format.

[0046] like Figure 6As shown, the display settings screen 120 includes an input box 121 for accepting the number of displays (a predetermined number based on priority) and a drop-down menu 122 for accepting the display mode. The drop-down menu 122 displays the display mode selected by the user from various display options. Figure 6 In this configuration, a "first marker" is set to overlap the robot icon 115 corresponding to the robot 3 within the top 5 priority positions. Therefore, the robot icon 115 corresponding to the robot 3 within the top 5 priority positions is displayed in a different manner than the robot icons 115 corresponding to the robot 3 outside the top 5 priority positions and the robot icons 115 corresponding to the robot 3 that has not experienced an anomaly.

[0047] Furthermore, it is also possible to display the robot icon 115 corresponding to the lower-priority maintenance robot 3 (which is outside the specified number indicating a higher priority) in a different manner than the robot icon 115 corresponding to the robot 3 that has not experienced any abnormalities. For example... Figure 6 As shown, the display settings screen 120 includes a selection box 123 for accepting user selection and a drop-down menu 125 for accepting display mode selection. The user selection is whether to display the robot icon 115 corresponding to the robot 3 (which indicates a lower priority, excluding the specified number of higher priority robots) in a different display mode than the robot icon 115 corresponding to the robot 3 that has not experienced any abnormalities. Figure 6 In this configuration, a "second mark" is set to overlap the robot icon 115 corresponding to robot 3, which is outside the top 5 (i.e., below the 6th position) in the priority order. Therefore, the robot icon 115 corresponding to robot 3, which has a low maintenance priority (below the 6th position), is displayed in a different manner than the robot icon 115 corresponding to robot 3, which has a high maintenance priority (within the top 5 positions) and the robot icon 115 corresponding to robot 3 that has not experienced any abnormalities.

[0048] like Figure 6As shown, the display settings screen 120 has four input boxes 126, 127, 128, and 129 corresponding to the four display items: abnormal content, abnormal code, maintenance method, and remaining days, as well as four toggle buttons 130, 131, 132, and 133. The four toggle buttons 130, 131, 132, and 133 accept the display items for robots 3 that have experienced abnormalities. For example, when toggle button 130 is set to "Do not display," the display item "Abnormal content" means that it will not be displayed for any robot 3. In the four input boxes 126, 127, 128, and 129, the number of robots 3 to be displayed is accepted for each of the abnormal content, abnormal code, maintenance method, and remaining days, respectively.

[0049] like Figure 6 As shown, for example, if the value "3" is entered in input box 126 corresponding to the display item "Abnormal Content", the toggle button 130 corresponding to the display item "Abnormal Content" will display "Display". This means that abnormal content is displayed for robots 3 within the top 3 in the display priority order, and abnormal content is not displayed for robots 3 with a display priority order of 4 or lower. Figure 6 The display item settings shown are as follows: for robot 3 with a priority of 1, all items are displayed, including the exception content, exception code, maintenance method, and remaining days; for robot 3 with a priority of 2, three items are displayed; for robot 3 with a priority of 3, two items are displayed; and for robot 3 with a priority of 4 to 10, only the remaining days are displayed. Thus, the higher the priority of robot 3, the more items are displayed. This allows users to intuitively understand the priority of robots 3 that have experienced exceptions by observing the number of displayed items.

[0050] like Figure 6 As shown, the display settings screen 120 has four drop-down menus 134, 135, 136, and 137 corresponding to the four text formats. Each of the four drop-down menus 134, 135, 136, and 137 contains candidate options for the user to select from multiple choices. Figure 6 In the text format, set the "Text Color" to "Black", the "Background" to "White", the "Size" to "10.5", and the "Position" to "Top".

[0051] The following is for reference Figure 7 This refers to the maintenance days setting screen displayed on the display unit 22. Figure 7 This shows an example of a screen displaying the maintenance days setting. Figure 7The maintenance days setting screen 140 is displayed when the "Maintenance Days Setting" option in the navigation tree 200 is clicked. The maintenance days setting screen 140 is a screen for receiving the set value for the number of maintenance days from the user.

[0052] like Figure 7 As shown, in the maintenance days setting screen 140, the maintenance grace days, the set value of the maintenance days, and the initial value of the maintenance days are displayed in relation to the diagnostic function names. The maintenance days setting screen 140 has multiple input boxes 141, 142, 143, 144, and 145, each corresponding to a different diagnostic function. Input boxes 141, 142, 143, 144, and 145 accept the set values ​​for the maintenance days corresponding to each diagnostic function. Figure 7 As shown, for example, the input box 141 corresponding to the function name "A Diagnosis" has the value "7" set. This indicates that the maintenance days for robot 3, where the "A Diagnosis" function has diagnosed an anomaly, are set to 7 days. In the calculation of the remaining days for robot 3, the maintenance grace days are set to "21 days", and the maintenance days are set to "7 days". On the other hand, the input box 143 corresponding to the diagnostic function name "C Replacement" is empty. This indicates that the maintenance days for robot 3, where the "C Replacement" function has diagnosed an anomaly, are not set. In the calculation of the remaining days for robot 3, the maintenance grace days are set to "25 days", and the initial maintenance days are set to "2 days". The initial maintenance days are the minimum maintenance days required for maintenance. Users can refer to the initial value of the maintenance days and set a set value for the maintenance days that is obtained by adding the initial value of the maintenance days to the number of days required by the company, such as the number of days approved. This can reduce the risk that the robot 3 may have to be stopped due to the company's maintenance-related operation time being too long.

[0053] The following is for reference Figure 8 This explains the monitoring process performed by monitoring device 2.

[0054] Figure 8This is a flowchart illustrating an example of the monitoring process performed by the monitoring device 2 in this embodiment. Upon receiving a start instruction for monitoring process, the monitoring device 2 begins monitoring each of the robots 3. Specifically, the monitoring device 2 displays a monitoring screen (S11) and monitors for the occurrence of anomalies (S12). For example, in step S12, based on sensor data received from the robots 3, the occurrence of anomalies in the robots 3 is diagnosed. Upon diagnosing an anomaly in a robot 3 (S13; Yes), the monitoring device 2 calculates the priority order of each of the robots 3 that have previously had anomalies diagnosed but have not undergone maintenance (S14), and updates the monitoring screen (S15). Through the processing in step S15, the display mode of the robot icons corresponding to the predetermined number of robots 3 indicating the highest priority is changed, as is the display mode of the robot icons corresponding to robots 3 not indicating the highest priority. Furthermore, the monitoring screen remains unchanged until a new anomaly occurs in a robot 3 (S13; No). The monitoring device 2 repeatedly executes processes S12 to S15, that is, it monitors the occurrence of abnormalities in each of the robots 3, and updates the monitoring screen based on the occurrence of a new abnormality, until it receives an end instruction for monitoring processing (S16; No). The monitoring device 2 terminates the monitoring process upon receiving the end instruction for monitoring processing (S16; Yes). Through the above monitoring process, whenever a new abnormality occurs in a robot 3, the monitoring screen displayed on the display unit 22 is updated, and the display mode of the multiple robot icons corresponding to the multiple robots 3 is changed.

[0055] The following is for reference Figure 9 , Figure 10 , Figure 11 This describes the effects achieved by the monitoring device 2 in this embodiment. Figure 9 Other examples of surveillance footage are shown. Figure 10 Shown in Figure 9 In the monitoring screen, the cursor is positioned on the first robot icon. Figure 11 Shown in Figure 9 In the monitoring screen, the cursor is positioned on the second robot icon. Figure 9 The screen shows a monitoring display of 11 robots 3 operating at different times.

[0056] The purpose of notifying the user of a malfunctioning robot 3 is to prompt the user to perform maintenance on that robot 3. Therefore, when the number of personnel performing maintenance is limited, it is impossible to perform maintenance on a large number of robots 3 simultaneously, so it is unnecessary to notify all malfunctioning robots 3 at the same time. In particular, when many robots 3 are malfunctioning, displaying a large amount of information on the monitoring screen would be necessary to notify the user. However, this could overwhelm the user and potentially reduce the efficiency of the maintenance work. Specifically, with many malfunctioning robots 3, the process of determining the order of maintenance may be delayed. Furthermore, there is a possibility that several robots 3 with lower maintenance priority may be maintained before those with higher priority, leading to failure to perform maintenance before the deadline and resulting in robot 3 malfunctions.

[0057] In order to prevent the reduction of workability of maintenance work performed by the user, the monitoring device 2 of this embodiment has improved the content and method of displaying the monitoring screen indicating the occurrence of abnormalities in the robot 3. One of the improvements is that it does not display too much information on the monitoring screen 160.

[0058] Specifically, such as Figure 9 As shown, a first mark 161 is superimposed on the robot icon 115 corresponding to a predetermined number of robots 3 with a high priority among those that have experienced malfunctions. This causes the robot icon 115 corresponding to the high-priority robots 3 to be displayed in a different manner than the robot icons 115 corresponding to the low-priority robots 3 and the robot icons 115 corresponding to the robots 3 that have not experienced malfunctions. Therefore, the user can intuitively identify the robot 3 corresponding to the robot icon 115 superimposed with the first mark 161 in the monitoring screen 160 as the high-priority robot 3, and can appropriately and quickly determine the order of maintenance operations. This improves the operability of maintenance operations and reduces the risk of reaching the deadline before maintenance is completed.

[0059] In addition, such as Figure 10 As shown, in the monitoring screen 160, by aligning the cursor 300 with the first robot icon 115, which is overlaid with the first mark 161, a pop-up screen 165 displays detailed information about the anomaly occurring in the robot 3 corresponding to the first robot icon 115. Similarly, as... Figure 11As shown, in the monitoring screen 160, by aligning the cursor 300 with the second robot icon 115, which is overlaid with the first mark 161, a pop-up screen 167 displays detailed information about the anomaly occurring in the robot 3 represented by the second robot icon 115. Thus, the monitoring screen 160 does not always display detailed information related to the anomaly, such as the anomaly content, anomaly code, maintenance method, and remaining days. Instead, it displays detailed information related to the anomaly occurring in the robot 3 represented by the robot icon 115, triggered by the cursor 300 aligning with the robot icon 115. Therefore, in the monitoring screen 160, without specific operational actions, only multiple robot icons 115 with display methods corresponding to maintenance priorities can be displayed, allowing the user to reliably identify the robot icon 115 corresponding to the robot 3 with the highest maintenance priority. This reduces the risk of overlooking the robot 3 with a high maintenance priority due to the large amount of information displayed on the monitoring screen 160.

[0060] Users can easily view detailed information related to the anomaly occurring in robot 3, represented by robot icon 115, by simply overlaying the cursor 300 with the robot icon 115, rather than by switching to other screens. This allows users to confirm details much less time and effort compared to always displaying detailed information. Furthermore, by displaying only the detailed information for the anomaly occurring in robot 3, represented by the specified robot icon, users can prevent misreading information and improve the efficiency of maintenance work.

[0061] In addition, Figure 10 The pop-up screen displays all items including the error content, error code, maintenance method, and remaining days. Figure 11 The pop-up screen 167 only displays the remaining days. As already explained, the robot 3 represented by the robot icon 115 with more displayed items has a higher priority than the robot 3 represented by the robot icon 115 with fewer displayed items. Users can, to some extent, determine the priority of the robot 3 represented by that robot icon based on the number of displayed items when the cursor 300 is hovering over it. Although a strict understanding of the priority is not necessary, understanding the priority allows for determining a more appropriate order for maintenance tasks.

[0062] Furthermore, in the monitoring screen 160, multiple robot icons 115 corresponding to each of the multiple robots 3 are configured according to the actual layout information. This allows the user to intuitively identify which robot 3 in the factory has malfunctioned. This saves manpower and time spent confirming which robot 3 has malfunctioned, improving the operability of maintenance operations.

[0063] Additionally, as in this embodiment, a second mark 163 can be superimposed on the robot icon 115 corresponding to a robot 3 that is outside the predetermined number of robots 3 that have experienced anomalies and whose priority is higher. This displays the robot icon 115 corresponding to robots 3 with low maintenance priority in a different manner than the robot icon 115 corresponding to robots 3 that have not experienced anomalies. The user can intuitively understand that the robot 3 corresponding to the robot icon 115 superimposed with the second mark 163 in the monitoring screen 160 is a robot 3 with low maintenance priority but experiencing anomalies. Therefore, even if a robot 3 has many remaining days and low maintenance priority, if it has the same anomaly as a robot 3 with high maintenance priority, maintenance work can be performed at the same time as the robot 3 with high maintenance priority. Furthermore, it is easier to schedule long-term maintenance operations. That is, the efficiency of overall maintenance operations can be improved.

[0064] The monitoring device 2 of this embodiment has a monitoring function to monitor the occurrence of abnormalities in the robot 3 and a notification function to alert the user that an abnormality has occurred in the robot 3. However, one feature of the monitoring device 2 of this embodiment is the notification function. Therefore, the notification function and the monitoring function of the monitoring device 2 of this embodiment can also be distributed in multiple devices. That is, the robot 3 monitoring system can also be composed of multiple robots 3, a monitoring device 2 that connects to the multiple robots 3 and monitors the occurrence of abnormalities in each of the robots 3, and a notification device connected to the monitoring device 2 that alerts the user that an abnormality has occurred in the robot 3.

[0065] The monitoring device 2 in this embodiment has the function of diagnosing abnormalities. However, if the robot 3 has the function of diagnosing its own abnormalities, the monitoring device 2 in this embodiment may not have the function of diagnosing abnormalities. In this case, the data receiving unit 23 receives abnormal information from the robot 3, including the factory ID, robot ID, abnormal content, abnormal code, and the date and time of the abnormality. The received abnormal information is recorded in the abnormality history management table.

[0066] In this embodiment, a mark is superimposed on the robot icon to change the display method. However, the type of display method is not limited to this, as long as the display method of the robot icon can be changed, that is, the user can distinguish the robot 3 with high maintenance priority from other robots 3. For example, the display method of the robot icon can be changed by using the flashing speed of the robot icon, the background color of the robot icon, etc. When using the flashing speed of the robot icon, the robot icon corresponding to the robot 3 within a predetermined number of robots with the highest priority is flashed at a first speed, the robot icon corresponding to the robot 3 outside the predetermined number of robots with the highest priority is flashed at a second speed slower than the first speed, and the robot icon corresponding to the robot 3 that has not experienced any abnormalities does not flash. In addition, the robot icons can also be displayed in a display method where their respective priorities are different. For example, the robot icons can also be displayed in a way that the higher the priority, the faster the flashing speed.

[0067] In this embodiment, by hovering the cursor over the robot icon, a pop-up window displays the anomaly details, anomaly code, date and time of occurrence, and remaining days (detailed information about the anomaly) of the robot 3 represented by that icon. However, the method of displaying detailed information related to the anomaly is not limited to this. For example, by hovering the cursor over the robot icon, detailed information related to the anomaly of the robot 3 represented by that icon can also be displayed on the monitoring screen instead of on another screen. Furthermore, if there is sufficient space to display detailed information related to the anomaly, it is not ruled out that detailed information related to the anomaly will always be displayed.

[0068] The following notes are also disclosed regarding this embodiment and its variations.

[0069] (Note 1) The monitoring device 2 includes: a monitoring unit 25 that monitors the occurrence of abnormalities in each of the multiple industrial machines 3; a calculation unit 26 that calculates the priority order of the industrial machines 3 that have experienced abnormalities based on the number of days remaining from the current date until the date when maintenance work needs to be carried out; and a display unit 22 that displays the graphic symbols of the industrial machines 3 that have experienced abnormalities, indicating the number of industrial machines 3 with the highest priority, in a different display mode than the graphic symbols of the industrial machines 3 that have experienced abnormalities but are not within the specified number of industrial machines with the highest priority, and the graphic symbols of the industrial machines 3 that have not experienced abnormalities.

[0070] (Note 2) In the monitoring device 2 described in Note 1, the display unit 22 displays the graphic symbols of industrial machines 3 that are outside the specified number of industrial machines 3 that have experienced abnormalities, in a different display mode than the graphic symbols of industrial machines 3 that have not experienced abnormalities.

[0071] (Note 3) In the monitoring device 2 described in Note 1 or Note 2, the calculation unit 26 calculates the remaining number of days by subtracting the initial value of the number of days required for maintenance work from the number of days from the date the anomaly occurred to the date when a problem might occur due to the anomaly, and by subtracting the number of days elapsed since the anomaly occurred.

[0072] (Note 4) In the monitoring device 2 described in Note 3, the calculation unit 26 replaces the initial value with the number of days set by the user to calculate the remaining days.

[0073] (Note 5) In the monitoring device 2 described in Note 3 or Note 4, the calculation unit 26 calculates the priority order based on the length of days required for maintenance work when the remaining number of days is the same.

[0074] (Note 6) The monitoring device 2 described in any one of Notes 1 to 5 further includes a display quantity setting unit 28, which sets a specified quantity according to user instructions.

[0075] (Note 7) The monitoring device 2 described in any one of Notes 1 to 6 further includes a display item setting unit 29, which sets display items related to the abnormality for the industrial machinery 3 that has experienced an abnormality, and the display unit 22 displays the display items set by the display item setting unit 29 together with the graphic symbols corresponding to the industrial machinery 3 that has experienced an abnormality.

[0076] (Note 8) In the monitoring device 2 described in Note 7, the display unit 22 is designated by the user as a graphic symbol corresponding to the industrial machine 3 that has malfunctioned, and displays display items. The display items are items related to the malfunction that has occurred in the designated industrial machine 3, and are items set by the display item setting unit 29.

[0077] (Note 9) In the monitoring device 2 described in Note 7 or Note 8, the display item setting unit 29 sets the number of industrial machines 3 that are the display objects for display items related to the anomaly.

[0078] (Note 10) In any one of Notes 7 to 9, the display items related to the anomaly include at least one of the following: anomaly content, anomaly code, maintenance method, and remaining days.

[0079] While embodiments of this disclosure have been described in detail, this disclosure is not limited to the embodiments described above. Various additions, substitutions, modifications, and partial deletions can be made to these embodiments without departing from the spirit and essence of the invention, or from the concept and spirit derived from the claims and their equivalents. For example, in the embodiments described above, the order of actions and processes is shown as an example and is not limited thereto. The same applies to the use of numerical values ​​or formulas in the description of the embodiments described above.

[0080] Explanation of reference numerals in the attached figures 1: Robot monitoring system; 2: Monitoring device; 3: Robot; 10: Network; 11: Processor; 12: Input device; 13: Display device; 14: Communication device; 15: Storage device; 21: Input unit; 22: Display unit; 23: Data receiving unit; 24: Storage unit; 25: Monitoring unit; 26: Calculation unit; 27: Screen generation unit; 28: Display quantity setting unit; 29: Display item setting unit; 30: Maintenance days setting unit; 31: Judgment unit.

Claims

1. A monitoring device, wherein, have: The monitoring department monitors the occurrence of abnormalities in various industrial machines. The calculation department calculates the priority of industrial machinery that has experienced the aforementioned anomaly based on the number of days remaining from the current date until the date when maintenance work needs to be carried out. as well as The display unit displays graphic symbols representing industrial machines within a predetermined number that have experienced the abnormality, indicating those with the highest priority, in a different manner than graphic symbols representing industrial machines outside the predetermined number that have experienced the abnormality and graphic symbols representing industrial machines that have not experienced the abnormality.

2. The monitoring device according to claim 1, wherein, The display unit will display the graphic symbols of industrial machines that have experienced the abnormality but are outside the specified number of those with the higher priority among the industrial machines, in a different display manner than the graphic symbols of industrial machines that have not experienced the abnormality.

3. The monitoring device according to claim 1 or 2, wherein, The calculation unit calculates the remaining number of days by subtracting the initial value of the number of days required for the maintenance operation from the number of days from the date the anomaly occurred to the date when the problem might occur due to the anomaly, and by subtracting the number of days elapsed since the anomaly occurred.

4. The monitoring device according to claim 3, wherein, The calculation unit replaces the initial value with the number of days set by the user to calculate the remaining number of days.

5. The monitoring device according to claim 3 or 4, wherein, When the remaining days are the same, the calculation unit calculates the priority order based on the length of days required for the maintenance operation.

6. The monitoring device according to any one of claims 1 to 5, wherein, The monitoring device also has a display quantity setting unit, which sets the specified quantity according to the user's instructions.

7. The monitoring device according to any one of claims 1 to 6, wherein, The monitoring device also includes a display item setting unit, which sets display items related to the abnormality for the industrial machinery that has experienced the abnormality. The display unit will display the display items set by the display item setting unit, along with the graphic symbols corresponding to the industrial machinery that has experienced the abnormality.

8. The monitoring device according to claim 7, wherein, The display unit is designated by the user as a trigger display item using a graphic symbol corresponding to the industrial machine that has experienced the abnormality. The display item is related to the abnormality that has occurred in the designated industrial machine and is set by the display item setting unit.

9. The monitoring device according to claim 7 or 8, wherein, The display item setting unit sets the number of industrial machines that are the display objects for display items related to the anomaly.

10. The monitoring device according to any one of claims 7 to 9, wherein, The display items related to the anomaly include at least one of the following: anomaly content, anomaly code, maintenance method, and remaining days.

Images