Task scheduling and processing system and method for electrode post-processing

Abstract

The application discloses an electrode post-processing task scheduling and processing system and method, and belongs to the technical field of electrode post-processing. The technical scheme provided by the application forms a distributed task scheduling and processing system by setting a foreground client module, a background service scheduling module and a background processing node, thereby realizing step-by-step and node-by-node processing of electrode post-processing tasks. The foreground client module only needs to perform task configuration and submission, thereby reducing resource occupation of a user terminal. The background service scheduling module can sort tasks and process the tasks by scheduling the background processing node. The background processing node performs formal processing of the electrode post-processing tasks after pre-checking, thereby reducing unnecessary waste of computing resources, improving processing efficiency and correctness of electrode post-processing, effectively solving the core defects of centralized resource occupation, frequent software conflicts and low efficiency of batch tasks during electrode post-processing, and meeting the demand of modern mold manufacturing for efficient, stable and large-scale electrode processing.

Description

Technical Field

[0001] This application relates to the field of electrode post-processing technology, and in particular to a task scheduling and processing system and method for electrode post-processing. Background Technology

[0002] In electrode machining within the field of computer-aided manufacturing (CAM) based on UG / NX (Unigraphics NX) software, electrode programmers need to perform post-processing operations to convert the machining toolpath data generated by UG / NX into NC (Numerical Control) code files recognizable by the machine tool control system. Simultaneously, a machining program sheet containing machining parameters, view screenshots, and a tool list is generated for on-site operators to execute. This post-processing step is essential for converting digital toolpaths into actual machining instructions and directly impacts the efficiency of electrode machining implementation.

[0003] However, the aforementioned post-processing process in the existing technology has significant technical pain points: on the one hand, post-processing calculations are high-load tasks, requiring a large amount of hardware resources (such as CPU and memory) on the programmer's local workstation. Especially when processing batches of electrodes, the continuous high resource consumption can lead to slow response and operation lag in UG / NX software, or even program unresponsiveness due to resource exhaustion, forcing programmers to interrupt other front-end work such as modeling and programming, severely restricting the task output capacity per unit time.

[0004] On the other hand, the UG / NX software itself has limited multi-threaded concurrent processing capabilities. If programmers attempt to process toolpaths in parallel by running multiple UG / NX processes simultaneously, resource contention between processes is likely to occur due to software kernel conflicts, leading to problems such as some processes freezing, data read / write errors, or a sudden drop in overall running speed, thus failing to achieve true parallel acceleration.

[0005] Therefore, in scenarios with large-scale electrode processing and tight delivery deadlines (such as peak mold manufacturing season), programmers still face the contradiction between "waiting for post-processing to be completed" and "continuing front-end work," resulting in extremely limited room for efficiency improvement.

[0006] In summary, existing electrode post-processing technologies based on UG / NX suffer from core drawbacks such as concentrated resource consumption, frequent software conflicts, and low efficiency in batch tasks, making it difficult to meet the demands of modern mold manufacturing for efficient, stable, and large-scale electrode processing. Summary of the Invention

[0007] In the existing technology, when performing large-scale electrode post-processing based on UG / NX software, the calculation tasks are concentrated on the programmer's local workstation, resulting in excessive consumption of hardware resources (such as CPU and memory), slow software response, and thus affecting the overall work efficiency. The embodiments of this application provide a task scheduling and processing system and method for electrode post-processing, which can overcome the above-mentioned problems of the prior art.

[0008] According to one aspect of the embodiments of this application, a task scheduling and processing system for post-electrode processing is provided. The task scheduling and processing system includes a front-end client module and a back-end processing center. The back-end processing center includes a back-end service scheduling module and back-end processing nodes. The front-end client module is configured to: receive task configuration information corresponding to a post-electrode processing task, encapsulate the task configuration information, generate a task data packet corresponding to the post-electrode processing task, and send it to the back-end processing center. The back-end service scheduling module is configured to: in response to receiving the task data packet, parse and store the task configuration information and store the post-electrode processing task in a target position in a global pending task queue; monitor the task processing status of the back-end processing nodes in real time; and, upon detecting the task processing status of the back-end processing nodes, [follow the instructions for further processing]. When the processing node is idle and the target position is updated to the first position, the electrode post-processing task is sent to the background processing node. The background processing node is used to: read the task configuration information, perform data preparation and pre-check processing, obtain and store the pre-check result, which is used to characterize whether there are any abnormal errors in the electrode post-processing task; when the pre-check result indicates that the pre-check has passed, perform post-processing calculations according to the task configuration information and the pre-check result, generate and store digital control code files, program sheet information and processing view information; the background service scheduling module is also used to: collect all output information stored during the execution of the current electrode post-processing task, and return the file path of all output information to the front-end client module.

[0009] In an exemplary embodiment, receiving task configuration information corresponding to the electrode post-processing task includes: displaying the task submission interface in response to an instruction to enter the task submission interface, the task submission interface including a file selector and an information form; receiving a selection instruction for a local electrode model file based on the file selector, and determining the target image information corresponding to the electrode post-processing task; receiving task metadata corresponding to the electrode post-processing task based on the information form, the task configuration information including the target image information and the task metadata; and encapsulating the task configuration information to generate a task data package corresponding to the electrode post-processing task includes: performing task data package encapsulation processing on the target image information and the task metadata to obtain a text-structured task data package and indicating a timestamp.

[0010] In an exemplary embodiment, the information form includes required fields, optional fields, and a remarks column; receiving task metadata corresponding to the electrode post-processing task based on the information form includes: generating the task metadata based on the information received from the required fields, the optional fields, and the remarks column; wherein, the required fields are used to receive required information, the optional fields are used to receive optional information, and the remarks column is used to receive remarks information; the optional information includes at least one of an urgency level indicator and additional processing instructions; and the remarks information includes special processing requirements information.

[0011] In an exemplary embodiment, the step of reading the task configuration information, performing data preparation and pre-check processing, and obtaining and storing the pre-check result includes: reading the target image file information to download the electrode model file, and performing file integrity verification on the electrode model file to obtain an integrity verification result, wherein the pre-check result includes the integrity verification result; reading the task metadata; and, if the task metadata includes additional processing instructions, executing additional processing tasks corresponding to the additional processing instructions on the electrode model file to obtain additional processing results, wherein the pre-check result includes the additional processing results; wherein, if there are multiple additional processing instructions, the additional check tasks corresponding to the multiple additional processing instructions are executed sequentially according to the check order corresponding to the multiple additional processing instructions.

[0012] In an exemplary embodiment, the additional processing instructions include at least one of a minimum tool length calculation instruction, a toolpath overcutting check instruction, and a toolpath collision detection instruction; the step of performing additional processing tasks on the electrode model file to obtain additional processing results when the task metadata includes additional processing instructions includes: performing a minimum tool length calculation task on the electrode model file to obtain a minimum tool length calculation result when the additional processing instructions include a minimum tool length calculation instruction; performing a toolpath overcutting check task on the electrode model file to obtain a toolpath overcutting check result when the additional processing instructions include a toolpath collision detection instruction; and performing a toolpath collision detection task on the electrode model file to obtain a toolpath collision point report when the additional processing instructions include a toolpath collision detection instruction.

[0013] In an exemplary embodiment, the step of performing post-processing operations based on the task configuration information and the pre-inspection results to generate and store digital control code files, program sheet information, and machining view information includes: reading and caching toolpath data from the pre-inspection results, and generating a digital control code file recognizable by the machine tool control system; capturing an image of a three-dimensional machining view of the electrode model based on the task configuration information, wherein the machining view information includes the image; collecting machining parameter information and appending it to the digital control code file in the form of annotations; and generating the program sheet information based on a preset template.

[0014] In an exemplary embodiment, the background service scheduling module is further configured to automatically send the processed temporary electrode model file back to the front-end client module; the front-end client module is further configured to view the output information and the temporary electrode model file.

[0015] In an exemplary embodiment, the background processing node is further configured to: automatically update the idle state and load the next electrode post-processing task when the pre-check result indicates that the pre-check has failed, and start execution from the step of reading the task configuration information; the background service scheduling module is specifically configured to: at least return the file path of the pre-check result to the front-end client module.

[0016] In an exemplary embodiment, the background processing node is further configured to: generate error log information if a syntax error and / or logical error occurs during the generation of the digital control code file; the background service scheduling module is specifically configured to: at least return the file path of the error log information to the front-end client module.

[0017] According to one aspect of the embodiments of this application, a task scheduling and processing method for post-electrode processing is provided. The method is applied to the task scheduling and processing system described in any of the above embodiments. The method includes: a front-end client module receiving task configuration information corresponding to a post-electrode processing task, encapsulating the task configuration information, generating a task data packet corresponding to the post-electrode processing task, and sending it to the back-end processing center; a back-end service scheduling module responding to receiving the task data packet, parsing and storing the task configuration information, and storing the post-electrode processing task in a target position in a global pending task queue; real-time monitoring of the task processing status of the back-end processing node; and detecting when the back-end processing node is idle. When the target position is updated to the first position, the electrode post-processing task is sent to the background processing node; the background processing node reads the task configuration information, performs data preparation and pre-check processing, obtains and stores the pre-check result, which is used to characterize whether there are any abnormal errors in the electrode post-processing task; when the pre-check result indicates that the pre-check has passed, post-processing calculations are performed according to the task configuration information and the pre-check result to generate and store digital control code files, program sheet information and processing view information; the background service scheduling module collects all output information stored during the execution of the current electrode post-processing task and returns the file path of all output information to the front-end client module.

[0018] According to one aspect of the embodiments of this application, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the above-described task scheduling and processing method on the front-end client module side, the back-end service scheduling module side or the back-end processing node side.

[0019] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein the storage medium stores at least one instruction, at least one program, code set or instruction set, wherein the at least one instruction, the at least one program, the code set or instruction set is loaded and executed by a processor to implement the above-described task scheduling and processing method on the front-end client module side, the back-end service scheduling module side or the back-end processing node side.

[0020] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the task scheduling and processing method described above for the front-end client module side, the back-end service scheduling module side, or the back-end processing node side.

[0021] The technical solution provided in this application embodiment can bring the following beneficial effects: By setting up a distributed task scheduling and processing system consisting of a front-end client module, a back-end service scheduling module, and back-end processing nodes, the electrode post-processing tasks can be processed step by step and node by node. The front-end client module only needs to configure and submit tasks, which reduces the resource occupation of the user terminal where the front-end client module is located. The back-end service scheduling module can sort and manage the tasks initiated by each front-end client module and issue tasks to the back-end processing nodes for processing when each back-end processing node is idle. The back-end processing nodes are responsible for pre-verification before formally processing the electrode post-processing tasks, reducing unnecessary waste of computing resources, improving the processing efficiency and correctness of electrode post-processing, and effectively solving the core defects of the prior art based on UG / NX electrode post-processing, such as concentrated resource occupation, frequent software conflicts, and low efficiency of batch tasks, thus meeting the needs of modern mold manufacturing for efficient, stable, and large-scale electrode processing. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is an interactive flowchart of a task scheduling and processing method for electrode post-processing provided in one embodiment of this application; Figure 2 An example diagram of a task submission interface is shown; Figure 3 An example is shown of the list of electrode post-processing tasks displayed by the front-end client module; Figure 4 This is a flowchart illustrating the task scheduling and processing method for electrode post-processing provided in the embodiments of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0025] This application provides a task scheduling and processing system for post-electrode processing, and a task scheduling and processing method for post-electrode processing. Please refer to... Figure 1 , Figure 1 This is an interactive flowchart of a task scheduling and processing method for post-electrode processing provided in one embodiment of this application. The above method is applied to the above-described task scheduling and processing system.

[0026] The aforementioned task scheduling and processing system includes a front-end client module and a back-end processing center. The back-end processing center includes a back-end service scheduling module and back-end processing nodes.

[0027] The front-end client module, deployed on the programmer's personal computer, is used to receive user instructions, send task data packets to the back-end service scheduling module, and display feedback information from the back-end service scheduling module.

[0028] The background service scheduling module, deployed in the background processing center, is used to receive, parse, queue and schedule the above-mentioned background processing nodes to execute post-processing tasks, and finally feed back the processing results to the corresponding front-end client module.

[0029] like Figure 1 As shown, the front-end client module is used to execute steps (110-120) in the above method.

[0030] Step 110: Receive the task configuration information corresponding to the electrode post-processing task.

[0031] During the task submission phase (front-end client operation), users can load electrode images, configure task attributes, and trigger commands on the front-end client. The front-end client responds to the command, performs the task submission operation, and sends the electrode post-processing task to the back-end service scheduling module.

[0032] The user interface interaction process involved is as follows: the user opens the front-end client and enters the task submission interface. In the task submission interface, the user can load the locally standardized and named electrode model file (usually with the .prt extension) through the file selector, and check the target image file to be sent to the background service scheduling module (hereinafter referred to as the background) in the list control.

[0033] Therefore, during the above user interface interaction process, the front-end client module responds to the instruction to enter the task submission interface and displays the task submission interface, which includes a file selector and an information form; based on the file selector, it receives the instruction to select the local electrode model file and determines the target image information corresponding to the electrode post-processing task.

[0034] In addition to selecting the target image file, users also need to configure task attributes in the front-end client. For example, they need to fill in task metadata in the form on the task submission interface. Therefore, during the above user interface interaction, the front-end client module receives the task metadata corresponding to the post-processing task based on the information form.

[0035] In an exemplary embodiment, the information form includes required fields, optional fields, and a remarks field; correspondingly, the front-end client module generates task metadata based on the information received from the required fields, optional fields, and remarks field. The required fields are used to receive required information, the optional fields are used to receive optional information, and the remarks field is used to receive remarks.

[0036] The required information includes, but is not limited to, the account identifier to which the task belongs (such as the programmer's name) and the name of the electrode project.

[0037] Optional information includes, but is not limited to, an urgency level indicator (such as "Normal", "Urgent", "Extreme Urgent") and at least one of the following additional processing instructions. These additional processing instructions can be selected via checkboxes and include, but are not limited to, at least one of the following: minimum tool length calculation instruction, toolpath overcut check instruction, and toolpath collision detection instruction.

[0038] The remarks section includes information on special processing requirements, which can be entered in the remarks column above. For example, you can specify the machine tool model or provide guidance on avoidance areas.

[0039] During the task attribute configuration process described above, the front-end client responds to the various task attribute configuration operations and obtains the task configuration information, which includes target image information and task metadata.

[0040] Step 120: Encapsulate the task configuration information to generate a task data package corresponding to the electrode post-processing task.

[0041] And send the task data packet to the backend processing center.

[0042] After the task attributes are configured, the front-end client encapsulates the target image information and task metadata into a task data package, resulting in a text-structured task data package with a timestamp.

[0043] When encapsulating the task data packet, the client automatically concatenates the local path of the selected target image file, the required information of the task attribute configuration, the additional instruction parameters in the optional information, and the remarks into an integrated text in text form. For example, whether to perform a certain test is represented as 0 or 1, and this text is concatenated with the path and other text using a separator, thereby integrating it into a structured data packet and indicating the timestamp (accurate to milliseconds).

[0044] After the user confirms that the task attribute configuration is correct, clicking the "Submit Task" button triggers the sending command. The front-end client responds to the triggered task submission command by transmitting the text-structured task data package to the task pool of the back-end service scheduling module through database interaction.

[0045] In one example, such as Figure 2 As shown, this example illustrates a schematic diagram of a task submission interface. It displays interactive elements such as a document selector and an information form, allowing users to configure the aforementioned task information.

[0046] After the task is submitted, the task queuing and scheduling phase begins (operated by the background service scheduling module). Its core functions are to receive tasks, parse and sort them, dynamically manage the queue, and schedule them for execution according to priority.

[0047] like Figure 1 As shown, the background service scheduling module is used to execute steps (130-150) in the above method.

[0048] Step 130: In response to receiving the task data packet, parse and store the task configuration information and store the electrode post-processing task in the target location of the global pending task queue.

[0049] During task reception and parsing, the background service scheduling module monitors the task pool. Upon receiving a task data packet, it verifies the readability and completeness of the target image associated with the post-processing task, parses various task attribute data in the task metadata, such as the account identifier, urgency identifier (priority), and additional instructions, and generates a unique task identifier.

[0050] After receiving and parsing the task, the task is added to the pending list. During this process, the background service scheduling module stores the unique task identifier of the parsed electrode post-processing task in the target position of the global pending task queue, and marks the initial state of the electrode post-processing task as "pending".

[0051] After a task is added to the pending list, priority rules are applied and the tasks are sorted. The background service scheduling module sorts the pending electrode post-processing tasks in the global pending task queue according to preset priority rules and updates the sorting results in real time.

[0052] The above-mentioned preset priority rules include, but are not limited to: First priority rule: Under the specified priority (such as "Urgent" > "Faster" > "Regular", corresponding to numerical weights 3 > 2 > 1), they are arranged in descending order according to the weight of the specified priority.

[0053] Second priority rule: If no priority is specified, tasks are sorted in ascending order of submission timestamp (first-in, first-out principle).

[0054] Therefore, if the aforementioned task metadata includes an urgency level identifier, the order of the electrode post-processing task in the global pending task list is determined according to the priority indicated by the urgency level identifier.

[0055] In a further implementation, the background service scheduling module supports dynamically adjusting the task order in the global pending task list. For example, the background service scheduling module allows users to delete pending tasks in the task management interface of the foreground client, or administrators to modify task priorities through the console of the background service scheduling module, and immediately reorder them after modification. Specifically, in response to a task deletion operation received in the task management interface, the foreground client sends a unique task identifier corresponding to the task deletion operation to the background service scheduling module. After receiving the unique task identifier, the background service scheduling module deletes the task from the global pending task queue and updates the sorting result. In one example, such as Figure 3 As shown, this example illustrates the list of electrode post-processing tasks displayed by the front-end client module. Users can view the electrode post-processing tasks they have initiated in this list and perform corresponding configurations, such as deleting, retrieving images, refreshing, and clearing the list.

[0056] Alternatively, the background service scheduling module responds to the task priority modification operation by updating the sorting results in the global task queue in real time based on the modified priority information.

[0057] Step 140: Monitor the task processing status of the background processing nodes in real time.

[0058] Step 150: If the background processing node is detected to be idle and the target position is updated to the first position, the electrode post-processing task is sent to the background processing node.

[0059] After prioritizing tasks, idle tasks are extracted and marked. Specifically, when the background service scheduling module detects that a background processing node (such as a background server or workstation) is idle, the scheduler of the background service scheduling module extracts the first highest priority task from the sorted global queue of pending tasks, updates its processing status to "in progress," and records the start timestamp.

[0060] Once the post-electrode processing task in step 110 is updated to the first position in the global task queue, the background service scheduling module can update the task processing status to "in progress", record the start processing timestamp, and schedule the background processing node to process it.

[0061] Thus, the task queuing and scheduling phase ends, and the data preparation and preprocessing phase begins (background processing node operations). The core function of this phase is for the background processing node to retrieve image data, execute user-specified additional check tasks, and determine whether to proceed to core post-processing.

[0062] like Figure 1 As shown, the background processing node is used to execute steps (160-170) in the above method.

[0063] Step 160: Read the task configuration information, perform data preparation and pre-check processing, and obtain and store the pre-check results.

[0064] The results of the preliminary inspection are used to characterize whether there are any abnormal errors in the electrode post-processing task.

[0065] The background processing node reads the target drawing information to download the electrode model file and performs file integrity verification on the electrode model file to obtain the integrity verification result. The pre-check result includes the integrity verification result.

[0066] When retrieving drawing data in the background processing node, the background processing node downloads the electrode model file from the shared storage database to the local temporary directory based on the drawing path associated with the unique task identifier, and verifies the integrity of the electrode model file, such as by opening the electrode model file through the application programming interface of the UG / NX software and detecting errors.

[0067] On the other hand, the background processing node reads the task metadata. If the task metadata includes additional processing instructions, it executes the additional processing tasks corresponding to the additional processing instructions on the electrode model file to obtain the additional processing results. The pre-check results include the additional processing results.

[0068] The background processing node can execute the additional inspection tasks corresponding to the additional processing instructions by calling the calculation function of the UG / NX software itself.

[0069] If there are multiple additional processing instructions, the additional check tasks corresponding to each of the multiple additional processing instructions will be executed in the order they are selected.

[0070] The aforementioned additional inspection tasks include, but are not limited to, the shortest tool length calculation task, the toolpath overcutting inspection task, and the toolpath collision detection task.

[0071] When additional processing instructions include a minimum tool length calculation instruction, the minimum tool length calculation task is performed on the electrode model file to obtain the minimum tool length calculation result. When the background processing node performs the minimum tool length calculation task, it reads the electrode model coordinate system, the Z-axis height of the machining surface, and the tool library parameters, calculates the minimum tool length from the safety plane to the machining surface, and temporarily stores the minimum tool length calculation result in the task log.

[0072] When additional processing instructions include toolpath overcutting check instructions, a toolpath overcutting check task is performed on the electrode model file to obtain the toolpath overcutting check results. When the background processing node performs the toolpath overcutting check task, it loads the electrode machining toolpath, performs interference analysis on the toolpath, electrode model, and fixture model, and records the toolpath overcutting check results, such as overcutting position coordinates and interference depth.

[0073] When additional processing instructions include toolpath collision detection instructions, a toolpath collision detection task is performed on the electrode model file to obtain a toolpath collision point report. When the background processing node performs the toolpath collision detection task, it simulates the tool movement trajectory, checks for potential collisions between the tool holder, tool shank, workpiece, and fixture, and generates a toolpath collision point report, which includes information such as the name of the colliding component and the tool axis angle at the time of the collision.

[0074] After performing the above additional inspection tasks, the background processing node performs inspection result judgment and exception handling. If the pre-inspection result indicates that the pre-inspection has failed, the background processing node automatically updates the idle status and loads the next electrode post-processing task, and starts execution from step 160 above.

[0075] The pre-check result indicates that the pre-check failed if any additional check task indicates an error. If any additional check task indicates an error, such as an overcut depth > 0.05mm or a collision risk level of "high," the error details are recorded as the pre-check result and stored in the task error log. The error details include, but are not limited to, check type, error location, and screenshots.

[0076] Furthermore, the background processing node marks the task status as "abnormal - check failed," skipping subsequent core post-processing steps. Afterward, the background processing node automatically loads the next priority task corresponding to the current electrode post-processing task in the aforementioned global pending task list, and returns to the idle task extraction and marking operations.

[0077] In this case, the background service scheduling module will at least return the file path of the pre-check results to the front-end client module so that the front-end client module can view the details of those that failed the pre-check.

[0078] Step 170: If the pre-check result indicates that the pre-check has passed, perform post-processing calculations based on the task configuration information and the pre-check result to generate and store the digital control code file, program sheet information and machining view information.

[0079] If all additional inspection tasks pass the inspection or there are no additional inspection tasks, the post-processing calculation stage begins. The background processing node performs the core post-processing calculation. The core functions of the background processing node in the post-processing calculation stage include, but are not limited to, reading toolpath data, performing path optimization, coordinate transformation, generating NC code and machining views.

[0080] The post-processing operation includes reading and caching the toolpath data from the pre-check results, and generating a digital control code file that can be recognized by the machine tool control system.

[0081] When the background processing node reads and parses toolpath data, it reads the toolpath data generated in the aforementioned steps and temporarily caches it. This toolpath data includes parameters such as toolpath, cutting parameters, feed rate, and spindle speed.

[0082] After the toolpath data is read, the background processing node performs NC code generation. It calls the CAM_POST post-processor constructor interface of the UG / NX software to generate a customized post-processing file, namely the aforementioned digital control code file, such as a file ending with NC, according to the specified name.

[0083] In addition, the background processing node also performs view screenshots and processing parameter collection.

[0084] Based on the task configuration information, the background processing node captures an image of the 3D machining view of the electrode model. The machining view information includes the image, which captures the coordinate system, toolpath highlighting, and other information of the 3D machining view of the electrode model, and saves it as an image, such as a PNG format.

[0085] The background processing nodes collect machining parameter information and append it to the digital control code file as comments. For example, they collect machining parameters such as tool type, cutting depth, and estimated machining time, record them line by line as text information, and append them to the end of the digital control code file as comments, thereby associating the digital control code file with the machining parameters.

[0086] If an error occurs in the above process, the background processing node also needs to perform core operation error handling. Specifically, if a syntax error and / or logical error occurs during the generation of the digital control code file, the background processing node will generate error log information. The error log will contain information such as the error line number and code snippet, and the task status of the task will be marked as "abnormal - core operation failure". The node will skip the following result document generation and archiving stage and enter the final result feedback process.

[0087] In this case, the background service scheduling module will at least return the file path of the error log information to the front-end client module.

[0088] If no errors occur in the above process, the process proceeds to the result document generation and archiving stage. The core functions of the background processing node at this stage include, but are not limited to, integrating processing information to generate a program sheet (including PNG images, etc.), packaging NC code and program sheets, and storing them in a standardized manner.

[0089] The background processing node needs to integrate machining information with the view. It integrates NC code, view screenshots, machining parameters (tool list, cutting parameters), and additional inspection results (shortest tool length, overcut / collision report) into a structured dataset in text and image formats, and caches it.

[0090] The background processing node also needs to generate program sheets and package and store files. It also needs to generate program sheet information based on preset templates, such as generating electrode machining program sheets in Excel or PDF format, and storing NC code files (machine tool readable files), program sheets (PDF or Excel format), etc. in a shared storage directory according to a preset directory structure. The top-level directory is the electrode folder, and the NC code files and program sheets are stored in multiple subdirectories of the top-level folder for subsequent machine tool reading.

[0091] After the background processing nodes complete the above-mentioned processing stages, the system enters the processing result summary stage, where the background service scheduling module collects all output information of this electrode post-processing task.

[0092] like Figure 1 As shown, the background service scheduling module is also used to execute steps (180-190) in the above method.

[0093] Step 180: Collect all output information stored from the execution of this electrode post-processing task.

[0094] All output information includes the pre-check results, digital control code files, program sheet information, and machining view information, as well as the output results of the aforementioned steps.

[0095] Step 190: Return the file paths of all output information to the front-end client module.

[0096] If the electrode post-processing task is successfully executed, the background service scheduling module collects the paths of various output information, such as the NC code file path, program single file path, and view screenshot path, and generates a summary result.

[0097] In the event of failure of the electrode post-processing task, the background service scheduling module collects error logs (including details of failed checks and core operation failures) and marks them as exceptions.

[0098] The background service scheduling module further processes the push of results to the front-end client. Through database interaction, it pushes the summarized results (including task ID, status, file path, error information, etc.) to the front-end client module that initiated the task. The front-end client module's interface displays notification information of the task processing results, such as task completion or task exception information, and can expand to display details.

[0099] The background service scheduling module also processes the return of original drawings / intermediate data. It automatically returns the processed electrode model temporary file (including toolpaths, post-processing configurations, etc.) to the "Processed Tasks" directory on the local computer where the front-end client module is located for subsequent verification. The front-end client module is also used to view output information and electrode model temporary files.

[0100] Once the above processing is completed, the background processing node performs system state reset and idle waiting processing, releasing the memory and temporary files occupied by this task, updating the task status to "completed" and moving it to the historical task library; the system status is restored to "idle", waiting for new task submission, and returning to the steps of extracting and marking idle state tasks.

[0101] For better understanding, the entire process described above can also be referenced. Figure 4 , Figure 4 This is a flowchart illustrating the task scheduling and processing method for electrode post-processing provided in this application embodiment. The relevant processes have been described previously and will not be repeated here.

[0102] In summary, the technical solution provided in this application provides a distributed task scheduling and processing system by setting up a front-end client module, a back-end service scheduling module, and back-end processing nodes. This enables step-by-step and node-based processing of electrode post-processing tasks. The front-end client module only needs to configure and submit tasks, reducing the resource consumption of the user terminal where the front-end client module is located. The back-end service scheduling module can sort and manage the tasks initiated by each front-end client module and issue tasks to the back-end processing nodes when they are idle to schedule them for processing. The back-end processing nodes are responsible for pre-verifying the electrode post-processing tasks before formally processing them, reducing unnecessary waste of computing resources and improving the processing efficiency and accuracy of electrode post-processing. This effectively solves the core defects of existing UG / NX-based electrode post-processing technologies, such as concentrated resource consumption, frequent software conflicts, and low efficiency of batch tasks, and meets the needs of modern mold manufacturing for efficient, stable, and large-scale electrode processing.

[0103] It should be noted that the systems and modules provided in the above embodiments are only illustrated by the division of the above functional modules when implementing their functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0104] One embodiment of this application provides a computer device. This computer device may be a computer device containing a front-end client module, a back-end service scheduling module, and a back-end processing node. This computer device is used to implement the task scheduling and processing methods provided in the above embodiments on the front-end client module side, the back-end service scheduling module side, or the back-end processing node side. Specifically, the computer device typically includes a processor and a memory.

[0105] The processor may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor may be implemented using at least one hardware form of DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), or PLA (Programmable Logic Array). The processor may also include a main processor and coprocessors. The main processor, also known as the CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor may also include an AI (Artificial Intelligence) processor, which handles computational operations related to machine learning.

[0106] The memory may include one or more computer-readable storage media, which may be non-transitory. The memory may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory is used to store at least one instruction, at least one program, code set, or instruction set, which is configured to be executed by one or more processors to implement the task scheduling and processing methods described above for the front-end client module side, the back-end service scheduling module side, or the back-end processing node side.

[0107] In some embodiments, the computer device may also optionally include: a peripheral device interface and at least one peripheral device. The processor, memory, and peripheral device interface can be connected via a bus or signal lines. Each peripheral device can be connected to the peripheral device interface via a bus, signal lines, or a circuit board.

[0108] Computer equipment can receive user input to execute the steps in the above method or the operations within those steps.

[0109] Those skilled in the art will understand that the above structure does not constitute a limitation on the computer device, and may include more or fewer components than illustrated, or combine certain components, or employ different component arrangements.

[0110] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein at least one instruction, at least one program, code set, or instruction set is stored therein, wherein the at least one instruction, the at least one program, the code set, or the instruction set, when executed by a processor, implements the task scheduling and processing method described above for the front-end client module side, the back-end service scheduling module side, or the back-end processing node side.

[0111] Optionally, the computer-readable storage medium may include: ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0112] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the task scheduling and processing methods described above for the front-end client module, the back-end service scheduling module, or the back-end processing node.

[0113] It should be understood that "multiple" as used herein refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0114] In the description of this application, it should be noted that, in the embodiments of this application, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature.

[0115] In the description of embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0116] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A task scheduling and processing system for electrode post-processing, characterized in that, The task scheduling and processing system includes a front-end client module and a back-end processing center. The back-end processing center includes a back-end service scheduling module and a back-end processing node. The front-end client module is used to: receive task configuration information corresponding to the post-electrode processing task, encapsulate the task configuration information, generate a task data packet corresponding to the post-electrode processing task, and send it to the back-end processing center. The background service scheduling module is used to: in response to receiving the task data packet, parse and store the task configuration information and store the electrode post-processing task into the target position in the global pending task queue; Real-time monitoring of the task processing status of the background processing nodes; If the background processing node is detected to be idle and the target position is updated to the first position, the electrode post-processing task is sent to the background processing node. The background processing node is used to: read the task configuration information, perform data preparation and pre-check processing, obtain and store the pre-check results, and the pre-check results are used to characterize whether there are any abnormal errors in the electrode post-processing task; If the pre-check result indicates that the pre-check has passed, post-processing calculations are performed based on the task configuration information and the pre-check result to generate and store digital control code files, program sheet information, and machining view information. The background service scheduling module is also used to: collect all output information stored during the execution of the current electrode post-processing task, and return the file path of all output information to the front-end client module.

2. The task scheduling and processing system according to claim 1, characterized in that, The step of receiving task configuration information corresponding to the electrode post-processing task includes: responding to an instruction to enter the task submission interface, displaying the task submission interface, which includes a file selector and an information form; receiving a selection instruction for a local electrode model file based on the file selector, and determining the target image information corresponding to the electrode post-processing task; receiving task metadata corresponding to the electrode post-processing task based on the information form, wherein the task configuration information includes the target image information and the task metadata; and encapsulating the task configuration information to generate a task data package corresponding to the electrode post-processing task includes: performing task data package encapsulation processing on the target image information and the task metadata to obtain a text-structured task data package and indicating a timestamp.

3. The task scheduling and processing system according to claim 2, characterized in that, The information form includes required fields, optional fields, and a remarks column; receiving task metadata corresponding to the electrode post-processing task based on the information form includes: generating the task metadata based on the information received from the required fields, the optional fields, and the remarks column; wherein, the required fields are used to receive required information, the optional fields are used to receive optional information, and the remarks column is used to receive remarks information; the optional information includes at least one of urgency level indicators and additional processing instructions; the remarks information includes special processing requirements information.

4. The task scheduling and processing system according to claim 3, characterized in that, The step of reading the task configuration information, performing data preparation and pre-check processing, and obtaining and storing the pre-check results includes: reading the target image file information to download the electrode model file, and performing file integrity verification on the electrode model file to obtain an integrity verification result, wherein the pre-check result includes the integrity verification result; reading the task metadata; and, if the task metadata includes additional processing instructions, executing additional processing tasks corresponding to the additional processing instructions on the electrode model file to obtain additional processing results, wherein the pre-check result includes the additional processing results; wherein, if there are multiple additional processing instructions, the additional check tasks corresponding to the multiple additional processing instructions are executed sequentially according to the check order corresponding to the multiple additional processing instructions.

5. The task scheduling and processing system according to claim 4, characterized in that, The additional processing instructions include at least one of a minimum tool length calculation instruction, a toolpath overcutting check instruction, and a toolpath collision detection instruction. When the task metadata includes additional processing instructions, performing additional processing tasks on the electrode model file to obtain additional processing results includes: when the additional processing instructions include a minimum tool length calculation instruction, performing a minimum tool length calculation task on the electrode model file to obtain a minimum tool length calculation result; when the additional processing instructions include a toolpath overcutting check instruction, performing a toolpath overcutting check task on the electrode model file to obtain a toolpath overcutting check result; and when the additional processing instructions include a toolpath collision detection instruction, performing a toolpath collision detection task on the electrode model file to obtain a toolpath collision point report.

6. The task scheduling and processing system according to claim 1, characterized in that, The step of performing post-processing calculations based on the task configuration information and the pre-inspection results to generate and store digital control code files, program sheet information, and machining view information includes: reading and caching toolpath data from the pre-inspection results, and generating a digital control code file recognizable by the machine tool control system; capturing an image of a three-dimensional machining view of the electrode model based on the task configuration information, wherein the machining view information includes the image; collecting machining parameter information and appending it to the digital control code file as annotations; and generating the program sheet information based on a preset template.

7. The task scheduling and processing system according to claim 5, characterized in that, The background service scheduling module is also used to automatically send the processed electrode model temporary file back to the front-end client module; the front-end client module is also used to view the output information and the electrode model temporary file.

8. The task scheduling and processing system according to any one of claims 1 to 7, characterized in that, The background processing node is also used to: automatically update the idle state and load the next electrode post-processing task when the pre-check result indicates that the pre-check has failed, and start execution from the step of reading the task configuration information; the background service scheduling module is specifically used to: at least return the file path of the pre-check result to the front-end client module.

9. The task scheduling and processing system according to any one of claims 1 to 7, characterized in that, The background processing node is also used to: generate error log information if a syntax error and / or logical error occurs during the generation of the digital control code file; the background service scheduling module is specifically used to: at least return the file path of the error log information to the front-end client module.

10. A task scheduling and processing method for electrode post-processing, characterized in that, The method is applied to the task scheduling and processing system according to any one of claims 1 to 7, the method comprising: the front-end client module receiving task configuration information corresponding to the post-electrode processing task, and encapsulating the task configuration information to generate a task data packet corresponding to the post-electrode processing task and sending it to the back-end processing center; the back-end service scheduling module responding to receiving the task data packet, parsing and storing the task configuration information and storing the post-electrode processing task in the target position of the global pending task queue; real-time monitoring of the task processing status of the back-end processing node; and, when the back-end processing node is detected to be in an idle state and the target position is updated to the first position. The electrode post-processing task is then sent to the background processing node. The background processing node reads the task configuration information, performs data preparation and pre-check processing, obtains and stores the pre-check result, which is used to characterize whether there are any abnormal errors in the electrode post-processing task. If the pre-check result indicates that the pre-check has passed, post-processing operations are performed according to the task configuration information and the pre-check result to generate and store the digital control code file, program sheet information and processing view information. The background service scheduling module collects all the output information stored during the execution of the current electrode post-processing task and returns the file path of all the output information to the front-end client module.

Images