Vehicle diagnosis data processing method, electronic equipment and storage medium

Abstract

The invention provides a vehicle diagnosis data processing method, electronic equipment and a storage medium, and the method comprises the steps: responding to a vehicle diagnosis topological graph generation request, and extracting a plurality of ECUs corresponding to a vehicle identifier from an ECU database according to the vehicle identifier indicated by the vehicle diagnosis topological graph generation request; determining a plurality of target ECUs participating in diagnosis in the plurality of ECUs; and in the drawing tool interface, automatically drawing a whole vehicle diagnosis topological graph formed by the multiple target ECUs. The method is used for automatically generating diagnosis related information, reducing manpower, improving the working efficiency of vehicle diagnosis design and reducing the error rate.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method for processing vehicle diagnostic data, an electronic device, and a storage medium. Background Art

[0002] Currently, when facing modified models and newly developed models, Visio drawing software is used to modify the original diagnostic topology and generate a new vehicle diagnostic topology. This step requires the diagnostic designer to manually identify the corresponding vehicle network topology and collect relevant information for each ECU. This information includes but is not limited to: the communication method of each ECU, whether independent diagnosis is performed, whether there is a private CAN, etc. After the vehicle diagnostic topology is released, it is necessary to manually edit the diagnostic routing ID table in Excel and assign a diagnostic ID to each ECU in the topology. It takes a lot of time and manpower, and has a high error rate. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a vehicle diagnostic data processing method, electronic device and storage medium, so as to automatically generate diagnosis-related information, reduce manpower, improve the work efficiency of vehicle diagnostic design, and reduce the error rate.

[0004] In a first aspect, the present invention provides a method for processing vehicle diagnostic data, the method comprising:

[0005] In response to a request for generating a vehicle diagnostic topology map, multiple ECUs corresponding to the vehicle identification indicated by the request for generating the vehicle diagnostic topology map are extracted from an ECU database; among the multiple ECUs, multiple target ECUs participating in the diagnosis are determined; and in a drawing tool interface, a vehicle diagnostic topology map consisting of the multiple target ECUs is automatically drawn.

[0006] In an optional implementation manner, in a drawing tool interface, the step of automatically drawing a vehicle diagnostic topology map composed of multiple target ECUs specifically includes:

[0007] Draw an editing control corresponding to each target ECU in the drawing tool interface; for each target ECU, obtain the communication link information of the target ECU through the ECU database to draw a connection line between the target ECUs in the drawing tool interface.

[0008] In an optional embodiment, it also includes responding to a first touch operation on a target editing control to update the position of the target editing control displayed in the drawing tool interface; and responding to a second touch operation on a target connecting line to update the position of the target connecting line displayed in the drawing tool interface.

[0009] In an optional implementation, the drawing tool interface includes a save control, and the method further includes responding to a third touch operation on the save control to save the drawing result in the current drawing tool interface in a file in a first preset format.

[0010] In an optional embodiment, the method further includes responding to a request to generate a vehicle diagnostic routing ID table, generating a vehicle identification indicated by the request according to a vehicle diagnostic topology map, and extracting multiple ECUs corresponding to the vehicle identification from an ECU database; among the multiple ECUs, determining multiple target ECUs participating in the diagnosis; and generating a vehicle diagnostic routing ID table based on the diagnostic IDs corresponding to all target ECUs and saving it in a file of a second preset format.

[0011] In an optional implementation, based on the diagnostic IDs corresponding to all target ECUs, the step of generating a vehicle diagnostic routing ID table in a second preset format specifically includes:

[0012] The name and diagnostic ID of each target ECU are sequentially written into a target worksheet of a newly created Excel workbook; the column width of the target worksheet is automatically adjusted; and the Excel workbook is written into a file of a second preset format.

[0013] In an optional embodiment, the method further includes sending a vehicle diagnostic topology map file in a first preset format and a vehicle diagnostic routing ID table file in a second preset format to a terminal device belonging to the target employee, and displaying the vehicle diagnostic topology map and the vehicle diagnostic routing ID table through the terminal device for the target employee to review.

[0014] In an optional implementation, it also includes adding an approved mark and saving the vehicle diagnostic topology map or vehicle diagnostic routing ID table that has been approved by the target employee.

[0015] In a second aspect, the present invention provides an electronic device comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of a method for processing vehicle diagnostic data as described in any of the aforementioned embodiments.

[0016] In a third aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the method for processing vehicle diagnostic data in any of the aforementioned embodiments are executed.

[0017] The present application provides a method for processing vehicle diagnostic data, an electronic device and a storage medium, wherein the method includes responding to a request for generating a vehicle diagnostic topology map, extracting multiple ECUs corresponding to the vehicle identification in an ECU database according to the vehicle identification indicated by the request for generating a vehicle diagnostic topology map; determining multiple target ECUs involved in the diagnosis among multiple ECUs; and automatically drawing a vehicle diagnostic topology map composed of multiple target ECUs in a drawing tool interface. This is used to automatically generate diagnostic related information, reduce manpower, improve the work efficiency of vehicle diagnostic design, and reduce the error rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 A flowchart of a method for processing vehicle diagnostic data provided by an embodiment of the present application;

[0020] Figure 2 A flowchart of another method for processing vehicle diagnostic data provided by an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of a vehicle diagnostic data processing device provided in an embodiment of the present application;

[0022] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0023] First, the application scenarios of the present application are described. The technical solution of the present application can be applied to the automatic production of chart files when ECU designers are performing vehicle diagnosis design.

[0024] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0025] Figure 1A flowchart of a method for processing vehicle diagnostic data provided in an embodiment of the present application. In one embodiment of the present application, an application or system is provided to assist ECU designers. The ECU (Engine Control Unit) here refers to an electronic module in a vehicle that is used to control and manage various systems of the vehicle. In addition to the Engine Control Unit (ECU), a car also contains many other types of electronic ECUs, each of which is responsible for monitoring and controlling a specific system or function of the vehicle.

[0026] like Figure 1 As shown, the present application provides a method for processing vehicle diagnostic data, comprising:

[0027] S11. Responding to a request for generating a vehicle diagnostic topology map, extracting a plurality of ECUs corresponding to the vehicle identification from an ECU database according to the vehicle identification indicated by the request for generating a vehicle diagnostic topology map.

[0028] S12. Determine, among the plurality of ECUs, a plurality of target ECUs involved in diagnosis.

[0029] S13. In the drawing tool interface, a vehicle diagnostic topology diagram consisting of multiple target ECUs is automatically drawn.

[0030] Here, taking the application as an example, a user graphical interface can be provided to allow designers to enter data in order to collect ECU-related information for different vehicle models and store it in the ECU database.

[0031] Specifically, designers can configure corresponding work platforms, establish designer tasks for corresponding projects, assign them to designers, and designers need to complete information filling tasks. Relevant information includes at least ① ECU name (needs to be consistent with FBOM) ② ECU communication method ③ Whether ECU participates in diagnosis (divided into independent diagnosis and upper node diagnosis) ④ Communication CAN to which ECU belongs (if it is CAN communication) ⑤ Whether ECU has private CAN ⑥ What type of routing can ECU complete. The information filling form of ②-⑥ is a drop-down selection box. The collected ECU information can be summarized in the work interface of the vehicle diagnosis designer.

[0032] The ECU database can also store other organized empirical data, such as the diagnostic ID corresponding to each ECU and the communication method between ECUs. The diagnostic routing ID is usually related to the identification and communication routing of the ECU. In a complex vehicle network, in order to effectively manage and diagnose multiple network nodes (such as sensors, actuators, etc.), each node or specific diagnostic function needs to be assigned a unique ID. This ID is used to identify, address and route diagnostic requests and responses during the diagnostic process.

[0033] Furthermore, the experience information in the ECU database will be used as a reference for information collection, and a pop-up window will be displayed when the information entered by the designer is different from the experience data in the database. Here, equalsIgnoreCase() in Java can be used to implement string matching verification.

[0034] The application can also provide a user graphical interface and a file generation control, and when the control is clicked, a request for generating a vehicle diagnostic topology map is generated. The request for generating a vehicle diagnostic topology map here can be generated based on data input by a designer in real time, or can be a vehicle identifier indicating a vehicle model, or a vehicle ID identifier, etc.

[0035] In step S12, based on the object indicated by the vehicle diagnostic topology map generation request, ECU search and matching are performed to determine multiple target ECUs.

[0036] In step S13, the editing control corresponding to each target ECU is drawn in the drawing tool interface. For each target ECU, the communication link information of the target ECU is obtained through the ECU database to draw the connection line between the target ECUs in the drawing tool interface.

[0037] Here, the whole vehicle diagnostic topology map can be drawn through drawing software. The ECU database contains a small module for each ECU. This small module can be equivalent to a rectangular control in the drawing software. This rectangular control can be dragged and connected, and is one of the basic elements of the topology map.

[0038] In the drawing software, the ECUs that "participate in diagnosis" in the target ECU will be displayed, and the ECUs that have not been entered and selected as "participate in diagnosis" will not appear in the drawing software, thus avoiding the appearance of redundant / missing ECUs in the vehicle diagnosis topology. Each ECU module will be automatically deployed on the corresponding communication link (different communication CAN roads or LIN / Doip communication links) according to the information pre-configured by the ECU designer.

[0039] Furthermore, the application may respond to a first touch operation on the target edit control to update the position of the target edit control displayed in the drawing tool interface, and respond to a second touch operation on the target connection line to update the position of the target connection line displayed in the drawing tool interface.

[0040] Diagnostic designers can manipulate connections in the drawing software to adjust and improve the vehicle diagnostic topology diagram.

[0041] The drawing tool interface includes a save control, and can respond to a third touch operation on the save control to save the drawing result in the current drawing tool interface in a file in a first preset format.

[0042] The completed vehicle diagnostic topology diagram can be converted into a .vsdx format file and saved in the system as a deliverable.

[0043] Figure 2 A flowchart of another method for processing vehicle diagnostic data provided by an embodiment of the present application. In one embodiment of the present application, in addition to the vehicle diagnostic topology map, a vehicle diagnostic routing ID table can also be automatically sorted and generated.

[0044] Specifically, Figure 2 As shown, the method may include:

[0045] S21, responding to a request for generating a vehicle diagnostic routing ID table, extracting a plurality of ECUs corresponding to the vehicle ID from an ECU database according to a vehicle ID indicated by the request for generating a vehicle diagnostic topology map;

[0046] S22, determining a plurality of target ECUs involved in diagnosis from among the plurality of ECUs;

[0047] S23: Based on the diagnostic IDs corresponding to all target ECUs, generate a vehicle diagnostic routing ID table and save it in a file of a second preset format.

[0048] Taking the application as an example, a user graphical interface can be provided for the ECU designer to select the ECU object, and then the user can click the file to generate a control, and after clicking the control, a request for generating a vehicle diagnostic routing ID table is generated. The request for generating a vehicle diagnostic routing ID table can include a vehicle ID, an ECU ID, and the like.

[0049] In step S22, it is necessary to determine all ECUs involved in the diagnosis.

[0050] In step S23, based on the diagnostic IDs corresponding to all target ECUs, the step of generating a vehicle diagnostic routing ID table in a second preset format specifically includes:

[0051] Write the name and diagnostic ID of each target ECU into the target worksheet of the newly created Excel workbook in turn. Automatically adjust the column width of the target worksheet; write the Excel workbook into a file in the second preset format.

[0052] In a specific embodiment, the Apache POI library (Java) can be used to create an Excel workbook and traverse the ECUs included in each communication link, call the fixed diagnostic ID of each target ECU, write the data into the rows and columns of the worksheet, and the diagnostic designer can export the vehicle diagnostic routing ID table in Excel table format with one click. Further, a new Excel workbook can be created, a worksheet can be created in it, the data list of the target ECU can be obtained, all the data can be traversed and written into the worksheet, the column width can be adjusted, and the Excel workbook can be written into a file.

[0053] This method of automatically matching and generating tables through a program greatly improves work efficiency and accuracy compared to manual identification and one-to-one matching in Excel tables.

[0054] In one embodiment of the present application, the vehicle diagnostic topology diagram in vsdx format and the diagnostic routing ID table in Excel format are used as two deliverables. The designer can select relevant departments or personnel related to the audit content on the designer's workbench, and negotiate, confirm and sign the file content through the network platform without face-to-face contact. This can improve efficiency, and all signature records and audit opinions can be queried and counted online.

[0055] Specifically, the vehicle diagnostic topology map file in the first preset format and the vehicle diagnostic routing ID table file in the second preset format can be sent to the terminal device of the target employee, and the vehicle diagnostic topology map and the vehicle diagnostic routing ID table can be displayed through the terminal device so that the target employee can review them. It also includes adding a review pass mark and saving the vehicle diagnostic topology map or vehicle diagnostic routing ID table that has been reviewed and approved by the target employee.

[0056] The approved vehicle diagnostic topology map or vehicle diagnostic routing ID table can be sent to the next node for production.

[0057] In one embodiment of the present application, the vehicle diagnostic topology map or the vehicle diagnostic routing ID table can also be modified and updated. When the vehicle diagnostic topology map and the diagnostic routing ID table need to be updated and adjusted, the ECU designer can re-edit the information he has filled in, and the diagnostic designer can also directly use the drawing program to open the historical version of the vehicle diagnostic topology map saved in the platform, save the new version after updating, and coexist with the historical version in the system. After the vehicle diagnostic topology map is updated, the new version of the vehicle diagnostic routing ID table can be exported. When the change only involves the vehicle diagnostic routing ID table, the Apache POI library can be used to read the Excel file uploaded by the user and parse the data therein. After importing the historical version of the Excel table into the system and modifying it on the system, re-export the new version of the table.

[0058] Figure 3 A schematic diagram of the structure of a vehicle diagnostic data processing device provided in an embodiment of the present application. Figure 3 As shown, based on the same inventive concept, an embodiment of the present application further provides a vehicle diagnostic data processing device 30, the device comprising:

[0059] The first response module 300 is used to respond to the request for generating the vehicle diagnostic topology map, and extract multiple ECUs corresponding to the vehicle identifier from the ECU database according to the vehicle identifier indicated by the request for generating the vehicle diagnostic topology map;

[0060] A first screening module 310 is used to determine a plurality of target ECUs involved in diagnosis from among a plurality of ECUs;

[0061] The first generating module 320 is used to automatically draw a vehicle diagnostic topology diagram consisting of multiple target ECUs in a drawing tool interface.

[0062] In a preferred embodiment, the first generation module 320 is specifically used to draw an editing control corresponding to each target ECU in the drawing tool interface; for each target ECU, the communication link information of the target ECU is obtained through the ECU database to draw a connection line between the target ECUs in the drawing tool interface.

[0063] In a preferred embodiment, the first response module 300 is also used to respond to a first touch operation on a target editing control to update the position of the target editing control displayed in the drawing tool interface; and to respond to a second touch operation on a target connecting line to update the position of the target connecting line displayed in the drawing tool interface.

[0064] In a preferred embodiment, the drawing tool interface includes a save control, and the first response module 300 is further used to respond to a third touch operation on the save control to save the drawing result in the current drawing tool interface in a file in a first preset format.

[0065] In a preferred embodiment, it further includes a second response module 330, which is used to respond to the vehicle diagnostic routing ID table generation request, extract multiple ECUs corresponding to the vehicle identification in the ECU database according to the vehicle identification indicated by the vehicle diagnostic topology map generation request;

[0066] A second screening module 340 is used to determine a plurality of target ECUs involved in diagnosis from among the plurality of ECUs;

[0067] The second generating module 350 is used to generate a vehicle diagnostic routing ID table based on the diagnostic IDs corresponding to all target ECUs and save it in a file of a second preset format.

[0068] In a preferred embodiment, the second generation module 350 is specifically used to write the name and diagnostic ID of each target ECU into the target worksheet of the newly created Excel workbook in turn; automatically adjust the column width of the target worksheet; and write the Excel workbook into a file in a second preset format.

[0069] In a preferred embodiment, it also includes an audit module 360, which is used to send the vehicle diagnostic topology map file in a first preset format and the vehicle diagnostic routing ID table file in a second preset format to the terminal device belonging to the target employee, and display the vehicle diagnostic topology map and the vehicle diagnostic routing ID table through the terminal device so that the target employee can review them.

[0070] In a preferred embodiment, the review module 360 ​​is also used to add a review pass mark and save the vehicle diagnostic topology map or vehicle diagnostic routing ID table that has been reviewed and approved by the target employee.

[0071] See also Figure 4 , Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown in , the electronic device 400 includes a processor 410 , a memory 420 and a bus 430 .

[0072] The memory 420 stores machine-readable instructions executable by the processor 410. When the electronic device 400 is running, the processor 410 communicates with the memory 420 via the bus 430. When the machine-readable instructions are executed by the processor 410, the steps of a vehicle diagnostic data processing method in the above-mentioned method embodiment can be executed. The specific implementation method can be found in the method embodiment, which will not be repeated here.

[0073] An embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of a method for processing vehicle diagnostic data in the above method embodiment can be executed. The specific implementation method can be found in the method embodiment, which will not be repeated here.

[0074] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0075] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0076] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0077] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0078] It should be noted that if the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM) random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0079] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0080] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for processing vehicle diagnostic data, characterized in that: The method comprises: In response to a request for generating a vehicle diagnostic topology map, extracting a plurality of ECUs corresponding to the vehicle identifier from an ECU database according to the vehicle identifier indicated by the request for generating a vehicle diagnostic topology map; Among the plurality of ECUs, determining a plurality of target ECUs involved in diagnosis; In the drawing tool interface, the vehicle diagnostic topology diagram consisting of multiple target ECUs is automatically drawn.

2. The method according to claim 1, characterized in that The step of automatically drawing a vehicle diagnostic topology map composed of multiple target ECUs in the drawing tool interface specifically includes: Draw an editing control corresponding to each target ECU in the drawing tool interface; For each target ECU, the communication link information of the target ECU is obtained through the ECU database to draw the connection lines between the target ECUs in the drawing tool interface.

3. The method according to claim 1, characterized in that Also includes: In response to a first touch operation on a target edit control, a position of the target edit control displayed in the drawing tool interface is updated; as well as In response to a second touch operation on the target connecting line, a position of the target connecting line displayed in the drawing tool interface is updated.

4. The method according to claim 1, characterized in that The drawing tool interface includes a save control, and the method further includes: In response to a third touch operation on the save control, the drawing result in the current drawing tool interface is saved in a file in a first preset format.

5. The method according to claim 1, characterized in that Also includes: In response to a request for generating a vehicle diagnostic routing ID table, extracting a plurality of ECUs corresponding to the vehicle identification in an ECU database according to the vehicle identification indicated by the request for generating a vehicle diagnostic topology map; Among the plurality of ECUs, determining a plurality of target ECUs involved in diagnosis; Based on the diagnostic IDs corresponding to all target ECUs, a vehicle diagnostic routing ID table is generated and saved in a file of a second preset format.

6. The method according to claim 5, characterized in that The step of generating a vehicle diagnostic routing ID table in a second preset format based on the diagnostic IDs corresponding to all target ECUs specifically includes: Write the name and diagnostic ID of each target ECU into the target worksheet of the newly created Excel workbook in turn; Automatically adjust the column width of the target worksheet; Write the Excel workbook to a file in a second preset format.

7. The method according to claim 1 or 5, characterized in that: Also includes: The vehicle diagnostic topology map file in the first preset format and the vehicle diagnostic routing ID table file in the second preset format are sent to the terminal device belonging to the target employee, and the vehicle diagnostic topology map and the vehicle diagnostic routing ID table are displayed through the terminal device so that the target employee can review them.

8. The method according to claim 7, characterized in that Also includes: For the vehicle diagnostic topology map or vehicle diagnostic routing ID table that has been approved by the target employee, add an approved mark and save it.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of the vehicle diagnostic data processing method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for processing vehicle diagnostic data as claimed in any one of claims 1 to 8 are executed.

Images