A fault detection method, a cabin domain control system and a vehicle

Abstract

The disclosure provides a fault detection method, a cabin domain control system and a vehicle, and relates to the technical field of fault diagnosis. The method comprises the following steps: when a fault detection request for a target system is acquired, it is determined whether a calibration result of the target system is recorded in an application layer; when it is determined that the calibration result is not recorded in the application layer, it is determined whether an interface encapsulation module is currently in an initialized state; when the interface encapsulation module is currently in a non-initialized state, an integrated circuit bus channel interface encapsulated by the interface encapsulation module is initialized; and the calibration result is read through the integrated circuit bus channel interface, and a fault detection result is generated according to the calibration result. The method can avoid interface encapsulation module initialization timeout caused by occupation of other modules, thereby ensuring accurate acquisition of the calibration result and reliability of fault detection.

Description

Technical Field

[0001] This disclosure relates to the field of fault diagnosis technology, and in particular to a fault detection method, a cockpit domain control system, and a vehicle. Background Technology

[0002] The infrared night vision system on a vehicle is limited by the neural network serial architecture design used in the cockpit domain control system chip. Multiple functional modules involving artificial intelligence (AI) algorithms, such as the interface encapsulation system (also known as the interface encapsulation module), driver monitoring system (DMS), occupant monitoring system (OMS), and sentry monitoring algorithm, may compete for neural network resources during execution.

[0003] Currently, the process of obtaining calibration results for infrared night vision systems typically relies on the initialization of the interface encapsulation module. Therefore, when other modules compete for neural network resources, the initialization of the interface encapsulation module may be queued, leading to execution timeouts. This can result in situations where, although the infrared night vision system has completed calibration, it may still obtain "uncalibrated" calibration results, leading to false calibration reports. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a fault detection method, a cockpit domain control system, and a vehicle to overcome or at least partially solve the problem of false alarms in infrared calibration results. The technical solution is as follows: A fault detection method, the method comprising: When a fault detection request for the target system is received, it is determined whether the application layer has recorded the calibration results of the target system; the target system is a system that needs to rely on calibration parameters to ensure normal operation. When it is determined that the application layer has not recorded the calibration result, it is determined whether the interface encapsulation module is currently in an initialized state; the interface encapsulation module is used to encapsulate the underlying functions and provide access capabilities to the application layer through the encapsulated interface; When the interface encapsulation module is not currently in an initialized state, the integrated circuit bus channel interface encapsulated by the interface encapsulation module is initialized; the hardware storing calibration results communicates with other modules through the integrated circuit bus channel interface. The calibration results are read through the integrated circuit bus channel interface, and fault detection results are generated based on the calibration results.

[0005] In this way, when a fault detection request for the target system is received, the system first checks whether the application layer already has calibration results. This allows for direct use of existing data, avoiding repeated readings and saving hardware access time and system resources. If the application layer has not recorded valid calibration results, it checks whether the interface encapsulation module has been initialized to determine if interface preparation is necessary. If the interface encapsulation module is not yet initialized, only the bus channel interface it encapsulates for communication with the underlying hardware storing calibration results is initialized. Since initializing this channel interface does not depend on neural network resources, it avoids initialization timeout issues that may occur if other modules occupy neural network resources, ensuring data accessibility. Subsequently, the calibration results are obtained through this channel interface, and fault detection results are generated based on the obtained calibration results. This provides reliable fault determination information, ensuring the accuracy and stability of fault detection in the target system. Therefore, this method prioritizes the use of existing calibration data at the application layer, avoids repeated hardware access, and avoids interface encapsulation module initialization timeouts caused by other modules preempting data, thus ensuring accurate acquisition of calibration results and reliable fault detection.

[0006] Optionally, the calibration result includes both "not obtained" and "obtained"; when the calibration result is "obtained", the calibration result also includes the record identifier of the target system; generating the fault detection result based on the calibration result includes: If the calibration result shows that the calibration has been obtained, but the recorded identifier is inconsistent with the pre-stored identifier, or if the calibration result shows that the calibration has not been obtained, the fault detection result is determined to be an uncalibrated fault. When the calibration result shows that it has been obtained and the recorded identifier is consistent with the pre-stored identifier, the fault detection result is determined to be calibrated.

[0007] By comparing the acquisition status and identification consistency of the calibration results, the validity of the calibration results can be accurately determined: when the calibration results are not obtained or the identification is inconsistent, it can be identified as an uncalibrated fault, avoiding misjudgment caused by missing data or invalid calibration; when the calibration results have been obtained and the identification is consistent, it indicates that there is valid calibration information and it can be determined as calibrated, thereby ensuring that the fault detection results can truly reflect the calibration situation and improving the accuracy and reliability of the detection results.

[0008] Optionally, after reading the calibration result through the integrated circuit bus channel interface, the method further includes: recording the calibration result at the application layer according to a preset storage method; the preset storage method is to record the calibration result and the timestamp corresponding to the calibration result, or to overwrite the previous calibration result.

[0009] After recording the calibration results at the application layer, subsequent detection can directly call upon existing data without having to read it again via the bus. This reduces underlying communication overhead and time, improves detection efficiency, and avoids resource consumption caused by frequent initialization of interface encapsulation modules or access to hardware. Furthermore, it supports flexible control over the storage method of calibration results. When application layer storage is ample, a storage method that records the calibration results along with their corresponding timestamps can be selected, ensuring the traceability of calibration results and time. When application layer storage is limited, a storage method that overwrites the previous calibration results can be selected, avoiding redundant recording and saving storage resources.

[0010] Optionally, determining whether the application layer has recorded the calibration results of the target system includes: The calibration results are read from the application layer and verified according to preset verification rules. The verification rules include verifying at least one of the data format, recording time, and data range of the calibration results. If the test passes, it is confirmed that the application layer has recorded the calibration results of the target system; If no calibration result is read, or if the verification fails, it is determined that the application layer has not recorded the calibration result of the target system.

[0011] In this way, by reading the calibration results from the application layer and performing multi-dimensional verification (such as data format, recording time, and data range), it is possible to determine whether the calibration results of the target system have been recorded, while ensuring the validity of the data. This avoids incorrect or invalid calibration results being mistakenly judged as recorded, thereby improving the reliability and robustness of system status judgment.

[0012] Optionally, if calibration results are recorded at the application layer, fault detection results can be generated directly based on the calibration results.

[0013] When the application layer already has calibration results, fault detection results can be generated directly, avoiding repeated access to the interface encapsulation module and hardware channel. This not only shortens the detection process and improves response speed, but also reduces system resource consumption and communication risks, making the fault detection process more efficient and robust.

[0014] Optionally, when the interface encapsulation module is currently in an initialized state, the calibration result can be read directly through the integrated circuit bus channel interface, and a fault detection result can be generated based on the calibration result.

[0015] With the interface encapsulation module already initialized, the calibration results can be quickly read directly using the existing integrated circuit bus channel interface, eliminating the need for repeated initialization, reducing system overhead and latency, thereby improving the execution efficiency of fault detection and ensuring the continuity and stability of the detection process.

[0016] Optionally, obtaining a fault detection request for the target system includes: when the vehicle is powered on, initiating a fault detection request for the target system fault according to a preset time period and a preset number of retries; the preset time period is greater than the standard time period; the standard time period is the initially set time period for initiating the fault detection request.

[0017] When the vehicle is powered on, a fault detection request is initiated at a time interval longer than the standard time period, combined with a preset number of retries. This allows sufficient response time to be reserved for the target system in the early stages of system startup, further avoiding false alarms caused by timeouts due to resource preemption.

[0018] Optionally, after generating the fault detection result based on the calibration result, the method further includes: When the fault detection result is an uncalibrated fault, the diagnostic result is determined to be abnormal; When the fault detection result is calibrated, the diagnostic result is determined to be normal. Upon receiving a request to read diagnostic results, the diagnostic results are returned.

[0019] By directly linking fault detection results with diagnostic results, a clear mapping from calibration status to system health status is achieved: uncalibrated faults correspond to anomalies, and calibrated faults correspond to normal status, making the diagnostic results intuitively reflect the operating status of the target system; at the same time, diagnostic results are generated in advance and can be directly returned when an external request to read diagnostic results is initiated, realizing timely feedback of fault status, improving system response speed and manageability, and forming a complete fault monitoring and diagnosis closed loop.

[0020] A fault detection device, the device comprising: The judgment module is used to determine whether the application layer has recorded the calibration results of the target system when a fault detection request for the target system is received; the target system is a system that needs to rely on calibration parameters to ensure normal operation. When it is determined that the application layer has not recorded the calibration result, it is determined whether the interface encapsulation module is currently in an initialized state; the interface encapsulation module is used to encapsulate the underlying functions and provide access capabilities to the application layer through the encapsulated interface; An initialization module is used to initialize the integrated circuit bus channel interface encapsulated by the interface encapsulation module when the interface encapsulation module is currently in an uninitialized state; the hardware storing calibration results communicates with other modules through the integrated circuit bus channel interface; The processing module is used to read the calibration results through the integrated circuit bus channel interface and generate fault detection results based on the calibration results.

[0021] Optionally, the calibration result includes both "not obtained" and "obtained"; when the calibration result is "obtained", the calibration result also includes the record identifier of the target system; The processing module is specifically used for: If the calibration result shows that the calibration has been obtained, but the recorded identifier matches the pre-stored identifier, or if the calibration result shows that the calibration has not been obtained, the fault detection result is determined to be an uncalibrated fault. When the calibration result shows that it has been obtained, and the recorded identifier is inconsistent with the pre-stored identifier, the fault detection result is determined to be calibrated.

[0022] Optionally, the fault detection device further includes a recording module; the recording module is used for: After reading the calibration result through the integrated circuit bus channel interface, the calibration result is recorded in the application layer according to a preset storage method; the preset storage method is to record the calibration result and the timestamp corresponding to the calibration result, or to overwrite the previous calibration result.

[0023] Optionally, a judgment module is specifically used to read the calibration results from the application layer and verify the calibration results according to preset verification rules; the verification rules include verifying at least one of the data format, recording time, and data range of the calibration results; If the test passes, it is confirmed that the application layer has recorded the calibration results of the target system; If no calibration result is read, or if the verification fails, it is determined that the application layer has not recorded the calibration result of the target system.

[0024] Optionally, the processing module is also used to: generate fault detection results directly based on the calibration results when calibration results are recorded at the application layer.

[0025] Optionally, the processing module is further configured to: when the interface encapsulation module is currently in an initialized state, directly read the calibration results through the integrated circuit bus channel interface, and generate fault detection results based on the calibration results.

[0026] Optionally, the judgment module is specifically used to: when it is determined that the vehicle is powered on, initiate a fault detection request for the target system fault according to a preset time period and a preset number of retries; the preset time period is greater than the standard time period; the standard time period is the initially set time period for initiating the fault detection request.

[0027] Optionally, the processing module is also used for: After generating the fault detection result based on the calibration result, if the fault detection result is an uncalibrated fault, the diagnosis result is determined to be abnormal. When the fault detection result is calibrated, the diagnostic result is determined to be normal. Upon receiving a request to read diagnostic results, the diagnostic results are returned.

[0028] A cockpit domain control system includes a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform any of the optional fault detection methods described above.

[0029] A vehicle including the aforementioned cockpit domain control system.

[0030] A computer-readable storage medium storing a computer program that, when executed by a processor, implements any of the optional fault detection methods described above.

[0031] A computer program product, when run on a computer, causes the computer to perform the aforementioned related steps to implement any of the optional fault detection methods described above.

[0032] Using the above technical solution, this disclosure provides a fault detection method, a cockpit domain control system, and a vehicle. First, upon receiving a fault detection request for a target system, it determines whether the application layer has recorded the calibration results of the target system. If it is determined that the application layer has not recorded calibration results, it determines whether the interface encapsulation module is currently in an initialized state. Then, if the interface encapsulation module is currently in an uninitialized state, the integrated circuit bus channel interface encapsulated by the interface encapsulation module is initialized. The hardware storing the calibration results communicates with other modules through the integrated circuit bus channel interface. Finally, the calibration results are read through the integrated circuit bus channel interface, and a fault detection result is generated based on the calibration results. In this way, a layered judgment and sequential rollback mechanism can ensure both efficiency and reliability in the fault detection process: First, it checks whether the application layer already has calibration results. If so, it uses them directly, avoiding lower-level access and improving detection speed. If not, it further checks whether the interface encapsulation module has been initialized. If initialized, it can be reused directly, reducing redundant operations. If not initialized, it establishes communication by initializing the bus channel interface encapsulated by the interface encapsulation module to ensure that the calibration results stored in the hardware can be obtained. This avoids interface encapsulation module initialization timeouts caused by other modules preempting the process, ensuring accurate acquisition of calibration results and reliable fault detection. Finally, the fault detection results generated based on the calibration results can more realistically reflect the operating status of the target system, thereby improving the accuracy of detection and the stability of the system.

[0033] The above description is merely an overview of the technical solution disclosed herein. In order to better understand the technical means of this disclosure and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this disclosure more apparent and understandable, specific embodiments of this disclosure are described below. Attached Figure Description

[0034] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this disclosure. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 A flowchart of a fault detection method in a related art is shown; Figure 2 A schematic diagram of a fault detection system provided in an embodiment of this disclosure is shown; Figure 3 One of the flowcharts of the fault detection method provided in this disclosure is shown. Figure 4 A second schematic flowchart of the fault detection method provided in this embodiment of the present disclosure is shown; Figure 5 One of the timing diagrams of fault detection methods in related technologies is shown; Figure 6 The second timing diagram of a fault detection method in the related art is shown; Figure 7 One of the timing diagrams of the fault detection method provided in this disclosure is shown; Figure 8 A second timing diagram of the fault detection method provided in this embodiment of the present disclosure is shown; Figure 9 A schematic diagram of the structure of a fault detection device provided in an embodiment of this disclosure is shown; Figure 10 A schematic diagram of the structure of a cockpit domain control system provided in an embodiment of this disclosure is shown. Detailed Implementation

[0035] Exemplary embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0036] Infrared night vision systems in vehicles can enhance the driver's field of vision at night or in low-visibility environments, but their imaging accuracy is affected by factors such as camera installation deviation and optical distortion. Therefore, infrared night vision systems usually need to be calibrated before use to obtain correction parameters and ensure that the output image is consistent with the actual scene, providing a reliable foundation for subsequent image processing, fault detection, and diagnosis. However, due to the limitations of the neural network serial architecture design used in the cockpit domain control system chip, multiple functional modules involving AI algorithms, such as the interface packaging system, DMS, OMS, and sentry monitoring algorithms, may compete for neural network resources during execution. Among them, DMS and OMS refer to the algorithm system used to realize driver status monitoring and in-vehicle occupant monitoring; the sentry monitoring algorithm refers to the algorithmic identification of the vehicle's surrounding environment through vehicle radar and surround-view cameras to identify warning information.

[0037] Currently, the fault detection process of infrared night vision systems is typically implemented by the cockpit domain control system. This system can be divided into three layers based on its functional responsibilities and abstraction: the bottom layer, the middle layer, and the application layer. The bottom layer consists of hardware and system service layers. Hardware provides the hardware support for the cockpit domain control system, such as processors, memory, sensors, and buses. The system service layer refers to the basic services or operating system functions running on top of the hardware, providing various service capabilities. For example, diagnostic services provide vehicle hardware and system status monitoring, fault detection, and diagnosis. The middle layer consists of operating system middleware, communication frameworks, function libraries, and interface encapsulation modules. It encapsulates the bottom-layer capabilities and provides standard interfaces to facilitate rapid development and invocation by the application layer. For example, the Infrared Software Development Kit (SDK) provides infrared camera image acquisition, processing, and interface encapsulation functions. The application layer consists of business-oriented applications that directly provide services to users or in-vehicle functions, implementing specific functions and interaction logic. For example, infrared programs acquire images, process and display them by calling interface encapsulation modules, providing nighttime auxiliary vision for the driver.

[0038] When the cockpit domain control system executes the fault detection process of the infrared night vision system, it includes two parts: a calibration test request initiation process executed by the diagnostic service, and a calibration result acquisition process jointly executed by the infrared night vision program and the interface encapsulation module. For example... Figure 1As shown in Figure A, this is the calibration test request initiation process executed by the diagnostic service. This process includes: S01 After the vehicle is powered on, the diagnostic service initiates a calibration test request for the infrared night vision system; S02 Determines whether a calibration result has not been received within the standard time period; if yes, proceed to S03; if no, proceed to S04; S03 Determines whether the number of retries has reached the standard number; if yes, proceed to S04; otherwise, return to S02. The standard time period is the initially set time period for initiating the fault detection request (e.g., 2 seconds), and the standard number of retries is the initially set number of retries for initiating the fault detection request (e.g., 6 times). Figure 1 As shown in B, the calibration result acquisition process is jointly executed by the infrared night vision program and the interface encapsulation module. The process includes: S011 receiving a calibration detection request for the infrared night vision system; S012 initializing the interface encapsulation module; S013 acquiring the calibration result; S014 deinitializing the interface encapsulation module; and S015 returning the calibration result.

[0039] It can be seen that the current fault detection process of infrared night vision systems relies on the initialization process of the interface encapsulation module. Therefore, when other modules compete for neural network resources, the initialization of the interface encapsulation module may be queued and wait, leading to execution timeouts. This can result in the infrared night vision system receiving "uncalibrated" calibration results even after calibration, leading to false alarms. Such false alarms could potentially affect the vehicle's production line rollout at the final assembly plant.

[0040] Therefore, this disclosure provides a fault detection system, such as Figure 2 As shown, the system mainly includes an external diagnostic device 100 and a cockpit domain control system 200.

[0041] The cockpit domain control system 200 provided in this disclosure, also known as cockpit domain control, is an intelligent interactive management architecture that includes a target system. Its core is a high-performance central computer platform that coordinates and manages terminal hardware such as data acquisition devices (e.g., infrared night vision devices), display devices, audio devices, environmental control systems, and human-machine interfaces to achieve cross-device functional collaboration and data fusion. The target system is a system that requires calibration parameters to ensure normal operation, such as an infrared night vision system or a panoramic imaging system. This cockpit domain control system 200 can be applied to cockpit domain control systems 200 that require the target system for assisted perception, monitoring, or control, such as vehicle cockpit domain control, aerospace cockpit domain control, and marine cockpit domain control.

[0042] In some embodiments, the external diagnostic device 100 can establish a communication connection with the cockpit domain control system 200 to obtain diagnostic results of various hardware and software in the cockpit domain control system 200. The external diagnostic device can be any electronic device capable of initiating diagnostic result requests and displaying diagnostic results, such as a handheld diagnostic tool, a personal computer (PC), a laptop computer, a tablet computer, etc.

[0043] It should be noted that the fault detection method provided in this embodiment can be executed by the cockpit domain control system 200 described above.

[0044] Furthermore, the fault detection method provided in this disclosure can also be executed by a fault detection device, which can be hardware or software. When the fault detection device is hardware, it can be various electronic devices with fault detection functions. When the fault detection device is software, it can be installed in the aforementioned electronic devices. It can be implemented as multiple software programs or software modules, or as a single software program or software module. No specific limitations are made here.

[0045] Based on the aforementioned cockpit domain control system, in order to solve the technical problem of false alarms in calibration results, this disclosure provides a fault detection method. The following description uses a vehicle's cockpit domain control system as an example. Figure 3 As shown, Figure 3 This is a schematic flowchart of a fault detection method provided in an embodiment of the present disclosure, the method including the following steps S11-S16: S11. Obtain a fault detection request for the target system.

[0046] Specifically, the target system is a system that relies on calibration parameters to ensure normal operation, and may include at least one image acquisition device (such as a camera) for collecting environmental information. For example, infrared night vision systems can convert invisible infrared light into visible images using infrared radiation, and are widely used in fields such as automotive driver assistance, aviation navigation, and security monitoring. Panoramic imaging systems can generate panoramic images based on images of the vehicle's surroundings acquired by multiple cameras, through image stitching and distortion correction, thereby assisting drivers in fully perceiving the vehicle's surrounding environment when driving at low speeds or parking.

[0047] When installing a target system, such as an infrared night vision system, the infrared camera needs to be calibrated to ensure the system's perception accuracy. Calibration refers to the compensation calibration of infrared camera parameters, such as yaw angle, during target system installation. The process involves the interface packaging module connecting to the integrated circuit bus (Inter-Integrated Circuit, I2C).2 C) The channel interface reads the identification information from the infrared camera and performs digital compensation on the image captured by the infrared camera based on the pre-stored calibration parameters associated with this identification information. The image captured by the infrared camera is usually transmitted to the interface encapsulation module via Low-Voltage Differential Signaling (LVDS). To ensure data reliability, the interface encapsulation module checks the calibration results each time the vehicle is powered on, that is, it checks whether the pre-stored identification information is consistent with the identification information of the current infrared camera. If they are inconsistent or no calibration result is obtained, the calibration result is considered uncalibrated; otherwise, it is determined that the calibration has been completed. The interface encapsulation module is used to encapsulate the underlying functions and provide access capabilities to the application layer through the encapsulated interface. For example, the interface encapsulation module corresponding to the infrared night vision system can be an infrared SDK.

[0048] A fault detection request is a request to determine whether a calibration result indicates a fault, and it can be issued by the underlying diagnostic service of the cockpit domain controller. Therefore, a fault detection request can be obtained by the underlying diagnostic service of the cockpit domain controller initiating a fault detection request for a target system fault according to a preset time period and a preset number of retries when the vehicle is powered on. The preset time period is longer than the standard time period; the standard time period is the initially set time period for initiating the fault detection request. For example, if the standard time period is 2 seconds, the preset time period can be 6 seconds, and the preset number of retries can be 6.

[0049] In the above scheme, when the vehicle is powered on, a fault detection request is initiated at a time interval longer than the standard time period, combined with a preset number of retries. This allows sufficient response time to be reserved for the target system in the early stages of system startup, further avoiding the problem of false alarms caused by timeouts due to resource preemption.

[0050] S12. Determine whether the application layer has recorded the calibration results of the target system. If it is determined that the application layer has recorded the calibration results, proceed to step S16; if it is determined that the application layer has not recorded the calibration results, proceed to step S13.

[0051] In some embodiments, the method for determining whether the application layer has recorded the calibration results of the target system is to consider that the application layer has recorded the calibration results of the target system when the calibration results are read from the location where the calibration results are stored in the application layer; otherwise, it is considered that the application layer has not recorded the calibration results of the target system.

[0052] In some embodiments, determining whether the application layer has recorded the calibration results of the target system can be achieved by first reading the calibration results from the application layer and then verifying the calibration results according to preset verification rules. If the verification passes, it is determined that the application layer has recorded the calibration results of the target system; if no calibration results are read, or if the verification fails, it is determined that the application layer has not recorded the calibration results of the target system. The verification rules include verifying at least one of the following: data format, recording time, and data range of the calibration results.

[0053] Specifically, reading calibration results from the application layer can begin by first determining the storage location of the calibration results within the application layer. This location could be a local file directory, a lightweight database, system configuration files, registry information, or other data storage areas accessible to the application layer. Then, the calibration results are read from this storage location. It's important to note that the methods for recording and retrieving calibration results at the application layer are not limited to the examples described above. They can be flexibly chosen based on the specific system architecture, storage requirements, and the interaction between the application layer and underlying modules. For instance, calibration results can be recorded and retrieved through structured data storage, key-value mapping, caching mechanisms, or middleware service interfaces, ensuring efficient and reliable access to the calibration results.

[0054] After reading the calibration results, their validity is verified according to pre-set validation rules to ensure their reliability. Specifically, verification methods may include, but are not limited to: validating the format of the calibration results to determine if they conform to a predetermined data structure; comparing the timestamps of the calibration results to confirm their relevance; checking the numerical range of the calibration results to ensure they are within a reasonable range; and comparing the calibration results with pre-stored reference values ​​to further confirm their accuracy. If the verification passes, the calibration results can be used as the basis for subsequent fault detection; if the verification fails, a recalibration process can be triggered, or the user can be prompted to perform relevant operations. It should be noted that the above verification methods are not limited to the examples shown and can be flexibly selected according to system design requirements and application scenarios to ensure the correctness and usability of the read calibration results.

[0055] In this way, by reading the calibration results from the application layer and performing multi-dimensional verification (such as data format, recording time, and data range), it is possible to determine whether the calibration results of the target system have been recorded, while ensuring the validity of the data. This avoids incorrect or invalid calibration results being mistakenly judged as recorded, thereby improving the reliability and robustness of system status judgment.

[0056] S13. Determine whether the interface encapsulation module is currently in an initialized state. If the interface encapsulation module is currently in an initialized state, execute step S15; if the interface encapsulation module is currently in an uninitialized state, execute step S14.

[0057] Specifically, determining whether an interface encapsulation module is currently in an initialized state can include: calling the initialization state interface provided by the interface encapsulation module, or querying the initialization state flag maintained internally by the interface encapsulation module. For example, when accessing the initialization state interface of the interface encapsulation module, if the interface returns an "initialized" flag, or a true status value, it can be determined that the interface encapsulation module is currently in an initialized state; conversely, if the returned result is empty, an error code, or a false status value, it can be determined that the interface encapsulation module has not yet completed initialization. Further, in some embodiments, the initialization state can also be indirectly determined by detecting the existence of resource information (such as cache, handle, channel number, or configuration file) generated by the interface encapsulation module during the initialization phase. If the resource information is detected to be complete and can be called normally, the interface encapsulation module is considered to be initialized; if it is not detected or the call fails, it is considered not initialized. In addition, the determination method is not limited to calling the interface or querying the flag; it can also be determined by combining multiple methods such as system logs, exception return codes, or middleware feedback, and this disclosure does not limit this.

[0058] S14. Initialize the integrated circuit bus channel interface encapsulated by the interface encapsulation module.

[0059] The hardware storing the calibration results is located via an integrated circuit bus (I0). 2 C) The channel interface communicates with other modules.

[0060] Specifically, if it is determined that the application layer has not recorded the calibration results of the target system, and the interface encapsulation module is currently in an uninitialized state, it can be further determined that the calibration results need to be read from the hardware storing the calibration results. The hardware storing the calibration results uses I... 2 The C-channel interface communicates with other modules; therefore, during initialization, only the I-channel needs to be initialized. 2 The calibration results can be read simply by initializing the C-channel interface, without needing to initialize other modules that may consume significant resources. This not only saves system initialization time but also avoids the risk of initialization timeouts or blockages caused by other modules occupying neural network resources, thereby improving system startup efficiency and reliability.

[0061] S15. Read the calibration results through the integrated circuit bus channel interface.

[0062] Specifically, with the interface encapsulation module already initialized, the calibration results can be quickly read directly using the existing integrated circuit bus channel interface without needing to re-initialize the interface encapsulation module. Reusing the already initialized bus channel not only avoids the system overhead of repeated initialization but also significantly reduces the latency of obtaining calibration results, thereby improving the execution efficiency of the entire fault detection process. In some embodiments, the reading process may include sending a read command via the bus channel, receiving data returned by the hardware, and parsing and verifying the data to ensure that the obtained calibration results are complete and valid. In this way, the system can directly use the latest calibration results for judgment when performing fault detection, without waiting for or repeatedly initializing the interface encapsulation module, thus ensuring the continuity and stability of the detection process. Simultaneously, by quickly accessing the calibration results, memory resource consumption can be reduced, potential conflicts during communication and processing can be decreased, further improving the overall reliability of the system.

[0063] S16. Generate fault detection results based on the calibration results.

[0064] Specifically, based on whether data was acquired, calibration results can be categorized into two types: not acquired and acquired. When the calibration result is "acquired," it also includes the specific data acquired, which may include hardware-acquired measurements, calculated correction parameters, or other relevant information. Based on this, the method for generating fault detection results from the calibration results can include: first, determining whether the calibration result was acquired; if not, the fault detection result can be directly marked as abnormal or incomplete; if acquired, the acquired data is further verified, including determining whether the data is complete, within a reasonable range, and the authenticity or validity of the data itself. Based on the verification results, a final fault detection result can be generated. For example, if the data is valid and reliable, the fault detection result is determined to be normal or passed; if the data is invalid or abnormal, the fault detection result is determined to be abnormal or failed. In this way, the fault detection process can more accurately reflect the current state of the system, considering both the existence of calibration data and the validity of the data itself, thereby improving the reliability and robustness of fault detection. Of course, the aforementioned data verification methods, anomaly detection strategies, and fault detection result generation rules can be flexibly selected according to system requirements and application scenarios, and this disclosure does not impose any limitations on them. Furthermore, when calibration results are already available at the application layer, fault detection results can be generated directly, avoiding repeated access to the interface encapsulation module and hardware channel. This not only shortens the detection process and improves response speed but also reduces system resource consumption and communication risks, thereby making the fault detection process more efficient and robust.

[0065] In the above scheme, when a fault detection request for the target system is received, it first determines whether the application layer already has calibration results. This allows for direct use of existing data, avoiding repeated readings and saving hardware access time and system resources. If the application layer has not recorded valid calibration results, it checks whether the interface encapsulation module has been initialized to determine if interface preparation is necessary. If the interface encapsulation module is not yet initialized, only the bus channel interface encapsulated for communication with the underlying hardware storing calibration results is initialized. Since initializing this channel interface does not depend on neural network resources, it avoids initialization timeout issues that may occur due to other modules occupying neural network resources, ensuring data accessibility. Subsequently, the calibration results are obtained through this channel interface, and fault detection results are generated based on the obtained calibration results. This provides reliable fault determination information, ensuring the accuracy and stability of fault detection in the target system. Therefore, this method prioritizes the use of existing calibration data at the application layer, avoiding repeated hardware access, and avoids interface encapsulation module initialization timeouts caused by other modules preempting data, thereby ensuring accurate acquisition of calibration results and reliable fault detection.

[0066] In some embodiments, after step S16, the fault detection method further includes recording the calibration result at the application layer according to a preset storage method after reading the calibration result through the integrated circuit bus channel interface. The preset storage method may be to record the calibration result and the timestamp corresponding to the calibration result, or to overwrite the previous calibration result.

[0067] Specifically, the fault query interface of the cockpit domain control system interface encapsulation module in this embodiment can support the vehicle software to record calibration results at the application layer according to a preset storage method when the interface encapsulation module initialization is completed. For example, the vehicle software can save the calibration results to a local file, write them to a lightweight database, store them in a system configuration file or registry according to a preset storage method. Of course, other suitable storage locations can also be used, and this disclosure does not limit this. In this way, the application layer can obtain and persist the latest calibration results, providing a reliable data foundation for subsequent fault detection and image processing. At the same time, even when the interface encapsulation module has not yet been initialized, the fault query interface of the interface encapsulation module can also support the vehicle software to directly call the previously recorded calibration results, thereby avoiding the delay caused by waiting for the interface encapsulation module initialization to complete and ensuring the continuity and stability of fault detection. In some embodiments, calling the previously recorded calibration results may also include verifying the validity of the recorded data, such as determining whether the data is complete, within a reasonable range, or usable for the current detection task. Through this mechanism, regardless of whether the interface encapsulation module has been initialized, the vehicle software can efficiently and reliably obtain calibration results, achieving rapid fault detection and stable system operation.

[0068] In the above scheme, after the calibration results are recorded at the application layer, subsequent detection can directly call the existing data without reading it again through the bus, thereby reducing underlying communication overhead and time, improving detection efficiency, and avoiding resource consumption caused by frequent initialization of interface encapsulation modules or access to hardware. Furthermore, it supports flexible control over the storage method of calibration results. When application layer storage is sufficient, a storage method that records the calibration results and their corresponding timestamps can be selected, ensuring the traceability of calibration results and time. When application layer storage is limited, a storage method that overwrites the previous calibration results can be selected, avoiding redundant recording and saving storage resources.

[0069] In some embodiments, the calibration result includes both "not obtained" and "obtained," and when the calibration result is "obtained," the calibration result also includes the record identifier of the target system. Therefore, as... Figure 4 As shown, the method for generating fault detection results based on calibration results in step S16 above may include the following steps S161-S164: S161. Determine whether the calibration result shows that it has been obtained. If the calibration result shows that it has been obtained, execute step S162. If the calibration result shows that it has not been obtained, execute step S164.

[0070] S162. Determine whether the record identifier is consistent with the pre-stored identifier. If the record identifier is consistent with the pre-stored identifier, execute step S163. If the record identifier is inconsistent with the pre-stored identifier, execute step S164.

[0071] S163. Confirm that the fault detection result is calibrated.

[0072] Specifically, when the calibration result shows that it has been obtained and the recorded identifier matches the pre-stored identifier, the correct calibration result can be considered successfully obtained. At this time, the fault detection result can be returned as calibrated, indicating that the calibration result of the target system is in a normal state, without any abnormalities or missing information. In some embodiments, the recorded identifier can be a unique identifier such as the serial number (SN) or name of the infrared camera. By comparing it with the pre-stored identifier, it can be ensured that the calibration result used is the calibration result of the current infrared camera.

[0073] S164. The fault detection result is determined to be an uncalibrated fault.

[0074] Specifically, when the calibration result shows that the data has been obtained, but the recorded identifier is inconsistent with the pre-stored identifier, it can be determined that although data has been acquired, it is not the true calibration result of the target system. In other words, although the system has read some information, its content does not match the expected calibration data and therefore cannot be used as a valid calibration result. This situation is the same problem in fault detection logic as the calibration result not being obtained, both indicating that the system failed to acquire the correct target system calibration data. Based on this, the fault detection result can be determined as an uncalibrated fault, thus prompting the system or user to reacquire or re-record the calibration result.

[0075] In the above scheme, the validity of the calibration results is accurately determined by comparing the acquisition status and the consistency of the identification of the calibration results: when the calibration results are not obtained or the identification is inconsistent, it can be identified as an uncalibrated fault, avoiding misjudgment caused by missing data or invalid calibration; when the calibration results have been obtained and the identification is consistent, it indicates that there is valid calibration information and it can be determined as calibrated, thereby ensuring that the fault detection results can truly reflect the calibration situation and improve the accuracy and reliability of the detection results.

[0076] In some embodiments, after step S16, the fault detection method further includes: determining the diagnostic result as abnormal when the fault detection result is an uncalibrated fault; determining the diagnostic result as normal when the fault detection result is calibrated; and returning the diagnostic result upon receiving a request to read the diagnostic result. The request to read the diagnostic result is typically initiated externally, for example, such as... Figure 2 After the diagnostic device 100 is connected to the cockpit domain control system 200, the diagnostic device 100 sends a request to the cockpit domain control system 200 to read the diagnostic results, and the cockpit domain control system 200 returns the pre-generated diagnostic results to the diagnostic device 100.

[0077] In the above scheme, by directly linking the fault detection results with the diagnostic results, a clear mapping from the calibration state to the system health state is achieved: uncalibrated faults correspond to anomalies, and calibrated faults correspond to normal states, so that the diagnostic results can intuitively reflect the operating status of the target system; at the same time, the diagnostic results are generated in advance and can be returned directly when an external request to read the diagnostic results is initiated, so as to realize timely feedback of the fault status, improve the system response speed and manageability, and form a complete fault monitoring and diagnosis closed loop.

[0078] In some embodiments, to better illustrate the fault detection method of this disclosure, the following uses an infrared night vision system as an example to further compare and illustrate the specific implementation process of each step through a timing diagram of the cockpit domain control system when executing the relevant technical methods and the methods of the embodiments of this disclosure.

[0079] First, such as Figure 5The diagram shown illustrates the timing of a fault detection method executed when the interface encapsulation module initialization does not time out in related technologies. The timing flow includes: T01 The underlying diagnostic module confirms that the vehicle is powered on; T02 The underlying diagnostic module initiates a calibration test request for the infrared night vision system to the infrared program; T03 The infrared program initiates the initialization of the interface encapsulation module to the interface encapsulation module; T04 The interface encapsulation module performs various initializations; T05 The interface encapsulation module returns a successful initialization to the infrared program; T06 The infrared program sends a calibration test request to the interface encapsulation module; T07 The interface encapsulation module returns the calibration result to the infrared program; T08 The infrared program sends a release instruction to the interface encapsulation module; T09 The interface encapsulation module returns a successful release to the infrared program; T10 The infrared program returns the calibration result to the underlying diagnostic module.

[0080] It can be seen that the underlying diagnostic module can obtain the calibration results normally when the interface encapsulation module initialization does not time out.

[0081] like Figure 6 The diagram shown illustrates the timing of a fault detection method executed when the interface encapsulation module initialization times out in related technologies. The timing flow includes: The T01 underlying diagnostic module confirms the vehicle is powered on; the T02 underlying diagnostic module initiates a calibration test request for the infrared night vision system to the infrared program; the T03 infrared program initiates the initialization of the interface encapsulation module to the interface encapsulation module; the T041 interface encapsulation module performs initialization and times out. At this point, before the T05 timing sequence, the T10 infrared program returns the calibration result to the underlying diagnostic module. Then, following the timing sequence, the T05 interface encapsulation module returns initialization success to the infrared program; the T06 infrared program sends a calibration test request to the interface encapsulation module; the T07 interface encapsulation module returns the calibration result to the infrared program; the T08 infrared program sends a release instruction to the interface encapsulation module; and the T09 interface encapsulation module returns release success to the infrared program.

[0082] It is evident that the timing of the infrared program returning the calibration result to the underlying diagnostic module in step T10 is before the interface encapsulation module returns the calibration result to the infrared program in step T07. That is, the calibration result actually exists, but because there is no data in the returned calibration result, the uncalibrated fault code is incorrectly recorded.

[0083] Therefore, the fault detection method provided in this embodiment, upon receiving a fault detection request for an infrared night vision system, first determines whether the application layer has recorded the calibration results of the infrared night vision system; if it is determined that the application layer has not recorded the calibration results, it then determines whether the interface encapsulation module is currently in an initialized state; only when the interface encapsulation module is currently in an uninitialized state is the integrated circuit bus channel interface encapsulated by the interface encapsulation module initialized; the hardware storing the calibration results communicates with other modules through the integrated circuit bus channel interface; the calibration results are read through the integrated circuit bus channel interface, and a fault detection result is generated based on the calibration results. This solves the problem of uncalibrated fault codes caused by interface encapsulation module initialization timeout.

[0084] Specifically, such as Figure 7 The diagram shown illustrates the timing of the fault detection method in this embodiment, where the application layer has not recorded the calibration results and the interface encapsulation module is currently in an uninitialized state. The timing flow includes: The T11 low-level diagnostic module confirms the vehicle is powered on; the T12 low-level diagnostic module initiates a fault detection request for the infrared night vision system to the infrared program; the T13 infrared program initiates the initialization of the interface encapsulation module to the interface encapsulation module; the T14 interface encapsulation module initializes I... 2 C-channel interface; T15 interface package module via I 2 C-channel interface reads calibration results; T16 interface encapsulation module releases I 2 The C-channel interface; the T17 interface encapsulation module returns fault detection results to the infrared program; the T18 infrared program returns fault detection results to the underlying diagnostic module.

[0085] As can be seen, when the application layer has not recorded the calibration results and the interface encapsulation module has not yet completed initialization, only the bus channel interface encapsulated by the module for communicating with the underlying hardware storing the calibration results is initialized. Since initializing this channel interface does not depend on neural network resources, it avoids initialization timeout issues caused by other modules occupying neural network resources during system startup or operation. In this way, it ensures that the calibration results are still accessible and readable at the hardware level, thus guaranteeing that fault detection or related functions can still obtain the necessary calibration information even when the interface encapsulation module is not initialized, improving system startup efficiency and reliability.

[0086] Specifically, such as Figure 8 The diagram shown illustrates the timing of the fault detection method execution in this embodiment, where the application layer records calibration results, or the interface encapsulation module is currently in an initialized state. The timing flow includes: The T21 low-level diagnostic module confirms the vehicle is powered on; the T22 low-level diagnostic module initiates a fault detection request for the infrared night vision system to the infrared program; the T23 infrared program initiates a fault detection request to the interface encapsulation module; the T24 interface encapsulation module directly obtains the calibration results from the application layer record, or through I... 2 The C-channel interface reads the calibration results; the T25 interface encapsulation module returns the fault detection results to the infrared program; the T26 infrared program returns the fault detection results to the underlying diagnostic module.

[0087] As can be seen, when the application layer has already recorded the calibration results, fault detection results can be generated directly without calling the interface encapsulation module or accessing the underlying hardware channel again. This shortens the detection process, improves response speed, and reduces system resource consumption and communication risks, making the fault detection process more efficient and robust. Furthermore, it prevents the initialization from timing out and re-entering the initialization loop after initialization is complete. When the interface encapsulation module has already completed initialization, it can directly access the existing I... 2 The C-channel interface quickly acquires calibration results, avoiding repeated initialization, reducing system overhead and latency, thereby improving the execution efficiency of fault detection and ensuring the continuity and stability of the detection process.

[0088] In summary, the infrared calibration result processing method provided in this disclosure can achieve efficient management of target system calibration data by optimizing the interface encapsulation module initialization process and the logic design of the fault query interface. In specific applications, this method can directly utilize existing bus channels to quickly read calibration results when the interface encapsulation module has been initialized, avoiding system resource consumption and delays caused by repeated initialization; when the interface encapsulation module is not initialized or the application layer has not recorded calibration results, it can initialize only the necessary I... 2 The C-channel interface acquires calibration data from the hardware, reducing unnecessary module calls and avoiding initialization timeouts caused by multiple modules simultaneously occupying resources. Through these optimizations, the system can more efficiently and stably complete target system calibration checks and fault detection, significantly improving the continuity and reliability of fault detection. Simultaneously, this method reduces system initialization overhead and communication latency, lowers hardware resource consumption, and for vehicle production lines, can significantly increase vehicle roll-off time, improve production efficiency, and ensure the integrity and safety of vehicle functional testing before delivery.

[0089] This disclosure embodiment can divide the fault detection device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0090] In addition, such as Figure 9 As shown, Figure 9 This is a schematic diagram of the structure of a fault detection device 700 provided in an embodiment of the present disclosure. The fault detection device includes a judgment module 701, an initialization module 702, and a processing module 703.

[0091] The judgment module 701 is used to determine whether the application layer has recorded the calibration results of the target system when a fault detection request for the target system is received; the target system is a system that needs to rely on calibration parameters to ensure normal operation. When it is determined that the application layer has not recorded the calibration result, it is determined whether the interface encapsulation module is currently in an initialized state; the interface encapsulation module is used to encapsulate the underlying functions and provide access capabilities to the application layer through the encapsulated interface; The initialization module 702 is used to initialize the integrated circuit bus channel interface encapsulated by the interface encapsulation module when the interface encapsulation module is currently in an uninitialized state; the hardware storing calibration results communicates with other modules through the integrated circuit bus channel interface; The processing module 703 is used to read the calibration results through the integrated circuit bus channel interface and generate fault detection results based on the calibration results.

[0092] In the above scheme, when a fault detection request for the target system is received, it first determines whether the application layer already has calibration results. This allows for direct use of existing data, avoiding repeated readings and saving hardware access time and system resources. If the application layer has not recorded valid calibration results, it checks whether the interface encapsulation module has been initialized to determine if interface preparation is necessary. If the interface encapsulation module is not yet initialized, only the bus channel interface encapsulated for communication with the underlying hardware storing calibration results is initialized. Since initializing this channel interface does not depend on neural network resources, it avoids initialization timeout issues that may occur due to other modules occupying neural network resources, ensuring data accessibility. Subsequently, the calibration results are obtained through this channel interface, and fault detection results are generated based on the obtained calibration results. This provides reliable fault determination information, ensuring the accuracy and stability of fault detection in the target system. Therefore, this method prioritizes the use of existing calibration data at the application layer, avoiding repeated hardware access, and avoids interface encapsulation module initialization timeouts caused by other modules preempting data, thereby ensuring accurate acquisition of calibration results and reliable fault detection.

[0093] In one specific embodiment, the calibration result includes both "not obtained" and "obtained"; when the calibration result is "obtained", the calibration result also includes the record identifier of the target system; Processing module 703 is specifically used for: If the calibration result shows that the calibration has been obtained, but the recorded identifier matches the pre-stored identifier, or if the calibration result shows that the calibration has not been obtained, the fault detection result is determined to be an uncalibrated fault. When the calibration result shows that it has been obtained, and the recorded identifier is inconsistent with the pre-stored identifier, the fault detection result is determined to be calibrated.

[0094] In one specific embodiment, the fault detection device further includes a recording module; the recording module is used for: After reading the calibration result through the integrated circuit bus channel interface, the calibration result is recorded in the application layer according to a preset storage method; the preset storage method is to record the calibration result and the timestamp corresponding to the calibration result, or to overwrite the previous calibration result.

[0095] In one specific embodiment, the judgment module 701 is specifically used to read the calibration result from the application layer and verify the calibration result according to a preset verification rule; the verification rule includes verifying at least one of the data format, recording time, and data range of the calibration result; If the test passes, it is confirmed that the application layer has recorded the calibration results of the target system; If no calibration result is read, or if the verification fails, it is determined that the application layer has not recorded the calibration result of the target system.

[0096] In one specific embodiment, the processing module 703 is further configured to: when the calibration results are recorded in the application layer, directly generate fault detection results based on the calibration results.

[0097] In one specific embodiment, the processing module 703 is further configured to: when the interface encapsulation module is currently in an initialized state, directly read the calibration result through the integrated circuit bus channel interface, and generate a fault detection result based on the calibration result.

[0098] In one specific embodiment, the judgment module 701 is specifically used to: when it is determined that the vehicle is powered on, initiate a fault detection request for the target system fault according to a preset time period and a preset number of retries; the preset time period is greater than the standard time period; the standard time period is the initially set time period for initiating the fault detection request.

[0099] In one specific embodiment, the processing module 703 is further configured to: After generating the fault detection result based on the calibration result, if the fault detection result is an uncalibrated fault, the diagnosis result is determined to be abnormal. When the fault detection result is calibrated, the diagnostic result is determined to be normal. Upon receiving a request to read diagnostic results, the diagnostic results are returned.

[0100] Regarding the apparatus in the above embodiments, the specific manner in which each unit performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0101] Figure 10 This is a schematic diagram of the structure of a cockpit domain control system 800 provided in an embodiment of this disclosure. For example, as shown... Figure 10 As shown, the cockpit domain control system 800 includes a memory 801 and a processor 802. The memory 801 stores executable program code 8011, and the processor 802 is used to call and execute the executable program code 8011 to perform a fault detection method.

[0102] This embodiment can divide the vehicle system into functional modules according to the above method example. For example, each module can be assigned to a separate function module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0103] When each functional module is divided according to its corresponding function, the cockpit domain control system may include: a judgment module, an initialization module, a processing module, etc. It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0104] The cockpit domain control system provided in this embodiment is used to execute the above-mentioned fault detection method, and therefore can achieve the same effect as the above-mentioned implementation method.

[0105] When using integrated units, the cockpit domain control system may include a processing module and a storage module. The processing module is used to control and manage the vehicle's movements. The storage module supports the vehicle in executing program code and data.

[0106] The processing module may be a processor or a controller, which may implement or execute various exemplary logic blocks, modules, and circuits as described in the embodiments of this disclosure. The processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc., and the storage module may be a memory.

[0107] This disclosure also provides a vehicle including the aforementioned cockpit domain control system.

[0108] This disclosure also provides a computer-readable storage medium (including but not limited to disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) storing computer program code. When the computer program code is run on a computer, the computer executes the above-described related method steps to implement a fault detection method provided in the above embodiments.

[0109] This disclosure also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement a fault detection method provided in the above embodiments.

[0110] The beneficial effects of the above embodiments can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0111] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0112] In the embodiments provided in this disclosure, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0113] In the description of this disclosure, it should be understood that if the terms "upper", "lower", "front", "rear", "left" and "right" are used to indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the position or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this disclosure.

[0114] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0115] The above are merely embodiments of this disclosure and are not intended to limit the scope of this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure should be included within the scope of the claims of this disclosure.

Claims

1. A fault detection method, characterized in that, The method includes: When a fault detection request for the target system is received, it is determined whether the application layer has recorded the calibration results of the target system; the target system is a system that needs to rely on calibration parameters to ensure normal operation. When it is determined that the application layer has not recorded the calibration results, it is determined whether the interface encapsulation module is currently in an initialized state; the interface encapsulation module is used to encapsulate the underlying functions and provide access capabilities to the application layer through the encapsulated interface; the initialization process of the interface encapsulation module depends on neural network resources; When the interface encapsulation module is currently in an uninitialized state, the integrated circuit bus channel interface encapsulated by the interface encapsulation module is initialized; the hardware storing calibration results communicates with other modules through the integrated circuit bus channel interface; the initialization of the integrated circuit bus channel interface does not depend on the neural network resources; The calibration results are read through the integrated circuit bus channel interface, and fault detection results are generated based on the calibration results.

2. The fault detection method according to claim 1, characterized in that, The calibration results include both "not obtained" and "obtained"; when the calibration result is "obtained", the calibration result also includes the record identifier of the target system; generating fault detection results based on the calibration results includes: If the calibration result shows that the calibration has been obtained, but the recorded identifier is inconsistent with the pre-stored identifier, or if the calibration result shows that the calibration has not been obtained, the fault detection result is determined to be an uncalibrated fault. When the calibration result shows that it has been obtained and the recorded identifier is consistent with the pre-stored identifier, the fault detection result is determined to be calibrated.

3. The fault detection method according to claim 1, characterized in that, After reading the calibration results through the integrated circuit bus channel interface, the method further includes: The calibration results are recorded at the application layer according to a preset storage method; the preset storage method is to record the calibration results and the timestamps corresponding to the calibration results, or to overwrite the previous calibration results.

4. The fault detection method according to claim 2, characterized in that, The step of determining whether the application layer has recorded the calibration results of the target system includes: The calibration results are read from the application layer and verified according to preset verification rules. The verification rules include verifying at least one of the data format, recording time, and data range of the calibration results. If the test passes, it is confirmed that the application layer has recorded the calibration results of the target system; If no calibration result is read, or if the verification fails, it is determined that the application layer has not recorded the calibration result of the target system.

5. The fault detection method according to claim 1, characterized in that, When calibration results are recorded at the application layer, fault detection results are generated directly based on the calibration results.

6. The fault detection method according to claim 1, characterized in that, When the interface encapsulation module is currently in an initialized state, the calibration results are read directly through the integrated circuit bus channel interface, and fault detection results are generated based on the calibration results.

7. The fault detection method according to any one of claims 1-6, characterized in that, The acquisition of a fault detection request for the target system includes: When the vehicle is powered on, a fault detection request for the target system fault is initiated according to a preset time period and a preset number of retries; the preset time period is longer than the standard time period; the standard time period is the initially set time period for initiating the fault detection request.

8. The fault detection method according to any one of claims 1-6, characterized in that, After generating fault detection results based on the calibration results, the method further includes: When the fault detection result is an uncalibrated fault, the diagnostic result is determined to be abnormal; When the fault detection result is calibrated, the diagnostic result is determined to be normal. Upon receiving a request to read diagnostic results, the diagnostic results are returned.

9. A cockpit domain control system, characterized in that, include: A memory and a processor, wherein the memory stores executable program code, and the processor is configured to call and execute the executable program code to perform the fault detection method as described in any one of claims 1 to 8.

10. A vehicle, characterized in that, include: The cockpit domain control system as described in claim 9.

Images