Machine tool management terminal, machine tool, and machine tool remote management system

Abstract

The invention relates to a management terminal of a machine tool, the machine tool and a remote management system of the machine tool, and belongs to the technical field of intelligent manufacturing, and the management terminal of the machine tool is used for being connected with a controller of the machine tool. The management terminal comprises a receiving module, a processing module and a first sending module. The receiving module is used for receiving a processing code file from a cloud platform, wherein the processing code file has a file number regenerated by the cloud platform; the processing module is connected with the receiving module and is used for preprocessing the received processing code file, and the preprocessing comprises the step of correcting grammar and / or lexical in the processing code file; the first sending module is connected with the processing module and used for sending the processing code file preprocessed by the processing module to the controller. By adopting the management terminal of the machine tool, the possibility of confusion and disorder of remotely transmitted processing code files can be reduced.

Description

Technical Field

[0001] This application relates to the field of intelligent manufacturing technology, and in particular to a machine tool management terminal, a machine tool, and a machine tool remote management system. Background Technology

[0002] With the advancement of intelligent manufacturing, the traditional method of transmitting machining codes through storage media such as USB flash drives or CF cards for CNC machine tools can no longer meet the needs of modern factories for efficiency, centralized management, and data security.

[0003] While some industrial computer-based DNC (Distributed Numerical Control) systems in the industry can currently achieve the transmission of machining code between machine tools without relying on storage media to a certain extent, they are usually expensive and consume a lot of power. If a new manufacturing workshop is built, the workload for upgrading and expanding the existing DNC system will be enormous.

[0004] Furthermore, it is well known that the machining code files for a series of products with similar dimensions and specifications contain a great deal of similar content. However, existing DNC systems are prone to problems of confusion and errors in the machining code files remotely sent to the corresponding machine tools.

[0005] Therefore, the current remote management of machine tool machining codes still needs further improvement. Summary of the Invention

[0006] This application aims to at least solve one of the technical problems existing in the prior art. Embodiments of this application provide a machine tool management terminal, a machine tool, and a remote machine tool management system to reduce the possibility of confusion and errors in remotely transmitted machining code files.

[0007] The relevant technical solutions of the embodiments of this application include the following: A first aspect of this application provides a machine tool management terminal. The machine tool management terminal is used to connect to the machine tool's controller, and the management terminal includes: A receiving module is used to receive a processing code file from a cloud platform, wherein the processing code file has a file number regenerated by the cloud platform; A processing module, connected to the receiving module, is used to preprocess the received processing code file, wherein the preprocessing includes correcting the syntax and / or lexical structure of the processing code file; and The first sending module, connected to the processing module, is used to send the preprocessed processing code file to the controller.

[0008] The machine tool management terminal in this embodiment has at least the following technical effects: the machine tool management terminal has a receiving module, a processing module, and a first sending module, wherein the receiving module is used to receive a machining code file from a cloud platform and having a file number regenerated by the cloud platform, and the first sending module is used to send the machining code file to the machine tool's controller. The file number is associated with the machine tool selected by the user through the cloud platform, thereby reducing the possibility of confusion and errors in remotely transmitted machining code files.

[0009] Optionally, the processing module further includes: A CNC language type matching check unit is used to obtain the CNC language type of the machine tool and confirm whether the CNC language type of the received machining code file matches the CNC language type information of the machine tool; and The machining code file correction unit is used to correct the syntax and / or lexical structure in the converted machining code file according to the CNC language type of the machine tool when the CNC language type matches; and to convert the received machining code file into a machining code file consistent with the CNC language type of the machine tool and correct the syntax and / or lexical structure in the converted machining code file when the CNC language type does not match.

[0010] Optionally, the first sending module further includes: A code segmentation unit is used to split the processing code file into multiple segments according to program segment numbers, wherein each segment has a unique segment sequence number and the maximum file size of each segment is a fixed value; or, to identify segment identifiers in the processing code file and split the processing code file into multiple segments according to the segment identifiers, wherein each segment has a unique segment sequence number, and the segment identifiers include a segment start identifier and a segment end identifier; and The segment-by-segment sending unit is used to send multiple segments of the machining code file to the controller of the machine tool one by one at a predetermined rate.

[0011] Optionally, the segment-by-segment transmission unit further includes: A breakpoint resume instruction generation subunit is used to generate a breakpoint resume instruction in response to a resume request from the controller of the machine tool, wherein the resume request includes a breakpoint sequence number, which is the segment sequence number of the last machining code file that has been fully received. A segment-by-segment recovery subunit is used to continue sending the processing code file segment by segment to the machine tool controller, starting from the next segment sequence number of the breakpoint sequence number, according to the breakpoint resume instruction.

[0012] Optionally, the receiving module further includes: The session key negotiation unit is used to perform two-way authentication and session key negotiation with the cloud platform using an asymmetric encryption algorithm. The processing code file receiving unit is used to receive the processing code file sent by the cloud platform and encrypted using a symmetric encryption algorithm through a data transmission security channel; The processing code file decryption unit is used to decrypt the processing code file using the key obtained through session key negotiation.

[0013] Optionally, the management terminal includes an ARM-based processor and is configured with a Linux system.

[0014] A second aspect of this application provides a machine tool. The machine tool includes a controller and a management terminal for the machine tool according to any technical solution of the first aspect of this application, wherein the management terminal is connected to the controller.

[0015] A third aspect of this application provides a remote management system for machine tools. The remote management system includes a cloud platform and a plurality of machine tools as described in the second aspect of this application. The cloud platform is communicatively connected to a management terminal in each of the machine tools. The cloud platform includes: The processing code file acquisition module is used to acquire the uploaded processing code file and assign a corresponding file number to the processing code file according to preset rules; and The second sending module is used to send machining code files to the management terminal of the corresponding machine tool, wherein the machining code files have an assigned file number.

[0016] Optionally, the cloud platform further includes a file number association module, which is used to establish an association between the file number of the machining code file to be sent and the selected machine number in response to the operation of selecting the machine number as the receiving object; The second sending module is used to send the associated version of the machining code file to the management terminal of the corresponding machine tool according to the association relationship.

[0017] Optionally, the acquired processing code file has an original file number including the file name, and the processing code file acquisition module further includes: The file naming matching confirmation unit is used to confirm whether there are other processing code files in the historical storage database that have the same file name as the processing code file obtained this time; The first unit of file number allocation is used to assign a file number to the processing code file obtained this time as the initial version when there are no other processing code files with the same file name; The second unit for file number allocation is used to assign a file number to the processing code file obtained this time, which is different from other processing code files, based on the order of completion time or upload time among all processing code files with the same file name, when other processing code files with the same file name exist.

[0018] The other aspects (machine tool and machine tool remote management system) in the embodiments of this application also have at least the technical effects of the machine tool management terminal in the foregoing embodiments, and will not be repeated here.

[0019] Additional aspects and advantages of this application will be set forth in part in the description which follows. Some will become apparent from the description, or may be learned by practice of this application. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the modules of the machine tool remote management system in the embodiments of this application; Figure 2 This is a schematic diagram of the receiving module in the management terminal of the machine tool in this embodiment of the application; Figure 3 This is a schematic diagram of the processing module in the management terminal of the machine tool in the embodiments of this application; Figure 4 This is a schematic diagram of the first sending module in the management terminal of the machine tool in the embodiments of this application; Figure 5 This is a schematic diagram of the processing code file acquisition module in the cloud platform in this application embodiment. Detailed Implementation

[0021] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar components or components having the same or similar functions throughout.

[0022] The embodiments described in this application with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application. The technical solutions of the various embodiments of this application can be combined with each other, but should be based on what those skilled in the art can implement.

[0023] In the description of this application, the term "multiple" means at least two. Unless otherwise specified, "connection" means at least a communication connection or coupling between program modules, wherein "communication connection" means the transmission and exchange of information through a medium, and communication connections include wired connections and wireless connections.

[0024] In this application, terms such as “first” or “second” are used only for distinguishing purposes and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated.

[0025] One aspect of this application provides a remote machine tool management system. For example... Figure 1 As shown, the machine tool remote management system includes a machine tool management terminal 100, a cloud platform 200, and a machine tool controller 300. Through the machine tool management terminal 100, the cloud platform 200 can remotely transmit machining code files to the machine tool controller 300.

[0026] In some embodiments of this application, the machine tool remote management system includes a cloud platform 200 and multiple machine tools, wherein each machine tool has at least one management terminal 100 and one controller 300, both of which are installed on the machine tool body. The cloud platform 200 is communicatively connected to the management terminal 100 in each machine tool. The management terminal 100 is connected to the controller 300.

[0027] like Figure 1 As shown, the machine tool management terminal 100 includes a receiving module 110, a processing module 130, and a first sending module 150. The cloud platform 200 includes a machining code file acquisition module 210 and a second sending module 230.

[0028] The machining code file acquisition module 210 in the cloud platform 200 is used to acquire the uploaded machining code files and assign corresponding file numbers to the machining code files according to preset rules. After completing CNC programming, the user uploads the machining code files to the cloud platform 200. However, the machining code files uploaded by the user may have inconsistent naming conventions that could lead to confusion. Therefore, the cloud platform 200 assigns corresponding file numbers to the machining code files according to preset rules, which helps reduce the possibility of confusion and errors between different machining code files.

[0029] The second sending module 230 in the cloud platform 200 is used to send the processing code file to the corresponding management terminal 100, wherein the processing code file has an assigned file number.

[0030] The receiving module 110 in the machine tool management terminal 100 is used to receive machining code files from the cloud platform, wherein the machining code files have file numbers regenerated by the cloud platform. After the user uploads the machining code file to the cloud platform, the cloud platform reassigns a corresponding file number to the machining code file according to preset rules, and the machining code file received by the receiving module 110 has the original file number. It can be understood that the file number may include file naming and version information, etc.

[0031] The processing module 130 in the machine tool's management terminal 100 is connected to the receiving module 110. The processing module 130 is used to preprocess the received machining code file, wherein the preprocessing includes correcting the syntax and / or lexical structure in the machining code file. In some cases, machining code files uploaded by users to the cloud platform and then received by the management terminal 100 may contain syntax errors or lexical errors, or there may be situations where the syntax or lexical structure is correct in one CNC language type (e.g., Siemens CNC language) but not applicable in another CNC language type (e.g., Mitsubishi CNC language). Therefore, the processing module 130 is used to correct errors or convert the CNC language type used in the machining code file to a CNC language type adapted to the selected machine tool.

[0032] The first sending module 150 in the machine tool's management terminal 100 is connected to the processing module 130. The first sending module 150 is used to send the machining code file, which has been preprocessed by the processing module 130, to the controller. Since the management terminal 100 is connected to the controller of the machine tool itself, a one-to-one correspondence is formed between the two. After receiving the machining code file, the management terminal 100 can directly send it to the controller connected to it.

[0033] For specific details regarding the machine tool management terminal 100 and the cloud platform 200, please refer to the descriptions in other embodiments of this application below.

[0034] In this embodiment, the machine tool management terminal 100, cloud platform 200, and machine tool controller 300 constitute a machine tool remote management system. The machine tool management terminal 100 includes a receiving module 110, a processing module 130, and a first sending module 150. The receiving module 110 receives machining code files from the cloud platform that have a file number regenerated by the cloud platform, while the first sending module 150 sends the machining code files to the machine tool controller. The file number is associated with the machine tool selected by the user through the cloud platform, thereby reducing the possibility of confusion or errors in remotely transmitted machining code files.

[0035] Furthermore, the machine tool remote management system in this application uses a cloud platform 200 to interact with the machine tool's management terminal 100, instead of using an industrial control computer or similar physical server, thus reducing costs and significantly lowering power consumption. Based on the cloud platform 200, upgrading and expanding existing machine tool remote management systems is simple and convenient.

[0036] Another aspect of this application provides a machine tool. The machine tool includes a controller 300 and a management terminal 100 for the machine tool according to any technical solution of one aspect of this application, wherein the management terminal 100 is connected to the controller 300. Specific details of the machine tool management terminal 100 are described in conjunction with the following descriptions of embodiments in other aspects of this application.

[0037] Another aspect of this application provides a machine tool management terminal 100. The machine tool management terminal 100 is used to connect to a controller 300 inherent in the machine tool itself; that is, both the management terminal 100 and the controller 300 are installed on the machine tool body. Figure 1 As shown, the management terminal 100 includes a receiving module 110, a processing module 130, and a first transmitting module 150, wherein at least one of the three is electrically connected, communicatively connected, or coupled to the first transmitting module 150 through the processing module 130. In some typical embodiments, the management terminal 100 may include a communication gateway. A communication gateway, also known as an internetwork connector or protocol converter, is a computer system or electronic device used to realize data conversion between different networks, typically supporting protocol translation, data repackaging, and security filtering functions.

[0038] The receiving module 110 receives a processing code file from the cloud platform 200, wherein the processing code file has a file number regenerated by the cloud platform 200. The processing module 130 is connected to the receiving module 110 and is used to preprocess the received processing code file, wherein the preprocessing includes correcting the syntax and / or lexical structure in the processing code file. The first sending module 150 is connected to the processing module 130 and is used to send the preprocessed processing code file to the controller.

[0039] Optionally, in some embodiments of this application, the management terminal 100 includes an ARM-based processor and is configured with a Linux system.

[0040] Specifically, the management terminal 100 can be a communication gateway, which has a memory and a processor, wherein the processor has an ARM architecture. The management terminal 100 is configured with a lightweight embedded Linux system. The management terminal 100 can establish a connection with the cloud platform via Ethernet, Wi-Fi, 4G or 5G, and can also establish a connection with the machine tool controller via RS232, RS485 or Ethernet.

[0041] Optionally, in some embodiments of this application, such as Figure 2 As shown, the receiving module 110 further includes a session key negotiation unit 111, a processing code file receiving unit 113, and a processing code file decryption unit 115.

[0042] The session key negotiation unit 111 is used to perform two-way authentication and session key negotiation with the cloud platform using an asymmetric encryption algorithm. The public / private key mechanism of the asymmetric encryption algorithm (public key is public, private key is confidential) can transmit keys more securely over relatively insecure networks.

[0043] The processing code file receiving unit 113 is used to receive the processing code file sent by the cloud platform and encrypted using a symmetric encryption algorithm via a secure data transmission channel. Asymmetric encryption algorithms offer stronger security than symmetric encryption algorithms. Symmetric encryption algorithms are faster than asymmetric encryption algorithms and are more suitable for processing large amounts of data.

[0044] The processing code file decryption unit 115 is used to decrypt the processing code file using the key obtained through session key negotiation.

[0045] Optionally, in some embodiments of this application, such as Figure 3 As shown, the processing module 130 further includes a CNC language type matching check unit 131 and a machining code file correction unit 133.

[0046] The CNC language type matching check unit 131 is used to obtain the CNC language type of the machine tool and confirm whether the CNC language type of the received machining code file matches the CNC language type information of the machine tool.

[0047] Specifically, when uploading the completed machining code file to the cloud platform, the user inputs the identifier of the CNC language type of the machining code file into the cloud platform or selects the identifier of the CNC language type of the machining code file on the operation interface of the terminal device. The identifier of the CNC language type of the machining code file, along with the machining code file itself, is received by the receiving module 110 in the management terminal 100.

[0048] Even if the user does not disclose the CNC language type information of the machining code file, the CNC language type matching and checking unit 131 in the management terminal 100 can also check the program structure or identify specific instructions. The program structure check includes viewing the format of the beginning and end of the program in the machining code file; the identification of specific instructions includes identifying representative instructions (e.g., cycle instructions, tool radius compensation instructions, or G-codes).

[0049] The machine tool controller can send an identifier representing the CNC language type of the machine tool to the CNC language type matching and checking unit 131 in the management terminal 100. For example, "01" represents the Mitsubishi CNC system, "02" represents the Siemens CNC system, etc.

[0050] The machining code file correction unit 133 is used to correct the syntax and / or lexical structure in the converted machining code file according to the CNC language type of the machine tool when the CNC language type matches; and to convert the received machining code file into a machining code file consistent with the CNC language type of the machine tool when the CNC language type does not match (for example, converting the received machining code file written in Mitsubishi CNC language into a machining code file consistent with the CNC language type of the Siemens CNC system of the machine tool), and correct the syntax and / or lexical structure in the converted machining code file.

[0051] Optionally, in some embodiments of this application, such as Figure 4 As shown, the first sending module 150 further includes a code segmentation unit 151 and a segment-by-segment sending unit 153.

[0052] Currently, some machine tool controllers have limited memory capacity, making it difficult to receive and execute large machining code files all at once. The code segmentation unit 151 is used to split the machining code file into multiple segments, so that the segment-by-segment sending unit 153 can send the multiple segments one by one.

[0053] The code segmentation unit 151 is used to split the processing code file into multiple segments according to the program segment numbers, wherein each segment has a unique segment sequence number and the upper limit of the file size of each segment is a fixed value. Typically, the processing code file itself has a program segment number for each program segment, such as N10, N20, ... Specifically, the code segmentation unit 151 automatically divides program segment numbers at fixed intervals into multiple segments. For example, segment 01 corresponds to program code with program segment numbers N10 to N30, i.e., segment sequence number 01. The content of the initially divided segment sequence number 01 corresponds to program code with program segment numbers N10, N20, and N30 respectively. It can be understood that the content of the initially divided segment sequence number 02 corresponds to program code with program segment numbers N40, N50, and N60 respectively. The initial segment sequence numbers 01 and 02 are N10 to N30 and N40 to N60 respectively, so the interval between their segment numbers is the same. However, the file size of each initially divided segment may vary. Therefore, an upper limit (e.g., 128KB) should be set for the file size of each segment. If the file size of a segment exceeds this upper limit, the segment is reduced in size based on its segment number to re-divide into multiple segments. For example, if the segment size from N40 to N60 exceeds the upper limit, the start and end segment numbers of that segment are adjusted to N40 to N50, and the size of the newly divided segment represented by sequence number 02 is rechecked to see if it exceeds the upper limit. If it still exceeds the upper limit, the adjustment continues.

[0054] Understandably, users can also manually set segment identifiers in the machining code file while programming. These segment identifiers effectively perform a manual segmentation of the machining code file. This manual segmentation typically ensures that the size of each segment does not exceed the machine tool's controller memory capacity.

[0055] Therefore, in some embodiments of this application, the code segmentation unit 151 is used to identify the segmentation identifier in the processing code file and split the processing code file into multiple segments according to the segmentation identifier, wherein each segment has a unique segmentation sequence number, and the segmentation identifier includes a segmentation start identifier and a segmentation end identifier.

[0056] The segment-by-segment transmission unit 153 is used to transmit multiple segments of the machining code file to the machine tool controller one by one at a predetermined rate. Specifically, each segment is transmitted to the machine tool controller one by one according to a rate matching the baud rate set by the machine tool controller. The baud rate is the number of bits transmitted per second; for example, 300 baud means 300 bits are transmitted per second.

[0057] Optionally, in some embodiments of this application, such as Figure 4 As shown, the segment-by-segment transmission unit 153 further includes a breakpoint resume instruction generation subunit 1531 and a segment-by-segment transmission recovery subunit 1533.

[0058] The breakpoint resume instruction generation subunit 1531 is used to generate a breakpoint resume instruction in response to a resume request from the machine tool controller, wherein the resume request includes a breakpoint sequence number, which is the segment sequence number of the last machining code file that has been fully received.

[0059] Specifically, when the transmission of the machining code file is interrupted, the machine tool controller records the sequence number of the last successfully received segment, which is the breakpoint information. This breakpoint information is recorded in non-volatile memory.

[0060] When the remote transmission of the machining code file is restored, the machine tool controller sends a resume request to the management terminal 100, which includes the segment sequence number of the last machining code file that has been fully received.

[0061] The segment-by-segment transmission recovery subunit 1533 is used to continue transmitting the processing code file segment by segment to the machine tool controller according to the breakpoint continuation instruction, starting from the segment of the processing code file next to the breakpoint sequence number.

[0062] Furthermore, in some embodiments of this application, the segment-by-segment transmission unit 153 further includes a transmission status detection subunit, wherein the transmission status detection subunit is used to send a network connection detection request to the controller of the machine tool, and the network connection detection request will carry a test data packet of a certain size.

[0063] The transmission status detection subunit is also used to determine that the transmission status is abnormal if it does not receive a return log of the data received from the machine tool controller within a preset time period, or if the data packet size information in the return log received within a preset time period is inconsistent with the data packet information sent.

[0064] The transmission status detection subunit is also used to repeatedly send network connection detection requests to the machine tool controller after a certain period of time when the transmission status is determined to be abnormal, and to judge whether the transmission status is abnormal until the transmission status is determined to be normal.

[0065] Another aspect of the embodiments of this application relates to a cloud platform 200. For example... Figure 5 As shown, the cloud platform 200 also includes a file number association module 250, which is used to establish an association between the file number of the machining code file to be sent and the selected machine number in response to the operation of selecting the machine number as the receiving object.

[0066] Understandably, after the machining code file acquisition module 210 in the cloud platform 200 assigns a corresponding file number to the machining code file uploaded by the user according to preset rules, the user can select on the terminal device which machine tool the machining code file with that file number will be remotely sent to. The user's selection of the machine tool number as the recipient establishes an association request between the file number of the machining code file to be sent and the selected machine tool number. This association request is received by the file number association module 250 in the cloud platform 200, thereby establishing the association between the file number of the machining code file to be sent and the selected machine tool number. Specifically, the file number association module 250 records and stores the file number of the machining code file to be sent and the selected machine tool number in the association database, and constructs them into a set of association data. For example, "(XXXXX-V0, 067)" indicates that the machining code file with file number "XXXXX-V0" is associated with the machine tool with number "067". The association data is then sent to the second sending module 230.

[0067] The second sending module 230 is used to send the associated version of the machining code file to the corresponding management terminal 100 according to the association relationship. Specifically, the second sending module 230 sends the associated version of the machining code file to the management terminal 100 corresponding to the machine tool number according to the content of the received association data, thereby reducing the possibility of confusion and errors in the remotely transmitted machining code file.

[0068] Optionally, in some embodiments of this application, the acquired processing code file has an original file number including a file name, and the processing code file acquisition module 210 further includes a file name matching confirmation unit 211, a file number allocation first unit 213, and a file number allocation second unit 215. It is understood that the processing code file uploaded by the user to the cloud platform 200 includes a file name, meaning the initial file name of the processing code file can be named by the user. The file number allocation first unit 213 and the file number allocation second unit 215 are used to reassign a corresponding file number to the processing code file according to preset rules. The preset rules are: if no other processing code files with the same file name exist, the acquired processing code file is reassigned a file number to serve as the initial version; if other processing code files with the same file name exist, the acquired processing code file is reassigned a file number different from other processing code files based on the order of completion time or upload time among all processing code files with the same file name.

[0069] The file name matching confirmation unit 211 is used to confirm whether there are other processing code files in the historical storage database that have the same file name as the processing code file obtained this time.

[0070] The first unit 213 for file number allocation is used to reassign the file number of the currently obtained processing code file as the initial version when there are no other processing code files with the same file name. For example, the reassigned file number is named "XXXXX-V0".

[0071] The second unit 215 for file number allocation is used to reassign a file number to the processing code file obtained this time, based on the order of completion time or upload time of all processing code files with the same file name, when other processing code files with the same file name exist. For example, the reassigned file number is named "XXXXX-V2".

[0072] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. Any combination of technical features that does not contradict each other should be considered within the scope of this application.

[0073] Those skilled in the art will understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A management terminal for a machine tool, used to connect to the controller of the machine tool, characterized in that, The management terminal includes: A receiving module is used to receive a processing code file from a cloud platform, wherein the processing code file has a file number regenerated by the cloud platform; A processing module, connected to the receiving module, is used to preprocess the received processing code file, wherein the preprocessing includes correcting the syntax and / or lexical structure of the processing code file; and The first sending module, connected to the processing module, is used to send the preprocessed processing code file to the controller.

2. The machine tool management terminal according to claim 1, characterized in that, The processing module further includes: A CNC language type matching check unit is used to obtain the CNC language type of the machine tool and confirm whether the CNC language type of the received machining code file matches the CNC language type information of the machine tool; and The machining code file correction unit is used to correct the syntax and / or lexical structure in the converted machining code file according to the CNC language type of the machine tool when the CNC language type matches; and to convert the received machining code file into a machining code file consistent with the CNC language type of the machine tool and correct the syntax and / or lexical structure in the converted machining code file when the CNC language type does not match.

3. The machine tool management terminal according to claim 1, characterized in that, The first sending module further includes: A code segmentation unit is used to split the processing code file into multiple segments according to program segment numbers, wherein each segment has a unique segment sequence number and the maximum file size of each segment is a fixed value; or, to identify segment identifiers in the processing code file and split the processing code file into multiple segments according to the segment identifiers, wherein each segment has a unique segment sequence number, and the segment identifiers include a segment start identifier and a segment end identifier; and The segment-by-segment sending unit is used to send multiple segments of the machining code file to the controller of the machine tool one by one at a predetermined rate.

4. The machine tool management terminal according to claim 3, characterized in that, The segment-by-segment transmission unit further includes: A breakpoint resume instruction generation subunit is used to generate a breakpoint resume instruction in response to a resume request from the controller of the machine tool, wherein the resume request includes a breakpoint sequence number, which is the segment sequence number of the last machining code file that has been fully received. A segment-by-segment recovery subunit is used to continue sending the processing code file segment by segment to the machine tool controller, starting from the next segment sequence number of the breakpoint sequence number, according to the breakpoint resume instruction.

5. The machine tool management terminal according to any one of claims 1 to 4, characterized in that, The receiving module further includes: The session key negotiation unit is used to perform two-way authentication and session key negotiation with the cloud platform using an asymmetric encryption algorithm. The processing code file receiving unit is used to receive the processing code file sent by the cloud platform and encrypted using a symmetric encryption algorithm through a data transmission security channel; The processing code file decryption unit is used to decrypt the processing code file using the key obtained through session key negotiation.

6. The machine tool management terminal according to claim 5, characterized in that, The management terminal includes an ARM-based processor and is configured with a Linux system.

7. A machine tool, including a controller, characterized in that, It also includes a management terminal for the machine tool according to any one of claims 1 to 6, the management terminal being connected to the controller.

8. A remote machine tool management system, including a cloud platform, characterized in that: It also includes multiple machine tools according to claim 7, wherein the cloud platform is communicatively connected to the management terminal in each of the machine tools, wherein the cloud platform includes: The processing code file acquisition module is used to acquire the uploaded processing code file and assign a corresponding file number to the processing code file according to preset rules; and The second sending module is used to send machining code files to the management terminal of the corresponding machine tool, wherein the machining code files have an assigned file number.

9. The machine tool remote management system according to claim 8, characterized in that, The cloud platform also includes a file number association module, which is used to establish an association between the file number of the machining code file to be sent and the selected machine number in response to the operation of selecting the machine number as the receiving object. The second sending module is used to send the associated version of the machining code file to the management terminal of the corresponding machine tool according to the association relationship.

10. The machine tool remote management system according to claim 9, characterized in that, The acquired processing code file has an original file number including the file name, and the processing code file acquisition module further includes: The file naming matching confirmation unit is used to confirm whether there are other processing code files in the historical storage database that have the same file name as the processing code file obtained this time; The first unit of file number allocation is used to reassign the file number of the processing code file obtained this time as the initial version when there are no other processing code files with the same file name; The second unit for file number allocation is used to reassign a file number to the newly acquired processing code file, based on the order of completion time or upload time among all processing code files with the same file name, when other processing code files with the same file name exist.

Images