JPWO2021100308A1 - Machine tools, log output methods, and log output programs - Google Patents

Abstract

The machine tool has an operation screen and operates on an operation panel for receiving operations on the machine machine, a first OS (Operating System) for controlling the display of the operation screen, a storage device, and the first OS. It runs on the application to be used and a second OS different from the first OS, controls the PLC (Programmable Logic Controller) according to the machining program, and controls the machining of the workpiece after receiving the instruction input to start machining the workpiece. It is equipped with a control device. The application provides a function different from the control performed by the control device and also provides a function related to the machine tool. The first log that receives the operation from the operation screen of the operation panel and is output from the application and the second log that is output from the control device are stored in the storage device in synchronization with the time held by the first OS. To.

Description

The present disclosure relates to a technique for supporting analysis of a plurality of types of logs output from a machine tool.

Japanese Unexamined Patent Publication No. 2018-129066 (Patent Document 1) discloses a machine tool equipped with an HMI (Human Machine Interface). The HMI is an HMI that functions as a user interface. The user can perform various operations on the machine tool via the HMI.

Japanese Unexamined Patent Publication No. 2018-129066

FIG. 12 is a diagram showing an example of the configuration of the machine tool 10X. As shown in FIG. 12, the machine tool 10X includes an OS (Operating System) 30, an application 40, and a control device 50.

OS30 is, for example, Windows®. The OS 30 provides various basic functions to the application 40. Application 40 is, for example, an HMI that acts as a user interface. The control device 50 is, for example, an NC (Numerical Control) unit. The control device 50 controls the machine tool 10X according to the machining program to control the machining of the workpiece.

Each of the application 40, the OS 30, and the control device 50 outputs a log individually. When an abnormality occurs in the machine tool 10X, the user tries to find out the cause of the abnormality by checking various logs. However, the logs output from each of the application 40, the OS 30, and the control device 50 are not related to each other, and the user takes a lot of time to analyze the logs. Therefore, a technique for supporting the analysis of various logs output from a machine tool is desired. The above-mentioned Patent Document 1 does not disclose any configuration for outputting a log.

In one example of the present disclosure, the machine tool has an operation screen, an operation panel for receiving operations on the machine machine, a first OS (Operating System) for controlling the display of the operation screen, and a storage device. , The application that runs on the first OS and the second OS that is different from the first OS, controls the PLC (Programmable Logic Controller) according to the machining program, and inputs instructions to start machining the workpiece. It is equipped with a control device that controls the machining of the work after receiving the signal. The application provides a function different from the control performed by the control device and also provides a function related to the machine tool. The first log output from the application upon receiving the operation from the operation screen of the operation panel and the second log output from the control device are synchronized with the time held by the first OS. It is stored in the above storage device.

In another example of the present disclosure, the machine tool operates on a first OS (Operating System) and a second OS different from the first OS, and controls a PLC (Programmable Logic Controller) according to a machining program. A control device that controls the machining of the workpiece, an application that operates on the first OS, provides a function different from the control performed by the control device, and provides a function related to the machine tool, a display, and the like. It includes the first OS, the application, and a display control unit that displays each log output from the control device on the display. Each of the logs displayed on the display includes the output time of the log, the identification information indicating the output source of the log, and the contents of the log.

It can support the analysis of various logs output from machine tools.

It is a figure which shows the appearance of a machine tool. It is a figure which shows an example of the configuration for realizing the log integration function. It is a figure which shows an example of the log screen displayed on the display. It is a figure which shows the log screen which follows the modification 1. It is a figure which shows the log screen which follows the modification 2. It is a figure which shows the flow of the log writing process by a recorder. It is a figure which shows roughly the function of the recorder which follows the modification. It is a schematic diagram which shows an example of the hardware composition of the operation panel. It is a flowchart which shows the flow of the log buffering process by a log accumulation part. It is a flowchart which shows the flow of the record processing of a log by a recorder. It is a flowchart which shows the flow of the record log display processing by a display control unit. It is a figure which shows an example of the structure of a machine tool. It is a figure which shows the other example of the configuration for realizing the log integration function. It is a figure which shows the contents of a record log in detail. It is a figure which shows the log screen. It is a figure which shows the log output from an application. It is a figure which shows the user interface 90 provided by HMI. It is a figure which shows an example of the shortcut icon which can be displayed in the icon display area AR. It is a figure which shows the user interface of a reference example. It is a figure which shows an example of the screen transition of a user interface. It is a figure which shows an example of the screen transition of a user interface.

Hereinafter, embodiments according to the present invention will be described with reference to the drawings. In the following description, the same parts and components are designated by the same reference numerals. Their names and functions are the same. Therefore, the detailed description of these will not be repeated. In addition, each embodiment and each modification described below may be selectively combined as appropriate.

<A. Appearance of machine tool 10>
A machine tool 10 according to an embodiment will be described with reference to FIG. FIG. 1 is a diagram showing the appearance of the machine tool 10.

The term "machine tool" as used herein is a concept that includes a machine tool that performs work removal processing (SM (Subtractive manufacturing) processing), a machine tool that performs work addition processing (AM (Additive manufacturing) processing), and the like. Is. Further, the machine tool 10 may be a vertical machining center or a horizontal machining center. Alternatively, the machine tool 10 may be a lathe, an additional processing machine, or another cutting machine or grinding machine.

As shown in FIG. 1, the machine tool 10 which is an example of the present embodiment includes an operation panel 100 and a processing machine 200. The operation panel 100 and the processing machine 200 are configured to be able to communicate with each other. The operation panel 100 and the processing machine 200 may be connected wirelessly or by wire. As an example, Ethernet (registered trademark) is adopted as the communication standard of the operation panel 100 and the processing machine 200.

The operation panel 100 functions as a display device. The operation panel 100 is a computer and includes a display 105 (display means) and operation keys 106. The display 105 displays various information related to processing. The display 105 is, for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or other display device. Further, the display 105, which is an example of the present embodiment, is composed of a touch panel, and accepts various operations on the machine tool 10 by touch operation. Of course, a display 105 that is not a touch panel may be used. The operation key 106 is composed of a plurality of hardware keys and accepts various operations on the machine tool 10.

The processing machine 200 of the present embodiment will be described with an example of processing a work according to a processing program designed in advance, but the present invention is not limited to this. For example, it may be a processing machine that manually operates the operation panel of the processing machine to process the work, or may be a processing machine that processes the work according to the processing program created on the operation panel. Further, the user can give various processing instructions to the processing machine 200 from the operation panel 100.

<B. Log integration function>
The log integration function of the machine tool 10 will be described with reference to FIGS. 2 and 3. FIG. 2 is a diagram showing an example of a configuration for realizing a log integration function.

As shown in FIG. 2, the machine tool 10 includes an operation panel 100 and a processing machine 200. The operation panel 100 includes an OS 30, an application 40, a clock unit 60, a log writing unit 61, a display control unit 66, a display 105, and a storage device 120. The log writing unit 61 includes a log collecting unit 62 and a recorder 64. The processing machine 200 has a control device 50. The OS 30, the application 40, and the control device 50 function as a log output unit 20 and output logs individually.

However, this configuration is not limited to this. For example, the operation panel 100 has only the display 105, and the processing machine 200 controls the OS 30, the application 40, the clock unit 60, the log writing unit 61, the display control unit 66, and the storage device 120. It may be configured to have the device 50. In this case, the physical operation panel of FIG. 1 has only a display 105 and an operation key 106, and when the operation key is pressed, the signal is sent to the processing machine 200 side and the log is written in the processing machine 200. Logs are collected in section 61.

OS30 is, for example, Windows®. Alternatively, the OS 30 may be a UNIX®-based OS such as Linux® or macOS. The OS 30 provides various basic functions to the application 40. The OS30 outputs, for example, a log related to its own performance. As an example, the log includes a CPU (Central Processing Unit) usage rate (usage amount), a memory usage rate (usage amount), and the like. The format of the log output by the OS 30 may be a text format or a structured format.

Application 40 runs on OS30. Application 40 is, for example, an HMI that acts as a user interface. The user interface accepts various operations (setting operations, etc.) for the machine tool 10 and displays various information for the machine tool 10. The HMI is, for example, MAPPS manufactured by DMG Mori Seiki Co., Ltd.

The application 40 is not limited to HMI. For example, the application 40 may be a management application for managing machining information and a machining program, or other applications related to machining.

The application 40 provides a function different from the control performed by the control device (NC unit) and also provides a function related to the machine tool. As an example of an application that provides functions different from the control performed by the control device (NC unit) and provides functions related to the machine tool, various data (spindle load, shaft speed, alarm, etc.) acquired from the machine tool are used as data types. There is an application (hereinafter referred to as "connect-application") that converts each data structure into a fixed data structure and sends it to an external server or the like. This connect-application is different from the HMI application. If the data structure is different for each machine tool or machine tool manufacturer, it becomes difficult to manage multiple machine tools. Therefore, it is an application for converting various data acquired from a machine tool into a predetermined data structure and making it common. This application outputs a log of transmission when data is transmitted to an external server, and outputs a log of data conversion completion when conversion to a predetermined data structure is completed.

An example of an application that provides functions related to machine tools is an alarm application that handles alarm messages from applications such as NC units and HMIs. From these applications, when a signal such as an input is received from an input means, a log such as reception of an input signal is output. Also, when an alarm message acquisition request is received, the log that sent the alarm message to the target is output.

The application 40 outputs, for example, a log related to its own performance, an operation log such as the order of operations, and the like. As an example, the log includes a screen switching time in HMI and the like. The format of the log output by the application 40 may be a text format or a structured format. The application 40 is operated by, for example, the operation panel 100, and outputs a log corresponding to the operation.

The control device 50 includes, for example, a numerical control device (NC unit) and a PLC (Programmable Logic Controller). The PLC includes an OS provided separately from the OS 30. Typically, the OS is a different type of OS than the OS 30. The OS is, for example, a real-time OS. The PLC controls a unit inside the control device 50 such as an NC unit. The NC unit controls the machining machine 200 according to a pre-designed machining program based on the machining start command from the PLC. As a result, the control device 50 controls the machining of the work.

The control device 50 outputs, for example, a log related to its own performance, a log displaying a status, and the like. As an example, the log includes a status display log that displays the ON / OFF status of the PLC signal. The format of the log output by the control device 50 may be a text format or a structured format.

The logs output from each of the OS 30, the application 40, and the control device 50 are input to the log accumulation unit 62. The log accumulation unit 62 functions as a buffer for sequentially storing input logs. Typically, the buffer is reserved in a predetermined storage area in the storage device 120. For example, as the log accumulation unit 62, an in-memory database such as EventStore can be used.

The clock unit 60 is a functional module for acquiring the current time information. The current time information is acquired from, for example, a timekeeping function (timer) installed as standard in the OS 30. Alternatively, the current time information may be acquired from an external device (eg, a server) configured to be communicable with the machine tool 10.

The log accumulation unit 62 stores a log sequentially output from the OS 30, a log sequentially output from the application 40, and a log sequentially output from the control device 50. At this time, the log accumulation unit 62 further associates the time information acquired from the clock unit 60 with the logs output from each of the OS 30, the application 40, and the control device 50. That is, since the time information from the same clock unit 60 is given to the logs collected in the log accumulation unit 62, the time axis of each log is the same.

More specifically, the log accumulation unit 62 acquires the current time from the clock unit 60 based on each of the OS 30, the application 40, and the control device 50 outputting the log. Next, the log accumulation unit 62 associates the acquired current time with the log as the output time of the log, and buffers the set of the log and the output time. In this way, the time information from the clock unit 60 shared among the OS 30, the application 40, and the control device 50 is associated with each log. As a result, the logs output from each of the OS 30, the application 40, and the control device 50 are synchronized. That is, the time axis of each log is unified.

When the data size of the log buffered in the log collecting unit 62 reaches the upper limit, the log collecting unit 62 overwrites the oldest log with the new log in order. By overwriting the log, the storage capacity of the log collecting unit 62 is maintained below a certain value. Further, by overwriting the oldest logs in order, a newer series of logs is left in the log collecting unit 62.

The recorder 64 sequentially reads the logs stored in the log collecting unit 62, and stores the read logs as the record log 124 in the storage device 120. Typically, the size of the storage area in the storage device 120 reserved for the record log 124 is larger than the buffer size of the log collection unit 62.

The display control unit 66 is a functional module for controlling the display of the display 105 of the operation panel 100. As an example, the display control unit 66 displays the record log 124 on the display 105. FIG. 3 is a diagram showing an example of the log screen 80 displayed on the display 105.

In the following example, an example in which the record log 124 is displayed on the display 105 will be described, but the output destination of the record log 124 is not limited to the display 105. As an example, the record log 124 may be displayed on the user's PC via the server, or may be output as data.

With reference to FIG. 3, the log screen 80 displays a part or all of the record log 124. Each of the logs displayed as the record log 124 includes a log output time 81A, identification information 81B indicating a log output source, and log contents 81C. The identification information 81B is information for uniquely identifying the output source. The identification information 81B is, for example, the name of the log output source or the ID (Identification) of the log output source.

As described above, by displaying the logs from different types of output sources on one log screen 80, the user can easily compare various logs and analyze the logs easily. As a result, the machine tool 10 can assist the user in analyzing the logs.

Further, since the output time 81A of each log is information attached based on the time of the same clock unit 60, the time axis is the same. In the past, even if there was information on the output time, the OS, application, and control device had different time axes, so it was necessary to align the time axes, but that is no longer necessary.

Preferably, the display control unit 66 displays each log displayed on the log screen 80 in the order of output time. As described above, the time information associated with each log displayed on the log screen 80 is synchronized. Therefore, by displaying each log in the order of output time, the user can compare the logs before and after the time when the abnormality such as tool interference or software occurred, and it is possible to easily find the cause of the abnormality. It will be possible.

The user can synchronize and reproduce (simulate) the behavior of the operation panel 100 and the processing machine 200 by using the logs before and after the occurrence of an abnormality such as tool interference or software, and the cause of the abnormality can be easily generated. It will be possible to find out. Furthermore, by loading the logs before and after the occurrence of an abnormality into a machine tool with the same specifications, the situation including machine operation can be reproduced. As a result, the user can easily identify the cause of the abnormality.

In addition, the log integration function shown in FIG. 2 has a new effect by having the following configuration. When the operation panel 100 acquires the log of the processing machine 200, normally, the application 40 as an HMI sends a log acquisition request to the control device 50 of the processing machine 200 at predetermined monitoring cycles. At this time, in order to monitor the control device 50 in more detail, it is necessary to set the monitoring cycle short. As a result, the frequency of sending log acquisition requests from the operation panel 100 to the processing machine 200 increases, and the load on the CPU of the operation panel 100 and the control device 50 of the processing machine 200 increases. However, in order to utilize the log integration function shown in FIG. 2, the control device 50 may be configured to spontaneously send logs to the log accumulation unit 62. With such a configuration, the operation panel 100 does not have to send a log acquisition request to the control device 50, and has a new effect of reducing the load on the CPU of the operation panel 100 and the control device 50 of the processing machine 200. Of course, the control device may send the log to the log collecting unit 62 in response to the log acquisition request from the operation panel 100.

Further, the log screen 80 shown in FIG. 3 allows the user to grasp the following. For example, the user can check from the logs of the OS 30 and the application 40 how much CPU load is applied to the screen switching in chronological order. Alternatively, the user can specify whether the setup work is in progress or the work is left unattended from the operation log when the application displayed on the operation panel 100 is operated and the in-flight camera image. Further, when it is possible to specify whether the setup work is in progress or the work is left unattended from the log output from the control device by pressing the operation key related to the control device of the operation panel 100 and the image of the in-flight camera. There is. Alternatively, the user can open the door from the status log of the control device (NC unit) and the operation log when operating the application displayed on the screen of the operation panel 100 even though the door lock is released. It is possible to identify that it was not open. This makes it possible to understand the possibility that the machine tool is left unattended and wasteful time cannot be used for machining. Alternatively, the machine tool 10 extracts an operation log or the like that is considered to have caused an abnormality from the operation log of the application or the status log of the control device (NC unit) displayed on the screen of the operation panel 100. The operation log can be displayed automatically. Alternatively, when the identification information of the person in charge is included in the log, the user can analyze the work efficiency of an individual such as who is taking time for which work.

In the above description, an example in which the log output unit 20 includes the OS 30, the application 40, and the control device 50 has been described, but the log output unit 20 includes the OS 30, the application 40, and the control device. At least two with 50 may be included. As an example, the log output unit 20 includes only the OS 30 and the application 40. As another example, the log output unit 20 includes only the OS 30 and the control device 50. As another example, the log output unit 20 includes only the application 40 and the control device 50. As another example, the log output unit 20 includes an OS 30, an application 40, a control device 50, and other devices or functional modules having a log output function.

Further, in the above description, the example in which the record log 124 is displayed on the display 105 of the operation panel 100 has been described, but the record log 124 may be transmitted to the server. As an example, the server analyzes the record log 124 collected from each of the machine tools 10 using AI (Artificial Intelligence) and identifies the work status. As another example, the server may specify the period during which the setup work was performed, the period during which the person in charge was absent, and the like, based on the operation log of the operation panel 100 and the like. As yet another example, the server may detect an operation error or a work error of an operator based on an operation log of the operation panel 100 or the like. The detection result is notified to an external device and is useful for improving the function.

Further, in the above description, the example in which the application 40 is installed in the operation panel 100 has been described, but the application 40 may be installed in another PC other than the operation panel 100. The PC is placed on the control panel of the machine tool 10, for example, and functions as a server. In this case, the log accumulation unit 62 collects logs from the application in the control panel and synchronizes the logs with other logs.

<C. Modification example 1 of log screen 80>
Next, a modification 1 of the log screen 80 shown in FIG. 3 will be described with reference to FIG. FIG. 4 is a diagram showing a log screen 80A according to the first modification.

The display control unit 66 (see FIG. 2) described above emphasizes the log satisfying the predetermined normal / abnormal condition among the record logs 124 displayed on the display 105 of the operation panel 100 more than the other logs. (See Fig. 4). The normal / abnormal condition may be arbitrarily selected from, for example, a plurality of predetermined candidates for the normal / abnormal condition.

In FIG. 4, "NC Status is in operation" is shown as an example of normal conditions. "NC Status is in operation" is a condition indicating that the NC unit was in operation.

Further, FIG. 4 shows "memory usage rate of 70% or more" and "CPU usage rate of 80% or more" as examples of abnormal conditions. "Memory usage rate of 70% or more" is a condition indicating that the memory usage rate exceeds 70%. "CPU usage rate of 80% or more" is a condition indicating that the CPU usage rate exceeds 80%.

In this modification, on the log screen 80A, highlight columns 82A to 82C indicating whether or not the normal / abnormal condition is satisfied are displayed side by side in the record log 124. The highlighting columns 82A to 82C are provided according to normal / abnormal conditions.

The highlight column 82A indicates whether or not the normal condition of "NC Status operation" is satisfied. The display control unit 66 highlights the line corresponding to the log satisfying the normal condition among the lines constituting the highlighting column 82A more than the other lines. The log highlighted in the highlight column 82A indicates that the NC unit was operating at the output time of the log.

The highlighting column 82B indicates whether or not the abnormal condition of "memory usage rate of 70% or more" is satisfied. The display control unit 66 highlights the line corresponding to the log satisfying the abnormal condition among the lines constituting the highlighting column 82B more than the other lines. The log highlighted in the highlighting column 82B indicates that the memory usage rate was 70% or more at the output time of the log.

The highlighting column 82C indicates whether or not the abnormal condition of "CPU usage rate of 80% or more" is satisfied. The display control unit 66 highlights the line corresponding to the log satisfying the abnormal condition among the lines constituting the highlighting column 82C more than the other lines. The log highlighted in the highlighting column 82C indicates that the CPU usage rate was 80% or more at the output time of the log.

The highlighting method in the highlighting columns 82A to 82C is arbitrary. As an example, logs that satisfy the normal / abnormal conditions are displayed in a different color from other logs. Alternatively, logs that satisfy the normal / abnormal conditions are displayed darker than other logs. Alternatively, logs that satisfy the normal / abnormal conditions are displayed in a font different from other logs.

Further, the logs satisfying the normal / abnormal conditions are displayed in different display modes between the highlighting columns 82A to 82C. As an example, logs that satisfy the condition of "NC Status running" are displayed in green, logs that satisfy the condition of "memory usage rate of 70% or more" are displayed in yellow, and the condition of "CPU usage rate of 80% or more" are displayed. The logs to be filled are displayed in red.

With the above highlighting function, the user can easily distinguish between a log indicating normality / abnormality from a huge amount of logs, and can find out the cause of the abnormality more quickly.

<D. Modification example 2 of log screen 80>
Next, a modification 2 of the log screen 80 shown in FIG. 3 will be described with reference to FIG. FIG. 5 is a diagram showing a log screen 80B according to the second modification.

In the above-mentioned modification 1, the highlighting columns 82A to 82C are displayed side by side in the record log 124, and the logs satisfying the normal / abnormal condition are highlighted in the highlighting columns 82A to 82C. On the other hand, in this modification, the method of highlighting the log is different from the above-mentioned modification 1. In this modification, the display control unit 66 highlights the log itself that satisfies the normal / abnormal condition.

In the example of FIG. 5, the log 83A indicating the start / completion of the operation of the NC unit is highlighted. Log 83B, which indicates that the memory usage is 70% or higher, is highlighted. Log 83C, which indicates that the CPU usage rate is 80% or more, is highlighted.

Even if the log is highlighted by the above method, the user can easily distinguish the normal / abnormal log from the huge number of logs. As a result, the user can find out the cause of the anomaly more quickly.

The log screen 80A according to the modification 1 and the log screen 80B according to the modification 2 may be combined. That is, the display control unit 66 may display the highlight fields 82A to 82C side by side on the record log 124, and may highlight the log itself that satisfies the normal / abnormal condition.

<E. Function of log collection unit 62>
Next, with reference to FIG. 6, the function of the above-mentioned log collecting unit 62 (see FIG. 2) will be described in more detail. FIG. 6 is a diagram showing a flow of log buffering processing by the log accumulation unit 62.

In step S1, the log accumulation unit 62 receives the logs sequentially output from the OS 30, the logs sequentially output from the application 40, and the logs sequentially output from the control device 50, and sequentially buffers those logs. do. At this time, each log is buffered in the log accumulation unit 62 in the order of output time. In the example of FIG. 6, the logs L1 to L10 are sequentially stored in the log collecting unit 62.

In step S2, it is assumed that the data size of the log buffered in the log accumulation unit 62 has reached a predetermined data size (upper limit value). In this case, the log accumulation unit 62 overwrites the buffered log with the newly obtained log in order from the log having the oldest output time. That is, the log buffered in the log collecting unit 62 is rewritten in the FIFO (First In First Out) format. In the example of step S2, the oldest log L1 is overwritten with the new log L11.

<F. Recorder 64 functions>
Next, with reference to FIG. 7, the function of the recorder 64 (see FIG. 2) described above will be described in more detail. FIG. 7 is a diagram schematically showing the functions of the recorder 64.

As described above, the recorder 64 stores the log buffered in the log collecting unit 62 in the storage device 120, and leaves the log in the storage device 120. At this time, the recorder 64 changes the storage mode of the log in the storage device 120 depending on whether or not an abnormality has occurred in the machine tool 10.

More specifically, in a normal time when no abnormality has occurred in the machine tool 10, the recorder 64 extracts a part of each log buffered in the log collecting unit 62, and the extracted log is used as a simple log 124A. , Store in a predetermined area (first storage area) in the storage device 120. That is, the amount of information per log of the simple log 124A is smaller than the amount of information per log of the log buffered in the log accumulation unit 62. In this way, the storage capacity can be reduced by storing only a part of each log as the simple log 124A.

On the other hand, when an abnormality occurs in the machine tool 10, a more detailed log buffered in the log collecting unit 62 (hereinafter, also referred to as “detailed log 124B”) is stored in a predetermined area (hereinafter, also referred to as “detailed log 124B”) in the storage device 120. Store in the second storage area). The amount of information per log of the detailed log 124B is larger than the amount of information per log of the simple log 124A. Further, the storage capacity of the storage area (second storage area) for the detailed log 124B is larger than the storage capacity of the storage area (first storage area) for the simple log 124A. By storing the detailed log 124B when an abnormality occurs, a log indicating the cause of the abnormality remains more reliably.

Typically, a plurality of detailed logs 124B before and after the occurrence of the abnormality are left in the above-mentioned second storage area. More specifically, when an abnormality occurs in the machine tool 10, the recorder 64 determines that the output time of the log in each log buffered in the log collecting unit 62 includes the time when the abnormality occurs. Acquire multiple logs belonging to the time (hereinafter, also referred to as "record time"). Then, the recorder 64 stores the acquired plurality of logs as the detailed log 124B. As a result, the logs output before and after the occurrence of the abnormality remain in the storage device 120.

Preferably, the length of record time varies depending on the type of anomaly that has occurred. As an example, the recorder 64 specifies the record time corresponding to the occurrence of the abnormality based on the record time information in which the length of the record time is defined by the type of abnormality. Then, the recorder 64 stores the log belonging to the record time based on the abnormality occurrence time as the detailed log 124B.

Depending on the amount of log output when an abnormality occurs, the log for the record time may not remain in the storage area for the simple log 124A. In that case, as many logs as possible remaining in the storage area are acquired.

Further, the recorder 64 selectively acquires logs according to the type of abnormality generated in the machine tool 10. More specifically, as described in FIG. 3 above, each log output from the OS 30, the application 40, and the control device 50 has a log output time 81A, an identification information 81B indicating a log output source, and the like. , Includes multiple types of information such as log content 81C. The recorder 64 changes the log information to be stored according to the type of abnormality generated in the machine tool 10. As an example, the log information to be stored is predetermined for the type of abnormality. In this way, by leaving the information corresponding to the occurrence of the abnormality as the detailed log 124B, not only the information of the log indicating the cause of the abnormality can be left, but also the storage capacity can be reduced.

The simple log 124A and the detailed log 124B can be read by various viewers. As an example, the simple log 124A and the detailed log 124B can be read by a dedicated display tool 85A or another display tool 85B such as a GUI (Graphical User Interface) analysis tool or a graph display tool.

<G. Hardware configuration of operation panel 100>
The hardware configuration of the operation panel 100 will be described with reference to FIG. FIG. 8 is a schematic diagram showing an example of the hardware configuration of the operation panel 100.

The operation panel 100 includes a processor 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a communication interface 104, a display 105, an operation key 106, and an auxiliary storage device 115. These components are connected to the bus 110. The ROM 102, the RAM 103, and the auxiliary storage device 115 are examples of the above-mentioned storage device 120 (see FIG. 8).

The processor 101 is composed of, for example, at least one integrated circuit. The integrated circuit may be, for example, at least one CPU (Central Processing Unit), at least one GPU (Graphics Processing Unit), at least one ASIC (Application Specific Integrated Circuit), at least one FPGA (Field Programmable Gate Array), or them. It may be composed of a combination of.

The processor 101 controls the operation of the operation panel 100 by executing various programs such as the information processing program 130 and the operating system. The information processing program 130 is a program for realizing the above-mentioned log collection and log display. The processor 101 reads the information processing program 130 from the auxiliary storage device 115 or the ROM 102 to the RAM 103 based on the reception of the execution instruction of the information processing program 130. The RAM 103 functions as a working memory and temporarily stores various data necessary for executing the information processing program 130.

A LAN (Local Area Network), an optical cable, an antenna, or the like is connected to the communication interface 104. The operation panel 100 is connected to various devices such as the processing machine 200 via the communication interface 104, for example. As a result, the operation panel 100 exchanges data with the NC unit in the processing machine 200.

The display 105 is, for example, a liquid crystal display, an organic EL display, or other display device. The display 105 sends an image signal for displaying an image to the display 105 in accordance with a command from the processor 101 or the like. As an example, the above-mentioned log screens 80, 80A, 80B (see FIGS. 3 to 5) and the like are displayed on the display 105. The display 105 may be integrally configured with the operation panel 100, or may be configured separately from the operation panel 100.

The operation key 106 is composed of a plurality of hardware keys and accepts various user operations on the operation panel 100. A signal corresponding to the pressed key is output to the processor 101.

The auxiliary storage device 115 is a storage medium such as a hard disk or a flash memory. The auxiliary storage device 115 stores the OS 30, the application 40, the record log 124, the information processing program 130, and the like. These storage locations are not limited to the auxiliary storage device 115, and may be stored in a storage area of the processor 101 (for example, a cache memory), a ROM 102, a RAM 103, an external device (for example, a server), or the like.

The information processing program 130 may be provided by being incorporated into a part of any program, not as a single program. In this case, the log integration process by the information processing program 130 is realized in cooperation with an arbitrary program. Even a program that does not include such a part of the modules does not deviate from the purpose of the information processing program 130 according to the present embodiment. Further, some or all of the functions provided by the information processing program 130 may be realized by dedicated hardware. Further, the operation panel 100 may be configured in the form of a so-called cloud service in which at least one server executes a part of the processing of the information processing program 130.

In the above description, an example in which a signal corresponding to a user's key operation on the operation panel 100 is output to the processor 101 has been described, but the signal may be sent directly to the NC unit or PLC.

Further, in the above description, the hardware configuration of the operation panel 100 is not limited to the example of FIG. As an example, the operation panel 100 may be composed of a display 105 and an operation key 106. Although not shown in FIG. 8, a processor different from the processor 101 and an auxiliary storage device different from the auxiliary storage device 115 are provided in the processing machine 200.

<H. Flowchart of log accumulation unit 62>
Next, the processing flow of the log collecting unit 62 will be described with reference to FIG. 9. FIG. 9 is a flowchart showing the flow of log buffering processing by the log accumulation unit 62.

The process shown in FIG. 9 is realized by the processor 101 of the operation panel 100 executing the above-mentioned information processing program 130 (see FIG. 8). In other aspects, some or all of the processing may be performed by circuit elements or other hardware.

In step S110, the processor 101 determines whether or not the log is output from the output source to be monitored. The monitoring target includes, for example, at least two of the OS 30, the application 40, and the control device 50. When the processor 101 determines that the log is output from the output source to be monitored (YES in step S110), the processor 101 switches the control to step S112. If not (NO in step S110), the processor 101 ends the process shown in FIG.

In step S112, the processor 101 acquires the current time from the above-mentioned clock unit 60 (see FIG. 2).

In step S120, the processor 101 determines whether or not the data size of the log stored in the above-mentioned log accumulation unit 62 (see FIG. 2) exceeds a predetermined upper limit value. When the processor 101 determines that the data size of the log stored in the log collecting unit 62 exceeds a predetermined upper limit value (YES in step S120), the processor 101 switches the control to step S122. Otherwise (NO in step S120), processor 101 switches control to step S124.

In step S122, the processor 101 deletes the log having the oldest output time from the log collecting unit 62 among the logs stored in the log collecting unit 62.

In step S124, the processor 101 associates the identification information for identifying the log output source with the current time information acquired in step S112 with the contents of the log, and writes them in the log accumulation unit 62.

In the above description, the example in which the processor 101 writes the log to the log collecting unit 62 has been described, but the log output source may write the log directly to the log collecting unit 62.

<I. Flowchart of recorder 64>
Next, the processing flow of the recorder 64 (see FIG. 2) described above will be described with reference to FIG. FIG. 10 is a flowchart showing the flow of log record processing by the recorder 64.

The process shown in FIG. 10 is realized by the processor 101 of the operation panel 100 executing the above-mentioned information processing program 130 (see FIG. 8). In other aspects, some or all of the processing may be performed by circuit elements or other hardware.

In step S130, the processor 101 determines whether or not an abnormality has occurred in the machine tool 10. When the processor 101 determines that an abnormality has occurred in the machine tool 10 (YES in step S130), the processor 101 switches the control to step S132. Otherwise (NO in step S130), processor 101 switches control to step S140.

In step S132, the processor 101 functions as the recorder 64 (see FIG. 2) described above, and stores the detailed log 124B, which is a part or all of each log buffered in the log collecting unit 62, in the storage device 120. .. Since the storage mode of the detailed log 124B is as described with reference to FIG. 7 above, the description thereof will not be repeated.

In step S140, it is determined whether or not the new log to be recorded is stored in the above-mentioned log accumulation unit 62 (see FIG. 2). The log to be recorded includes, for example, at least two logs output from the OS 30, a log output from the application 40, and a log output from the control device 50. Preferably, the log to be recorded may be preset or arbitrarily set by the user. When the processor 101 determines that the new log to be recorded is stored in the log accumulation unit 62 (YES in step S140), the processor 101 switches the control to step S142. If not (NO in step S140), processor 101 returns processing to step S130.

In step S142, the processor 101 functions as the recorder 64 (see FIG. 2) described above, extracts a part of the log of the record target buffered in the log collecting unit 62, and uses the extracted log as the simple log 124A. Remember. The amount of information per log of the simple log 124A stored in step S142 is smaller than the amount of information per log of the detailed log 124B stored in step S132. Since the storage mode of the simplified log 124A is as described with reference to FIG. 7 above, the description thereof will not be repeated.

In the above description, an example in which the process of step S142 is executed according to the determination result of step S130 has been described, but the process of step S142 may be executed regardless of the determination result of step S130. In this case, the process of step S142 is executed in parallel with the flowchart shown in FIG. 10, and the simple log 124A is always stored.

<J. Flowchart of display control unit 66>
Next, with reference to FIG. 11, the processing flow of the display control unit 66 described above will be described. FIG. 11 is a flowchart showing a flow of display processing of the record log 124 by the display control unit 66.

The process shown in FIG. 11 is realized by the processor 101 of the operation panel 100 executing the above-mentioned information processing program 130 (see FIG. 8). In other aspects, some or all of the processing may be performed by circuit elements or other hardware.

In step S150, the processor 101 determines whether or not the display instruction of the record log 124 has been accepted. The display instruction is issued, for example, based on invoking the display tool of the record log 124. When the processor 101 determines that the display instruction of the record log 124 has been received (YES in step S150), the processor 101 switches the control to step S152. If not (NO in step S150), processor 101 ends the process shown in FIG.

In step S152, the processor 101 displays the record log 124 on the display 105 of the operation panel 100.

In step S154, the processor 101 highlights a log that satisfies a predetermined condition more than other logs. Since the method of highlighting the log is as described in FIGS. 4 and 5, the description will not be repeated.

<K. Modification example of functional configuration>
Next, a modified example of the functional configuration shown in FIG. 2 will be described with reference to FIGS. 13 and 14. FIG. 13 is a diagram showing another example of the configuration for realizing the log integration function.

The machine tool 10 shown in FIG. 2 described above integrates the logs by using the time information of the clock unit 60A provided separately from the OS 30. On the other hand, the machine tool 10 shown in FIG. 13 integrates logs by using the time information of the clock unit 60A in the OS 30. Further, the machine tool 10 shown in FIG. 13 is different from the machine tool 10 shown in FIG. 2 in that it has a format unification unit 65.

Since other points are the same as those of the machine tool 10 shown in FIG. 2, only the functional configuration of the clock unit 60A and the format unification unit 65 will be described below.

The OS 30 includes a clock unit 60A. The clock unit 60A is a timekeeping function installed as standard in the OS 30. This is a functional module for acquiring the current time information.

The log accumulation unit 62 stores various logs sequentially output from the log output unit 20 such as the OS 30, the application 40, and the control device 50. At this time, the log accumulation unit 62 associates the time information acquired from the clock unit 60A with various logs sequentially output from the log output unit 20. As a result, the time information output from the clock unit 60A of the OS 30 becomes the reference for the output time of various logs.

The format unification unit 65 unifies the formats of various logs sequentially output from the log output unit 20.

The format of the log output from the OS 30 is composed of, for example, the date when the log was output, the output time of the log, the CPU temperature, and the CPU usage rate. As an example, OS30 outputs the log "" 07/15/2019 "," 17: 17: 12.419 "," 328 "," 14.0910342 "".

The format of the log output from the application 40 as HMI is, for example, the date when the log was output, the time of the log, the log level, the name of the application from which the log is output, and the contents such as operation information for the application. Consists of. As an example, the application 40 is a log "2019-07-15 17: 15: 49,384 INFO Application Operation LOG: KEY: KeyDown: G that provides functions different from those performed by the control device and functions related to machine tools." Is output.

The format of the log output from the control device 50 is composed of, for example, the contents of the log and the time of the log. The contents of the log include operation information such as reset key input. As an example, the control device 50 outputs the log "MDI P_ <RESET> 17:44:03".

The format unification unit 65 defines the format of the log output from the OS 30, the format of the log output from the application 40, and the format of the log output from the control device 50 in advance (hereinafter, "unified format"). It is also called.).

More specifically, the unified format is composed of the date when the log was output, the time when the log was output, the log level, the log output source, and the log contents such as operation information. The date and the time are the times acquired from the clock unit 60A. Preferably, the format unification unit 65 rewrites the time information of the log output from each of the application 40 and the control device 50 with the time acquired from the clock unit 60A, and does not rewrite the time information of the log output from the OS 30. This is because the log output from the OS 30 is originally generated based on the time of the clock unit 60A.

When the load of the NC unit is high as described above, the processing of the time information of the time unit independently owned by the NC unit is also delayed, which may cause a difference from the time information of the clock unit 60A of the OS 30 in which the application is executed. In such a case, if the time information is not unified, the processing between the NC unit and OS30 will correspond when the log information is output to find the cause when the movement of the machine tool is different from the normal one. You haven't done that. Therefore, conventionally, it has been necessary to first adjust the time information of the NC unit and the time information of the OS30, and investigate the correspondence between the processing of the NC unit and the processing of the OS in the unified time information. By unifying the time information in the clock section like this time, it is easy to search for the cause.

In this embodiment, only the time of the log of the OS 30 is not rewritten, but the present embodiment is not limited to this mode. Even if the OS 30 has a clock unit for ticking the time for associating with the log, the log output from the OS 30 may be processed in the same manner as other logs and the time may be rewritten.

FIG. 14 is a diagram showing the contents of the record log 124 in detail. In the example of FIG. 14, the record log 124 includes logs D1 to D3.

The log D1 is a log obtained by modifying the log output from the application 40 according to the unified format. The log D2 is a log obtained by modifying the log output from the OS 30 according to the unified format. The log D3 is a log obtained by modifying the log output from the control device 50 according to the unified format.

In this way, by modifying various logs according to the unified format, different types of logs can be easily compared. In particular, the user can compare various logs on the same time axis, which facilitates log analysis.

In the above description, an example in which the format unification unit 65 is mounted on the recorder 64 has been described, but the format unification unit 65 does not necessarily have to be mounted on the recorder 64. Further, the log shaping function can be implemented not only in the recorder 64 but also in other functional configurations such as the display control unit 66.

<L. Advantages of log synchronization function>
The advantages of the above-mentioned log synchronization function will be described with reference to FIG. FIG. 15 is a diagram showing a log screen 80C. The log screen 80C shown in FIG. 15 is different from the log screen 80A shown in FIG. 4 in the content of the record log 124.

The broken line portion 86A of the log screen 80C shows a log related to screen switching in the HMI (application 40). As an example, the log relating to screen switching includes a log indicating that a screen display operation on the display 105 has been accepted and a log indicating that the screen display on the display 105 has been completed.

By checking the log in the broken line portion 86A, the user can identify that it took 2 seconds or more to switch the screen of the HMI. The user can also specify that it takes about 500 msec from the press of the screen switching button of the HMI to the start of screen switching. In order to estimate these causes, the user confirms the highlight columns 82A to 82C corresponding to the broken line portion 86A. As a result, the user can grasp that the memory usage is large and the CPU usage rate is high, and it can be inferred that there is a problem in the internal processing and the screen switching processing related to the completion of the operation.

The broken line portion 86B of the log screen 80C shows a log related to screen switching in HMI. By checking the log in the broken line portion 86B, the user can identify that it took about 2 seconds to switch the screen (functional window). The details of the functional window will be described later. The screen constituting the HMI includes a screen for acquiring information received from the NC device (control device 50). When the NC device performs processing with a large amount of calculation, the reception of information from the NC device to the HMI is delayed, and switching to the screen or updating the screen is delayed.

In order to investigate the cause, the user confirms the highlight columns 82A to 82C corresponding to the broken line portion 86B. As a result, the user can identify that the memory usage is large and the CPU usage rate is high in the first half (about 1 second) of the screen switching. Further, the user can identify from the contents of the log of the broken line portion 86B that the function window switching process is executed and the response from the NC unit is slow. As a result, the user can presume that the reason why the screen switching is delayed is that the load on the NC unit is high and it takes time to acquire the information necessary for display.

If the above-mentioned log synchronization function is not implemented, the user will investigate the cause by checking the log shown in FIG. FIG. 16 is a diagram showing a log 125 output from the application 40.

Since the log 125 only indicates that there is no response from the NC device, the user cannot determine the reason. However, with the synchronization log shown in FIG. 15, the user can easily infer the cause of the anomaly.

<M. An example of the HMI screen>
The user interface provided by HMI will be described with reference to FIG. FIG. 17 is a diagram showing a user interface 90 provided by the HMI.

The user interface 90 is displayed on the display 105 of the operation panel 100. The user interface 90 includes an icon display area AR and functional windows SC1 to SC6 that function as screen display areas.

A shortcut icon for opening the screen is displayed in the icon display area AR. Each of the shortcut icons is associated with a predetermined screen.

The user interface 90 is configured to accept a selection operation of a shortcut icon displayed in the icon display area AR and a selection operation of the function windows SC1 to SC6. The user interface 90 shifts the screen associated with the shortcut icon selected from the plurality of shortcut icons displayed in the icon display area AR to the selected function window in the plurality of function windows SC1 to SC6. indicate.

As an example, the size of the functional window SC6 is larger than the size of the functional windows SC1 to SC5. Each of the functional windows SC1 to SC6 functions as a display area of the screen and displays various information related to processing.

In the example of FIG. 17, a tool information display screen is displayed on the functional window SC1. On the display screen, the shape parameter of the tool, the wear amount parameter of the tool, and the like are displayed.

A modal information display screen is displayed on the function window SC2.
A work offset setting screen is displayed on the function window SC3. The user sets a reference point of the work in the three-dimensional space on the setting screen. The reference point is referred to in a machining program or the like.

A display screen of the coordinate system is displayed on the function window SC4. On the display screen, various coordinate systems recognized by the machining program are displayed.

A machining program related to foreground operation is displayed on the functional window SC5.
A tool offset setting screen is displayed on the function window SC6. On the setting screen, the tool correction value is displayed. The tool correction value includes, for example, a shape parameter indicating the shape of the tool and a wear parameter indicating the amount of wear of the tool.

FIG. 18 is a diagram showing shortcut icons IC1 to IC8, which are examples of shortcut icons that can be displayed in the icon display area AR. Each of the shortcut icons IC1 to IC8 is associated with a predetermined screen.

Typically, the shortcut icons IC1 to IC8 represent thumbnails of the associated screens. This makes it easier to distinguish the shortcut icons IC1 to IC8.

The number of shortcut icons in the icon display area AR is arbitrary. Preferably, the user can configure the icon display area AR with any combination of shortcut icons.

Also, the number and size of functional windows in the user interface 90 is arbitrary. Preferably, the user can configure the user interface 90 with any combination of functional windows.

<N. Advantages of shortcut icons>
The advantage of providing the icon display area AR in the user interface 90 will be described with reference to FIG. FIG. 19 is a diagram showing a reference example user interface 90X for comparison with the user interface 90 shown in FIG.

When displaying a specific screen on the user interface 90X, the user first presses the mode switching button BT1 to switch the operation mode to the screen set editing mode. Next, the user presses the expansion button BT2 to open the list of major categories, and selects the major category including the screen to be displayed. Next, the user presses the expansion button BT3 to open the list of middle classifications and selects the middle classification including the screen to be displayed. Next, the user moves the screen to a place to be displayed while holding down the button BT4 representing the screen to be displayed, so that the screen is displayed at an arbitrary place. Next, press the mode switching button BT1 to end the screen set editing mode.

As described above, in the user interface 90X which is a reference example, the user performs the button pressing operation four times and the drag and drop operation once to display the target screen on the user interface 90X. Can be done. On the other hand, in the user interface 90 shown in FIG. 17, the user can display the target screen on the user interface 90 by one drag and drop operation.

<O. Screen transition of user interface 90>
The operation mode of the user interface 90 shown in FIG. 17 will be described with reference to FIGS. 20 and 21. 20 and 21 are diagrams showing an example of screen transition of the user interface 90.

In step S11, it is assumed that the user presses the shortcut button BT. As a result, the operation panel 100 displays a list of shortcut icons in the icon display area AR.

In step S12, the user presses the shortcut icon IC related to the screen to be displayed from the list of shortcut icons displayed in the icon display area AR.

In step S13, the user moves the shortcut icon IC to a desired location while pressing the shortcut icon IC. In the example of FIG. 21, the shortcut icon IC has been moved to the location of the function window SC1. The user then lifts his or her finger from the display 105.

In step S14, the operation panel 100 displays a screen associated with the shortcut icon IC in the functional window SC1A of the user interface 90. After that, the operation panel 100 hides the list of shortcut icons.

The log output by HMI includes the operation log in steps S11 to S14. As an example, the log output by the HMI includes a log indicating that the screen display operation on the display 105 has been accepted and a log indicating that the screen display on the display 105 has been completed. The log indicating that the screen display operation on the display 105 has been accepted includes the screen type of the shortcut icon selected in step S12 and the selection time of the screen. The log indicating that the display of the screen on the display 105 is completed includes the type of the screen displayed in step S14 and the time when the display of the screen is completed.

Although FIGS. 20 and 21 have described an example in which an operation of opening a target screen at a target location is performed by a drag and drop operation, the opening operation is not necessarily performed by a drag and drop operation. There is no need. For example, the opening operation may be realized by sequentially performing an operation of pressing a shortcut icon included in the icon display area AR and an operation of pressing any of the function windows SC1 to SC6.

<P. Summary>
As described above, when the machine tool 10 receives a log from the OS 30, the application 40, the control device 50, or the like, the machine tool 10 acquires and acquires the time information shared between the OS 30, the application 40, and the control device 50. The set of the collected log and the acquired time information is stored in the storage device 120. As a result, the machine tool 10 can synchronize the logs output from different output sources, and can compare various logs with a common time index.

It should be considered that the embodiments disclosed this time are exemplary in all respects and not restrictive. The scope of the present invention is shown by the scope of claims rather than the above description, and is intended to include all modifications within the meaning and scope of the claims.

10,10X machine machine, 20 log output unit, 40 application, 50 controller, 60, 60A clock unit, 61 log writing unit, 62 log integration unit, 64 recorder, 65 format unification unit, 66 display control unit, 80, 80A, 80B, 80C log screen, 81A output time, 81B identification information, 81C content, 82A, 82B, 82C highlight column, 83A, 83B, 83C, 125 log, 85A, 85B display tool, 86A, 86B broken line part, 90 , 90X user interface, 100 operation panel, 101 processor, 102 ROM, 103 RAM, 104 communication interface, 105 display, 106 operation key, 110 bus, 115 auxiliary storage device, 120 storage device, 124 record log, 124A simple log, 124B Detailed log, 130 information processing program, 200 processing machine.

Claims (5)

It ’s a machine tool,
An operation panel that has an operation screen and accepts operations on the machine tool,
A first OS (Operating System) that controls the display of the operation screen,
With storage
The application running on the first OS and
A control device that operates on a second OS different from the first OS, controls a PLC (Programmable Logic Controller) according to a machining program, and controls machining of a workpiece after receiving an instruction input for starting machining of the workpiece. , Equipped with
The application provides functions different from those performed by the control device and provides functions related to the machine tool.
The first log output from the application in response to the operation from the operation screen of the operation panel and the second log output from the control device are synchronized with the time held by the first OS. A machine tool stored in the storage device. The machine tool unifies the logs of the first log and the second log into a predetermined format, and stores the logs in the storage device in association with the time held by the first OS. , The machine tool according to claim 1. The first log is
A log indicating that the screen display operation on the operation panel has been accepted, and
The machine tool according to claim 1 or 2, including a log indicating that the display of the screen on the operation panel is completed. The application is configured to display the user interface on the control panel.
The user interface is
Multiple screen display areas and
Includes an icon display area for multiple shortcut icons,
Each of the plurality of shortcut icons is associated with a predetermined screen.
The third aspect of the present invention, wherein the user interface displays a screen associated with a shortcut icon selected from the plurality of shortcut icons in a selected display area among the plurality of screen display areas. Machine Tools. It ’s a machine tool,
The first OS (Operating System) and
A control device that operates on a second OS different from the first OS, controls a PLC (Programmable Logic Controller) according to a machining program, and controls machining of a workpiece.
An application that operates on the first OS, provides a function different from the control performed by the control device, and provides a function related to the machine tool.
With the display
The first OS, the application, and a display control unit for displaying each log output from the control device on the display are provided.
Each of the logs displayed on the display is a machine tool including the output time of the log, identification information indicating the output source of the log, and the contents of the log.

Images