Management system and method for numerical control equipment

Abstract

The invention relates to the technical field of information, in particular to a management system and method for numerical control equipment, and the system comprises a general protocol matching module which matches and dispatches an equipment data model file corresponding to a preset database according to a configuration file, and imports an equipment data model file of third-party equipment from an external interface; the general protocol conversion module is used for providing equipment access interfaces for different target numerical control equipment, docking with communication protocols of the different target numerical control equipment, converting the communication protocols of the different target numerical control equipment into general communication protocols and issuing data to the different target numerical control equipment; and the application service module is used for docking a client through a general protocol of the system and providing a service interface and a human-computer interface. Communication protocols of different devices can be converted into the same communication protocol interface, so that the difference of protocols of various numerical control systems is solved, centralized management of a plurality of numerical control devices is realized, and the states of the devices are convenient to monitor and maintain.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a management system and method for numerical control equipment. Background Art

[0002] In the machining workshop, during the application of automated production lines, workers need to monitor the different CNC equipment in the production line: CNC machine tools and industrial robots in real time to ensure the stability of production. When the production line changes to a new type of workpiece, on-site workers are also required to change the processing procedures and parameter modifications corresponding to the machine tools. However, due to the large number of CNC machine tools and robots, the harsh production environment in the workshop, and the safety of the robot's range of motion, it is not convenient for workers to monitor the equipment at close range for a long time and manage and operate multiple machine tools and robots, which leads to problems such as low efficiency and low safety of automated production lines.

[0003] At present, there are differences in the communication interfaces of different CNC devices, and there are also differences in the protocols of different CNC systems. The existing CNC equipment management system does not have an interface to convert the communication protocols of different devices into the same communication protocol, which makes it inconvenient to achieve unified management of CNC equipment of different models, and cannot meet the needs of providing external data acquisition, third-party software communication, and secondary development. Summary of the invention

[0004] In order to solve the technical problems existing in the prior art, the present invention provides a management system and method for CNC equipment, which can solve the differences in the communication interfaces of various CNC equipment, solve the differences in the protocols of various CNC systems, achieve unified data collection, and transform the original management of a single device from data collection to the management of multiple devices on the platform.

[0005] A management system for numerical control equipment, comprising a general protocol matching module, a general protocol conversion module, a middleware module, and an application service module.

[0006] The general protocol matching module is used to input the device information of the target CNC device and generate a configuration file. Each configuration file matches the device data model file corresponding to the scheduling preset database. When the preset database does not have the corresponding device data model file, the device data model file of the third-party device is imported from the external interface;

[0007] The universal protocol conversion module is used to provide device access interfaces for different target CNC devices, connect with the communication protocols of different target CNC devices, and convert the communication protocols of different target CNC devices into universal communication protocols; users send data to different target CNC devices through universal communication protocols;

[0008] Middleware module, used to complete task scheduling, database management and file management between the general protocol matching module, application service module, general protocol conversion module and application service module respectively;

[0009] The application service module is used to connect to the client through the system's general protocol and provide service interfaces and human-machine interface for specific application services of CNC equipment based on workshop management services.

[0010] Specifically, the communication protocols of different target numerical control devices are converted into a universal communication protocol, including the steps of:

[0011] Update the protocol data, schedule the corresponding communication protocol file according to the device driver file of the CNC device, create the protocol item class corresponding to the CNC device, and create a process to communicate with the CNC device;

[0012] Find the object instance corresponding to the protocol, find the data object instance of the communication protocol file of the corresponding numerical control device, and create its application unit data according to the data object instance of the communication protocol file of the numerical control device and the device data model;

[0013] Protocol decoding and conversion, generating protocol object model information according to the protocol item class corresponding to the numerical control equipment, and generating protocol object instances in the general protocol converter;

[0014] Update the protocol object instance data, receive the subscription SDO service data object data from the middleware, and convert the subscription SDO service data object data into a data format representation based on the JSON format according to the object instance content of the communication protocol of the corresponding CNC device;

[0015] Call the middleware module to update the function of the protocol converter object and update the SDO service data object data, and convert the collected device data into a JSON data structure for storage.

[0016] Specifically, the step of sending data to different target numerical control devices through a universal communication protocol includes:

[0017] Receive object instance data, obtain the number of instructions for controlling the CNC equipment input by the user from the application service module through middleware scheduling, and subscribe to the SDO service data object data sent by the receiving middleware;

[0018] According to the data object instance content of the communication protocol of the corresponding CNC device, it is converted into a data format representation based on the JSON format;

[0019] Update the protocol corresponding to the object instance data, obtain the protocol item class corresponding to the CNC device according to the communication driver of the CNC device, and the general protocol conversion module schedules the corresponding communication protocol file and creates a process according to the corresponding device type to achieve communication connection with the CNC device;

[0020] Protocol decoding and conversion, mapping the protocol items and object model information types to the protocol items corresponding to the SDO service data objects, refreshing the protocol format information in the protocol items, and calling the underlying communication interface function to send the protocol item data to the CNC equipment;

[0021] Update protocol data, associate with the background database according to the device configuration file, schedule the device data model, receive externally imported third-party device model files through the file interface, decode the third-party device model files, create target device data and protocol conversion process, and communicate with CNC equipment.

[0022] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0023] The present invention provides a management system and method for numerical control equipment. The present invention converts the communication protocols of different equipment into the same communication protocol interface through a universal protocol conversion module, so as to meet the needs of providing external data acquisition, third-party software communication, and secondary development; it can solve the differences in the communication interfaces of various numerical control equipment, solve the differences in the protocols of various numerical control systems, achieve unified data collection, and transform the original management of a single device from data collection to the management of multiple devices on the platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0025] Figure 1 is a diagram of the architecture of a numerical control equipment management system in an embodiment of the present invention;

[0026] Figure 2 is a general protocol configuration module scheduling flow chart in an embodiment of the present invention;

[0027] Figure 3 is a general protocol conversion module application flow chart in an embodiment of the present invention;

[0028] Figure 4 It is an application architecture diagram of the management system and external numerical control equipment in an embodiment of the present invention. DETAILED DESCRIPTION

[0029] The technical solution of the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is obvious that the described embodiments are part of the embodiments of the present invention, not all of the embodiments, and the implementation of the present invention is not limited to this. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0030] Embodiment 1:

[0031] The present invention provides a management system for numerical control equipment, which realizes external data collection of numerical control equipment through a general protocol matching module, automatically matches the communication protocol of the numerical control equipment, and realizes communication with the numerical control equipment. The different communication protocols and different data models of different numerical control equipment are converted into the same communication protocol and data model through the general protocol conversion module, which can solve the differences in the communication interfaces of various numerical control equipment, solve the differences in the protocols of various numerical control systems, achieve unified data collection, and realize a method for collecting data of multiple numerical control equipment; database management and file management are performed through middleware, and the collected numerical control equipment data is persisted, which can provide a basis for more applications. For example, according to the storage time, the application of the start-up rate and processing time optimization of the equipment in different time periods is statistically classified from the time, and the original management of a single device is collected from the data to the management of multiple devices on the platform. The application service module provides a service interface for the application business of the numerical control equipment, sends operation instructions to the numerical control equipment, and thus realizes the application business.

[0032] like Figure 1 As shown in the architecture diagram of the numerical control equipment management system, the management system of the numerical control equipment includes: a general protocol matching module, a general protocol conversion module, a middleware and an application service module, wherein:

[0033] The general protocol matching module is used to input the device information of the target CNC device and generate a configuration file. Each configuration file matches the device data model file corresponding to the scheduling preset database. When the preset database does not have the corresponding device data model file, the device data model file of the third-party device is imported from the external interface.

[0034] Specifically, the device information to be entered into the target CNC device includes the communication protocol information and device data model information on the CNC device. Currently, common CNC device hardware generally has a communication interface, such as an RJ45 network port, and has its own device data model for internal use of the machine. Through a certain communication protocol, the device data model can also be transmitted through the communication interface to an external third party for use. For CNC devices of different brands, types, and uses, there are various communication protocols and different device data models.

[0035] In this embodiment, entering the device information of the target CNC device and generating a configuration file specifically includes: entering the device type, device ID number, device model, device IP address, device data model and communication protocol name (device layer protocol name) of the target CNC device. After entering the configuration information of the target CNC device, the configuration data is submitted to the general protocol conversion module and middleware according to the business logic, and the device configuration file is generated and saved. After the device configuration file is saved, it is written into the database to make the data persistent.

[0036] like Figure 2 As shown in the figure, the scheduling flow chart of the general protocol configuration module is shown. The configuration information is associated with the database, the corresponding device driver is scheduled through the database, and the corresponding communication protocol is selected according to the corresponding device driver; when the corresponding device driver cannot be scheduled through the database, the third-party device data model file is imported through the third-party file interface to select the corresponding communication protocol.

[0037] The device data model file includes: model file and device driver file. The model file is used for data model description and includes XML format and JSON format. The device driver file is used for device communication driver and includes DLL format. The process is the same as the content of the general protocol conversion module. The difference is that the communication driver file and data model file used are specified external third-party import files, rather than standard files built into the files selected by the general protocol matching module. After importing the third-party device model file, decode the third-party device model file to achieve the creation of the target device data model and communication protocol conversion process. Parse the third-party device model file and read the file content. For example, if its content is described in JSON format, obtain the target field value according to the JSON key-value pair, create a new JSON key-value pair, write the field value into the new JSON structure, and achieve the new JSON data model conversion.

[0038] The universal protocol conversion module is used to provide device access interfaces for different target CNC devices, connect with the communication protocols of the target CNC devices, and convert the communication protocols of different target CNC devices into universal communication protocols; send data to different target CNC devices through universal communication protocols, and realize unified data models and communication protocol conversion of target CNC devices.

[0039] The purpose of the communication protocol conversion process includes two parts: conversion between protocols, that is, using matching DLL files (syntax conversion); conversion of data formats under different services between protocols (content conversion), using JSON format.

[0040] In this embodiment, a numerical control device based on the Modbus communication protocol is used as an example for illustration. For numerical control devices with other different communication protocols, the corresponding device driver will be selected, and then the communication protocol of the corresponding numerical control device will be converted into a universal communication protocol HTTP protocol with a unified target, including the process from the numerical control device (Modbus protocol) to the client of the universal protocol (HTTP protocol), and then the client (HTTP protocol) sends data to the numerical control device (Modbus protocol).

[0041] like Figure 3 As shown, the general protocol conversion module application flow diagram: the steps of converting the communication protocol (Modbus protocol) of the numerical control equipment into the general communication protocol (HTTP protocol) include:

[0042] Update the protocol data, schedule the corresponding communication protocol file according to the device driver file of the CNC device, create the protocol item class corresponding to the CNC device, and create a process to communicate with the CNC device.

[0043] Specifically, the general protocol conversion module searches for the protocol item class corresponding to the corresponding numerical control device according to the device driver file of the numerical control device. The protocol item class of the numerical control device includes the protocol name, the target device of the protocol item, the dynamic frame identifier of the protocol item, the position of the number of dynamic frames of the protocol item, the dynamic maximum number of the protocol item, the remarks of the protocol item, the header group of the protocol frame, the tail group of the protocol frame, the element group of the protocol item, etc. According to the IP address information configured in the configuration protocol information, a process is created to communicate with the numerical control device.

[0044] Find the object instance corresponding to the protocol, find the data object instance of the communication protocol file of the corresponding CNC device (that is, the Modbus protocol in this example), and create its application unit data based on the data object instance of the communication protocol file of the CNC device and the device data model. The application unit data contains the current CNC device data model, and the main information includes data description, address number range, data length, and supported operation function codes.

[0045] Protocol decoding and conversion generates protocol object model information according to the protocol item class corresponding to the CNC device, and generates the protocol object instance in the general protocol converter.

[0046] The protocol object model information includes: object model name, timestamp identifier, protocol attribute list: includes the transaction processing identifier, protocol identifier, unit identifier and other message header information in the CNC equipment communication protocol, protocol event list, and protocol format.

[0047] Update the object instance data, receive the subscribed SDO service data object data (ServiceData Obiect) from the middleware, and convert the subscribed SDO data into a data format representation based on the JSON format according to the object instance content of the communication protocol of the corresponding CNC device.

[0048] In this embodiment, the HTTP protocol conversion component receives the subscription SDO data transmitted by the middleware; according to the object instance content of the Modbus protocol of the corresponding numerical control device, the subscription SDO data is converted into a data format representation based on the JSON format.

[0049] Publish object instance data, call the function of the middleware to update the protocol converter object (publish object) and update the SDO service data object data (Service Data Obiect), and convert the collected CNC equipment data into a JSON data structure for storage. The middleware includes: subscription and publishing relationship information, unified data format instance data, current CNC equipment data object instance data, initialization method, sending and receiving methods, etc., which schedule the tasks of each module. After the equipment data is collected, it is converted into a JSON data structure for storage. The data content includes the equipment model, IP address, equipment name, equipment production line, equipment ID number and other information.

[0050] Start the HTTP protocol related process, and obtain data through the API application data interface provided by the CNC equipment itself. According to different types of CNC equipment, CNC equipment data can be divided into major equipment categories, such as robots and CNC machine tool data formats. Among them, CNC machine tool data can be divided into equipment data formats and application business data, such as: machine tool tool compensation data, alarm information data, and processing program data; it is convenient for users to extract corresponding data display according to business, and the system can quickly respond. After collecting data from different CNC equipment, it is converted by the system into a collection form of "name / value" pairs, where the name is the business content of the equipment, such as: machine tool tool compensation number, and the value is the value corresponding to the current collection device.

[0051] Steps to send data to different target CNC devices via universal communication protocol:

[0052] Receive object instance data processing, obtain the data that needs to be transmitted to the external CNC device through middleware scheduling, and receive the subscribed SDO service data object data sent by the middleware.

[0053] Update object instance data, the general protocol (HTTP protocol in this example) conversion component receives the subscription SDO (Service Data Object) data from the middleware; according to the object instance content of the target CNC device protocol (modbus protocol in this example). General protocol data is represented in the form of a collection of "name / value" pairs, and according to the model file (XML\JSON format) of the target device data model file, the value in the name is mapped, and the name includes: address number range, data length, and supported operation function code.

[0054] Update the protocol corresponding to the object instance data, obtain the protocol item class corresponding to the CNC device according to the communication driver of the CNC device, and the general protocol conversion module schedules the corresponding communication protocol file and creates a process according to the corresponding device type to achieve communication connection with the CNC device. The protocol item class of the CNC device includes the protocol name, protocol item target device, protocol item dynamic frame identifier, protocol dynamic frame quantity position, protocol item dynamic maximum quantity, protocol item remarks, protocol frame header group, protocol frame tail group, protocol item element group, etc.

[0055] Protocol decoding conversion, the protocol item and the object model information type map out the protocol item corresponding to the SDO service data object (Service DataObiect), refresh the protocol format information in the protocol item, and call the underlying communication interface function to send the protocol item data to the CNC device. The protocol format information in the protocol item includes: packet frame header, frame tail, frame length, frame content, frame binary and other frame feature information.

[0056] Update protocol data, associate with the background database according to the device configuration file, schedule the device data model, receive the external imported third-party device model file through the file interface, decode the third-party device model file, and create the target device data and protocol conversion process. The general protocol conversion module schedules the corresponding communication protocol file and creates a process according to the corresponding device type to communicate with the CNC device.

[0057] In this embodiment, the third-party device model file is decoded, for example, its content is described in JSON format, the target field value is obtained according to the JSON key-value pair, and then a new JSON key-value pair is created, and the field value is written into the new JSON structure to implement a new JSON data model conversion.

[0058] The third-party device data model files include: model description files (XML\JSON format), and device communication driver files (DLL format). The process is the same as the content of the general protocol conversion module. The difference is that the communication driver files and data model files used are specified external third-party import files, rather than files selected by the general protocol matching module.

[0059] The application service module is used to connect to the client through the system's general protocol and provide service interfaces and human-machine interface for specific application services of CNC equipment based on workshop management services.

[0060] Through the system's universal protocol, the client is connected, based on the background data and according to the workshop management business, the service interface is provided for the application business such as the transmission of processing programs for machine tools and robots, modification of equipment parameters, modification of machine tool tool compensation, etc. The client business interface is realized, and the business logic and human-machine interface display are realized.

[0061] Specifically, the client is interacted with through the system's general protocol. The middleware provides service interfaces for application services such as transferring processing programs, modifying equipment parameters, modifying machine tool tool compensation, etc. for CNC equipment (machine tools, robots) based on background data through the upper-layer application interface corresponding to the application service module according to the configuration table, application layer protocol, and database interface. Specifically, the upper-layer application interface is in the form of a Restful-API architecture, and converts the operation instructions and addresses of the device's own protocol into a unified and easy-to-understand description, that is, mapping operations based on address codes to English-named descriptions of corresponding application service business functions, and mapping the operation codes of operation instructions to operations named in English.

[0062] In this embodiment, the application business of workshop management is displayed in the user application as some buttons and charts, and the business logic is triggered by events such as clicking on operation buttons. When an operation instruction to add, delete, modify or query data is initiated to the application service module, the general protocol conversion module modifies the operation instruction, target machine tool address and target modification value according to the API interface, and converts them into the operation instruction format, address and value under the communication protocol corresponding to the machine tool equipment, and then sends them to the machine tool equipment to implement the business.

[0063] Specifically, the data addition, deletion, modification and query operation instructions include modifying the machine tool tool compensation operation, initiating the business data API interface for modifying the machine tool tool compensation, as well as the modified operation instructions, the address of the target machine tool, and the target modification value.

[0064] like Figure 4As shown, the application architecture diagram of the management system and the external numerical control equipment, the present invention is connected to the numerical control equipment for implementation, and multiple numerical control equipment are connected to the local area network of the workshop site through a hardware interface (generally an RJ45 interface). There is a server in the local area network, and the example application of the present invention is installed in the server. When the accessed numerical control equipment has different types of communication protocols (mainly referring to the application layer protocol, such as modbus protocol, MQTT protocol, OPCUA protocol, HTTP protocol), the interface enters the server network, and the server implements the protocol conversion into a unified application protocol (HTTP) and a unified data model in the same network, and can be displayed to the client. Through the client interface, the HTTP protocol is used to communicate with the client, and data viewing, modification, and device remote control functions can be realized on the client.

[0065] In summary, a management system for CNC equipment in this embodiment can realize unified management of CNC equipment of different models, and remotely monitor various operating conditions and internal parameters of the equipment in real time. Data of multiple devices are managed on the same platform, and data of multiple devices are displayed at the same time. The data content of the past can be traced back through data persistence in the database. For multiple application protocols of a single device, multi-protocol communication is realized through file configuration to meet various application business requirements of CNC equipment and robots, such as remote file transfer, remote parameter modification, etc.

[0066] Based on the above-mentioned management system of numerical control equipment, a management method of numerical control equipment is also provided, which comprises the steps of:

[0067] S1. Input the configuration information of the target CNC device through the application service module on the client;

[0068] S2. The protocol matching module dispatches the device data model file of the target device in the system database according to the configuration information. When the database cannot dispatch the corresponding device data model, the third-party device model file is imported through the third-party file interface;

[0069] S3, the protocol conversion module connects with the communication protocol of the target numerical control device according to the data file of the target device, converts the communication protocols of different target numerical control devices into a universal communication protocol, sends data to the target numerical control device through the universal communication protocol, and realizes the conversion of the unified data model and the communication protocol of the target numerical control device;

[0070] S4. After the protocol conversion is completed, based on the unified data model of the server, various application services are implemented for the target CNC equipment through the upper-level application interface corresponding to the application service module, including the transmission of machining program files, modification of equipment parameters, modification of machine tool tool compensation data and other application services.

[0071] The above embodiments are preferred implementation modes of the present invention, but the implementation modes of the present invention are not limited to the above embodiments. Any other changes, modifications, substitutions, combinations, and simplifications made without departing from the spirit and principles of the present invention shall be equivalent replacement methods and shall be included in the protection scope of the present invention.

Claims

1. A management system for numerical control equipment, characterized in that: It includes a general protocol matching module, a general protocol conversion module, a middleware module, and an application service module, among which: The general protocol matching module is used to input the device information of the target CNC device, generate a configuration file, and match each configuration file with the device data model file corresponding to the scheduling preset database. When the preset database does not have the corresponding device data model file, the device data model file of the third-party device is imported from the external interface; The universal protocol conversion module is used to provide device access interfaces for different target CNC devices, connect with the communication protocols of different target CNC devices, and convert the communication protocols of different target CNC devices into universal communication protocols; users send data to different target CNC devices through universal communication protocols; Middleware module, used to complete task scheduling, database management and file management between the general protocol matching module, application service module, general protocol conversion module and application service module respectively; The application service module is used to connect to the client through the system's general protocol and provide service interfaces and human-machine interface for specific application services of CNC equipment based on workshop management services.

2. A management system for numerical control equipment according to claim 1, characterized in that: The device information of the target numerical control device is input and a configuration file is generated, including: inputting the device information of the target numerical control device: device type, device ID number, device model, device IP address, device data model and communication protocol name, submitting the device information to the general protocol conversion module and middleware according to the business logic, generating a device configuration file and saving it.

3. A management system for numerical control equipment according to claim 1, characterized in that: The device data model file includes: a model file and a device driver file. The model file is used for data model description, and the model file includes XML format and JSON format; the device driver file is used for device communication driver, and the device driver file includes DLL format.

4. A management system for numerical control equipment according to claim 1, characterized in that: The communication protocol of the target numerical control device includes: Modbus communication protocol, and the universal communication protocol includes: HTTP protocol.

5. The management system of a numerical control device according to claim 1, characterized in that: Convert the communication protocols of different target CNC devices into a universal communication protocol, including the following steps: Update the protocol data, schedule the corresponding communication protocol file according to the device driver file of the CNC device, create the protocol item class corresponding to the CNC device, and create a process to communicate with the CNC device; Find the object instance corresponding to the protocol, find the data object instance of the communication protocol file of the corresponding numerical control device, and create its application unit data according to the data object instance of the communication protocol file of the numerical control device and the device data model; Protocol decoding and conversion, generating protocol object model information according to the protocol item class corresponding to the numerical control equipment, and generating protocol object instances in the general protocol converter; Update the protocol object instance data, receive the subscription SDO service data object data from the middleware, and convert the subscription SDO service data object data into a data format representation based on the JSON format according to the object instance content of the communication protocol of the corresponding CNC device; Call the middleware module to update the function of the protocol converter object and update the SDO service data object data, and convert the collected device data into a JSON data structure for storage.

6. A management system for numerical control equipment according to claim 5, characterized in that: The protocol item class of the numerical control device includes a protocol name, a protocol item target device, a protocol item dynamic frame identifier, a protocol dynamic frame quantity position, a protocol item dynamic maximum quantity, a protocol item remark, a protocol frame header group, a protocol frame tail group, and a protocol item element group.

7. A management system for numerical control equipment according to claim 6, characterized in that: The protocol object model information includes: object model name, timestamp identifier, protocol attribute list: including transaction processing identifier, protocol identifier, unit identifier and other message header information in the numerical control equipment communication protocol, protocol event list, and protocol format.

8. A management system for numerical control equipment according to claim 5, characterized in that: The step of sending data to different target numerical control devices through a universal communication protocol includes: Receive object instance data, obtain the number of instructions for controlling the CNC equipment input by the user from the application service module through middleware scheduling, and subscribe to the SDO service data object data sent by the receiving middleware; According to the data object instance content of the communication protocol of the corresponding CNC device, it is converted into a data format representation based on the JSON format; Update the protocol corresponding to the object instance data, obtain the protocol item class corresponding to the CNC device according to the communication driver of the CNC device, and the general protocol conversion module schedules the corresponding communication protocol file and creates a process according to the corresponding device type to achieve communication connection with the CNC device; Protocol decoding and conversion, mapping the protocol items and object model information types to the protocol items corresponding to the SDO service data objects, refreshing the protocol format information in the protocol items, and calling the underlying communication interface function to send the protocol item data to the CNC equipment; Update protocol data, associate with the background database according to the device configuration file, schedule the device data model, receive externally imported third-party device model files through the file interface, decode the third-party device model files, create target device data and protocol conversion process, and communicate with CNC equipment.

9. A management system for numerical control equipment according to claim 1, characterized in that: The method comprises: interacting with the client through the system's general protocol, and providing a service interface and a human-machine interface for the specific application business of the numerical control equipment according to the workshop management business, including: interacting with the client through the system's general protocol, and the middleware providing a service interface for the application business of the numerical control equipment based on the background data through the upper-layer application interface corresponding to the application service module according to the configuration table and the application layer protocol and the database interface; the layer application interface is in the form of a Restful-API architecture, and the operation instructions and addresses of the device's own protocol are converted into a unified and easy-to-understand description, that is, mapping the operation based on the address code to the English naming description of the corresponding application service business function, and mapping the operation code of the operation instruction to the operation named in English.

10. A method for managing numerical control equipment, implemented based on a management system for numerical control equipment according to any one of claims 1 to 9, characterized in that the method comprises the steps of: Input the configuration information of the target CNC device through the application service module on the client side; The general protocol matching module dispatches the device data model file of the target CNC device in the system database according to the configuration information. When the database cannot dispatch the corresponding device data model, the third-party device model file is imported through the third-party file interface; The universal protocol conversion module connects with the communication protocol of the target numerical control device according to the data file of the target numerical control device, converts the communication protocols of different target numerical control devices into the universal communication protocol, and sends data to the target numerical control device through the universal communication protocol; Based on the unified data model of the server, various application services are implemented for the target CNC equipment through the upper-level application interface corresponding to the application service module.

Images