CN116701177A

CN116701177A - Method and device for testing interface pins of vehicle-mounted diagnostic system and electronic equipment

Info

Publication number: CN116701177A
Application number: CN202310479646.1A
Authority: CN
Inventors: 葛张成; 刘海彬; 魏英英
Original assignee: Great Wall Motor Co Ltd
Current assignee: Great Wall Motor Co Ltd
Priority date: 2023-04-28
Filing date: 2023-04-28
Publication date: 2023-09-05

Abstract

The application provides a method, a device and electronic equipment for testing interface pins of a vehicle-mounted diagnosis system, wherein the method is applied to the field of vehicles and comprises the following steps: acquiring a standard protocol corresponding to a target stitch to be tested in a vehicle-mounted diagnostic system interface, wherein the standard protocol is used for indicating a target function which can be realized by the target stitch, and the target stitch is a stitch with completed function configuration; testing the target pins based on a standard protocol; and determining a test result of the target stitch, wherein the test result is used for indicating whether the configured function of the target stitch is matched with the target function. The method can find out the problem of error configuration of the functions of the pins of the OBD interface in time, and ensures the accuracy of the configuration of the pins of the OBD interface.

Description

Method and device for testing interface pins of vehicle-mounted diagnostic system and electronic equipment

Technical Field

The present application relates to the field of vehicles, and more particularly, to a method, apparatus, and electronic device for testing interface pins of an on-board diagnostic system in the field of vehicles.

Background

At present, in the field of vehicles, in order to ensure the safety of the vehicles in the running process, testers can carry out fault diagnosis on the vehicles, and corresponding solutions are formulated according to the fault conditions of the vehicles.

In one possible implementation, during the diagnosis of a fault in the vehicle, the device may be connected to an OBD interface in the vehicle via an external On-board diagnostic system (On-Board Diagnostics, OBD) detection device. Further, the OBD detection device may obtain information data (e.g., vehicle speed, engine speed) of the vehicle operation and fault data (e.g., fault code) of the vehicle through the OBD interface.

In the above process, the OBD interface has 16 pins in total, and the OBD interface pins need to comply with standard protocols to realize corresponding functions.

In summary, how to detect whether the pin configuration of the OBD interface is correct is a problem to be solved.

Disclosure of Invention

The application provides a method, a device and electronic equipment for testing the interface pins of a vehicle-mounted diagnosis system, which can timely find the problem of error configuration of the functions of the OBD interface pins and ensure the accuracy of the configuration of the OBD interface pins.

In a first aspect, a method of testing an on-board diagnostic system interface pin is provided, the method comprising: acquiring a standard protocol corresponding to a target stitch to be tested in an interface of a vehicle-mounted diagnostic system, wherein the standard protocol is used for indicating a target function which can be realized by the target stitch, and the target stitch is a stitch with function configuration completed; testing the target pin based on the standard protocol; a test result of the target pin is determined, the test result being indicative of whether the configured function of the target pin matches the target function.

In the above solutions, the OBD interface typically comprises a plurality of pins, each of which may be given a different function. Wherein the functions of some pins are predefined target functions, and the target functions need to be realized by adhering to corresponding standard protocols and cannot be changed. After the configuration of the OBD interface in the vehicle is completed, in order to detect whether the functions of the OBD interface pins are configured correctly, the application provides a method for testing the OBD interface pins. Specifically, the target stitch can be tested through a standard protocol corresponding to the target stitch, and a test result in a test process is further obtained to judge whether the configured function of the target stitch is a target function. The above process can test and find out in time when the function of the OBD interface pin is not in accordance with the target function. The condition of wrong wiring of the OBD interface pins is avoided, and the accuracy of the application of the OBD in the vehicle is ensured.

With reference to the first aspect, in some possible implementations, the testing the target pin based on the standard protocol includes: determining preset test information corresponding to the standard protocol, wherein the preset test information is used for testing the configured function of the target pin; and sending the preset test information to the vehicle-mounted diagnosis system so as to test the target pin.

In the above technical solution, in the process of testing the target pins according to the standard protocol, the operation specifications of the target pins corresponding to different standard protocols are different. Therefore, the application can determine the preset test information corresponding to the standard protocol based on the standard protocol, and send the preset test information to the vehicle-mounted diagnosis system, and the effect of testing the target stitch is achieved through the response condition of the vehicle-mounted diagnosis system.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, before the determining a test result of the target pin, the method further includes: determining preset reply information corresponding to the preset test information; obtaining reply information corresponding to the preset test information sent by the vehicle-mounted diagnosis system; and the test result for determining the target pin comprises: determining a matching result of the reply information and the preset reply information; and determining the test result of the target pin according to the matching result.

In the above technical solution, the test information is understood as information sent to the on-board diagnostic system, and the sending and receiving are usually performed in pairs. Therefore, each standard protocol corresponds to the preset reply information in addition to the preset test information required in the test process. The application can also determine the preset reply information corresponding to the preset test information one by one according to the preset test information. Further, after the preset test information is sent to the vehicle-mounted diagnostic system, the reply information sent by the vehicle-mounted diagnostic system can be obtained. And comparing the reply information with preset reply information to determine a matching result of the reply information and the preset reply information. And finally, based on the matching result, obtaining the test result of the target stitch.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, the determining, according to the matching result, a test result of the target pin includes: under the condition that the reply information is matched with the preset reply information, determining that the configured function of the target stitch is matched with the target function; and under the condition that the reply information is not matched with the preset reply information, determining that the configured function of the target stitch is not matched with the target function.

In the above technical solution, the test result of the target pin may indicate whether the function configured by the target pin is the target function. Therefore, based on the matching result of the reply information and the preset reply information, the method and the device can directly determine whether the function configured by the target stitch is the target function or not. Specifically, if the reply information is matched with the preset reply information, the successful test of the target stitch according to the standard protocol is indicated, and the configured function of the target stitch is the target function; otherwise, the function configured by the target stitch is not the target function, and the function configuration of the target stitch is inaccurate. The method and the device for testing the target stitch determine whether the configured function of the target stitch is correct according to the matching of the preset reply information and the reply information, can ensure the accuracy of the testing process of the target stitch, and timely detect errors in the development process of the OBD interface.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, before the acquiring a standard protocol corresponding to a target pin to be tested in an on-vehicle diagnostic system interface, the method further includes: sending a stitch acquisition request to the vehicle-mounted diagnostic system, wherein the stitch acquisition request is used for requesting to acquire the identification of the target stitch; and the obtaining standard protocols corresponding to the target pins to be tested in the vehicle-mounted diagnosis system interface comprises the following steps: and responding to the identification of the target pin sent by the vehicle-mounted diagnosis system, and acquiring the standard protocol.

In the above technical solution, before acquiring the standard protocol of the target stitch, the present application may first send a stitch acquisition request to the vehicle-mounted diagnostic system to determine the identification of the target stitch. And further determining a standard protocol corresponding to the target pin based on the identification of the target pin with the configured function. The process can ensure the accuracy of the correspondence between the target stitch and the standard protocol, and provides a correct detection basis for the detection of the target stitch.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, the method further includes: and displaying a test progress display interface, wherein the test progress display interface is used for displaying a test result of the target pin so as to prompt a tester whether the configured function of the target pin is matched with the target function.

In the technical scheme, the application can also display the test progress display interface at the same time when detecting the target stitch. The test progress presentation interface may display a detailed page of the target pin during the process being tested. And after the test is completed, the test result is displayed on a test progress display interface so as to clearly remind the testers whether the target stitch passes the test. The process can enable a tester to quickly know the test result of the target stitch, and discover and solve the problem in time. And the OBD function caused by the configuration error of the target pin is prevented from being influenced.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, the method further includes: and under the condition that the test result indicates that the function of the target pin configured is not matched with the target function, sending the test result to terminal equipment of a tester to prompt the tester to process the function of the target pin configured according to the test result.

In the technical scheme, under the condition that the target pins do not accord with the corresponding standard protocol, in order to timely process the target pins with incorrect function configuration, the application can also push the test result to the terminal equipment of the tester so as to enable the tester to timely process the function of the configured target pins. The above process ensures that the effect of changing the configured function of the target stitch in time is ensured under the condition that the function configuration of the target stitch is not right, and the potential safety hazard of the vehicle caused by untimely treatment is avoided.

In summary, an OBD interface typically includes a plurality of pins, each of which may be assigned a different function. Wherein the functions of some pins are predefined target functions, and the target functions need to be realized by adhering to corresponding standard protocols and cannot be changed. After the configuration of the OBD interface in the vehicle is completed, in order to detect whether the functions of the OBD interface pins are configured correctly, the application provides a method for testing the OBD interface pins. Specifically, the target stitch can be tested through a standard protocol corresponding to the target stitch, and a test result in a test process is further obtained to judge whether the configured function of the target stitch is a target function. The above process can test and find out in time when the function of the OBD interface pin is not in accordance with the target function. The condition of wrong wiring of the OBD interface pins is avoided, and the accuracy of the application of the OBD in the vehicle is ensured.

In testing the target pins according to the standard protocol, the operating specifications of the target pins corresponding to different standard protocols are different. Therefore, the application can determine the preset test information corresponding to the standard protocol based on the standard protocol, and send the preset test information to the vehicle-mounted diagnosis system, and the effect of testing the target stitch is achieved through the response condition of the vehicle-mounted diagnosis system.

Test information is understood to be information sent to an on-board diagnostic system, the sending and receiving typically being in pairs. Therefore, each standard protocol corresponds to the preset reply information in addition to the preset test information required in the test process. The application can also determine the preset reply information corresponding to the preset test information one by one according to the preset test information. Further, after the preset test information is sent to the vehicle-mounted diagnostic system, the reply information sent by the vehicle-mounted diagnostic system can be obtained. And comparing the reply information with preset reply information to determine a matching result of the reply information and the preset reply information. And finally, based on the matching result, obtaining the test result of the target stitch.

The test result for the target pin may indicate whether the function for which the target pin is configured is a target function. Therefore, based on the matching result of the reply information and the preset reply information, the method and the device can directly determine whether the function configured by the target stitch is the target function or not. Specifically, if the reply information is matched with the preset reply information, the successful test of the target stitch according to the standard protocol is indicated, and the configured function of the target stitch is the target function; otherwise, the function configured by the target stitch is not the target function, and the function configuration of the target stitch is inaccurate. The method and the device for testing the target stitch determine whether the configured function of the target stitch is correct according to the matching of the preset reply information and the reply information, can ensure the accuracy of the testing process of the target stitch, and timely detect errors in the development process of the OBD interface.

Before acquiring the standard protocol of the target stitch, the application can firstly send a stitch acquisition request to the vehicle-mounted diagnosis system so as to determine the identification of the target stitch. And further determining a standard protocol corresponding to the target pin based on the identification of the target pin with the configured function. The process can ensure the accuracy of the correspondence between the target stitch and the standard protocol, and provides a correct detection basis for the detection of the target stitch.

When the target stitch is detected, the application can also display the test progress display interface at the same time. The test progress presentation interface may display a detailed page of the target pin during the process being tested. And after the test is completed, the test result is displayed on a test progress display interface so as to clearly remind the testers whether the target stitch passes the test. The process can enable a tester to quickly know the test result of the target stitch, and discover and solve the problem in time. And the OBD function caused by the configuration error of the target pin is prevented from being influenced.

In order to timely process the target pins with incorrect function configuration under the condition that the target pins do not accord with the corresponding standard protocol, the application can also push the test result to the terminal equipment of the tester so as to enable the tester to timely process the function of the configured target pins. The above process ensures that the effect of changing the configured function of the target stitch in time is ensured under the condition that the function configuration of the target stitch is not right, and the potential safety hazard of the vehicle caused by untimely treatment is avoided.

In a second aspect, there is provided an apparatus for testing on-board diagnostic system interface pins, the apparatus comprising: the system comprises an acquisition module, a function configuration module and a function configuration module, wherein the acquisition module is used for acquiring a standard protocol corresponding to a target stitch to be tested in an interface of a vehicle-mounted diagnostic system, the standard protocol is used for indicating a target function which can be realized by the target stitch, and the target stitch is a stitch with completed function configuration; the test module is used for testing the target pin based on the standard protocol; and the determining module is used for determining a test result of the target pin, wherein the test result is used for indicating whether the configured function of the target pin is matched with the target function.

With reference to the second aspect, in some possible implementations, the test module is specifically configured to: determining preset test information corresponding to the standard protocol, wherein the preset test information is used for testing the configured function of the target pin; and sending the preset test information to the vehicle-mounted diagnosis system so as to test the target pin.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, before the determining a test result of the target pin, the apparatus further includes: the processing module is used for determining preset reply information corresponding to the preset test information; obtaining reply information corresponding to the preset test information sent by the vehicle-mounted diagnosis system; and, the determining module is specifically configured to: determining a matching result of the reply information and the preset reply information; and determining the test result of the target pin according to the matching result.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, the determining module is further configured to: under the condition that the reply information is matched with the preset reply information, determining that the configured function of the target stitch is matched with the target function; and under the condition that the reply information is not matched with the preset reply information, determining that the configured function of the target stitch is not matched with the target function.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, before the acquiring a standard protocol corresponding to the target pin, the apparatus further includes: the first sending module is used for sending a stitch acquisition request to the vehicle-mounted diagnosis system, wherein the stitch acquisition request is used for requesting to acquire the identification of the target stitch; and, the acquisition module is specifically configured to: and responding to the identification of the target pin sent by the vehicle-mounted diagnosis system, and acquiring the standard protocol.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, the apparatus further includes: the display module is used for displaying a test progress display interface, and the test progress display interface is used for displaying a test result of the target pin so as to prompt a tester whether the configured function of the target pin is matched with the target function.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, the apparatus further includes: and the second sending module is used for sending the test result to the terminal equipment of the tester to prompt the tester to process the function of the target pin configured according to the test result under the condition that the test result indicates that the function of the target pin configured is not matched with the target function.

In a third aspect, an electronic device is provided that includes a memory and a processor. The memory is for storing executable program code and the processor is for calling and running the executable program code from the memory for causing the electronic device to perform the method of the first aspect or any one of the possible implementations of the first aspect.

In a fourth aspect, there is provided a computer program product comprising: computer program code which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the possible implementations of the first aspect.

In a fifth aspect, a computer readable storage medium is provided, the computer readable storage medium storing computer program code which, when run on a computer, causes the computer to perform the method of the first aspect or any one of the possible implementations of the first aspect.

Drawings

Fig. 1 is a schematic structural diagram of an OBD interface in a vehicle according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a scenario for testing interface pins of a vehicle-mounted diagnostic system according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of a method of testing on-board diagnostic system interface pins provided by an embodiment of the present application;

fig. 4 is a schematic diagram of a scenario of configuring test information according to an embodiment of the present application;

FIG. 5 is a schematic view of a scenario displaying a test progress display interface according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an apparatus for testing interface pins of an on-board diagnostic system according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical scheme of the application will be clearly and thoroughly described below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B: the text "and/or" is merely an association relation describing the associated object, and indicates that three relations may exist, for example, a and/or B may indicate: the three cases where a exists alone, a and B exist together, and B exists alone, and furthermore, in the description of the embodiments of the present application, "plural" means two or more than two.

The terms "first," "second," and the like, are used below for descriptive purposes only and are not to be construed as implying or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature.

Firstly, before describing a method for testing interface pins of a vehicle-mounted diagnostic system provided by the embodiment of the application, the embodiment of the application first describes OBD briefly.

OBD is a system that monitors the running state of a vehicle and feeds back anomalies in time. A complete OBD typically comprises three parts, a warning part, a software part and a hardware part, respectively. Wherein the warning part comprises a fault indicator lamp (Malfunction Indicator Lamp, MILs) for visual warning after a fault has occurred for alerting the driver. The software part comprises a fault diagnosis control strategy and calibration codes, and is the core of the whole system operation. The hardware part is a carrier of the software part and is also an intermediate medium from instruction issuing to instruction execution, and comprises an electronic control unit (Electronic Control Unit, ECU), sensors, actuators, communication lines and a diagnosis interface.

The communication line comprises a CAN bus, a K line, an L line and the like; the actuator comprises a fuel system diagnosis pump, an activated carbon tank electromagnetic valve, an activated carbon tank, an oil sprayer and the like; the ECU includes an engine control module (Engine Control Module, ECM, also referred to as an engine electronic control unit or an engine controller) and other electronic control units such as an automatic transmission electronic control unit (Transmission Control Unit, TCU), a battery management system (Battery Manage System, BMS), a motor control unit (Motor Control Unit, MCU, also referred to as a motor controller), and the like; the sensor comprises an air quality sensor, a vehicle speed sensor, a rotating speed sensor and the like; the diagnosis interface is an OBD interface, and is generally a 16-needle trapezoid diagnosis interface.

OBD plays a vital role in fault detection of vehicles. The OBD can be connected to an ECU in the vehicle by which the operating conditions of the engine electronic control system and other basic functions of the vehicle during operation of the vehicle are checked.

When a problem occurs in the vehicle, an MILs light in the OBD or a warning light for detecting the Engine of the vehicle (Check Engine) is turned on, and the OBD stores fault information in a memory.

Further, maintenance personnel can read fault information of the vehicle in the form of fault codes by connecting the standard OBD detection equipment with an OBD interface in the vehicle, and the cause and the position of the fault problem can be positioned.

The OBD interface is typically located under the steering wheel of the vehicle, and the structure of the OBD interface is described first.

Fig. 1 is a schematic structural diagram of an OBD interface in a vehicle according to an embodiment of the present application.

Illustratively, as shown in FIG. 1, the OBD interface in a vehicle is configured in a manner that the dimensions of the OBD interface, the current second generation OBD (OBD-II) standard version installed, are required to comply with the society of automotive Engineers (Society of Automotive Engineers, SAE) J1962 protocol. With the development of OBD, the corresponding protocol may change, and the embodiment of the application is illustrated by taking the current OBD-II version as an example.

The protocol specifies that the corresponding OBD diagnostic interface includes a total of 16 pins. As shown in fig. 1, the left-to-right stitches of the long side are respectively 1 to 8, the left-to-right stitches of the short side are respectively 9 to 16, and each stitch represents a different function. The function of some pins, commonly referred to as "dedicated pins", is predefined. The function of some pins may be customized, and these pins are commonly referred to as "custom pins". The function of each pin is defined as follows:

stitch number 1-manufacturer definition; pin number 2-pulse width modulation (Pulse Width Modulation, PWM) and variable pulse width modulation (Variable Pulse Width, VPW) bus positive; stitch number 3-manufacturer definition; stitch number 4-body ground; a No. 5 pin-a signal ground wire; pin 6—high data line (H line) of the controller area network (Controller Area Network, CAN) bus; 7 number stitch-K line; stitch number 8-manufacturer definition; pin number 9-manufacturer definition; the pin 10, PWM and VPM bus negative, exists in pairs with pin 2; 11 pins-manufacturer definition; 12 pins-manufacturer definition; 13 pins-manufacturer definition; 14 pins-Low-level data line (Low, L line) of CAN bus; 15 number stitch-L line; 16 pins-battery voltage line.

As can be seen from the definition of OBD interface pins above: the functions of stitches 1, 3, 8, 9, 11, 12 and 13 are not preset in advance, and can be defined by the vehicle manufacturer as custom stitches. For the pins 2, 4, 5, 6, 7, 10, 14, 15, and 16 for which functions have been defined, the defined functions (target functions) are one-to-one correspondence with the standard protocols, being dedicated pins. That is, pins 2, 4, 5, 6, 7, 10, 14, 15, and 16 must operate according to respective standard protocols during operation to achieve the corresponding target functions. The dedicated pins, if not configured, are in an idle state and cannot be customized by the manufacturer.

Table 1 is a schematic table of the correspondence between dedicated pins and standard protocols provided by an embodiment of the present application.

TABLE 1

Stitch numbering	Stitch function	Corresponding standard protocol
			2	PWM and VPM bus positive	SAE J1850
10	PWM and VPM bus negatives	SAE J1850
			6	CAN-H	ISO J15765-4 and SAE J2284
14	CAN-L	ISO J15765-4 and SAE J2284
			7	K line	ISO 9142-2 and ISO 14230-4
15	L line	ISO 9142-2 and ISO 14230-4

Illustratively, as shown in table 1, it can be seen that: for dedicated pins 2 and 10, which are PWM and VPM, the corresponding standard protocol is SAE J1850. Pins 6 and 14 are dedicated pins for CAN communications, and the corresponding standard protocols are International organization for standardization (International Organization for Standardization, ISO) J15765-4 and SAE J2284. Pins 7 and 15 are dedicated pins for the K-wire and L-wire, and the corresponding standard protocols are ISO 9142-2 and ISO 14230-4.

In order to determine whether the OBD interface pins are configured according to a standard protocol in the configuration process. The embodiment of the application provides a method for testing interface pins of a vehicle-mounted diagnosis system.

Fig. 2 is a schematic diagram of a scenario for testing interface pins of a vehicle-mounted diagnostic system according to an embodiment of the present application.

Illustratively, as shown in FIG. 2, embodiments of the present application may test OBD interface pins in a vehicle 202 via an electronic device 201.

Alternatively, the electronic device 201 may be a notebook computer, a wearable device, a smart phone, a tablet, etc., and the embodiment of the present application does not limit the type of the electronic device 201.

In a possible implementation, a test tool is installed in the electronic device 201, and the electronic device 201 may be connected to the vehicle 202 to detect the OBD interface pins through the test tool in the electronic device 201.

Optionally, the manner in which the electronic device 201 is connected to the vehicle 202 includes both wired and wireless connections. Wired connections include broadband connections, fiber optic connections, asymmetric digital subscriber line (Asymmetric Digital Subscriber Line, ADSL) connections, serial port connections, universal serial bus (Universal Serial Bus, USB) connections, modbus connections. The wireless connection modes include a Zigbee connection, a bluetooth connection, a cellular connection (e.g., fourth generation mobile communication technology (the 4th Generation mobile communication technology,4G), 5G), a Wi-Fi (Wireless Fidelity) connection, a Long Range Radio (Lora) connection, and a narrowband internet of things (Narrow Band Internet of Things, NB-LoT) connection.

After connection with the vehicle 202, the electronic device 201 may test the OBD interface pins via several standard protocols in table 1.

FIG. 3 is a schematic flow chart of a method for testing interface pins of an on-board diagnostic system provided by an embodiment of the application. It should be appreciated that the method may be applied to a test scenario as shown in fig. 2, and in particular to the electronic device 201 in fig. 2.

Illustratively, as shown in FIG. 3, the method 300 includes:

301, acquiring a standard protocol corresponding to a target pin to be tested in an interface of a vehicle-mounted diagnostic system, wherein the standard protocol is used for indicating a target function which can be realized by the target pin, and the target pin is a pin with function configuration completed.

In the process of testing the pins of the OBD interface, the embodiment of the application completes the testing process through a testing tool arranged in the electronic equipment.

In one possible implementation, before testing, the embodiment of the present application may first turn on the testing tool in the electronic device in any one of the following manners.

Opening the test tool by clicking operation on a display area of the electronic device;

opening a test tool through voice information on a display area of the electronic device;

The test tool is opened by a gesture adjustment operation on a display area of the electronic device.

By way of example, a tester may open an icon corresponding to the test tool by clicking on a display area of the electronic device, so as to enable the test tool to run.

Still another example, a tester may pass voice information, such as "turn on a test tool," on a display area of an electronic device to cause the test tool to run.

Still further exemplary, the tester may operate the test tool through a gesture adjustment operation, such as a "V" gesture adjustment operation, on the display area of the electronic device.

Alternatively, the test tool is embodied in the embodiment of the present application as the "J1699-3 test program" of the test software "DiagRA-D".

The J1699-3 test procedure is primarily used for mass production vehicle assessment (Production Vehicle Evaluation, PVE) testing of vehicles. The PVE test consists essentially of three parts: j1 standardization verification, J2 monitoring requirement verification, J3 in-use monitoring performance verification.

The pin test of the OBD interface is mainly the first part of test in PVE test, namely J1 standardized verification.

It should be appreciated that the purpose of the J1 standardized validation is to verify whether the underlying protocol of the vehicle meets SAE J1979 protocol requirements, which is divided into static testing and dynamic testing. The static test is the contents of chapter five through chapter nine in the J1699-3 test program. The dynamic test is mainly the contents of chapter ten to chapter eleventh in the J1699-3 test program. The test of the embodiment of the application is mainly a static test in J1 standardized verification, and particularly a test for communication in the second section of the fifth chapter in the static test.

It should also be appreciated that the static test operates the vehicle primarily according to a series of instructions on the J1699-3 test program to see if the vehicle OBD can respond properly. Before testing, the vehicle type, the engine type, the power assembly type, the number of ECUs and the like need to be configured, and the test software (or the electronic equipment) can determine a specific test program corresponding to the test information from the J1699-3 test programs to test the target pins.

Fig. 4 is a schematic diagram of a scenario of configuring test information according to an embodiment of the present application.

For example, as shown in FIG. 4, after the tester opens the test tool, a test information configuration interface 400 of the J1699-3 test program may be displayed in the display area of the electronic device. The tester may configure the test information in the test information configuration interface 400. As shown in fig. 4, the test information includes general information, vehicle information, engine type, powertrain type, vehicle type, type approval test type, and test options.

The general information includes the version of the J1699-3 test program, the PassThur interface and the name of the tester.

The vehicle information includes model year, vehicle brand, model, number of ECUs conforming to OBD-II, and number of ECUs that can be rewritten. Wherein the number of ECUs conforming to OBD-II is generally the same as the number of ECUs in the vehicle, a rewritable ECU generally refers to an ECU tuning, also known as an ECU upgrade or retrofit, and generally a re-writing of the ECU program. The number of re-writable ECUs is generally consistent with the number of OBD-II compliant ECUs.

The type approval test generally refers to a test performed to verify whether the vehicle meets all requirements of the technical specification. In an embodiment of the present application, the type approval test type refers to an actual diagnostic rate (In-Use Performance Ratio, IUPR, or In-Use Monitor Performance Ratio, IUMPR) type of the vehicle.

Vehicle types include light/medium vehicle chassis, medium truck engine mounts.

Engine types include spark-ignition and compression-ignition.

Powertrain types include conventional (i.e., fuel-powered vehicles), start-stop functionality (e.g., vehicle automatically stops when a red light is encountered, vehicle automatically starts when a green light is encountered), hybrid vehicles, and plug-in hybrid vehicles.

The test options include running a static test of the fifth chapter to the ninth chapter and running a dynamic test of the tenth chapter to the eleventh chapter. The static test refers to a test performed in a parking state without running after the vehicle is started; dynamic testing refers to testing that requires operation in a certain condition (e.g., ten minutes at a vehicle speed of 10 km/h) after the vehicle is started.

By configuring the above-described test information at the test information configuration interface 400. The tester can start the test process of the OBD interface pins through the validation operation in the test information configuration interface 400.

It should be understood that the OBD interface pin test in the embodiment of the present application is mainly to test pins corresponding to the standard protocol, that is, dedicated pins-2, 4, 5, 6, 7, 10, 14, 15 and 16.

In a possible implementation manner, before testing the target pins, the embodiment of the present application may acquire the target pins with the configured functions in the OBD interface pins, which specifically includes:

and sending a stitch acquisition request to the vehicle-mounted diagnostic system, wherein the stitch acquisition request is used for requesting to acquire the identification of the target stitch.

In the test process, the embodiment of the application can determine which pin functions are configured through the J1699-3 test program.

For example, the electronic device (or J1699-3 program) may send the pin acquisition request in the form of a CAN signal to the OBD of the vehicle via the CAN bus and OBD interface during operation.

Further, the OBD sends an identification of the target stitch in the vehicle for which the function configuration has been completed to the electronic device based on the stitch acquisition request.

Specifically, when the electronic device obtains the standard protocol corresponding to the target pin, the method specifically includes:

and responding to the identification of the target pin sent by the vehicle-mounted diagnostic system, and acquiring a standard protocol.

It should be appreciated that embodiments of the present application focus on testing dedicated pins corresponding to standard protocols. Therefore, after the electronic device receives the identifier of the target stitch, it can first determine whether the target stitch includes a dedicated stitch according to the identifier of the target stitch. And further acquiring a standard protocol corresponding to the special stitch based on the identification of the target stitch on the premise of inclusion.

Or after receiving the identification of the target stitch, the electronic device does not judge whether the target stitch contains a special stitch, and directly obtains a corresponding standard protocol according to the identification of the target stitch. If the standard protocol can be acquired, the subsequent testing flow is started, and if the standard protocol is not acquired, the default testing flow for the pins is ended.

For example, if the electronic device obtains the identification of the target pin sent by the OBD as 1, 2, 4, 5, 6, 7, 10, 14, 15, 16. From the foregoing, 1 is a custom stitch, and stitches 2, 4, 5, 6, 7, 10, 14, 15, and 16 are dedicated stitches.

In one case, the electronic device first determines whether the target pin includes a dedicated pin based on the identification of the target pin. By judging that the stitches 2, 4, 5, 6, 7, 10, 14, 15 and 16 are the dedicated stitches. The electronic device may obtain the standard protocols corresponding to pins 2, 4, 5, 6, 7, 10, 14, 15 and 16 on the premise that the target pin comprises a dedicated pin.

In another case, the electronic device directly acquires the standard protocol based on the identification of the target pin. Wherein pin 1 does not have a corresponding standard protocol. That is, when the electronic device directly acquires the standard protocol, the acquired result is the standard protocol corresponding to pins 2, 4, 5, 6, 7, 10, 14, 15 and 16.

302, a target pin is tested based on a standard protocol.

Further, after determining the standard protocol, embodiments of the present application may test the target pins based on the standard protocol.

In a possible implementation manner, when testing a target pin based on a standard protocol, the embodiment of the application includes:

determining preset test information corresponding to a standard protocol, wherein the preset test information is used for testing the configured function of a target pin;

And sending preset test information to the vehicle-mounted diagnosis system so as to test the target pins.

It should be appreciated that in embodiments of the present application, the OBD test procedure all needs to adhere to SAE J1979 protocol. The SAE J1979 protocol specifies 9 modes of OBD, namely the output content of OBD. Each pattern has a unique identifier, denoted by "$xx". Wherein xx represents a hexadecimal identifier.

In addition, parameters such as SAE J1850, ISO J15765-4, ISO 9142-2, ISO 14230-4, and SAE J2284 protocol diagnostic service definition, supported parameter identification (Parameter Identification, PID), test Identifiers (TID), message Type (Info Type) are included in the SAE J1979 protocol. Therefore, based on the different modes and parameters, the embodiment of the application can test the OBD interface pins.

Table 2 is a schematic table of an OBD mode provided by an embodiment of the present application.

TABLE 2

Illustratively, as shown in Table 2, in the embodiment of the present application, taking $01 as an example, SAE J1979 mainly defines the parameter in $01 as PID. Therefore, in the embodiment of the application, the preset test information is the preset PID test parameter.

For example, using pins 2 and 10 as an example, the corresponding standard protocol is SAE 1850.SAE J1979 specifies that in $01, the PID test parameters of the target function PWM corresponding to SAE J1850 are 61, 6A, F, 01, 00; the PID test parameters of the target function VPM corresponding to SAE J1850 are 68, 6A, F1, 01, 00.

Thus, based on the PID test parameters described above, the electronic device can send the PID test parameters to the OBD to test pins 2 and 10.

303, determining a test result of the target pin, where the test result is used to indicate whether the configured function of the target pin matches the target function.

It should be understood that, in addition to the preset test information (PID test parameters), the preset reply information corresponding to the preset test information may be preset in the standard protocol, where the preset reply information and the preset reply information exist in pairs.

In a possible implementation manner, after sending preset test information to the OBD, before determining the test result of the target pin, the embodiment of the present application may further include:

determining preset reply information corresponding to the preset test information;

And acquiring reply information which is sent by the vehicle-mounted diagnosis system and corresponds to the preset test information.

Further, determining the test result of the target pin includes:

determining a matching result of the reply information and the preset reply information;

and determining the test result of the target stitch according to the matching result.

Illustratively, taking the test for pins 2 and 10 as an example, the corresponding standard protocol is SAE 1850. In $01, SAE J1979 specifies that the PID test parameters of the target function PWM corresponding to SAE J1850 are 61, 6A, F1, 01, 00; the PID test parameters of the target function VPM corresponding to SAE J1850 are 68, 6A, F1, 01, 00.

Further, SAE J1979 also specifies PID reply parameters in $01, which correspond one-to-one to the PID test parameters. PID reply parameters of the target function PWM corresponding to SAE J1850 are 41, 6B, 11, 01 and 00; the PID reply parameters of the target function VPM corresponding to SAE J1850 are 48, 6B, 00, 01, 00.

The PID reply message is the preset reply message in the embodiment of the present application.

Based on the preset reply information, the electronic device can also receive reply information responded by the OBD based on the preset test information. The electronic equipment can match the preset reply information with the reply information, determine the matching result of the preset reply information and the reply information, and determine the test result of the target pin according to the matching result.

Specifically, determining a test result of the target pin according to a preset reply message and a matching result of the reply message specifically includes:

under the condition that the reply information is matched with the preset reply information, determining that the configured function of the target stitch is matched with the target function;

and under the condition that the reply information is not matched with the preset reply information, determining that the configured function of the target stitch is not matched with the target function.

It should be appreciated that in the event that the reply message matches the preset reply message, the target pin is illustrated as operating in accordance with the standard protocol. Based on the one-to-one correspondence between the standard protocol and the target function, it can be stated that the function of the target pin configured is the target function corresponding to the standard protocol. Otherwise, it is indicated that the function for which the target pin is configured is not the target function.

Finally, the embodiment of the application also provides a method for visualizing the test result, which specifically comprises the following steps:

and displaying a test progress display interface, wherein the test progress display interface is used for displaying a test result of the target stitch so as to prompt a tester whether the configured function of the target stitch is matched with the target function.

Fig. 5 is a schematic view of a scenario displaying a test progress display interface according to an embodiment of the present application.

For example, as shown in fig. 5, in the process of testing the OBD interface pins, the electronic device may display a test progress display interface 500 in a display area of the electronic device. The test progress presentation interface 500 includes an identification of the target pin currently being tested and a standard protocol corresponding to the target pin. Preset test information corresponding to the target pin (standard protocol) can be displayed, and real-time reply information of the OBD can be displayed.

After the electronic device matches the reply information with the preset reply information, the determined test result of the target pin may also be displayed in the test progress display interface 500.

As shown in fig. 5, the target pins are identified as 2 and 10, and the standard protocol for the target pin is SAE J1850. The preset test information corresponding to SAE J1850 is 61, 6A, F1, 01 and 00, and the real-time response information of OBD is 41, 6B, 11, 01 and 00. Then the electronic device may determine that pins 2 and 10 conform to SAE J1850 standard protocols. The popup window of "pins 2 and 10 test pass" is further displayed to alert the tester.

Alternatively, in addition to the manner of popup prompting described above. The electronic device may also prompt the test result with voice, send mail, short message, send prompt message to the enterprise application, etc., which is not limited by the embodiment of the present application.

In addition, when the embodiment of the application tests the target pins, the number of the target pins is not limited. The embodiment of the application can display the test result of each target stitch after the test of each target stitch is finished. After all the target pin tests are completed, the test results of all the target pins, in particular, which target pin tests pass and which target pin tests fail, are displayed in a unified manner.

In a possible implementation manner, when the test result indicates that the function of the target pin configured is not a specified target function, in order to remind the tester to process the function of the target pin configured in time, the embodiment of the present application may further push the test result to a terminal device of the tester, where the method specifically includes:

And under the condition that the test result indicates that the function of the target pin configured is not matched with the target function, sending the test result to terminal equipment of a tester to prompt the tester to process the function of the target pin configured according to the test result.

Alternatively, the types of the terminal device and the electronic device may be the same. For example, the terminal device and the electronic device are both notebook computers. The types of the terminal device and the electronic device may also be different, for example, the terminal device is a smart phone, and the electronic device is a notebook computer.

For example, when the electronic device determines that the function of the target stitch configured is not matched with the target function, the identification of the terminal device of the tester, such as a phone number, a mailbox address, enterprise application login information, and the like, may be determined based on the name of the tester.

In one case, when the identifier of the terminal device is a phone number, the electronic device may send the test result to the terminal device-smart phone of the tester in the form of a short message based on the phone number;

in another case, when the identifier of the terminal device is a mailbox address, the electronic device may send the test result to the terminal device of the tester, i.e. the smart phone or the notebook computer, in the form of a mail based on the mailbox address;

In another case, when the identifier of the terminal device is the enterprise application login information, the electronic device may send the test result to the terminal device of the tester, i.e. the smart phone or the notebook computer, in the form of a notification message based on the enterprise application login information.

After the tester views the test result from the terminal device based on any one of the above forms, the configured function of the target pin can be processed in time, for example, the configured function of the target pin is reconfigured according to the standard protocol corresponding to the target pin.

Fig. 6 is a schematic structural diagram of an apparatus for testing interface pins of an on-board diagnostic system according to an embodiment of the present application.

Illustratively, as shown in FIG. 6, the apparatus 600 includes:

the obtaining module 601 is configured to obtain a standard protocol corresponding to a target pin to be tested in the vehicle-mounted diagnostic system interface, where the standard protocol is used to indicate a target function that can be implemented by the target pin, and the target pin is a pin with a function configuration completed;

a test module 602 for testing the target pin based on the standard protocol;

a determining module 603 is configured to determine a test result of the target pin, where the test result is used to indicate whether the configured function of the target pin matches the target function.

In one possible implementation, the test module 602 is specifically configured to: determining preset test information corresponding to the standard protocol, wherein the preset test information is used for testing the configured function of the target pin; and sending the preset test information to the vehicle-mounted diagnosis system so as to test the target pin.

Optionally, before the determining the test result of the target pin, the apparatus further includes: the processing module is used for determining preset reply information corresponding to the preset test information; obtaining reply information corresponding to the preset test information sent by the vehicle-mounted diagnosis system; and, the determining module 603 is specifically configured to: determining a matching result of the reply information and the preset reply information; and determining the test result of the target pin according to the matching result.

In a possible implementation, the determining module 603 is further configured to: under the condition that the reply information is matched with the preset reply information, determining that the configured function of the target stitch is matched with the target function; and under the condition that the reply information is not matched with the preset reply information, determining that the configured function of the target stitch is not matched with the target function.

Optionally, before the obtaining the standard protocol corresponding to the target pin, the apparatus further includes: the first sending module is used for sending a stitch acquisition request to the vehicle-mounted diagnosis system, wherein the stitch acquisition request is used for requesting to acquire the identification of the target stitch; and, the obtaining module 601 is specifically configured to: and responding to the identification of the target pin sent by the vehicle-mounted diagnosis system, and acquiring the standard protocol.

Optionally, the apparatus further comprises: the display module is used for displaying a test progress display interface, and the test progress display interface is used for displaying a test result of the target pin so as to prompt a tester whether the configured function of the target pin is matched with the target function.

Optionally, the apparatus further comprises: and the second sending module is used for sending the test result to the terminal equipment of the tester to prompt the tester to process the function of the target pin configured according to the test result under the condition that the test result indicates that the function of the target pin configured is not matched with the target function.

Illustratively, as shown in FIG. 7, the electronic device 201 includes: the system comprises a memory 701 and a processor 702, wherein executable program code 7011 is stored in the memory 701, and the processor 702 is used for calling and executing the executable program code 7011 to execute a method for testing the on-board diagnostic system interface pins.

In this embodiment, the electronic device may be divided into functional modules according to the above method example, for example, each functional module may be corresponding to one processing module, or two or more functions may be integrated into one processing module, where the integrated modules may be implemented in a hardware form. It should be noted that, in this embodiment, the division of the modules is schematic, only one logic function is divided, and another division manner may be implemented in actual implementation.

In the case of dividing each function module with corresponding each function, the electronic device may include: an acquisition module, a test module, a determination module and the like. It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

The electronic device provided in this embodiment is configured to execute the above method for testing the interface pins of the vehicle-mounted diagnostic system, so that the same effects as those of the implementation method can be achieved.

In case an integrated unit is employed, the electronic device may comprise a processing module, a memory module. The processing module can be used for controlling and managing the actions of the electronic equipment. The memory module may be used to support the electronic device in executing, inter alia, program code and data.

Wherein a processing module may be a processor or controller that may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the present disclosure. A processor may also be a combination of computing functions, e.g., including one or more microprocessors, digital signal processing (digital signal processing, DSP) and microprocessor combinations, etc., and a memory module may be a memory.

The present embodiment also provides a computer readable storage medium having stored therein computer program code which, when run on a computer, causes the computer to perform the above-described related method steps to implement a method of testing an on-board diagnostic system interface pin in the above-described embodiments.

The present embodiment also provides a computer program product which, when run on a computer, causes the computer to perform the above-described related steps to implement a method of testing on-board diagnostic system interface pins in the above-described embodiments.

In addition, the electronic device provided by the embodiment of the application can be a chip, a component or a module, and the electronic device can comprise a processor and a memory which are connected; the memory is used for storing instructions, and when the electronic device is running, the processor can call and execute the instructions to enable the chip to execute one of the methods for testing the on-board diagnostic system interface pins in the embodiment.

The electronic device, the computer readable storage medium, the computer program product or the chip provided in this embodiment are used to execute the corresponding method provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding method provided above, and will not be described herein.

It will be appreciated by those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A method of testing an interface pin of an on-board diagnostic system, the method comprising:

Acquiring a standard protocol corresponding to a target stitch to be tested in a vehicle-mounted diagnostic system interface, wherein the standard protocol is used for indicating a target function which can be realized by the target stitch, and the target stitch is a stitch with function configuration completed;

testing the target pin based on the standard protocol;

and determining a test result of the target stitch, wherein the test result is used for indicating whether the configured function of the target stitch is matched with the target function.

2. The method of claim 1, wherein the testing the target pin based on the standard protocol comprises:

determining preset test information corresponding to the standard protocol, wherein the preset test information is used for testing the configured function of the target pin;

and sending the preset test information to the vehicle-mounted diagnosis system so as to test the target pin.

3. The method of claim 2, wherein prior to determining the test result for the target stitch, the method further comprises:

obtaining reply information corresponding to the preset test information sent by the vehicle-mounted diagnostic system;

And the determining the test result of the target stitch comprises:

4. The method of claim 3, wherein determining the test result of the target pin based on the matching result comprises:

5. The method of claim 1, wherein before the acquiring the standard protocol corresponding to the target pin to be tested in the on-board diagnostic system interface, the method further comprises:

sending a stitch acquisition request to the vehicle-mounted diagnostic system, wherein the stitch acquisition request is used for requesting to acquire the identification of the target stitch;

and the obtaining the standard protocol corresponding to the target pin to be tested in the vehicle-mounted diagnosis system interface comprises the following steps:

And responding to the identification of the target pin sent by the vehicle-mounted diagnosis system, and acquiring the standard protocol.

6. The method according to claim 1, wherein the method further comprises:

7. The method according to claim 1, wherein the method further comprises:

8. An apparatus for testing on-board diagnostic system interface pins, the apparatus comprising:

the system comprises an acquisition module, a function configuration module and a function configuration module, wherein the acquisition module is used for acquiring a standard protocol corresponding to a target stitch to be tested in an interface of a vehicle-mounted diagnostic system, the standard protocol is used for indicating a target function which can be realized by the target stitch, and the target stitch is a stitch with completed function configuration;

The test module is used for testing the target pins based on the standard protocol;

and the determining module is used for determining a test result of the target stitch, wherein the test result is used for indicating whether the configured function of the target stitch is matched with the target function.

9. An electronic device, the electronic device comprising:

a memory for storing executable program code;

a processor for calling and running the executable program code from the memory, causing the electronic device to perform the method of any one of claims 1 to 7.

10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed, implements the method according to any of claims 1 to 7.