Hybrid vehicle obd system automatic test method, device and vehicle

Abstract

The application discloses a kind of hybrid vehicle OBD system automatic test method, device and vehicle, including setting preset test execution order and preset test result;According to preset test execution order, relevant OBD fault is injected to OBD system;According to preset test execution order, the real situation of various test conditions and faults is simulated to OBD system;According to preset test execution order, corresponding diagnostic request is sent to OBD system;OBD diagnostic information fed back to OBD system is collected and analyzed to obtain actual test result;Actual test result is compared and analyzed with preset test result, whether test passes is judged.The overall detection of hybrid vehicle OBD system is realized, the efficiency and accuracy of fault detection are improved, maintenance cost is reduced, and user experience is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automobiles, in particular to a hybrid vehicle OBD system automatic testing method, device and vehicle. BACKGROUND

[0002] With the enhancement of human environmental protection consciousness and the increasing of global automobile ownership year by year, the pollution of automobile emissions has attracted more and more attention from the world, and the OBD (On-Bard Diagnostic) system has emerged as the times require. With the continuous improvement of the electrification degree of vehicles, the existing emission and measurement standards have put forward more detailed monitoring requirements for electronic power system components / systems, especially extended to hybrid vehicle components. The hybrid vehicle OBD system increases the electric energy storage system, the thermal management system, the drive motor and the generator, etc., and the test process is more complex. The OBD diagnostic test method of the traditional vehicle for the engine controller (EMS) cannot completely cover the requirements of the hybrid vehicle OBD system. SUMMARY

[0003] The present application aims to at least solve one of the technical problems existing in the prior art. To this end, the present application provides a hybrid vehicle OBD system automatic testing method, which can realize comprehensive detection of the hybrid vehicle OBD system and improve the efficiency and accuracy of fault detection.

[0004] According to the hybrid vehicle OBD system automatic testing method of the first aspect of the embodiment of the present application, the method comprises:

[0005] Setting a preset test execution sequence and a preset test result;

[0006] According to the preset test execution sequence, injecting relevant OBD faults into the OBD system;

[0007] According to the preset test execution sequence, simulating various test conditions and real situations of faults for the OBD system;

[0008] According to the preset test execution sequence, sending corresponding diagnostic requests to the OBD system;

[0009] Collecting and analyzing the OBD diagnostic information fed back by the OBD system to obtain an actual test result;

[0010] Comparing and analyzing the actual test result with the preset test result to determine whether the test is passed.

[0011] According to the hybrid vehicle OBD system automatic testing method of the embodiment of the present application, at least the following beneficial effects are achieved:

[0012] The application injects relevant OBD faults into the OBD system according to a preset test execution sequence, simulates various test conditions and real situations of faults to the OBD system, then sends corresponding diagnostic requests to the OBD system according to the preset test execution sequence, collects and analyzes the OBD diagnostic information fed back by the OBD system to obtain actual test results, compares the actual test results with preset test results, and judges whether the test is passed, so as to realize comprehensive detection of the OBD system of the hybrid vehicle, improve the efficiency and accuracy of fault detection, reduce maintenance cost, and improve user experience.

[0013] According to some embodiments of the application, the injection of the relevant OBD faults into the OBD system according to the preset test execution sequence comprises:

[0014] Injecting the relevant OBD faults of IO, assembly components, and CAN communication into the OBD system.

[0015] According to some embodiments of the application, the injection of the relevant OBD faults into the OBD system according to the preset test execution sequence comprises:

[0016] Setting the relevant OBD faults to include accelerator pedal faults, brake pedal faults, proportional pressure valve faults, normal controller self faults, communication faults with the motor control system, communication faults with the battery management system, water pump, fan body faults and control pin circuit faults, and OBD faults related to the motor system and the battery system.

[0017] According to some embodiments of the application, the simulation of various test conditions and real situations of faults to the OBD system according to the preset test execution sequence comprises:

[0018] Providing the OBD system with driver operation, key assembly component state feedback, IO interface with the OBD system, and CAN communication interface.

[0019] According to some embodiments of the application, the simulation of various test conditions and real situations of faults to the OBD system according to the preset test execution sequence comprises:

[0020] Performing IG power-on, IG power-off, CAN wake-up, hibernation, and engine warm-up operations to realize test conditions of multiple driving cycles;

[0021] According to the relevant OBD faults, setting the OBD faults sent by the motor controller and the battery control system to the vehicle control unit, and manufacturing real fault states of the IO interface and the CAN communication of the OBD system.

[0022] According to some embodiments of the present application, the sending of the diagnostic request to the OBD system according to the preset test execution sequence comprises:

[0023] The setting of the diagnostic request comprises reading data stream, reading frozen frame, reading confirmed fault code, reading permanent fault code, reading pending fault code, and reading vehicle information.

[0024] According to some embodiments of the present application, the OBD diagnostic information fed back by the OBD system is collected and analyzed to obtain actual test results, which comprises:

[0025] The number of driving cycles and the number of warm-up cycles are collected in real time.

[0026] The OBD diagnostic information fed back by the OBD system comprises pending fault code, confirmed fault code, permanent fault code, data stream, frozen frame, and MIL lamp flag bit.

[0027] According to the hybrid vehicle OBD system automatic test device of the second aspect of the embodiments of the present application, which comprises:

[0028] The test sequence module is configured to set a preset test execution sequence and a preset test result.

[0029] The test environment module is configured to simulate various test conditions and real situations of faults for the OBD system according to the preset test execution sequence.

[0030] The fault injection module is configured to inject relevant OBD faults into the OBD system according to the preset test execution sequence.

[0031] The diagnostic request module is configured to send a corresponding diagnostic request to the OBD system according to the preset test execution sequence.

[0032] The data collection module is configured to collect and analyze the OBD diagnostic information fed back by the OBD system to obtain actual test results.

[0033] The data analysis module is configured to compare and analyze the actual test results with the preset test results to determine whether the test is passed.

[0034] According to the vehicle of the third aspect of the embodiments of the present application, the hybrid vehicle OBD system automatic test device is included.

[0035] According to the computer readable storage medium of the fourth aspect of the embodiments of the present application, the computer readable storage medium stores computer executable instructions, and the computer executable instructions are configured to make the computer execute the hybrid vehicle OBD system automatic test method.

[0036] Other features and advantages of the present application will be set forth in the description that follows, and in part will be apparent from the description, or can be learned by practice of the application. BRIEF DESCRIPTION OF DRAWINGS

[0037] The application will be further described below with reference to the drawings and examples, wherein:

[0038] Figure 1 A schematic diagram of the hybrid system control scheme of the present application;

[0039] Figure 2 A schematic diagram of the hybrid system OBD architecture of the present application;

[0040] Figure 3 A flow chart of the steps of the hybrid vehicle OBD system automatic testing method of the present application;

[0041] Figure 4 A schematic diagram of the hybrid vehicle OBD system automatic testing device of the present application;

[0042] Figure 5 A detailed testing flow chart of the hybrid vehicle OBD system automatic testing method of the present application. DETAILED DESCRIPTION

[0043] Embodiments of the present application are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar notations represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by reference to the drawings are exemplary only, and are used only for the purpose of explaining the present application, and should not be understood as limiting the present application.

[0044] In the description of the present application, it should be understood that the orientation description, such as the upper, lower, etc. orientation or position relationship is based on the orientation or position relationship shown in the drawings, and is only for the purpose of facilitating the description of the present application and simplifying the description, and is not intended to indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore should not be understood as limiting the present application.

[0045] In the description of the present application, the plural refers to two or more. If there is a description of the first, second, it is only for the purpose of distinguishing technical features, and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated or the sequence of technical features indicated.

[0046] In the description of the present application, unless otherwise explicitly limited, the words such as setting, installing, connecting, etc. should be broadly understood, and the person skilled in the art can reasonably determine the specific meaning of the above words in the present application in combination with the specific content of the technical solution.

[0047] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described below are some embodiments of the present invention, not all embodiments.

[0048] Existing OBD diagnostic technologies for hybrid vehicles either focus on OBD diagnostic testing methods for engine controllers, automated testing processes, or manual testing methods for hybrid vehicle OBD systems. Previous OBD diagnostic testing methods for engine controllers can no longer be directly applied, and a complete set of automated testing methods and devices for hybrid vehicle OBD systems needs to be established.

[0049] like Figure 1 The hybrid power system control scheme illustrated in this embodiment of the invention uses a vehicle controller 800, which acts as the brain of the hybrid vehicle. It identifies the states of the accelerator pedal, brake pedal, gear position, clutch, etc., and receives relevant component information and vehicle speed signals from controllers such as the engine controller 110, drive motor controller 310, generator controller 210, and battery management system 410 via the CAN bus. It calculates the driver's required torque and sends control commands to relevant controllers via the CAN bus to coordinate the orderly operation of all power components (engine, clutch, drive motor, generator, and power battery), achieving hybrid drive and regenerative braking functions. Furthermore, the vehicle controller is responsible for controlling the hybrid vehicle's thermal management system. It identifies the water temperature based on the water temperature sensor and controls the fan and water pump according to a predetermined strategy to ensure the reasonable operating temperature of the engine, drive motor, generator, and power battery.

[0050] like Figure 2The hybrid power system OBD architecture targeted by the embodiment of the application shown, since the engine controller 110 monitors more engine emission related indicators than hybrid specific components, in order to save network resources, the engine controller 110 is selected as the main OBD controller, the vehicle controller 800 and the vehicle body electronic stability control system are selected as the first level OBD controller, and the drive motor controller 310, the generator controller 210 and the battery management system 410 are selected as the second level OBD controller. The engine controller 110, the vehicle controller 800 and the vehicle body electronic stability control system can all communicate with the diagnostic tool, the vehicle controller 800 and the vehicle body electronic stability control system support part of the diagnostic service according to the data interaction needs, and the engine controller 110 is responsible for implementing all diagnostic services and arbitration of the MIL state. The drive motor controller 310, the generator controller 210 and the battery management system 410 as the second level OBD controller of the vehicle controller 800 do not need to directly interact with the diagnostic tool and do not need to support the OBD diagnostic service, only need to have the OBD fault identification function, and send the related information to the vehicle controller 800 through the CAN bus, and the vehicle controller 800 implements the hybrid power related OBD fault management and the diagnostic tool communication function.

[0051] As shown in Figure 3 The hybrid power vehicle OBD system automatic test method of the embodiment of the application includes but is not limited to the following steps:

[0052] Step S100: set the preset test execution sequence and the preset test result;

[0053] Step S200: according to the preset test execution sequence, inject related OBD faults into the OBD system;

[0054] Step S300: according to the preset test execution sequence, simulate various test conditions and the real situation of faults for the OBD system;

[0055] Step S400: according to the preset test execution sequence, send the corresponding diagnostic request to the OBD system;

[0056] Step S500: collect and analyze the OBD diagnostic information fed back by the OBD system to obtain the actual test result;

[0057] Step S600: compare and analyze the actual test result with the preset test result to determine whether the test is passed.

[0058] The application injects relevant OBD faults into the OBD system according to a preset test execution sequence, simulates various test conditions and real situations of faults to the OBD system, then sends corresponding diagnostic requests to the OBD system according to the preset test execution sequence, collects and analyzes the OBD diagnostic information fed back by the OBD system to obtain actual test results, compares the actual test results with preset test results, judges whether the test passes, thereby realizing comprehensive detection of the OBD system of the hybrid vehicle, improving the efficiency and accuracy of fault detection, reducing maintenance costs, and improving user experience.

[0059] In addition, as Figure 4 shown, the application also provides an automatic test device for an OBD system of a hybrid vehicle, which comprises a test sequence module, a test environment module, a fault injection module, a diagnostic request module, a data collection module and a data analysis module, the test sequence module is used for setting a preset test execution sequence and a preset test result; the test environment module is used for simulating various test conditions and real situations of faults to the OBD system according to the preset test execution sequence; the fault injection module is used for injecting relevant OBD faults into the OBD system according to the preset test execution sequence; the diagnostic request module is used for sending corresponding diagnostic requests to the OBD system according to the preset test execution sequence; the data collection module is used for collecting and analyzing the OBD diagnostic information fed back by the OBD system to obtain actual test results; and the data analysis module is used for comparing the actual test results with the preset test results and judging whether the test passes.

[0060] The following will describe each step of the automatic test method for the OBD system of the hybrid vehicle in combination with the automatic test device for the OBD system of the hybrid vehicle.

[0061] The measured object of the automatic test device for the OBD system of the hybrid vehicle includes but is not limited to the OBD system of the hybrid vehicle in this document, including the vehicle controller, the engine controller and the body electronic stability control system. In other embodiments, for other OBD systems, only the test sequence module and the test environment module need to be optimized according to the OBD requirements to meet the automatic test function.

[0062] The test sequence module of the embodiment of the application is mainly responsible for defining the sequence of test execution, ensuring that the test is performed according to the established logic and sequence, avoiding confusion in test execution, and playing a core coordination and management role in the OBD system automatic test process. The test sequence module can dispatch the test environment module, the fault injection module, the diagnostic request module, the data collection module and the data analysis module to complete the key steps of automatic test according to the established sequence. In addition, the test sequence module is also responsible for clearly defining the expected test results to facilitate data analysis by the data analysis module.

[0063] The test environment module of the embodiment of the present application is mainly responsible for providing a test environment, including providing driver operation, key assembly component (drive motor, generator, high-voltage battery) state feedback, IO interface with the object under test, CAN communication interface, etc. The test environment module can perform IG power-on, IG power-off, CAN wake-up, hibernation, engine warm-up, etc. according to the requirements of the test sequence module to realize the test conditions of multiple driving cycles, and can also set the OBD faults sent by the motor controller and the battery management system to the vehicle controller according to the request of the fault injection module, and the real fault state of the IO interface and CAN communication of the object under test, wherein the motor controller includes a drive motor controller 310 and a generator controller 210.

[0064] The fault injection module is mainly responsible for injecting IO, assembly component, CAN communication, etc. according to the requirements of the test sequence module, and simulating the real situation of various faults through the test environment module, which can effectively detect the fault identification ability and response ability of the OBD system. The related OBD faults mainly include but are not limited to accelerator pedal faults (sensor supply voltage exceeds upper limit, sensor supply voltage exceeds lower limit, sensor voltage exceeds upper limit, sensor voltage exceeds lower limit), brake pedal faults (brake pedal differential fault, brake failure fault), proportional pressure valve faults (proportional pressure valve control pin pair short circuit, short circuit to ground, open circuit), vehicle controller itself faults (over temperature, power supply fault), communication faults with the motor controller, communication faults with the battery management system, water pump, fan body faults and control pin circuit faults, OBD faults related to the motor system and the battery system, etc.

[0065] The diagnostic request module of the embodiment of the present application is mainly responsible for sending corresponding diagnostic requests to the OBD system according to the requirements of the test sequence module, mainly including but not limited to reading data stream, reading frozen frame, reading confirmation fault code, reading permanent fault code, reading pending fault code, reading vehicle information, etc.

[0066] The data acquisition module of the embodiment of the present application is mainly responsible for real-time acquisition of the number of driving cycles, the number of warm-up cycles, OBD diagnostic information (pending fault code, confirmation fault code, permanent fault code, data stream, frozen frame, MIL lamp flag, etc.) fed back by the OBD system, and parsing into the required form and sending to the data analysis module.

[0067] The data analysis module of the embodiment of the present application is mainly responsible for comparing and analyzing the expected test results of the test sequence module with the data of the data acquisition module, then judging whether the test is passed, and finally outputting a test report.

[0068] As shown in Figure 5 the specific process of testing the functions of fault storage, data stream, frozen frame, vehicle information, and MIL lamp lighting of the hybrid vehicle OBD system is as follows:

[0069] Step S1 : IG ON or message wake up related controller (1st drive cycle), it can be understood that the first time to start the vehicle;

[0070] Step S2: read vehicle information and data stream, determine whether the vehicle VIN, CVN, data stream is consistent with the preset information, if yes, execute step S3, otherwise, the test fails;

[0071] Step S3: inject OBD related faults;

[0072] Step S4: read pending faults, confirm faults, permanent faults, frozen frames, MIL lamp status, determine whether there are pending faults, no confirm faults, no permanent faults, stored frozen frames and no MIL lamp, if yes, execute step S5, otherwise, the test fails;

[0073] Step S5: control related controller sleep and wake up again (2nd drive cycle) to maintain faults;

[0074] Step S6: read pending faults, confirm faults, permanent faults, frozen frames, MIL lamp status, determine whether there are pending faults, confirm faults, no permanent faults, update frozen frames and MIL lamp, if yes, execute step S7, otherwise, the test fails;

[0075] Step S7: control related controller sleep and wake up again (3rd drive cycle) to maintain faults;

[0076] Step S8: read pending faults, confirm faults, permanent faults, frozen frames, MIL lamp status, determine whether there are no pending faults, confirm faults, permanent faults, frozen frames are not updated and MIL lamp, if yes, execute step S9, otherwise, the test fails;

[0077] Step S9: control related controller sleep and clear OBD related faults;

[0078] Step S10: wake up sleep related controller again, at this time, re-count the drive cycle, 1-3 drive cycles;

[0079] Step S11 : read pending faults, confirm faults, permanent faults, frozen frames, MIL lamp status, determine whether there are no pending faults, confirm faults, permanent faults, frozen frames are not updated and MIL lamp, if yes, execute step S12, otherwise, the test fails;

[0080] Step S12: control related controller sleep and wake up again (4th drive cycle);

[0081] Step S13: reading the status of pending faults, confirmed faults, permanent faults, frozen frames, MIL lamp, judging whether there is no pending fault, confirmed fault, permanent fault, frozen frame not updating and MIL lamp, if yes, executing step S14, otherwise, the test fails;

[0082] Step S14: controlling the related controller to sleep and then wake up again (41st driving cycle);

[0083] Step S15: reading the status of pending faults, confirmed faults, permanent faults, frozen frames, MIL lamp, judging whether there is no pending fault, confirmed fault, permanent fault, frozen frame and MIL lamp, if yes, the test passes, otherwise, the test fails.

[0084] The present application can comprehensively test the functions of fault storage, data flow, frozen frame, vehicle information, MIL lamp lighting and the like of the OBD system of the hybrid vehicle, and effectively ensure the correctness of the OBD system. In addition, the automatic test method of the present application further includes the test of the clearing function of the pending faults, confirmed faults and permanent faults, the test of the storage / update of the frozen frame when multiple faults occur, the test of the test result of the requested oxygen sensor monitoring, the test of the test result of the requested specified monitoring system of the vehicle monitoring, and the like, which are relatively simple and will not be described one by one.

[0085] The automatic test method and device of the embodiment of the present application can comprehensively test the OBD system of the hybrid vehicle, improve the efficiency and accuracy of fault detection, reduce the maintenance cost and improve the user experience.

[0086] The present application further provides a vehicle comprising the automatic test device of the OBD system of the hybrid vehicle, and it can be understood that the contents in the above automatic test device of the OBD system of the hybrid vehicle are applicable to the vehicle embodiment, the vehicle embodiment specifically realizes the same functions as the automatic test device of the OBD system of the hybrid vehicle, and achieves the same beneficial effects as the automatic test device of the OBD system of the hybrid vehicle.

[0087] According to the computer readable storage medium of the embodiment of the present application, a computer program is stored thereon, and the program is executed by a processor to realize the automatic test method of the OBD system of the hybrid vehicle.

[0088] The computer readable storage medium of the embodiments of the present application can adopt any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples (non-exhaustive list) of the computer readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiments of the present application, the computer readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus or device.

[0089] The computer readable signal medium can include a data signal propagated in baseband or propagated as a carrier wave in a propagated data signal, in which the computer readable program code is contained. Such propagated data signal can take many forms, including but not limited to electro-magnetic, optical or any suitable combination thereof. The computer readable signal medium can also be any computer readable medium that is not a storage medium and that can communicate, propagate or transport program for use by or in connection with an instruction execution system, apparatus or device.

[0090] The program code contained in the computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire line, optical cable, RF, etc., or any suitable combination thereof.

[0091] It should be understood that parts of the present application can be implemented in hardware, software, firmware or a combination thereof. In the above described embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and as in another embodiment, any one or a combination of the following technologies known in the art can be used: discrete logic circuitry having logic gates for implementing logic functions on data signals, application specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field programmable gate arrays (FPGA), etc.

[0092] In the description of the specification, the description of the terms "one embodiment", "some embodiments", "exemplary embodiment", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the specification, the exemplary description of the above terms does not necessarily mean the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0093] The embodiments of the present application are described above in detail with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the spirit of the present application.

Claims

1. A hybrid vehicle OBD system automatic test method characterized by, The method comprises the following steps: S100: setting a preset test execution sequence and a preset test result; S200: injecting relevant OBD faults into an OBD system according to the preset test execution sequence; S300: simulating various test conditions and real situations of faults for the OBD system according to the preset test execution sequence; S400: sending corresponding diagnostic requests to the OBD system according to the preset test execution sequence; S500: collecting and analyzing OBD diagnostic information fed back by the OBD system to obtain an actual test result; S600: comparing and analyzing the actual test result with the preset test result to determine whether the test is passed; The step S200 further comprises: injecting IO, assembly component and CAN communication related OBD faults into the OBD system; setting the relevant OBD faults to include accelerator pedal faults, brake pedal faults, proportional pressure valve faults, normal controller self faults, motor control system communication faults, battery management system communication faults, water pump, fan body faults and control pin circuit faults, and OBD faults related to the motor system and the battery system; The step S300 further comprises: providing driver operation, key assembly component state feedback, IO interface and CAN communication interface of the OBD system for the OBD system; performing IG power-on, IG power-off, CAN wake-up, hibernation and engine warm-up operations to realize test conditions of multiple driving cycles; sending OBD faults from the motor controller and the battery control system to the vehicle controller according to the relevant OBD faults, and manufacturing real fault states of the IO interface and the CAN communication of the OBD system; The step S400 further comprises: setting the diagnostic requests to include reading data streams, reading frozen frames, reading confirmation fault codes, reading permanent fault codes, reading pending fault codes and reading vehicle information; The step S500 further comprises: collecting the number of driving cycles and the number of warm-up cycles in real time; setting the OBD diagnostic information fed back by the OBD system to include pending fault codes, confirmation fault codes, permanent fault codes, data streams, frozen frames and MIL lamp flag bits.

2. A hybrid vehicle OBD system automatic testing device, characterized by, The automatic test device is suitable for the automatic test method of the hybrid vehicle OBD system, and comprises: a test sequence module for setting a preset test execution sequence and a preset test result; a test environment module for simulating various test conditions and real situations of faults for the OBD system according to the preset test execution sequence; a fault injection module for injecting relevant OBD faults into an OBD system according to the preset test execution sequence; a diagnostic request module for sending corresponding diagnostic requests to the OBD system according to the preset test execution sequence; a data collection module for collecting and analyzing OBD diagnostic information fed back by the OBD system to obtain an actual test result; a data analysis module for comparing and analyzing the actual test result with the preset test result to determine whether the test is passed.

3. A vehicle characterized by comprising: The application relates to a hybrid vehicle OBD system automatic testing device.

4. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer executable instructions for causing a computer to execute the hybrid vehicle OBD system automatic testing method.

Images