A quick diagnosis method for display abnormality of vehicle-mounted HUD

Abstract

This invention discloses a rapid diagnostic method for abnormal vehicle HUD displays, relating to the field of HUD fault diagnosis technology. The method includes the following steps: S100, when an abnormality is detected in the first type of information displayed on the HUD, the first type of information is recorded as information A, and the diagnostic process is initiated; S200, a first-path diagnosis is performed: comparison of information from the same source, where information from the same source refers to information used for comparison originating from the same data generation module as information A; S300, a second-path diagnosis is performed: comparison of information from different sources. This invention requires no external equipment or disassembly, shortening the diagnostic process and rapidly converging complex system-level problems to 1-2 suspicious modules, greatly saving time and material costs for subsequent precise location. It also transforms the systematic problem investigation, which relies on the experience of senior engineers, into a standardized and repeatable "dual-path comparison" diagnostic step, enabling frontline technicians to make rapid and accurate preliminary judgments.

Description

Technical Field

[0001] This invention relates to the field of HUD fault diagnosis technology, and specifically to a rapid diagnostic method for abnormal vehicle HUD display. Background Technology

[0002] A head-up display (HUD) is a head-up display system used to display information such as vehicle speed, navigation, steering, and adaptive cruise control (ACC). It mainly includes a data processing unit and an image display device. When a HUD malfunctions, it needs to be troubleshooted to identify the cause of the malfunction.

[0003] Currently, troubleshooting HUD display anomalies mainly relies on two methods:

[0004] (1) Diagnostic test based on UDS: Connect to professional diagnostic equipment to read the fault codes (DTCs) and data streams stored in the electronic control units (ECUs) such as HUD controllers and vehicle navigation hosts, and have them analyzed by engineers.

[0005] (2) Module replacement method: Replace the suspected faulty HUD hardware, vehicle host, or related wiring harness in sequence, and locate the problem by observing whether the phenomenon is reproduced.

[0006] However, there are still many problems when using the above methods for troubleshooting:

[0007] (1) Blind spot in diagnosis of “no code fault”: UDS diagnosis relies heavily on the ECU’s own identification and recording of faults. However, for performance degradation faults (such as image rendering delay and occasional jitter in data transmission), since the ECU’s preset fault threshold is not triggered, the system often does not store valid fault codes (i.e., “no code fault”), which makes it impossible for UDS to provide effective diagnostic clues.

[0008] (2) The troubleshooting process is inefficient and costly: the module replacement method is time-consuming and labor-intensive, and requires spare parts; UDS link diagnosis requires independent testing and complex correlation analysis of the sending end, receiving end and intermediate network, which is a cumbersome process.

[0009] (3) Inability to make a quick preliminary judgment on site: The above methods all rely on external equipment and professional environment (such as repair workshop). It is impossible for test engineers, quality inspectors or maintenance personnel to make a quick and reliable preliminary judgment on the scope of the fault within a few minutes at the driving site where the problem occurs, resulting in a long problem feedback cycle and a vague entry point for investigation. Summary of the Invention

[0010] The purpose of this invention is to provide a rapid diagnostic method for abnormal vehicle HUD displays, thereby solving the technical problems mentioned in the background section.

[0011] To solve the above-mentioned technical problems, the present invention specifically provides the following technical solution:

[0012] A rapid diagnostic method for abnormal vehicle HUD display, comprising the following steps:

[0013] S100: When an abnormality is detected in the first type of information displayed on the HUD, the first type of information is recorded as information A, and the diagnostic process is started.

[0014] S200, perform the first path diagnosis: same source information comparison, where same source information refers to the information used for comparison and information A originating from the same data generation module;

[0015] S300, perform second path diagnosis: heterogeneous information comparison, where heterogeneous information refers to the information used for comparison and information A originating from two independent modules or buses.

[0016] As a preferred embodiment of the present invention, in step S100, the first type of information includes one or more of navigation guidance arrows and lane lines.

[0017] As a preferred embodiment of the present invention, the specific steps for comparing source information in step S200 are as follows:

[0018] S201, On other display terminals inside the vehicle, obtain the display status of the second type of information that is the same as information A, wherein the second type of information is denoted as information A';

[0019] S202, Determine whether the display status of information A' is also abnormal;

[0020] S203, First-level diagnostic conclusion: If information A' shows an abnormality, it is determined that the fault is most likely located in the data generation module that generates information from the same source, the common upstream data source module on which the data generation module depends, or the data and data link input from the common upstream data source module to the data generation module; if information A' shows a normal result, proceed to step S300.

[0021] As a preferred embodiment of the present invention, the specific steps for heterogeneous information comparison in step S300 are as follows:

[0022] S301, within the HUD display interface, obtain the display status of a third type of information from a different source than information A, wherein the third type of information is information B;

[0023] S302, Determine whether the display status of information B on the HUD is normal;

[0024] S303, Level 2 Diagnostic Conclusion: If information B is displayed normally, it is determined that the overall rendering and display hardware functions of the HUD terminal are normal, and the fault is focused on the specific data transmission link of information A or the specific software service of the HUD that processes information A; if information B is displayed abnormally, it is determined that the fault originates from a systemic fault in the HUD terminal itself.

[0025] As a preferred embodiment of the present invention, the information B is the real-time vehicle speed or engine speed obtained directly from the vehicle CAN bus.

[0026] As a preferred embodiment of the present invention, the execution order of steps S200 and S300 can be interchanged.

[0027] As a preferred embodiment of the present invention, the display anomaly includes one or more of the following: display delay, display stuttering, missing content, positional offset, and content error.

[0028] Compared with the prior art, the present invention has the following advantages:

[0029] This invention requires no external equipment or disassembly, shortening the diagnostic process and quickly narrowing complex system-level problems down to 1-2 suspect modules. This significantly saves time and material costs for subsequent precise location. Furthermore, it transforms the systematic problem-solving process, which relies on the experience of senior engineers, into a standardized and repeatable "dual-path comparison" diagnostic procedure. This enables frontline technicians to make quick and accurate preliminary judgments, improving the team's overall problem-solving capabilities. Moreover, it can be widely applied to the rapid location of display faults in any "one source, multiple screens" or "one screen, multiple sources" scenario in smart cockpits. Attached Figure Description

[0030] To more clearly illustrate the embodiments of the present invention or the technical solutions in 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 merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.

[0031] Figure 1 This is a flowchart illustrating a rapid diagnostic method for abnormal vehicle HUD displays provided by the present invention. Detailed Implementation

[0032] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0033] The concepts involved in this application will first be described with reference to the accompanying drawings. It should be noted that the following descriptions of various concepts are only for the purpose of making the content of this application easier to understand and do not constitute a limitation on the scope of protection of this application; furthermore, the embodiments and features in the embodiments of this application can be combined with each other unless otherwise specified. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0034] like Figure 1 As shown, this invention provides a rapid diagnostic method for abnormal vehicle HUD displays, including the following steps:

[0035] S100: When an abnormality is detected in the first type of information displayed on the HUD, the first type of information is recorded as information A, and the diagnostic process is started.

[0036] S200, perform the first path diagnosis: same source information comparison, where same source information refers to the information used for comparison and information A originating from the same data generation module;

[0037] S300, perform second path diagnosis: heterogeneous information comparison, where heterogeneous information refers to the information used for comparison and information A originating from two independent modules or buses.

[0038] The core of this solution lies in "same-source-heterogeneous dual-path comparison", which quickly converges system-level faults through two information status comparisons.

[0039] In step S100, the first type of information includes one or more of the navigation guide arrows and lane lines.

[0040] The first category of information includes, but is not limited to, the above types. Information A is graphic / image information processed by the HUD or vehicle infotainment system, such as AR navigation route lines, intersection zoom-in images, adaptive cruise control (ACC) status icons, lane keeping assist (LKA) prompts, traffic sign recognition (TSR) signs, forward collision warning (FCW) prompts, blind spot monitoring (BSD) warning icons, turn signal indicators, driving mode icons, multimedia information, Bluetooth phone status prompts, low battery / fuel warnings, engine malfunction warning icons, seatbelt reminder icons, pedestrian / cyclist warning icons, traffic light recognition status, and tire pressure warnings, among other things.

[0041] In step S200, the specific steps for comparing source information are as follows:

[0042] S201, On other display terminals inside the vehicle, obtain the display status of the second type of information that is the same as information A, wherein the second type of information is denoted as information A';

[0043] S202, Determine whether the display status of information A' is also abnormal;

[0044] S203, First-level diagnostic conclusion: If information A' shows an abnormality, it is determined that the fault is most likely located in the data generation module that generates information from the same source, the common upstream data source module on which the data generation module depends, or the data and data link input from the common upstream data source module to the data generation module; if information A' shows a normal result, proceed to step S300.

[0045] Determine if the anomaly originates from the upstream public data source. If both information A and information A' are abnormal, the fault lies in the aforementioned module or data. If only the HUD is abnormal, proceed to the second path for further judgment.

[0046] In step S300, the specific steps for comparing heterogeneous information are as follows:

[0047] S301, within the HUD display interface, obtain the display status of a third type of information from a different source than information A, wherein the third type of information is information B;

[0048] S302, Determine whether the display status of information B on the HUD is normal;

[0049] S303, Level 2 Diagnostic Conclusion: If information B is displayed normally, it is determined that the overall rendering and display hardware functions of the HUD terminal are normal, and the fault is focused on the specific data transmission link of information A or the specific software service of the HUD that processes information A; if information B is displayed abnormally, it is determined that the fault originates from a systemic fault in the HUD terminal itself.

[0050] The purpose of heterogeneous comparison (step S300) is to verify whether the basic functions of the HUD terminal itself are normal. This is determined by observing the status of information B from another independent source on the HUD (such as vehicle speed directly from the CAN bus).

[0051] (1) If information B is normal, it proves that the display hardware, basic rendering, power supply and bus communication of HUD are normal. The fault should be focused on the dedicated transmission link of information A or the specific software service that processes information A inside HUD.

[0052] (2) If information B is also abnormal, it indicates that there is a systemic failure in the HUD (such as a system crash, display driver failure, etc.).

[0053] This application is particularly suitable for "code-free faults" (such as image delays and stuttering) that traditional diagnostic instruments cannot capture. Through standardized procedures, frontline personnel can quickly complete the initial location on-site without external equipment, greatly improving efficiency.

[0054] Information B is the real-time vehicle speed or engine speed obtained directly from the vehicle's CAN bus.

[0055] Information B includes, but is not limited to, the above information. Information B is numerical or status information read directly from vehicle buses such as CAN / LIN. For example, it also includes one or more of the following: current gear, total mileage, average fuel consumption, driving range, battery voltage, engine oil temperature, coolant temperature, tire pressure, system time, outside temperature, ACC activation status, lane keeping status, seat belt status, door status, and light status.

[0056] The execution order of steps S200 and S300 can be interchanged.

[0057] Display anomalies include one or more of the following: display delay, display stuttering, missing content, positional misalignment, and content errors.

[0058] Display anomalies include, but are not limited to, the above-mentioned categories, such as display flickering, display ghosting, abnormal display brightness, display color distortion, display content imbalance, display focus blur, display content jitter, display content tearing, abnormal blending of display content with background, and display content overlay disorder, as well as any combination of the above anomalies.

[0059] The fault diagnosis method described in this application can effectively shorten the diagnostic process, quickly narrowing complex system-level problems down to 1-2 suspicious modules, greatly saving time and material costs for subsequent precise location. It also transforms the systemic problem investigation that relies on the experience of senior engineers into a standardized and repeatable "dual-path comparison" diagnostic step, enabling frontline technicians to make quick and accurate preliminary judgments, improving the team's overall problem-solving capabilities. Furthermore, it can effectively diagnose faults without codes, reducing reliance on UDS diagnosis. It can be widely applied to the rapid location of display faults in any "one source, multiple screens" or "one screen, multiple sources" scenario in smart cockpits.

[0060] Experimental Example 1:

[0061] 1. Scenario: Road test engineers discovered a rendering delay of about 2 seconds on the navigation turn arrows on the HUD.

[0062] 2. Perform S200 (Same Source Information Comparison): The engineer immediately checks the map interface on the central control screen. Observation result: The navigation arrow on the central control screen also has a delay of about 2 seconds.

[0063] 3. First-level diagnostic conclusion (S23): Based on "simultaneous anomalies in information from the same source", the output conclusion is: the root cause of the problem is most likely in the common upstream, that is, insufficient performance of the vehicle navigation computing module or unstable current GPS signal. The possibility of the HUD itself being faulty is low.

[0064] Experimental Example 2:

[0065] 1. Scenario: The user reports that the HUD is not displaying navigation arrows, but the navigation function on the central control screen is normal.

[0066] 2. Execute S2: Confirm that the navigation arrows on the central control screen are displayed completely and smoothly. Conclusion: The vehicle navigation data source output is normal.

[0067] 3. Perform S3 (Heterogeneous Information Comparison): Observe the HUD and find that the real-time vehicle speed, gear position and other vehicle status information are displayed normally.

[0068] 4. Second-level diagnostic conclusion (S33): Based on "Normal heterogeneous information", the output conclusion is: The basic functions of the HUD hardware are normal. The fault should focus on the interruption of the dedicated navigation data transmission channel from the vehicle's infotainment system to the HUD, or the abnormality of the software service inside the HUD responsible for parsing navigation data.

[0069] The embodiments and / or implementation methods described above are merely preferred embodiments and / or implementation methods for implementing the technology of the present invention, and are not intended to limit the implementation methods of the technology of the present invention in any way. Any person skilled in the art can make some modifications or alterations to other equivalent embodiments without departing from the scope of the technical means disclosed in the content of the present invention, but they should still be regarded as the technology or embodiments that are substantially the same as the present invention.

[0070] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. The above descriptions are only preferred embodiments of this application. It should be noted that due to the limitations of written expression, while there are objectively infinite specific structures, those skilled in the art can make several improvements, modifications, or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner. These improvements, modifications, changes, or combinations, or the direct application of the inventive concept and technical solution to other situations without modification, should all be considered within the scope of protection of this application.

Claims

1. A rapid diagnostic method for abnormal vehicle-mounted HUD displays, characterized in that, Including the following steps: S100: When an abnormality is detected in the first type of information displayed on the HUD, the first type of information is recorded as information A, and the diagnostic process is started. S200, perform the first path diagnosis: same source information comparison, where same source information refers to the information used for comparison and information A originating from the same data generation module; S300, perform second path diagnosis: heterogeneous information comparison, where heterogeneous information refers to the information used for comparison and information A originating from two independent modules or buses.

2. The rapid diagnostic method for abnormal vehicle HUD display according to claim 1, characterized in that, In step S100, the first type of information includes one or more of the navigation guide arrows and lane lines.

3. The rapid diagnostic method for abnormal vehicle HUD display according to claim 1, characterized in that, In step S200, the specific steps for comparing source information are as follows: S201, On other display terminals inside the vehicle, obtain the display status of the second type of information that is the same as information A, wherein the second type of information is denoted as information A'; S202, Determine whether the display status of information A' is also abnormal; S203, First-level diagnostic conclusion: If information A' shows an abnormality, it is determined that the fault is most likely located in the data generation module that generates information from the same source, the common upstream data source module on which the data generation module depends, or the data and data link input from the common upstream data source module to the data generation module; if information A' shows a normal result, proceed to step S300.

4. The rapid diagnostic method for abnormal vehicle HUD display according to claim 1, characterized in that, In step S300, the specific steps for comparing heterogeneous information are as follows: S301, within the HUD display interface, obtain the display status of a third type of information from a different source than information A, wherein the third type of information is information B; S302, Determine whether the display status of information B on the HUD is normal; S303, Level 2 Diagnostic Conclusion: If information B is displayed normally, it is determined that the overall rendering and display hardware functions of the HUD terminal are normal, and the fault is focused on the specific data transmission link of information A or the specific software service of the HUD that processes information A; if information B is displayed abnormally, it is determined that the fault originates from a systemic fault in the HUD terminal itself.

5. A rapid diagnostic method for abnormal vehicle HUD display according to claim 4, characterized in that, Information B is the real-time vehicle speed or engine speed obtained directly from the vehicle's CAN bus.

6. A rapid diagnostic method for abnormal vehicle HUD display according to claim 1, characterized in that, The execution order of steps S200 and S300 can be interchanged.

7. A rapid diagnostic method for abnormal vehicle HUD display according to claim 3 or 4, characterized in that, Display anomalies include one or more of the following: display delay, display stuttering, missing content, positional misalignment, and content errors.

Images