Method and system for automatically testing vehicle emission diagnostic interfaces

Abstract

This application discloses a method and system for automatically testing an on-board emission diagnostic interface (OBD). The system includes: an OBD interface for outputting vehicle test data during vehicle testing; an ECU device for detecting and / or storing the vehicle test data; a first bus connected to the terminals of the OBD interface and the ECU device; a display device comprising a control module for testing whether the OBD interface has malfunctioned and a display module for displaying information indicating whether the OBD interface has malfunctioned; and a second bus connected to the interface terminals of the OBD interface and the control device. The control module is configured to interact with the ECU device via the first and second buses to determine whether the terminals of the OBD interface and the interface terminals have malfunctioned. The advantage of this application is that it achieves fully automated testing of the on-board emission diagnostic interface.

Description

Technical Field

[0001] This invention relates to the field of vehicle emission diagnostics technology, and more specifically, to a method and system for automatically testing vehicle emission diagnostic interfaces. Background Technology

[0002] With increasingly severe environmental problems, countries around the world have introduced stricter limits on vehicle exhaust emissions to reduce pollutant emissions. To ensure that actual vehicle emissions meet standards, it is necessary to regularly inspect the on-board emission diagnostic system (OBD). As a key component of the OBD system, the normal working condition of the OBD interface directly determines the accuracy of emission testing; therefore, regular inspection of the OBD interface is required to ensure its proper functioning.

[0003] Existing OBD interface inspection methods mainly rely on manual labor, requiring technicians to manually extract the interface's electronic signals and determine compliance with standards. This method is inefficient and lacks precision. Furthermore, some vehicle models' OBD interfaces are difficult to inspect manually, further complicating the inspection process. Summary of the Invention

[0004] The summary section of this application is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description section below. This summary section is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.

[0005] Some embodiments of this application propose a method and system for automatically testing on-board emission diagnostic interfaces to address the technical problems mentioned in the background section above.

[0006] As a first aspect of this application, some embodiments of this application provide a system for automatically testing an on-board diagnostic (OBD) interface, comprising: an OBD interface for outputting vehicle test data during vehicle testing; an ECU device for detecting and / or storing the vehicle test data; a first bus connected to the terminals of the OBD interface and the ECU device to enable data transmission between the input terminals of the OBD interface and the ECU device; the vehicle interface testing system further comprises: a display device including a control module for testing whether the OBD interface has malfunctioned and a display module for displaying information indicating whether the OBD interface has malfunctioned; a second bus connected to the interface terminals of the OBD interface and the control device to enable data transmission between the interface terminals of the OBD interface and the testing device; wherein the control module is configured to interact with the ECU device via the first bus and the second bus to determine whether the terminals of the OBD interface and the interface terminals have malfunctioned.

[0007] Furthermore, the control module determines whether it can obtain data from the ECU device through the first bus; if so, the control module reads the model of the ECU device.

[0008] Furthermore, the control module determines whether the model of the ECU device can be obtained through the first bus; if so, the control module reads the CVN code of the ECU device; otherwise, the display module displays the fault information of the corresponding OBD interface terminal.

[0009] Furthermore, the control module determines whether the CVN code of the ECU device can be obtained through the first bus; if so, the control module obtains the CVN code of the ECU device through the second bus; otherwise, the display module displays the fault information of the corresponding OBD interface terminal.

[0010] Furthermore, the control module determines whether the CVN code of the ECU device can be obtained through the second bus; if so, the display module displays information indicating that the interface terminal of the corresponding OBD interface is normal; otherwise, the display module displays information indicating that the interface terminal of the corresponding OBD interface is faulty.

[0011] Furthermore, the first bus and the second bus are two different types of buses.

[0012] Furthermore, the first bus is the J1939 bus, and the second bus is the CAN bus.

[0013] Furthermore, the vehicle detection data output by the OBD interface includes, but is not limited to, the vehicle's engine emission data.

[0014] Furthermore, the vehicle interface inspection system also includes: a communication terminal, used to enable the ECU device to establish wireless communication with the outside; wherein, the communication terminal is connected to the display device, the ECU device and the OBD interface through a first bus; the ECU device interacts with the server to exchange vehicle monitoring data through the communication terminal.

[0015] As a second aspect of this application, some embodiments of this application provide a method for automatically testing an on-board diagnostic (OBD) interface, which is performed by a vehicle interface testing system. The vehicle interface testing system includes: an OBD interface for outputting vehicle testing data during vehicle testing; an ECU device for detecting and / or storing the vehicle testing data; a first bus connected to the terminals of the OBD interface and the ECU device to enable data transmission between the input terminals of the OBD interface and the ECU device; the vehicle interface testing system further includes: a display device comprising a control module for testing whether the OBD interface has malfunctioned and a display module for displaying information indicating whether the OBD interface has malfunctioned; a second bus connected to the interface terminals of the OBD interface and the control device to enable data transmission between the interface terminals of the OBD interface and the testing device; wherein the control module is configured to connect to the ECU device via the first bus and the second bus respectively. The CU device performs data interaction; the vehicle interface verification method includes: the control module determines whether it can obtain data from the ECU device through the first bus; if so, the control module reads the model of the ECU device; the control module determines whether it can obtain the model of the ECU device through the first bus; if so, the control module reads the CVN code of the ECU device; otherwise, the display module displays the terminal fault information of the corresponding OBD interface; the control module determines whether it can obtain the CVN code of the ECU device through the first bus; if so, the control module obtains the CVN code of the ECU device through the second bus; otherwise, the display module displays the terminal fault information of the corresponding OBD interface; the control module determines whether it can obtain the CVN code of the ECU device through the second bus; if so, the display module displays the information that the interface terminal of the corresponding OBD interface is normal; otherwise, the display module displays the information that the interface terminal of the corresponding OBD interface is faulty.

[0016] The beneficial effect of this application is that it enables fully automated testing of the vehicle emission diagnostic interface.

[0017] More specifically, some embodiments of this application may produce the following specific beneficial effects:

[0018] It has achieved fully automated inspection of the OBD interface, eliminating a lot of repetitive work in the manual inspection process and greatly improving inspection efficiency;

[0019] The inspection process and results are displayed through a display device, and standard inspection reports can be generated to provide a basis for tracking, monitoring and verifying inspection results;

[0020] It employs general technical methods, does not rely on specialized testing equipment, has high versatility, and can be widely applied to the OBD interface testing of various motor vehicles. Attached Figure Description

[0021] The accompanying drawings, which form part of this application, are used to provide a further understanding of the application and to make other features, objects, and advantages of the application more apparent. The illustrative embodiments and descriptions of this application are used to explain the application and do not constitute an undue limitation of the application.

[0022] Furthermore, throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the elements are not necessarily drawn to scale.

[0023] In the attached diagram:

[0024] Figure 1 This is a vehicle data management system according to one embodiment of the present application;

[0025] Figure 2 This is a schematic diagram of the specific component architecture of a vehicle according to one embodiment of this application;

[0026] Figure 3 This is a schematic diagram of the hardware structure of a display device according to an embodiment of this application;

[0027] Figure 4 This is a schematic diagram of the module composition of a processor according to an embodiment of this application;

[0028] Figure 5 This is a schematic block diagram of the structure of an OBD interface according to an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of the main steps of a method for automatically inspecting an on-board emission diagnostic interface according to an embodiment of this application;

[0030] Figure 7 This is a schematic diagram illustrating the specific steps of a method for automatically inspecting an on-board emission diagnostic interface according to an embodiment of this application.

[0031] Meaning of the reference numerals in the diagram:

[0032] 100. Vehicle Data Management System;

[0033] 200. Vehicles;

[0034] 210. Ontology;

[0035] 220. Communication terminal;

[0036] 230. ECU device;

[0037] 240. First bus;

[0038] 250. Display device;

[0039] 251. Processor;

[0040] 251a. Interactive module;

[0041] 251b, Control Module;

[0042] 251c, Alarm Module;

[0043] 251d, Display module;

[0044] 252. Display screen;

[0045] 253. Memory.

[0046] 260. OBD interface;

[0047] 261. Interface terminals;

[0048] 262. Input terminals;

[0049] 263. Terminal blocks;

[0050] 270. Second bus. Detailed Implementation

[0051] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0052] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.

[0053] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0054] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0055] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0056] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0057] like Figure 1 The vehicle data management system shown includes a vehicle and a server. The vehicle includes a main unit and a communication terminal. The communication terminal can be detachably installed on the main unit, and can wirelessly communicate with the server to exchange data.

[0058] The vehicle body refers to the main functional parts of the vehicle, which may include the chassis, frame, engine, power system, cockpit, etc. In this application, it can be understood as the part of the vehicle excluding the communication terminal.

[0059] As a preferred option, the vehicles are engineering vehicles, such as underground scrapers, rock drilling rigs, and blasting hole drilling rigs.

[0060] The wireless communication between the communication terminal and the server can be 4G, 5G, WiFi, or other wireless communication technologies.

[0061] The server can be a standalone server or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. The communication terminal is detachably installed on the engineering vehicle so that the vehicle still stores vehicle identification information when the communication terminal is removed.

[0062] This invention establishes a wireless communication connection between engineering vehicles and a server to obtain the identification information of engineering vehicles, thereby meeting the monitoring needs of the monitoring system for engineering vehicles.

[0063] like Figure 2 As shown, the vehicle of this application also includes: an ECU device, a first bus, and a display device. The display device, communication terminal, and ECU device are all connected to the first bus. As a preferred embodiment, the first bus can be a J1939 bus.

[0064] like Figure 3 As shown, the display device of this application includes, from a hardware perspective, a processor, a display screen, and a memory. Thus, the display device enables it to perform functions such as control, verification, judgment, and storage.

[0065] The processor is mainly used for control, judgment, and verification functions. The control function is mainly used to write vehicle identification information to the communication terminal; the display screen is mainly used for human-machine interaction; and the memory is mainly used to store vehicle codes.

[0066] Specifically, the processor communicates with the display screen and memory to enable human-machine interaction between the display device and the user, while simultaneously presenting vehicle status information to the user. In some embodiments, the processor may optionally consist of two processor chips with processing capabilities. The specific processor chips may be ARM11 or ARM136. ARM11 is a 32-bit RISC microprocessor architecture and processor core series. Due to its advantages such as low power consumption and low cost, ARM11 is widely used in various embedded devices, such as set-top boxes, vehicle terminals, and industrial control equipment. ARM1136 is a processor in the ARM11 series. It inherits and develops the characteristics of the ARM11 series, and its low power consumption and high performance make it very suitable for embedded devices such as vehicle systems and industrial control systems.

[0067] like Figure 4 As shown, the display device includes at least a control module, a display module, an interaction module, and an alarm module. The control module is communicatively connected to the display module, interaction module, and alarm module. The control module processes and stores data exchanged with the ECU device and / or the communication terminal. The display module interacts with the control module to display the vehicle serial number generated by the control module. The interaction module allows the user to operate the display device for manual verification; the alarm module outputs an alarm signal when the verification module fails.

[0068] like Figure 5 As shown, an OBD interface generally includes: interface terminals, input terminals, and wiring terminals.

[0069] Specifically, the OBD interface is used to output vehicle detection data during vehicle testing; the ECU device is used to detect and / or store the vehicle detection data; a first bus is connected to the terminals of the OBD interface and the ECU device respectively to enable data transmission between the input terminals of the OBD interface and the ECU device; the display device includes a control module for checking whether the OBD interface has malfunctioned and a display module for displaying information on whether the OBD interface has malfunctioned; a second bus is connected to the interface terminals of the OBD interface and the control module respectively to enable data transmission between the interface terminals of the OBD interface and the control module; wherein, the control module is configured to interact with the ECU device through the first bus and the second bus respectively to determine whether the terminals of the OBD interface and the interface terminals have malfunctioned.

[0070] As the standard interface for vehicle testing and diagnostics, the OBD interface's hardware design adheres to relevant OBD standards and specifications. This ensures compatibility between the OBD interface and various testing equipment and vehicle systems. The OBD interface's input terminals use standard connectors, simplifying connections to data acquisition devices such as sensors. The interface terminals also use standard connectors, simplifying connections to external devices such as diagnostic tools and improving work efficiency. The OBD interface acquires data from the ECU and various sensors through its input terminals and outputs this data to external diagnostic equipment through its interface terminals. This efficient acquisition and transmission of vehicle testing data is crucial for the normal operation of the OBD interface. The OBD interface's wiring terminals are used to connect to the ECU or data bus, providing a channel for data acquisition and transmission. As a vital interface device in vehicle testing and diagnostic systems, the performance of the OBD interface affects the overall system's efficiency and accuracy. Monitoring the OBD interface's operating status is essential to ensuring its proper functioning. The input terminals, interface terminals, and wiring terminals of the OBD interface are connected via internal wiring. This clear internal connection structure facilitates efficient data transmission within the OBD interface.

[0071] like Figure 6 As shown, the method for automatically testing the on-board emissions diagnostic interface includes the following steps:

[0072] S301: The control module determines whether it can obtain data from the ECU device via the first bus; if so, the control module reads the model of the ECU device.

[0073] S302: The control module determines whether the model of the ECU device can be obtained through the first bus; if so, the control module reads the CVN code of the ECU device; otherwise, the display module displays the terminal fault information of the corresponding OBD interface.

[0074] S303: The control module determines whether the CVN code of the ECU device can be obtained through the first bus; if so, the control module obtains the CVN code of the ECU device through the second bus; otherwise, the display module displays the terminal fault information of the corresponding OBD interface.

[0075] S304: The control module determines whether the CVN code of the ECU device can be obtained through the second bus; if so, the display module displays information indicating that the interface terminal of the corresponding OBD interface is normal; otherwise, the display module displays information indicating that the interface terminal of the corresponding OBD interface is faulty.

[0076] Employing a bus connection, the control module acts as the core, making judgments and controlling the display module to show information. The judgment process escalates from basic data acquisition to CVN code comparison, enabling multi-level and accurate assessment of the OBD interface's operational status. This improves the accuracy of the judgment. The method for determining whether the OBD interface is functioning correctly, through a progressively escalating judgment process, can accurately and efficiently determine the operational status of both the OBD interface input terminals and interface terminals, achieving dual monitoring of the OBD interface. It boasts a high degree of automation, versatility, and reliability, making it a crucial means of ensuring the normal operation of the OBD interface.

[0077] The ECU (Emissions Control Unit) transmits emission and status data via the first bus. The communication terminal acquires this data and transmits it to the regulatory platform via a wireless network for oversight. The display device also communicates with the ECU via the first bus and can acquire engine emission and status data. The OBD interface can also read emission data from the ECU via the first bus. The CVN code is one type of emission data; if the CVN code can be read, other emission data can be obtained. If regulatory authorities cannot obtain engine emission data via the OBD interface using external testing equipment, the entire vehicle is deemed unqualified.

[0078] like Figure 7 As shown, the specific steps of the method for automatically testing the on-board emission diagnostic interface include:

[0079] S311: The control module cyclically checks whether it can read the data of the engine ECU device through the second bus. If it detects, it enters S312. If it cannot detect, it sends the fault information of the OBD interface terminal to the display module. After completing the repair, it cyclically checks the data of the ECU device.

[0080] S312: When ECU device data is detected, the control device stops the loop detection and sends an operation command via the first bus to read the engine ECU device model. Based on this model, the engine emission data operation command set category is determined. The command set is the set of commands used to obtain engine emission data. For example, if the engine ECU model is EMR5, the command set is ISO27145; if the engine ECU model is EMR4, the command set is ISO15031. If the ECU device model is obtained, proceed to S313; if the engine model cannot be obtained, send a terminal fault information to the display module to remind the user to perform maintenance.

[0081] S313: When the control module obtains the model number of the ECU device through the first bus, it sends an instruction to obtain the CVN code of the ECU device through the first bus and stores it in the display module; if the CVN code is obtained, it proceeds to S314; if it cannot obtain the CVN code, it sends a terminal fault information to the display module to remind the user to repair it.

[0082] S314: When the control module obtains the CVN code through the first bus, the control module sends a command to obtain the CVN code through the second bus; if obtained, proceed to S315; if it cannot be obtained, send an interface terminal fault information to the display module to remind the user to repair.

[0083] S315: When the control module obtains the CVN code through the second bus, it compares the CVN codes obtained through the first bus and the second bus respectively. When the two are consistent, it outputs a normal OBD interface information to the display device. When the two are inconsistent, it outputs a fault information for the OBD interface terminal to the user.

[0084] This logic for determining the normal operation of the OBD interface employs a continuously upgraded judgment method to accurately determine the working status of the OBD interface. It boasts a high degree of automation and ease of use, making it a crucial means of ensuring the normal operation of the OBD interface. This method relies heavily on the CVN code, accurately and effectively determining whether data transmission between the OBD interface and the ECU device is normal, thereby judging the working status of the OBD interface. It demonstrates strong accuracy and practicality.

[0085] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by the processing device 801, it performs the functions defined in the methods of some embodiments of this disclosure.

[0086] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function.

[0087] It should also be noted that in some alternative implementations, the functions marked in the box may occur in a different order than those marked in the attached figures.

[0088] For example, two consecutively represented blocks can actually be executed in substantially parallel order, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, as well as combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified functions or operations, or using a combination of dedicated hardware and computer instructions.

[0089] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.

Claims

1. A vehicle interface inspection system, comprising: The OBD interface is used to output vehicle inspection data when the vehicle is being inspected. ECU unit, used to detect and / or store vehicle detection data; The first bus is connected to the terminals of the OBD interface and the ECU device respectively to enable data transmission between the input terminals of the OBD interface and the ECU device; Its features are: The vehicle interface inspection system also includes: The display device includes a control module for detecting whether the OBD interface has malfunctioned and a display module for displaying information about whether the OBD interface has malfunctioned. The second bus is connected to the interface terminal of the OBD interface and the control device respectively, so that data transmission can be established between the interface terminal of the OBD interface and the testing device. The control module is configured to interact with the ECU device via the first bus and the second bus respectively to determine whether the wiring terminals and interface terminals of the OBD interface are faulty. The control module determines whether it can obtain data from the ECU device via the first bus; if so, the control module reads the model of the ECU device. The control module determines whether the model of the ECU device can be obtained through the first bus; if so, the control module reads the CVN code of the ECU device; otherwise, the display module displays the terminal fault information of the corresponding OBD interface. The control module determines whether the CVN code of the ECU device can be obtained through the first bus; if so, the control module obtains the CVN code of the ECU device through the second bus; otherwise, the display module displays the terminal fault information of the corresponding OBD interface.

2. The vehicle interface inspection system according to claim 1, characterized in that: The control module determines whether the CVN code of the ECU device can be obtained through the second bus; if so, the display module displays information indicating that the interface terminal of the corresponding OBD interface is normal; otherwise, the display module displays information indicating that the interface terminal of the corresponding OBD interface is faulty.

3. The vehicle interface inspection system according to any one of claims 1 or 2, characterized in that: The first bus and the second bus are two different types of buses.

4. The vehicle interface inspection system according to claim 3, characterized in that: The first bus is the J1939 bus, and the second bus is the CAN bus.

5. The vehicle interface inspection system according to claim 4, characterized in that: The vehicle detection data output by the OBD interface includes, but is not limited to, the vehicle's engine emission data.

6. The vehicle interface inspection system according to claim 4, characterized in that: The vehicle interface inspection system also includes: A communication terminal, used to enable wireless communication between the ECU device and external devices; The communication terminal is connected to the display device, ECU device and OBD interface via the first bus; the ECU device interacts with the server to exchange vehicle detection data through the communication terminal.

7. A vehicle interface inspection method, wherein the method is performed by a vehicle interface inspection system; The vehicle interface inspection system includes: The OBD interface is used to output vehicle inspection data when the vehicle is being inspected. ECU unit, used to detect and / or store vehicle detection data; The first bus is connected to the terminals of the OBD interface and the ECU device respectively to enable data transmission between the input terminals of the OBD interface and the ECU device; Its features are: The vehicle interface inspection system also includes: The display device includes a control module for detecting whether the OBD interface has malfunctioned and a display module for displaying information about whether the OBD interface has malfunctioned. The second bus is connected to the interface terminal of the OBD interface and the control device respectively, so that data transmission can be established between the interface terminal of the OBD interface and the testing device. The control module is configured to interact with the ECU device via a first bus and a second bus, respectively. The control module determines whether it can obtain data from the ECU device via the first bus; if so, the control module reads the model of the ECU device. Vehicle interface inspection methods include: The control module determines whether it can obtain data from the ECU device via the first bus; if so, the control module reads the model of the ECU device. The control module determines whether the model of the ECU device can be obtained through the first bus; if so, the control module reads the CVN code of the ECU device; otherwise, the display module displays the terminal fault information of the corresponding OBD interface. The control module determines whether the CVN code of the ECU device can be obtained through the first bus; if so, the control module obtains the CVN code of the ECU device through the second bus; otherwise, the display module displays the terminal fault information of the corresponding OBD interface. The control module determines whether the CVN code of the ECU device can be obtained through the second bus; if so, the display module displays information indicating that the interface terminal of the corresponding OBD interface is normal; otherwise, the display module displays information indicating that the interface terminal of the corresponding OBD interface is faulty.

Images