Method and device for tool data exchange

Abstract

The present invention relates to a method for processing tool data on a machine tool with a data interface for connection to a tool management system and associated control device and computer program product.The procedure comprises the following steps: capturing a unique tool identifier (WID) of a tool to be picked up; comparing the captured 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 is available for the WID: via the data interface, automated retrieval of tool data directly from the tool management system, based on the captured WID, or automated retrieval of tool data directly from the tool to be picked up; determining a loading location for the tool to be picked up based on the retrieved tool data and preferably, picking up the tool at the determined loading location.

Description

[0001] The present invention relates to a method for processing tool data on a machine tool with a data interface for connection to a tool management system and associated control device and computer program product. background

[0002] It is known in the art to control workpiece machining on numerically controlled machine tools using an NC control unit, which is usually integrated into the machine tool. In particular, the NC control unit controls controllable actuators, e.g., spindle drives, axis drives of the machine tool's axes, and other machine functions of the machine tool, e.g., based on an NC program generated by a CAD / CAM system or programmed by a machine operator.

[0003] DE 10 2006 043 390 A1 describes a device and method for simulating a workpiece machining process on a machine tool. The described approach is characterized by a holistic simulation approach. In particular, the PLC motion sequences of the machine tool are simulated using a PLC control unit and a PLC sequence simulation unit. This enables a realistic simulation of a machine tool in all its essential aspects.

[0004] EP 2 891 020 A1 proposes an extended control of a numerically controlled machine tool, in which a further control device or operating device is provided at a higher level than the NC control device, which extends the operation or control of the machine tool by the operator compared to the functions of an NC control device.

[0005] Tool and tool data management in the machine tool sector currently pose a very significant challenge. In particular, there are currently a variety of ways in which tools and the corresponding data are transferred to the machine. On the machine tool side, it is particularly important that the tool data is entered so that it can be used in the control system, and therefore a specific data format is required. Furthermore, current presetting devices are usually designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, the designations, and the presentation of the data differ from manufacturer to manufacturer. Corresponding APIs are not available. Due to these hurdles, automation in machine tool control represents a key problem, particularly with regard to the processing of tool data.However, tool data that is as precise as possible is essential for modern manufacturing processes in order to enable efficient and effective use of tools and machine tools.

[0006] It is therefore an object of the present invention to provide a system, a device or a method with which the operation or control of a machine tool is expanded and improved, in particular with regard to the operability of the machine tool with regard to automation, in order to achieve efficient production of workpieces by the machine tool. Summary

[0007] To achieve the above-described problem, a method for processing tool data on a machine tool according to claim 1, as well as systems, devices, and methods according to the independent claims, are proposed. Dependent claims relate to preferred or particularly useful embodiments.

[0008] According to a preferred embodiment, the following is proposed: A method for processing tool data on a machine tool (in particular on the control device of the machine tool) with a data interface for connection to a tool management system. The method steps include, in particular: the recording of a unique tool identifier, hereinafter referred to as "WID", of a tool to be picked up, and then the comparison of the recorded 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 are available, then tool data, based on the recorded WID, are first automatically retrieved directly (and preferably immediately) from the tool management system via the data interface. Preferably, therefore, no manual intervention is required.Alternatively, the tool data is automatically retrieved directly (and preferably immediately) from the tool to be picked up. The tool data is therefore directly available in the machine tool controller, e.g., the NC control unit. In the next step, a loading location for the tool to be picked up is determined based on the retrieved tool data, and preferably the tool is also picked up at the specified loading location. This design enables automated and efficient recording of the necessary (and current) tools with tool data, which can be used directly in the production process, thus significantly improving the efficiency of using the machine tool and, in particular, in the manufacture of workpieces. In addition, errors and waiting times during tool recording / input are reduced or completely eliminated.

[0009] In preferred embodiments, capturing the WID also includes scanning a tool identification code of the tool to be picked up. The WID can be a unique identifier (e.g., UUID - Universally Unique Identifier) ​​that uniquely identifies the specific tool globally and thus enables secure and rapid detection of the tool.

[0010] In preferred embodiments, the tool management system is an external tool management system for providing data, for example, from the cloud, and the data interface is a tool data interface that is connected to the external tool management system via a network connection. The term "external" preferably refers to the machine tool, so that an external data management system is a system that is provided externally and preferably independently of the individual machine tool. A tool management system can, in particular, be a resource management system with which some or all available tools include master data (for example, as part of the tool data) as well as current documentation on tool data, maintenance status, and the operational readiness of the tools (concrete statements about tool availability at any time).In addition, the tool data from the tool management system can include a tool history. The tool history can record all events, from planning and tool introduction to the actual working periods during which the tool was in use. The automated provision of this comprehensive tool data via WID enables efficient and precise use of the machine tool. Providing the data via the external tool management system offers the possibility of decentralized and flexible provision of the data for various machine tools.

[0011] In preferred embodiments, the tool data includes measured values ​​and / or setting values ​​of the tool, which were determined on an external device, in particular a presetting, balancing, or shrinking device. This specific data is particularly advantageous for the even more precise use of the tool on the machine tool, whereby the individual provision of the data via automated data retrieval has the particular advantage that the most current measured values ​​and / or setting values ​​of the actual tool to be changed are automatically available on the machine tool, allowing the production process to be designed efficiently and precisely.

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

[0013] In preferred embodiments, an NC program is scanned for required tools, and preferably a corresponding difference list is created. In this advanced version, not only is the specific tool data automatically retrieved, but the required tools for the specific production or machining order are also automatically determined. The machining order can, in particular, be a CNC or NC program for the production of one or more components.

[0014] In preferred embodiments, a predetermined setup location is defined for the tool to be changed. In this advanced implementation, not only are the specific tool data automatically retrieved, but an optimal setup location for the tool to be changed (which is still required to process the specific production order or machining order and still needs to be changed at the machine tool or tool magazine) is also automatically determined.

[0015] In preferred embodiments, a tool setup sequence is also determined based on a machining order, so that the tool loading locations are determined according to the machining order. In this advanced version, not only are the specific tool data automatically retrieved, but an optimal setup location for all required tools is also automatically determined.

[0016] In preferred embodiments, the previously known tool identification data is stored in a memory on the machine tool, in particular an internal memory of the machine tool or the machine tool control system. This enables rapid retrieval of the data during the production process, allowing the production process to be designed efficiently and precisely.

[0017] In preferred embodiments, the WID and / or tool data are attached directly to the tool or tool holder in a machine-readable format for retrieval by scanning. This enables rapid retrieval of the data during the production process, allowing the production workflow to be designed efficiently and precisely.

[0018] In preferred embodiments, the tool data is stored in at least one of the following ways: • the tool data and / or the WID are stored in a database; • the tool data and / or the WID are permanently affixed to the tool, in particular as an engraved or printed 2D 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 assigned to the tool, in particular an RFID chip.

[0019] This enables data to be retrieved quickly during the production process, allowing the production process to be designed efficiently and precisely.

[0020] In preferred embodiments, the 2D code is a data matrix code encoding or a QR code encoding.

[0021] In preferred embodiments, the tool data is retrieved via a direct data connection, so that it is transferred directly to the machine tool and is immediately available for further processing. Preferably, the tool data is stored on the machine tool side after retrieval and used when processing a machining job. This enables very fast and reliable retrieval of the data during the production process, allowing the production process to be designed efficiently and precisely.

[0022] In preferred embodiments, the data interface is a tool data interface that conforms to UPC UA (Open Platform Communications Unified Architecture), and the interface includes an OPC UA server. This enables particularly flexible use and efficient data retrieval.

[0023] In preferred embodiments, UPC UA is used for communication with the tool management system, and in particular for retrieving tool data. This enables particularly flexible use and efficient data retrieval.

[0024] In preferred embodiments, the tool data is retrieved from an OPC UA server via an OPC UA client as an OPC UA service call. This enables particularly flexible use and efficient data retrieval.

[0025] In preferred embodiments, the tool data is converted after retrieval into an input format (standardized input format) that is specified depending on the machine tool control system used. This enables particularly flexible use and efficient data retrieval.

[0026] Further advantageous aspects are suggested: A computer program product comprising instructions which, when the program is executed by a control device of a numerically controlled machine tool, cause the latter to carry out the method according to at least one of the preceding features.

[0027] Control device for a machine tool with a data interface for connection to a tool management system and to an application-based control system. The control device can be configured to: detect a unique tool identifier, hereinafter referred to as "WID," of a tool to be picked up, and then compare the detected 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, tool data based on the detected 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, a loading location for the tool to be picked up is defined based on the retrieved tool data, and preferably the tool is also picked up at the specified loading location.

[0028] The data interface of the control device is a tool data interface that complies with UPC UA, Open Platform Communications Unified Architecture, and includes an OPC UA server.

[0029] Tool and tool data management in the machine tool sector currently poses a major challenge, and in particular, there are currently a variety of ways in which tools and data are transferred to the machine. On the machine tool side, this requires that the tool data be entered and can be used in the control system, and therefore a specific data format is available. Various data formats are relevant for this, such as CNC or PLC.

[0030] In addition to the actual tools, tool manufacturers also provide presetting devices and tool controls with which target values, tolerance ranges, and actual values ​​for the respective tools can be determined or output. These presetting devices are designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, the designations, and the presentation of the data vary from manufacturer to manufacturer. Corresponding APIs are not available; only the generic OPC UA protocol is supported for computer-implemented control. The OPC UA protocol is based on low-level, hardware-related commands, so control via this protocol represents a complex task in practice that currently cannot be easily solved.This is especially true when controlling devices from third-party manufacturers with proprietary hardware. A particularly advantageous aspect in this case is the unified input format, which solves the aforementioned problems regarding data and format conversions.

[0031] According to a further preferred embodiment according to at least one of the described features, the following is also proposed: an operating device for use on a numerically controlled machine tool, with a data processing device which is particularly designed to execute control and operating 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 designed to accept input information in accordance with operating inputs from an operator of the machine tool and to transmit it to the data processing device and / or to output output information transmitted by the data processing device to the operator.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, tool data is first automatically retrieved directly (and preferably immediately) from the tool management system via the data interface based on the recorded WID. Preferably, this no longer requires manual intervention (by the operator). Alternatively, the tool data can be automatically retrieved directly (and preferably immediately) from the tool to be picked up. In the next step, a loading location for the tool to be picked up is determined based on the retrieved tool data, and preferably the tool is also picked up at the specified loading location.This design enables automated and efficient recording of the required (and current) tools with tool data, which can be used directly in the production process, thus significantly improving the efficiency of machine tool use and, in particular, workpiece production. Furthermore, errors and waiting times during tool recording / input are reduced or completely eliminated.

[0032] In preferred embodiments, the data processing device is configured to control a machining order for machining one or more workpieces on the machine tool based on a machining step sequence, in particular a machining step sequence selectable by the operator via the user interface, and / or to call corresponding machine or control functions via the control interface on the control device. Depending on the machining order, a setup sequence for the tools is defined so that the tool loading locations are determined according to the machining order. In this embodiment, not only are the specific tool data automatically retrieved, but an optimal setup location for all required tools is also automatically determined.

[0033] In preferred embodiments, the data processing device is configured to control the processing order on the basis of processing step sequence data stored in a data storage device of the operating device, which are associated with the processing step sequence.

[0034] In preferred embodiments, the processing step sequence data specify a plurality of processing steps and / or a predetermined order of the plurality of processing steps.

[0035] In preferred embodiments, the plurality of processing steps comprises at least one or more of: - accept a processing order assigned to the processing step sequence, - set up or prepare one or more clamping devices required for the machining order on the machine tool, - set up one or more tools required for the machining job on the machine tool, - load or prepare one or more tools required for the machining job on the machine tool, - load and / or program one or more NC codes, NC programs and / or NC program sections required for the machining order, - execute one or more NC codes, NC programs and / or NC program sections required for the machining order, - run a process monitoring application, - document one or more processing processes assigned to the processing order, - carry out an automated quality check of one or more machined workpieces, and / or - Submitting the processing order.

[0036] In preferred embodiments, the plurality of processing steps comprises at least one or more: - automatic assembly of workpiece pallets, - automated loading of workpiece pallets, - automatic re-sorting of workpieces onto workpiece pallets, - Setting a clamping position of a workpiece, - Changing from one clamping position to another, - automatic measurement of workpieces, - automatic loading of a tool magazine of the machine tool, - automated setting of tools on the machine tool, - automatic re-sorting of tools at the tool magazine, and / or - Carrying out one or more cleaning, maintenance, repair and / or service applications on the machine tool.

[0037] In preferred embodiments, the processing step sequence data specify an associated processing step application for each processing step of the processing step sequence. The data processing device is preferably configured to execute the respectively associated processing step application to control a processing step.

[0038] In preferred embodiments, the operating device further comprises a network interface which is configured to connect the operating device to one or more servers via a communication network.

[0039] In preferred embodiments, the data processing device is configured, if at least one of the servers provides for the execution of processing step applications as web applications according to client-server communication, to execute the associated processing step application as a web application according to the client-server communication with the at least one server via the network interface to control a processing step. This server can also specify a tool setup sequence depending on a processing order, so that the tool loading locations are determined according to the processing order. In this embodiment, not only are the specific tool data automatically retrieved, but an optimal setup location for all required tools is also automatically determined.

[0040] In preferred embodiments, the data processing device is configured to automatically retrieve input information and / or the required tool data from the external tool management system for executing a processing step application associated with a processing step of the processing step sequence.

[0041] Preferably, the data processing device is configured to automatically retrieve or load input data and / or tool data required to execute a processing step application associated with a processing step of the processing step sequence from one or more servers via the network interface.

[0042] Preferably, the input data comprises one or more of: - Model data specifying a CAD model of one or more workpieces, one or more workpiece parts and / or one or more tools, - NC data specifying one or more NC codes, one or more NC programs and / or one or more NC program sections, - Order data that specify order data assigned to a workpiece processing, - Tool data, which provides information about one or more assigned tools, - Tool list data, which specifies a list of tools assigned to a machining order or workpiece machining, - Clamping device data, which provides information on one or more assigned clamping devices, and / or - Clamping device list data that specifies a list of clamping devices assigned to a machining order or workpiece machining.

[0043] In preferred embodiments, the data processing device is configured to check or confirm, before executing a processing step sequence, whether or that required input data are available for each processing step application assigned to the processing steps, in particular by means of input from the operator, by means of loadable input data and / or by means of output data of a processing step application to be executed beforehand.

[0044] A control device for use on a numerically controlled machine tool with a control device for controlling machine functions of the machine tool and an operating device connected or connectable to the control device according to one of the preceding aspects and / or a machine tool with such a control device.

[0045] Further aspects and their advantages as well as advantages and more specific embodiments of the aspects and features described above are described in the following, but in no way limiting, descriptions and explanations of the attached figures. Short description of the characters Fig. 1 shows a schematic representation of a system for operating and controlling one or more numerically controlled machine tools according to an embodiment of the present invention. Fig. 2 shows a schematic representation of the method according to an embodiment of the present invention. Fig. 3 schematically shows the various levels of abstraction from the graphical interface that the operator sees, through the backend, further through the standardization of the data structure, up to the presetting devices from a plurality of different manufacturers according to at least one embodiment of the present invention. Fig. 4 shows, by way of example, the exchange of tool data between the machine tool WZM and the tool presetting device WV via the OPC UA protocol according to at least one embodiment of the present invention. Fig. 5 shows an example of the tool data exchange as an interface provided via OPC UA according to at least one embodiment of the present invention. Fig. 6 shows an example of a job selection screen of a graphical user interface of the user interface of the operating device of the machine tool according to at least one embodiment of the present invention. Fig. 7 shows an example of a tool inspection screen of the graphical user interface of the user interface of the operating device of the machine tool according to at least one embodiment of the present invention. Fig. 8 shows an example of a tool loading screen of the graphical user interface of the user interface of the operating device of the machine tool according to at least one embodiment of the present invention. Fig. 9 shows, by way of example, excerpts from a portion of the API specifications for the input format according to at least one embodiment of the present invention. Fig. Figure 10 shows, by way of example, excerpts from some of the different specifications for the input format and the manufacturer formats required for controlling the tool controllers and presetting devices. Using the lookup table shown, the formats can be converted into one another according to at least one embodiment of the present invention. Detailed description of the figures and preferred embodiments

[0046] Examples and embodiments of the present invention are described in detail below with reference to the accompanying figures. Identical or similar elements in the figures may be designated by the same reference numerals, although sometimes different reference numerals may be used.

[0047] It should be emphasized, however, that the present invention is in no way limited or restricted to the exemplary embodiments and their embodiment features described below, but further comprises modifications of the exemplary embodiments, in particular those which are encompassed by modifications of the features of the described examples or by combination of one or more of the features of the described examples within the scope of protection of the independent claims.

[0048] Tool and tool data management in the machine tool sector currently pose a very significant challenge. In particular, there are currently a variety of ways in which tools and their data reach the machine tool for use. On the machine tool side, it is particularly necessary for the tool data to be entered in order for it to be used in the machine tool control system. Therefore, a specific data format for the tool data is usually required. This is usually determined by the machine tool control system. Furthermore, presetting devices for setting or measuring tools are designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, the designations, and the presentation of the data differ from manufacturer to manufacturer. Corresponding APIs are not available.Due to these diverse hurdles, automation in machine tool control with regard to tool data currently represents a central problem.

[0049] It is therefore advantageously proposed to create the possibility of connecting the entire machine tool system directly with other data management systems that exist outside the machine tool by means of a tool management application on the machine tool control (e.g. "Tool Master") combined with special processing and provision of the tool data (e.g. "Tool Data Exchange"), so that tool data that is present, for example, in a tool measuring device can be recorded and loaded directly into the machine tool (or machine tool control or NC control device) via an identification of the tool on the machine, so that the workflow and tool handling can be handled jointly and automatically via the tool data exchange application of the machine tool control.

[0050] A direct data connection is proposed as being particularly advantageous, i.e. the data can be exchanged directly via an interface, but the tool data can also be available in a cloud, so that when the tool is selected on the machine tool control, tool data is sent directly to the machine and is therefore directly available in the machine tool.

[0051] To explain the underlying system structure, the arrangement and connectivity of the machine tools in a specific network is first described. Fig. 1 shows a schematic, exemplary representation of a system for operating and controlling one or more numerically controlled machine tools according to an embodiment of the present invention.

[0052] The system according to Fig. 1 comprises, for example, a web server 110, which is connected, for example, to a communication network 100, for example the Internet, a cloud service network or a local network.

[0053] Furthermore, the system includes Fig. 1 shows, for example, a database server 210 and a CAD / CAM system server 220, which are connected, for example, to a communication network 200, preferably a local network (e.g. LAN, WLAN, etc.).

[0054] An example is the 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.

[0055] The system according to Fig. 1 further comprises, by way of example, a numerically controlled machine tool 250A (e.g., a milling machine, a universal milling machine, a machining center, a milling / turning machine, a turning center, a grinding machine, a gear cutting machine, a coating machine for additive manufacturing, etc.) with an NC control device 240A assigned to the machine tool 250A, which is connected to the machine tool 250A or, preferably, to controllable actuators and sensors of the machine tool 250A, and which is configured to control the machine tool 250A or functions of the machine tool 250A. The control device 240A can, by way of example, be integrated into the machine tool 250A.

[0056] Furthermore, the system includes Fig. 1 shows, by way of example, an operating device 230A assigned to the machine tool 250A, which is connected to the control device 240A assigned to the machine tool 250A. The operating device 230A is also connected, by way of example, to the communications network 200. By way of example, the operating device 230A is configured to communicate with the database server 210 and the CAD / CAM system server 220 via the communications network 200.

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

[0058] For example, the system includes Fig. 1 also further numerically controlled machine tools 250B and 250C each with correspondingly assigned control devices 240B and 240C as well as each with correspondingly assigned operating devices 230B and 230C.

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

[0060] Furthermore, the system includes Fig. 1 shows, by way of example, a separate operating device 260 (e.g. a user computer such as a laptop, desktop PC, tablet, or even a smartphone) which is connected to the communication network 200.

[0061] Furthermore, the system includes Fig. 1 shows, by way of example, an external device WV suitable for providing and / or determining tool data, for example a presetting, balancing, or shrinking device. The external device WV is connected to the communication network 200.

[0062] The operating device 230 can be designed or provided by means of a computer (e.g. a front-end PC integrated in a control panel of the machine tool or in the machine tool).

[0063] Furthermore, the operating device 230 comprises, for example, a user interface 233, TM UI, or a frontend and a network interface for establishing a communicative connection with the network 200 or with the network 100.

[0064] The TM UI or frontend is preferably a graphical user interface 233 (GUI) for the operator (e.g., comprising output functions via a screen and input functions via input devices, e.g., comprising a mouse, a keyboard, one or more touch screens implemented on the screen, softkeys, rotary knobs, rotary controls, and / or buttons, etc., and optionally output functions via further output devices such as LED information fields, lights, lamps, warning lights, audio outputs, etc.).

[0065] In terms of hardware, the control device 240 can, in embodiments, be implemented on a computer, for example, such as the same computer as the operating device 230. Alternatively, the control device 240 can be implemented on a separate computer, for example, on a back-end PC of the machine tool, which can, for example, be integrated into the machine tool.

[0066] The web server 110 is configured, for example, to provide web-based data or web-based applications via the network 100 and to execute them upon request, for example, by one or more of the operating devices 230 or 260 and to transmit corresponding data via the networks 100 and 200 to the requesting operating device 230 or 260.

[0067] For example, the operating device 260 can be designed as a computer that includes both an operating device software analogous to the operating device software of the operating devices 230 and optionally one or more CAD / CAM software applications.

[0068] Fig. 2 shows a schematic, exemplary representation of the method for processing tool data on a machine tool (WZM) with a data interface for connection to a tool management system. The method steps include: recording a unique tool identifier, hereinafter referred to as "WID", of a tool (WZ) to be picked up, and then comparing the recorded WID with the tool identification data previously known to the machine tool (WZ). If it is determined that the tool (WZ) to be picked up is not yet known to the machine tool (WZ) and / or updated tool data for the WID are available, then tool data (or updated tool data) based on the recorded 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, a loading location for the tool WZ to be picked up is defined based on the retrieved tool data, and preferably the tool WZ is also picked up at the specified loading location.

[0069] The standardization of measured tool data is preferably achieved through a uniform input format, which can be converted into the manufacturer formats of all supported manufacturers and vice versa. This allows the requests and responses to a manufacturer-specific presetting device (WV) to be mapped manufacturer-independently. The control program for controlling the machine tool can then access the data in the standardized input format in the next step. In particular, this also allows tool data measured with different presetting devices to be compared with each other.

[0070] The tool manufacturers, for example S1, S2, S3, provide not only the actual tools but also presetting devices and tool controllers with which, for example, target values, tolerance ranges, and actual values ​​for the respective tools can be determined or output. These presetting devices are designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, the designations, and the presentation of the data vary from manufacturer to manufacturer. Corresponding APIs are not available; only an M2M protocol, such as MQTT, MTConnect, AMQP, and, particularly advantageously, the generic OPC UA protocol, is supported for computer-implemented control.The OPC UA protocol is based on low-level, hardware-related commands, so controlling it via this protocol is a complex task in practice, requiring special operator qualifications. This is especially true when controlling devices from third-party manufacturers with proprietary hardware. In this version, the standardized input format represents a solution to this complex task.

[0071] The exemplary data transfer occurs through a network request via a tool data interface to the tool management system, which is preferably external and provides data from the cloud, for example, to the communication network 100 and / or communication network 200, via the network connection. The tool management system provides tool data on request for the devices connected to the communication network 100 or 200, such as the machine tool WZM or the machine tools 250A; 250B; 250C, the operating devices 230A; 230B; 230C, the NC control devices 240A; 240B; 240C, or the tool presetting device WV, see also Fig. 1. Optionally, the tool management system can process further requests via the communication network 100 or 200, see also Fig. 5.

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

[0073] Preferably, the tool data are converted after retrieval (on the machine tool control side) into an input format which is specified depending on the machine tool control used.

[0074] For example, during scanning S, the WID is recorded, and a tool identification code 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 it) for recording information that has been encoded in such a way that it is particularly suitable for further data processing on at least one digital device. The coding can be, for example, barcodes, 2D codes, or RFID chips. This type of coding is particularly suitable if the corresponding information is applied directly to a tool, in particular to the tool WZ, and if it can be relevant, for example, for the management, handling, localization, identification, and / or description of the tool.According to one application example, the information can be applied directly to the tool, particularly the WZ tool, preferably by laser engraving, or alternatively, a sticker can be printed and affixed to the tool. This approach is also optionally available for workpieces that are loaded into the machine tool. Workpiece data can therefore be automatically retrieved from a workpiece management system (e.g., cloud-based) via automatic retrieval after scanning a workpiece ID.

[0075] Information capture via a scanning device is advantageous over conventional methods that require human intervention, e.g., by the machine tool operator. Conventional methods that require the operator to manually read information from the tool and enter it manually into the machine tool controller are known from the state of the art. This can lead to transmission errors, which can be minimized or eliminated through automated processes, such as scanning S. Furthermore, information capture via a scanning device is less time-consuming and is therefore particularly suitable for time-optimized work.

[0076] The tool data include measured values ​​and / or setting values ​​of the tool WZ, which were determined on an external device, in particular on the tool presetting device WV, on a balancing device or on a shrinking device.

[0077] The data stored in the input format includes, among other things, the tool data. The tool data includes the measurement data from the WV presetter and possibly additional data on tool properties that are not recorded by the WV presetter. The measurement data can include, among other things: • Length • Thickness • Weight • Tolerance range • Count the number of required free spaces in the tool magazine. Additional data on additional tool properties may include: • Date of acquisition • Tool history • Number of uses • Last job in which this tool was used.

[0078] Furthermore, the data stored in the input format also includes the WID. The WID is represented by a unique ID, for example, a Unique Device Identification (UDI). To ensure the uniqueness of the ID across the entire scope, a central server, such as a UDI server, can be used to assign the IDs. In particular, in the case of the UDI, a global UDI server is used, which issues globally unique IDs (see also Fig. 5).

[0079] For example, the previously known tool identification data are stored in a memory on the machine tool, in particular an internal memory of the machine tool or the machine tool control system. Furthermore, the WID and / or tool data can, for example, be attached in a machine-readable manner directly to the tool WZ or the tool holder WZH in order to be retrieved by the scanning process step S. In particular, the tool data and / or the WID can be attached in a machine-readable manner as follows: • Save in a database (e.g. in the cloud or on an external server); • Permanently affix to the tool WZ, in particular as an engraved or printed 2D code; • Temporarily deposited on the tool WZ, in particular as a printed sticker, whereby the sticker is preferably printed with a 2D code; and / or • Save on a data carrier assigned to the tool WZ (e.g. attached to the tool), in particular an RFID chip.

[0080] Preferably, the data is physically attached directly to the corresponding tool (WZ). This offers the advantage that the data can always be accessed whenever the tool (WZ) is accessible. Encodings specifically designed for reading by digital devices are particularly advantageous. These include, in particular, optical encodings such as 2D codes. The present invention supports both reading DataMatrixCode encoding and QR Code encoding.

[0081] An alternative way to attach information directly to the tool is to write RFID chips that are integrated directly into the tool. This option is advantageous over a database because they are attached directly to the tool, similar to 2D codes.

[0082] Permanently storing data on the tool via laser engraving is advantageous over conventional methods in which the information is attached to the tool in a way that allows the relevant information to become separated from the tool, or that the relevant information becomes corrupted over time or due to expected external influences. Compared to applying a sticker to which relevant information is written, engraving can have advantages. The adhesive surface of the sticker can lose its adhesion over time or due to external influences, meaning the sticker is lost and the relevant information can no longer be assigned to the tool.

[0083] Likewise, the material of the sticker or the ink used for labeling can be damaged by normal use, so that the relevant information can only be assigned to the tool in part or incorrectly.

[0084] For example, the tool data is retrieved via a direct data connection so that it reaches the machine tool WZM or WZ directly and is available there for further processing. Preferably, the tool data is stored on the machine tool side after retrieval and is used when processing a machining order.

[0085] For example, an NC program is scanned for required tools, for example, WZ1, WZ2, WZ3, and WZ4, and preferably a difference list is created. The difference list is created by comparing the tools required for a machining job with the tools already available, for example, WZ1 and WZ2. One or more tools to be changed, for example, WZ3 and WZ4, are then determined based on the difference list. A predetermined setup location is defined for the specific tools, for example, WZ3 and WZ4. A setup sequence for the tools is determined depending on a machining job, so that the tool loading locations are determined according to the machining job. See also Fig. 7.

[0086] The first step in the loading process is, for example, finding a free location in the machine tool (WZM). The machine tool (WZM), for example, includes a tool magazine into which the tool can be loaded. To do this, the required size of the tool to be loaded is determined based on the data stored in the input format. A suitable, free location is then searched for. If no such location is found in the machine tool (WZM) or in the tool magazine, an error message is displayed explaining the problem. Otherwise, the machine tool (WZM) or the tool magazine is positioned to enable loading at the corresponding free location.

[0087] In the next step, the tool flap of the machine tool (WZM) or the tool magazine is opened and instructions are issued on how to load the machine tool (WZM) or the tool magazine. Loading can also be automated. In the automated process, the system waits until the tool flap has been closed again. At this point, the corresponding tool must be loaded into the free space on the machine tool (WZM) or the tool magazine. This can be done either manually by the operator or automatically by an external system. Closing the tool flap signals that the tool, for example WZ2 or WZ4, has been loaded and the loading process can continue.

[0088] As a final step, a check (optional) is performed to determine whether the tool has been loaded correctly. If the check is negative, an error message is issued explaining the problem. If the check is positive, the loading process for this tool is considered complete, and the next process step is executed. The next process step could be, for example, either the loading of another tool or the automated processing of a machining order.

[0089] If the difference list is empty, the machining order is processed automatically. Otherwise, one of the missing tools on the difference list is selected and its tool data and identification data is retrieved in the input format. When selecting the tool to be set up from the difference list, the specified setup sequence is preferably maintained. Based on this data, the loading process for the tool is initiated. After the loading process has been successfully completed, the entry for the tool to be loaded is deleted from the list of missing tools and added to the list of available tools. This step is repeated until all missing tools on the difference list have been loaded and processing of the order begins.

[0090] For automatic loading, the computer program product can directly use the data in the input format, since the tool data contains, among other things, all the information necessary for loading, such as the number of positions to be occupied in the tool magazine.

[0091] Fig. 3 schematically shows the various abstraction levels from the graphical user interface 233, which the operator sees, through the backend, further through the standardization of the data structure, up to the presetting devices from a plurality of different manufacturers, for example S1, S2, and S3, according to an embodiment of the present invention.

[0092] The TM UI or frontend is preferably a graphical user interface 233 (GUI) for the operator (e.g., comprising output functions via a screen, having at least one screen area 233A, and input functions via input devices, e.g., comprising a mouse, a keyboard, one or more touch screens, softkeys, rotary knobs, dials, and / or buttons, etc., implemented on the screen, and optionally output functions via further output devices such as LED information fields, lights, lamps, warning lights, audio outputs, etc.).

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

[0094] The system for standardizing the data structure preferably corresponds to the conversion from at least one manufacturer format or from the OPC UA protocol to the standardized input format, or the conversion of the standardized input format to at least one manufacturer format or to the OPC UA protocol. Communication with the manufacturer devices S1; S2; and S3 can take place in the respective manufacturer format or via the OPC UA protocol.

[0095] Fig. Figure 4 shows an example schematic of the exchange of tool data between the machine tool WZM and the tool presetter WV via the OPC UA protocol.

[0096] Tool data is stored on the tool presetter WV and is uniquely identified with the tool holder WZH, for example, using a QR code. The tool WZ is scanned and identified by the scanner during the scanning step S. The data of the tool WZ is then written from the database in the tool presetter WV to the machine tool's tool table via the OPC UA interface. The central database can be located, for example, in the tool presetter WV.

[0097] Fig. 5 shows a schematic example of tool data exchange as an interface provided via OPC UA. In particular, the figure shows the connection of the Control adapter as part of the Control IPC to the preferably external tool management system. The connection is made via the Edge IPC, which includes the Generic machine adapter and the OPC UA Server. Overall, there are connections between the Control adapter and the Generic machine adapter, between the Generic machine adapter and the OPC UA Server, and between the OPC UA Server and the preferably external tool management system. In particular, the Control adapter can, for example, exist as a PLC / NC agent, with the Generic machine adapter present as Machine Communication X. Alternatively, the Control adapter can, for example, exist as a UDI server, with the Generic machine adapter present as a UDI client.

[0098] For example, if the control adapter is configured as a UDI server and the generic machine adapter as a UDI client, the UDI client sends a request to the UDI server when needed to generate a unique WID, which is then provided to the tool management system via the OPC UA server. The UDI server ensures that the assigned WIDs are truly globally unique.

[0099] Fig. 6 shows, by way of example, a schematic diagram of a job selection screen of the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250.

[0100] By way of example, job selection elements B1 to B5 are provided, via which the operator can select jobs 1 to 5. Preferably, the selection of the corresponding jobs on the operating device 230 can only be carried out by operators with sufficient authorization. This can be achieved, for example, through different user roles based on the operator's qualifications or training, e.g., through the user roles: simple machine operator, experienced machine operator, machine loader, setter, machine programmer, machine maintenance technician, multi-machine operator, tool presetter, work planner, factory planner, process standardizer, etc.

[0101] The selection element B6 enables, for example, the launch of an editor application for executing the machining step sequence editor on the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250. The editor application is configured to list the machining step applications provided on the web server 110 and to import them upon operator selection. The operator can also specify or define the order of the imported machining step applications and save predefined machining step sequences. This editor functionality can preferably be made available only to operators with special authorization.

[0102] Preferably, the editor specifies for each machining step application which input data or input information is required or retrieved automatically, which output data or output information is provided and / or which control functions of the machine tool are called.

[0103] In preferred embodiments, when saving an edited machining step sequence, an automatic plausibility check can be carried out, in which it is automatically checked for each machining step application whether the required input data is available (data availability check), either by manual input on the editor, by provision as output data of a machining step application preceding in the predetermined sequence, from the memory device of the operating device, the control device, from PLC registers, 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, namely the tool data measured values ​​and / or setting values ​​of the tool, which were determined on an external device, in particular a presetting, balancing or shrinking device.These special data are particularly advantageous for the even more precise use of the tool on the machine tool, whereby the individual provision of the data via automated data retrieval has the particular advantage that the most recent measured values ​​and / or setting values ​​of the tool actually to be changed are automatically available on the machine tool and the production process can be designed efficiently and precisely.

[0104] In particular, data availability will preferably be checked not only when saving an edited or created processing step sequence, but also when linking a new order with a processing step sequence or when starting a processing step sequence linked to an order or optionally also when (or before) executing the corresponding processing step applications.

[0105] When the operator executes a predefined machining step sequence on the operating device 230, preferably only each machining step application can be called and executed in the order specified by the saved or imported machining step sequence, and in particular, no machining step application can be skipped. Particularly advantageously, the tool data are only retrieved when the tool is actually needed in the next machining step of the sequence. Therefore, the tool data is retrieved promptly according to the just-in-time principle, which can reduce the memory load and computing power of the control system. Optionally, the tool data can be deleted from the machine tool control system after the last use in the machining process and only automatically retrieved from the external tool management system when the tool is used again.

[0106] Particularly advantageous is that the machine tool provides the external tool management system with detailed feedback on the use (duration and extent of use as well as, for example, working temperatures, applied forces, limit value violations, etc.) of (each) tool, so that the tool history in the external tool management system is always up to date and the tool is always linked to the most current tool data, even when changing to another machine tool.

[0107] The execution of a predetermined processing step sequence assigned to an order by the operator on the operating device 230 is triggered by the operator by selecting one of the order selection elements B1 to B5 that are assigned to a respective processing order, at least insofar as his authorization allows this.

[0108] When the operator starts a particular processing step application, a new window of the corresponding processing step application can be opened and a validity check can be performed (e.g., including a data availability check). In addition, machine functions assigned to the respective processing step application can be executed.

[0109] Furthermore, in preferred embodiments, a screen display associated with the respective processing step or a control menu associated with the respective processing step can be automatically called up on the other screen area, for example, screen area 233B, which displays a control screen of the control device 240. This can be requested or automatically set via the TM UI or the frontend.

[0110] A first processing step application (e.g., "Accept order") can provide the operator with the order header data, e.g., based on the order data of an order to be executed, wherein the associated order file is imported from the database server 210.

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

[0112] Another (optional) processing step application can concern the loading of tools or the checking of tool requirements, see Fig. 7.

[0113] The order data in an order file (e.g. order database) assigned to the corresponding workpiece processing order can contain one or more of the following header data: a name of the operation, an order identification number, an order description, a workpiece identification number, a workpiece description, an order identification number assigned to the order, an assigned customer identification number, a work plan identification number, an indication of the desired or to be achieved quantity (i.e. a number of the quantity to be produced, e.g. in the case of analog processing of several workpieces one after the other in the same workpiece processing order), a planned start time, a planned end time, a planned or calculated processing time and, if applicable, optional information from a free text field. Such data can also be provided from an ERP or MES system.

[0114] The data storage device of the database server 210 optionally stores, by way of example, a plurality of tool files (e.g., tool database), wherein each tool file provides or specifies information about an associated tool, such as one or more of: tool dimensions (size, diameter, length, cutting edge type, number of cutting edges, etc.), tool type, tool identification number, etc.

[0115] Fig. 7 shows, by way of example, a schematic diagram of a tool inspection screen of the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250.

[0116] Here, the required tools, for example, WZ1, WZ2, WZ3, and WZ4, are specified (e.g., based on a tool list file assigned to the job to be executed). Furthermore, based on the data available on the operating device, the tools present on the machine tool, for example, WZ1 and WZ3, can be displayed, as well as the tools that are still missing or still to be loaded, for example, WZ2 and WZ4.

[0117] By pressing the selection element B7 “Load tools”, the operator can proceed to the tool loading in order to load the missing tools if necessary or to enter the corresponding tool data (or either import these from the tool data if previously scanned, or import them from a tool presetter connected to the network 200 after scanning S of the tool), see e.g. Fig. 8.

[0118] Fig. 8 schematically shows, by way of example, a tool loading screen of the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250.

[0119] By selecting the B8 "Manual Input" selection element, the operator can scan the missing tools before loading them at the tool station and then enter the data manually, or import them from a tool presetter connected to the network 200 by selecting the B9 "Import from Tool Station" selection element. Particularly advantageous is that the data input, as described, is automated during the scanning process when changing the tool, particularly without operator intervention.

[0120] Another (optional) processing step application can involve loading or programming the NC code. NC files assigned to the job are specified (e.g., based on the job data of an assigned job file), and these can be exported to the control device 240 by activating the corresponding "Load NC file to NC" selection element (if necessary, after importing the corresponding file(s) from the CAD / CAM system server 220). By selecting the B10 "Edit NC file" selection element, the operator can edit (or create a new) a loaded file in the display window shown above, at least if the required operator authorization is present.

[0121] After tool loading, clamping device setup (if necessary) and NC code provision in the order and type according to the specified machining step sequence (and if necessary after further specified steps), the workpiece machining can be carried out, if necessary in conjunction with specified process monitoring, subsequent process documentation and if necessary optional quality inspection, until the order can be automatically confirmed as finished or executed in a final machining step.

[0122] Particularly advantageous is that the machine tool provides the external tool management system with detailed feedback on the use (duration and extent of use as well as, for example, working temperatures, applied forces, limit value violations, etc.) of (each) tool, so that the tool history in the external tool management system is always up to date and the tool is always linked to the most current tool data, even when changing to another machine tool.

[0123] According to one or more of the above embodiments, the operation or control of a machine tool can be expanded and improved, in particular with regard to the operability or the automation or semi-automated support of machining steps of a workpiece machining order, possibly even by partially untrained or less experienced operators.

[0124] Fig. Figure 9 shows an example excerpt from the API specifications for the input format. The input format is in JSON format.

[0125] The "Schema" column represents the version number of the input format. Using the "Schema" field, it is possible to distinguish between different versions of the input format. This is particularly advantageous because the API specifications of different versions do not have to be compatible with each other.

[0126] In addition, the “Name” column represents the name by which a field in the input format can be read, created, overwritten, or deleted.

[0127] Furthermore, the "Type" column represents the data type of the field in the input format. The data type specifies the binary or human-readable representation in the input format. Furthermore, the data type specifies the parsing method for converting the field.

[0128] Finally, the “Description” column provides a description that can be used by the user to interpret the meaning of a field in the input format.

[0129] Fig. Figure 10 shows an example of some of the different specifications for the input format and the manufacturer formats required to control the tool controllers and presetting devices. The formats can be converted into one another using the lookup table shown.

[0130] The "uniform tool type" column represents a manufacturer-agnostic tool type designation. This makes it possible to group equivalent tools from different manufacturers under one term and to assign the equivalent fields to each other when converting between different data formats.

[0131] The next columns represent the manufacturers S1; S2; and S3. The respective manufacturer columns are further subdivided into "name," the manufacturer's own designation of the tool type, and "ID," a manufacturer-independent ID. The "name" is unique to a specific manufacturer and is assigned by the manufacturer and used in the manufacturer format. The "ID," on the other hand, is determined by the input format, and the ID can be used to uniquely resolve the manufacturer's own designation "name," the manufacturer S1; S2; or S3, and the manufacturer-agnostic tool type designation "uniform tool type."

[0132] In summary, tool and tool data management currently poses a major challenge in the machine tool sector, and in particular, there are currently a variety of ways in which tools and data are transferred to the machine. On the machine tool side, this requires, in particular, that the tool data is entered and can be used in the control system, and therefore a specific data format is available. Various data formats are relevant for this, such as CNC or PLC.

[0133] A CNC is a numerical control system (NC) that incorporates one or more microprocessors for executing control functions. The external features of a CNC are usually a screen and a keyboard. The numerical control system (CNC) is operated with a CNC program that includes all required functions, such as interpolation, position, and speed control. With the help of the one or more microprocessors and the CNC program, a workpiece-specific CNC part program is executed, which is usually specified by the machine operator.

[0134] A CNC part program consists of any number of blocks that describe the entire machine workflow for machining a workpiece step by step. Each block in the program represents a geometric machining step and / or a specific machine function. A block can contain different instructions. • geometric instructions that control the relative movements between the tool and the workpiece; • technological instructions that specify feed rate, spindle speed and tools; • Movement instructions that determine the type of movement, such as rapid traverse, linear interpolation, circular interpolation and plane selection; • Switching commands for selecting tools, indexing table positions, coolant supply; • Correction calls, for example for tool length correction, cutter diameter correction, cutting radius correction, and zero point shift; as well as • Cycle and subroutine calls for frequently recurring program sections.

[0135] In addition to the numerical control, the CNC program, and the CNC part program, an adaptation program (PLC program) for the machine to be controlled is also required. This program is created by the machine manufacturer and integrated into a programmable logic controller (PLC). This program defines all machine-related links and interlocks for special functional sequences, such as tool changes, workpiece changes, and axis limitations.

[0136] To further differentiate between CNC and PLC, some differences should be highlighted. A CNC part program for machining workpieces is created by the machine user. CNC part programs can be changed or modified by the user at any time. A PLC program, on the other hand, is created by the machine manufacturer and stored permanently, for example, in a ROM (read-only memory). The PLC program only needs to be changed or replaced in exceptional cases. In particular, with a PLC, no programming takes place during operation. PLC programs must be created for each PLC (programmable logic controller) and cannot be compiled for other PLC brands. Based on this key difference, there can be up to several thousand CNC part programs per machine. The CNC part programs are created by the machine user, but the manufacturer can certainly supply fixed cycles and subroutines.A PLC typically has only one fixed, system-specific program. The program is created by the machine manufacturer, usually using available function blocks.

[0137] Machine tools are each customized to each customer. Therefore, it's very time-consuming for the service technician to determine the exact software versions required for each customer in advance and to select the appropriate software for that customer.

[0138] There are various manufacturers of key components within the machine tool, such as PLCs and NCs. The dependencies between manufacturers, versions, updates, and special equipment must be managed efficiently to ensure that the appropriate software updates are always applied.

[0139] It is therefore advantageously proposed to create the possibility of connecting the entire machine tool system directly with other data management systems that exist outside the machine tool by means of a tool management application on the machine tool control (e.g. "Tool Master") combined with special processing and provision of the tool data (e.g. "Tool Data Exchange"), so that tool data that is present, for example, in a tool measuring device can be recorded and loaded directly into the machine tool (or machine tool control or NC control device) via an identification of the tool on the machine, so that the workflow and tool handling can be handled jointly and automatically via the tool data exchange application of the machine tool control.

[0140] Examples and embodiments of the present invention and their advantages have been described in detail above with reference to the accompanying figures. It should be emphasized again that the present invention is in no way limited or restricted to the above-described embodiments and their design features, but rather further encompasses modifications of the embodiments, in particular those encompassed by modifications of the features of the described examples or by combining one or more of the features of the described examples within the scope of the independent claims. List of reference symbols: 100 communication network 110 web servers 200 communication network 210 database servers 220 CAD / CAM system servers 230 Control device 230A; 230B; 230C first operating device; second operating device; third operating device 233 User interface 233A; 233B first screen area; second screen area 240 Control device 240A; 240B; 240C first NC control device; second NC control device; third NC control device 250A; 250B; 250C first machine tool; second machine tool; third machine tool 260 Separate control device B1; B2; B3; B4; B5 Selection element for order 1; order 2; order 3; order 4; order 5 B6 Selection element for editor application B7 Load tool selection element B8 Selection element for manual input B9 Selection element for import of tool station S Scan S1; S2; S3 Tool control of a first; second; third manufacturer WV presetting device WZ tool WZ1; WZ2; WZ3; WZ4 Tool 1; Tool 2; Tool 3; Tool 4 WZH tool holder WZM machine tool QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited patent literature

[0000] DE 10 2006 043 390 A1

[0003] EP 2 891 020 A1

[0004]

Claims

[1] Method for processing tool data on a machine tool with a data interface for connection to a tool management system, the method comprising the steps of: - Recording a unique tool identifier, WID, of a tool to be picked up; - Comparison of the recorded WID with previously known tool identification data of the machine tool; - if it is determined that the tool to be recorded is not yet known and / or updated tool data is available for the WID: ◯ via the data interface, automated retrieval of tool data directly from the tool management system, based on the recorded WID or automated retrieval of the tool data directly from the tool to be picked up; ◯ Specifying a loading location for the tool to be picked up based on the retrieved tool data and preferably picking up the tool at the specified loading location. [2] The method of claim 1, wherein detecting the WID comprises scanning a tool identification tag of the tool to be picked up. [3] 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 the cloud and the data interface is a tool data interface which is connected to the external tool management system via a network connection. [4] Method according to at least one of the preceding claims, wherein the tool data comprise measured values ​​and / or setting values ​​of the tool which were determined on an external device, in particular a presetting, balancing or shrinking device. [5] Method according to at least one of the preceding claims, wherein, in order to create a difference list, the tools required for a machining order are compared with the tools already available and wherein one or more tools to be exchanged are determined on the basis of the difference list. [6] Method according to at least one of the preceding claims, wherein the method first comprises the step of scanning an NC program for required tools and preferably creating a corresponding difference list. [7] Method according to at least one of the preceding claims, wherein a predetermined setup location is defined for the tool to be changed. [8] Method according to at least one of the preceding claims, wherein the method further determines a setup sequence of the tools as a function of a machining order, so that the loading positions of the tools are determined according to the machining order. [9] Method according to at least one of the preceding claims, wherein the previously known tool identification data are stored in a memory on the machine tool, in particular an internal memory of the machine tool or the machine tool control. [10] Method according to at least one of the preceding claims, wherein the WID and / or tool data are attached directly to the tool or tool holder in a machine-readable manner in order to be retrieved by scanning. [11] 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 affixed to the tool, in particular as an engraved or printed 2D 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 assigned to the tool, in particular an RFID chip. [12] Method according to at least one of the preceding claims, wherein the 2D code is a data matrix code encoding or a QR code encoding. [13] Method according to at least one of the preceding claims, wherein the tool data are retrieved via a direct data connection so that they reach the machine tool directly and are available there for further processing, wherein the tool data are preferably stored on the machine tool side after retrieval and are used in the processing of a machining order. [14] Method according to at least one of the preceding claims, wherein the data interface is a tool data interface which corresponds to the UPC UA, Open Platform Communications Unified Architecture, and wherein the interface comprises an OPC UA server. [15] Method according to at least one of the preceding claims, wherein the UPC UA, Open Platform Communications Unified Architecture, is used for communication with the tool management system and in particular for retrieving the tool data. [16] Method according to at least one of the preceding claims, wherein the tool data are retrieved from an OPC UA server as an OPC UA service call via an OPC UA client. [17] Method according to at least one of the preceding claims, wherein the tool data are converted after retrieval into an input format which is predetermined depending on the machine tool control used. [18] Computer program product comprising instructions which, when the program is executed by a control device of a numerically controlled machine tool, cause the control device to carry out the method according to at least one of the preceding claims. [19] Control device for a machine tool with a data interface for connection to a tool management system and with an application-based control system, configured to: - Recording a unique tool identifier, WID, of a tool to be picked up; - Comparison of the recorded WID with previously known tool identification data of the machine tool; - if it is determined that the tool to be recorded is not yet known and / or updated tool data is available for the WID: ◯ via the data interface, automated retrieval of tool data directly from the tool management system, based on the recorded WID or automated retrieval of the tool data directly from the tool to be picked up; ◯ Specifying a loading location for the tool to be picked up based on the retrieved tool data and preferably picking up the tool at the specified loading location. [20] Control device according to the preceding claim, wherein the data interface is a tool data interface which corresponds to the UPC UA, Open Platform Communications Unified Architecture, and wherein the interface comprises an OPC UA server. [21] Machine tool with a control device according to at least one of claims 19 or 20.

Images