Diagnostic methods and equipment

Abstract

This application provides a diagnostic method and apparatus, relating to the field of diagnostic technology. The method includes: if the predicted in-use monitoring frequency of a first diagnostic item among all diagnostic items of a vehicle's engine controller is lower than a preset frequency, receiving diagnostic request information for the first diagnostic item sent by the engine controller, and then determining whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item; if the vehicle meets the diagnostic conditions of a second diagnostic item in the first diagnostic item, sending a handshake confirmation signal to the engine controller and entering an engine operating condition control mode; the engine operating condition control mode is used to control the engine operating condition of the vehicle to match the required operating condition of a third diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters a diagnostic state and executes the third diagnostic item within the current driving cycle. The diagnostic method and apparatus provided in this application can improve the in-use monitoring frequency of engine diagnostic items.

Description

Technical Field

[0001] This application relates to the field of diagnostic technology, and in particular to a diagnostic method and device. Background Technology

[0002] With increasingly stringent vehicle emission regulations, especially the implementation of the China VI and Euro VI emission standards, higher requirements have been placed on the diagnostic coverage of on-board diagnostic (OBD) systems. The diagnostic completion rate, or in-use performance ratio (IUPR), has become a key indicator subject to mandatory regulatory monitoring. Meanwhile, hybrid vehicles continue to gain market share due to their combined advantages in energy saving and range.

[0003] In hybrid electric vehicles, engine operating condition selection is typically dominated by the Vehicle Control Unit (VCU), whose core objectives are to optimize fuel economy, reduce emissions, and maintain energy balance. To achieve these goals, the VCU's selection strategy tends to keep the engine operating in its most efficient range, usually at medium to high loads, or to directly shut down the engine when the battery is fully charged, deliberately avoiding low-to-medium load and low-efficiency operating conditions. However, some critical diagnostics performed by the engine control unit's (ECU) on-board diagnostic system, such as evaporative emission desorption diagnostics, fuel system leak diagnostics, and post-oxygen sensor diagnostics, require low-to-medium load and steady-state conditions. This conflict in operating condition selection leads to a persistently low frequency of these diagnostics being monitored, potentially resulting in non-compliance with regulatory requirements. Summary of the Invention

[0004] This application provides a diagnostic method and device to address the deficiency of low in-use monitoring frequency of engine diagnostic items in the prior art, and to improve the in-use monitoring frequency of engine diagnostic items.

[0005] Firstly, this application provides a diagnostic method applied to a vehicle controller, comprising: If the cloud determines that the predicted monitoring frequency of the first diagnostic item in all diagnostic items of the vehicle's engine controller is lower than the preset frequency, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

[0006] Optionally, entering the engine operating condition control mode includes: The engine speed and load are controlled to match the required operating conditions of the third diagnostic item; wherein the third diagnostic item is the highest priority diagnostic item among the second diagnostic items, and the diagnostic priority is determined based on the diagnostic urgency and safety impact of each diagnostic item among all diagnostic items.

[0007] Optionally, the diagnostic method also includes: If the vehicle meets any of the following first preset conditions, the engine operating condition control mode will be exited. The plurality of first preset conditions include: Receive the diagnostic completion information for the third diagnostic item sent by the engine controller; Received diagnostic failure information for the third diagnostic item sent by the engine controller; The system receives information from the engine controller that the duration of a single diagnostic test for the third diagnostic item exceeds a preset upper limit. The system receives information from the engine controller that the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds a preset limit. The vehicle's accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value is detected to exceed a preset upper limit. The engine controller receives information indicating that the engine is in an abnormal operating state.

[0008] Optionally, the cloud is used for: Acquire target data; wherein, the target data includes historical diagnostic data of all diagnostic items, historical driving data of the vehicle, and future planned route data of the vehicle's user; Based on the target data, diagnostic predictions are performed to obtain the predicted number of times all diagnostic items will be completed in future driving cycles. Based on the number of prediction completions, the prediction monitoring frequency for all diagnostic items is determined.

[0009] Optionally, the diagnostic request information includes at least one of the following: the identifier of the first diagnostic item, the required operating conditions, diagnostic priority information, estimated diagnostic time, number of repeated diagnostic requests, and diagnostic conditions; the diagnostic conditions include at least one of the following: vehicle speed conditions, temperature conditions, altitude conditions, and driver intention conditions.

[0010] Secondly, this application provides a diagnostic method applied to the engine controller of a vehicle, comprising: If the cloud determines that the predicted monitoring frequency of the first diagnostic item among all diagnostic items of the engine controller is lower than a preset frequency, it sends a diagnostic request message for the first diagnostic item to the vehicle controller. Upon receiving the diagnostic request message, the vehicle controller determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it sends a handshake confirmation signal to the engine controller and enters the engine operating condition control mode. This engine operating condition control mode is used to match the operating condition of the vehicle's engine with the required operating condition of the third diagnostic item. The third diagnostic item is one of the second diagnostic items. The handshake confirmation signal is received, and then the diagnostic state is entered, and the third diagnostic item is executed within the current driving cycle.

[0011] Optionally, the diagnostic method also includes: If the vehicle meets any of the following multiple second preset conditions, causing the vehicle controller to exit the engine operating condition control mode, then when the vehicle no longer meets any of the following multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the diagnostic request information of the third diagnostic item will be resent to the vehicle controller. The plurality of second preset conditions include: The duration of a single diagnosis for the third diagnostic item was detected to exceed a preset upper limit; The third diagnostic item was detected to have exceeded a preset limit in terms of cumulative activation duration or cumulative activation count within the current driving cycle. The vehicle controller receives information that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value of the vehicle exceeds a preset upper limit. An abnormal operating condition of the engine was detected.

[0012] Optionally, the diagnostic method also includes: If the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds the preset limit, no other diagnostic request information will be sent in the current driving cycle. If the diagnostic request information for the first diagnostic item has already been sent within a preset interval, no other diagnostic request information will be sent. If the number of times the engine operating status is abnormal within the current driving cycle exceeds a set threshold, no further diagnostic request information will be sent within the current driving cycle.

[0013] Optionally, the diagnostic method also includes: When the vehicle controller exits the engine operating condition control mode, it adjusts the engine's ignition angle or air-fuel ratio.

[0014] Thirdly, this application provides a diagnostic device applied to a vehicle's overall controller, comprising: The judgment module is used to receive the diagnosis request information of the first diagnosis item sent by the engine controller if the cloud determines that the predicted in-use monitoring frequency of the first diagnosis item is lower than the preset frequency among all the diagnosis items of the engine controller of the vehicle, and then determine whether the vehicle meets the diagnosis conditions of each diagnosis item in the first diagnosis item. The control module is configured to send a handshake confirmation signal to the engine controller and enter the engine operating condition control mode if the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; the engine controller enters the diagnostic state after receiving the handshake confirmation signal and executes the third diagnostic item in the current driving cycle.

[0015] Fourthly, this application provides a diagnostic device applied to the engine controller of a vehicle, comprising: The transmission module is used to send a diagnostic request message for the first diagnostic item to the vehicle controller if the cloud determines that the predicted monitoring frequency of the first diagnostic item is lower than a preset frequency among all diagnostic items of the engine controller. Upon receiving the diagnostic request message, the vehicle controller determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, the vehicle controller sends a handshake confirmation signal to the engine controller and enters an engine operating condition control mode. This engine operating condition control mode is used to match the operating condition of the vehicle's engine with the required operating condition of a third diagnostic item, where the third diagnostic item is one of the second diagnostic items. A diagnostic module is configured to receive the handshake confirmation signal, then enter a diagnostic state, and execute the third diagnostic item within the current driving cycle. Thirdly, this application also provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method described in the first aspect.

[0016] Fifthly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in the first or second aspect.

[0017] In a sixth aspect, this application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first or second aspect.

[0018] In a seventh aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first or second aspect.

[0019] The diagnostic method and equipment provided in this application, when the predicted in-use monitoring frequency of diagnostic items in the vehicle's engine controller is lower than the preset frequency, send diagnostic request information through the engine controller. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic items, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic items to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic items, increasing the in-use monitoring frequency of the diagnostic items, and ensuring vehicle safety. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is one of the flowcharts illustrating the diagnostic method provided in the embodiments of this application; Figure 2 This is a schematic diagram of the diagnostic system architecture provided in an embodiment of this application; Figure 3 This is a second schematic flowchart of the diagnostic method provided in the embodiments of this application; Figure 4 This is the third flowchart illustrating the diagnostic method provided in the embodiments of this application; Figure 5 This is one of the structural schematic diagrams of the diagnostic device provided in the embodiments of this application; Figure 6 This is a second schematic diagram of the structure of the diagnostic device provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0022] This application's analysis reveals that existing engine OBD diagnostics typically employ a passive waiting approach, either by setting a fixed diagnostic window or by selectively cutting off fuel supply. These methods fail to dynamically adjust to actual user scenarios and cannot effectively balance diagnostic needs with vehicle performance dimensions. For example, inappropriate fuel cut-off timing during post-oxygen diagnostics can lead to significant deterioration in emissions, noise, vibration, and harshness (NVH), resulting in regulatory violations and potential user complaints. Therefore, a new diagnostic method is needed that can consider the overall vehicle performance requirements of OBD diagnostics and achieve more intelligent operating condition scheduling.

[0023] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] Figure 1 This is one of the flowcharts illustrating the diagnostic method provided in the embodiments of this application. (Refer to...) Figure 1 This application provides a diagnostic method applied to a vehicle controller. The method may include: Step 110: If the cloud determines that the predicted monitoring frequency of the first diagnostic item is lower than the preset frequency among all diagnostic items of the vehicle's engine controller, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. Step 120: If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the engine operating condition of the vehicle to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

[0025] Figure 2 This is a schematic diagram of the diagnostic system architecture provided in an embodiment of this application. Figure 2 As shown, the vehicle's overall controller is responsible for vehicle energy management, torque coordination, diagnostic mode switching control, coordinating the operation of key components such as the battery, motor, and engine, deciding the vehicle's operating mode, and ensuring overall vehicle performance control. The vehicle's engine controller is responsible for OBD diagnostic execution, engine operating status monitoring, data acquisition, computational processing, and strategy decision-making. The OBD diagnostic system is a real-time monitoring system integrated into either the engine controller or the vehicle controller. The vehicle controller can communicate bidirectionally with the vehicle's engine controller and cloud controllers distributed in the onboard telematics box (T-box) via a Controller Area Network (CAN) bus. The T-box is an intelligent connected terminal device integrated within the vehicle. Interaction signals between the vehicle controller and the engine controller can include diagnostic condition requests, handshake confirmations, diagnostic status feedback, and interrupt commands.

[0026] In step 110, when the cloud determines that the predicted in-use detection frequency of the first diagnostic item among all diagnostic items of the vehicle's engine controller is lower than a preset frequency (which can be the IUPR rate required by regulations), it can prompt the activation of the vehicle's intelligent point selection mode to create a suitable diagnostic environment for executing the diagnostic items, thereby executing each diagnostic item. The IUPR rate is an indicator used to quantify the frequency with which the on-board diagnostic (OBD) system performs monitoring tasks on emission-related components during actual use.

[0027] After the intelligent point selection mode is activated, the engine controller can send the diagnostic request information of the first diagnostic item to the vehicle controller. After receiving the diagnostic request information of the first diagnostic item, the vehicle controller can determine whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item.

[0028] In step 120, when the vehicle controller determines that the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it can send a handshake confirmation signal to the engine controller and switch to the "diagnostic coordination mode," that is, enter the engine operating condition control mode. When the vehicle enters the engine operating condition control mode, the vehicle controller temporarily weakens the fuel economy and power optimization goals, and uses a speed and torque variation control strategy to control the engine speed and load within the hysteresis range of the target values, and controls the engine operating conditions of the vehicle to match the required operating conditions of the third diagnostic item, avoiding diagnostic interruption due to slight fluctuations in operating conditions. The third diagnostic item is one of the diagnostic items in the second diagnostic item.

[0029] After receiving the handshake confirmation signal sent by the vehicle controller, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle. It also provides real-time feedback on the diagnostic status to the vehicle controller, such as diagnostic in progress, diagnostic completion, diagnostic failure, and diagnostic timeout.

[0030] Figure 3 This is the second flowchart of the diagnostic method provided in the embodiments of this application, which can be referred to in correspondence with the above steps.

[0031] The diagnostic method provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of the diagnostic item in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic item, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic item, increasing the in-use monitoring frequency of the diagnostic item, and ensuring vehicle safety.

[0032] In some embodiments, entering the engine operating condition control mode includes: controlling the engine speed and load to match the required operating conditions of the third diagnostic item; wherein the third diagnostic item is the diagnostic item with the highest diagnostic priority among the second diagnostic items, and the diagnostic priority is determined based on the diagnostic urgency and safety impact of each diagnostic item among all diagnostic items.

[0033] The vehicle controller can enter the engine operating condition control mode by matching the engine speed and load with the required operating conditions of the third diagnostic item. For example, this application can pre-calibrate the target speed, target load, and hysteresis range between the target speed and target load for the third diagnostic item, and control the engine speed within the hysteresis range of the target speed and the engine load within the hysteresis range of the target load, thereby creating a suitable diagnostic environment for executing the third diagnostic item.

[0034] The third diagnostic item is the highest priority diagnostic item among the second diagnostic items. That is, if five diagnostic items (i.e., the number of first diagnostic items is five) have a predicted usage frequency lower than a preset frequency, and the vehicle meets the diagnostic conditions of four out of the five diagnostic items (i.e., the number of second diagnostic items is four), then the highest priority diagnostic item among these four is the third diagnostic item. The vehicle controller maintains a queue of second diagnostic items and only responds to the highest priority diagnostic condition request in the queue at a time; after a high-priority diagnosis is completed or fails, the next priority request is processed sequentially.

[0035] Specifically, the vehicle controller can determine the priority of each diagnostic item based on its urgency and impact on vehicle safety, and pre-establish a diagnostic priority queue. An example priority list from highest to lowest is: First priority, fuel system leak diagnosis (directly related to safety); Second priority, evaporative emission desorption diagnosis (affecting evaporative emission regulations); Third priority, rear oxygen sensor diagnosis (affecting emission control accuracy); Fourth priority, other routine diagnostic items.

[0036] The diagnostic method provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of diagnostic items in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic items, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item with the highest diagnostic priority. When multiple diagnostic items need to be activated at the same time, a priority scheduling mechanism is adopted to avoid operating condition conflicts, actively creating suitable engine operating conditions for the execution of the diagnostic item with the highest diagnostic priority, increasing the in-use monitoring frequency of diagnostic items, and ensuring vehicle safety.

[0037] In some embodiments, the diagnostic method further includes: exiting the engine operating condition control mode if the vehicle meets any one of the following plurality of first preset conditions; wherein the plurality of first preset conditions include: receiving diagnostic completion information of a third diagnostic item sent by the engine controller; receiving diagnostic failure information of a third diagnostic item sent by the engine controller; receiving information that the single diagnostic duration of a third diagnostic item sent by the engine controller exceeds a preset upper limit; receiving information that the cumulative activation duration or cumulative activation count of a third diagnostic item in the current driving cycle sent by the engine controller exceeds a preset upper limit; detecting that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value of the vehicle exceeds a preset upper limit; and receiving information that the engine operating state is abnormal sent by the engine controller.

[0038] When the vehicle meets any of a number of first preset conditions, the vehicle controller exits the diagnostic coordination mode, i.e., exits the engine operating condition control mode, switches back to the normal control mode, and sends an exit confirmation signal to the engine controller. The various first preset conditions include: the engine controller detecting that the third diagnostic item has been completed; the engine controller detecting that the third diagnostic item has failed; the engine controller detecting that the duration of a single diagnosis of the third diagnostic item exceeds a preset limit; the engine controller detecting that the cumulative activation time or cumulative activation count within the current driving cycle exceeds a preset limit; the vehicle controller detecting that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value exceeds a preset limit (i.e., driver intention to take over); and the engine controller detecting an abnormal engine operating state. Among these, the conditions other than the engine controller detecting that the third diagnostic item has been completed or failed constitute various second preset conditions. The second preset conditions include: the engine controller detects that the duration of a single diagnosis of the third diagnostic item exceeds the preset limit; the engine controller detects that the cumulative activation time or cumulative activation count in the current driving cycle exceeds the preset limit; the vehicle controller detects that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value exceeds the preset limit; and the engine controller detects that the engine operating status is abnormal.

[0039] When in collaborative diagnostic mode, considering the vehicle's requirements for rapid power response during overtaking and rapid torque decay during braking, coupled with the risk of permanent engine damage from abnormal operation, it is necessary to perform safety monitoring on important parameters of the vehicle controller and engine controller. After evaluation, the collaborative diagnostic mode will be exited and the normal control mode will be restored.

[0040] Driver Intent Takeover: The vehicle controller monitors the accelerator pedal change rate, brake pedal change rate, and longitudinal acceleration signal value in real time through the safety monitoring module. When the accelerator pedal change rate or the longitudinal acceleration signal value exceeds a set threshold, it indicates an intention to accelerate rapidly; when the brake pedal change rate or the longitudinal acceleration signal value exceeds a set threshold, it indicates an intention to decelerate rapidly. Once an intention to accelerate or decelerate rapidly is determined, the vehicle controller immediately and unconditionally exits the diagnostic coordination mode, switches back to the normal control mode, and sends an interrupt signal to the engine controller, providing the interruption reason and status. Upon receiving the interrupt signal, the engine controller immediately terminates the current OBD diagnostics and enters a retreat state to ensure that the driver's control priority is not affected.

[0041] Abnormal engine operation: During diagnostic maintenance, the engine controller monitors engine operation stability parameters in real time through the safety monitoring module. Speed ​​fluctuation: When the speed fluctuation exceeds a set threshold (e.g., ±100 rpm, calibrable) and persists for more than a set time (e.g., 0.5 seconds, calibrable), the engine is deemed unstable. Misfire count: When the number of misfires in the diagnostic window exceeds a set threshold (e.g., more than 50 times, calibrable), a misfire risk is identified.

[0042] When any of the above anomalies is detected, the engine controller proactively sends an anomaly interrupt request to the vehicle controller, indicating the cause and status of the anomaly. Upon receiving this request, the vehicle controller immediately exits the diagnostic coordination mode, switches back to the normal control mode, and sends an interrupt confirmation signal to the engine controller. The engine controller records the anomaly event.

[0043] If the vehicle controller exits the engine operating condition control mode due to the normal completion or failure of the third diagnostic item, the engine controller records the diagnostic results and updates the IUPR count. If the vehicle controller exits the engine operating condition control mode due to any of the multiple second preset conditions, the engine controller enters a retreat state. When the vehicle no longer meets any of the multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the engine controller resends the diagnostic request information for the third diagnostic item to the vehicle controller to continue executing the third diagnostic item.

[0044] Specifically, to avoid significant negative impacts on vehicle emissions, fuel consumption, and NVH (noise, vibration, and harshness) indicators during diagnostic procedures, this application establishes a multi-layered resource constraint mechanism: Maximum duration of a single diagnosis: After each entry into the intelligent point selection mode, the cumulative time maintained in the diagnostic state shall not exceed the preset threshold range (e.g., 20 seconds, which can be calibrated). If the timeout is exceeded, the system will be forced to exit. Current driving cycle quota: Within each driving cycle (from power-on to power-off), the cumulative activation time of the intelligent point selection mode does not exceed the preset threshold range (e.g., 3 minutes, which can be calibrated), or the cumulative activation times do not exceed the preset threshold range (e.g., 5 times, which can be calibrated).

[0045] The diagnostic method provided in this application embodiment exits the engine operating condition control mode when the vehicle meets any of the multiple first preset conditions. This can avoid the diagnostic behavior from causing significant negative impacts on the vehicle's emissions, fuel consumption, NVH and other dimensions, and achieve an effective balance between diagnostic needs and vehicle performance dimensions.

[0046] In some embodiments, the cloud is used to: acquire target data; wherein the target data includes historical diagnostic data of all diagnostic items, historical driving data of the vehicle, and future planned route data of the vehicle's users; perform diagnostic prediction based on the target data to obtain the prediction completion number of all diagnostic items in future driving cycles; and determine the prediction in-use monitoring frequency of all diagnostic items based on the prediction completion number.

[0047] The cloud can acquire target data, which includes historical diagnostic data for all diagnostic items, historical driving data of the vehicle, and future route planning data for the vehicle's users. Historical diagnostic data includes, for example, the operating condition window (speed / load range) corresponding to each diagnostic item, the required diagnostic time, the IUPR target value required by regulations, and the historical diagnostic completion status; historical driving data includes, for example, the vehicle speed distribution and engine operating condition distribution over several past driving cycles; future route planning data includes, for example, information such as road type, congestion conditions, and gradient in the current and future planned routes.

[0048] Based on the above information, the cloud uses the prediction module to calculate the predicted number of times all diagnostic items will be completed in the future driving cycle, and then obtains the predicted IUPR rate = (historical number of completed items + predicted number of completed items) / total number of required items according to regulations. The vehicle's intelligent point selection mode can only be activated when the estimated IUPR rate of any diagnostic item is lower than the preset frequency (e.g., 0.8 times the regulatory limit, which can be calibrated with reference to regulatory requirements).

[0049] The diagnostic method provided in this application determines whether to activate the vehicle's intelligent point selection mode by judging whether the predicted in-use monitoring frequency of the first diagnostic item is lower than the preset frequency among all diagnostic items of the vehicle's engine controller. This proactively creates engine operating conditions that are suitable for the execution of diagnostic items and increases the in-use monitoring frequency of diagnostic items.

[0050] In some embodiments, the diagnostic request information includes at least one of the following: the identifier of the first diagnostic item, the required operating conditions, diagnostic priority information, estimated diagnostic duration, number of repeated diagnostic requests, and diagnostic conditions; the diagnostic conditions include at least one of the following: vehicle speed conditions, temperature conditions, altitude conditions, and driver intention conditions.

[0051] After the intelligent point selection mode is activated, the engine controller sends diagnostic request information to the vehicle controller, which may include the following: diagnostic identifier, identifying the specific diagnostic item (such as desorption diagnosis, air leakage diagnosis, after-oxygen diagnosis, etc.); required operating conditions, the requested target speed, target load, and hysteresis range of the target speed and target load; diagnostic priority information, pre-calibrated according to the urgency of the diagnostic item and its impact on vehicle safety; estimated diagnostic time, the estimated time required to complete the diagnostic item; number of repeated diagnostic requests, the maximum number of diagnostic attempts allowed before the current power-on cycle diagnostic failure is reported; and diagnostic conditions.

[0052] This application configures independent access conditions for each diagnostic item, including vehicle speed thresholds, ambient temperature thresholds, and altitude thresholds. Before responding to a diagnostic request, the vehicle controller verifies whether the current operating conditions meet the access conditions for that diagnostic item, avoiding performing diagnostics under unsuitable conditions. Specifically, after receiving the diagnostic request information for the first diagnostic item from the engine controller, the vehicle controller enters the arbitration phase to assess the current vehicle's safety boundary conditions, i.e., to assess whether the vehicle meets the diagnostic conditions for the first diagnostic item. Diagnostic conditions can include: vehicle speed conditions, whether the vehicle is in a stable driving state, avoiding diagnostics at low speeds, during start-up, or while stationary; a preset threshold range (e.g., 10km / h to 40km / h, calibrable); temperature conditions, whether the ambient temperature is within the required diagnostic range; a preset threshold range (e.g., -7℃ to 35℃, calibrable according to regulations); and coolant temperature, whether it is within the required warm-up range; a preset threshold range (e.g., above 70℃, calibrable); altitude conditions, whether the vehicle is within the suitable altitude range for diagnostics; a preset threshold range (e.g., below 2440m, calibrable according to regulations); and driver intent conditions, determined by the accelerator and brake pedal openings and longitudinal acceleration signals to determine if there is an intention to accelerate or decelerate rapidly. When all safety boundary conditions are met, the vehicle controller sends a handshake confirmation signal to the engine controller, entering the diagnostic coordination mode; if any condition is not met, a rejection signal is sent, and the engine controller enters a waiting or retreating state.

[0053] The diagnostic method provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of the diagnostic item in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic item, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic item, increasing the in-use monitoring frequency of the diagnostic item, and ensuring vehicle safety.

[0054] Figure 4 This is the third flowchart illustrating the diagnostic method provided in the embodiments of this application. (Refer to...) Figure 4 This application provides a diagnostic method applied to the engine controller of a vehicle, which may include: Step 410: If the cloud determines that the predicted monitoring frequency of the first diagnostic item is lower than the preset frequency among all diagnostic items of the engine controller, it sends a diagnostic request message for the first diagnostic item to the vehicle controller. Upon receiving the diagnostic request message, the vehicle controller determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it sends a handshake confirmation signal to the engine controller and enters the engine operating condition control mode. The engine operating condition control mode is used to match the operating conditions of the vehicle's engine with the required operating conditions of the third diagnostic item. The third diagnostic item is one of the diagnostic items in the second diagnostic item. Step 420: Receive handshake confirmation signal, then enter diagnostic state, and perform the third diagnostic item within the current driving cycle.

[0055] like Figure 2 As shown, the vehicle's overall controller is responsible for vehicle energy management, torque coordination, diagnostic mode switching control, coordinating the operation of key components such as the battery, motor, and engine, deciding the vehicle's operating mode, and ensuring overall vehicle performance control. The vehicle's engine controller is responsible for OBD diagnostic execution, engine operating status monitoring, data acquisition, computational processing, and strategy decision-making. The OBD diagnostic system is a real-time monitoring system integrated into either the engine controller or the vehicle controller. The vehicle controller can communicate bidirectionally with the vehicle's engine controller and cloud controllers distributed in the onboard telematics box (T-box) via a Controller Area Network (CAN) bus. The T-box is an intelligent connected terminal device integrated within the vehicle. Interaction signals between the vehicle controller and the engine controller can include diagnostic condition requests, handshake confirmations, diagnostic status feedback, and interrupt commands.

[0056] In step 410, when the cloud determines that the predicted in-use detection frequency of the first diagnostic item among all diagnostic items of the vehicle's engine controller is lower than a preset frequency (which can be the IUPR rate required by regulations), it can prompt the activation of the vehicle's intelligent point selection mode to create a suitable diagnostic environment for executing the diagnostic items, thereby executing each diagnostic item. The IUPR rate is an indicator used to quantify the frequency with which the on-board diagnostic (OBD) system performs monitoring tasks on emission-related components during actual use.

[0057] After the intelligent point selection mode is activated, the engine controller can send the diagnostic request information of the first diagnostic item to the vehicle controller. After receiving the diagnostic request information of the first diagnostic item, the vehicle controller can determine whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item.

[0058] When the vehicle controller determines that the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it can send a handshake confirmation signal to the engine controller and switch to "diagnostic coordination mode," i.e., enter the engine operating condition control mode. When the vehicle enters the engine operating condition control mode, the vehicle controller temporarily weakens the fuel economy and power optimization goals, and uses a speed and torque variation control strategy to control the engine speed and load within the hysteresis range of the target values, thus matching the engine operating conditions of the vehicle with the operating conditions required by the third diagnostic item, avoiding diagnostic interruptions due to slight fluctuations in operating conditions. The third diagnostic item is one of the diagnostic items in the second diagnostic item.

[0059] In step 420, after receiving the handshake confirmation signal sent by the vehicle controller, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle, and provides real-time feedback on the diagnostic status to the vehicle controller, such as diagnostic in progress, diagnostic completed, diagnostic failed, and diagnostic timeout.

[0060] Figure 3 The steps can be referred to in the same way as those above.

[0061] The diagnostic method provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of the diagnostic item in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic item, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic item, increasing the in-use monitoring frequency of the diagnostic item, and ensuring vehicle safety.

[0062] In some embodiments, the diagnostic method further includes: if the vehicle meets any one of the following multiple second preset conditions, causing the vehicle controller to exit the engine operating condition control mode, then when the vehicle no longer meets any one of the following multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the diagnostic request information for the third diagnostic item is resent to the vehicle controller; wherein the multiple second preset conditions include: detecting that the single diagnostic duration of the third diagnostic item exceeds a preset upper limit; detecting that the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds a preset upper limit; receiving information from the vehicle controller that the vehicle's accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value exceeds a preset upper limit; and detecting an abnormal engine operating state.

[0063] When the vehicle meets any of a number of first preset conditions, the vehicle controller exits the diagnostic coordination mode, i.e., exits the engine operating condition control mode, switches back to the normal control mode, and sends an exit confirmation signal to the engine controller. The various first preset conditions include: the engine controller detecting that the third diagnostic item has been completed; the engine controller detecting that the third diagnostic item has failed; the engine controller detecting that the duration of a single diagnosis of the third diagnostic item exceeds a preset limit; the engine controller detecting that the cumulative activation time or cumulative activation count within the current driving cycle exceeds a preset limit; the vehicle controller detecting that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value exceeds a preset limit (i.e., driver intention to take over); and the engine controller detecting an abnormal engine operating state. Among these, the conditions other than the engine controller detecting that the third diagnostic item has been completed or failed constitute various second preset conditions. The second preset conditions include: the engine controller detects that the duration of a single diagnosis of the third diagnostic item exceeds the preset limit; the engine controller detects that the cumulative activation time or cumulative activation count in the current driving cycle exceeds the preset limit; the vehicle controller detects that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value exceeds the preset limit; and the engine controller detects that the engine operating status is abnormal.

[0064] When in collaborative diagnostic mode, considering the vehicle's requirements for rapid power response during overtaking and rapid torque decay during braking, coupled with the risk of permanent engine damage from abnormal operation, it is necessary to perform safety monitoring on important parameters of the vehicle controller and engine controller. After evaluation, the collaborative diagnostic mode will be exited and the normal control mode will be restored.

[0065] Driver Intent Takeover: The vehicle controller monitors the accelerator pedal change rate, brake pedal change rate, and longitudinal acceleration signal value in real time through the safety monitoring module. When the accelerator pedal change rate or the longitudinal acceleration signal value exceeds a set threshold, it indicates an intention to accelerate rapidly; when the brake pedal change rate or the longitudinal acceleration signal value exceeds a set threshold, it indicates an intention to decelerate rapidly. Once an intention to accelerate or decelerate rapidly is determined, the vehicle controller immediately and unconditionally exits the diagnostic coordination mode, switches back to the normal control mode, and sends an interrupt signal to the engine controller, providing the interruption reason and status. Upon receiving the interrupt signal, the engine controller immediately terminates the current OBD diagnostics and enters a retreat state to ensure that the driver's control priority is not affected.

[0066] Abnormal engine operation: During diagnostic maintenance, the engine controller monitors engine operation stability parameters in real time through the safety monitoring module. Speed ​​fluctuation: When the speed fluctuation exceeds a set threshold (e.g., ±100 rpm, calibrable) and persists for more than a set time (e.g., 0.5 seconds, calibrable), the engine is deemed unstable. Misfire count: When the number of misfires in the diagnostic window exceeds a set threshold (e.g., more than 50 times, calibrable), a misfire risk is identified.

[0067] When any of the above anomalies is detected, the engine controller proactively sends an anomaly interrupt request to the vehicle controller, indicating the cause and status of the anomaly. Upon receiving this request, the vehicle controller immediately exits the diagnostic coordination mode, switches back to the normal control mode, and sends an interrupt confirmation signal to the engine controller. The engine controller records the anomaly event.

[0068] If the vehicle controller exits the engine operating condition control mode due to the normal completion or failure of the third diagnostic item, the engine controller records the diagnostic results and updates the IUPR count. If the vehicle controller exits the engine operating condition control mode due to any of the multiple second preset conditions, the engine controller enters a retreat state. When the vehicle no longer meets any of the multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the engine controller resends the diagnostic request information for the third diagnostic item to the vehicle controller to continue executing the third diagnostic item.

[0069] Specifically, to avoid significant negative impacts on vehicle emissions, fuel consumption, and NVH (noise, vibration, and harshness) indicators during diagnostic procedures, this application establishes a multi-layered resource constraint mechanism: Maximum duration of a single diagnosis: After each entry into the intelligent point selection mode, the cumulative time maintained in the diagnostic state shall not exceed the preset threshold range (e.g., 20 seconds, which can be calibrated). If the timeout is exceeded, the system will be forced to exit. Current driving cycle quota: Within each driving cycle (from power-on to power-off), the cumulative activation time of the intelligent point selection mode does not exceed the preset threshold range (e.g., 3 minutes, which can be calibrated), or the cumulative activation times do not exceed the preset threshold range (e.g., 5 times, which can be calibrated).

[0070] The diagnostic method provided in this application embodiment exits the engine operating condition control mode when the vehicle meets any of the multiple first preset conditions. This can avoid the diagnostic behavior from causing significant negative impacts on the vehicle's emissions, fuel consumption, NVH and other dimensions, and achieve an effective balance between diagnostic needs and vehicle performance dimensions.

[0071] In some embodiments, the diagnostic method further includes: if the cumulative activation time or cumulative activation count of the third diagnostic item in the current driving cycle exceeds a preset upper limit, no other diagnostic request information will be sent in the current driving cycle; if the diagnostic request information of the first diagnostic item has been sent within a preset interval, no other diagnostic request information will be sent; if the number of times the engine operating status is abnormal in the current driving cycle exceeds a set threshold, no other diagnostic request information will be sent in the current driving cycle.

[0072] The diagnostic method provided in this application, by setting restrictions on the engine controller sending diagnostic request information, can prevent the impact on vehicle performance caused by multiple responses to diagnostic request information in cases of abnormal execution of diagnostic items, excessively short intervals, and abnormal engine operation. It avoids vehicle instability caused by frequent switching of engine operating conditions and can achieve an effective balance between diagnostic needs and vehicle performance.

[0073] In some embodiments, the diagnostic method further includes: adjusting the engine's ignition angle or air-fuel ratio after the vehicle controller exits the engine operating condition control mode.

[0074] The diagnostic method provided in this application embodiment, after the vehicle controller switches to engine operating condition control mode, allows the engine controller to quickly restore the operating temperature of the aftertreatment system by adjusting the engine's ignition angle or air-fuel ratio, in order to compensate for the potential impact on emissions caused by the vehicle controller entering engine operating condition control mode under medium and low load conditions.

[0075] Based on the descriptions of the above embodiments, this application provides an intelligent point selection control method that can dynamically activate according to user scenarios, achieve bidirectional collaborative control between VCU and ECU, and possess safety priority and resource scheduling mechanisms. This method can proactively create the necessary low-to-medium load steady-state operating conditions for OBD diagnostics, effectively improving the Integral Upgrade Rate (IUPR) and reducing regulatory compliance risks while ensuring driving safety, engine reliability, and vehicle economy. The core innovative architecture of this application lies in bidirectional collaborative control based on predictive activation: unifying vehicle controllers such as VCU, ECU, and cloud-based systems to construct an intelligent control system of "predictive activation—bidirectional collaboration—safety priority." It proactively predicts the future trend of the user's vehicle's IUPR and only proactively activates the diagnostic mode when there is a risk of non-compliance, achieving a fundamental shift from "passive waiting" to "proactive optimization." This application possesses a safety and performance balance mechanism: multi-layered resource scheduling and real-time monitoring, setting multi-dimensional constraint mechanisms to ensure that diagnostic behavior does not interfere with driving safety, damage engine reliability, or excessively affect vehicle performance. The system unconditionally interrupts diagnostics and resumes normal control, ensuring driving priority and component safety. The above two points together constitute the essential innovation of this application that distinguishes it from existing solutions. Through a comprehensive mechanism of intelligent prediction, two-way collaboration and safety priority, it effectively improves the OBD diagnostic completion rate (IUPR) of hybrid vehicles while ensuring driving experience and reliability, and meets increasingly stringent regulatory requirements.

[0076] Specifically, this application has the following beneficial effects: Improving IUPR compliance rate: By proactively identifying diagnostic needs through predictive algorithms and actively creating diagnostic conditions through the collaborative control of VCU, the problem of low completion rate of key OBD diagnostics in hybrid vehicles caused by point selection strategies is effectively solved, reducing the risk of regulatory default.

[0077] Achieving a balance between vehicle performance and diagnostics: By setting resource quotas, priority scheduling, and safety monitoring mechanisms, diagnostic needs are guaranteed while avoiding excessive impact of diagnostic activities on vehicle power, economy, drivability, and emissions.

[0078] Enhanced system robustness and safety: Through a dual safety mechanism of driver intent takeover and engine status anomaly monitoring, it is ensured that diagnostic actions will not interfere with driving safety or cause component damage in emergency conditions or engine malfunctions, thus achieving safety priority in diagnostic scheduling.

[0079] Adapting to personalized driving scenarios: The dynamic activation mechanism based on big data (historical driving data, navigation information) enables diagnostic strategies to adapt to different users' driving habits and actual road conditions, improving the system's intelligence level.

[0080] The diagnostic device provided in this application is described below. The diagnostic device described below can be referred to in correspondence with the diagnostic method described above.

[0081] Figure 5 This is one of the structural schematic diagrams of the diagnostic device provided in the embodiments of this application. (Refer to...) Figure 5 The diagnostic device provided in this application embodiment is applied to the vehicle controller of a vehicle, and the device may include: The judgment module 510 is used to receive the diagnosis request information of the first diagnostic item sent by the engine controller if the cloud determines that the predicted in-use monitoring frequency of the first diagnostic item is lower than the preset frequency among all diagnostic items of the engine controller of the vehicle, and then determine whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. The control module 520 is configured to send a handshake confirmation signal to the engine controller and enter the engine operating condition control mode if the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; the engine controller enters the diagnostic state after receiving the handshake confirmation signal and executes the third diagnostic item in the current driving cycle.

[0082] The diagnostic device provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of the diagnostic item in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic item, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic item, increasing the in-use monitoring frequency of the diagnostic item, and ensuring vehicle safety.

[0083] In some embodiments, the control module is used to: The engine speed and load are controlled to match the required operating conditions of the third diagnostic item; wherein the third diagnostic item is the highest priority diagnostic item among the second diagnostic items, and the diagnostic priority is determined based on the diagnostic urgency and safety impact of each diagnostic item among all diagnostic items.

[0084] In some embodiments, the control module is further configured to: If the vehicle meets any of the following first preset conditions, the engine operating condition control mode will be exited. The plurality of first preset conditions include: Receive the diagnostic completion information for the third diagnostic item sent by the engine controller; Received diagnostic failure information for the third diagnostic item sent by the engine controller; The system receives information from the engine controller that the duration of a single diagnostic test for the third diagnostic item exceeds a preset upper limit. The system receives information from the engine controller that the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds a preset limit. The vehicle's accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value is detected to exceed a preset upper limit. The engine controller receives information indicating that the engine is in an abnormal operating state.

[0085] In some embodiments, the cloud is used for: Acquire target data; wherein, the target data includes historical diagnostic data of all diagnostic items, historical driving data of the vehicle, and future planned route data of the vehicle's user; Based on the target data, diagnostic predictions are performed to obtain the predicted number of times all diagnostic items will be completed in future driving cycles. Based on the number of prediction completions, the prediction monitoring frequency for all diagnostic items is determined.

[0086] In some embodiments, the diagnostic request information includes at least one of the following: the identifier of the first diagnostic item, the required operating conditions, diagnostic priority information, estimated diagnostic duration, number of repeated diagnostic requests, and diagnostic conditions; the diagnostic conditions include at least one of the following: vehicle speed conditions, temperature conditions, altitude conditions, and driver intention conditions.

[0087] Figure 6 This is a second schematic diagram of the diagnostic device provided in the embodiments of this application. (Refer to...) Figure 6 The diagnostic device provided in this application embodiment is applied to the engine controller of a vehicle, and the device may include: The transmission module 610 is configured to send a diagnostic request message for the first diagnostic item to the vehicle controller if the cloud determines that the predicted monitoring frequency of the first diagnostic item among all diagnostic items of the engine controller is lower than a preset frequency; wherein, after receiving the diagnostic request message, the vehicle controller determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item; and when the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it sends a handshake confirmation signal to the engine controller and enters the engine operating condition control mode; the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is one of the second diagnostic items. The diagnostic module 620 is used to receive the handshake confirmation signal, then enter the diagnostic state, and execute the third diagnostic item within the current driving cycle.

[0088] The diagnostic device provided in this application embodiment sends a diagnostic request message through the engine controller when the predicted in-use monitoring frequency of the diagnostic item in the vehicle's engine controller is lower than a preset frequency. When the vehicle controller determines that the vehicle meets the diagnostic conditions of the diagnostic item, the vehicle controller actively controls the engine's operating conditions to match the required operating conditions of the diagnostic item to be executed, thereby actively creating suitable engine operating conditions for the execution of the diagnostic item, increasing the in-use monitoring frequency of the diagnostic item, and ensuring vehicle safety.

[0089] In some embodiments, the transmission module is further configured to: If the vehicle meets any of the following multiple second preset conditions, causing the vehicle controller to exit the engine operating condition control mode, then when the vehicle no longer meets any of the following multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the diagnostic request information of the third diagnostic item will be resent to the vehicle controller. The plurality of second preset conditions include: The duration of a single diagnosis for the third diagnostic item was detected to exceed a preset upper limit; The third diagnostic item was detected to have exceeded a preset limit in terms of cumulative activation duration or cumulative activation count within the current driving cycle. The vehicle controller receives information that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value of the vehicle exceeds a preset upper limit. An abnormal operating condition of the engine was detected.

[0090] In some embodiments, the transmission module is further configured to: If the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds the preset limit, no other diagnostic request information will be sent in the current driving cycle. If the diagnostic request information for the first diagnostic item has already been sent within a preset interval, no other diagnostic request information will be sent. If the number of times the engine operating status is abnormal within the current driving cycle exceeds a set threshold, no further diagnostic request information will be sent within the current driving cycle.

[0091] In some embodiments, the diagnostic module is further configured to: When the vehicle controller exits the engine operating condition control mode, it adjusts the engine's ignition angle or air-fuel ratio.

[0092] Specifically, the diagnostic device provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0093] Figure 7 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 7 As shown, the electronic device may include: a processor 710, a communications interface 720, a memory 730, and a communication bus 740, wherein the processor 710, the communications interface 720, and the memory 730 communicate with each other via the communication bus 740. The processor 710 can call logical instructions in the memory 730 to execute diagnostic methods, such as: If the cloud determines that the predicted monitoring frequency of the first diagnostic item in all diagnostic items of the vehicle's engine controller is lower than the preset frequency, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

[0094] Furthermore, the logical instructions in the aforementioned memory 730 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0095] On the other hand, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the diagnostic methods provided by the above methods, including, for example: If the cloud determines that the predicted monitoring frequency of the first diagnostic item in all diagnostic items of the vehicle's engine controller is lower than the preset frequency, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

[0096] Furthermore, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer is able to perform the steps of the diagnostic methods provided by the above-described methods, such as including: If the cloud determines that the predicted monitoring frequency of the first diagnostic item in all diagnostic items of the vehicle's engine controller is lower than the preset frequency, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

[0097] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0098] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0099] It should also be noted that in the embodiments of this application, the terms "first," "second," etc., are used to distinguish similar objects, and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited. For example, the first object can be one or more.

[0100] In this application embodiment, the term "and / or" describes the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0101] In this application's embodiments, "determine B based on A" means that factor A must be considered when determining B. It is not limited to "B can be determined based solely on A," but should also include: "determine B based on A and C," "determine B based on A, C, and E," "determine C based on A, and further determine B based on C," etc. Additionally, it can include using A as a condition for determining B, for example, "when A meets the first condition, determine B using the first method"; another example, "when A meets the second condition, determine B," etc.; another example, "when A meets the third condition, determine B based on the first parameter," etc. Of course, it can also be a condition where A is a factor in determining B, for example, "when A meets the first condition, determine C using the first method, and further determine B based on C," etc.

[0102] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0103] In this application, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this application, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described can be combined in a suitable manner in any one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0104] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A diagnostic method, characterized in that, Vehicle controllers used in vehicles include: If the cloud determines that the predicted monitoring frequency of the first diagnostic item in all diagnostic items of the vehicle's engine controller is lower than the preset frequency, it receives the diagnostic request information of the first diagnostic item sent by the engine controller, and then determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, a handshake confirmation signal is sent to the engine controller, and the engine operating condition control mode is entered; wherein, the engine operating condition control mode is used to control the operating condition of the vehicle's engine to match the required operating condition of the third diagnostic item; the third diagnostic item is a diagnostic item in the second diagnostic item; after receiving the handshake confirmation signal, the engine controller enters the diagnostic state and executes the third diagnostic item in the current driving cycle.

2. The diagnostic method according to claim 1, characterized in that, The entry into the engine operating condition control mode includes: The engine speed and load are controlled to match the required operating conditions of the third diagnostic item; wherein the third diagnostic item is the highest priority diagnostic item among the second diagnostic items, and the diagnostic priority is determined based on the diagnostic urgency and safety impact of each diagnostic item among all diagnostic items.

3. The diagnostic method according to claim 1, characterized in that, Also includes: If the vehicle meets any of the following first preset conditions, the engine operating condition control mode will be exited. The plurality of first preset conditions include: Receive the diagnostic completion information for the third diagnostic item sent by the engine controller; Received diagnostic failure information for the third diagnostic item sent by the engine controller; The system receives information from the engine controller that the duration of a single diagnostic test for the third diagnostic item exceeds a preset upper limit. The system receives information from the engine controller that the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds a preset limit. The vehicle's accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value is detected to exceed a preset upper limit. The engine controller receives information indicating that the engine is in an abnormal operating state.

4. The diagnostic method according to claim 1, characterized in that, The cloud is used for: Acquire target data; wherein, the target data includes historical diagnostic data of all diagnostic items, historical driving data of the vehicle, and future planned route data of the vehicle's user; Based on the target data, diagnostic predictions are performed to obtain the predicted number of times all diagnostic items will be completed in future driving cycles. Based on the number of prediction completions, the prediction monitoring frequency for all diagnostic items is determined.

5. The diagnostic method according to claim 1, characterized in that, The diagnostic request information includes at least one of the following: the identifier of the first diagnostic item, the required operating conditions, the diagnostic priority information, the estimated diagnostic time, the number of repeated diagnostic requests, and the diagnostic conditions; the diagnostic conditions include at least one of the following: vehicle speed conditions, temperature conditions, altitude conditions, and driver intention conditions.

6. A diagnostic method, characterized in that, An engine controller used in vehicles, including: If the cloud determines that the predicted monitoring frequency of the first diagnostic item among all diagnostic items of the engine controller is lower than a preset frequency, it sends a diagnostic request message for the first diagnostic item to the vehicle controller. Upon receiving the diagnostic request message, the vehicle controller determines whether the vehicle meets the diagnostic conditions of each diagnostic item in the first diagnostic item. If the vehicle meets the diagnostic conditions of the second diagnostic item in the first diagnostic item, it sends a handshake confirmation signal to the engine controller and enters the engine operating condition control mode. This engine operating condition control mode is used to match the operating condition of the vehicle's engine with the required operating condition of the third diagnostic item. The third diagnostic item is one of the second diagnostic items. The handshake confirmation signal is received, and then the diagnostic state is entered, and the third diagnostic item is executed within the current driving cycle.

7. The diagnostic method according to claim 6, characterized in that, Also includes: If the vehicle meets any of the following multiple second preset conditions, causing the vehicle controller to exit the engine operating condition control mode, then when the vehicle no longer meets any of the following multiple second preset conditions and meets the diagnostic conditions of the third diagnostic item, the diagnostic request information of the third diagnostic item will be resent to the vehicle controller. The plurality of second preset conditions include: The duration of a single diagnosis for the third diagnostic item was detected to exceed a preset upper limit; The third diagnostic item was detected to have exceeded a preset limit in terms of cumulative activation duration or cumulative activation count within the current driving cycle. The vehicle controller receives information that the accelerator pedal change rate, brake pedal change rate, or longitudinal acceleration signal value of the vehicle exceeds a preset upper limit. An abnormal operating condition of the engine was detected.

8. The diagnostic method according to claim 6, characterized in that, Also includes: If the cumulative activation duration or cumulative activation count of the third diagnostic item in the current driving cycle exceeds the preset limit, no other diagnostic request information will be sent in the current driving cycle. If the diagnostic request information for the first diagnostic item has already been sent within a preset interval, no other diagnostic request information will be sent. If the number of times the engine operating status is abnormal within the current driving cycle exceeds a set threshold, no further diagnostic request information will be sent within the current driving cycle.

9. The diagnostic method according to claim 6, characterized in that, Also includes: When the vehicle controller exits the engine operating condition control mode, it adjusts the engine's ignition angle or air-fuel ratio.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the diagnostic method as described in any one of claims 1 to 5 or the diagnostic method as described in any one of claims 6 to 9.

Images