Program automatic burning method and device and electronic equipment

Abstract

The application provides a program automatic burning method and device and electronic equipment, and relates to industrial automation control technology; the method comprises the following steps: when a target to be burned is identified, automatically acquiring production identification information of the target to be burned; determining and downloading a corresponding target application program file from a corresponding software management system according to the production identification information; the target application program file is a composite file integrating program data and burning configuration parameters of the target to be burned; dynamically loading a corresponding diagnostic protocol driver module according to a protocol identifier parsed from the target application program file; and burning the program data in the target application program file into a controller of the target to be burned based on the diagnostic protocol driver module. Through the application, the application program burning success rate can be effectively improved.

Description

Technical Field

[0001] This application relates to industrial automation control technology, and more particularly to a method, apparatus and electronic device for automatic program burning. Background Technology

[0002] In fields such as new energy vehicle manufacturing and industrial intelligent control, various controllers, as core control components, need to be programmed to achieve preset functions. Programming is a critical process in the production and assembly of controllers. With the rapid development of the new energy vehicle industry, production lines are increasingly demanding higher efficiency, accuracy, and universal adaptability in controller programming.

[0003] Currently, the industry mainly uses dedicated programming tools in conjunction with manual operation to program controllers. During the operation, the operator first identifies the type of the target to be programmed, manually collects relevant information about the target, and then filters the matching application file from the locally stored files based on this information. At the same time, the operator manually configures the programming configuration information such as programming protocol and communication parameters that match the target. After configuration, the programming tool is started to program the application data into the controller. Some programming tools have developed dedicated versions for different types of targets to be programmed, and the operator needs to switch to the corresponding programming tool version according to the actual needs.

[0004] However, the above-mentioned burning process relies heavily on human expertise and is prone to failure due to various matching operation errors. Summary of the Invention

[0005] This application provides a method, apparatus, and electronic device for automatic program burning, in order to achieve automated burning and improve the burning success rate.

[0006] In a first aspect, this application provides a method for automatically burning a program, the method comprising:

[0007] When a target to be programmed is identified, the production identification information of the target to be programmed is automatically obtained;

[0008] The corresponding target application file is determined and downloaded from the corresponding software management system based on the production identification information; the target application file is a composite file that integrates the program data and burning configuration parameters of the target to be burned.

[0009] Based on the protocol identifier parsed from the target application file, the corresponding diagnostic protocol driver module is dynamically loaded;

[0010] Based on the diagnostic protocol driver module, the program data in the target application file is burned into the controller of the target to be burned.

[0011] In one possible implementation, the target application file has a hierarchical structure, including a metadata area and a data area;

[0012] The metadata area encapsulates the programming configuration parameters, which include the protocol identifier; the data area encapsulates the program data.

[0013] In one possible implementation, determining and downloading the corresponding target application file from the corresponding software management system based on the production identification information includes:

[0014] Based on the production identification information, the corresponding controller component information and the required application software information are retrieved from the software management system; the software information includes the application version number and model.

[0015] Based on the software information, a download request is initiated to the software management system to download the target application file that integrates the corresponding program data and burning configuration parameters.

[0016] In one possible implementation, dynamically loading the corresponding diagnostic protocol driver module based on the protocol identifier parsed from the target application file includes:

[0017] Parse the target application file to read the protocol identifier;

[0018] Based on the protocol identifier, request and download the corresponding diagnostic protocol driver file from the protocol server;

[0019] Load the diagnostic protocol driver file to instantiate the diagnostic protocol driver module.

[0020] In one possible implementation, the step of burning the program data from the target application file into the controller of the target to be burned, based on the diagnostic protocol driver module, includes:

[0021] Using the diagnostic protocol driver module, a diagnostic communication session is established with the controller of the target to be programmed;

[0022] In the diagnostic communication session, secure access, erasure, programming, and verification operations are performed to complete the burning of program data.

[0023] In one possible implementation, the method further includes:

[0024] Before or after the burning process begins, it interacts with the production line control system to control the flow or tooling status of the target to be burned.

[0025] Upload the burning process log and result status to the production information management system.

[0026] In one possible implementation, requesting and downloading the corresponding diagnostic protocol driver file from the protocol server based on the protocol identifier includes:

[0027] The protocol identifier is parsed to obtain version information; the version information includes the protocol version number and the update time.

[0028] Based on the version information, determine the latest version of the diagnostic protocol driver file that is compatible with the target application file;

[0029] If the latest version of the diagnostic protocol driver file is not present in the local cache or the protocol version has been updated, request and download the latest version of the diagnostic protocol driver file from the protocol server, and update the local cache according to the latest version of the diagnostic protocol driver file.

[0030] In one possible implementation, the automatic acquisition of the production identification information of the target to be programmed includes:

[0031] Read the identification barcode attached to the target to be burned or the corresponding carrier tooling, and obtain the production identification information from the production information management system based on the identification barcode;

[0032] And / or, receive a trigger signal from the production information management system or production line control system for automatically starting the programming process, wherein the trigger signal carries or is associated with the production identification information of the target to be programmed.

[0033] Secondly, this application provides an automatic program burning device, the device comprising:

[0034] The information acquisition module is used to automatically acquire the production identification information of the target to be programmed when the target to be programmed is identified;

[0035] The software management module is used to determine and download the corresponding target application file from the corresponding software management system based on the production identification information; the target application file is a composite file that integrates the program data and burning configuration parameters of the target to be burned.

[0036] The protocol loading module is used to dynamically load the corresponding diagnostic protocol driver module based on the protocol identifier parsed from the target application file;

[0037] The burning execution module is used to burn the program data in the target application file into the controller of the target to be burned, based on the diagnostic protocol driver module.

[0038] Thirdly, this application provides an electronic device, including at least one processor and a memory communicatively connected to the processor;

[0039] The memory stores computer-executed instructions;

[0040] The processor executes computer execution instructions stored in the memory to implement the method as described in any of the first aspects.

[0041] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any of the first aspects.

[0042] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method as described in any of the first aspects.

[0043] This application provides a method, apparatus, and electronic device for automatic program burning. The method proposes to automatically acquire the production identification information of the target to be burned, replacing the manual identification and information collection process. At the same time, it integrates program data and burning configuration parameters into the same composite file, eliminating the need for manual screening and matching of program files and configuration parameters. It can also dynamically load the corresponding diagnostic protocol driver module according to the protocol identifier in the composite file, completely eliminating the dependence on human expertise. From a technical process perspective, it completely avoids the possibility of errors in manual matching operations, effectively solving the problem of burning failure due to manual matching errors in known burning methods, and improving the burning success rate. Attached Figure Description

[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0045] Figure 1 This is a schematic diagram illustrating an application scenario of an automatic program burning method provided in an embodiment of this application;

[0046] Figure 2 A flowchart illustrating an automatic program burning method provided in this application embodiment. Figure 1 ;

[0047] Figure 3 A schematic diagram of the interface of the software management system provided in an embodiment of this application;

[0048] Figure 4 A flowchart illustrating an automatic program burning method provided in this application embodiment. Figure 2 ;

[0049] Figure 5 A schematic diagram of an automatic program burning device provided in this application embodiment;

[0050] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0051] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0052] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0053] In fields such as new energy vehicle manufacturing and industrial intelligent control, various controllers, as core control components, require programming to achieve preset functions. Programming is a critical process in controller production and assembly. Taking the battery pack controller of a new energy vehicle as an example, as the core unit of the battery management system, it directly affects key performance aspects such as battery charging and discharging strategies, safety protection, and status monitoring. Therefore, the quality of its programming directly affects the safety and reliability of the entire vehicle. With the rapid development of the new energy vehicle industry, the pace of model iteration is accelerating, and controller types are becoming increasingly diversified. The demand for efficiency, accuracy, and universal adaptability in controller programming is also increasing on production lines.

[0054] Currently, the industry primarily uses specialized programming tools combined with manual operation to program controllers. During the process, operators first visually or with a barcode scanner identify the type of the target device (e.g., battery pack controller, motor controller), manually collect its production identification information (e.g., PACK barcode, component model), and then, based on this information, systematically filter matching application files from locally stored files. Simultaneously, they manually configure the programming protocol (e.g., UDS diagnostic protocol) and communication parameters (e.g., baud rate, request ID, response ID) to match the target device. After configuration, the operator starts the programming tool to program the application data into the controller. Some programming tools have customized versions for different types of targets, requiring operators to switch to the appropriate tool version based on actual needs, and sometimes even reinstalling drivers or updating firmware.

[0055] It should be understood that the above burning process relies heavily on manual professionalism and is prone to burning failures due to various matching operation errors. For example, the operator may misselect the application program version, fill in the communication parameters incorrectly, or switch to the wrong burning tool version, resulting in the controller after burning being unable to communicate normally or having abnormal functions. This not only causes rework on the production line but may also pose potential safety hazards. At the same time, this manual-dependent burning method is difficult to adapt to the flexible production line requirements of multiple vehicle models and multiple controller types. The production line switching cost is high and the efficiency is low, which restricts the development of intelligent manufacturing.

[0056] Therefore, the embodiments of the present application provide an automatic program burning method, device, and electronic device to solve the above problems. Specifically, the method of the present application proposes that when a target to be burned is recognized, the production identification information of the target to be burned is automatically obtained; according to the production identification information, the corresponding target application program file is determined and downloaded from the corresponding software management system; according to the protocol identification parsed from the target application program file, the corresponding diagnostic protocol driver module is dynamically loaded; based on the diagnostic protocol driver module, the program data in the target application program file is burned into the controller of the target to be burned. Among them, the target application program file is a composite file integrating the program data and burning configuration parameters of the target to be burned.

[0057] It can be understood that the automatic program burning method of the present application is applicable to any industrial production line automation program burning scenario. Exemplarily, as described in the above background section, the method of the present application can be used in the application program burning process corresponding to the electric vehicle battery pack. Figure 1 The following is a schematic diagram of the application scenario of an automatic program burning method provided by an embodiment of the present application. As Figure 1 shown, the method of the present application is executed by the industrial control computer of the burning platform on the electric vehicle battery pack production line.

[0058] Specifically, at the burning station of the electric vehicle battery pack production, after the industrial control computer of the burning platform recognizes the battery pack to be burned, it automatically obtains the PACK barcode of the battery pack as the production identification information; then, according to the PACK barcode, it determines and downloads the target application program file corresponding to the controller matching the battery pack from the software management system supporting the production line. The target application program file is a composite file integrating the program data and burning configuration parameters of the battery pack controller; then the industrial control computer of the burning platform parses the protocol identification from the target application program file and dynamically loads the corresponding diagnostic protocol driver module according to the protocol identification; finally, based on the loaded diagnostic protocol driver module, the program data in the target application program file is burned into the controller of the battery pack.

[0059] In the above process, the industrial control computer of the programming platform uses the battery pack as the identification object and accurately matches the programming file of the corresponding controller through the PACK barcode. The entire process of obtaining the production identification, downloading the composite program file, loading the protocol driver module, and programming is completed automatically. There is no need for manual intervention in program screening, parameter configuration, etc., which fundamentally solves the problem of programming failure caused by manual matching operation errors in traditional programming methods. While ensuring the accuracy of battery pack controller programming, it also effectively improves the efficiency of program programming operations on the battery pack production line.

[0060] It should be understood that, in the above process, the executing entity of the method of this application can also be an industrial intelligent control device such as a production line edge computing terminal or an intelligent manufacturing central control host, and this embodiment does not limit this. In addition, the application scenario of the method of this application can also be other scenarios, such as the programming of new energy vehicle motor controllers, the programming of vehicle-mounted power distribution boxes, the programming of industrial robot core module firmware, etc., and this embodiment does not limit this.

[0061] The following detailed description, with reference to the accompanying drawings and using any electronic device as the execution subject, outlines some embodiments of the automatic program burning method of this application. Where the embodiments do not conflict, the following embodiments and features thereof can be combined with each other.

[0062] This application provides a method for automatic program burning. Figure 2 A flowchart illustrating an automatic program burning method provided in this application embodiment. Figure 1 ,like Figure 2 As shown, the method in this application embodiment includes:

[0063] S201. When a target to be programmed is identified, the production identification information of the target to be programmed is automatically obtained.

[0064] The target to be programmed is an industrial control component and a complete machine equipped with such a component that requires programming to achieve preset functions. It can be a single controller or a new energy vehicle battery pack, motor, distribution box, or other equipment that integrates a controller. The controller is the core programming object of the target to be programmed. After the programming is programmed, the target to be programmed can achieve the predetermined control, monitoring, and management functions.

[0065] In this embodiment, a battery pack is used as the target for programming. This battery pack integrates a battery management system controller, and a corresponding application needs to be programmed to realize functions such as battery charging and discharging control, safety protection, and status monitoring. During programming, the battery pack is placed in the programming station, and the electronic device is connected to the programming / communication interface reserved on the battery pack casing.

[0066] In this embodiment, the identification of the target to be programmed is achieved based on the signal detection of the production line station. The electronic device is communicatively connected to the sensors of the battery pack production programming station and the production line control system. When the sensor detects that the battery pack is transported to the preset position of the programming station by the automatic trolley, and the station positioning device completes the positioning and fixing of the battery pack, the production line control system sends a station arrival signal to the electronic device. After the electronic device receives the arrival signal, it confirms that the battery pack to be programmed has been identified.

[0067] In practical applications, the scanning module of the electronic device can also scan the target to be burned on the production line in real time. When the scanning module successfully identifies the identity barcode of the target to be burned, it confirms that the target to be burned has been identified. Alternatively, the target to be burned can establish a wireless / wired communication connection with the electronic device. When the electronic device successfully detects the communication connection signal, it confirms that the target to be burned has been identified. This application does not limit this.

[0068] In this embodiment, the electronic device reads the identity barcode attached to the target to be programmed or the corresponding carrier tooling, and obtains the production identification information from the production information management system based on the identity barcode; and / or receives a trigger signal from the production information management system or the production line control system to automatically start the programming process, wherein the trigger signal carries or is associated with the production identification information of the target to be programmed.

[0069] Specifically, in this embodiment, the electronic device is equipped with a barcode scanning and identification module. This module can scan the one-dimensional / two-dimensional identification barcode attached to the surface of the battery pack or its supporting tooling tray through hardware devices such as barcode scanners and barcode cameras. After scanning, it parses the basic coding information in the barcode and initiates a data query request to the production information management system based on the coding information. The production information management system matches and returns the complete production identification information corresponding to the battery pack according to the coding information.

[0070] Meanwhile, the electronic equipment establishes a real-time communication connection with the production information management system and the production line programmable logic controller. When the battery pack arrives, the production information management system or the production line programmable logic controller will send a programming start trigger signal to the electronic equipment. This signal directly carries production identification information or carries an identification code that can be associated with the production information management system. The electronic equipment can obtain complete production identification information by parsing the signal or by making a secondary query. The above two methods can be executed individually or in combination.

[0071] For battery pack programming scenarios, production identification information includes basic battery pack information and distribution box information. The basic battery pack information includes at least the PACK barcode, battery pack model, production batch, vehicle model, and controller component code. The distribution box information includes the distribution box barcode and model number that match the battery pack. As a core component of the battery pack, the information of the distribution box is crucial for matching the controller application. Electronic devices need to obtain both the basic battery pack information and the distribution box information to achieve accurate application matching.

[0072] In practical applications, production identification information can also be obtained by collecting hardware information of the target to be programmed. The electronic device establishes a temporary connection with the battery pack controller through the communication interface, reads the controller's inherent information such as hardware serial number and model, and matches the corresponding production identification information from the database based on the hardware information. Alternatively, the production plan data of the target to be programmed can be directly pushed through the production information management system of the production line. The electronic device matches the production identification information of the corresponding battery pack according to the workstation and timing information of the production plan. This application does not limit this.

[0073] The method for obtaining production identification information provided in this embodiment achieves automated, unmanned acquisition of production identification information by combining barcode recognition and system trigger signals, avoiding errors caused by manual data collection and entry, and improving the accuracy of information acquisition. Furthermore, obtaining standardized and structured production identification information from the production information management system ensures the integrity and consistency of the information, laying a data foundation for accurate matching in subsequent applications. Simultaneously, the compatible design of multiple acquisition methods can adapt to the automation configuration of different production lines, improving the method's versatility and adaptability. In addition, for battery pack scenarios, simultaneously acquiring battery pack and distribution box information enables multi-dimensional information association between the pack, box, and controller, further avoiding application matching errors.

[0074] S202. Based on the production identification information, determine and download the corresponding target application file from the corresponding software management system.

[0075] The target application file is a composite file that integrates the program data of the target to be burned and the burning configuration parameters.

[0076] In this embodiment, the target application file has a hierarchical structure, including a metadata area and a data area; wherein, the metadata area encapsulates the burning configuration parameters, which include the protocol identifier; the data area encapsulates the program data.

[0077] More specifically, the target application file is a custom composite format file (in this embodiment, it is in .ZCK format) that is pre-developed and configured by the R&D personnel based on the controller hardware parameters, functional requirements, and burning process requirements of the target to be burned. After compiling and processing the program data required for the controller to run, the R&D personnel integrate it with all the configuration parameters required for the burning process, encapsulate it according to the hierarchical structure of metadata area + data area, and finally generate the target application file. The file is then uploaded to the software management system for classified storage, so that electronic devices can query and download it based on the production identification information.

[0078] More specifically, the programming configuration parameters are all communication, protocol, and hardware matching parameters required to program the target device, including at least the protocol identifier, which is the unique identification information of the diagnostic protocol and is used to match the corresponding diagnostic protocol driver module; the program data are the executable program code, data tables, firmware information, etc. required for the controller of the target device to implement the preset functions, which are the core data for the controller operation. This data is compiled and encapsulated in binary form in the data area, and can be directly written to the controller's storage unit.

[0079] It should be understood that the programming configuration parameters and program data vary depending on the type, model, and functional requirements of the target device to be programmed. Different targets require different programming configuration parameters and program data. For example, for battery packs, the programming configuration parameters also include at least one of the following: programming task ID, communication interface type, communication baud rate, software version number, hardware compatibility identifier, ECU type, request ID, response ID, and function ID. All of these parameters are indispensable configuration bases during the battery pack controller programming process.

[0080] As a preferred design, in this embodiment, the target application file also includes a signature area. The signature area is a verification area independent of the metadata area and the data area. It encapsulates verification data, which contains information of at least one signature segment. Each signature segment is marked with a corresponding starting address and length. The starting address corresponds to the storage starting address of the program data, and the length is a preset verification data length. The verification data in the signature area is used to verify the integrity and authenticity of the program data after the file is downloaded and before parsing, so as to avoid data tampering, loss or damage during file transmission.

[0081] In practical applications, in addition to the metadata area, data area, and signature area, the target application file may also include a file remarks area and a version update area. The file remarks area can encapsulate remarks such as the file's development time, developers, and applicable scenarios, while the version update area can encapsulate the file's update logs, version iteration information, etc. The data encapsulated in each part can be flexibly adjusted and updated according to the needs of the target to be burned and the optimization of the burning process. For example, protocol-related configuration parameters can be added according to a new burning protocol, and program data can be updated according to controller function upgrades. This embodiment does not limit this.

[0082] Furthermore, in practical applications, the target application file may not be a hierarchical structure. The burning configuration parameters and program data can be mixed and packaged according to preset encoding rules. The electronic device can extract the corresponding burning configuration parameters and program data from the file through a preset parsing algorithm. This application does not limit this.

[0083] In this embodiment, the target application file is set up as a hierarchical structure. First, it achieves the classification and encapsulation of burning configuration parameters and program data, making the file structure clear and facilitating the electronic device to quickly parse and extract the required information, thus improving file parsing efficiency. Second, the hierarchical structure enables independent management and updating of data in each area. For example, when only the burning configuration parameters need to be adjusted, only the metadata area can be modified without changing the program data, reducing file maintenance costs. In addition, the independent signature area enables accurate verification of core program data, avoiding the impact of minor errors in configuration parameters on the verification results, and improving the targeting and accuracy of verification. Finally, the standardized hierarchical structure facilitates the software management system to classify, store, and retrieve files, improving file management efficiency.

[0084] In this embodiment, the software management system is a pre-built server system dedicated to the management of program files for burning. It communicates with the production information management system and electronic devices. The software management system pre-stores all application files that have been developed and configured in advance according to the controller hardware parameters and functional requirements of various targets to be burned. It also standardizes, classifies, stores and manages all files, and has functions such as file query, download, version update and data statistics. It can accurately match and return the corresponding target application file according to the query request sent by the electronic device.

[0085] As an example, Figure 3 The interface diagram of the software management system provided in the embodiments of this application is as follows: Figure 3As shown, for battery pack programming scenarios, the software management system provides a file management interface with project number, vehicle model, vehicle model code, and component code as search dimensions. The interface stores application files corresponding to various battery pack controller component codes under different project numbers, vehicle models, and vehicle model codes. It also marks file type (such as Flash file, S19 file, ZCK file), whether it is a neural network file, and other attribute information. Electronic devices can quickly match the corresponding ZCK format target application file under the corresponding search dimension based on the battery pack's production identification information.

[0086] Specifically, in this embodiment, the electronic device retrieves the corresponding controller component information and the required application software information from the software management system based on the production identification information; based on the software information, it initiates a download request to the software management system to download the target application file that integrates the corresponding program data and burning configuration parameters. The software information includes the application's version number and model.

[0087] More specifically, the electronic device parses the complete production identification information it obtains, extracting key information such as the target type, model, and controller component code, and then sends a retrieval request containing the aforementioned key information to the software management system. Upon receiving the request, the software management system searches its file library according to preset matching rules, matching the component information compatible with the controller of the target to be programmed, and further determines the application software information required for the component, including the application version number, model, format, and applicable programming process. After receiving the software information from the software management system, the electronic device sends a download request for the target application file to the software management system based on this software information, specifying the file's version number, model, and other information. According to the download request, the software management system retrieves the corresponding target application file from the file library and sends the file to the electronic device through an encrypted transmission channel. The electronic device receives and stores the file, completing the download process.

[0088] In the battery pack programming scenario, the electronic device parses the production identification information, extracts key information such as the PACK barcode, distribution box barcode, battery pack model, and controller component code, and sends a retrieval request containing the above information to the software management system. The software management system matches the corresponding battery pack hardware configuration information based on the PACK barcode and distribution box barcode, and then, combined with the model and controller component code, retrieves the component information corresponding to the battery pack controller in the system, thereby determining the version number, model, and other software information of the compatible ZCK format application. Based on this software information, the electronic device initiates a ZCK file download request to the software management system. The software management system retrieves the corresponding ZCK format target application file and sends it to the electronic device, which then completes the file reception and storage.

[0089] It should be understood that some battery packs are complex and integrate multiple controllers with different functions (such as battery management master controller, slave controller, safety controller, etc.). Each controller needs to be programmed with a corresponding application. In this case, the electronic device can retrieve the component information and software information corresponding to each controller from the software management system based on the production identification information, initiate download requests, download multiple corresponding target application files, and then program each controller in turn to achieve batch automatic programming of multiple controllers.

[0090] In practical applications, the software management system can also push the target application file to be burned to the local cache of the electronic device in advance based on the production plan data of the production information management system. When the electronic device recognizes the target to be burned, it can directly retrieve the corresponding file from the local cache without initiating a download request in real time. Alternatively, the electronic device can generate search keywords based on the production identification information, perform a fuzzy search in the software management system, match the application file with the highest similarity, and then download it after manual confirmation. This application does not limit this.

[0091] In this embodiment, the method of determining and downloading the target application file from the software management system based on production identification information achieves automated and accurate matching and downloading of application files, avoiding errors caused by manual file selection and eliminating burning failures due to file mismatch at the source. Secondly, the centralized management and unified distribution of application files through the software management system ensures that all electronic devices on the production line obtain consistent file versions and accurate information, improving the standardization of the burning process. In addition, file matching based on multi-dimensional production identification information, such as combining battery pack and distribution box information in the battery pack scenario, further improves the accuracy of file matching. At the same time, the classification storage and retrieval functions of the software management system facilitate file maintenance, updates, and management, reducing the file management cost of the production line.

[0092] S203. Based on the protocol identifier parsed from the target application file, dynamically load the corresponding diagnostic protocol driver module.

[0093] In this embodiment, the electronic device is equipped with a protocol driver module management module and a local storage cache. The protocol driver module management module has functions such as file parsing, protocol identifier recognition, protocol server communication, driver module loading and instantiation, and can realize dynamic management of the entire process of diagnostic protocol driver modules. The local storage cache can temporarily store downloaded diagnostic protocol driver modules for easy reuse later. Through the above configuration, the electronic device can dynamically load different diagnostic protocol driver modules according to different protocol identifiers, so as to realize the burning requirements of multiple diagnostic protocols compatible with one burning platform.

[0094] In this embodiment, the electronic device parses the target application file to read the protocol identifier; based on the protocol identifier, it requests and downloads the corresponding diagnostic protocol driver file from the protocol server; and loads the diagnostic protocol driver file to instantiate the diagnostic protocol driver module.

[0095] Specifically, for target application files with layered settings, the electronic device first verifies the overall integrity of the file using a preset layered parsing algorithm. After the verification is successful, it locates the file's metadata area, parses it according to the encapsulation rules of the metadata area, and extracts the protocol identifier from the configuration parameters of the metadata area. This protocol identifier is a preset string or encoding that corresponds one-to-one with the diagnostic protocol driver file in the protocol server.

[0096] The preset layered parsing algorithm is a structured parsing algorithm based on the layered structure of the target application file. This algorithm is pre-configured with parsing rules that match the file layering encapsulation rules. First, it reads the header identifier of the file to determine the number of file layers and basic information such as the starting address, data length, and encapsulation format of each region. Then, it performs integrity verification on the byte stream data of each region according to the preset verification rules. After the verification is passed, it locates the metadata region according to the starting address and data length of the metadata region. It then parses out various configuration parameters in the metadata encapsulation rules such as key-value pairs and fixed bit order. Finally, it extracts the protocol identifier related fields to complete the parsing.

[0097] It should be understood that if the target application file does not have a signature area, the electronic device will directly perform layered parsing of the file without performing the signature area verification step, and the rest of the parsing process is the same as for files with a signature area; if the target application file does not have layered settings, the electronic device will use a preset general parsing algorithm to search for and extract the protocol identifier in the file according to the preset encoding rules of the protocol identifier, and complete the parsing process.

[0098] The preset general parsing algorithm is a feature field retrieval-based parsing algorithm. This algorithm is pre-configured with preset encoding rules such as the feature start character, feature end character, and field length of the protocol identifier. By traversing the binary byte stream of the file segment by segment, after matching the protocol identifier feature field that conforms to the preset encoding rules, the algorithm extracts the content corresponding to the feature field as the protocol identifier, thus completing the extraction and parsing. If the protocol identifier is a fixed-length code, the algorithm can directly locate and extract the protocol identifier in the file according to the preset encoding position offset.

[0099] Specifically, after the electronic device extracts the protocol identifier, it parses it to determine the corresponding diagnostic protocol type, version, and other information. Then, it sends a download request containing the protocol identifier and the diagnostic protocol type and version to a preset protocol server. This protocol server is a pre-built server system dedicated to storing and distributing diagnostic protocol driver files. The system stores driver files (in this embodiment, .dll dynamic link library files) corresponding to various diagnostic protocols.

[0100] Correspondingly, after receiving the download request, the protocol server matches the corresponding diagnostic protocol driver file according to the protocol identifier and sends the file to the electronic device. After receiving the driver file, the electronic device loads it into the system operating environment through the protocol driver module management module and performs instantiation processing to generate a diagnostic protocol driver module that can be directly called. This module can realize diagnostic communication and program burning control with the target controller to be programmed.

[0101] For battery pack programming scenarios, the electronic device parses the metadata area of ​​the ZCK format target application file and extracts the UDS diagnostic protocol identifier, which is the version and type encoding of the UDS protocol. Subsequently, the electronic device sends a download request containing the UDS protocol identifier to the protocol server. The protocol server matches the corresponding UDS protocol dynamic link library (.dll) file and sends it to the electronic device. After receiving the .dll file, the electronic device loads and instantiates it through the protocol driver module management module to generate the UDS diagnostic protocol driver module. This module encapsulates all the communication and programming logic of the UDS diagnostic protocol, enabling UDS protocol communication and program programming with the battery pack controller.

[0102] In practical applications, the electronic device can also send the parsed protocol identifier to the software management system, which then acts as an intermediary to request the corresponding diagnostic protocol driver file from the protocol server and forward the file to the electronic device. Alternatively, the protocol server can push the diagnostic protocol driver file to the software management system and store it together with the target application file. When the electronic device downloads the target application file, it also downloads the corresponding diagnostic protocol driver file. This embodiment does not limit this approach.

[0103] As a preferred example, when downloading the corresponding diagnostic protocol driver file, the electronic device first parses the protocol identifier to obtain version information; based on the version information, it determines the latest version of the diagnostic protocol driver file compatible with the target application file; if the latest version of the diagnostic protocol driver file does not exist in the local cache or the protocol version has been updated, it requests and downloads the latest version of the diagnostic protocol driver file from the protocol server, and updates the local cache according to the latest version of the diagnostic protocol driver file. The version information includes the protocol version number and the update time.

[0104] Specifically, in this embodiment, when dynamically loading the diagnostic protocol driver module, the electronic device introduces a version control mechanism. The protocol driver module management module performs deep parsing on the parsed protocol identifier to obtain information such as the protocol version number and update time. This enables the burning platform to match the latest version of the protocol module (such as a .dll library) based on the protocol identifier in the file header, while refusing to load low-version or high-version protocol modules that are incompatible with the target application file.

[0105] Meanwhile, the electronic device is designed with a local caching strategy. It stores downloaded and instantiated protocol modules in the local storage cache and records information such as protocol identifier, version number, and cache time. When a protocol with the same identifier and unchanged version is parsed again, the corresponding protocol module is directly retrieved from the local cache and loaded without having to send a download request to the protocol server again. If it is detected that the version corresponding to the protocol identifier has been updated, the electronic device downloads the new version of the protocol module from the protocol server first, stores it in the local cache, replaces the original old version module, and completes the cache update.

[0106] Based on this setup, the version control mechanism ensures that the burning platform always uses protocol modules compatible with the burning files, technically avoiding communication failures and burning interruptions caused by protocol version incompatibility, effectively improving the burning success rate. The caching strategy reduces repeated download requests to the protocol server, effectively lowering the network load and operational pressure on the backend server, and improving server service stability. Simultaneously, local cache loading replaces network downloads, shortening protocol module loading time and improving the efficiency of pre-burning work, especially in high-frequency, high-volume burning tasks. Furthermore, the automatic cache replacement mechanism after version updates eliminates the need for manual intervention in protocol module updates and maintenance on the production line, achieving automated iteration of the protocol modules, ensuring the production line's ability to quickly adapt to protocol changes, and improving the production line's flexible production level.

[0107] In this embodiment, the method of parsing the protocol identifier from the target application file and dynamically loading the corresponding diagnostic protocol driver module automates and loads the diagnostic protocol driver module on demand, eliminating the need for manual installation and switching of protocol drivers, avoiding errors caused by manual operation, and improving the automation level of the burning process. Secondly, by dynamically loading different diagnostic protocol driver modules, an electronic device (burning platform) can be compatible with the burning requirements of multiple diagnostic protocols, breaking the traditional binding relationship between the burning platform and the protocol, solving the pain point of the production line needing to maintain multiple burning platforms for different protocols, and effectively reducing the equipment investment and maintenance costs of the production line. In addition, the centralized management and unified distribution of diagnostic protocol driver files through the protocol server ensures that the protocol module versions loaded on all electronic devices in the production line are consistent, improving the standardization of the burning process.

[0108] S204. Based on the diagnostic protocol driver module, the program data in the target application file is burned into the controller of the target to be burned.

[0109] Specifically, in this embodiment, the electronic device uses a diagnostic protocol driver module to establish a diagnostic communication session with the controller of the target to be programmed; in the diagnostic communication session, secure access, erasure, programming and verification operations are performed to complete the programming of program data.

[0110] More specifically, the electronic device calls the instantiated diagnostic protocol driver module and sends a diagnostic communication establishment request to the controller of the target device to be programmed through a preset communication interface (such as a CAN bus interface). This request includes the controller's identification information, communication parameters, etc. After receiving the request, the controller performs identity verification and parameter matching according to the diagnostic protocol. After successful verification and matching, a stable diagnostic communication session is established with the electronic device.

[0111] After the communication session is established, the electronic device, through the diagnostic protocol driver module, follows the standard procedure of the diagnostic protocol to first send a security access request to the controller to unlock the controller and obtain the operation permission for program burning. Then, it sends an erase command to erase the original program data in the controller's storage unit, reserving space for writing new program data. After erasure, the electronic device extracts the program data from the data area of ​​the target application file, segments and encodes it according to the transmission rules of the diagnostic protocol, and writes the program data step by step into the controller's storage unit through the diagnostic communication session to complete the programming operation.

[0112] After the programming operation is completed, the electronic device sends a verification command to read the program data written in the controller and compare it with the original program data in the target application file, or to perform integrity verification through verification code, hash value, etc. If the verification passes, the burning is considered successful; if the verification fails, a retry or alarm mechanism is triggered.

[0113] In the battery pack programming scenario, the electronic device calls the UDS diagnostic protocol driver module and sends a UDS diagnostic communication establishment request to the battery pack controller via the CAN bus interface. After the controller completes the verification, it establishes a UDS diagnostic communication session with the electronic device. The electronic device sends a secure access service command to the controller via the UDS protocol to complete the secure unlocking of the controller. Subsequently, it sends an erase memory service command to erase the original program data in the controller's Flash storage area. After erasure, the electronic device extracts the program data of the battery pack controller from the data area of ​​the ZCK file, performs block transmission according to the programming service rules of the UDS protocol, and writes the program data into the controller's Flash storage area. After programming, the electronic device reads the programmed program data in the controller through the verification service command of the UDS protocol, compares it with the original program data in the ZCK file, or verifies the checksum of the program data. If the verification passes, the program programming of the battery pack controller is completed. If the verification fails, an alarm signal is sent to the production line control system to prompt manual inspection.

[0114] In practical applications, when establishing a diagnostic communication session, multiple authentication steps can be added, such as password verification and hardware serial number verification, to improve communication security. For secure access, a dynamic key unlocking method can be used instead of a fixed password to further enhance controller security. During the erasure process, partial erasure can be performed based on the storage range of the program data, eliminating the need to erase all storage units of the controller and shortening erasure time. During the programming process, multi-threading and high-speed transmission can be used to improve the writing speed of program data. For the verification process, an offline verification method can be used, exporting the controller's program data to the local machine for verification after programming, reducing the impact of the communication link on verification. This embodiment does not limit this approach.

[0115] In the above process, the method of burning based on the diagnostic protocol driver module realizes the automation and standardization of the entire program burning process, without any manual intervention, thus improving burning efficiency. At the same time, the above process strictly follows the standard procedure of the diagnostic protocol to perform the burning operation, ensuring the standardization and accuracy of the burning process, and effectively improving the burning success rate.

[0116] Furthermore, the above process achieves standardized communication with the controller through the diagnostic protocol driver module, breaking down communication barriers between different brands and models of controllers and improving the method's versatility. At the same time, each step in the programming process has clear instructions and feedback, facilitating full monitoring and traceability of the programming process, and allowing for rapid location of the problem if a fault occurs. For battery pack scenarios, the programming process based on the UDS protocol complies with industry standards for new energy vehicle controllers, ensuring the operational stability and safety of the battery pack controller after programming.

[0117] As can be seen from the above, the method provided in this embodiment achieves full-process automation through S201 to S204, realizing the entire process of the target to be burned from identification, acquisition of production identification information, matching and downloading of application files, to dynamic loading of protocol driver module and burning of program without human intervention. This effectively solves the problem that traditional burning methods rely heavily on human expertise and are prone to burning failure due to human matching operation errors, thereby improving the accuracy and success rate of burning.

[0118] In this embodiment, by integrating a composite application file and dynamically loading a diagnostic protocol driver module, a single programming platform achieves compatibility with multiple programming targets and multiple diagnostic protocols. This solves the pain point of traditional production lines requiring the maintenance of multiple programming platforms, reducing equipment investment and maintenance costs. Simultaneously, through linkage with the production information management system, software management system, and protocol server, standardized and data-driven management of the programming process is achieved, ensuring traceability and consistency and improving the production line's production management level. Furthermore, the method is highly versatile and adaptable, suitable for different types of programming targets and different industrial production line automation configurations, possessing broad industrial application value.

[0119] This application also provides an embodiment of an automatic program burning method. Figure 4 A flowchart illustrating an automatic program burning method provided in this application embodiment. Figure 2 ,like Figure 4 As shown, the method in this embodiment includes:

[0120] S401. Before or after the burning process begins, interact with the production line control system to control the flow of the target to be burned or the tooling status.

[0121] Specifically, the production line control system is the core control system of the industrial production line. In this embodiment, it is a programmable logic controller (PLC), which communicates with the production line's automated transport equipment (such as automated guided vehicles (AGVs), tooling equipment (such as robotic arms, wire harness connectors, and workstation positioning devices), sensors, and electronic equipment. It is responsible for the overall process control, equipment scheduling, and status monitoring of the production line.

[0122] Before the programming process begins, the electronic device completes the acquisition of production identification information, download of application files, and loading of protocol driver modules. Then, it sends a programming readiness signal to the production line control system. Upon receiving this signal, the production line control system controls the automatic trolley to accurately transport the target to be programmed to the programming station and controls the station positioning device to fix the target to be programmed. Subsequently, it controls the robotic arm to grab the programming wiring harness and automatically plug it into the communication interface of the target to be programmed, completing the tooling preparation before programming.

[0123] After programming is completed, if programming is successful, the electronic device sends a programming success signal to the production line control system. Upon receiving the signal, the production line control system controls the robotic arm to remove the programming cable from the target to be programmed, releases the station positioning device, and then controls the automatic trolley to transport the programmed target to the next production station. If programming fails, the electronic device sends a programming failure alarm signal to the production line control system. Upon receiving the signal, the production line control system suspends the operation of that station and triggers an audible and visual alarm to prompt manual on-site inspection of the fault. After the fault is resolved, the production line operation and tooling operation are resumed according to manual instructions.

[0124] For the battery pack programming scenario, the flow of the aforementioned target to be programmed is the transportation of the battery pack between the programming station and the upstream / downstream process stations. The tooling status control includes the automatic insertion and removal of the battery pack programming CAN harness by the robotic arm, and the positioning, fixing and releasing of the battery pack by the programming station. The entire process realizes automated control of battery pack flow and tooling operation.

[0125] S402. Upload the burning process log and result status to the production information management system.

[0126] In this embodiment, the burning process log is structured and standardized data recorded by the electronic device throughout the entire burning process. It includes at least the production identification information of the target to be burned, the burning start time, the burning end time, the operation instructions for each stage, the execution status of each stage, communication parameters, protocol module information, and file parsing information. The log data can completely reconstruct the entire burning process. The result status is the final execution result of the burning, including burning success and burning failure. If the burning fails, it also needs to include information such as the reason for failure and the failed stage, such as file parsing failure, communication establishment failure, and verification failure.

[0127] In the battery pack programming scenario, after programming is completed, the electronic device associates the battery pack's PACK barcode, distribution box barcode, vehicle model, and other production identification information with the programming process log and programming result status, and uploads them together to the production information management system. After receiving the above information, the production information management system stores it in the production database and integrates it with other production data such as the battery pack's production batch, workstation information, and testing data to form a complete production file for the battery pack.

[0128] Meanwhile, the production information management system can perform data statistics and analysis based on the burning results, such as the burning success rate, failure types and proportions, to provide data support for production line optimization. If the burning is successful, the production information management system marks the battery pack as burned successfully, allowing it to enter the next production process. If the burning fails, the production information management system marks the battery pack as unqualified, restricts its circulation, and records the fault information for easy traceability and rework.

[0129] In the method provided in this embodiment, the interaction between the programming process and the production line control system before and after the programming process realizes the automated control of the flow of the target to be programmed and the tooling status, so that the programming is seamlessly connected with other production processes on the production line, forming a closed loop of full-process automation of the production line, which effectively improves the overall automation level and production efficiency of the production line. At the same time, the automated control of the tooling status avoids errors caused by manual wiring harness insertion and target positioning, improves the accuracy of pre-programming preparation work, and further ensures the smooth progress of the programming process.

[0130] Furthermore, the automatic alarm and production line pause mechanism after a programming failure can quickly detect faults and prevent defective products from flowing into the next process, improving the quality control level of the production line. By uploading the programming process log and result status to the production information management system, full data traceability of the programming process is achieved, facilitating production line managers to monitor, analyze, and troubleshoot the programming process, thus improving the production management level of the production line. At the same time, the integration of programming data with other production data forms a complete production file of the target to be programmed, meeting the digital management needs of intelligent industrial manufacturing. In addition, data analysis based on the programming result status can provide data support for production line process optimization, equipment maintenance, and fault early warning, helping to continuously optimize and improve the efficiency of the production line. For core components of new energy vehicles such as battery packs, complete programming data traceability can also meet the quality traceability requirements of the automotive industry, improving the product quality assurance capabilities.

[0131] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0132] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0133] The above embodiments introduce an automatic program burning method from the perspective of process flow. The following embodiments introduce an automatic program burning device from the perspective of virtual module or virtual unit. For details, please refer to the following embodiments.

[0134] This application also provides an automatic program burning device for implementing the methods described in the above method embodiments. Figure 5 This is a schematic diagram of the structure of an automatic program burning device provided in an embodiment of this application, as shown below. Figure 5 As shown, in this embodiment, the automatic program burning device may include:

[0135] The information acquisition module 51 is used to automatically acquire the production identification information of the target to be programmed when the target to be programmed is identified;

[0136] Software management module 52 is used to determine and download the corresponding target application file from the corresponding software management system based on the production identification information; the target application file is a composite file that integrates the program data of the target to be burned and the burning configuration parameters;

[0137] Protocol loading module 53 is used to dynamically load the corresponding diagnostic protocol driver module based on the protocol identifier parsed from the target application file;

[0138] The programming execution module 54 is used to program data in the target application file into the controller of the target to be programmed, based on the diagnostic protocol driver module.

[0139] In one possible implementation of this application embodiment, the target application file has a hierarchical structure, including a metadata area and a data area;

[0140] The metadata area encapsulates the programming configuration parameters, including the protocol identifier; the data area encapsulates the program data.

[0141] In one possible implementation of this application embodiment, the software management module 52 is specifically used for:

[0142] Based on production identification information, retrieve the corresponding controller component information and the required application software information from the software management system; the software information includes the application version number and model.

[0143] Based on the software information, a download request is sent to the software management system to download the target application file that integrates the corresponding program data and burning configuration parameters.

[0144] In one possible implementation of this application embodiment, the protocol loading module 53 is specifically used for:

[0145] Parse the target application file to read the protocol identifier;

[0146] Based on the protocol identifier, request and download the corresponding diagnostic protocol driver file from the protocol server;

[0147] Load the diagnostic protocol driver file to instantiate the diagnostic protocol driver module.

[0148] In one possible implementation of this application embodiment, the programming execution module 54 is specifically used for:

[0149] The diagnostic protocol driver module is used to establish a diagnostic communication session with the controller of the target to be programmed.

[0150] During the diagnostic communication session, secure access, erasure, programming, and verification operations are performed to complete the burning of program data.

[0151] In one possible implementation of this application embodiment, the programming execution module 54 is further configured to:

[0152] Before or after the burning process begins, it interacts with the production line control system to control the flow of the target to be burned or the tooling status.

[0153] Upload the burning process log and result status to the production information management system.

[0154] In one possible implementation of this application embodiment, the protocol loading module 53 is specifically used for:

[0155] Parse the protocol identifier to obtain version information; the version information includes the protocol version number and update time.

[0156] Determine the latest version of the diagnostic protocol driver file that is compatible with the target application file based on the version information;

[0157] If the latest version of the diagnostic protocol driver file is not available in the local cache or the protocol version has been updated, request and download the latest version of the diagnostic protocol driver file from the protocol server, and update the local cache according to the latest version of the diagnostic protocol driver file.

[0158] In one possible implementation of this application embodiment, the information acquisition module 51 is specifically used for:

[0159] Read the identification barcode attached to the target to be burned or the corresponding carrier tooling, and obtain the production identification information from the production information management system based on the identification barcode;

[0160] And / or, receive a trigger signal from the production information management system or production line control system to automatically start the programming process, wherein the trigger signal carries or is associated with the production identification information of the target to be programmed.

[0161] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0162] This application provides an electronic device. Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 6 As shown, Figure 6 The illustrated electronic device includes at least one processor 61 and a memory 62. The processor 61 and the memory 62 are connected, for example, via a bus 63. Optionally, the electronic device may also include a transceiver 64. It should be noted that in practical applications, the transceiver 64 is not limited to one, and the structure of this electronic device does not constitute a limitation on the embodiments of this application.

[0163] Processor 61 may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 61 may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0164] Bus 63 may include a pathway for transmitting information between the aforementioned components. Bus 63 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 63 may be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0165] The memory 62 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0166] The memory 62 stores computer execution instructions for implementing the scheme of this application, and the processor 61 controls the execution. The processor 61 executes the computer execution instructions stored in the memory 62 to implement the content shown in the foregoing method embodiments.

[0167] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores computer-executable instructions, which are used to implement the methods in the above embodiments.

[0168] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the technical solution of the above method embodiments. Its implementation principle and technical effects are similar, and will not be repeated here.

[0169] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0170] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0171] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for automatically burning programs, characterized in that, The method includes: When a target to be programmed is identified, the production identification information of the target to be programmed is automatically obtained; The corresponding target application file is determined and downloaded from the corresponding software management system based on the production identification information; the target application file is a composite file that integrates the program data and burning configuration parameters of the target to be burned. Based on the protocol identifier parsed from the target application file, the corresponding diagnostic protocol driver module is dynamically loaded; Based on the diagnostic protocol driver module, the program data in the target application file is burned into the controller of the target to be burned.

2. The method according to claim 1, characterized in that, The target application file has a hierarchical structure, including a metadata area and a data area; The metadata area encapsulates the programming configuration parameters, which include the protocol identifier; the data area encapsulates the program data.

3. The method according to claim 1 or 2, characterized in that, The step of determining and downloading the corresponding target application file from the corresponding software management system based on the production identification information includes: Based on the production identification information, the corresponding controller component information and the required application software information are retrieved from the software management system; the software information includes the application version number and model. Based on the software information, a download request is initiated to the software management system to download the target application file that integrates the corresponding program data and burning configuration parameters.

4. The method according to claim 1 or 2, characterized in that, The step of dynamically loading the corresponding diagnostic protocol driver module based on the protocol identifier parsed from the target application file includes: Parse the target application file to read the protocol identifier; Based on the protocol identifier, request and download the corresponding diagnostic protocol driver file from the protocol server; Load the diagnostic protocol driver file to instantiate the diagnostic protocol driver module.

5. The method according to claim 1 or 2, characterized in that, The step of burning program data from the target application file into the controller of the target to be burned, based on the diagnostic protocol driver module, includes: Using the diagnostic protocol driver module, a diagnostic communication session is established with the controller of the target to be programmed; In the diagnostic communication session, secure access, erasure, programming, and verification operations are performed to complete the burning of program data.

6. The method according to claim 1 or 2, characterized in that, The method further includes: Before or after the burning process begins, it interacts with the production line control system to control the flow or tooling status of the target to be burned. Upload the burning process log and result status to the production information management system.

7. The method according to claim 4, characterized in that, The step of requesting and downloading the corresponding diagnostic protocol driver file from the protocol server based on the protocol identifier includes: The protocol identifier is parsed to obtain version information; the version information includes the protocol version number and the update time. Based on the version information, determine the latest version of the diagnostic protocol driver file that is compatible with the target application file; If the latest version of the diagnostic protocol driver file is not present in the local cache or the protocol version has been updated, request and download the latest version of the diagnostic protocol driver file from the protocol server, and update the local cache according to the latest version of the diagnostic protocol driver file.

8. The method according to claim 1 or 2, characterized in that, The automatic acquisition of the production identification information of the target to be programmed includes: Read the identification barcode attached to the target to be burned or the corresponding carrier tooling, and obtain the production identification information from the production information management system based on the identification barcode; And / or, receive a trigger signal from the production information management system or production line control system for automatically starting the programming process, wherein the trigger signal carries or is associated with the production identification information of the target to be programmed.

9. An automatic program burning device, characterized in that, The device includes: The information acquisition module is used to automatically acquire the production identification information of the target to be programmed when the target to be programmed is identified; The software management module is used to determine and download the corresponding target application file from the corresponding software management system based on the production identification information; the target application file is a composite file that integrates the program data and burning configuration parameters of the target to be burned. The protocol loading module is used to dynamically load the corresponding diagnostic protocol driver module based on the protocol identifier parsed from the target application file; The burning execution module is used to burn the program data in the target application file into the controller of the target to be burned, based on the diagnostic protocol driver module.

10. An electronic device, characterized in that, It includes at least one processor and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-8.

Images