Method and device for tool data exchange

Abstract

To provide 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.SOLUTION: The method comprises: acquiring a unique tool identifier WID of a tool to be picked up; and matching the acquired WID with known tool identification information 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, the method also comprises: automatically, via the data interface, retrieving tool data directly from the tool management system based on the acquired WID or automatically retrieving the tool data directly from the tool to be picked up; and 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.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a method and associated controller and computer program product for processing tool data on a machine tool having a data interface for connecting to a tool management system. [Background technology]

[0002] background In the prior art it is known to control the machining of workpieces on numerically controlled machine tools by means of an NC controller which is usually integrated into the machine tool, in particular the NC controller controls controllable actuators, such as the spindle drives of the machine tool, the axle drives of the axles and further machine functions of the machine tool, based on an NC program which has been generated, for example, by a CAD / CAM system or programmed by a machine operator.

[0003] DE 10 2006 043 390 A1 describes an apparatus and a method for simulating a sequence for machining a workpiece on a machine tool. The described approach is characterized by an integrated simulation approach. In particular, 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. As a result, a realistic simulation of the machine tool in all essential aspects is possible.

[0004] In EP 2 891 020 A1 an extended control of a numerically controlled machine tool is proposed, in which in addition to the NC controller a further control or operating device is provided, which extends the operation or control of the operator of the machine tool with respect to the functions of the NC controller.

[0005] The management of tools and tool data in the field of machine tools currently represents a very big challenge, especially since there is currently a great variety in the manner in which tools with corresponding data come into contact with the machine. On the machine tool side, for this purpose it is particularly necessary that the tool data be entered in order to be made available for the control, 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, designations and presentation of data here vary from manufacturer to manufacturer. No corresponding API is available here. Due to these obstacles, automation in machine tool controllers also represents a central problem, especially with regard to the processing of tool data. Tool data that is as accurate as possible is however essential for modern manufacturing processes in order to enable an efficient and effective use of tools and machine tools.

[0006] It is therefore an object of the present invention to provide a system, apparatus or method in which the operation or control of a machine tool is enhanced and improved, particularly with regard to the operability of the machine tool with respect to automation, in order to achieve efficient production of workpieces by the machine tool. Summary of the Invention [Means for solving the problem]

[0007] overview In order to achieve the above object, a method for processing tool data on a machine tool is proposed according to claim 1 as well as a system, an arrangement 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 the machine tool) having a data interface for connecting to a tool management system. The method steps include, in particular, obtaining a unique tool identifier (hereinafter referred to as "WID") of the tool to be picked up and subsequently matching the obtained WID with 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, firstly the tool data based on the obtained WID is automatically retrieved directly (preferably immediately) from the tool management system via the data interface. Thus, preferably, manual intervention is no longer necessary for this purpose. Alternatively, the tool data is automatically retrieved directly (preferably immediately) from the tool to be picked up. Thus, the tool data is directly available to a WZM controller, for example an NC control device. In a next step, based on the retrieved tool data, a loading location for the tool to be picked up is determined, and preferably the tool is also picked up at the determined loading location. As a result of this configuration, automated and efficient acquisition of required (and current) tools with tool data that can be directly used in the production process is possible in order to significantly improve the efficiency of machine tool use, especially in the manufacture of workpieces. In addition, tool acquisition / entry errors and waiting times are reduced or completely avoided.

[0009] In a preferred exemplary embodiment, obtaining the WID also includes scanning the tool identification identifier of the tool to be picked up, where the WID may be a unique identification (e.g., UUID - Universally Unique Identifier) ​​that globally uniquely identifies a particular tool, thus allowing reliable and rapid tool retrieval.

[0010] In a preferred exemplary embodiment, 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 connected to the external tool management system via a network connection. In this case, the term "external" preferably relates to the machine tools, so that the external data management system is a system that is provided externally, preferably independent of the individual machine tools. The tool management system can in particular be a system of resource management, in which some or all available tools are provided with master data (for example as part of the tool data) and with up-to-date documentation of the tool data, the maintenance status and the readiness of the tools for use (specific description of the availability of the tool at any point in time). Furthermore, the tool data of the tool management system can include a tool history. The tool history can show all events from planning through the introduction of the tool to the actual working period during which the tool was used. As a result of the automatic provision of these comprehensive tool data by the WID, an efficient and accurate use of the machine tools is possible. Providing data via an external tool management system offers the possibility of a decentralized and flexible provision of data for different machine tools.

[0011] In a preferred exemplary embodiment, the tool data comprises tool measurement and / or setting values ​​determined by an external device, in particular a presetting, balancing or shrinking device. These particular data are in particular advantageous for an even more precise use of the tools on the machine tool, and the individual provision of the data by automatic data retrieval has the particular advantage that the latest measurement and / or setting values ​​of the tools actually to be exchanged are automatically available on the machine tool, allowing production sequences to be designed efficiently and precisely.

[0012] In a preferred exemplary embodiment, the tools required for a machining assignment are compared to the tools already present 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 automatically obtained, but further, which tools are required are also automatically determined for a particular production task or machining assignment. The machining assignment can be, among other things, a CNC or NC program for producing one or more components.

[0013] In a preferred exemplary embodiment, the NC program is scanned for required tools and a corresponding difference list is preferably created. In this advanced embodiment, not only is the specific tool data automatically obtained, but further, which tools are required are also automatically determined for a particular production task or machining assignment. The machining assignment may be, among other things, a CNC or NC program for producing one or more components.

[0014] In a preferred exemplary embodiment, a predefined setup location for the replaced tool is determined. In this advanced embodiment, not only is the specific tool data automatically retrieved, but the optimal setup location for the replaced tool (which is still required for the execution of the specific production task or machining assignment and will still be replaced on the machine tool or tool magazine) is automatically determined.

[0015] In a preferred exemplary embodiment, the setup sequence of the tools is further determined as a function of the machining assignment, so that the loading locations of the tools are determined according to the machining assignment. In this advanced embodiment, not only is the specific tool data automatically retrieved, but the optimal setup locations of all required tools are also automatically determined.

[0016] In a preferred exemplary embodiment, the known tool identification data is stored in a memory on the machine tool, in particular in an internal memory of the machine tool or the machine tool controller, thus enabling fast retrieval of the data during the production process and allowing efficient and accurate design of production sequences.

[0017] In a preferred exemplary embodiment, the WID and / or tool data is attached directly to the tool or tool holder in machine-readable format for retrieval by scanning, thus enabling rapid retrieval of data during the production process and allowing efficient and accurate design of production sequences.

[0018] In a preferred exemplary embodiment, the tool data is stored in at least one of the following ways: Tool data and / or WID are stored in a database, The tool data and / or WID are permanently attached 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 associated with the tool, in particular on an RFID chip.

[0019] Therefore, data in the production process can be quickly retrieved, and the production sequence can be designed efficiently and accurately.

[0020] In a preferred exemplary embodiment, the 2D code is a Data Matrix code encoding or a QR Code encoding.

[0021] In a preferred exemplary embodiment, the tool data are retrieved via a direct data connection, so that they arrive directly at the machine tool and are directly available there for further processing, and preferably the tool data are stored on the machine tool side after retrieval and used for executing the machining assignment. Thus, a very fast and reliable retrieval of data in the production process is possible, so that production sequences can be designed efficiently and accurately.

[0022] In a preferred exemplary embodiment, the data interface is a tool data interface that complies with the Open Platform Communications Unified Architecture (UPC UA) and the interface comprises an OPC UA server, thus allowing a particularly flexible use and efficient data retrieval.

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

[0024] In a preferred exemplary embodiment, the tool data is retrieved from the OPC UA server via the OPC UA client as OPC UA service calls, thus allowing a particularly flexible use and efficient data retrieval.

[0025] In a preferred exemplary embodiment, the tool data is converted after retrieval into an input format (standardized input format), said input format being predefined depending on the machine tool controller used, thus allowing a particularly flexible use and efficient data retrieval.

[0026] In a further advantageous embodiment, it is proposed: A computer program product comprising instructions, which when the program is executed by a controller of a numerically controlled machine tool, cause said machine tool to perform a method according to at least one of the preceding features.

[0027] A control device for a machine tool having a data interface for connecting to a tool management system and to an application-based control system. The control device may be configured to obtain a unique tool identifier (hereinafter referred to as "WID") of a tool to be picked up, and then match the obtained WID with known tool identification information 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, first, tool data based on the obtained WID is 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 a 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 determined loading location.

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

[0029] The management of tools and tool data in the field of machine tools currently represents a very big challenge, especially since there are currently many different ways in which tools with data can come into contact with the machine. On the machine tool side, for this purpose it is particularly necessary that the tool data can be entered and used for control, and therefore specific data formats exist. For this purpose, different data formats are relevant, for example for CNC or PLC.

[0030] In addition to the actual tools, the tool manufacturer also provides presetting devices and tool controls that can determine or output the setpoint values, tolerance ranges and actual values ​​of the respective tools. These presetting devices are in this case designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, designations and data presentation here vary from manufacturer to manufacturer. No corresponding API is available here and only the generic OPC UA protocol is supported for computer-implemented actuation. Since the OPC UA protocol is based on low-level instructions close to the hardware, actuation via this protocol actually represents complex objects that cannot currently be easily solved. This is especially true if the devices are actuated by foreign manufacturers with their own hardware. A particularly advantageous aspect in this case is therefore the standardized input format, which represents a solution to the above-mentioned problems regarding data and format conversion.

[0031] According to a further preferred embodiment according to at least one of the described features, it is further proposed: an operating device for use with a numerically controlled machine tool, having a data processing device configured in particular for executing a control and an operator control application, a control interface by which the data processing device can be communicatively connected to a control device of the machine tool, and / or a user interface configured to receive input information according to an operator control input of an operator of the machine tool, to transmit said input information 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, firstly the tool data based on the acquired WID is automatically retrieved directly (preferably immediately) from the tool management system via the data interface. Thus, preferably, manual intervention (by the operator) is no longer necessary for this purpose. Alternatively, the tool data is automatically retrieved directly (preferably immediately) from the tool to be picked up. In a next step, based on the retrieved tool data, a loading location for the tool to be picked up is determined, and preferably the tool is also picked up at the determined loading location. As a result of this configuration, automated and efficient acquisition of required (and current) tools with tool data that can be directly used in the production process is possible in order to significantly improve the efficiency of machine tool use, especially in the manufacture of workpieces. In addition, tool acquisition / entry errors and waiting times are reduced or completely avoided.

[0032] In a preferred exemplary embodiment, the data processing device is configured to control a machining assignment 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 corresponding machine or control functions on a control device via a control interface. A tool setup sequence is determined depending on the machining assignment, so that the tool loading locations are determined according to the machining assignment. In this embodiment, not only is the specific tool data automatically retrieved, but also the optimal setup locations of all required tools are automatically determined.

[0033] In a preferred exemplary embodiment, the data processing device is configured to control the machining assignment based on machining step sequence data stored in a data storage device of the operating device and assigned to the machining step sequences.

[0034] In a preferred exemplary embodiment, the machining step sequence data specifies a plurality of machining steps and / or a predefined sequence of a plurality of machining steps.

[0035] In a preferred exemplary embodiment, the multiple machining steps include at least one or more of the following: - accepting the machining assignments assigned to the machining step sequence; - setting up or preparing one or more clamping means required for the machining assignment of the machine tool; - setting up one or more tools required for a machining assignment on a machine tool; - loading or preparing one or more tools required for a machining assignment of a machine tool; - loading and / or programming one or more NC codes, NC programs and / or NC program sections required for the machining assignment; - executing one or more NC codes, NC programs and / or NC program sections required for the machining assignment; - running a process monitoring application; - documenting one or more machining processes assigned to a machining assignment; - carrying out an automated quality check of one or more machined workpieces; and / or - Outputting machining assignments.

[0036] In a preferred exemplary embodiment, the multiple machining steps include at least one or more of the following: -Automatic assembly of workpiece pallets, - automated loading of workpiece pallets, - Automatic re-use of workpieces to the workpiece pallet, - Adjustment of the clamping position of the workpiece, - changing from one clamping position to another, - Automatic measurement of workpieces, -Automatic loading of tool magazines for machine tools, - Automated setup of tools on machine tools, - Automatic reuse of tools in the tool magazine, and / or -Performing one or more cleaning, maintenance, maintenance and / or service applications on a machine tool.

[0037] In a preferred exemplary embodiment, the machining step sequence data specifies an assigned machining step application for each machining step of the machining step sequence. Preferably, the data processing device is configured to perform the respectively assigned machining step application for controlling the machining steps.

[0038] 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.

[0039] In a preferred exemplary embodiment, the data processing device is configured to execute the assigned machining step application as a web application according to client-server communication with at least one server via the network interface to control the machining steps when at least one of the servers provides execution of the machining step application as a web application according to client-server communication. The latter can further determine a setup sequence of tools according to the machining assignment, so that the loading locations of the tools are determined according to the machining assignment. In this embodiment, not only the specific tool data is automatically retrieved, but also the optimal setup locations of all required tools are automatically determined.

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

[0041] Preferably, the data processing device is configured to automatically obtain or load input data and / or tool data required for the execution of machining step applications assigned to machining steps of the machining step sequence from one or more servers via the network interface.

[0042] Preferably, the input data includes one or more of the following: - model data indicative of CAD models of one or more workpieces, one or more workpiece parts and / or one or more tools; - NC data representing one or more NC codes, one or more NC programs and / or one or more NC program sections, - order data indicating the order data assigned to the workpiece machining, - tool data indicating information about one or more assigned tools, - tool list data indicating a machining assignment or a list of tools assigned to machining a workpiece; - clamping means data indicating information about one or more assigned clamping means, and / or - Clamping means list data indicating a machining assignment or a list of clamping means assigned to a workpiece machining.

[0043] In a preferred exemplary embodiment, the data processing device is configured to check or verify, prior to execution of the machining step sequence, whether the input data required for each machining step application respectively assigned to the machining step are present, in particular by operator entered, by the presence of loadable input data and / or by output data of a previously performed machining step application.

[0044] A control device for use in a numerically controlled machine tool having a control device for controlling machine functions of the machine tool and an operating device according to one of the aforementioned aspects which is connected or can be connected to the control device and / or to a machine tool having such a control device.

[0045] Further aspects and advantages thereof, as well as advantages and more specific possible embodiments of the above-mentioned aspects and features, will be elucidated from the following description and explanation of the accompanying drawings, which should not be construed as limiting in any way. [Brief description of the drawings]

[0046] [Figure 1]1 is a schematic diagram of a system for operating and controlling one or more numerically controlled machine tools in accordance with an exemplary embodiment of the present invention; [Diagram 2] 1 is a schematic diagram of a method according to an exemplary embodiment of the present invention; [Diagram 3] FIG. 1 is a schematic diagram of various abstraction levels from the graphical interface an operator sees through a back end, through standardization of data structures, to input devices from multiple different manufacturers, in accordance with at least one exemplary embodiment of the present invention. [Figure 4] FIG. 1 illustrates, by way of example, an exchange of tool data between a machine tool WZM and a tool presetting device WV via the OPC UA protocol, in accordance with at least one exemplary embodiment of the present invention. [Diagram 5] FIG. 1 illustrates, by way of example, tool data exchange as an interface provided via OPC UA in accordance with at least one exemplary embodiment of the present invention. [Figure 6] FIG. 1 illustrates, by way of example, an order selection screen of a graphical user interface of a user interface of a machine tool operating device in accordance with at least one exemplary embodiment of the present invention. [Figure 7] FIG. 1 illustrates, by way of example, a tool inspection screen of a graphical user interface of a user interface of a machine tool operating device, in accordance with at least one exemplary embodiment of the present invention. [Figure 8] FIG. 1 illustrates, by way of example, a tool loading screen of a graphical user interface of a user interface of a machine tool operating device in accordance with at least one exemplary embodiment of the present invention. [Figure 9] FIG. 2 is a diagram illustrating, by way of example, a portion of an API specification for an input format in accordance with at least one exemplary embodiment of the present invention. [Figure 10]1 illustrates, by way of example, some of the different specifications of input formats and manufacturer formats required for controlling a tool control and a presetting device, based on the illustrated look-up tables, the formats can be converted into one another, according to at least one exemplary embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0047] Detailed Description of the Drawings and Preferred Exemplary Embodiments Example or exemplary embodiments of the present invention are described in detail below with reference to the accompanying drawings, in which the same or similar elements may be designated by the same reference numerals, but may also be designated by different reference numerals.

[0048] It should be emphasized that the present invention is in no way limited or restricted to the exemplary embodiments and the features of those embodiments described below, but rather also includes modifications of the exemplary embodiments, in particular modifications consisting of modifications of the features of the described examples or of a combination of individual or several features of the described examples, within the scope of protection of the independent claims.

[0049] The management of tools and tool data in the field of machine tools currently represents a very big challenge, in particular the manner in which tools with their data are currently contacted with the machine tool for use is very diverse. On the machine tool side, for this purpose it is particularly usually necessary that the tool data is entered in order to make it usable in the WZM controller, and therefore a specific data format of the tool data is also usually required. This is usually determined by the WZM controller. Furthermore, presetting devices for setting or measuring tools are usually designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, designations and presentation of data here vary from manufacturer to manufacturer. Corresponding APIs are not available here. Due to these diverse obstacles, automation in machine tool controllers currently represents a central problem with regard to tool data.

[0050] As a result, it is advantageously proposed that a tool management application on the WZM controller (e.g., "tool master") combined with special processing and provision of tool data (e.g., "tool data exchange") creates the possibility of directly connecting the entire WZM system to further data management systems present outside the machine tool, so that, for example, tool data present in a tool measuring device can be obtained and loaded directly into the WZM (or WZM controller or NC control device) via the tool identification information on the machine, so that workflows and tool handling can be negotiated jointly and automatically via the tool data exchange application of the WZM controller.

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

[0052] To explain the underlying system design, we first describe the placement and connectivity of the WZM in a particular network. Figure 1 shows 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.

[0053] The system according to FIG. 1 exemplarily comprises a web server 110 connected to a communication network 100, for example the Internet, a cloud service network or a local network.

[0054] Furthermore, the system according to FIG. 1 exemplarily comprises a database server 210 and a CAD / CAM system server 220 connected to a communication network 200, preferably a local network (eg LAN, WLAN, etc.).

[0055] As an example, the communication network 200 in FIG. 1 is connected to the communication network 100, and a firewall (dashed line) is provided between the communication network 100 and the communication network 200.

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

[0057] 1 further comprises, for example, an operation device 230A assigned to the machine tool 250A and connected to a control device 240A assigned to the machine tool 250A. The operation device 230A is further connected, for example, to a communication network 200. For example, the operation device 230A is configured to communicate with a database server 210 and a CAD / CAM system server 220 via the communication network 200.

[0058] The operation device 230A is also configured to communicate with the web server 110 via the communication network 200 and the communication network 100, for example.

[0059] By way of example, the system according to FIG. 1 further comprises further numerically controlled machine tools 250B and 250C, each with a correspondingly assigned control device 240B and 240C and each with a correspondingly assigned operating device 230B and 230C.

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

[0061] Furthermore, the system according to FIG. 1 exemplarily comprises a separate operating device 260 (for example a user computer, such as a laptop, desktop PC, tablet or smartphone) connected to the communication network 200.

[0062] 1 further comprises, by way of example, an external device WV suitable for providing and / or determining tool data, for example a presetting, balancing or retracting device, in which case the external device WV is connected to the communication network 200.

[0063] The operating device 230 may be formed or provided by a computer (eg, an operating console of a machine tool or a front-end PC built into the machine tool).

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

[0065] The TM UI or front end is preferably a graphical user interface 233 (GUI) for an operator (e.g. with output capabilities via a screen and input capabilities via input devices, e.g. with a mouse, a keyboard, one or more touch screens implemented on the screen, soft keys, rotary knobs, rotary knobs and / or keys, etc., and possibly with output capabilities via further output devices, e.g. LED information fields, lights, lamps, warning lights, audio output, etc.).

[0066] With regard to hardware, the controller 240, in an exemplary embodiment, can be formed on a computer, such as, for example, on the same computer as the manipulation device 230. Alternatively, the controller 240 can be implemented on its own computer, such as, for example, a back-end PC of a machine tool that can be integrated into the machine tool.

[0067] Web server 110 is, for example, configured to provide web-based data or web-based applications over network 100 upon request, e.g., by one or more of operating devices 230 or 260, and to transmit the corresponding data to the requesting operating device 230 or 260 over networks 100 and 200.

[0068] By way of example, manipulation device 260 may be formed as a computer that includes both manipulation device software similar to that of manipulation device 230 and, optionally, one or more CAD / CAM software applications.

[0069] 2 shows a schematic exemplary diagram of a method for processing tool data on a machine tool WZM having a data interface for connecting to a tool management system. 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 known tool identification information 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 for the WID is available, first the tool data (or the updated tool data) based on the obtained WID is automatically retrieved directly from the tool management system via the data interface. Alternatively, the tool data (or the updated tool data) is automatically retrieved directly from the tool WZ to be picked up. In a next step, based on the retrieved tool data, a loading location for the tool WZ to be picked up is determined, and preferably the tool WZ is also picked up at the determined loading location.

[0070] The standardization of the measured tool data is preferably implemented by a standardized input format, which can be converted into the manufacturer's format of all supported manufacturers and vice versa. As a result, manufacturer-specific requests and responses to the presetting device WV can be mapped manufacturer-independently. The control program for controlling the machine tool can then utilize the data in the standardized input format in the next step. In particular, tool data measured using different presetting devices can also thus be compared with each other.

[0071] In addition to the actual tools, the tool manufacturers, e.g. S1, S2, S3, also provide presetting devices and tool controls, which can determine or output, for example, setpoint values, tolerance ranges and actual values ​​of the respective tools. In this case, these presetting devices are designed to be operated by a human operator via a manufacturer-specific user interface. The exact operating steps, specifications and data presentation here vary from manufacturer to manufacturer. No corresponding API is available here, only M2M protocols, such as e.g. MQTT, MTConnect, AMQP, and particularly advantageously the generic OPC UA protocol, are supported for computer-implemented actuation. Since the OPC UA protocol is based on low-level instructions close to the hardware, actuation via this protocol actually represents a complex object and therefore also requires specific qualifications of the operator. This is especially true if the devices are actuated by foreign manufacturers with their own hardware. In the present embodiment, a standardized input format represents a solution to this complex object.

[0072] An exemplary data transfer is performed by a network query via a tool data interface to a tool management system, which is preferably external and provides data via a network connection from a cloud, e.g., communication network 100 and / or communication network 200. Upon request, the tool management system provides tool data to a device connected to communication network 100 or 200, e.g., machine tool WZM or machine tool 250A, 250B, 250C, operating device 230A, 230B, 230C, NC control device 240A, 240B, 240C or tool presetting device WV (see also FIG. 1). Optionally, the tool management system can process further requests via communication network 100 or 200 (see also FIG. 5).

[0073] The data interface of the control device 240 is, for example, a tool data interface corresponding to the Open Platform Communications Unified Architecture (UPC UA), the interface comprising an OPC UA server. Also, for example, the UPC UA is used for communication with the tool management system, in particular to retrieve tool data. Also, for example, the tool data is retrieved from the OPC UA server via an OPC UA client as an OPC UA service call.

[0074] Preferably, the tool data is converted after retrieval (on the machine tool controller side) into an input format, said input format being predefined depending on the machine tool controller used.

[0075] By way of example, during the scan S, the WID is acquired and the tool identification information identifier of the tool WZ to be picked up is scanned. For this purpose, the machine tool WZ is equipped with a (integrated or connected) scanning device for acquiring information encoded in such a way that it is particularly suitable for further data processing on at least one digital device. The encoding can be, for example, a barcode, a 2D code or an RFID chip. This type of encoding is particularly suitable if the corresponding information is attached directly to the tool, in particular to the tool WZ, and can, for example, relate to the management, handling, localization, identification information and / or description of the tool. According to one exemplary application, the information can be attached directly to the tool, in particular to the tool WZ, in that it is preferably engraved by a laser or a seal is printed and adhesively bonded to the tool accordingly. Optionally, this procedure is also possible for the workpiece inserted in the WZM. The data of the workpiece can thus be automatically retrieved by a (for example, cloud-based) workpiece management system via an automatic search after scanning the ID of the workpiece.

[0076] Acquisition of information by means of a scanning device is advantageous over conventional methods, in which acquisition of information is performed by human intervention, for example by an operator of the WZM. From the prior art, conventional methods are known, in which the operator has to read information manually from the tool and then manually enter this information in the WZM controller. In this case, transmission errors may occur, for example during scanning S, which can be minimized or eliminated by automated methods. Furthermore, acquisition of information by means of a scanning device is less time-consuming and is therefore particularly suitable for time-optimized tasks.

[0077] The tool data includes measured and / or set values ​​of the tool WZ determined by an external device, in particular by a tool presetting device WV, by a balancing or retracting device.

[0078] The data stored in the input format include, among other things, tool data. The tool data includes measurement data of the presetting device WV and possibly further data relating to tool characteristics not acquired by the presetting device WV. The measured data can include, among other things: ·length Thickness ·weight Tolerance range ·How much free space is required in the tool magazine?

[0079] Further data regarding additional tool characteristics may include, among others: ·Acquisition date Tool history Number of uses The last job this tool was used in.

[0080] Furthermore, the data stored in the input format also includes, among others, a WID. The WID is shown based on a unique ID, for example based on a Unique Device Identification (UDI). To ensure the uniqueness of the IDs over the entire scope of application, a central server, for example a UDI server, can be used to assign the IDs. In particular, in the case of UDI, a global UDI server is used that issues unique IDs worldwide (see also FIG. 5).

[0081] By way of example, the known tool identification data is stored in a memory on the machine tool, in particular in an internal memory of the machine tool or of the machine tool controller. Furthermore, the WID and / or the tool data can be attached, for example in machine-readable form, directly to the tool WZ or the tool holder WZH 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 machine-readable form as follows: storing it in a database (e.g. in the cloud or on an external server); permanently attached to the tool WZ, especially as an engraved or printed 2D code, Temporarily storing the data on the tool WZ, in particular as a printed sticker, the sticker being preferably printed with a 2D code, and / or Storage on a data carrier, in particular an RFID chip, associated with the tool WZ (e.g. attached to the tool).

[0082] The data is preferably physically attached directly to the corresponding tool WZ. This has the advantage that the data is always accessible when the tool WZ is accessible. Encodings that are specially designed for reading by digital devices are particularly advantageous. These include optical encodings, such as in particular 2D codes. To this end, the invention supports both the reading of Data Matrix code encodings and the reading of QR code encodings.

[0083] An alternative variant for attaching the information directly to the tool WZ is the writing of an RFID chip directly integrated into the tool WZ. This variant has the advantage over a database, since it is attached directly to the tool in a similar manner to a 2D code.

[0084] Permanent data storage by laser engraving on the tool has advantages over conventional methods in which an information attachment is attached to the tool, allowing the corresponding information to be separated from the tool or to become incorrect over time or as a result of expected external influences. In comparison to the relevant information being glued with an inscribed sticker, engraving can have advantages. The adhesive side of the sticker can lose its adhesiveness over time or as a result of external influences, resulting in the sticker being lost and the relevant information being unable to be assigned to the tool WZ. Similarly, the sticker or colorant material used for inscription can be damaged by normal work, resulting in the relevant information being assigned to the tool only partially or incorrectly.

[0085] For example, the tool data are retrieved via a direct data connection so that they arrive directly to the machine tool WZM or WZ and are directly available there for further processing, preferably the tool data are stored on the machine tool side after retrieval and used to execute the machining assignment.

[0086] As an example, the NC program is scanned for required tools, e.g., WZ1, WZ2, WZ3 and WZ4, and preferably a difference list is created. The difference list is created by comparing the tools required for the machining assignment with the tools already present, e.g., WZ1 and WZ2. Subsequently, one or more tools to be replaced, e.g., WZ3 and WZ4, are determined based on the difference list. Predetermined setup locations for the replacement are determined for the determined tools, e.g., WZ3 and WZ4. In this case, the setup sequence of the tools is determined according to the machining assignment, and as a result, the loading locations of the tools are determined according to the machining assignment. See also FIG. 7.

[0087] The first step of the loading process is the finding of free space, for example in a machine tool WZM, which comprises, for example, a tool magazine, into which a tool can be loaded. For this purpose, the claimed size of the tool to be loaded is determined, among other things, on the basis of the data stored in the input format. A correspondingly larger free space is then sought. If no such space is found in the machine tool WZM or in the tool magazine, an error message is output explaining the problem. Otherwise, the machine tool WZM or the tool magazine is put into position to allow loading in the corresponding free space.

[0088] In the next step, the tool flap of the machine tool WZM or the tool magazine is opened and instructions are output on how to load the machine tool WZM or the tool magazine. The loading can also proceed in an automated manner. In the automated manner, it is now awaited until the tool flap is closed again. At this point, the corresponding tool must be loaded into the free space of the machine tool WZM or the tool magazine. This can be done manually by the operator or in an automated manner by an external system. Closing the tool flap signals that a tool, e.g. WZ2 or WZ4, has been loaded and the loading process can continue.

[0089] As a final step, it is (optionally) checked whether the tool is correctly loaded. If the check is not negative, a corresponding error message is output explaining the problem. Otherwise, if the check is not positive, this tool loading process is considered to be finished and the next method step is performed. The next method step is, for example, either a further tool loading process or the automatic execution of a machining assignment.

[0090] If the difference list is empty, an automatic machining assignment is performed. Otherwise, one of the missing tools is selected on the difference list and its tool data and identification data are searched for in the input format. The determined setup sequence is preferably maintained during the selection of the tool to be set up from the difference list. Based on these data, the tool loading process is started. After the loading process is successfully completed, the entry of the loaded tool from the list of missing tools is removed and instead added to the list of present tools. This step is repeated until all missing tools are loaded into the difference list and the execution of the order is started.

[0091] In the case of automatic loading, the computer program product can directly use the data in the input format since the tool data contains all information required for loading, inter alia, for example the number of spaces to be occupied in the tool magazine.

[0092] FIG. 3 is a schematic diagram of various abstraction levels from a graphical user interface 233 where an operator sees through a backend, through standardization of data structures, through input devices from multiple different manufacturers, e.g., S1, S2 and S3, in accordance with an exemplary embodiment of the invention.

[0093] The TM UI or front end is preferably a graphical user interface 233 (GUI) for an operator (e.g. with output capabilities via a screen having at least one screen area 233A and with input capabilities via input devices, e.g. with a mouse, a keyboard, one or more touch screens implemented on the screen, soft keys, rotary knobs, rotary knobs and / or keys, etc., and possibly with output capabilities via further output devices, e.g. LED information fields, lights, lamps, warning lights, audio output, etc.).

[0094] 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, the 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 the input format.

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

[0096] FIG. 4 shows, by way of example, a schematic diagram of the exchange of tool data between a machine tool WZM and a tool presetting device WV via the OPC UA protocol.

[0097] The tool data is present on the tool presetting device WV and is uniquely identified in the tool holder WZH, for example via a QR code. The tool WZ is scanned during the method step of scanning S and is thus identified by the scanner. The data of the tool WZ is 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.

[0098] FIG. 5 shows, by way of example, a schematic representation of a 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 IP to a preferably external tool management system. The connection is made via an edge IPC with a generic machine adapter and an 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 be present, by way of example, as a PLC / NC agent and the generic machine adapter is present as a machine communication X. Alternatively, by way of example, the control adapter can be present, by way of example, as a UDI server and the generic machine adapter is present as a UDI client.

[0099] As an example, if a control adapter exists as a UDI server and a generic machine adapter exists as a UDI client, the UDI client provides a request to the UDI server to generate a unique WID that is provided to the tool management system via the OPC UA server, if necessary. In this case, the UDI server ensures that the assigned WID is indeed globally unique.

[0100] FIG. 6 shows, as an example, a schematic order selection screen of the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250.

[0101] By way of example, order selection elements B1-B5 are provided, via which the operator can select orders 1-5. Preferably, the selection of the corresponding orders in the operating device 230 can only be selected according to the order by an operator with sufficient authority. This can be done, for example, based on the operator's competence or training, by different user roles, e.g. simple machine operator, experienced machine operator, machine loader, set-up, machine programmer, machine maintenance provider, multi-machine operator, tool presetter, job creator, factory planner, process standardizer, etc.

[0102] Selection element B6 allows the launching of an editor application for executing a machining step sequence editor, for example, on a 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 further determine or define the sequence of the imported machining step applications and store predefined machining step sequences. This editor functionality can preferably be made available only to operators with a certain authorization.

[0103] The editor preferably indicates, for each machining step application, what input data or input information is required or will be automatically retrieved, what output data or output information is provided, and / or what control functions of the machine tool are to be invoked.

[0104] In a preferred exemplary embodiment, when storing the edited machining step sequence, an automatic plausibility check can be performed, in which the availability of the required input data is checked in an automated manner for each machining step application (data availability check), either by manual input in the editor, by provision as output data of a previous machining step application in a predefined sequence, from the memory of the operating device, from the control device, from the 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, in particular tool data measurement values ​​and / or settings of tools determined by external devices, in particular presetting, balancing or shrinking devices. These specific data are in particular advantageous for an even more accurate use of the tools on the machine tool, and the individual provision of data by automatic data retrieval has the particular advantage that the latest measurement values ​​and / or settings of the tools to be actually exchanged are automatically available on the machine tool and the production sequence can be designed efficiently and accurately.

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

[0106] When executing a predefined machining step sequence on the operating device 230 by the operator, preferably only each machining step application is called and executed in the sequence predefined by the stored or imported machining step sequence, in particular machining step applications cannot be skipped. It is particularly advantageous that the tool data is only retrieved when the tool is actually required in the machining process in the next machining step of the sequence. Thus, the tool data is only retrieved quickly according to the just-in-time principle, which makes it possible to reduce the memory load and the computational power of the control. Optionally, the tool data can be deleted again on the WZM controller after the last use in the machining process and is retrieved again automatically from the external tool management system only when the tool is used again.

[0107] It is particularly advantageous for the WZM to provide the external tool management system with detailed feedback on the use of the (each) tool (duration and extent of use as well as, for example, working temperature, applied force, exceeded limits, etc.), so that the tool history in the external tool management system is always up to date and the tools are always linked to the latest tool data, even when changing to another WZM.

[0108] The execution of a predefined machining step sequence assigned to an order by an operator on the operating device 230 is triggered by the operator by selecting one of the order selection elements B1-B5 assigned to the respective machining assignment, at least as long as his authorization allows this.

[0109] When each machining step application is started by the operator, a new window of the corresponding machining step application can be opened, validity checks (including, for example, data availability checks) can be performed, and machine functions assigned to each machining step application can be executed.

[0110] Furthermore, in a preferred exemplary embodiment, the screen representation assigned to the respective machining step or the control menu assigned to the respective machining step can be automatically called up in another screen area showing the control screen of the control device 240, for example in the screen area 233B. This can be requested or automatically set via the TM UI or the front end.

[0111] The first machining step application (e.g., “Accept Order”) can present order header data to the operator, for example based on the order data of the order to be executed, and the assigned order file is imported by the database server 210.

[0112] By confirming the machining step application (e.g., "Accept Order"), it can be set to the status "RUNNING", which can also be automatically reported to the production monitoring system via the network 200.

[0113] Further (optional) machining step applications may relate to loading of tools or checking tool requirements (see FIG. 7).

[0114] The order data in the order file (e.g., order database) assigned to the corresponding workpiece machining assignment may, for example, indicate one or more of the following header data: work operation designation, 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, an indication of the piece number desired or to be achieved (i.e., the quantity to be produced, for example, in case of similar machining of multiple workpieces one after the other in the same workpiece machining assignment), planned start time, planned end time, planned or calculated machining duration, and optionally optional information in a free text field. Such data may also be provided from an ERP or MES system.

[0115] The data storage device of database server 210, by way of example, optionally stores a plurality of tool files (e.g., tool databases), each tool file providing or indicating information about an assigned tool, such as, for example, one or more of tool dimensions (size, diameter, length, cutting edge type, cutting edge number, etc.), tool type, tool identification number, etc.

[0116] FIG. 7 shows, as an 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.

[0117] In this case, the required tools, e.g. WZ1, WZ2, WZ3 and WZ4, are shown (e.g. based on a tool list file assigned to the order to be executed). Furthermore, based on the data present on the operating device, the tools present on the machine tool WZ, e.g. WZ1 and WZ3, can be displayed, and tools, e.g. WZ2 and WZ4, are still missing or have not yet been loaded.

[0118] By activating selection element B7 "Load tools", the operator can go to tool loading, if necessary, to load missing tools or to enter the relevant tool data (or either import these from the tool data, if already scanned, or import them from a tool presetting device connected to the network 200 after the tool has been scanned S), see for example FIG. 8.

[0119] FIG. 8 shows, as an example, a schematic diagram of a tool loading screen of the graphical user interface of the user interface 233 of the operating device 230 of the machine tool 250.

[0120] The operator can scan the missing tools before loading at the tool station and then enter the data manually, by activating selection element B8 "manual input", or import these from a tool presetting device connected to the network 200, by activating selection element B9 "import from tool station". The input of data as described is particularly advantageously carried out in an automated manner, in particular without the involvement of an operator, during the scanning process in which the tools are exchanged.

[0121] Further (optional) machining step applications can relate to the loading or programming of NC codes. In this case, the NC files assigned to the order are shown (e.g. based on the order data of the assigned order file) and these can be exported to the control device 240 (if necessary after importing the corresponding files from the CAD / CAM system server 220) by activating the corresponding selection element "Load NC files to NC". By selecting the selection element B10 "Edit NC files", the operator can, for example, edit (or create new) the loaded files in the display window located above, at least if the necessary operator permissions are present.

[0122] After tool loading, appropriate clamping means have been set and the NC code provided in a sequence and manner according to the predefined machining step sequence (and after further predefined steps, if appropriate), workpiece machining can take place together with predefined process monitoring, subsequent process documentation, and optional quality checks, if appropriate, until it can be confirmed that the order has been completed or executed in an automated manner at the last machining step.

[0123] It is particularly advantageous for the WZM to provide the external tool management system with detailed feedback on the use of the (each) tool (duration and extent of use as well as, for example, working temperature, applied force, exceeded limits, etc.), so that the tool history in the external tool management system is always up to date and the tools are always linked to the latest tool data, even when changing to another WZM.

[0124] According to one or more of the aforementioned exemplary embodiments, the operation or control of the machine tool can be extended and improved, if necessary, even by a partially untrained or less experienced operator, in particular with regard to maneuverability or automated or semi-automated support of machining steps of a workpiece machining assignment.

[0125] Figure 9 shows a part of the API specification of the input format as an example. The input format is, for example, in JSON format.

[0126] In this case, the "schema" column represents the version number of the input format. It is possible to distinguish between different versions of the input format using the "schema" field. This is particularly advantageous because different versions of the API specification therefore do not need to be compatible with each other.

[0127] Additionally, the "Name" column represents the names by which fields in the input format can be read, created, overwritten, or deleted.

[0128] Additionally, the "Type" column indicates the data type of the field in the input format. The data type defines the binary or human-readable representation in the input format. Furthermore, the data type defines the parsing for converting the field.

[0129] Finally, the "Explanation" column presents a description that an operator can use to interpret the meaning of the fields in the input format.

[0130] Figure 10 shows, by way of example, some of the different specifications of input formats and manufacturer formats required for controlling tool controls and presetting devices. The formats can be converted into one another based on the look-up tables shown.

[0131] In this case, the "Uniform Tool Type" column represents a manufacturer-independent tool type designation, so it is possible to combine equivalent tools from different manufacturers under one term and assign equivalent fields to each other during conversion between different data formats.

[0132] Further, the next columns represent the manufacturers S1, S2, and S3. Each manufacturer column is further subdivided into a "Name", which is the manufacturer's own designation of the tool type, and an "ID", which is a cross-manufacturer ID. The "Name" is respectively specific to a fixed manufacturer, assigned by the manufacturer, and used in the manufacturer's format. In contrast, the "ID" is defined by the input format and the manufacturer's own designation "Name", and the manufacturer S1, S2, or S3, and the manufacturer-independent tool type designation "Uniform Tool Type", can be uniquely resolved based on the ID.

[0133] In summary, the management of tools and tool data in the field of machine tools currently represents a very big challenge, especially since there is currently a great variety of ways in which tools with data can come into contact with the machine. On the machine tool side, for this purpose it is particularly necessary that the tool data can be entered and used for control, and therefore specific data formats exist. For this purpose, different data formats are relevant, for example for CNC or PLC.

[0134] CNC is understood to mean a numerical control that comprises one or more microprocessors for carrying out the control functions. The external identifiers of a CNC are usually a screen and a keyboard. A numerical control (CNC) works with a CNC program that contains all the necessary functions, such as, for example, interpolation, position control and speed control. With the help of one or more microprocessors and the CNC program, a workpiece-dependent CNC part program is executed that is generally specified by the machine user.

[0135] A CNC part program consists of any number of sets that describe the entire work 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. The sets can contain different instructions. Here, a distinction is made between: Geometric instructions by which the relative motion between the tool and the workpiece is controlled; - technical instructions for determining feed rates, spindle speeds and tools, Movement instructions that determine the type of movement, e.g., fast traverse, linear interpolation, circular interpolation, and planar selection; Switching commands for selecting tools, switching table positions, coolant supply, Compensation calls, e.g. tool length compensation, milling diameter compensation, cutting radius compensation and zero point deviation, and Cycle and subprogram calls for frequently repeated program sections.

[0136] In addition to the numerical control, CNC program and CNC part program, an adaptation program for the machine to be controlled (PLC program) is further required, which is created by the machine builder and integrated into a programmable logic controller (PLC). All machine-related links and locks for a specific function sequence are determined therein, e.g. for tool change, workpiece change, axis boundaries, etc.

[0137] For further separation between CNC and PLC, some differences should be highlighted. The CNC part program for machining the workpiece is created by the machine user. The CNC part program can be changed or modified at will by the user. In contrast, the PLC program is created by the machine manufacturer and captured and stored, for example on a read only memory (ROM). The PLC program only needs to be changed or replaced exceptionally. In particular, for PLCs, no programming takes place during operation. The PLC program has to be created for each PLC (programmable logic controller) and is not complicated for other PLC manufacturers. Based on this central difference, it becomes clear that there can be up to several thousand CNC part programs per machine. The CNC part program is created by the machine user, and the canned cycles and subprograms can be reliably supplied by the manufacturer. For PLCs, there is generally only a single fixed, plant-related program. The program is created by the machine manufacturer, usually using available functional modules.

[0138] Machine tools are equipped for each customer, and it is therefore very complicated for a service technician to find out in advance which software version is exactly required for this customer and to find the appropriate software for the respective customer.

[0139] Within a machine tool there are various manufacturers of central components such as PLCs and NCs. Dependencies on manufacturers, versions, updates and special equipment must be managed efficiently to ensure that the right software update for the machine is always used.

[0140] As a result, it is advantageously proposed that a tool management application on the WZM controller (e.g., "tool master") combined with special processing and provision of tool data (e.g., "tool data exchange") creates the possibility of directly connecting the entire WZM system to further data management systems present outside the machine tool, so that, for example, tool data present in a tool measuring device can be obtained and loaded directly into the WZM (or WZM controller or NC control device) via the tool identification information on the machine, so that workflows and tool handling can be negotiated jointly and automatically via the tool data exchange application of the WZM controller.

[0141] Examples or exemplary embodiments of the present invention and its advantages have been described in detail above with reference to the attached drawings. It should be emphasized again that the present invention is in no way limited or restricted to the exemplary embodiments and their features described above, but rather also includes modifications of the exemplary embodiments, in particular modifications consisting of modifications of the features of the described examples or combinations of individual or several features of the described examples, within the scope of protection of the independent claims. [Explanation of symbols]

[0142] Reference symbols list: 100: Communication Networks 110: Web server 200: Communication Network 210: Database server 220: CAD / CAM system server 230: Operating 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 operating device B1, B2, B3, B4, B5: Selection elements for job 1, job 2, job 3, job 4, job 5 B6: Selection elements for editor applications B7: Loading selection elements for tools B8: Selection elements for manual input B9: Selection elements to import from tool station S: Scan S1, S2, S3: 1st, 2nd and 3rd manufacturer tool control WV: Preset device WZ:Tools WZ1, WZ2, WZ3, WZ4: Tool 1, Tool 2, Tool 3, Tool 4 WZH: Tool holder WZM: Machine tool

Claims

1. 1. A method for processing tool data on a machine tool having a data interface for connecting to a tool management system, comprising: Obtaining a unique tool identifier WID of the tool to be picked up; Matching the obtained WID with known tool identification information 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, Automatically retrieving tool data directly from the tool management system based on the acquired WID via the data interface, or automatically retrieving the 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. A method comprising:

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

3. 10. 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 the cloud, and the data interface is a tool data interface connected to the external tool management system via a network connection.

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

5. To generate a difference list, the tools required for a machining assignment are compared with the tools already present; 10. The method according to at least one of the preceding claims, wherein the tool or tools to be replaced are determined based on the difference list.

6. 10. A method according to at least one of the preceding claims, comprising firstly scanning the NC program for required tools and preferably creating a corresponding difference list.

7. 10. The method according to claim 9, wherein a predetermined setup location for the tool to be replaced is determined.

8. 10. The method according to at least one of the preceding claims, further comprising determining a setup sequence for the tools depending on a machining allocation, so that the loading locations of the tools are determined according to the machining allocation.

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

10. 10. The 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 format for retrieval by scanning.

11. 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 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 10. The method according to at least one of the preceding claims, wherein the tool data and / or the WID are stored on a data carrier, in particular an RFID chip, associated with the tool.

12. 13. The 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. the tool data are retrieved via a direct data connection such that they arrive directly to the machine tool and are directly available there for further processing; Method according to at least one of the preceding claims, wherein preferably said tool data is stored at the machine tool side after said retrieval and used for executing said machining assignment.

14. The data interface is a tool data interface that complies with the Open Platform Communications Unified Architecture (UPC UA), 5. The method according to claim 1, wherein the interface comprises an OPC UA server.

15. 10. The method according to claim 9, wherein the Open Platform Communications Unified Architecture (UPC UA) is used for communication with the tool management system, in particular for retrieving the tool data.

16. 5. The method according to claim 1, wherein the tool data is obtained from an OPC UA server via an OPC UA client as an OPC UA service call.

17. 10. The method according to at least one of the preceding claims, wherein the tool data is converted after said retrieval into an input format, said input format being predefined depending on the machine tool controller used.

18. 13. A computer program product comprising instructions which, when said program is executed by a controller of a numerically controlled machine tool, cause said machine tool to perform a method according to at least one of the preceding claims.

19. 1. A control device for a machine tool having a data interface for connecting to a tool management system and to an application based control system, said control device comprising: Get the unique tool identifier WID of the tool to be picked up, Matching the obtained WID with known tool identification information 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, Automatically retrieve tool data directly from the tool management system based on the acquired WID via the data interface, or automatically retrieve the 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. The control device is configured to:

20. The data interface is a tool data interface that complies with the Open Platform Communications Unified Architecture (UPC UA), The control device according to any preceding claim, wherein the interface comprises an OPC UA server.

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

Images