Method, system and ecu for importing on-board diagnostic questionnaire into autosar tool

Abstract

This invention provides a method for importing an on-board diagnostic questionnaire into the AutoSar tool, comprising: obtaining an on-board diagnostic questionnaire in Excel format; identifying all diagnostic service parameters in the questionnaire based on preset column parameters for each diagnostic service parameter, and writing them into a pre-prepared XML file to generate an Arxml file required by the AutoSar tool; and importing the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path within the AutoSar tool. This invention also provides a system for importing an on-board diagnostic questionnaire into the AutoSar tool. Implementing this invention can solve the problems of low efficiency, high cost, and susceptibility to errors in the prior art when processing a large number of diagnostic service parameters.

Description

Technical Field

[0001] This invention relates to the fields of data processing technology and automotive technology, and in particular to a method, system, and ECU for importing an on-board diagnostic questionnaire into the AutoSar tool. Background Technology

[0002] With the rapid development of automotive electronics technology and the increasing trend towards intelligentization, the functionality and performance of on-board diagnostic (OBD) systems have been significantly improved. Modern OBD systems not only possess basic fault code reading capabilities but also monitor various vehicle operating parameters in real time and upload data to the cloud via wireless communication technology, allowing vehicle owners and repair technicians to access vehicle status information promptly. Furthermore, with the development of vehicle networking technology, OBD systems will connect with more external services, such as remote diagnostics and emergency assistance, providing users with a more convenient service experience.

[0003] However, the development and integration of on-board diagnostic systems still face some technical challenges, especially importing Excel-formatted on-board diagnostic forms into the AutoSar tool. Currently, existing on-board diagnostic forms are either manually created as AutoSarCP project containers or imported into AutoSar using the Canoe delaStudio professional tool. However, manually creating AutoSarCP project containers relies entirely on manual operation, which is inefficient and error-prone, especially when dealing with a large number of diagnostic service parameters; using the Canoe delaStudio professional tool not only requires purchasing expensive licenses, increasing development costs, but is also inefficient when handling large numbers of diagnostic service parameters.

[0004] Therefore, there is an urgent need for a new method to import vehicle diagnostic questionnaires into the AutoSar tool, which can solve the problems of inefficiency, high cost, and error susceptibility of existing technologies when processing a large number of diagnostic service parameters, greatly save human effort and resources, and improve the efficiency and economy of vehicle diagnostic system development. Summary of the Invention

[0005] The technical problem to be solved by the embodiments of the present invention is to provide a method, system and ECU for importing vehicle diagnostic questionnaires into the AutoSar tool, which can solve the problems of low efficiency, high cost and easy error in the prior art when processing a large number of diagnostic service parameters, greatly save human effort and resources, and improve the efficiency and economy of vehicle diagnostic system development.

[0006] To address the aforementioned technical problems, this invention provides a method for importing an on-board diagnostic questionnaire into the AutoSar tool, the method comprising the following steps: S1. Obtain the vehicle diagnostic questionnaire in Excel format; S2. Based on the preset column parameters of each diagnostic service parameter, traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. S3. Import the generated Arxml file into the AutoSar tool to replace the original Arxml file in the fixed path of the AutoSar tool.

[0007] Specifically, step S2 includes: The on-board diagnostic questionnaire is opened using Python's openpyxl library. Each column in all sheets of the questionnaire is then iterated through, and all diagnostic service parameters are extracted based on the predefined column parameters. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the extracted data is output as the corresponding diagnostic service parameter. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). All extracted diagnostic service parameters are written into a pre-prepared XML file to generate the Arxml file required by the AutoSar tool; wherein, the pre-prepared XML file is initially empty and its path can be found in the project directory of the AutoSar tool.

[0008] The defined column parameters for the data identifier DID include DID Number, DID SessionDefault, DID Session Extended, DID Security Unlock, DID Security Unlock L1, DID Security Unlock L9, DID Length, DID Write NvM, and DID Project Support. The routine identifier RID has defined column parameters including RID Number, RID Session Default, RID Session Extended, RID Security Unlock, RID Security Unlock L1, RID Security Unlock L9, and RID Control Type; The defined parameters for Diagnostic Trouble Codes (DTCs) include DTC Number, DTC Kind Type, DTC EnableCondition, DTC Debounce, DTC Project Support, and DTC SnapShot Type.

[0009] The method further includes: Before the Arxml file is imported into the AutoSar tool, the request length and response length of the Control Type column parameter in each routine identifier (RID) are written synchronously, as well as the relevant content corresponding to the Diagnostic Trouble Code (DTC) configured according to the individual settings; wherein, the relevant content is the content specified in the project's OEM enterprise standard.

[0010] The method further includes: The AutoSar tool imports and displays the replaced Arxml file in a GUI, allowing operators to check the changes to various service types in the AutoSar project to confirm the effectiveness of the Arxml file import operation.

[0011] This invention also provides a system for importing vehicle diagnostic questionnaires into the AutoSar tool, comprising: The vehicle diagnostic questionnaire acquisition unit is used to acquire vehicle diagnostic questionnaires in Excel format. The Arxml file generation unit is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The Arxml file import unit is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

[0012] The Arxml file generation unit includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

[0013] This invention also provides an ECU, comprising: The vehicle diagnostic questionnaire acquisition unit is used to acquire vehicle diagnostic questionnaires in Excel format. The Arxml file generation unit is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The Arxml file import unit is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

[0014] The Arxml file generation unit includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

[0015] Implementing the embodiments of the present invention has the following beneficial effects: 1. This invention uses Python to automatically generate Arxml files, which not only significantly reduces the time and effort required for manual operations, but also improves efficiency, especially when dealing with a large number of diagnostic service parameters. At the same time, the Arxml files can be directly replaced in the AutoSar CP project, simplifying the integration process and accelerating the development cycle. In addition, there is no need to purchase the expensive CanoedelaStudio License, saving development costs. It is especially suitable for development teams with limited resources. 2. This invention improves the consistency of generated files, reduces errors caused by manual operation, and ensures the accuracy and reliability of files. It is not only applicable to specific diagnostic service parameters, but also has wide applicability, can handle various types of diagnostic questionnaires, and is suitable for the development of different vehicle diagnostic systems. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, obtaining other drawings based on these drawings without creative effort still falls within the scope of the present invention.

[0017] Figure 1 A flowchart illustrating a method for importing an on-board diagnostic questionnaire into the AutoSar tool, as provided in an embodiment of the present invention; Figure 2 A schematic diagram of the structure of a system for importing vehicle diagnostic questionnaires into the AutoSar tool, provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of an ECU provided in an embodiment of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings.

[0019] like Figure 1 As shown in the figure, a method for importing an on-board diagnostic questionnaire into the AutoSar tool is provided in an embodiment of the present invention. The method includes the following steps: Step S1: Obtain the vehicle diagnostic questionnaire in Excel format; Step S2: Based on the preset column parameters of each diagnostic service parameter, traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. Step S3: Import the generated Arxml file into the AutoSar tool to replace the original Arxml file in the fixed path of the AutoSar tool.

[0020] The specific process is as follows: In step S1, an Excel-formatted vehicle diagnostic questionnaire from a specific OEM is obtained. It should be noted that because the descriptions provided by different individuals within the OEM responsible for creating and editing the diagnostic questionnaire may differ, leading to inaccurate identification, the obtained vehicle diagnostic questionnaire may require preprocessing. Specifically, this involves trimming and modifying parameters based on pre-defined column parameters in the diagnostic service parameters. Examples include the fault enable conditions, fault setting conditions, and fault recovery conditions for Diagnostic Trouble Codes (DTCs), and the length of RID routines.

[0021] In step S2, in the vehicle diagnostic survey form, given that each sheet page corresponds to a diagnostic service parameter, and each column parameter of the diagnostic service parameter occupies one column, the diagnostic service parameter corresponding to each sheet page can be extracted by traversing all columns.

[0022] First, use Python's openpyxl library to open the on-board diagnostics form and iterate through every column in all sheets of the form. Then, based on the predefined column parameters for each diagnostic service parameter, extract all diagnostic service parameters. At this point, the diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC).

[0023] The Data Identifier (DID) occupies 9 columns, with corresponding column parameters including DID Number, DID SessionDefault, DID Session Extended, DID Security Unlock, DID Security Unlock L1, DID Security Unlock L9, DID Length, DID Write NvM, and DID Project Support.

[0024] 1) DID Number: Data Identification identifier (DID identifier), in Hex format, consisting of two bytes; 2) DID Session Default: Whether this DID supports access via the default session; 3) DID Session Extended: Whether this DID supports extended session access; 4) DID Security Unlock: Whether the DID supports insecure session access. This parameter is not directly reflected in the table. The platform determines whether this parameter is generated in the Arxml file by identifying the number of security session levels directly under the DID. 5) DID Security Unlock L1: Whether this DID supports Level 1 security session access; 6) DID Security Unlock L9: Whether this DID supports security session level 9 access; 7) DID Length: The length of this DID; 8) DID Write NvM: Does this DID support NvM writing? 9) DID Project Support: Whether the project supports this DID.

[0025] The routine identifier RID occupies 7 columns, and the corresponding column parameters are RID Number, RID SessionDefault, RID Session Extended, RID Security Unlock, RID Security Unlock L1, RID Security Unlock L9 and RID Control Type.

[0026] 1) RID Number: Routine Control (RID identifier), Hex format, consisting of two bytes; 2) RID Session Default: Whether this RID supports access via the default session; 3) RID Session Extended: Whether this RID supports extended session access; 4) RID Security Unlock: Whether the RID supports insecure session access. This parameter is not directly reflected in the table. The platform determines whether this parameter is generated in the Arxml file by identifying the number of security session levels between the DIDs. 5) RID Security Unlock L1: Whether this RID supports security session level 1 access; 6) RID Security Unlock L9: Does this RID support Level 9 security session access? 7) RID Control Type: This RID control type mainly consists of Start Routine, Stop Routine, Request Routine, etc.

[0027] The Diagnostic Trouble Codes (DTCs) occupy 6 columns, with corresponding column parameters including DTC Number, DTC KindType, DTC Enable Condition, DTC Debounce, DTC Project Support, and DTC SnapShotType.

[0028] 1) DTC Number: Diagnostic Trouble Code identifier (DTC identifier), in Hex format, consisting of three bytes; 2) DTC Kind Type: DTC type, such as whether it is set by the application layer ASW or by the underlying software BSW, etc.; 3) DTC Enable Condition: DTC enable condition; 4) DTC Debounce: DTC debounce parameters. There are two DTC debounce methods: ① Time-based debounce, consisting of two parameters: fault occurrence debounce time and fault recovery debounce time; ② Count-based debounce, consisting of three parameters: count rise value, count fall value, and technical threshold value. The platform automatically selects the appropriate DTC debounce format by recognizing the parameter composition. 5) DTC Project Support: Does this project support this DTC? 6) DTC SnapShot Type: DTC freeze frame type.

[0029] It should be noted that if a column in a sheet contains merged cells, the first row of data in the merged cells will be selected as the baseline, and the data will be extracted and used as the corresponding diagnostic service parameters for output.

[0030] Finally, because different AutoSar manufacturers require different XML file formats, it's necessary to standardize the XML statement format beforehand. This XML file format path can be found directly in the AutoSar project directory, and it needs to be initially empty. That is, the pre-prepared XML file format must be initially empty, and its path must be found in the AutoSar tool's project directory. Therefore, it's necessary to prepare the XML file format in advance and write all extracted diagnostic service parameters into the pre-prepared XML file format to generate the Arxml file required by the AutoSar tool.

[0031] It should be noted that before importing the Arxml file into the AutoSar tool, the system will also identify the request length and response length of the Control Type in each RID and fill these lengths into the generated Arxml file. Furthermore, it will generate some content specified in the OEM's enterprise standards based on the project requirements. Therefore, the method further includes: the generated Arxml file will also synchronously write the request length and response length of the Control Type column parameter in each RID, and synchronously write the relevant content corresponding to the Diagnostic Trouble Code (DTC) configured according to the individual user profile; wherein, the relevant content is the content specified in the OEM's enterprise standards for the project (including manufacturer fault codes, etc.).

[0032] In step S3, the Arxml file generated in step S2 is imported into the AutoSar tool to replace the original Arxml file in a fixed path within the AutoSar tool. At this point, the AutoSar tool uses a text comparison tool to compare the two Arxml files before and after the replacement to compare the parameter changes of different XML statements. Then, the changed XML statements are filtered and merged.

[0033] In this embodiment of the invention, since the Arxml file is generated directly, there is no need to worry about configuration errors or errors in the code generated by the AutoSar tool. The C language code can be directly generated and merged into the code of the project for use.

[0034] In addition, the AutoSar tool will display the replaced Arxml file in a GUI, allowing operators to check the changes in various service types in the AutoSar project to confirm the validity of the Arxml file import operation, thus eliminating the need to perform time-consuming and laborious operations such as creating containers directly in the AutoSar tool.

[0035] like Figure 2 As shown in the illustration, a system for importing vehicle diagnostic questionnaires into the AutoSar tool is provided in an embodiment of the present invention, comprising: The vehicle diagnostic questionnaire acquisition unit 110 is used to acquire vehicle diagnostic questionnaires in Excel format. Arxml file generation unit 120 is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. Arxml file import unit 130 is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

[0036] The Arxml file generation unit 120 includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

[0037] like Figure 3 As shown in the figure, an ECU is provided in an embodiment of the present invention, comprising: The vehicle diagnostic questionnaire acquisition unit 210 is used to acquire vehicle diagnostic questionnaires in Excel format. Arxml file generation unit 220 is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. Arxml file import unit 230 is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

[0038] The Arxml file generation unit 220 includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

[0039] Implementing the embodiments of the present invention has the following beneficial effects: 1. This invention uses Python to automatically generate Arxml files, which not only significantly reduces the time and effort required for manual operations, but also improves efficiency, especially when dealing with a large number of diagnostic service parameters. At the same time, the Arxml files can be directly replaced in the AutoSar CP project, simplifying the integration process and accelerating the development cycle. In addition, there is no need to purchase the expensive CanoedelaStudio License, saving development costs. It is especially suitable for development teams with limited resources. 2. This invention improves the consistency of generated files, reduces errors caused by manual operation, and ensures the accuracy and reliability of files. It is not only applicable to specific diagnostic service parameters, but also has wide applicability, can handle various types of diagnostic questionnaires, and is suitable for the development of different vehicle diagnostic systems.

[0040] It is worth noting that the various system modules included in the above system embodiments are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional module are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0041] Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as ROM / RAM, disk, optical disk, etc.

[0042] The above description discloses only preferred embodiments of the present invention and should not be construed as limiting the scope of the present invention. Therefore, equivalent variations made in accordance with the claims of the present invention are still within the scope of the present invention.

Claims

1. A method for importing vehicle diagnostic questionnaires into the AutoSar tool, characterized in that, The method includes the following steps: S1. Obtain the vehicle diagnostic questionnaire in Excel format; S2. Based on the preset column parameters of each diagnostic service parameter, traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. S3. Import the generated Arxml file into the AutoSar tool to replace the original Arxml file in the fixed path of the AutoSar tool.

2. The method for importing the vehicle diagnostic questionnaire into the AutoSar tool as described in claim 1, characterized in that, Step S2 specifically includes: The on-board diagnostic questionnaire is opened using Python's openpyxl library. Each column in all sheets of the questionnaire is then iterated through, and all diagnostic service parameters are extracted based on the predefined column parameters. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the extracted data is output as the corresponding diagnostic service parameter. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). All extracted diagnostic service parameters are written into a pre-prepared XML file to generate the Arxml file required by the AutoSar tool; wherein, the pre-prepared XML file is initially empty and its path can be found in the project directory of the AutoSar tool.

3. The method for importing the vehicle diagnostic questionnaire into the AutoSar tool as described in claim 2, characterized in that, The defined column parameters for the Data Identifier (DID) include DID Number, DID Session Default, DID Session Extended, DID Security Unlock, DID Security Unlock L1, DID Security Unlock L9, DID Length, DID Write NvM, and DID Project Support. The routine identifier RID has defined column parameters including RID Number, RID Session Default, RID Session Extended, RID Security Unlock, RID Security Unlock L1, RID Security Unlock L9, and RID Control Type; The defined parameters for Diagnostic Trouble Codes (DTCs) include DTC Number, DTC Kind Type, DTC EnableCondition, DTC Debounce, DTC Project Support, and DTC SnapShot Type.

4. The method for importing the vehicle diagnostic questionnaire into the AutoSar tool as described in claim 3, characterized in that, The method further includes: Before the Arxml file is imported into the AutoSar tool, the request length and response length of the Control Type column parameter in each routine identifier (RID) are written synchronously, as well as the relevant content corresponding to the Diagnostic Trouble Code (DTC) configured according to the individual settings; wherein, the relevant content is the content specified in the project's OEM enterprise standard.

5. The method for importing the vehicle diagnostic questionnaire into the AutoSar tool as described in claim 1, characterized in that, The method further includes: The AutoSar tool imports and displays the replaced Arxml file in a GUI, allowing operators to check the changes to various service types in the AutoSar project to confirm the effectiveness of the Arxml file import operation.

6. A system for importing vehicle diagnostic questionnaires into the AutoSar tool, characterized in that, include: The vehicle diagnostic questionnaire acquisition unit is used to acquire vehicle diagnostic questionnaires in Excel format. The Arxml file generation unit is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The Arxml file import unit is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

7. The system for importing vehicle diagnostic questionnaires into the AutoSar tool as described in claim 6, characterized in that, The Arxml file generation unit includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

8. An ECU, characterized in that, include: The vehicle diagnostic questionnaire acquisition unit is used to acquire vehicle diagnostic questionnaires in Excel format. The Arxml file generation unit is used to traverse and identify all diagnostic service parameters in the vehicle diagnostic questionnaire according to the preset column parameters of each diagnostic service parameter, and write them into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The Arxml file import unit is used to import the generated Arxml file into the AutoSar tool to replace the original Arxml file in a fixed path in the AutoSar tool.

9. The ECU as described in claim 8, characterized in that, The Arxml file generation unit includes: The diagnostic service parameter traversal and extraction module is used to open the vehicle diagnostic survey form using Python's openpyxl library, traverse each column in all sheets of the vehicle diagnostic survey form, and further extract all diagnostic service parameters according to the predefined column parameters of each diagnostic service parameter. If a column in a sheet contains merged cells, the first row of data in the merged cells is selected as the baseline, and the data is extracted as the corresponding diagnostic service parameter output. The diagnostic service parameters include Data Identifier (DID), Routine Identifier (RID), and Diagnostic Trouble Code (DTC). The module for writing diagnostic service parameters and generating Arxml files is used to write all extracted diagnostic service parameters into a pre-prepared XML file format to generate the Arxml file required by the AutoSar tool. The pre-prepared XML file format is initially empty, and its path can be found in the project directory of the AutoSar tool.

Images