Diagnostic system and method for commercial vehicle driver end OBD annual inspection and pre-inspection

Abstract

The invention provides a commercial vehicle driver end OBD annual inspection pre-inspection diagnosis system and method. The commercial vehicle driver end OBD annual inspection pre-inspection diagnosis system comprises an entrance module, a supportability judgment module, a power-on detection module, a connection state judgment module and a cloud analysis module. The commercial vehicle driver end OBD annual inspection reservation diagnosis method comprises the following steps: S1, starting an annual inspection pre-inspection function; s2, judging whether the vehicle supports an OBD annual inspection and pre-inspection function or not; s3, detecting the power-on state of the vehicle; s4, the connection state of the vehicle-mounted Tbox and an engine controller EMS is judged; s5, whether the OBD annual inspection pre-inspection item is qualified or not is judged, and an annual inspection pre-inspection report is output; according to the method, comprehensive monitoring and diagnosis of the vehicle OBD system are realized, and a driver is helped to know the vehicle state in advance before annual inspection, so that time, economic and human resources are prevented from being wasted due to blind annual inspection.

Description

Technical Field

[0001] The present invention relates to the technical field of commercial vehicles, and in particular to a diagnostic system and method for OBD annual inspection and pre-inspection on a commercial vehicle driver side. Background Art

[0002] With the advancement of commercial vehicle technology, society has placed increasingly higher demands on the environmental performance of commercial vehicles, especially in terms of emission standards. Commercial vehicles have been gradually upgraded from the National V emission standard to the National VI emission standard. All in-use National VI commercial vehicles and newly produced National VI emission vehicles must have an OBD (on-board diagnostic system) module built into the engine controller EMS to monitor key steps such as the vehicle engine, fuel system, and emission system, and meet the regulatory requirements of environmental regulations on vehicle emission status. Currently, commercial vehicles are required to undergo annual vehicle inspections, during which the OBD system must be inspected at a third-party inspection station or vehicle management office. If the vehicle's OBD system fails the inspection, the driver must adjust the vehicle and re-test it. However, it is common for drivers to not understand the status of their vehicle's OBD system, leading them to blindly go through the inspection line for annual inspections. Only after failing the inspection will they realize the problem and then adjust the vehicle's status or seek repairs. In this case, the driver wastes time, money, and manpower due to not understanding the status of the vehicle's OBD system.

[0003] In the prior art, the reasons why drivers do not understand the status of their vehicle's OBD system are as follows: Closed access channels for obtaining OBD system status information: Currently, commercial vehicle OBD system status information can be read through the vehicle manufacturer's Internet of Vehicles system, but this information is generally not open to commercial vehicle drivers. Without professional channels, drivers cannot know the status of the vehicle's OBD system in advance. Vehicle repair shops or service stations can obtain vehicle OBD status information through diagnostic equipment, but this method is costly, and drivers generally do not take the initiative to go to the repair station for diagnosis unless there is an obvious fault. Drivers have difficulty accurately understanding OBD system status information: Even if the vehicle's OBD system status information is obtained through professional diagnostic equipment, because this information is usually highly professional and technical, drivers who are not familiar with vehicle engineering technology or environmental regulations often find it difficult to understand the meaning of this information and cannot make correct judgments. As a result, when the OBD system fails, they are unable to take appropriate maintenance measures or make decisions in a timely manner. Summary of the Invention

[0004] The purpose of the present invention is to solve the shortcomings of the prior art and to propose a diagnostic system and method for OBD annual inspection and pre-inspection on the driver side of commercial vehicles.

[0005] To achieve the above object, the present invention adopts the following technical solutions: A diagnostic system and method for OBD annual inspection and pre-inspection on a commercial vehicle driver side, the diagnostic system for OBD annual inspection and pre-inspection on a commercial vehicle driver side includes an entry module, a support judgment module, a power-on detection module, a connection status judgment module, and a cloud analysis module; The entry module is used to provide the driver with an entry to start the annual inspection pre-inspection function; The support determination module is used to determine whether the vehicle supports the OBD annual inspection function; The power-on detection module is used to ensure that the vehicle is in a powered-on state when using the annual inspection pre-inspection function; The connection status judgment module is used to monitor the connection between the Tbox and the EMS controller; The cloud analysis module is used to analyze OBD data and generate an annual inspection report.

[0006] The diagnostic method for the commercial vehicle driver-side OBD annual inspection reservation includes the following steps: S1: Start the annual inspection and pre-inspection function; The driver starts the OBD annual inspection pre-inspection function by selecting the function entry icon in the APP, which activates the entry module. The entry module sends a request to the support judgment module to confirm whether the vehicle meets the requirements of the OBD annual inspection pre-inspection function; The APP is connected to the vehicle-mounted Tbox and obtains basic vehicle information through the vehicle-mounted Tbox; the basic vehicle information includes the vehicle's OBD interface type, hardware configuration, etc.

[0007] S2: Determine whether the vehicle supports the OBD annual inspection pre-inspection function; The supportability determination module receives the request and determines whether the vehicle supports the OBD annual inspection pre-inspection function based on the basic vehicle information, including the following sub-steps: S21: Check the vehicle's OBD interface type; The supportability judgment module checks whether the vehicle's OBD interface type meets the interface type required for the OBD annual inspection pre-inspection. If so, the process proceeds to step S22. If not, a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; S22: confirm whether the vehicle's OBD interface is enabled; The supportability judgment module connects to the vehicle's OBD interface. If the connection is successful and data or fault codes can be read, the vehicle's OBD interface is confirmed to be enabled, and the process proceeds to step S23. If the connection cannot be made or data or fault codes cannot be read, it indicates that the vehicle's OBD interface is not enabled or there is a fault, and a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function. S23: Check whether the vehicle meets the data requirements of the OBD annual inspection pre-inspection function; The support judgment module checks whether the vehicle's engine control module (ECM) can provide the data required for the OBD annual inspection pre-inspection function, including engine fault codes, emission control system data, etc. If the data cannot be provided, a prompt will pop up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; if the data can be provided, it meets the data requirements of the OBD annual inspection pre-inspection function, and the judgment result that the vehicle supports the OBD annual inspection pre-inspection function will be returned.

[0008] S3: Detect vehicle power-on status; The power-on detection module communicates data with the engine controller EMS through the vehicle's Tbox. If the vehicle's Tbox can continuously read and monitor the OBD status information of the engine controller EMS, it means that the vehicle is in a normal power-on state. If the vehicle's Tbox cannot normally receive data information from the engine controller EMS, it means that the connection has failed and the vehicle is not powered on. The driver will be reminded through the APP that the vehicle needs to be powered on before the OBD annual inspection pre-inspection function can be used. Furthermore, whether the vehicle is fully powered on is confirmed by whether the on-board Tbox can read the vehicle's status information (such as engine operating status, sensor data, etc.) in real time; if the on-board Tbox cannot normally obtain the vehicle's status information, it is determined that the vehicle is not powered on normally; otherwise, it is in a normal powered-on state.

[0009] S4: Determine the connection status between the vehicle-mounted Tbox and the engine controller EMS; The connection status judgment module determines the connection status between the vehicle-mounted Tbox and the engine controller EMS through real-time data communication monitoring, arbitration status judgment, and fault detection mechanisms. When the vehicle-mounted Tbox and the engine controller EMS are in abnormal connection, arbitration status, or unable to connect, the APP provides a fixed message to remind the driver to use the annual inspection pre-inspection function later. Specifically, real-time data communication monitoring: The connection status judgment module confirms whether the connection is normal by monitoring the data communication between the vehicle-mounted Tbox and the engine controller EMS; if the vehicle-mounted Tbox cannot receive valid OBD data or signals from the engine controller EMS, the connection status judgment module will determine that the connection is abnormal; Arbitration status judgment: When multiple controllers on the bus initiate communication requests at the same time, resulting in data transmission conflicts, the connection status judgment module identifies that the communication between the vehicle-mounted Tbox and the engine controller EMS is in arbitration status; Fault detection mechanism: The connection status judgment module detects the fault indication signal between the vehicle-mounted Tbox and the engine controller EMS. If the engine controller EMS fails to respond or the communication is interrupted, the connection status judgment module marks it as an unconnectable state.

[0010] S5: Determine whether the OBD annual inspection and pre-inspection items are qualified and output the annual inspection and pre-inspection report; The cloud analysis module checks the basic vehicle information collected by the on-board Tbox item by item. If any item fails, the OBD annual inspection pre-inspection item is judged as unqualified. Based on the judgment results, an annual inspection pre-inspection report is generated; The annual inspection and pre-inspection report shall include the judgment results, items requiring re-inspection, and suggestions for the next steps for unqualified items; Furthermore, the basic vehicle information collected by the onboard Tbox also includes vehicle VIN, engine EMS CVN, engine EMS CALID, OBD inspection information, etc. The vehicle VIN is the vehicle unique identification number; the engine EMS CVN is the engine controller verification number, and the engine EMS CALID is the engine controller calibration identifier; The OBD check information includes OBD communication check, MIL light status check, OBD fault code status check, and ready status unfinished item check; The cloud analysis module verifies the vehicle VIN, verifies the version and status of the engine controller through the engine EMS CVN, and checks the specific configuration and version of the vehicle engine controller through the engine EMS CALID; Verify that the OBD system can communicate normally with the vehicle's various control units through the OBD communication check, verify that the MIL light status is normal through the MIL status check, check whether the vehicle has any fault codes through the OBD fault code status check, and check whether the ready state in the OBD system is complete through the ready state incomplete items; Compared with the prior art, the present invention has the following beneficial effects: This method establishes communication between the on-board Tbox and the vehicle engine EMS to read OBD information in real time, and automatically analyzes and judges the read information in the cloud, outputting the inspection conclusion of whether the annual inspection OBD inspection items are qualified and the next step disposal suggestions for the unqualified items; it realizes comprehensive monitoring and diagnosis of the vehicle OBD system, helping drivers to understand the vehicle status in advance before the annual inspection, thereby avoiding wasting time, economic and human resources due to blind annual inspection. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 This is a flowchart of the steps of a diagnostic method for OBD annual inspection and pre-inspection on the driver side of a commercial vehicle according to the present invention. DETAILED DESCRIPTION

[0012] In order to provide a further understanding of the purpose, structure, features, and functions of the present invention, the present invention is described in detail below with reference to the embodiments.

[0013] like Figure 1 As shown, a diagnostic system and method for OBD annual inspection pre-inspection on the driver side of a commercial vehicle, the diagnostic system for OBD annual inspection appointment on the driver side of a commercial vehicle includes an entry module, a support judgment module, a power-on detection module, a connection status judgment module, and a cloud analysis module; The entry module is used to provide the driver with an entry to start the annual inspection pre-inspection function; The support determination module is used to determine whether the vehicle supports the OBD annual inspection function; The power-on detection module is used to ensure that the vehicle is in a powered-on state when using the annual inspection pre-inspection function; The connection status judgment module is used to monitor the connection between the Tbox and the EMS controller; The cloud analysis module is used to analyze OBD data and generate an annual inspection report.

[0014] The diagnostic method for the commercial vehicle driver-side OBD annual inspection reservation includes the following steps: S1: Start the annual inspection and pre-inspection function; The driver starts the OBD annual inspection pre-inspection function by selecting the function entry icon in the APP, which activates the entry module. The entry module sends a request to the support judgment module to confirm whether the vehicle meets the requirements of the OBD annual inspection pre-inspection function; The APP is connected to the vehicle-mounted Tbox and obtains basic vehicle information through the vehicle-mounted Tbox; the basic vehicle information includes the vehicle's OBD interface type, hardware configuration, etc.

[0015] In this method, drivers only need to activate the annual inspection pre-inspection function through the app to obtain information on whether the vehicle meets the OBD annual inspection requirements. Compared with the traditional annual inspection, which only discovers problems after the inspection, knowing the vehicle status in advance can effectively reduce the waste of time and money.

[0016] S2: Determine whether the vehicle supports the OBD annual inspection pre-inspection function; The supportability determination module receives the request and determines whether the vehicle supports the OBD annual inspection pre-inspection function based on the basic vehicle information, including the following sub-steps: S21: Check the vehicle's OBD interface type; The supportability judgment module checks whether the vehicle's OBD interface type meets the interface type required for the OBD annual inspection pre-inspection. If so, the process proceeds to step S22. If not, a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; S22: confirm whether the vehicle's OBD interface is enabled; The supportability judgment module connects to the vehicle's OBD interface. If the connection is successful and data or fault codes can be read, the vehicle's OBD interface is confirmed to be enabled, and the process proceeds to step S23. If the connection cannot be made or data or fault codes cannot be read, it indicates that the vehicle's OBD interface is not enabled or there is a fault, and a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function. S23: Check whether the vehicle meets the data requirements of the OBD annual inspection pre-inspection function; The support judgment module checks whether the vehicle's engine control module (ECM) can provide the data required for the OBD annual inspection pre-inspection function, including engine fault codes, emission control system data, etc. If the data cannot be provided, a prompt will pop up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; if the data can be provided, it meets the data requirements of the OBD annual inspection pre-inspection function, and the judgment result that the vehicle supports the OBD annual inspection pre-inspection function will be returned.

[0017] This method ensures that vehicle owners fully understand whether their vehicle's OBD system meets annual inspection requirements before the inspection by comprehensively checking multiple data points, including the OBD interface, vehicle hardware, and the Engine Control Module (ECM). This avoids inspection failures due to system failures or data anomalies.

[0018] S3: Detect vehicle power-on status; The power-on detection module communicates data with the engine controller EMS through the vehicle's Tbox. If the vehicle's Tbox can continuously read and monitor the OBD status information of the engine controller EMS, it means that the vehicle is in a normal power-on state. If the vehicle's Tbox cannot normally receive data information from the engine controller EMS, it means that the connection has failed and the vehicle is not powered on. The driver will be reminded through the APP that the vehicle needs to be powered on before the OBD annual inspection pre-inspection function can be used. Furthermore, whether the vehicle is fully powered on is confirmed by whether the on-board Tbox can read the vehicle's status information (such as engine operating status, sensor data, etc.) in real time; if the on-board Tbox cannot normally obtain the vehicle's status information, it is determined that the vehicle is not powered on normally; otherwise, it is in a normal powered-on state.

[0019] S4: Determine the connection status between the vehicle-mounted Tbox and the engine controller EMS; The connection status judgment module determines the connection status between the vehicle-mounted Tbox and the engine controller EMS through real-time data communication monitoring, arbitration status judgment, and fault detection mechanisms. When the vehicle-mounted Tbox and the engine controller EMS are in abnormal connection, arbitration status, or unable to connect, the APP provides a fixed message to remind the driver to use the annual inspection pre-inspection function later. Specifically, real-time data communication monitoring: The connection status judgment module confirms whether the connection is normal by monitoring the data communication between the vehicle-mounted Tbox and the engine controller EMS; if the vehicle-mounted Tbox cannot receive valid OBD data or signals from the engine controller EMS, the connection status judgment module will determine that the connection is abnormal; Arbitration status judgment: When multiple controllers on the bus initiate communication requests at the same time, resulting in data transmission conflicts, the connection status judgment module identifies that the communication between the vehicle-mounted Tbox and the engine controller EMS is in arbitration status; Fault detection mechanism: The connection status judgment module detects the fault indication signal between the vehicle-mounted Tbox and the engine controller EMS. If the engine controller EMS fails to respond or the communication is interrupted, the connection status judgment module marks it as an unconnectable state.

[0020] This method uses real-time data communication between the vehicle-mounted Tbox and the engine controller EMS. The system can accurately determine whether the vehicle is in normal working condition, ensuring that the OBD annual inspection pre-inspection function can only be performed when the vehicle is in normal condition, thereby avoiding annual inspection pre-inspection of vehicles that do not meet the conditions.

[0021] S5: Determine whether the OBD annual inspection and pre-inspection items are qualified and output the annual inspection and pre-inspection report; The cloud analysis module checks the basic vehicle information collected by the on-board Tbox item by item. If any item fails, the OBD annual inspection pre-inspection item is judged as unqualified. Based on the judgment results, an annual inspection pre-inspection report is generated; The annual inspection and pre-inspection report shall include the judgment results, items requiring re-inspection, and suggestions for the next steps for unqualified items; Furthermore, the basic vehicle information collected by the onboard Tbox also includes vehicle VIN, engine EMS CVN, engine EMS CALID, OBD inspection information, etc. The vehicle VIN is the vehicle unique identification number; the engine EMS CVN is the engine controller verification number, and the engine EMS CALID is the engine controller calibration identifier; The OBD check information includes OBD communication check, MIL light status check, OBD fault code status check, and ready status unfinished item check; The cloud analysis module verifies the vehicle VIN, verifies the version and status of the engine controller through the engine EMS CVN, and checks the specific configuration and version of the vehicle engine controller through the engine EMS CALID; Use OBD communication check to verify whether the OBD system can communicate normally with the vehicle's various control units, use MIL light status to check whether it is in normal status, use OBD fault code status to check whether the vehicle has fault codes, and use ready status incomplete items to check whether the ready status in the OBD system is completed.

[0022] The annual inspection pre-inspection report generated by this method includes the judgment results, items that need to be re-inspected, and suggestions for the next steps for unqualified items. Drivers can make repairs or adjustments in a timely manner based on the suggestions in the annual inspection pre-inspection report to avoid being judged as unqualified during the formal annual inspection, reducing unnecessary repeated repairs and inspections and improving maintenance efficiency.

[0023] The present invention has been described with reference to the above embodiments. However, the above embodiments are merely exemplary embodiments of the present invention. It should be noted that the disclosed embodiments do not limit the scope of the present invention. On the contrary, modifications and improvements that do not depart from the spirit and scope of the present invention are intended to be protected by the present invention.

Claims

1. A diagnostic method for scheduling an annual OBD inspection on a commercial vehicle driver, characterized by: The following steps are involved: S1: Start the annual inspection and pre-inspection function; A diagnostic system based on the OBD annual inspection appointment of a commercial vehicle driver, which includes an entry module, a support judgment module, a power-on detection module, a connection status judgment module, and a cloud analysis module; The driver starts the OBD annual inspection pre-inspection function by selecting the function entry icon in the app, which activates the entry module. The entry module sends a request to the support judgment module to confirm whether the vehicle meets the requirements of the OBD annual inspection pre-inspection function; S2: Determine whether the vehicle supports the OBD annual inspection pre-inspection function; The supportability determination module receives the request and determines whether the vehicle supports the OBD annual inspection pre-inspection function based on the basic vehicle information, including the following sub-steps: S21: Check the vehicle's OBD interface type; S22: confirm whether the vehicle's OBD interface is enabled; S23: Check whether the vehicle meets the data requirements of the OBD annual inspection pre-inspection function; S3: Detect vehicle power-on status; The power-on detection module communicates data with the engine controller EMS through the vehicle-mounted Tbox to check whether the vehicle is in the power-on state; S4: Determine the connection status between the vehicle-mounted Tbox and the engine controller EMS; The connection status judgment module judges the connection status between the vehicle-mounted Tbox and the engine controller EMS through real-time data communication monitoring, arbitration status judgment, and fault detection mechanisms; S5: Determine whether the OBD annual inspection and pre-inspection items are qualified and output the annual inspection and pre-inspection report; The cloud-based analysis module checks each item of the basic vehicle information collected by the on-board Tbox. If any item fails to meet the requirements, the OBD annual inspection pre-inspection item is judged to be unqualified. An annual inspection pre-inspection report is generated based on the determination results. The annual inspection pre-inspection report includes the determination results, items that need to be re-inspected, and suggestions for the next steps for unqualified items.

2. The diagnostic method for annual OBD inspection reservation on a commercial vehicle driver side according to claim 1, characterized in that: In step S1, the entry module is used to provide the driver with an entry to start the annual inspection pre-inspection function; The support determination module is used to determine whether the vehicle supports the OBD annual inspection function; The power-on detection module is used to ensure that the vehicle is in a powered-on state when using the annual inspection pre-inspection function; The connection status judgment module is used to monitor the connection between the Tbox and the EMS controller; The cloud analysis module is used to analyze OBD data and generate an annual inspection report; The APP is connected to the vehicle Tbox and obtains basic vehicle information through the vehicle Tbox.

3. The diagnostic method for scheduling an annual OBD inspection on a commercial vehicle driver side according to claim 1, characterized in that: The specific contents of step S2 are as follows: S21: Check the vehicle's OBD interface type; The supportability judgment module checks whether the vehicle's OBD interface type meets the interface type required for the OBD annual inspection pre-inspection. If so, the process proceeds to step S22. If not, a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; S22: confirm whether the vehicle's OBD interface is enabled; The supportability judgment module connects to the vehicle's OBD interface. If the connection is successful and data or fault codes can be read, the vehicle's OBD interface is confirmed to be enabled, and the process proceeds to step S23. If the connection cannot be made or data or fault codes cannot be read, it indicates that the vehicle's OBD interface is not enabled or there is a fault, and a prompt pops up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function. S23: Check whether the vehicle meets the data requirements of the OBD annual inspection pre-inspection function; The support judgment module checks whether the vehicle's engine control module (ECM) can provide the data required for the OBD annual inspection pre-inspection function, including engine fault codes, emission control system data, etc. If the data cannot be provided, a prompt will pop up through the APP to remind the driver that the vehicle does not support the OBD annual inspection pre-inspection function; if the data can be provided, it meets the data requirements of the OBD annual inspection pre-inspection function, and the judgment result that the vehicle supports the OBD annual inspection pre-inspection function will be returned.

4. The diagnostic method for scheduling an annual OBD inspection on a commercial vehicle driver side according to claim 1, characterized in that: The specific contents of step S3 are as follows: The power-on detection module communicates data with the engine controller EMS through the on-board Tbox. If the on-board Tbox can continuously read and monitor the OBD status information of the engine controller EMS, it means that the vehicle is in a normal power-on state; if the on-board Tbox cannot normally receive data information from the engine controller EMS, it means that the connection has failed and the vehicle is not powered on. A reminder is provided through the APP to inform the driver that the vehicle needs to be powered on before the OBD annual inspection pre-inspection function can be used.

5. The diagnostic method for annual OBD inspection reservation on a commercial vehicle driver side according to claim 1, characterized in that: In step S4, the connection status judgment module determines the connection status between the vehicle-mounted Tbox and the engine controller EMS through real-time data communication monitoring, arbitration status judgment, and fault detection mechanism; when the vehicle-mounted Tbox and the engine controller EMS are in abnormal connection, arbitration status, or unable to connect status, the APP side provides fixed words to remind the driver to use the annual inspection pre-inspection function later.

6. The diagnostic method for scheduling an annual OBD inspection on a commercial vehicle driver side as claimed in claim 4, characterized in that: Whether the vehicle is fully powered on is confirmed by whether the on-board Tbox can read the vehicle's status information in real time; if the on-board Tbox cannot normally obtain the vehicle's status information, it is determined that the vehicle is not powered on normally; otherwise, it is in a normal powered state.

Images