Method and device for exchanging tool data

Abstract

The invention relates to a method for processing tool data on a machine tool having a data interface for connection to a tool management system and an associated control device and computer program product. The method comprises the following steps: acquiring a unique tool identifier WID of a tool to be picked up; matching the acquired WID with previously known tool identification data of the machine tool; if it is determined that the to-be-picked tool is not determined and / or the updated tool data of the WID is available, tool data is automatically retrieved directly from the tool management system through the data interface based on the acquired WID or tool data is automatically retrieved directly from the to-be-picked tool; the loading position of the tool to be picked up is determined on the basis of the retrieved tool data, and the tool is preferably picked up at the determined loading position.

Description

Technical Field

[0001] The invention relates to a method for processing tool data on a machine tool having a data interface for connection to a tool management system and an associated control device and a computer program product. Background Art

[0002] In the prior art, it is known to control workpiece machining on numerically controlled machine tools by means of an NC control device which is usually integrated on the machine tool. Specifically, the NC control device controls controllable actuators such as a spindle drive of a machine tool, axis drives of machine tool axes and other machine functions of the machine tool, for example, based on an NC program generated by a CAD / CAM system or programmed by a machine operator.

[0003] In the German patent application with publication number DE102006043390A1, a device and a method for simulating the machining sequence of a workpiece on a machine tool are described. The method is characterized by an integrated simulation method. Specifically, the PLC movement sequence of the machine tool is also simulated with the help of a PLC control device and a PLC sequence simulation device. Therefore, all basic aspects of the machine tool can be realistically simulated.

[0004] In European patent application with publication number EP2891020A1, an extended control of a numerically controlled machine tool is proposed, in which, in addition to the NC control device, another control device or operating device is provided, which extends the operation or control of the machine tool operator relative to the functions of the NC control device.

[0005] Tool and tool data management in the field of machine tools is currently a huge challenge, especially since there are currently a wide variety of ways to bring tools with the corresponding data into contact with the machine. In the case of machine tools, for this purpose, it is particularly necessary to enter the tool data in order to be able to use it in the control, which therefore requires a specific data format. In addition, current pre-set devices are usually designed to be operated by human operators via manufacturer-specific user interfaces. The precise operating steps, names and data presentation vary from manufacturer to manufacturer. There is no corresponding API here. Due to these obstacles, automation in machine tool controls also represents a core issue, especially with regard to the processing of tool data. However, tool data that is as precise as possible is indispensable for modern manufacturing processes in order to be able to use tools and machines efficiently and effectively.

[0006] Therefore, the object of the present invention is to provide a system, device or method, through which the operation or control of a machine tool can be expanded and improved, especially in terms of the operability of machine tool automation, so as to achieve efficient manufacturing of workpieces by the machine tool. Summary of the invention

[0007] To achieve the above-mentioned object, a method for processing tool data on a machine tool is proposed according to claim 1 and a system, a device and a method according to the independent claims. The dependent claims relate to preferred and particularly advantageous exemplary embodiments.

[0008] According to a preferred embodiment, the following is proposed: A method for processing tool data on a machine tool (in particular on a control device of a machine tool) having a data interface for connecting to a tool management system. The method steps specifically include: obtaining a unique tool identifier (hereinafter referred to as "WID") of the tool to be picked up, and then matching the obtained WID with previously known tool identification data of the machine tool. If it is determined that the tool to be picked up is not yet known and / or updated tool data for the WID is available, the tool data based on the obtained WID are first automatically retrieved directly (preferably directly) from the tool management system via the data interface. Therefore, preferably no manual intervention is required for this purpose. Alternatively, the tool data are automatically retrieved directly (preferably instantly) from the tool to be picked up. Therefore, the tool data are directly available in the WZM controller (e.g. NC control device). In the next step, the loading position of the tool to be picked up is determined based on the retrieved tool data, and the tool is preferably also picked up at the determined loading position. Through this configuration, the necessary (and current) tools and tool data can be automatically and efficiently acquired, and the tool data can be directly used in the production process, thereby significantly improving the efficiency of machine tool utilization, especially the manufacturing efficiency of workpieces. In addition, errors and waiting time in tool acquisition / input can be reduced or completely avoided.

[0009] In a preferred exemplary embodiment, obtaining WID also includes scanning the tool identification identifier of the tool to be picked up. In this case, the WID can be a unique identification (e.g., UUID-universally unique identifier), which can globally uniquely identify a specific tool, thereby enabling reliable and rapid acquisition of the tool.

[0010] In a preferred embodiment, the tool management system is an external tool management system for providing data (e.g. data from the cloud), and the data interface is a tool data interface connected to the external tool management system via a network connection. In this case, the term "external" is preferably related to the machine tool, so the external data management system is an externally provided system and is preferably independent of a single machine tool. The tool management system can specifically be a resource management system, in which some or all available tools include master data (e.g. as part of the tool data) and up-to-date documentation about tool data, maintenance status and tool readiness (specific statements about the availability of the tool at any time). In addition, the tool data of the tool management system can include tool history records. The tool history records can indicate all events from planning through the introduction of the tool to the actual work period using the tool. Since these comprehensive tool data are automatically provided by WID, efficient and precise use of the machine tool can be achieved. Providing data through an external tool management system allows data to be provided in a decentralized and flexible manner for different machine tools.

[0011] In a preferred embodiment, the tool data include measured values ​​and / or set values ​​of the tool determined by external means, in particular a presetting, balancing or retraction device. These specific data are particularly advantageous for a more precise use of the tool on the machine tool, wherein the separate provision of the data by automatic data retrieval has the particular advantage that the latest measured values ​​and / or set values ​​of the tool actually to be replaced are automatically available on the machine tool and the production sequence can be designed efficiently and accurately.

[0012] In a preferred embodiment, the tool required for the machining task is compared with the already existing tools in order to create a difference list, and one or more tools to be replaced can be determined based on the difference list. In this advanced embodiment, not only is the specific tool data retrieved automatically, but also the tool required for a specific production task or machining task is automatically determined. The machining task can specifically be a CNC or NC program for producing one or more components.

[0013] In a preferred exemplary embodiment, the NC program is scanned for the required tool and a corresponding difference list is preferably created. In this further embodiment, not only is the specific tool data automatically retrieved, but also the tool required for a specific production task or machining task is automatically determined. The machining task may specifically be a CNC or NC program for producing one or more components.

[0014] In a preferred exemplary embodiment, a predetermined setting position of the tool to be replaced is determined. In this further embodiment, not only is the specific tool data automatically retrieved, but also the optimal setting position of the tool to be replaced (which is still necessary for performing a specific production task or machining task and still has to be replaced on the machine tool or tool magazine) is automatically determined.

[0015] In a preferred exemplary embodiment, the setting sequence of the tool is also determined according to the processing task, so as to determine the loading position of the tool according to the processing task. In this further embodiment, not only the specific tool data is automatically retrieved, but also the optimal setting position of all required tools will be automatically determined.

[0016] In a preferred embodiment, previously known tool identification data is stored in a memory on the machine tool, in particular in an internal memory of the machine tool or a machine tool controller. Therefore, data can be quickly retrieved during the production process and the production sequence can be designed efficiently and accurately.

[0017] In a preferred embodiment, the WID and / or tool data are directly attached to the tool or tool holder in a machine-readable manner so that the WID and / or tool data can be retrieved by scanning. Thus, data can be quickly retrieved during the production process and production sequences can be designed efficiently and accurately.

[0018] In a preferred embodiment, the tool data is stored in at least one of the following ways:

[0019] Tool data and / or WID are stored in a database;

[0020] The tool data and / or WID are permanently attached to the tool, in particular as an engraved code or a printed QR code;

[0021] The tool data and / or WID are temporarily stored on the tool, in particular as a printed sticker; and / or

[0022] The tool data and / or the WID are stored on a data carrier associated with the tool, in particular an RFID chip.

[0023] This allows data from the production process to be quickly retrieved and production sequences to be designed efficiently and accurately.

[0024] In a preferred exemplary embodiment, the two-dimensional code is a data matrix code or a two-dimensional code.

[0025] In a preferred exemplary embodiment, the tool data are retrieved via a direct data connection so that the tool data arrive directly at the machine tool and are directly available for further processing, wherein the tool data are preferably stored on the machine tool side after retrieval and used to perform the machining task. As a result, data in the production process can be retrieved very quickly and reliably, and production sequences can be designed efficiently and precisely.

[0026] In a preferred exemplary embodiment, the data interface is a tool data interface corresponding to OPC UA (Open Platform Communications Unified Architecture), and the interface comprises an OPC UA server. This allows particularly flexible use and efficient data retrieval.

[0027] In a preferred exemplary embodiment, the UPC UA is used for communication with a tool management system, in particular for retrieving tool data, thereby enabling particularly flexible use and efficient data retrieval.

[0028] In a preferred exemplary embodiment, the tool data are retrieved from the OPC UA server by an OPC UA client as an OPC UA service call, thereby enabling particularly flexible use and efficient data retrieval.

[0029] In a preferred exemplary embodiment, the tool data are converted after retrieval into an input format (standardized input format) which is predefined according to the machine tool controller used. This enables particularly flexible use and efficient data retrieval.

[0030] In a further advantageous aspect, the following is proposed:

[0031] A computer program product comprising instructions which, when executed by a control device of a numerically controlled machine tool, cause the machine tool to carry out a method according to at least one of the preceding features.

[0032] The control device of the machine tool has a data interface for connecting to a tool management system and an application-based control system. The control device can be configured to: obtain a unique tool identifier (hereinafter referred to as "WID") of the tool to be picked up, and then match the obtained WID with previously known tool identification data of the machine tool. If it is determined that the tool to be picked up has not yet been determined and / or updated tool data for the WID is available, the tool data based on the obtained WID is first automatically retrieved directly from the tool management system via the data interface. Alternatively, the tool data is automatically retrieved directly from the tool to be picked up. In the next step, the loading position of the tool to be picked up is determined based on the retrieved tool data, and preferably, the tool is also picked up at the determined loading position.

[0033] The data interface of the control device is a tool data interface corresponding to OPC UA (Open Platform Communications Unified Architecture), wherein the interface includes an OPC UA server.

[0034] Tool and tool data management in the machine tool sector currently represents a huge challenge, especially since there are currently a wide variety of ways in which tools come into contact with the machine. For this reason, in the machine tool sector, it is particularly necessary to input tool data and be able to use it in the control, so specific data formats exist. For this purpose, different data formats are relevant, such as CNC or PLC.

[0035] In addition to the actual tool, tool manufacturers also provide presetting devices and tool controllers, via which setpoints, tolerance ranges and actual values ​​of the respective tool can be determined or output. In this case, these presetting devices are designed to be operated by an operator via a manufacturer-specific user interface. The precise operating steps, names and data presentation vary from manufacturer to manufacturer. There is no corresponding API here; only the generic OPC UA protocol is supported for computer-implemented drives. This OPC UA protocol is based on low-level instructions close to the hardware, so that driving via this protocol represents a complex goal in practice that cannot be easily solved at present. This applies in particular to the case where the device is driven by a foreign manufacturer with proprietary hardware. Therefore, a particularly advantageous aspect in this case is the standardized input format, which represents a solution to the above-mentioned data and format conversion problem.

[0036] According to another preferred embodiment according to at least one of the features, the following is additionally proposed: an operating device for a numerically controlled machine tool, having a data processing device, which is specifically configured to execute control and operator control applications, a control interface, via which the data processing device can be communicatively connected to a control device of the machine tool, and / or a user interface, which is configured to accept input information based on an operator control input of an operator of the machine tool and transmit the input information to the data processing device and / or output output information transmitted by the data processing device to the operator. If it is determined that the tool to be picked up has not yet been determined and / or updated tool data of the WID are available, the tool data based on the acquired WID are first automatically retrieved directly (preferably instantly) from the tool management system via the data interface. Therefore, preferably, manual intervention (performed by the operator) for this purpose is no longer necessary. Alternatively, the tool data are automatically retrieved directly (preferably instantly) from the tool to be picked up. In a next step, the loading position of the tool to be picked up is determined based on the retrieved tool data, and preferably, the tool is also picked up at the determined loading position. Thanks to this configuration, the necessary (and current) tools and tool data can be automatically and efficiently acquired, which can be directly used in the production process, thus significantly improving the efficiency of machine tool utilization and, in particular, the efficiency of workpiece manufacturing. In addition, errors and waiting times in tool acquisition / input can be reduced or completely avoided.

[0037] In a preferred exemplary embodiment, the data processing device is configured to control a machining task for machining one or more workpieces on a machine tool based on a machining step sequence (in particular a machining step sequence that can be selected by an operator via a user interface) and / or to call a corresponding machine or control function on a control device via a control interface. The setting sequence of the tools is determined according to the machining task, and thus the loading position of the tools is determined according to the machining task. In this embodiment, not only is the specific tool data automatically retrieved, but also the optimal setting position of all required tools is automatically determined.

[0038] In a preferred exemplary embodiment, the data processing device is configured to control the processing task on the basis of processing step sequence data which are stored in a data storage device of the operating device and assigned to the processing step sequence.

[0039] In a preferred exemplary embodiment, the process step sequence data specifies a plurality of process steps and / or a predetermined sequence of a plurality of process steps.

[0040] In a preferred exemplary embodiment, the plurality of processing steps comprises at least one or more of the following steps:

[0041] Accepts processing tasks assigned to a sequence of processing steps,

[0042] Set up or prepare one or more clamping devices required for the machining task on the machine tool,

[0043] Set up one or more tools required for the machining task on the machine tool,

[0044] Load or prepare one or more tools required for a machining task on a machine tool,

[0045] loading and / or programming one or more NC codes, NC programs and / or NC program segments required for the machining task,

[0046] One or more NC codes, NC programs and / or NC program segments required to perform a machining task,

[0047] Execute process monitoring applications,

[0048] Record one or more machining processes assigned to a machining task,

[0049] Automatic quality inspection of one or more machined parts, and / or

[0050] Output processing tasks.

[0051] In a preferred exemplary embodiment, the plurality of processing steps comprises at least one or more of the following steps:

[0052] Automatic assembly of workpiece pallets,

[0053] Automatic loading of workpiece pallets,

[0054] Automatic re-arrangement of workpieces onto workpiece pallets,

[0055] Adjust the clamping position of the workpiece,

[0056] Changing from one clamping position to another,

[0057] Automatically measure workpieces,

[0058] Automatic loading of tool magazines for machine tools,

[0059] Automatically set tools on machine tools,

[0060] Automatically reorganize tools in the tool magazine, and / or

[0061] Perform one or more cleaning, maintenance, servicing and / or service applications on a machine tool.

[0062] In a preferred exemplary embodiment, the process step sequence data specifies an assigned process step application for each process step in the process step sequence. Preferably, the data processing device is configured to execute the respectively assigned process step application in order to control the process steps.

[0063] In a preferred exemplary embodiment, the operating device further comprises a network interface configured to connect the operating device to one or more servers via a communication network.

[0064] In a preferred exemplary embodiment, when at least one server provides for executing a processing step application as a web application according to a client-server communication, the data processing device is configured to execute the assigned processing step application as a web application according to a client-server communication with at least one server via a network interface to control the processing step. The latter can also determine the setting sequence of the tools according to the processing task and thus the loading position of the tools according to the processing task. In this embodiment, not only the specific tool data is automatically retrieved, but also the optimal setting position of all required tools will be automatically determined.

[0065] In a preferred exemplary embodiment, the data processing device is configured to automatically retrieve from an external tool management system the input information required for the processing step application and / or the required tool data for executing the processing steps assigned to the processing step sequence.

[0066] Preferably, the data processing device is configured to automatically retrieve or load from one or more servers via a network interface input data and / or tool data required for executing a processing step application assigned to a processing step sequence.

[0067] Preferably, the input data includes one or more of the following data:

[0068] model data representing a CAD model of one or more workpieces, one or more workpiece components and / or one or more tools,

[0069] NC data, the NC data representing one or more NC codes, one or more NC programs and / or one or more NC program segments,

[0070] Order data, which indicates the order data assigned to the workpiece processing,

[0071] tool data, which represent information about one or more assigned tools,

[0072] Tool list data, which represents a list of tools assigned to a machining task or workpiece machining,

[0073] Clamping device data, which represents information about one or more assigned clamping devices, and / or

[0074] Clamping device list data, which represents a list of clamping devices assigned to a machining task or workpiece machining.

[0075] In a preferred exemplary embodiment, the data processing device is configured to check or confirm before executing the process step sequence whether there are input data required for each process step application respectively assigned to the process step, in particular input by an operator, by the presence of loadable input data and / or by output data of the process step application to be executed in advance.

[0076] A control device for a numerically controlled machine tool, comprising a control device for controlling machine functions of the machine tool and an operating device according to one of the preceding aspects, which is connected or connectable to the control device and / or a machine tool having such a control device.

[0077] Further aspects and advantages thereof as well as advantages of the above-described aspects and features and more specific possible embodiments are described from the following description and illustrations related to the accompanying drawings, which description and illustrations should not be construed as limiting in any way. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 A schematic diagram of a system for operating and controlling one or more CNC machine tools according to an exemplary embodiment of the present invention is shown.

[0079] Figure 2 A schematic diagram of a method according to an exemplary embodiment of the present invention is shown.

[0080] Figure 3 Various abstraction levels from a graphical interface seen by an operator through a backend and through standardization of data structures to input devices from a number of different manufacturers according to at least one exemplary embodiment of the present invention are schematically illustrated.

[0081] Figure 4 An example of tool data exchange between a machine tool WZM and a tool presetting device WV via the OPC UA protocol according to at least one exemplary embodiment of the present invention is shown.

[0082] Figure 5 An example of tool data exchange through an interface provided by OPC UA according to at least one exemplary embodiment of the present invention is shown.

[0083] Figure 6 An example of a sequential selection screen of a graphical user interface of a user interface of a machine tool operating device according to at least one exemplary embodiment of the present invention is shown.

[0084] Figure 7 An example of a tool inspection screen of a graphical user interface of a user interface of a machine tool operating device according to at least one exemplary embodiment of the present invention is shown.

[0085] Figure 8 An example of a tool loading screen of a graphical user interface of a user interface of a machine tool operating device according to at least one exemplary embodiment of the present invention is shown.

[0086] Fig. 9 An example of a portion of an input format API specification according to at least one exemplary embodiment of the present invention is shown.

[0087] Fig.10 A portion of different specifications of the input format and manufacturer format required for controlling tool controls and presetting devices is shown by way of example. Based on the shown lookup table, the formats can be converted into one another according to at least one exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0088] Below will be described in detail examples or exemplary embodiments of the present invention with reference to the accompanying drawings. In this case, the same or similar elements in the figures may be represented by the same reference numerals, but may also be represented by different reference numerals at times.

[0089] It should be emphasized that the present invention is not in any way limited or restricted to the exemplary embodiments described below and their exemplary embodiment features, but also includes modifications of the exemplary embodiments, in particular modifications consisting of modifications of the features of the embodiments or consisting of a combination of single or multiple features of the embodiments, within the scope of protection of the independent claims.

[0090] Tool and tool data management in the machine tool sector is currently a huge challenge, especially since there are currently a wide variety of ways to bring tools and their data into contact with the machine tool for use. On the machine tool side, for this purpose, it is usually necessary to enter the tool data so that it can be used in the WZM controller, and therefore a specific data format for the tool data is usually also required. This is usually determined by the WZM controller. In addition, the preset devices for setting or measuring the tool are designed to be operated by the operator via a manufacturer-specific user interface. The precise operating steps, names and data presentation vary from manufacturer to manufacturer. There is no corresponding API here. Due to these different obstacles, automation in the machine tool controller currently represents a core issue related to tool data.

[0091] It is therefore advantageously proposed to connect the entire WZM system directly to other data management systems outside the machine tool via a tool management application on the WZM controller (e.g. "Tool Master") in combination with special processing and provision of tool data (e.g. "Tool Data Exchange"), so that tool data present, for example, in a tool measuring device can be acquired and loaded directly into the WZM (or WZM controller or NC control) by identifying the tool on the machine, so that the workflow and tool handling can be jointly and automatically negotiated via the tool data exchange application of the WZM controller.

[0092] For this purpose, a direct data connection is particularly advantageously proposed, i.e. data can be exchanged directly via the interface, but the tool data can also be present in the cloud, so that when a tool is selected on the WZM control, the tool data reaches the machine directly and is therefore directly available in the WZM.

[0093] To explain the underlying system design, we first describe the arrangement and connectivity of the WZM in a specific network. Figure 1 A schematic illustration of a system for operating and controlling one or more numerically controlled machine tools according to an exemplary embodiment of the present invention is shown.

[0094] according to Figure 1 The system includes, for example, a network server 110, which is connected to a communication network 100, such as the Internet, a cloud service network, or a local network.

[0095] In addition, according to Figure 1 The system includes, for example, a database server 210 and a CAD / CAM system server 220. The CAD / CAM system server 220 is, for example, connected to a communication network 200, which is preferably a local network (eg, a local area network, a wireless local area network, etc.).

[0096] For example, Figure 1The communication network 200 in FIG. 1 is connected to the communication network 100 , wherein, for example, a firewall (dashed line) is provided between the communication network 100 and the communication network 200 .

[0097] according to Figure 1 The system also includes, for example, a numerically controlled machine tool 250A (e.g., a milling machine, a universal milling machine, a machining center, a milling machine / lathe, a lathe, a turning center, a grinding machine, a gear cutting machine, an application machine for additive manufacturing, etc.), the NC control device 240A being assigned to the machine tool 250A and connected to the machine tool 250A, or preferably connected to controllable actuators and sensors of the machine tool 250A, and configured to control the machine tool 250A or functions of the machine tool 250A. The control device 240A can, for example, be integrated on the machine tool 250A.

[0098] In addition, according to Figure 1 The system includes, for example, an operating device 230A, which is assigned to a machine tool 250A and connected to a control device 240A assigned to the machine tool 250A. The operating device 230A is also, for example, connected to a communication network 200. For example, the operating device 230A is configured to communicate with a database server 210 and a CAD / CAM system server 220 through the communication network 200.

[0099] Furthermore, the operating device 230A is also configured to communicate with the network server 110 through the communication network 200 and the communication network 100 , for example.

[0100] For example, according to Figure 1 The system also includes further CNC machine tools 250B and 250C, which have correspondingly assigned control devices 240B and 240C, respectively, and correspondingly assigned operating devices 230B and 230C, respectively.

[0101] By way of example, the operating device 230A is configured to communicate with the operating devices 230B and 230C of the respective machine tools 250B and 250C via the communication network 200 , and by way of example, vice versa.

[0102] In addition, according to Figure 1 The system comprises, for example, a separate operating device 260 (eg, a user computer, such as a laptop, desktop, tablet or smartphone) connected to the communication network 200.

[0103] In addition, according to Figure 1 The system comprises, for example, an external device WV suitable for providing and / or determining tool data, such as a preset, balancing or retraction device. In this case, the external device WV is connected to the communication network 200 .

[0104] The operating device 230 may be formed or provided by a computer (eg, a front-end PC integrated in a machine tool operating console or in the machine tool).

[0105] Furthermore, the operating device 230 comprises, for example, a user interface 233 , TM UI or front end, and a network interface for establishing a communication connection with the network 200 or the network 100 .

[0106] The TM UI or the front end is preferably a graphical user interface 233 (GUI) for the operator (e.g., including output functions through a screen and input functions through input devices, such as a mouse, a keyboard, one or more touch screens implemented on a screen, soft keys, knobs, knobs and / or buttons, etc., and possibly output functions through other output devices, such as LED information fields, lights, illumination lights, warning lights, audio outputs, etc.).

[0107] In terms of hardware, in an exemplary embodiment, the control device 240 may be formed, for example, on a computer, for example, on the same computer as the operating device 230. Alternatively, the control device 240 may be implemented on its own computer, for example, on a backend PC of a machine tool, which may be integrated in the machine tool, for example.

[0108] For example, the network server 110 is configured to provide network-based data or network-based applications through the network 100, and execute the network-based data or network-based applications upon request, such as by one or more operating devices 230 or 260, and transmit corresponding data to the requesting operating device 230 or 260 through the network 100 and the network 200.

[0109] For example, the operating device 260 may be formed as a computer comprising operating device software similar to that of the operating device 230 and optionally one or more CAD / CAM software applications.

[0110] Figure 2A schematic example diagram of a method for processing tool data on a machine tool WZM having a data interface for connecting to a tool management system is shown. The method steps include: obtaining a unique tool identifier (hereinafter referred to as "WID") of the tool WZ to be picked up, and then matching the obtained WID with previously known tool identification data of the machine tool WZM. If it is determined that the tool WZ to be picked up is not yet known to the WZM and / or updated tool data of the WID are available, the tool data (or updated tool data) based on the obtained WID are first automatically retrieved directly from the tool management system via the data interface. Alternatively, the tool data (or updated tool data) are automatically retrieved directly from the tool WZ to be picked up. In the next step, the loading position of the tool WZ to be picked up is determined based on the retrieved tool data, and preferably, the tool WZ is also picked up at the determined loading position.

[0111] The standardization of the measured tool data is preferably performed by means of a standardized input format, which can be converted into the manufacturer formats of all supported manufacturers and vice versa. Thus, requests and responses to manufacturer-specific preset devices WV can be mapped independently of the manufacturer. The control program for controlling the machine tool can then use the data in the standardized input format in a next step. In particular, tool data measured using different preset devices can also be compared with one another.

[0112] In addition to the actual tools, tool manufacturers (e.g. S1, S2, S3) also provide preset devices and tool controllers, through which the set values, tolerance ranges and actual values ​​of the corresponding tools can be determined or output. In this case, these preset devices are designed to be operated by the operator via a manufacturer-specific user interface. The precise operating steps, names and data presentation vary from manufacturer to manufacturer. There is no corresponding API here; for computer-implemented drives, only M2M protocols such as MQTT, MTConnect, AMQP are supported, and the universal OPC UA protocol is particularly advantageously supported. The OPC UA protocol is based on low-level instructions close to the hardware, so driving via this protocol represents a complex goal in practice, and therefore also requires special qualifications for the operator. This applies in particular to the case where the device is driven by a foreign manufacturer with proprietary hardware. In the present embodiment, the standardized input format represents a solution to this complex goal.

[0113] An exemplary data transmission is carried out via a network query via a tool data interface, which tool management system is preferably located externally and provides data via a network connection from a cloud, such as the communication network 100 and / or the communication network 200. Upon request, the tool management system provides tool data to a device connected to the communication network 100 or 200, such as a machine tool WZM or a machine tool 250A; 250B; 250C, an operating device 230A; 230B; 230C, an NC control device 240A; 240B; 240C or a tool presetting device WV, see Figure 1 Optionally, the tool management system can process further requests via the communication network 100 or 200, see Figure 5 .

[0114] The data interface of the control device 240 is, for example, a tool data interface corresponding to UPC UA (Open Platform Communications Unified Architecture), wherein the interface includes an OPC UA server. Similarly, for example, UPC UA is used to communicate with a tool management system, in particular for retrieving tool data. Furthermore, for example, tool data is retrieved from the OPC UA server by an OPC UA client as an OPC UA service call.

[0115] Preferably, after being retrieved (on the machine tool controller side), the tool data are converted into an input format which is predefined according to the machine tool controller used.

[0116] For example, during the scanning S, the WID is acquired and the tool identification identifier of the tool WZ to be picked up is scanned. For this purpose, the machine tool WZ comprises, for example, a scanning device (integrated or connected to the machine tool WZ) for acquiring the coded information, making it particularly suitable for further data processing on at least one digital device. The coding can be, for example, a barcode, a QR code or an RFID chip. This type of coding is particularly suitable if the corresponding information is directly attached to the tool, in particular the tool WZ, and is, for example, related to the management, handling, positioning, identification and / or description of the tool. According to an exemplary application, the information can be attached directly to the tool, in particular the tool WZ, wherein the information is preferably attached to the tool by laser engraving, or alternatively a sticker is printed and correspondingly glued to the tool. Optionally, this process is also possible for workpieces inserted into the WZM. Therefore, after scanning the ID of the workpiece, the workpiece management system (for example a cloud-based workpiece management system) can automatically retrieve the data of the workpiece by automatic retrieval.

[0117] The acquisition of information by means of a scanning device has advantages over conventional methods, in which the acquisition of information is carried out with manual intervention, for example by an operator of the WZM. As is known from the prior art, in conventional methods the operator has to manually read the information from the tool and has to manually enter this information on the WZM controller. In this case, transmission errors can occur, which can be minimized or eliminated by automated methods (e.g. during scanning S). In addition, the acquisition of information by a scanning device requires less time and is therefore particularly suitable for time-optimized work.

[0118] The tool data include measured values ​​and / or set values ​​of the tool WZ determined by external devices, in particular a tool presetting device WV, a balancing device or a shrinking device.

[0119] The data stored in the input format include, among other things, tool data. The tool data include measurement data of the presetting device WV and possibly other data relating to tool properties that are not captured by the presetting device WV. The measurement data may include, among other things:

[0120] ·length

[0121] ·thickness

[0122] ·weight

[0123] Tolerance range

[0124] The amount of free space required in the tool magazine

[0125] ·count.

[0126] Further data relating to additional tool properties may include, among other things:

[0127] Acquisition date

[0128] Tool History

[0129] Number of times used

[0130] The last job using the tool

[0131] ·count.

[0132] Furthermore, the data stored in the input format include, among other things, a WID. The WID is described based on a unique ID, for example based on a unique device identification (UDI). In order to ensure the uniqueness of the ID across the entire application, a central server, for example a UDI server, can be used to assign the ID. In particular, in the case of a UDI, a global UDI server is used which issues unique IDs worldwide, see also Figure 5 .

[0133] For example, previously known tool identification data are stored in a memory on the machine tool, in particular in an internal memory of the machine tool or of a machine tool controller. Furthermore, the WID and / or the tool data can be attached directly to the tool WZ or the tool holder WZH in a machine-readable manner, for example, in order to be retrieved by the method step of scanning S. In particular, the tool data and / or the WID can be attached in a machine-readable manner as follows:

[0134] Stored in a database (e.g. in the cloud or on an external server);

[0135] Permanently attached to the tool WZ, in particular as an engraved code or printed QR code;

[0136] Temporary storage on the tool WZ, in particular as a printed sticker, wherein the sticker is preferably printed with a QR code; and / or

[0137] • On a data carrier associated with the tool WZ (eg attached to the tool), in particular an RFID chip.

[0138] The data are preferably physically attached directly to the respective tool WZ. This offers the advantage that the data are always accessible when the tool WZ is accessible. Codings designed specifically for reading by digital means are particularly advantageous. These include in particular optical codings, such as two-dimensional codes. For this purpose, the invention supports the reading of both data matrix code codings and QR code codings.

[0139] Another variant of attaching information directly to the tool WZ is to write to an RFID chip that is directly integrated into the tool WZ. This variant is superior to databases because they are attached directly to the tool in a manner similar to a QR code.

[0140] Permanent data storage on the tool by laser engraving is superior to conventional methods, in which the information attachment is attached to the tool in such a way that the corresponding information can be separated from the tool or that the corresponding information becomes incorrect over time or due to expected external influences. Engraving has advantages over sticking stickers engraved with the relevant information. The adhesive surface of the sticker can lose its adhesiveness over time or due to external influences, so that the sticker is lost and the relevant information is no longer assigned to the tool WZ. Likewise, the material of the sticker or the colorant used for the engraving can be damaged during normal operation, so that the relevant information can only be assigned partially or incorrectly to the tool WZ.

[0141] For example, tool data are retrieved via a direct data connection so that they reach the machine tool WZM or WZ directly and can be further processed directly there, wherein the tool data are preferably stored on the machine tool side after retrieval and used to execute the machining task.

[0142] For example, the NC program is scanned for the required tools, such as WZ1, WZ2, WZ3 and WZ4, and a difference list is preferably created. The difference list is created by comparing the tools required for the machining task with the already existing tools (such as WZ1 and WZ2). Subsequently, one or more tools to be replaced, such as WZ3 and WZ4, are determined based on the difference list. The predetermined setting positions for the replacement are determined for the determined tools (such as WZ3 and WZ4). In this case, the setting order of the tools is determined according to the machining task so that the loading positions of the tools are determined according to the machining task. See also Figure 7 .

[0143] The first step in the loading process is, for example, to find a free space in a machine tool WZM, wherein the machine tool WZM comprises, for example, a tool magazine into which a tool can be loaded. For this purpose, the required size of the tool to be loaded is determined, among other things, based on the data stored in the input format. Subsequently, a correspondingly large free space is searched for. If no such space is found in the machine tool WZM or the tool magazine, an error message is output to explain the problem. Otherwise, the machine tool WZM or the tool magazine is brought into position for loading in the corresponding free space.

[0144] In the next step, the tool cover of the machine WZM or the tool magazine is opened and instructions are output on how to load the machine WZM or the tool magazine. Loading can also be performed in an automated manner. In the automated method, it is now necessary to wait for the tool cover to be closed again. At this point, the corresponding tool must be loaded into the free space of the machine WZM or the tool magazine. This can be done manually by the operator or in an automated manner by an external system. By closing the tool cover, a signal is given that the tool (e.g. WZ2 or WZ4) has been loaded and the loading process can continue.

[0145] As a final step, it is checked (optionally) whether the tool has been correctly loaded. If the check result is negative, a corresponding error message is output to explain the problem. If the check result is positive, the loading process for this tool is considered to be completed and the next method step is executed. The next method step is, for example, the loading process of another tool or the automatic execution of a machining task.

[0146] If the difference list is empty, the machining task is automatically executed. Otherwise, one of the missing tools is selected in the difference list and its tool and identification data are retrieved in input format. When selecting the tools to be set from the difference list, it is best to maintain a defined setting sequence. Based on these data, the loading process for the tool is started. After the loading process has been successfully completed, the entry for the loaded tool is deleted from the missing tool list and added to the existing tool list. This step is repeated until all missing tools have been loaded into the difference list and the command is executed.

[0147] For automatic loading, the computer program product can directly use the data in the input format, since the tool data contain, among other things, all the information required for loading, such as the amount of space to be occupied in the tool magazine.

[0148] Figure 3 Various abstraction levels from a graphical user interface 233 seen by an operator through a backend and further through standardization of data structures to input devices (eg, S1, S2, and S3) from multiple different manufacturers according to an exemplary embodiment of the present invention are schematically illustrated.

[0149] The TM UI or front end is preferably a graphical user interface 233 (GUI) for an operator (e.g., including output functionality through a screen having at least one screen area 233A, and input functionality through input devices, such as a mouse, keyboard, one or more touch screens implemented on the screen, soft keys, knobs, knobs and / or buttons, etc., and possibly output functionality through other output devices, such as LED information fields, lights, illumination lights, warning lights, audio outputs, etc.).

[0150] The TM backend preferably corresponds to a tool management system. In this case, the TM frontend of the machine tool is connected to the tool management system via a data interface. In particular, tool data based on the acquired WID can be automatically retrieved directly from the tool management system via the data interface. The data is present in an input format.

[0151] The system for standardizing data structures preferably corresponds to conversion from at least one manufacturer format or from the OPC UA protocol to a standardized input format, or corresponds to conversion of a standardized input format to at least one manufacturer format or the OPC UA protocol. The manufacturer devices S1; S2; and S3 can be used to communicate in the corresponding manufacturer format or via the OPC UA protocol.

[0152] Figure 4 By way of example, the exchange of tool data between a machine tool WZM and a tool presetting device WV via the OPC UA protocol is schematically shown.

[0153] The tool data is present on the tool presetting device WV and is uniquely identified with the tool holder WZH by, for example, a QR code. During the method step of scanning S, the tool WZ is scanned at the scanner and identified. The data of the tool WZ are then written from the database in the presetting device WV to the tool table of the machine tool via the OPC UA interface. The central database can be located, for example, in the tool presetting device WV.

[0154] Figure 5The tool data exchange as an interface provided by OPC UA is schematically shown by way of example. In particular, the figure shows the connection of a control adapter as part of a control IP to a preferably external tool management system. The connection is made via an edge IPC comprising a universal machine adapter and an OPC UA server. In general, there is a connection between the control adapter and the universal machine adapter, between the universal machine adapter and the OPC UA server, and between the OPC UA server and the preferably external tool management system. Specifically, the control adapter can exist, for example, as a PLC / NC agent, wherein the universal machine adapter exists as machine communication X. Alternatively, for example, the control adapter can exist, for example, as a UDI server, wherein the universal machine adapter exists as a UDI client.

[0155] If the control adapter exists, for example, as a UDI server and the universal machine adapter exists as a UDI client, the UDI client (if necessary) provides a request to the UDI server to generate a unique WID, which is provided to the tool management system via the OPC UA server. In this case, the UDI server ensures that the assigned WID is actually globally unique.

[0156] Figure 6 An order selection screen of a graphical user interface of a user interface 233 of an operating device 230 of a machine tool 250 is schematically shown by way of example.

[0157] By way of example, order selection elements B1 to B5 are provided, by which the operator can select orders 1 to 5. Preferably, only operators with sufficient authorization can select the corresponding order according to the order on the operating device 230. This can be done, for example, by different user roles according to the operator's abilities or training, for example by user roles: simple machine operator, experienced machine operator, machine loader, setter, machine programmer, machine maintenance provider, multi-machine operator, tool presetter, job preparer, factory planner, process standardizer, etc.

[0158] The selection element B6 allows, for example, to start an editor application on the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250 to execute a processing step sequence editor. The editor application is configured to list the processing step applications provided on the network server 110 and import these processing step applications when the operator selects them. The operator can also determine or define the order of the imported processing step applications and store predefined processing step sequences. This editor function is preferably only available to operators with specific authorization.

[0159] The editor preferably indicates for each machining step which input data or input information the application needs or automatically retrieves, which output data or output information it provides and / or which control functions of the machine tool it calls up.

[0160] In a preferred embodiment, when storing the edited sequence of processing steps, an automatic plausibility check can be performed, wherein it is checked in an automatic manner whether the input data required for each processing step application are available (data availability check), which can be obtained by manual entry in the editor, by providing output data of the previous processing step application in a predefined sequence, from a storage device of the operating device, from a control device, from a PLC register, or by accessing database data on the database server 210 and / or the CAD / CAM system server 220. The required data can also include tool data, in particular tool data measurement values ​​and / or tool setting values ​​determined by external devices, in particular presetting devices, balancing devices or shrinking devices. These specific data are particularly conducive to a more accurate use of the tool on the machine tool, wherein the separate provision of the data by automatic data retrieval has the particular advantage that the latest measurement values ​​and / or setting values ​​of the tool actually to be replaced are automatically available on the machine tool and the production sequence can be designed efficiently and accurately.

[0161] In particular, data availability is preferably checked not only when storing an edited or created process step sequence, but also when linking a new job to a process step sequence or when starting a process step sequence linked to a job or optionally during (or before, respectively) the execution of the corresponding process step application.

[0162] When the operator executes a predefined sequence of machining steps on the operating device 230, preferably only each machining step application can be called up and executed, the sequence being predefined by the stored or imported machining step sequence, and in particular no machining step application can be skipped. It is particularly advantageous if the tool data is only retrieved when the tool is actually required in the next machining step in the sequence during machining. Thus, the tool data is only retrieved in a timely manner according to the just-in-time principle, which can reduce the memory load and computing power of the controller. Optionally, the tool data can be deleted again on the WZM controller after the last use of the tool in the machining process, and the tool data are only automatically retrieved from the external tool management system when the tool is used again.

[0163] The WZM particularly advantageously provides the external tool management system with detailed feedback on the usage of (each) tool (duration and extent of use, e.g. operating temperature, applied forces, exceeded limit values, etc.) so that the tool history in the external tool management system is always up-to-date and the tool is always linked to the latest tool data even when switching to another WZM.

[0164] The operator triggers the execution of the predefined sequence of processing steps assigned to the order on the operating device 230 by selecting one of the order selection elements B1 to B5 assigned to the corresponding processing task, at least if his authorization allows it.

[0165] When the operator starts the corresponding processing step application, a new window of the corresponding processing step application can be opened and a validity check (eg, including a data availability check) can be performed. In addition, the machine function assigned to the corresponding processing step application can be performed.

[0166] Furthermore, in a preferred exemplary embodiment, a screen presentation assigned to each processing step or a control menu assigned to each processing step can be automatically called on another screen area (e.g., screen area 233B of the control screen of the display control device 240). This can be requested or automatically set by the TM UI or the front end.

[0167] The first processing step application (eg, "accept order") may indicate to the operator order header data, for example, order data based on the order to be executed, wherein the assigned order file is imported by the database server 210.

[0168] By confirming the processing step application (e.g., "accepting the order"), the order can be set to the "execution" status. This can also be automatically reported to the production monitoring system via the network 200.

[0169] Another (optional) machining step application may involve tool loading or tool requirement checking, see Figure 7 .

[0170] The order data of an order file (e.g. an order database) assigned to the respective workpiece machining task may indicate, for example, one or more of the following header data: name of the work operation, order identification number, order description, workpiece identification number, workpiece description, setup identification number assigned to the order, assigned customer identification number, work plan identification number, indication of the required or to-be-realized workpiece number (i.e., the quantity to be manufactured, e.g. in the case of consecutive machining of multiple workpieces in the same workpiece machining task), planned start time, planned end time, planned or calculated machining duration, and optional free text field information. Such data may also be provided from an ERP or MES system.

[0171] The data storage device of the database server 210 optionally stores, for example, multiple tool files (e.g., a tool database), each tool file providing or indicating information about a specified tool, such as one or more of the following: tool dimensions (size, diameter, length, cutting edge type, cutting edge number, etc.), tool type, tool identification number, etc.

[0172] Figure 7 A tool inspection screen of a graphical user interface of user interface 233 of operating device 230 of machine tool 250 is schematically shown by way of example.

[0173] In this case, the required tools are indicated (for example, based on a tool list file assigned to the order to be executed), such as WZ1, WZ2, WZ3 and WZ4. In addition, based on the data present on the operating device, the tools present on the machine tool WZ, such as WZ1 and WZ3, and the tools still missing or still to be loaded, such as WZ2 and WZ4, can be displayed.

[0174] By activating the selection element B7 "Load tool", the operator can move to tool loading in order to load the missing tool if appropriate or to enter the relevant tool data (either importing these from the tool data, if they have been scanned before, or importing these from a tool presetting device connected to the network 200 after scanning the S tool), see e.g. Figure 8 .

[0175] Figure 8 By way of example, a tool loading screen of a graphical user interface of user interface 233 of operating device 230 of machine tool 250 is schematically shown.

[0176] By activating the selection element B8 "Manual input", the operator can scan the missing tools before loading the tool station and then manually enter the data, or by activating the selection element B9 "Import from tool station" import these data from a tool presetting device connected to the network 200. When changing tools, it is particularly advantageous to enter the data in an automated manner during the scanning process, especially without the involvement of an operator.

[0177] Another (optional) application of a machining step may involve the loading or programming of NC codes. In this case, the NC files assigned to the order (e.g., based on the order data of the assigned order file) are indicated and these files can be exported to the control device 240 by activating the corresponding selection element "Load NC files to NC" (if appropriate, after importing the corresponding files from the CAD / CAM system server 220). By selecting the selection element B10 "Edit NC files", the operator can edit (or create a new) the loaded files in the display window located above it, for example, at least if the required authorization for the operator is present.

[0178] After loading the tool, if appropriate, setting the clamping device and providing the NC code in a sequence and manner according to a predefined sequence of processing steps (and, if appropriate, after further predetermined steps), the workpiece processing can be carried out, if appropriate in combination with predetermined process monitoring, subsequent process documentation and, if appropriate, optional quality checks, until the order can be confirmed as completed in the final processing step or executed in an automated manner.

[0179] The WZM particularly advantageously provides the external tool management system with detailed feedback about the usage of (each) tool (usage time and usage range, e.g. operating temperature, applied forces, exceeded limit values, etc.) so that the tool history in the external tool management system is always up-to-date and the tool is always linked to the latest tool data even when switching to another WZM.

[0180] According to one or more of the aforementioned exemplary embodiments, the operation or control of a machine tool can be expanded and improved, in particular with regard to operability or automated or semi-automated support of processing steps of a workpiece processing task, if appropriate also by partially untrained or inexperienced operators.

[0181] Fig. 9 A portion of the API specification that illustrates the input format. For example, the input format exists in JSON format.

[0182] In this case, the "Schema" column indicates the version number of the input format. Using the field "Schema", different versions of the input format can be distinguished. This is particularly advantageous because different versions of the API specification do not have to be compatible with each other.

[0183] Additionally, the "Name" column indicates the name of the field in the input format that can be read, created, overwritten, or deleted.

[0184] Furthermore, the "Type" column indicates the data type of the field in the input format. The data type defines the binary representation or human-readable representation in the input format. Furthermore, the data type defines the parsing used to convert the field.

[0185] Finally, the "Description" column represents a description that can be used by the operator to explain the meaning of the field in the input format.

[0186] Fig.10 An example of a portion of different specifications for the required input format and manufacturer format for controlling tool control and presetting devices is shown. The formats can be converted into one another using the look-up table shown.

[0187] In this case, the "Uniform tool type" column represents the manufacturer-independent tool type designation. It is thus possible to combine equivalent tools from different manufacturers under one term and to assign equivalent fields to one another during conversion between different data formats.

[0188] Furthermore, the next columns represent manufacturers S1; S2; and S3. The columns for the individual manufacturers are further subdivided into "name" (the manufacturer's own tool type name) and "ID" (the cross-manufacturer ID). "name" is unique to a fixed manufacturer, assigned by the manufacturer and used in the manufacturer's format. In contrast, "ID" is defined by the input format and the manufacturer's own name "name", manufacturer S1; S2; or S3, and the manufacturer-agnostic tool type name "Uniform Tool Type" can be uniquely resolved based on the ID.

[0189] In summary, tool and tool data management in the field of machine tools currently represents a very big challenge, especially since there are currently a wide variety of ways to bring tools with data into contact with the machine. In the case of machine tools, for this purpose it is particularly necessary to enter tool data and to be able to use it in the control, so specific data formats exist. Different data formats are relevant for this purpose, such as CNC or PLC.

[0190] CNC refers to a numerical control system that contains one or more microprocessors to perform control functions. The external identifiers of CNC are usually a screen and a keyboard. The numerical control system (CNC) is operated by a CNC program, which contains all the necessary functions such as interpolation, position control and speed control. With the help of one or more microprocessors and the CNC program, CNC part programs related to the workpiece, which are usually specified by the machine user, can be executed.

[0191] A CNC part program consists of an arbitrary number of sets that describe the entire working sequence of the machine for machining a workpiece step by step. Each set in the program represents a geometric machining step and / or a specific machine function. A set can contain different instructions. A distinction is made here between:

[0192] Geometric instructions for controlling the relative motion between the tool and the workpiece;

[0193] Technical instructions for determining feed rate, spindle speed and tool;

[0194] Travel instructions that determine the type of motion, such as rapid movement, linear interpolation, circular interpolation, and plane selection;

[0195] Switching commands for selecting tools, switching worktable positions, and coolant supply;

[0196] Correction calls, e.g. for tool length correction, cutter diameter correction, cutting edge radius correction and zero point shift; and

[0197] · Used for loops and subroutine calls of frequently repeated program segments.

[0198] In addition to the numerical control, CNC program and CNC part program, an adapter program (PLC program) is required for the machine to be controlled, which is created by the machine manufacturer and integrated into the programmable logic controller (PLC). In it, all machine-related links and locks for specific function sequences are defined, e.g. for tool change, workpiece change and axis boundaries.

[0199] To further demarcate the boundary between CNC and PLC, some differences need to be highlighted. CNC part programs for machining workpieces are created by the machine user. CNC part programs can be changed or modified by the user at will. In contrast, PLC programs are created by the machine manufacturer and permanently stored, for example on a ROM (read-only memory). PLC programs only need to be changed or replaced in special cases. In particular, in the case of PLCs, no programming is required during operation. PLC programs must be created for each PLC (Programmable Logic Controller), while for other PLC manufacturers this is not so complicated. Based on this major difference, there can be up to several thousand CNC part programs per machine. CNC part programs are created by the machine user, and canned cycles and subroutines can of course be provided by the manufacturer. With a PLC, there is usually only one fixed, machine-dependent program. This program is created by the machine manufacturer, usually using available function modules.

[0200] Machine tools are equipped according to customer needs. Therefore, service technicians need to find out in advance exactly which software version the customer requires and find the right software for the respective customer, which is very complicated.

[0201] Central components within machine tools, such as PLC and NC, come from different manufacturers. Dependencies among manufacturers, versions, updates and special devices must be managed effectively to ensure that the right software update for the machine is always used.

[0202] It is therefore advantageously proposed to connect the entire WZM system directly to other data management systems outside the machine tool via a tool management application on the WZM controller (e.g. "Tool Master") in combination with special processing and provision of tool data (e.g. "Tool Data Exchange"), so that tool data present, for example, in the tool measuring device can be acquired and loaded directly into the WZM (or WZM controller or NC control) by identifying the tool on the machine tool, so that workflows and tool handling can be jointly and automatically negotiated via the tool data exchange application of the WZM controller.

[0203] The examples or exemplary embodiments of the present invention and their advantages have been described in detail above with reference to the accompanying drawings. It should be emphasized again that the present invention is not limited to or in any way restricted to the above exemplary embodiments and their embodiment features, but also includes modifications of the exemplary embodiments, in particular modifications of the features of the embodiments or modifications consisting of a combination of single or multiple features of the embodiments within the scope of protection of the independent claims.

[0204] List of reference numerals:

[0205] 100: Communication Network

[0206] 110: Network server

[0207] 200: Communication Network

[0208] 210: Database server

[0209] 220: CAD / CAM system server

[0210] 230: Operating device

[0211] 230A; 230B; 230C: first operating device; second operating device; third operating device

[0212] 233: User Interface

[0213] 233A; 233B: first screen area; second screen area

[0214] 240: Control device

[0215] 240A; 240B; 240C: first NC control device; second NC control device; third NC control device

[0216] 250A; 250B; 250C: first machine tool; second machine tool; third machine tool;

[0217] 260: Independent operating device

[0218] B1; B2; B3; B4; B5: Selected element for operation 1; Selected element for operation 2; Selected element for operation 3; Selected element for operation 4; Selected element for operation 5

[0219] B6: Editor application selection element

[0220] B7: Tool loading selection element

[0221] B8: Manual input selection element

[0222] B9: Selected components imported from tool stations

[0223] S: Scan

[0224] S1; S2; S3: Tool control of the first manufacturer, tool control of the second manufacturer, tool control of the third manufacturer

[0225] WV: Preset Device

[0226] WZ: Knife

[0227] WZ1; WZ2; WZ3; WZ4: Tool 1; Tool 2; Tool 3; Tool 4WZH: Tool holder

[0228] WZM: Machine tools

Claims

1. A method for processing tool data on a machine tool, the machine tool having a data interface for connecting to a tool management system, wherein: The method comprises the following steps: Get the unique tool identifier WID of the tool to be picked up; matching the acquired WID with previously known tool identification data of the machine tool; If it is determined that the tool to be picked up has not been determined and / or updated tool data of the WID is available, then: Automatically, through the data interface, directly retrieve tool data from the tool management system based on the acquired WID or automatically directly retrieve the tool data from the tool to be picked up; A loading position of the tool to be picked up is determined based on the retrieved tool data, and preferably, the tool is picked up at the determined loading position.

2. The method according to claim 1, wherein: Acquiring the WID includes scanning a tool identification identifier of the tool to be picked up.

3. The method according to at least one of the preceding claims, wherein: The tool management system is an external tool management system for providing data from a cloud, and the data interface is a tool data interface connected to the external tool management system via a network connection.

4. The method according to at least one of the preceding claims, wherein: The tool data include measured values ​​and / or set values ​​of the tool determined by an external device, in particular a presetting device, a balancing device or a retraction device.

5. The method according to at least one of the preceding claims, wherein: To create a difference list, the tool required for the machining task is compared with the already existing tools, and One or more tools to be replaced are determined based on the difference list.

6. The method according to at least one of the preceding claims, wherein: The method initially comprises the steps of scanning the NC program for the required tools and preferably creating a corresponding difference list.

7. The method according to at least one of the preceding claims, wherein: Determine the intended setup location for the tool to be changed.

8. The method according to at least one of the preceding claims, wherein: The method further determines a setting sequence of the tools according to a machining task, so as to determine the loading positions of the tools according to the machining task.

9. The method according to at least one of the preceding claims, wherein: The previously known tool identification data is stored in a memory of the machine tool, in particular in an internal memory of the machine tool or of a machine tool controller.

10. The method according to at least one of the preceding claims, wherein: The WID and / or the tool data are attached directly to the tool or the tool holder in a machine-readable manner so that the WID and / or the tool data can be retrieved by scanning.

11. The method according to at least one of the preceding claims, wherein: The tool data and / or the WID are stored in a database; The tool data and / or the WID are permanently attached to the tool, in particular as an engraved code or a printed QR code; The tool data and / or the WID are temporarily stored on the tool, in particular as a printed sticker; and / or The tool data and / or the WID are stored on a data carrier associated with the tool, in particular on an RFID chip.

12. The method according to at least one of the preceding claims, wherein: The two-dimensional code is a data matrix code or a two-dimensional code.

13. The method according to at least one of the preceding claims, wherein: The tool data are retrieved via a direct data connection so that the tool data directly arrive at the machine tool and are directly available at the machine tool for further processing of the tool data, wherein: Preferably, after the retrieval, the tool data is stored on the machine tool side and used for executing the machining task.

14. The method according to at least one of the preceding claims, wherein: The data interface is a tool data interface corresponding to the UPC UA (Open Platform Communications Unified Architecture), and wherein: The interface includes an OPC UA server.

15. The method according to at least one of the preceding claims, wherein: The UPC UA (Open Platform Communications Unified Architecture) is used to communicate with the tool management system, specifically to retrieve the tool data.

16. The method according to at least one of the preceding claims, wherein: The tool data is retrieved from the OPC UA server by the OPC UA client as an OPC UA service call.

17. The method according to at least one of the preceding claims, wherein: After the retrieval, the tool data are converted into an input format, which is predefined according to the machine tool controller used.

18. Computer program product comprising instructions which, when said program is executed by a control device of a numerically controlled machine tool, cause said machine tool to carry out the method according to at least one of the preceding claims.

19. A control device for a machine tool, the control device of the machine tool having a data interface for connecting to a tool management system and an application-based control system, the control device being configured to: Get the unique tool identifier WID of the tool to be picked up; matching the acquired WID with previously known tool identification data of the machine tool; If it is determined that the tool to be picked up has not been determined and / or updated tool data of the WID is available, then: Automatically, through the data interface, directly retrieve tool data from the tool management system based on the acquired WID or automatically directly retrieve the tool data from the tool to be picked up; A loading position of the tool to be picked up is determined based on the retrieved tool data, and the tool is preferably picked up at the determined loading position.

20. A control device according to the preceding claim, wherein: The data interface is a tool data interface corresponding to the UPC UA (Open Platform Communications Unified Architecture), and wherein The interface includes an OPC UA server.

21. A machine tool having a control device according to at least one of claims 19 or 20.

Images