Machine data acquisition device

Abstract

The present invention simplifies setting for reading machine data so that a user himself / herself does not need to look up the source from which the machine data is acquired.　A machine data acquisition device according to the present invention comprises: a setting unit for setting, according to a data definition table, a data name and a source from which the data is acquired; a data reading unit for reading the data from a control device of an industrial machine according to the setting by the setting unit; and a data storage unit in which the read data is associated with the data name and stored.

Description

Machine Data Acquisition Device

[0001] The present disclosure relates to a machine data acquisition device for acquiring desired machine data.

[0002] In addition to the data held by the numerical control device, machine tool manufacturers add their own machine data (e.g., open / close status, on / off status of lights, etc.). Such machine data may be designed to be accessible externally. Furthermore, machine tool installers (integrators) may modify the machine to suit the installation environment, further increasing the amount of machine data that can be accessed. For example, there is a known technology that provides candidate data types for collected data that correspond to the data types of reference data, even when the data types of reference data that can be interpreted by an application are not associated with the data types of collected data. For example, see Patent Document 1.

[0003] International Publication No. 2021 / 059460

[0004] However, the allocation of added machine data is not standardized and generally differs for each machine depending on the design of the machine tool manufacturer or integrator. Therefore, in order for a user to obtain the desired machine data, they must refer to the machine tool manual or inquire with the machine tool manufacturer or integrator, which requires a lot of time and effort for setup.

[0005] Therefore, it is desirable to simplify the settings for reading machine data without requiring the user to search for the source of the machine data.

[0006] One aspect of the machine data acquisition device disclosed herein includes a setting unit that sets the data acquisition destination and data name in accordance with a data definition table, a data reading unit that reads data from a control device of an industrial machine in accordance with the settings made by the setting unit, and a data storage unit that stores the read data in association with the data name.

[0007] FIG. 1 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to a first embodiment. FIG. 2 is a diagram showing an example of a data definition table. FIG. 3 is a flowchart explaining the acquisition processing of the machine data acquisition device. FIG. 4 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to a second embodiment. FIG. 5 is a diagram showing an example of a data definition table. FIG. 6 is a flowchart explaining the acquisition processing of the machine data acquisition device. FIG. 7 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to a third embodiment. FIG. 8 is a flowchart explaining the acquisition processing of the machine data acquisition device. FIG. 9 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to a fourth embodiment. FIG. 10 is a diagram showing an example of a data definition table. FIG. 11 is a flowchart explaining the acquisition processing of the machine data acquisition device.

[0008] <First embodiment> A mechanical data acquisition system according to a first embodiment will be described in detail below with reference to the drawings. Fig. 1 is a diagram showing an example of a functional block configuration of the mechanical data acquisition system according to the first embodiment. As shown in Fig. 1, the mechanical data acquisition system 1 has a mechanical data acquisition device 10 and a control device 20.

[0009] The mechanical data acquisition device 10 and the control device 20 are connected to each other and communicate via a network (not shown) such as a LAN (Local Area Network) or the Internet. In this case, the mechanical data acquisition device 10 and the control device 20 are provided with a communication unit (not shown) for communicating with each other via such a connection. The mechanical data acquisition device 10 and the control device 20 may also be directly connected to each other via a connection interface (not shown). Although the mechanical data acquisition device 10 is connected to one control device 20, this is not limited thereto and the mechanical data acquisition device 10 may be connected to two or more control devices 20.

[0010] <Control device 20> For example, when the industrial machine is a machine tool, the control device 20 is a numerical control device known to those skilled in the art. For example, the control device 20 generates commands based on a machining program acquired from a CAD / CAM device (not shown) and outputs the generated commands to the machine tool (not shown). In this way, the control device 20 controls the operation of the machine tool (not shown). If the industrial machine is a robot, the control device 20 may be a robot control device or the like. The present invention is also applicable to control devices such as numerical control devices and robot control devices that control various industrial machines, including machine tools, industrial robots, service robots, forging machines, laser processing machines, and injection molding machines. The control device 20 also controls peripheral devices (not shown). In this case, the control device 20 may cooperate with another control device (not shown) (for example, a PMC (Programmable Machine Controller), a PLC (Programmable Logic Controller), etc.). Another control device (e.g., a PMC, a PLC, etc.) (not shown) that controls peripheral devices (not shown) may or may not be built into the control device 20. When the control device 20 does not have a built-in control device (e.g., a PMC, a PLC, etc.), the control device 20 may or may not be built into the industrial machine. The control device 20 and the other control device (e.g., a PMC, a PLC, etc.) are interconnected and communicate via a network (not shown). In this case, the control device 20 and the other control device (e.g., a PMC, a PLC, etc.) are provided with a communication unit (not shown) for communicating with each other via such a connection. The control device 20 and the other control device (e.g., a PMC, a PLC, etc.) may also be directly connected to each other via a connection interface (not shown). In addition, the control device 20 outputs machine data (e.g., door opening / closing, lighting, alarms, warnings, etc.) from the machine tool (not shown) controlled by the control device 20 to the machine data acquisition device 10 in response to an acquisition request from the machine data acquisition device 10 (described later).

[0011] <Mechanical Data Acquisition Device 10> The mechanical data acquisition device 10 is, for example, a computer device, and is configured to include a setting unit 110, a data reading unit 111, an input unit 120, a display unit 130, and a data storage unit 140. The mechanical data acquisition device 10 is equipped with a processing unit (not shown) such as a CPU in order to realize the operations of the functional blocks in Fig. 1. The mechanical data acquisition device 10 is also equipped with auxiliary storage devices (not shown) such as a ROM (Read Only Memory), SSD (Solid State Drive), or HDD (Hard Disk Drive) that store various control programs, and a main storage device (not shown) such as a RAM for storing data temporarily required for the processing unit to execute programs.

[0012] In the mechanical data acquisition device 10, the arithmetic processing unit reads the OS and application software from the auxiliary storage device, and executes arithmetic processing based on the OS and application software while loading the read OS and application software into the main storage device. Based on the results of this calculation, the mechanical data acquisition device 10 controls each piece of hardware. In this way, the processing by the functional blocks in Figure 1 is realized. In other words, the mechanical data acquisition device 10 can be realized by the cooperation of hardware and software.

[0013] <Setting Unit 110> The setting unit 110 sets the machine data acquisition destination and data name in accordance with the data definition table 30. The data definition table 30 is provided by a machine tool manufacturer, an integrator, or the like, and is set in the machine data acquisition device by a user or the like before executing the setting unit 110. Specifically, the data definition table 30 is set in the machine data acquisition device, for example, from a user's terminal (not shown) via a network (not shown) such as a LAN or the Internet, via the display unit 130. The data definition table 30 may be set in the machine data acquisition device in advance. Note that the setting unit 110 may acquire the data definition table 30 from a server, for example, via a network (not shown). Alternatively, if the user knows the information necessary to create the data definition table 30, the user may create the data definition table 30.

[0014] FIG. 2 is a diagram showing an example of the data definition table 30. As shown in FIG. 2, the data definition table 30 has, for example, a setting of the data name "door open / close" for the machine data acquired from PMC address "01," and a setting of the data name "light on" for the machine data acquired from PMC address "02." The data definition table 30 also has a setting of the data name "alarm" for the machine data acquired from PMC address "03," and a setting of the data name "warning" for the machine data acquired from PMC address "04." Based on the acquired data definition table 30, the setting unit 110 sets the machine data acquisition destination and the data name to be used when saving the data in the data saving unit 140 for the data reading unit 111 (described later). Specifically, the setting unit 110 sets, for example, the PMC address "01" for the data reading unit 111 and the data name to be used when saving the data. Furthermore, the setting unit 110 sets the PMC address "02" as the acquisition destination and the data name at the time of saving to "light on" for the data reading unit 111. Furthermore, the setting unit 110 sets the PMC address "03" as the acquisition destination and the data name at the time of saving to "alarm" for the data reading unit 111. Furthermore, the setting unit 110 sets the PMC address "04" as the acquisition destination and the data name at the time of saving to "warning" for the data reading unit 111. By doing so, the machine data acquisition device 10 can simplify the settings for reading machine data without the user having to look up the acquisition destination of the machine data acquired from the control device 20.

[0015] <Data Reading Unit 111> The data reading unit 111 reads machine data from the control device 20 in accordance with the settings made by the setting unit 110. Specifically, the data reading unit 111 obtains machine data from the control device 20 from an acquisition source, such as PMC address "01" set by the setting unit 110. The data reading unit 111 associates the obtained machine data with the data name set by the setting unit 110 and stores the data in the data storage unit 140. For example, when the data reading unit 111 obtains machine data "0" from PMC address "01," the data reading unit 111 stores the machine data "0 (door closed)" in the data storage unit 140 with the data name "door open / close." Furthermore, when the data reading unit 111 obtains machine data "1" from PMC address "02," the data reading unit 111 stores the machine data "1 (lights on)" in the data storage unit 140 with the data name "lights on." Furthermore, when the data reading unit 111 acquires machine data "0" from PMC address "03", it stores the machine data "0 (OFF)" as the data name "alarm" in the data storage unit 140. The machine data read by the data reading unit 111 is, for example, the value of the PMC signal of the control device 20, the value of a custom macro variable, the value of a P-CODE variable, the value of an SRAM variable, etc.

[0016] <Input unit 120> The input unit 120 communicates with a user terminal (not shown) (such as a PC (Personal Computer) or a tablet terminal) via a network (not shown) such as a LAN (Local Area Network) or the Internet, and accepts input operations from the user via software (for example, a web browser) in the user terminal (not shown). Note that the input unit 120 may also accept input operations from the user via a keyboard, mouse, touch panel, etc.

[0017] <Display unit 130> The display unit 130 may be connected to and communicate with a user's terminal (not shown) (such as a PC or a tablet terminal) via a network (not shown) such as a LAN or the Internet, and may display, for example, the data definition table 30 of machine data from software (for example, a web browser) in the user's terminal (not shown), or may display machine data acquired from the control device 20. The display unit 130 may also display the input unit 120 that accepts input operations from the user. The display unit 130 may be a liquid crystal display or the like, and may display, for example, the data definition table 30 of machine data or the machine data acquired from the control device 20.

[0018] <Data storage unit 140> The data storage unit 140 is, for example, a storage device such as an SSD or HDD, and a program for storing data in the storage device. The program for storing data is a file system, a database (DB), or the like. The above program associates the machine data acquired from the control device 20 by the data reading unit 111 with the data name given by the data reading unit 111 and stores the data.

[0019] <Acquisition process of the machine data acquisition device 10> Next, the flow of the acquisition process of the machine data acquisition device 10 will be described with reference to Fig. 3. Fig. 3 is a flowchart illustrating the acquisition process of the machine data acquisition device 10. Of the flow shown here, steps S13 and S14 are repeatedly executed while the industrial machine (not shown) is operating.

[0020] In step S11 , the setting unit 110 acquires the data definition table 30 from the server in the machine data acquisition device 10 .

[0021] In step S12, the setting unit 110 sets the machine data acquisition destination and the data name at the time of saving for the data reading unit 111 based on the data definition table 30 acquired in step S11.

[0022] In step S13, the data reading unit 111 acquires the machine data from the control device 20 for the acquisition destination set in step S12.

[0023] In step S14, the data reading unit 111 associates the machine data acquired in step S13 with the data name set in step S12 and stores it in the data storage unit 140.

[0024] As described above, the machine data acquisition device 10 according to the first embodiment can be configured based on the data definition table 30 created by a machine tool manufacturer, an integrator, etc., thereby simplifying the settings for reading out machine data without the user having to look up where the machine data is to be acquired.

[0025] Second Embodiment Next, a second embodiment will be described. As described above, in the first embodiment, the machine data acquisition device 10 acquires a data definition table 30 from a machine tool manufacturer or the like, and sets the machine data acquisition destination and data name based on the acquired data definition table 30. The machine data acquisition device 10 acquires machine data from the control device 20 for the set acquisition destination, and stores the acquired machine data linked to the set data name. In contrast, in the second embodiment, the machine data acquisition device 10A acquires a data definition table 30A from a machine tool manufacturer or the like, in which determination conditions for determining whether each machine data item is valid or invalid for each industrial machine are set, and sets the acquisition destination and data name for only machine data determined to be valid for the industrial machine based on the acquired data definition table 30A. This differs from the first embodiment in that the machine data acquisition device 10A can thereby simplify the settings for reading machine data without the user having to check the machine data acquisition destination and acquisition conditions. The second embodiment will be described below.

[0026] FIG. 4 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to the second embodiment. Elements having the same functions as elements of the machine data acquisition system 1 in FIG. 1 are designated by the same reference numerals, and detailed descriptions thereof will be omitted. As shown in FIG. 4, the machine data acquisition system 1 includes a machine data acquisition device 10A and a control device 20A. The machine data acquisition device 10A and the control device 20A are connected to each other via a network (not shown), such as a LAN or the Internet, for communication. In this case, the machine data acquisition device 10A and the control device 20A are provided with a communication unit (not shown) for communicating with each other via such a connection. The machine data acquisition device 10A and the control device 20A may also be directly connected to each other via a connection interface (not shown).

[0027] <Control device 20A> When the industrial machine is a machine tool, the control device 20A is a numerical control device known to those skilled in the art, similar to the control device 20 of the first embodiment. For example, the control device 20A generates commands based on a machining program acquired from a CAD / CAM device (not shown) and outputs the generated commands to the machine tool (not shown). In this way, the control device 20A controls the operation of the machine tool (not shown). If the industrial machine is a robot, the control device 20A may be a robot control device (not shown). The control device 20A also cooperates with another control device (not shown) to control peripheral devices (not shown). In this case, the control device 20A may also cooperate with another control device (not shown) (e.g., a PMC, a PLC, etc.). In response to an acquisition request from the machine data acquisition device 10A (described later), the control device 20A outputs machine data (e.g., door opening / closing, alarms, warnings, etc.) from the machine tool (not shown) controlled by the control device 20A to the machine data acquisition device 10A.

[0028] In the following, the machine data acquisition process of the machine data acquisition device 10A will be described using the example of a case where the control device 20A does not have machine data for lighting on, for example, when lighting inside a machine tool (not shown) is not installed due to reasons such as being an option. However, the case where there is no other machine data such as door opening / closing is similar to the case where lighting is on, and so a description thereof will be omitted. In addition to cases where there is no machine data, possible cases include when there is no optional equipment installed but the equipment is not operating due to a malfunction, or when the user or other user has disabled the function.

[0029] <Mechanical Data Acquisition Device 10A> The mechanical data acquisition device 10A is, for example, a computer device similar to the mechanical data acquisition device 10 of the first embodiment, and is configured to include a setting unit 110a, a data reading unit 111a, an input unit 120, a display unit 130, and a data storage unit 140. The data reading unit 111a also has a data validity determination unit 1110. The mechanical data acquisition device 10A is equipped with a processing unit (not shown) such as a CPU to realize the operations of the functional blocks in FIG. 4. The mechanical data acquisition device 10A is also equipped with a main storage unit (not shown) such as a ROM, SSD, or HDD that stores various control programs, and a RAM for storing data temporarily required for the processing unit to execute the programs.

[0030] In the mechanical data acquisition device 10A, the arithmetic processing unit reads the OS and application software from the auxiliary storage device, and executes arithmetic processing based on the OS and application software while expanding the read OS and application software into the main storage device. Based on the results of this calculation, the mechanical data acquisition device 10A controls each piece of hardware. This realizes the processing represented by the functional blocks in Figure 4. In other words, the mechanical data acquisition device 10A can be realized by the cooperation of hardware and software. The input unit 120, display unit 130, and data storage unit 140 have the same functions as the input unit 120, display unit 130, and data storage unit 140 of the first embodiment.

[0031] <Setting Unit 110a> Similar to the setting unit 110 of the first embodiment, the setting unit 110a sets the machine data acquisition destination and data name according to the data definition table 30A. Specifically, the setting unit 110a acquires the data definition table 30A from the machine data acquisition device 10A. The data definition table 30A contains determination conditions for determining whether each machine data item is valid or invalid, based on the options of the industrial machine, and is provided by a machine tool manufacturer, an integrator, or the like. Note that the determination result may indicate that the machine data item is valid or invalid. FIG. 5 is a diagram showing an example of the data definition table 30A. As shown in FIG. 5, the data definition table 30A includes, for example, the machine data acquisition destination of PMC address "01" and the data name "door open / close," as well as the determination conditions for determining whether the machine data item is valid or invalid. The data definition table 30A also includes the machine data acquisition destination of PMC address "02," the data name "light on," and the determination conditions for determining whether the machine data item is valid or invalid. The data definition table 30A also has a determination condition for determining whether the machine data is always valid, along with the destination of the machine data at PMC address "03" and the data name "alarm." The data definition table 30A also has a determination condition for determining whether the machine data is valid or invalid, along with the destination of the machine data at PMC address "04" and the data name "warning." The data definition table 30A also has settings for the destination of the machine data at PMC address "05" and the data name "coolant," along with the determination condition for determining whether the machine data is valid or invalid. The judgment conditions are programs or arithmetic expressions, and for example, the judgment conditions for determining whether the coolant machine data is valid are a program or arithmetic expression that describes: (a) if the software series of the control device 20A is G100 and the version number is 10 or less, it is always invalid, (b) if the software series of the control device 20A is G101, it is unknown because it cannot be determined, (c) when the address K99.9 of the PMC keep relay is 0 and K99.8 is 1, the coolant option (hardware option) is valid, so the machine data is valid, (d) if not, the machine data is invalid. The program or arithmetic expression for the judgment conditions may be written in the data definition table, or may be written in a separate file outside the data definition table.When describing the conditions in a separate file outside the data definition table, the information for referencing the determination conditions is described in the data definition table.

[0032] When the setting unit 110a acquires the data definition table 30A, it transfers the judgment conditions to a data validity judgment unit 1110 (described later) in the data reading unit 111a in order to set the machine data acquisition destination and the data name when saved in the data saving unit 140 for the data reading unit 111a (described later). Then, based on the judgment result by the data validity judgment unit 1110 (described later), the setting unit 110a excludes the acquisition destination and data name of machine data that is invalid due to options or the like and sets the machine data acquisition destination and data name for the data reading unit 111a. By doing so, even if there is a case where machine data is not available in the industrial machine due to options or the like, the machine data acquisition device 10A can simplify the settings for reading machine data without the user having to check the acquisition destination and acquisition conditions of the machine data acquired from the control device 20A.

[0033] <Data Readout Unit 111a> The data readout unit 111a reads machine data from the control device 20A in accordance with the determination results of the data validity determination unit 1110 (described later) based on the determination conditions set by the setting unit 110a. Specifically, for example, based on the determination conditions set by the setting unit 110a, the data validity determination unit 1110 acquires data required for determining the determination conditions from the control device 20A via the source of the data to be read within the determination conditions. The data required for determining the determination conditions includes, for example, the values ​​of the PMC signals, custom macro variables, P-CODE variables, and SRAM variables of the control device 20A, as well as the model, software series / version number, C-EXE series / version number, number of systems, diagnostic number value, and parameter values ​​of the control device 20A. The data validity determination unit 1110 determines whether each piece of machine data is valid or invalid using the determination conditions (programs) set for each piece of machine data and the acquired data. The data validity determination unit 1110 notifies the setting unit 110a of the determination results.

[0034] The setting unit 110a sets the destination and data name of machine data for the data reading unit 111a, excluding invalid machine data, based on the judgment result received from the data validity judgment unit 1110. Specifically, in the case of the machine data acquisition system 1 of Fig. 4, the setting unit 110a sets the destination of PMC address "01" and the data name of "door open / close", and the destination of PMC address "03" and the data name of "alarm", excluding light on, for the data reading unit 111a. The setting unit 110a also sets the destination of PMC address "04" and the data name of "warning", and the destination of PMC address "05" and the data name of "coolant", etc.

[0035] The data reading unit 111a obtains machine data from the control device 20A from an acquisition destination such as PMC address "01" set by the setting unit 110a. The data reading unit 111a associates the obtained machine data with the data name set by the setting unit 110a and stores it in the data storage unit 140. Note that the machine data read by the data reading unit 111a is, for example, the value of the PMC signal of the control device 20, the value of a custom macro variable, the value of a P-CODE variable, the value of an SRAM variable, etc., similar to the data reading unit 111 of the first embodiment.

[0036] <Acquisition Process of Machine Data Acquisition Device 10A> Next, the flow of the acquisition process of the machine data acquisition device 10A will be described with reference to Fig. 6. Fig. 6 is a flowchart illustrating the acquisition process of the machine data acquisition device 10A. Of the flow shown here, steps S25 and S26 are repeatedly executed while the industrial machine (not shown) is operating. Note that the processes of steps S21, S25, and S26 are similar to the processes of steps S11, S13, and S14 in Fig. 3, and therefore will not be described again.

[0037] In step S22, when the setting unit 110a acquires the data definition table 30A in step S21, the setting unit 110a transfers the determination conditions for each machine data in the data definition table 30A to the data validity determination unit 1110.

[0038] In step S23, the data validity determination unit 1110 acquires data required for determining the judgment conditions set in step S22 from the control device 20A as the source of the machine data to be read within the judgment conditions. The data validity determination unit 1110 determines whether each machine data is valid or invalid using the judgment conditions set for each machine data and the acquired machine data. The data validity determination unit 1110 notifies the setting unit 110a of the judgment result.

[0039] In step S24, the setting unit 110a excludes invalid machine data based on the determination result received from the data validity determination unit 1110, and sets the machine data acquisition destination and data name for the data reading unit 111a.

[0040] As described above, the machine data acquisition device 10A according to the second embodiment acquires the data definition table 30A created by a machine tool manufacturer, an integrator, or the like, and determines in advance whether each piece of machine data is valid or invalid based on the determination conditions set in the data definition table 30A. This allows the machine data acquisition device 10A to simplify the settings for reading machine data without the user having to check the machine data acquisition source or acquisition conditions themselves. The second embodiment has been described above.

[0041] <Modification of Second Embodiment> In the second embodiment, the data validity determination unit 1110 obtains data required for determining whether a set determination condition is met from the control device 20A for the data source to be read under the determination condition, and the data reading unit 111a obtains machine data from the control device 20A for the source set by the setting unit 110a. However, this is not limited to this. For example, the data validity determination unit 1110 may obtain data from a numerical control device for the data source to be read under the determination condition set by the setting unit 110a, and the data reading unit 111a may obtain data from the numerical control device for the machine data source set by the setting unit 110a. The data reading unit 111a may associate the obtained machine data with the data name set by the setting unit 110a and store it in the data storage unit 140.

[0042] <Third Embodiment> Next, a third embodiment will be described. In the first embodiment, the machine data acquisition device 10 acquires a data definition table 30 from a machine tool manufacturer or the like, and sets the machine data acquisition destination and data name based on the acquired data definition table 30. The machine data acquisition device 10 acquires machine data from the control device 20 for the set acquisition destination, and stores the acquired machine data linked to the set data name. In the second embodiment, the machine data acquisition device 10A acquires a data definition table 30A from a machine tool manufacturer or the like, in which judgment conditions for determining whether each machine data is valid / invalid for each industrial machine are set, and sets the acquisition destination and data name for only machine data judged to be valid for the industrial machine based on the acquired data definition table 30A. In contrast, in the third embodiment, the machine data acquisition device 10B differs from the first and second embodiments in that it displays a list of machine data to be read from the control device 20A and allows the user to select desired machine data. This allows the machine data acquisition device 10B to simplify the settings for reading machine data without the user having to check the machine data acquisition destination and acquisition conditions. The third embodiment will be described below.

[0043] Fig. 7 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to the third embodiment. Elements having the same functions as elements of the machine data acquisition system 1 in Fig. 4 are denoted by the same reference numerals, and detailed description thereof will be omitted. As shown in Fig. 7, the machine data acquisition system 1 has a machine data acquisition device 10B and a control device 20A. The control device 20A has the same functions as the control device 20A of the second embodiment.

[0044] The mechanical data acquisition device 10B is, for example, a computer device or the like similar to the mechanical data acquisition device 10A of the second embodiment, and is configured to include a read data selection unit 112, a setting unit 110b, a data reading unit 111a, an input unit 120, a display unit 130, and a data storage unit 140. The data reading unit 111a also has a data validity determination unit 1110. The mechanical data acquisition device 10B is equipped with a processing unit (not shown) such as a CPU to realize the operation of the functional blocks in FIG. 7. The mechanical data acquisition device 10B is also equipped with a main storage unit (not shown) such as a ROM, SSD, or HDD that stores various control programs, and a RAM for storing data temporarily required for the processing unit to execute the programs.

[0045] In the mechanical data acquisition device 10B, the arithmetic processing unit reads the OS and application software from the auxiliary storage device, and executes arithmetic processing based on the OS and application software while expanding the loaded OS and application software into the main storage device. Based on the results of this calculation, the mechanical data acquisition device 10B controls each piece of hardware. This achieves the processing represented by the functional blocks in FIG. 7. In other words, the mechanical data acquisition device 10B can be realized by the cooperation of hardware and software. The input unit 120, display unit 130, and data storage unit 140 have the same functions as the input unit 120, display unit 130, and data storage unit 140 of the first embodiment. The data reading unit 111a has the same functions as the data reading unit 111a of the second embodiment. The data validity determination unit 1110 has the same functions as the data validity determination unit 1110 of the second embodiment.

[0046] <Read data selection unit 112> The read data selection unit 112 selects machine data to read based on, for example, the judgment result of the data validity judgment unit 1110. Specifically, the read data selection unit 112 displays, for example, the judgment result of the data validity judgment unit 1110 on the display unit 130. The read data selection unit 112 selects the machine data to read that the user desires from the displayed machine data that has been judged to be valid, based on an input operation by the user via the input unit 120. The read data selection unit 112 notifies the setting unit 110b of the selected machine data.

[0047] <Setting unit 110b> The setting unit 110b has the same function as the setting unit 110a of the second embodiment, and when it receives machine data selected by the read data selection unit 112, it sets the acquisition destination and data name of the selected machine data in the data reading unit 111a based on the judgment result of the data validity judgment unit 1110 and the data definition table 30A. In this way, even if optional machine data is present in an industrial machine (not shown), the machine data acquisition device 10B can simplify the settings for reading desired machine data without the user having to look up the acquisition destination of the machine data themselves.

[0048] <Acquisition Process of Machine Data Acquisition Device 10B> Next, the flow of the acquisition process of the machine data acquisition device 10B will be described with reference to Fig. 8. Fig. 8 is a flowchart illustrating the acquisition process of the machine data acquisition device 10B. Of the flow shown here, steps S36 and S37 are repeatedly executed while the industrial machine (not shown) is operating. Note that the processes of steps S31 to S33 and steps S36 to S37 are similar to the processes of steps S21 to S23 and steps S25 to S26 in Fig. 6, and therefore will not be described again.

[0049] In step S34, the read data selection unit 112 selects the machine data to be read based on the determination result of step S33 in response to the user's input operation via the input unit 120.

[0050] In step S35, the setting unit 110b sets the acquisition destination and data name of the machine data selected in step S34 in the data reading unit 111a.

[0051] As described above, the machine data acquisition device 10B according to the third embodiment acquires the data definition table 30A created by a machine tool manufacturer, an integrator, or the like, and determines whether each piece of machine data is valid or invalid in advance based on the determination conditions set in the data definition table 30A. Based on the determination results, the machine data acquisition device 10B sets the acquisition destination and data name of the desired machine data selected by the user. This allows the machine data acquisition device 10A to simplify the settings for reading machine data without the user having to look up the acquisition destination of the machine data themselves. The third embodiment has been described above.

[0052] <Fourth Embodiment> Next, the fourth embodiment will be described. In the first embodiment, the machine data acquisition device 10 acquires a data definition table 30 from a machine tool manufacturer or the like, and sets the machine data acquisition destination and data name based on the acquired data definition table 30. The machine data acquisition device 10 acquires machine data from the control device 20 for the set acquisition destination, and stores the acquired machine data linked to the set data name. In the second embodiment, the machine data acquisition device 10A acquires a data definition table 30A from a machine tool manufacturer or the like, in which judgment conditions for determining whether each machine data is valid / invalid according to the machine tool are set, and sets the acquisition destination and data name only for machine data judged to be valid according to the machine tool based on the acquired data definition table 30A. In the third embodiment, the machine data acquisition device 10B differs from the first and second embodiments in that it displays a list of machine data read from the control device 20A and allows the user to select desired machine data. In contrast, in the fourth embodiment, the machine data acquisition device 10C differs from the first to third embodiments in that it processes the read data into machine data desired by the user. This allows the machine data acquisition device 10C to simplify the settings for reading machine data without the user having to look up where to obtain the machine data. Furthermore, even if the machine data desired by the user is not directly stored in the control device 20, the machine data acquisition device 10C can generate the machine data desired by the user by processing the data read from the control device 20. The fourth embodiment will now be described.

[0053] Fig. 9 is a diagram showing an example of a functional block configuration of a machine data acquisition system according to the fourth embodiment. Elements having the same functions as elements of the machine data acquisition system 1 in Fig. 1 are denoted by the same reference numerals, and detailed description thereof will be omitted. As shown in Fig. 9, the machine data acquisition system 1 has a machine data acquisition device 10C and a control device 20. The control device 20 has the same functions as the control device 20 in the first embodiment.

[0054] The mechanical data acquisition device 10C is, for example, a computer device similar to the mechanical data acquisition device 10 of the first embodiment, and is configured to include a setting unit 110c, a data reading unit 111, a calculation unit 113, an input unit 120, a display unit 130, and a data storage unit 140. Note that the mechanical data acquisition device 10C is equipped with a processing unit (not shown) such as a CPU in order to realize the operations of the functional blocks in Fig. 9. The mechanical data acquisition device 10C also includes a main storage unit (not shown) such as a ROM, SSD, or HDD that stores various control programs, and a RAM for storing data temporarily required for the processing unit to execute the programs.

[0055] In the mechanical data acquisition device 10C, the arithmetic processing unit loads the OS and application software from the auxiliary storage device, and executes arithmetic processing based on the OS and application software while expanding the loaded OS and application software into the main storage device. Based on the results of this calculation, the mechanical data acquisition device 10C controls each piece of hardware. This achieves the processing represented by the functional blocks in FIG. 9. In other words, the mechanical data acquisition device 10C can be realized by the cooperation of hardware and software. The input unit 120, display unit 130, and data storage unit 140 have the same functions as the input unit 120, display unit 130, and data storage unit 140 of the first embodiment. The data reading unit 111 has the same functions as the data reading unit 111 of the first embodiment.

[0056] <Setting Unit 110c> Similar to the setting unit 110 of the first embodiment, the setting unit 110c acquires a data definition table 30C provided by a machine tool manufacturer, an integrator, or the like, from within the machine data acquisition device 10C. FIG. 10 is a diagram showing an example of the data definition table 30C. As shown in FIG. 10, the data definition table 30C contains, for example, a data acquisition destination, an arithmetic expression for processing the machine data acquired from the acquisition destination, and a data name of the machine data processed by the arithmetic expression. Note that when an arithmetic expression is written in the data definition table 30C, there may be multiple data acquisition destinations for one machine data. Furthermore, the value of another machine data may be set for that data acquisition destination. For example, the data definition table 30C contains the "PMC address value" as the acquisition destination of the machine data of coolant temperature (Fahrenheit), the arithmetic expression for converting coolant temperature (Fahrenheit) to coolant temperature (Celsius), and the data name of the machine data processed by the arithmetic expression, "coolant temperature (Fahrenheit)." The data definition table 30C also contains the following settings: the "PMC address value" for the source of the machine data for the coolant pressure drop; the "PMC address value" for the source of the machine data for the filter pressure drop; an arithmetic expression for determining whether or not a warning is issued from the acquired machine data; and the data name "Warning" for the machine data processed by the arithmetic expression. The data definition table 30C also contains the following settings: an arithmetic expression for determining whether or not air blow is ON from the block elements of the machining program executed by the control device 20; and the data name "Air Blow ON" for the machine data processed by the arithmetic expression. Note that, similar to the data definition table 30 of the first embodiment, only the source and the data name may be set in the data definition table 30C. Based on the acquired data definition table 30C, the setting unit 110 sets the source of the machine data and the data name when saved in the data saving unit 140 for the data reading unit 111. The setting unit 110c also transfers the arithmetic expressions of the data definition table 30C to the calculation unit 113, which will be described later, and sets them.

[0057] <Calculation unit 113> The calculation unit 113 processes the machine data read by the data reading unit 111. Specifically, the calculation unit 113 inputs the machine data read by the data reading unit 111 into an arithmetic expression set by the setting unit 110c, for example, and outputs the processed machine data (e.g., coolant temperature (Celsius)) to the data storage unit 140. The calculation unit 113 then associates the output machine data with a data name and stores it in the data storage unit 140. Note that the calculation unit 113 may output machine data for which an arithmetic expression is not set directly from the data reading unit 111 to the data storage unit 140.

[0058] <Acquisition Processing of Machine Data Acquisition Device 10C> Next, the flow of the acquisition processing of the machine data acquisition device 10C will be described with reference to Fig. 11. Fig. 11 is a flowchart illustrating the acquisition processing of the machine data acquisition device 10C. Of the flow shown here, steps S44, S45, and S46 are repeatedly executed while the machine tool (not shown) is operating. Note that the processing of steps S41, S42, and S44 is similar to the processing of steps S11, S12, and S13 in Fig. 3, and therefore description thereof will be omitted.

[0059] In step S43, the arithmetic expression of the data definition table 30C obtained in step S41 is transferred to the arithmetic unit 113 and set.

[0060] In step S45, the calculation unit 113 inputs the machine data read out in step S44 into the calculation formula set in step S43, and processes the machine data.

[0061] In step S46, the data reading unit 111 / calculating unit 113 associates the read / processed machine data with the set data name and stores it in the data storage unit 140.

[0062] As described above, the machine data acquisition device 10C according to the fourth embodiment can be configured based on the data definition table 30 created by a machine tool manufacturer, integrator, or the like, thereby simplifying the settings for reading machine data without the user having to look up where to obtain the machine data. Furthermore, even if the machine data desired by the user is not directly stored in the control device 20, the machine data acquisition device 10C can generate the machine data desired by the user by processing the data read from the control device 20. The fourth embodiment has been described above.

[0063] As described above in the first embodiment, the second embodiment, the modified example of the second embodiment, the third embodiment, and the fourth embodiment, the machine data acquisition devices 10, 10A, 10B, and 10C of the present disclosure can simplify the settings for reading machine data without the user having to look up the source of the machine data themselves.

[0064] <Modifications> In the first embodiment, the second embodiment, the modification of the second embodiment, the third embodiment, and the fourth embodiment described above, the mechanical data acquisition devices 10, 10A, 10B, and 10C are devices separate from the control devices 20 and 20A, but this is not limiting. For example, the mechanical data acquisition devices 10, 10A, 10B, and 10C may be included in the control devices 20 and 20A.

[0065] Note that the functions included in the machine data acquisition devices 10, 10A, 10B, and 10C in the first embodiment, the second embodiment, the modified example of the second embodiment, the third embodiment, the modified example of the third embodiment, and the fourth embodiment can be realized by hardware, software, or a combination of these. Here, "realized by software" means that the functions are realized by a computer reading and executing a program.

[0066] The program can be stored and supplied to a computer using various types of non-transitory computer-readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / Ws, and semiconductor memories (e.g., mask ROMs, PROMs (Programmable ROMs), EPROMs (Erasable PROMs), flash ROMs, and RAMs). The program may be provided to the computer by various types of transient computer-readable media. Examples of transient computer-readable media include electrical signals, optical signals, and electromagnetic waves. The transient computer-readable media can provide the program to the computer via a wired communication path such as an electrical wire or optical fiber, or via a wireless communication path.

[0067] The step of executing the program recorded on the recording medium includes not only processes that are performed in chronological order, but also processes that are not necessarily performed in chronological order but are performed in parallel or individually. Also, the step of writing the program may be performed by cloud computing.

[0068] Although the present disclosure has been described in detail, the present disclosure is not limited to the individual embodiments described above. Various additions, substitutions, modifications, partial deletions, etc. are possible in these embodiments without departing from the gist of the present disclosure or the spirit of the present disclosure derived from the content of the claims and their equivalents. These embodiments can also be implemented in combination. For example, in the above-described embodiments, the order of each operation and the order of each process are shown as examples and are not limited to these. The same applies when numerical values ​​or mathematical expressions are used in the description of the above-described embodiments.

[0069] The following supplementary notes are further disclosed regarding the above-described embodiments and modified examples. (Supplementary Note 1) A machine data acquisition device (10) includes a setting unit (110) that sets a data acquisition destination and a data name in accordance with a data definition table (30), a data reading unit (111) that reads data from an industrial machine control device (20) in accordance with the settings by the setting unit (110), and a data storage unit (140) that stores the read data in association with the data name. (Supplementary Note 2) The machine data acquisition device (10A) of Supplementary Note 1 includes a data validity determination unit (1110) that determines whether data is valid or invalid using a determination condition, and the setting unit (110a) sets a data acquisition destination and a data name in the data reading unit (111a) based on the determination result of the data validity determination unit (1110). (Supplementary Note 3) The machine data acquisition device (10B) of Supplementary Note 2 is provided with a read data selection unit (112) that selects data to be read based on the determination result of the data validity determination unit (1110). (Supplementary Note 4) In the machine data acquisition device (10B) of Supplementary Note 1 or Supplementary Note 2, the data reading unit (111a) uses data read from the numerical control device. (Supplementary Note 5) The machine data acquisition device (10C) of Supplementary Note 1 is further provided with a calculation unit (113) that processes the data read by the data reading unit (111), and the calculation unit (113) stores the processed data in the data storage unit (140).

[0070] 1 Mechanical data acquisition system 10, 10A, 10B, 10C Mechanical data acquisition device 110, 110a, 110b, 110c Setting unit 111, 111a Data reading unit 1110 Data validity determination unit 112 Read data selection unit 113 Calculation unit 120 Input unit 130 Display unit 140 Data storage unit 20, 20A Control device 30, 30A, 30C Data definition table

Claims

1. A machine data acquisition device comprising: a setting unit that sets the data acquisition destination and data name in accordance with a data definition table; a data reading unit that reads data from an industrial machinery control device in accordance with the settings made by the setting unit; and a data storage unit that links the read data to the data name and stores it.

2. A machine data acquisition device as described in claim 1, further comprising a data validity determination unit which determines whether data is valid or invalid using a determination condition, and the setting unit sets the data acquisition destination and data name in the data reading unit based on the determination result of the data validity determination unit.

3. The machine data acquisition device according to claim 2, further comprising a read data selection section which selects data to be read based on a result of the judgment by said data validity judgment section.

4. A machine data acquisition device as claimed in claim 1 or 2, wherein the data reading unit uses data read from a numerical control device.

5. The machine data acquisition device according to claim 1, further comprising a calculation unit that processes the data read by the data reading unit, and the calculation unit stores the processed data in the data storage unit.