Method and system for determining unknown fault code of vehicle

Abstract

The embodiment of the invention provides a method and a system for determining an unknown fault code of a vehicle. The vehicle unknown fault code determination method comprises the steps that a low-voltage power supply is controlled to supply power to a low-voltage interface of a test platform, the test platform is constructed based on low-voltage electrical components of a target type vehicle and the connection relation of the low-voltage electrical components, and the low-voltage electrical components comprise electronic control units; supplying power to the low-voltage interface to enable a low-voltage circuit of the test platform to operate; the electronic control unit generates running log data in the running process of the low-voltage circuit, and the running log data comprises running fault codes; reading the operation fault code from a diagnosis interface of the test platform; and screening operation fault codes based on the identified fault codes to obtain unidentified fault codes. According to the scheme provided by the embodiment of the invention, the test platform with the same connection relationship with the target type of vehicle electrical component is directly pressurized, so that the test platform operates as a whole, and all possible operation fault codes are generated under the test condition, so that more unknown fault codes are tested as much as possible.

Description

Technical Field

[0001] The present disclosure relates to the field of vehicle technology, and in particular to a method and system for determining an unknown fault code of a vehicle. Background Art

[0002] During the vehicle after-sales service, after-sales personnel use a vehicle diagnostic instrument to read various fault codes displayed by the on-board diagnostic system and use them to locate the vehicle's potential fault. However, locating the vehicle's potential fault based on fault codes requires knowing the fault types corresponding to each fault code. To address this issue, vehicle manufacturers must identify and define various types of fault codes during the vehicle design and testing phases. Identifying fault codes is a prerequisite for defining the fault types associated with these codes.

[0003] Because fault codes are generated by various types of electronic control units in the vehicle, fault code identification is currently performed at the individual electronic control unit level. Specifically, various types of input voltage signals are injected, the fault code is read from the fault output port of the electronic control unit (in this case, the fault output port may be a general data output port), and the output fault code is identified as an undefined fault code. After determining that the fault code is undefined, technicians use technical identification to determine the corresponding fault type.

[0004] However, a large number of after-sales technical feedback indicates that many fault codes read using vehicle diagnostic instruments remain undefined, making it difficult for after-sales to quickly identify the fault location. They can only report the fault code to R&D, which then urgently identifies the fault type. This means that existing fault testing at the electronic control unit level cannot capture the full range of fault codes that occur in actual vehicle use. Summary of the Invention

[0005] In order to solve the above technical problems, the embodiments of the present disclosure provide a method and system for determining an unknown fault code of a vehicle.

[0006] In a first aspect, an embodiment of the present disclosure provides a method for determining an unknown fault code of a vehicle, comprising:

[0007] Controlling a low-voltage power supply to supply power to a low-voltage interface of a test platform, the test platform being constructed based on a connection relationship between low-voltage electrical components of a target type vehicle and the low-voltage electrical components, the low-voltage electrical components including an electronic control unit; supplying power to the low-voltage interface to enable operation of a low-voltage circuit of the test platform; during operation of the low-voltage circuit, the electronic control unit generating operation log data, the operation log data including an operation fault code;

[0008] Reading the operating fault code from the diagnostic interface of the test platform;

[0009] The operating fault codes are filtered based on the identified fault codes to obtain unidentified fault codes.

[0010] Optionally, before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform, the method further includes:

[0011] Determine input voltage characteristics based on test requirements, wherein the input voltage characteristics include a voltage peak, a waveform, and a duration of the input voltage;

[0012] The controlling the low-voltage power supply to supply voltage to the test platform includes: controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform according to the input voltage characteristics.

[0013] Optionally, the low-voltage power supply is a programmable power supply;

[0014] The controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform according to the input voltage characteristics includes: generating voltage modulation data based on the input voltage characteristics;

[0015] The voltage modulation data is used to control the programmable power supply so that the programmable power supply outputs a supply voltage that meets the input voltage characteristics.

[0016] Optionally, determine input voltage characteristics based on test requirements, including:

[0017] Determine an overvoltage voltage characteristic based on an overvoltage test requirement, or determine an undervoltage voltage characteristic based on an undervoltage test requirement;

[0018] The overvoltage voltage is higher than the rated input voltage of the low-voltage interface, and the undervoltage voltage is lower than the rated input voltage of the low-voltage interface.

[0019] Optionally, determining the input voltage characteristics based on the test requirements includes:

[0020] Determine a fluctuating voltage characteristic based on a fluctuation test requirement, wherein the fluctuating voltage fluctuates up and down relative to a rated input voltage of the low-voltage interface, wherein the up and down fluctuation is a gradual increase from a first voltage value to a second voltage value, or a gradual decrease from the second voltage value to the first voltage value, or a periodic step jump or continuous fluctuating change between the first voltage value and the second voltage value;

[0021] The first voltage value is lower than the rated input voltage of the low-voltage interface, and the second voltage value is higher than the rated input voltage of the low-voltage interface.

[0022] Optionally, the operation log data further includes the generation time of the operation fault code; the method further includes:

[0023] Measuring the real-time voltage output by the programmable power supply, and determining whether the real-time voltage meets the input voltage characteristics, determining that the operating period of the test platform under the real-time voltage is a trustworthy period;

[0024] Reading the operating fault code from the diagnostic interface of the test platform includes: reading the operating fault code whose corresponding generation time is within the trustworthy time period from the diagnostic interface.

[0025] Optionally, after determining an unidentified fault code in the operational fault, the method further includes:

[0026] Obtaining a target input voltage characteristic corresponding to a time period during which the unidentified fault code appears;

[0027] The unidentified fault code is associated with the target input voltage characteristic.

[0028] Optionally, after determining an unidentified fault code in the operating fault, the method further includes:

[0029] Obtaining target log data from the operation log data; the target log data is the operation log data within a set time period before the unidentified fault code appears;

[0030] The unidentified fault code is associated with the target log data.

[0031] Optionally, the method further includes: before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform, the method further includes:

[0032] The operation log data or the operation fault code stored in the test platform is deleted through the diagnostic interface.

[0033] In a second aspect, an embodiment of the present disclosure provides a vehicle unknown fault code determination system, comprising a test platform, a power supply, and a data reading and analysis device;

[0034] The test platform is constructed based on the low-voltage electrical components of the target type vehicle and the connection relationship between the low-voltage electrical components; the low-voltage electrical components include an electronic control unit;

[0035] The power supply is used to control the low-voltage power supply to supply power to the low-voltage interface of the test platform; the power supply supplies power to the low-voltage interface to enable the low-voltage circuit of the test platform to operate; during the operation of the low-voltage circuit, the electronic control unit generates operation log data, and the operation log data includes an operation fault code;

[0036] The data reading and analyzing device is used to read the operating fault code from the diagnostic interface of the test platform; and to filter the operating fault code based on the identified fault code to determine the unidentified fault code in the operating fault.

[0037] The embodiment of the present disclosure directly applies pressure to the test platform with the same connection relationship as the target type of vehicle electrical components, so that the test platform is operated as a whole and all possible operating fault codes are generated under the test conditions. After all the operating fault codes are read, all the operating fault codes are compared with the identified fault codes, and unidentified fault codes can be determined. In actual applications, by setting various test conditions, that is, setting various types of voltages for powering the low-voltage power supply interface, the fault codes that appear when the vehicle is operating as a whole can be obtained as much as possible based on the overall characteristics of the test platform, thereby reducing the number of unidentified fault codes that are missed. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0039] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work, including:

[0040] Figure 1 is a flow chart of a method for determining an unknown vehicle fault code in an embodiment of the present disclosure;

[0041] Figure 2 It is a schematic diagram of the voltage characteristics of a DC superimposed rectangular wave voltage;

[0042] Figure 3 is a flow chart of a method for determining an unknown vehicle fault code provided by another embodiment of the present disclosure;

[0043] Figure 4 It is a schematic diagram of the structural framework of the vehicle unknown fault code determination system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0044] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0045] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc. mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0046] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0047] In order to eliminate the vehicle's location fault code as much as possible and facilitate rapid determination of vehicle faults based on the vehicle's fault code during vehicle maintenance, an embodiment of the present disclosure provides a method for determining an unknown vehicle fault code.

[0048] Before analyzing the method for determining vehicle position fault codes provided by the embodiment of the present disclosure, the reasons why the prior art fails to determine all vehicle fault codes as much as possible are first analyzed.

[0049] As analyzed in the background technology, the existing technology determines fault codes at the level of the electronic control unit (ECU). However, determining fault codes at the ECU elevator level does not consider the data interaction and control issues between the ECU and other vehicle components (such as other ECUs, vehicle sensors, and actuators) after the ECU is integrated into the vehicle. It also does not consider the varying impedance characteristics caused by the complexity of the vehicle circuits, nor the random errors in input voltage and output data caused by varying impedance characteristics and various electromagnetic environments.

[0050] Precisely because the aforementioned issues are not taken into consideration, the existing fault code determination method cannot effectively identify the fault problems of the electronic control unit in a complex environment (possible random extreme conditions) and complex data interaction process when the vehicle is in operation, and cannot effectively extract the fault codes corresponding to the aforementioned fault problems.

[0051] Based on the foregoing analysis, an embodiment of the present disclosure provides a method for determining unknown fault codes based on a vehicle test platform, which performs vehicle testing based on the vehicle test platform to extract as many fault codes as possible from the vehicle.

[0052] The test platform in the disclosed embodiments is constructed based on the target vehicle's low-voltage electrical components and their connections. These components include the target vehicle's various electronic control units, sensors, electric actuator control components, and data harnesses. These components are connected according to their connections in the target vehicle to create a 1:1 simulation of the target vehicle's state. In practice, the methods described in the disclosed embodiments can be performed directly using a target vehicle as the test platform.

[0053] To implement the method for determining location fault codes in the disclosed embodiments, corresponding testing hardware is required. This testing hardware includes a low-voltage power supply for providing test voltage to the test platform, a data reader for detecting faults on the test platform, and a data processing device for implementing fault code screening. In practice, the aforementioned data processing device and data reader for fault code screening can be integrated into a single device, such as a vehicle fault diagnostic instrument.

[0054] Figure 1 FIG. 1 is a flow chart of a method for determining an unknown vehicle fault code in an embodiment of the present disclosure. Figure 1 As shown, the method for determining an unknown vehicle fault code provided by the embodiment of the present disclosure includes S110-S130.

[0055] S110: Controls the low-voltage power supply to supply power to the low-voltage interface of the test platform.

[0056] As previously stated, the test platform is constructed based on the low-voltage electrical components and their connections within the target vehicle. These components include the electronic control unit (ECU), various sensors, various electric actuators, and various data wiring harnesses. A low-voltage power supply supplies power to the test platform's low-voltage interface, enabling the test platform's low-voltage circuits to operate, specifically the ECU, sensors, and electric actuators, and to transmit signals and data between them.

[0057] It should be noted that the aforementioned enabling of the low-voltage circuit operation of the test platform is a targeted statement. In actual applications, the voltage of the low-voltage interface may be unreasonable, causing the low-voltage circuit of the test platform to fail to start, or overvoltage and power-off protection.

[0058] During low-voltage circuit operation, the electronic control unit (ECU) generates operational log data based on its business logic and monitoring of its own operating status. This log data is then stored locally or sent to a dedicated data storage platform. This log data includes operational fault codes and may also include normal operating record data.

[0059] S120: Read the operating fault code from the diagnostic interface of the test platform.

[0060] After the test platform generates the aforementioned operation log data, the vehicle fault diagnosis instrument can read the aforementioned operation log data from the diagnostic interface of the test platform, and thus can read the operation fault code.

[0061] In the disclosed embodiment, a vehicle fault diagnostic instrument can be connected to a data storage and reading interface of an onboard diagnostic system of a test platform and read operation log data via a pre-defined communication protocol. After obtaining the operation log data, the vehicle fault diagnostic instrument can identify the operation fault code in the operation log data based on the data type identifier.

[0062] S130: Filtering operating fault codes based on identified fault codes to obtain unidentified fault codes.

[0063] In the disclosed embodiment, the vehicle fault diagnostic instrument pre-stores identified fault codes. Identified fault codes are fault codes for which the corresponding fault type has been determined. By comparing each operational fault code with the identified fault codes, identified fault codes can be filtered out from operational faults, leaving only unidentified fault codes.

[0064] Based on the aforementioned analysis, the disclosed embodiment directly applies pressure to a test platform with the same electrical components as the target vehicle, causing the entire test platform to operate and generate all possible operational fault codes under test conditions. After reading all operational fault codes, they are compared with recognized fault codes to determine unrecognized fault codes.

[0065] In actual applications, by setting various test conditions, that is, setting various types of voltages for the low-voltage power supply interface, the fault codes that appear during the overall operation of the vehicle can be obtained as much as possible based on the overall characteristics of the test platform, reducing the number of unidentified fault codes that are missed.

[0066] In practice, to control the low-voltage power supply to the test platform's low-voltage interface and ensure the test platform generates as many unknown fault codes as possible, it is necessary to properly set the power supply voltage provided to the test platform. In practice, this power supply voltage should be such that the electronic control unit in the test platform operates in an abnormal state as much as possible. To achieve the 1,000-speed target, before executing S110 above, the following S140 may also be executed.

[0067] S140: Determine input voltage characteristics based on test requirements, where the input voltage characteristics include a voltage peak, waveform, and duration of the input voltage.

[0068] The test requirements in the disclosed embodiments refer to the requirements for low-voltage power input control of target vehicles under various harsh environments. In practical applications, the low-voltage battery of the target vehicle may experience overvoltage, undervoltage, random voltage fluctuations due to loose connections, or periodic voltage fluctuations. Therefore, the input voltage characteristics can be determined based on these conditions. In specific implementations, multiple standard input voltage characteristics can be determined based on the aforementioned test requirements, each of which includes voltage peak, waveform, and duration characteristics.

[0069] In a specific application, determining the input voltage based on the test requirement may include the following S140A.

[0070] S140A: Determine overvoltage voltage characteristics based on overvoltage test requirements.

[0071] As the name suggests, overvoltage testing requires that the test platform input voltage be in an overvoltage state. The corresponding overvoltage voltage needs to be higher than the rated input voltage of the low-voltage interface. For example, in an application, if the rated input voltage of the low-voltage interface is 12V, the corresponding overvoltage voltage should be higher than 12V, such as 18V or 24V.

[0072] In another specific application, determining the input voltage based on the test requirement may include the following S140B.

[0073] S140B: Determine an undervoltage voltage characteristic based on an undervoltage test requirement.

[0074] As the name suggests, undervoltage testing requires that the test platform input voltage be undervoltage. The corresponding undervoltage voltage must be lower than the rated input voltage of the low-voltage interface. For example, in an application where the rated input voltage of the low-voltage interface is 12V, the corresponding undervoltage voltage should be lower than 12V, for example, 9V.

[0075] In yet another specific application, determining the input voltage based on the test requirement may include the following S140C.

[0076] S140C: Determines the fluctuation voltage characteristics based on the fluctuation test requirements. The fluctuation voltage fluctuates above and below the rated input voltage of the low-voltage interface.

[0077] In actual applications, due to reasons such as unreliable low-voltage battery connection or strong external electromagnetic interference, the voltage input to the low-voltage interface may fluctuate strongly. In one possible case, the voltage of the low-voltage interface of the target type of vehicle will fluctuate up and down relative to its rated voltage. In this case, the input voltage fluctuates up and down relative to the low-voltage interface. The aforementioned up and down fluctuations can be a slow rise from the first voltage value to the second voltage value, or a slow fall from the second voltage to the first voltage value, or a periodic step jump or continuous fluctuation between the first voltage value and the second voltage value. The aforementioned continuous fluctuation can be a periodic fluctuation with a specific regularity, or a random fluctuation. According to the process in the previous article, the first voltage value is lower than the rated input voltage of the low-voltage interface, and the second voltage value is higher than the rated input voltage of the voltage interface.

[0078] In some embodiments of the present disclosure, the low-voltage power supply used to supply power to the low-voltage interface is a programmable power supply. The programmable power supply can modulate the voltage it provides to the low-voltage interface via the output interface based on input control data. The aforementioned S140 of controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform according to the input voltage characteristics may include S141-S142.

[0079] S141: Generate voltage modulation data based on input voltage characteristics.

[0080] S142: Using the voltage modulation data to control the programmable power supply, so that the programmable power supply outputs a supply voltage that meets the input voltage characteristics.

[0081] In practice, to ensure that the programmable power supply outputs a supply voltage that matches the input voltage characteristics, a control computer and a programmable power supply form a master-slave architecture. The control computer serves as the master, while the programmable power supply serves as the slave. The control power supply generates voltage modulation data based on the input voltage characteristics input by the user based on test requirements, and transmits this voltage modulation data to the programmable power supply, serving as the slave. After receiving the voltage modulation data, the programmable power supply modulates the input AC and DC power through its internal modulation circuit to produce a supply voltage that matches the input voltage characteristics.

[0082] In actual applications, although the programmable voltage outputs the supply voltage according to the voltage modulation data, due to factors such as the programmable power supply's own systematic errors and circuit impedance characteristics, the supply voltage output by the programmable power supply may not match the input voltage characteristics. If the power supply output by the programmable voltage does not match the input voltage characteristics, the aforementioned output voltage test may fail to meet the test requirements. In this case, unknown fault codes may not be properly captured.

[0083] As previously analyzed, the operation log data also includes the generation time of the operation fault code. To avoid the problem mentioned in the previous paragraph, after executing the aforementioned S142, the following S143 may also be executed.

[0084] S143: Measure the real-time voltage output by the programmable power supply, and if it is determined that the real-time voltage meets the input voltage characteristics, determine that the operating period of the test platform under the real-time voltage is a credible period.

[0085] In order to achieve voltage measurement, the test equipment in the embodiment of the present disclosure also includes a voltmeter or an oscilloscope including a voltage test function. The aforementioned voltmeter or oscilloscope is connected in parallel to the output interface of the program-controlled voltage to measure the real-time voltage of the program-controlled voltage. After obtaining the real-time voltage, the real-time voltage can then be sent to the vehicle fault diagnostic instrument. The vehicle fault diagnostic instrument compares the real-time voltage and the input voltage characteristics to determine whether the real-time voltage meets the characteristics of the input voltage characteristics at the corresponding moment. If it is determined that the real-time voltage meets the characteristics of the input voltage characteristics at the corresponding moment, the operating period of the test platform under the real-time voltage is a credible period. The aforementioned credible period is a period that indicates that the corresponding operating fault code can be trusted.

[0086] Accordingly, the aforementioned step S120 of reading the operating fault codes from the diagnostic interface of the test platform may include reading, from the diagnostic interface, operating fault codes whose generation times fall within a trustworthy time period. By only reading the operating fault codes corresponding to the trustworthy time period, the amount of data to be filtered in the subsequent step S130 can be reduced, thereby reducing the workload of subsequent steps.

[0087] In some embodiments of the present disclosure, after executing the aforementioned S130 , the following S150 - S160 may also be executed.

[0088] S150: Obtain target input voltage characteristics corresponding to the period of occurrence of unidentified fault codes.

[0089] S160: Correlate the unidentified fault code with the target input voltage characteristic.

[0090] Based on circuit principles and logical reasoning, it's likely that in actual applications, unrecognizable fault codes (i.e., unidentifiable fault codes) are caused by changes in the test platform's system characteristics due to input voltage characteristics. To subsequently identify the cause of the unrecognized fault code, the unrecognized fault code can be associated with the target input voltage characteristics, allowing technicians to infer the cause of the test platform's failure based on the target input voltage characteristics.

[0091] In some embodiments, after executing the aforementioned S140 , the following S170 - S180 may also be executed.

[0092] S170: Acquire target log data from the operation log data; the target log data is the operation log data within a set time period before the unrecognized fault code appears.

[0093] S180: Associating the unidentified fault code with the target operation log data.

[0094] In some cases, a test platform failure is caused by cumulative factors, which can be inferred from its operating log data. In other words, in some cases, operating log data can be used to determine the cause of an unidentified fault. Based on this, in the disclosed embodiment, target operating log data corresponding to a set period of time when an unidentified fault code appears is obtained. After obtaining the corresponding target operating log data, it can then be associated with the location fault code and provided to technicians to facilitate inverse analysis to determine the cause of the unknown fault code during testing.

[0095] In actual applications, in order to avoid insufficient data processing, before executing the aforementioned S110 , the operation log data or operation fault codes stored in the test platform can also be deleted through the diagnostic interface.

[0096] To facilitate understanding of this solution, the following describes a fault code test using actual measurements. To identify unknown fault codes, a host computer, a programmable power supply, and an oscilloscope are required for vehicle diagnostic testing. The host computer is equipped with a fault code reading program, a voltage jump waveform control program, and a data filtering program. The host computer is connected to the programmable power supply, which uses the voltage jump waveform control program to control the power supply to output a test voltage with specific characteristics. The host computer is connected to the OBD port of the target vehicle via an OBD-to-RJ45 network cable.

[0097] The fault code test process includes: (1) Before the test, the fault code reading program sends a fault code clearing instruction to the test platform to clear the historical fault codes stored in the test platform. (2) Then the voltage jump waveform control program generates voltage modulation data according to the input voltage characteristics input by the user, and sends the voltage modulation data to the programmable power supply. (3) The programmable power supply outputs the test voltage according to the voltage modulation data, and applies the test voltage to the low-voltage interface of the test platform to enable the low-voltage circuit of the test platform to operate, while being monitored by the output voltage of the programmable power supply. The test platform generates operation log data under voltage enable. (4) The fault code reading program will read the newly stored fault codes of the test platform periodically or after the test is completed. (5) After reading the newly stored fault codes, the fault codes are screened to determine the unrecognized fault codes.

[0098] In a specific implementation, the voltage jump waveform control program can be developed based on Labview, and its input voltage characteristics can be set arbitrarily by the user. In one application, the input voltage characteristics set by the user include the following.

[0099] Step voltage: maintain at 13V for 30s, then decrease to 9V at a frequency of 1V / s and maintain for 60s, then increase to 13V at a frequency of 1V / s and maintain for 60s, increase to 16V at a frequency of 1V / s and maintain for 60s, and finally decrease to 13V at a frequency of 1V / s and maintain for 30s.

[0100] Long-term constant voltage overvoltage: maintain constant voltage of 18V for 60 minutes.

[0101] Short-time constant voltage overvoltage: maintain a constant voltage of 24V for 60s.

[0102] Slowly increase or decrease the voltage: reduce the supply voltage from 16V to 0V at a linear rate of change of (0.5±0.1)V / min or in steps of no more than 25mV, and then increase it to 16V at the same rate of change.

[0103] Fast rise and slow fall voltage: reduce the supply voltage from 16V to 0V at a linear rate of change of (0.5±0.1)V / min or in steps of no more than 25mV, and then raise the voltage from 0V to 16V within 0.5s.

[0104] Reset characteristic voltage: reduce the voltage from Usmin (generally set to 12V in actual vehicles) to 0.95Usmin in 5% steps, hold for 5s, then increase to Usmin, hold for 10s and perform functional test, then reduce the voltage to 0.9Usmin, and so on, continue with a 5% gradient of Usmin until it drops to 0V, and then increase the voltage to Usmin.

[0105] DC superimposed rectangular wave voltage: maintain 11.8V for 2s, then increase the voltage to 15V within 300ms and maintain for 2s, then reduce the voltage to 11.8V within no less than 300ms and maintain for 2s. Figure 2 This is a schematic diagram of the voltage characteristics of a DC superimposed rectangular wave voltage. Figure 2 As shown in the figure, the input voltage characteristic initially maintains a constant voltage of 11.8V. After 2000s, it increases at a rate of 10.67V / s for 300ms until it reaches 15V. After the input voltage remains at 15V for 2000ms, it decreases to 11.8V at a rate of 10.67V / s for 300ms.

[0106] In order to more clearly understand the above content, the method for determining an unknown vehicle fault code provided by an embodiment of the present disclosure is introduced below with an example. Figure 3 FIG. 1 is a flow chart of a method for determining an unknown vehicle fault code according to another embodiment of the present disclosure. Figure 3 As shown, another embodiment provides a method for determining an unknown vehicle fault code, including S310-S350.

[0107] S310: Construct a test platform based on the low-voltage electrical components of the target type vehicle and their connection relationships, and connect the power supply to the low-voltage interface of the test platform.

[0108] S320: Connect the fault tester to the data reading interface of the test platform, and control the test platform to delete the stored operation log data.

[0109] S330: Determine the input voltage characteristics, and control the power supply to supply power to the test platform according to the input voltage characteristics, so as to enable the low-voltage circuit of the test platform to operate; during the operation of the low-voltage circuit, the electronic control unit generates operation log data.

[0110] In a specific implementation, the power supply can supply power to the test platform in sequence according to the characteristics of each input voltage, so that the test platform generates operation log data under various input voltage conditions.

[0111] S340: Here, the fault tester is connected to the data reading interface of the test platform to read the operating fault code from the diagnostic interface of the test platform.

[0112] S350: Filtering operating fault codes based on identified fault codes to obtain unidentified fault codes.

[0113] In addition to providing the aforementioned vehicle unknown fault code determination method, the embodiment of the present disclosure also provides a vehicle unknown fault code determination system. Figure 4 FIG. 4 is a schematic diagram of the structural framework of a vehicle unknown fault code determination system provided by an embodiment of the present disclosure. The vehicle unknown fault code determination system 400 includes a test platform 401 , a power supply 402 , and a data reading and analysis device 403 .

[0114] The test platform 401 is constructed based on the low-voltage electrical components of the target type vehicle and the connection relationship between the low-voltage electrical components; the low-voltage electrical components include the electronic control unit.

[0115] The power supply 402 is used to control the low-voltage power supply to supply power to the low-voltage interface of the test platform 401; the power supply 402 supplies power to the low-voltage interface to enable the low-voltage circuit of the test platform 401 to operate; during the operation of the low-voltage circuit, the electronic control unit generates operation log data, and the operation log data includes operation fault codes.

[0116] The data reading and analyzing device 403 is used to read the operating fault codes from the diagnostic interface of the test platform 401 ; and to filter the operating fault codes based on the identified fault codes to determine the unidentified fault codes in the operating faults.

[0117] In some embodiments, before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform 401, the power supply 402 determines input voltage characteristics based on test requirements. The input voltage characteristics include the peak voltage, waveform, and duration of the input voltage. Subsequently, the power supply 402 controls the low-voltage power supply to supply power to the low-voltage interface of the test platform 401 according to the input voltage characteristics.

[0118] The low-voltage power supply includes a control host computer and a programmable power supply; the control host computer generates voltage modulation data based on input voltage characteristics; the programmable power supply outputs a supply voltage that meets the input voltage characteristics based on the voltage modulation data.

[0119] In some embodiments, the power supply 402 determines the overvoltage voltage characteristics based on the overvoltage test requirements, or determines the undervoltage voltage characteristics based on the undervoltage test requirements; wherein the overvoltage voltage is higher than the rated input voltage of the low voltage interface, and the undervoltage voltage is lower than the rated input voltage of the low voltage interface.

[0120] In some embodiments, the power supply 402 determines the fluctuating voltage characteristics based on the fluctuation test requirements, and the fluctuating voltage fluctuates up and down relative to the rated input voltage of the low-voltage interface. The up and down fluctuations are a slow rise from a first voltage value to a second voltage value, or a slow fall from the second voltage value to the first voltage value, or a periodic step jump or continuous fluctuation between the first voltage value and the second voltage value; wherein, the first voltage value is lower than the rated input voltage of the low-voltage interface, and the second voltage value is higher than the rated input voltage of the low-voltage interface.

[0121] In some embodiments, the operation log data also includes the generation time of the operation fault code. The vehicle location fault code determination system also includes a voltage measuring device. The voltage measuring device is used to measure the real-time voltage output by the programmable power supply. If the data analysis and reading device determines that the real-time voltage meets the input voltage characteristics, it determines that the operating period of the test platform 401 under the real-time voltage is a trustworthy period, and reads the corresponding operation fault code whose generation time falls within the trustworthy period from the diagnostic interface.

[0122] In some embodiments, after determining an unidentified fault code in an operational fault, the data analysis and reading device obtains a target input voltage characteristic corresponding to a time period in which the unidentified fault code occurs, and associates the unidentified fault code with the target input voltage characteristic.

[0123] In some embodiments, after determining an unidentified fault code in an operation fault, the data analysis and reading device obtains target log data in the operation log data and associates the unidentified fault code with the target log data; the target log data is the operation log data within a set time period before the unidentified fault code appears;

[0124] In some embodiments, before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform 401 , the data reading and analyzing device 403 deletes the operation log data or operation fault codes stored in the test platform 401 through the diagnostic interface.

[0125] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0126] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection according to one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0127] The embodiment of the present disclosure also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it can implement the method of any of the above method embodiments. Its execution method and beneficial effects are similar and will not be repeated here.

[0128] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device that includes the element.

[0129] The foregoing are merely specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not to be limited to the embodiments described herein, but is to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A method for determining an unknown vehicle fault code, characterized in that: include: Controlling a low-voltage power supply to supply power to a low-voltage interface of a test platform, the test platform being constructed based on a connection relationship between low-voltage electrical components of a target type vehicle and the low-voltage electrical components; the low-voltage electrical components including an electronic control unit; supplying power to the low-voltage interface to enable operation of a low-voltage circuit of the test platform; during operation of the low-voltage circuit, the electronic control unit generating operation log data, the operation log data including an operation fault code; Reading the operating fault code from the diagnostic interface of the test platform; The operating fault codes are filtered based on the identified fault codes to obtain unidentified fault codes.

2. The method according to claim 1, characterized in that Before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform, the method further includes: Determine input voltage characteristics based on test requirements, wherein the input voltage characteristics include a voltage peak, a waveform, and a duration of the input voltage; The controlling the low-voltage power supply to supply voltage to the test platform includes: The low-voltage power supply is controlled to supply power to the low-voltage interface of the test platform according to the input voltage characteristics.

3. The method according to claim 2, characterized in that The low-voltage power supply is a program-controlled power supply; The controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform according to the input voltage characteristics includes: generating voltage modulation data based on the input voltage characteristic; The voltage modulation data is used to control the programmable power supply so that the programmable power supply outputs a supply voltage that meets the input voltage characteristics.

4. The method according to claim 2, characterized in that The determining of the input voltage characteristics based on the test requirements includes: Determine an overvoltage voltage characteristic based on an overvoltage test requirement, or determine an undervoltage voltage characteristic based on an undervoltage test requirement; The overvoltage voltage is higher than the rated input voltage of the low-voltage interface, and the undervoltage voltage is lower than the rated input voltage of the low-voltage interface.

5. The method according to claim 2, characterized in that The determining of the input voltage characteristics based on the test requirements includes: Determine a fluctuating voltage characteristic based on a fluctuation test requirement, wherein the fluctuating voltage fluctuates up and down relative to a rated input voltage of the low-voltage interface, wherein the up and down fluctuation is a gradual increase from a first voltage value to a second voltage value, or a gradual decrease from the second voltage value to the first voltage value, or a periodic step jump or continuous fluctuating change between the first voltage value and the second voltage value; The first voltage value is lower than the rated input voltage of the low-voltage interface, and the second voltage value is higher than the rated input voltage of the low-voltage interface.

6. The method according to claim 3, characterized in that The operation log data also includes the generation time of the operation fault code; the method further includes: measuring the real-time voltage output by the programmable power supply, and determining that the operating period of the test platform under the real-time voltage is a trustworthy period if it is determined that the real-time voltage meets the input voltage characteristics; Reading the operating fault code from the diagnostic interface of the test platform includes: The operation fault code corresponding to the generation time within the trustworthy time period is read from the diagnostic interface.

7. The method according to any one of claims 2 to 6, characterized in that: After determining an unrecognized fault code in the operational fault, the method further includes: Obtaining a target input voltage characteristic corresponding to a time period during which the unidentified fault code appears; The unidentified fault code is associated with the target input voltage characteristic.

8. The method according to any one of claims 1 to 6, characterized in that After determining the unidentified fault code in the operating fault, the method further includes: Obtaining target log data from the operation log data; the target log data is the operation log data within a set time period before the unidentified fault code appears; The unidentified fault code is associated with the target log data.

9. The method according to any one of claims 1 to 6, characterized in that Before controlling the low-voltage power supply to supply power to the low-voltage interface of the test platform, the method further includes: The operation log data or operation fault codes stored in the test platform are deleted through the diagnostic interface.

10. A vehicle unknown fault code determination system, characterized in that: include: Test platform, power supply and data reading and analysis equipment; The test platform is constructed based on the low-voltage electrical components of the target type vehicle and the connection relationship between the low-voltage electrical components; the low-voltage electrical components include an electronic control unit; The power supply is used to control the low-voltage power supply to supply power to the low-voltage interface of the test platform; the power supply supplies power to the low-voltage interface to enable the low-voltage circuit of the test platform to operate; during the operation of the low-voltage circuit, the electronic control unit generates operation log data, and the operation log data includes an operation fault code; The data reading and analyzing device is used to read the operating fault code from the diagnostic interface of the test platform; and to filter the operating fault code based on the identified fault code to determine the unidentified fault code in the operating fault.

Images