Diagnostic code generation method and device and electronic equipment

Abstract

The embodiment of the invention discloses a diagnosis code generation method and device and electronic equipment. The method comprises the following steps: acquiring configuration information in an original configuration file; replacing the configuration information with the information category identifier to obtain a template configuration file; extracting DID information of each diagnosis service from the diagnosis demand document; and filling the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code. Through the mode, the configuration information in the original configuration file can be obtained, and the configuration information is replaced by the information category identifier to obtain the template configuration file; and extracting the DID information of each diagnosis service from the diagnosis demand document, and filling the DID information of each diagnosis service into the information category identifier corresponding to the template configuration file to generate the diagnosis code, so that automatic configuration of the diagnosis code is realized, and the development efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a diagnostic code generation method, device and electronic device. Background Art

[0002] With the continuous development and popularization of AUTOSAR (AUTomotive Open System Architecture), there are more and more AUTOSAR tool developers, and automotive electronic software development will use a variety of AUTOSAR tools to develop diagnostic codes. Among the related methods, manual configuration is usually used for diagnostic code development, with numerous configuration parameters, resulting in low development efficiency. Summary of the invention

[0003] In view of the above problems, the present application proposes a diagnostic code generation method, device and electronic device to improve the above problems.

[0004] In a first aspect, the present application provides a method for generating a diagnostic code, the method comprising: obtaining configuration information in an original configuration file; replacing the configuration information with an information category identifier to obtain a template configuration file; extracting DID information of each diagnostic service from a diagnostic requirement document, the DID information representing data involved in the corresponding diagnostic service; filling the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

[0005] In the second aspect, the present application provides a diagnostic code generation device, which includes: a template configuration file generation unit, used to obtain configuration information in an original configuration file; replace the configuration information with an information category identifier to obtain a template configuration file; an information extraction unit, used to extract DID information of each diagnostic service from a diagnostic requirement document, wherein the DID information represents data involved in the corresponding diagnostic service; and a diagnostic code generation unit, used to fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

[0006] In a third aspect, the present application provides an electronic device comprising one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the above-mentioned method.

[0007] In a fourth aspect, the present application provides a computer-readable storage medium, in which program code is stored, wherein the above method is executed when the program code is run.

[0008] The present application provides a diagnostic code generation method, device, electronic device and storage medium. After obtaining the configuration information in the original configuration file, the configuration information is replaced with an information category identifier to obtain a template configuration file, and the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code. Through the above method, the configuration information in the original configuration file can be obtained, and the configuration information is replaced with an information category identifier to obtain a template configuration file; the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code, thereby realizing automatic configuration of the diagnostic code and improving development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0010] Figure 1 A flowchart of a diagnostic code generation method proposed in an embodiment of the present application is shown;

[0011] Figure 2 Shows Figure 1 A flowchart of an implementation method of S140;

[0012] Figure 3 A schematic diagram showing a mapping relationship between DTC information, OBD information, diagnostic service information, and DID information of each diagnostic service and cache respectively proposed in the present application;

[0013] Figure 4 A flowchart of a diagnostic code generation method proposed in another embodiment of the present application is shown;

[0014] Figure 5 A structural block diagram of a diagnostic code generating device proposed in an embodiment of the present application is shown;

[0015] Figure 6 A structural block diagram of an electronic device proposed in this application is shown. DETAILED DESCRIPTION

[0016] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0017] In an embodiment of the present application, the inventor proposes a diagnostic code generation method, device, and electronic device. After obtaining the configuration information in the original configuration file, the configuration information is replaced with an information category identifier to obtain a template configuration file, and the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code. Through the above method, the configuration information in the original configuration file can be obtained, and the configuration information is replaced with an information category identifier to obtain a template configuration file; the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code, thereby realizing automatic configuration of the diagnostic code and improving development efficiency.

[0018] See also Figure 1 , an embodiment of the present application provides a method for generating a diagnostic code, the method comprising:

[0019] S110: Obtain configuration information in the original configuration file.

[0020] The original configuration file may refer to a configuration file that has been configured in order to develop other diagnostic codes. The configuration information may include at least one of the following: diagnostic service dispatch (Diagnostic Communication Manager DiagnosticService Dispatcher, DcmDsd) information, diagnostic service process (Diagnostic Communication Manager Diagnostic Service Processing, DcmDsp) information, UDS service (Unified Diagnostic Services) configuration information in DEM (Diagnostic Event Manager, Diagnostic Event Management), OBD (On-Board Diagnostic, On-Board Diagnostic System) service configuration information in DEM, and FIM (Function Inhibition Manager, Function Inhibition Module) configuration information. The UDS service configuration information and OBD service configuration information in DEM can be obtained from the DemConfigSet of the original configuration file, and the FIM configuration information can be obtained from the FiMConfigSet of the original configuration file.

[0021] As a method, the configuration information in the original configuration file can be obtained according to the Dcm, Dem, and FiM standard configuration options of AUTOSAR. In other words, different configuration information in the original configuration file can each correspond to a keyword or a key information category identifier. By identifying the corresponding keyword or key information category identifier, the starting position of different configuration information in the original configuration file can be determined, thereby extracting the configuration information.

[0022] S120: Replace the configuration information with the information category identifier to obtain a template configuration file.

[0023] The information category identifier can be used to indicate the location of the configuration information in the original configuration file. Each configuration information can correspond to an information category identifier. The template configuration file can be in the xdm format of EB tresos, the arxml format of Vector and NeuSAR, etc.

[0024] As a method, the configuration information in the original configuration file may be replaced with the corresponding information category identifier, so that the replaced original configuration file is used as a template configuration file.

[0025] Optionally, the information category identifier: DcmDsd_Value can be used to replace the diagnostic service scheduling information, the information category identifier: DcmDsp_Value can be used to replace the diagnostic service process information, the information category identifier: DemDtcValue can be used to replace the UDS service configuration information in the DEM, the information category identifier: DemPidClassValue can be used to replace the OBD service configuration information in the DEM, and the information category identifier: FiM_Value can be used to replace the FIM configuration information.

[0026] S130: Extracting DID information of each diagnostic service from the diagnostic requirement document, wherein the DID information represents data involved in the corresponding diagnostic service.

[0027] Among them, the diagnostic requirements document may refer to a DPT (Diagnostics Protocol Table) Excel document. The diagnostic services extracted in this application may be the diagnostic services that are most easily changed during the development of the diagnostic code. The diagnostic services extracted in this application may include at least one of the data reading service (22&2E services), input and output control service (2F service), and routine control service (31 service). DID information can be used to identify and obtain specific parameter data. Each DID information may correspond to a specific data item of the vehicle, such as sensor data, status information, etc.

[0028] As a method, the DID (Data Identifiers) information of each diagnostic service can be extracted from the diagnostic requirement document.

[0029] S140: Fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

[0030] As a method, the DID information of each diagnostic service can be filled into the information category identifier corresponding to the template configuration file to obtain an update configuration file; an application configuration file is generated based on the update configuration file, and the application configuration file may include interface information required to execute the content in the update configuration file; based on the update configuration file and the application configuration file, a diagnostic code is generated.

[0031] Optionally, when executing step S130, not only the DID information of each diagnostic service can be extracted, but also DTC (Diagnostic Trouble Code) information, OBD information, and diagnostic service information can be extracted from the diagnostic requirement document.

[0032] Since the DTC information, OBD information, diagnostic service information and DID information of each diagnostic service are extracted from the diagnostic requirement document in step S130, Figure 2 As shown, the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to obtain an updated configuration file, including:

[0033] S141: storing the DTC information, the OBD information, the diagnostic service information and the DID information of each diagnostic service in their corresponding caches respectively, each of the caches corresponding to an information category identifier.

[0034] The diagnostic service information may include the number of extracted diagnostic services and service identifiers of the extracted diagnostic services.

[0035] In an embodiment of the present application, the buffer may include DcmDsd_Value_Temp, DcmDsp_Value_Temp, DemDtcValue_Temp, DemPidClassValue_Temp, and FiM_Value_Temp.

[0036] As a method, based on the mapping relationship between DTC information, OBD information, diagnostic service information and DID information of each diagnostic service and different caches, DTC information, OBD information, diagnostic service information and DID information of each diagnostic service can be stored in their respective corresponding caches.

[0037] Among them, the mapping relationship between DTC information, OBD information, diagnostic service information and DID information of each diagnostic service and different caches can be as follows: Figure 3 shown.

[0038] S142: Fill the content in each of the caches into the corresponding information category identifier, so as to use the filled template configuration file as the update configuration file.

[0039] The updated configuration file may be a configuration arxml file.

[0040] As a method, based on the mapping relationship between the cache and the information category identifier, the content in each cache can be filled into the corresponding information category identifier, so that the filled template configuration file is used as the update configuration file. Filling the content in each cache into the corresponding information category identifier can be understood as replacing the information category identifier with the content of the corresponding cache.

[0041] In an embodiment of the present application, by first storing the DTC information, OBD information, diagnostic service information and DID information of each diagnostic service into a cache, and then filling the contents in the cache into the corresponding information category identifier, the correctness of the contents in the cache can be checked in advance before filling; and when the template configuration file changes due to changes in the configuration tool, repeated extraction of the contents in the diagnostic requirement document can be directly avoided; and in the subsequent debugging process, the cause of the debugging error can be more conveniently located.

[0042] Optionally, after extracting DTC information, OBD information, diagnostic service information and DID information of each diagnostic service from the diagnostic requirement document in step S130, the above information can be directly filled into the corresponding information category identifier based on the mapping relationship between the above information and the identifier, so that the filled template configuration file can be used as the update configuration file.

[0043] In an embodiment of the present application, directly extracting DTC information, OBD information, diagnostic service information, and DID information of each diagnostic service and filling it into the corresponding information category identifier can speed up the generation speed of the update configuration file.

[0044] Optionally, when generating an application configuration file based on an update configuration file, you can first replace the original arxml file in the AUTOSAR project with the configuration arxml file (i.e., the update configuration file), and use the AUTOSAR tool to generate a Service arxml file that interacts with the application, and then generate an application SWC arxml file (i.e., the application configuration file) based on the Service arxml.

[0045] Optionally, an initial diagnostic code may be generated based on an update configuration file and an application configuration file; the initial diagnostic code may be debugged to obtain a diagnostic code.

[0046] Optionally, the update configuration file and the application configuration file can be imported into the AUTOSAR tool to generate initial diagnostic code.

[0047] Optionally, the initial diagnostic code may be integrated into the corresponding entire development project for compilation, debugging and verification to obtain the diagnostic code, thereby improving the reliability and accuracy of the diagnostic code.

[0048] The present embodiment provides a method for generating a diagnostic code. After obtaining the configuration information in the original configuration file, the configuration information is replaced with an information category identifier to obtain a template configuration file, and the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code. Through the above method, the configuration information in the original configuration file can be obtained, and the configuration information is replaced with an information category identifier to obtain a template configuration file; the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code, thereby realizing automatic configuration of the diagnostic code and improving development efficiency.

[0049] See also Figure 4 , an embodiment of the present application provides a method for generating a diagnostic code, the method comprising:

[0050] S210: Obtain version information of the configuration tool.

[0051] As a way, developers can input the configuration tool adapted by the AUTOSAR project and the version information of the configuration tool into the electronic device, thereby obtaining the version information of the configuration tool.

[0052] S220: Based on the version information, obtain an information extraction script.

[0053] Among them, the information extraction script may refer to a script used to extract information related to the development of diagnostic codes, such as configuration information, DID information of each diagnostic service, etc.

[0054] As a way, developers can develop different extraction scripts (which can be scripts in Python format) in advance for different configuration tools and different version information of configuration tools, and distinguish configuration tools and different versions of configuration tools through macro switches in different extraction scripts, so that after obtaining the version information of the configuration tool, they can obtain the information extraction script based on the version information.

[0055] S230: Extracting information from the original configuration file using the information extraction script to obtain the configuration information.

[0056] As a method, the original configuration file can be extracted through an information extraction script to obtain configuration information.

[0057] Optionally, the information extraction script can find the configuration information in the original configuration file according to the AUTOSAR DCM, DEM, and FiM standard configuration options.

[0058] S240: Replace the configuration information with the information category identifier to obtain a template configuration file.

[0059] As a method, the configuration information in the original configuration file can be deleted through an information extraction script, and the configuration information is replaced with an information category identifier to obtain a template configuration file.

[0060] S250: Extracting DID information of each diagnostic service from the diagnostic requirement document, where the DID information represents data involved in the corresponding diagnostic service.

[0061] As a method, DTC information, OBD information, diagnostic service information and DID information of each diagnostic service can be extracted from the diagnostic requirement document through an information extraction script, wherein the DID value, DID length, DID supported session, and DID supported security level of the DID information of 22&2E services can be extracted; the DID value, DID sub-service, DID supported session, and DID supported security level of the DID information of 2F service can be extracted; the DID value, DID sub-service, DID supported session, and DID supported security level of the DID information of 31 service can be extracted; the DTC fault code, DTC Debounce, DTC freeze frame, and Fid value of the DTC information can be extracted; the OBD code and OBD freeze frame of the OBD information can be extracted.

[0062] In this embodiment, the configuration information of different configuration tools under the AUTOSAR architecture can be directly identified, and the diagnostic requirement document can be extracted through the information extraction script, and the extracted information can be used to fill in the configuration information, thereby realizing the configuration of diagnostic content in different configuration tools.

[0063] S260: Fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

[0064] As a method, DTC information, OBD information, diagnostic service information and DID information of each diagnostic service can be filled into the information category identifier corresponding to the template configuration file to obtain an updated configuration file; an application configuration file is generated based on the updated configuration file to generate a diagnostic code based on the updated configuration file and the application configuration file.

[0065] Optionally, when generating an application configuration file based on an update configuration file, you can first replace the original arxml file in the AUTOSAR project with the configuration arxml file (i.e., the update configuration file), and use the AUTOSAR tool to generate a Service arxml file that interacts with the application, and then use the information extraction script to generate an application SWC arxml file (i.e., the application configuration file) based on the Service arxml.

[0066] In the embodiment of the present application, the method of generating an application configuration file based on updating the configuration file replaces the method of manually writing the application SWC interface according to the DPT Excel file in the prior art, thereby achieving the simultaneous completion of the diagnostic configuration and the application SWC and improving the efficiency of generating the diagnostic code.

[0067] The present embodiment provides a diagnostic code generation method, which can obtain the configuration information in the original configuration file through the above method, replace the configuration information with the information category identifier to obtain the template configuration file; extract the DID information of each diagnostic service from the diagnostic requirement document, and fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate the diagnostic code, thereby realizing automatic configuration of the diagnostic code and improving the development efficiency. In addition, in the present embodiment, by configuring different extraction scripts for different types and versions of configuration tools, the compatibility problem of different AUTOSAR tools is solved, and the flexibility and applicability of the diagnostic code generation method proposed in the present application are improved.

[0068] See also Figure 5 The present application provides a diagnostic code generating device 400, the device 400 comprising:

[0069] The template configuration file generating unit 410 is used to obtain configuration information in the original configuration file; replace the configuration information with the information category identifier to obtain the template configuration file;

[0070] An information extraction unit 420 is used to extract DID information of each diagnostic service from the diagnostic requirement document, wherein the DID information represents data involved in the corresponding diagnostic service;

[0071] The diagnosis code generating unit 430 is used to fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnosis code.

[0072] As a method, the diagnostic code generation unit 430 is specifically used to fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to obtain an updated configuration file; generate an application configuration file based on the updated configuration file, and the application configuration file includes the interface information required to execute the content in the updated configuration file; based on the update configuration file and the application configuration file, generate the diagnostic code.

[0073] Optionally, there are multiple information category identifiers, each of which corresponds to a type of configuration information; the information extraction unit 420 is specifically used to extract DTC information, OBD information, diagnostic service information and the DID information of each diagnostic service from the diagnostic requirement document; the diagnostic code generation unit 430 is specifically used to store the DTC information, the OBD information, the diagnostic service information and the DID information of each diagnostic service into their respective corresponding caches, each of which corresponds to an information category identifier; the content in each cache is filled into the corresponding information category identifier, so that the filled template configuration file is used as the update configuration file.

[0074] Optionally, the diagnostic code generating unit 430 is specifically configured to generate an initial diagnostic code based on the update configuration file and the application configuration file; and debug the initial diagnostic code to obtain the diagnostic code.

[0075] As a method, the template configuration file generating unit 410 is specifically used to obtain version information of the configuration tool; based on the version information, obtain an information extraction script; extract information from the original configuration file through the information extraction script to obtain the configuration information.

[0076] Optionally, the configuration information includes at least one of diagnostic service scheduling information, diagnostic service process information, UDS service configuration information in DEM, OBD service configuration information in DEM, and FIM configuration information.

[0077] Optionally, each diagnostic service includes at least one of a data reading service, an input / output control service, and a routine control service.

[0078] The following will be combined Figure 6 An electronic device provided by the present application is described.

[0079] See also Figure 6 Based on the above-mentioned diagnostic code generation method and device, the embodiment of the present application also provides another electronic device 100 that can execute the above-mentioned diagnostic code generation method. The electronic device 100 includes a processor 102 and a memory 104. The memory 104 stores a program that can execute the content of the above-mentioned embodiment, and the backup processor 102 can execute the program stored in the memory 104.

[0080] Among them, the processor 102 may include one or more processing cores. The processor 102 uses various interfaces and lines to connect various parts within the entire electronic device 100, and executes various functions and processes data of the electronic device 100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 104, and calling data stored in the memory 104. Optionally, the processor 102 can be implemented in at least one hardware form of a network processor (Neural network Processing Unit, NPU), a digital signal processing (Digital Signal Processing, DSP), a field programmable gate array (Field-Programmable Gate Array, FPGA), and a programmable logic array (Programmable Logic Array, PLA). The processor 102 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU), a network processor (Neural network Processing Unit, NPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing display content; the NPU is responsible for processing multimedia data such as video and images; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor 102, but may be implemented separately through a communication chip.

[0081] The memory 104 may include a random access memory (RAM), and may also include a read-only memory (RAM) and a double data rate synchronous dynamic random access memory (DDR). The memory 104 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 104 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc. The data storage area may also store data (such as a phone book, audio and video data, chat record data) created by the electronic device 100 during use.

[0082] An embodiment of the present application provides a computer-readable storage medium in which a program code is stored, and the program code can be called by a processor to execute the method described in the above method embodiment.

[0083] The computer readable storage medium may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium includes a non-transitory computer-readable storage medium. The computer readable storage medium has storage space for program codes that execute any of the method steps in the above method. These program codes can be read from or written to one or more computer program products. The program code can be compressed, for example, in an appropriate form.

[0084] In summary, the present application provides a diagnostic code generation method, device, and electronic device. After obtaining the configuration information in the original configuration file, the configuration information is replaced with an information category identifier to obtain a template configuration file, and the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code. Through the above method, the configuration information in the original configuration file can be obtained, and the configuration information is replaced with an information category identifier to obtain a template configuration file; the DID information of each diagnostic service is extracted from the diagnostic requirement document, and the DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code, thereby realizing automatic configuration of the diagnostic code and improving development efficiency.

[0085] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for generating a diagnostic code, characterized in that: The method comprises: Get the configuration information in the original configuration file; Replacing the configuration information with the information category identifier to obtain a template configuration file; Extracting DID information of each diagnostic service from the diagnostic requirement document, wherein the DID information represents data involved in the corresponding diagnostic service; The DID information of each diagnostic service is filled into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

2. The method according to claim 1, characterized in that Filling the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code includes: Fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to obtain an updated configuration file; Generate an application configuration file based on the update configuration file, wherein the application configuration file includes interface information required to execute the content in the update configuration file; The diagnostic code is generated based on the update configuration file and the application configuration file.

3. The method according to claim 2, characterized in that There are multiple information category identifiers, each of which corresponds to a type of configuration information. The DID information of each diagnostic service is extracted from the diagnostic requirement document, including: Extracting DTC information, OBD information, diagnostic service information and DID information of each diagnostic service from the diagnostic requirement document; The step of filling the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to obtain an updated configuration file includes: The DTC information, the OBD information, the diagnostic service information and the DID information of each diagnostic service are stored in corresponding caches, each of the caches corresponds to an information category identifier; The content in each of the caches is filled into the corresponding information category identifier, so that the filled template configuration file is used as the update configuration file.

4. The method according to claim 2, characterized in that: The generating the diagnostic code based on the update configuration file and the application configuration file comprises: generating an initial diagnostic code based on the update configuration file and the application configuration file; The initial diagnostic code is debugged to obtain the diagnostic code.

5. The method according to claim 1, characterized in that The obtaining of configuration information in the original configuration file includes: Get the version information of the configuration tool; Based on the version information, obtaining an information extraction script; The information extraction script is used to extract information from the original configuration file to obtain the configuration information.

6. The method according to any one of claims 1 to 5, characterized in that: The configuration information includes at least one of diagnostic service scheduling information, diagnostic service process information, UDS service configuration information in DEM, OBD service configuration information in DEM, and FIM configuration information.

7. The method according to any one of claims 1 to 5, characterized in that: The various diagnostic services include at least one of a data reading service, an input / output control service, and a routine control service.

8. A diagnostic code generating device, characterized in that: The device comprises: The template configuration file generating unit is used to obtain the configuration information in the original configuration file; replace the configuration information with the information category identifier to obtain the template configuration file; An information extraction unit, used to extract DID information of each diagnostic service from the diagnostic requirement document, wherein the DID information represents data involved in the corresponding diagnostic service; The diagnostic code generating unit is used to fill the DID information of each diagnostic service into the information category identifier corresponding to the template configuration file to generate a diagnostic code.

9. An electronic device, characterized in that: including one or more processors and memory; One or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program code, wherein when the program code is run, the method according to any one of claims 1 to 7 is executed.

Images