Verification method and device for injector compensation codes

Abstract

This invention discloses a method and apparatus for verifying injector compensation codes, relating to the field of engine fuel system testing. The method includes the following steps: establishing a vehicle simulation model; forming test cases based on the required test conditions; setting the test duration and test parameters for each test condition within the test cases; adjusting the operating parameters of the vehicle simulation model according to the test cases; collecting the simulated injection pulse width under different conditions; comparing the simulated injection pulse width under different conditions with the set target pulse width for that condition to obtain the corrected pulse width for that condition. This invention not only improves the verification accuracy and efficiency of injectors but also enables stable operating performance under varying adverse conditions and achieves precise control of the injection quantity.

Description

Technical Field

[0001] This invention relates to the field of engine fuel system testing, and specifically to a method and apparatus for verifying injector compensation codes. Background Technology

[0002] Existing methods for verifying fuel injector compensation codes in automobile engines generally involve:

[0003] Testers verified the injector compensation code correction function by simulating injector injection with a load cell and acquiring data using an oscilloscope. This method involves setting a standard injection pulse width and timing, simulating injection with a load cell, and acquiring the pulse width and timing data with an oscilloscope. By comparing this data with the required injection pulse width and timing, the injector compensation code correction value can be obtained, ensuring the injector operates with the required injection volume under various conditions.

[0004] The drawback of the above method is:

[0005] (1) When it is necessary to collect multiple injection pulse width and timing signals for analysis, errors are easily generated by reading the oscilloscope, which reduces the accuracy of injection pulse width and timing.

[0006] (2) When special working conditions need to be injected for verification, the calibration quantity needs to be manually modified for injection, and only one working condition can be met at a time, resulting in low work efficiency.

[0007] Therefore, it can be seen that the existing verification methods for injector compensation codes have low verification accuracy and low efficiency. Summary of the Invention

[0008] In view of the deficiencies in the existing technology, the technical problem solved by the present invention is: how to improve the verification accuracy and verification efficiency of injector compensation codes.

[0009] To achieve the above objectives, in a first aspect, embodiments of this application provide a method for verifying injector compensation codes. The method includes the following steps: establishing a vehicle simulation model, forming test cases according to the required test conditions, and setting the test duration and test parameters for each test condition in the test cases; adjusting the working parameters of the vehicle simulation model according to the test cases, collecting the simulated injection pulse width under different conditions, and comparing the simulated injection pulse width under different conditions with the set target pulse width for that condition to obtain the corrected pulse width for that condition.

[0010] In conjunction with the first aspect, in one embodiment, the vehicle simulation model includes an engine model, a vehicle controller model, and a virtual vehicle model corresponding to the vehicle structure;

[0011] The process of establishing a whole vehicle simulation model includes:

[0012] A virtual model of the vehicle and an engine model are built on a simulation bench. Both the virtual model and the engine model communicate with the simulation bench through boards to generate vehicle simulation signals. The host computer and the vehicle controller model communicate with the simulation bench respectively.

[0013] In conjunction with the first aspect, in one embodiment, the communication method between the host computer and the simulation test bench is local area network communication, and the communication method between the vehicle controller and the simulation test bench is wired communication.

[0014] In conjunction with the first aspect, in one embodiment, the simulated fuel injection pulse width acquisition process includes: presetting different stable level corresponding to level sampling ranges, wherein the lower limit of the level sampling range is above the lowest level, and the upper limit of the level sampling range is 0.5 to 2V higher than the lower limit; and selecting the highest precision level within the level sampling range according to the sampling accuracy under different stable level level sampling ranges.

[0015] In conjunction with the first aspect, in one implementation, the process of forming test cases according to the required test conditions and setting the test duration and test parameters for each test condition in the test cases includes: forming a configuration file with the test information, test duration and test parameters for each test condition, and associating all configuration files according to the test order to form test cases.

[0016] In conjunction with the first aspect, in one implementation, the test information for each test condition includes the condition type and the climate environment of the condition.

[0017] In conjunction with the first aspect, in one implementation, the operating conditions include: highway driving, national road travel, mountain road operation, traffic congestion, and vehicle parking.

[0018] The operating conditions and climate environment include: temperature, humidity, and altitude;

[0019] Temperature includes normal temperature (which remains constant or changes), extreme high temperature, and extreme low temperature;

[0020] Humidity includes normal humidity (which remains constant or changes), extremely high humidity, and extremely low humidity.

[0021] Altitude includes normal altitude (which remains constant or changes), extreme high altitude, and extreme low altitude.

[0022] In conjunction with the first aspect, in one implementation, the operating condition type further includes a fault operating condition.

[0023] In conjunction with the first aspect, in one embodiment, the test information for each test condition further includes a cyclic mode, which includes at least one of WHSC, WHTC, and WNTE.

[0024] Secondly, embodiments of this application provide a verification device for injector compensation codes, the device including a simulation model building device, a test case generation module and a test case execution module;

[0025] The simulation model building device is used to: implement the process of building a whole vehicle simulation model provided in the first aspect;

[0026] The test case generation module is used to: implement the process provided in the first aspect of generating test cases based on the required test conditions and setting the test duration and test parameters for each test condition in the test cases;

[0027] The test case execution module is used to: implement the process provided in the first aspect of adjusting the working parameters of the whole vehicle simulation model according to the test cases, collecting the simulated fuel injection pulse width under different working conditions, comparing the simulated fuel injection pulse width under different working conditions with the set target pulse width of the working condition, and obtaining the corrected pulse width of the working condition.

[0028] Compared with the prior art, the advantages of the present invention are as follows:

[0029] Compared with existing technologies that use load cells and oscilloscopes to acquire fuel injection pulse width, this invention acquires fuel injection pulse width by building a whole vehicle simulation model (e.g., hardware-in-the-loop HIL). This method can achieve automatic fuel injection, automatic acquisition, and automatic monitoring according to a preset workflow, and can also record the injection pulse width and timing data of the fuel injector in detail. That is, compared with reading from an oscilloscope, the accuracy of fuel injection and acquisition through simulation is higher, and there is basically no error.

[0030] Meanwhile, compared to existing technologies that require multiple operations to verify the injection pulse width under different operating conditions, this invention generates test cases based on the required test conditions and sets the test duration for each test condition within the test cases. After adjusting the working parameters of the vehicle simulation model according to the test cases, the simulated injection pulse width under different operating conditions is collected. In other words, this invention can automatically and continuously simulate and verify the injector under different operating conditions. Specific operating conditions include scenarios such as highway driving, national highway driving, mountain road operation, traffic congestion, and vehicle parking; and environmental conditions such as extreme high and low temperatures, humidity differences, and altitude variations.

[0031] Therefore, this invention can not only improve the verification accuracy and efficiency of the injector, but also maintain stable operating performance under varying adverse conditions and achieve precise control of the injection quantity. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a schematic diagram illustrating the principle of fuel injection pulse width acquisition in the embodiments of this application;

[0034] Figure 2 This is a flowchart illustrating the method for verifying the injector compensation code in an embodiment of this application.

[0035] Figure 3 This is a schematic diagram of the hardware structure of the fuel injector compensation code verification device involved in the embodiments of this application. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0037] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0039] In a first aspect, embodiments of this application provide a method for verifying injector compensation codes. The method includes the following steps: establishing a vehicle simulation model, forming test cases according to the required test conditions, and setting the test duration and test parameters for each test condition in the test cases; adjusting the working parameters of the vehicle simulation model according to the test cases, collecting the simulated injection pulse width under different conditions, and comparing the simulated injection pulse width under different conditions with the set target pulse width for that condition to obtain the corrected pulse width for that condition.

[0040] Therefore, compared with the existing technology of acquiring fuel injection pulse width through load cell and oscilloscope, the present invention acquires fuel injection pulse width by building a whole vehicle simulation model (e.g., hardware-in-the-loop HIL). This method can realize automatic fuel injection, automatic acquisition and automatic monitoring according to the preset workflow, and can also record the injection pulse width and timing data of the fuel injector in detail. That is, compared with the method of reading oscilloscope, the accuracy of fuel injection and acquisition through simulation is higher and there is basically no error.

[0041] Meanwhile, compared to existing technologies that require multiple operations to verify the injection pulse width under different operating conditions, this invention generates test cases based on the required test conditions and sets the test duration for each test condition within the test cases. After adjusting the working parameters of the vehicle simulation model according to the test cases, the simulated injection pulse width under different operating conditions is collected. In other words, this invention can automatically and continuously simulate and verify the injector under different operating conditions. Specific operating conditions include scenarios such as highway driving, national highway driving, mountain road operation, traffic congestion, and vehicle parking; and environmental conditions such as extreme high and low temperatures, humidity differences, and altitude variations.

[0042] Therefore, this invention can not only improve the verification accuracy and efficiency of the injector, but also maintain stable operating performance under varying adverse conditions and achieve precise control of the injection quantity.

[0043] In one embodiment, the vehicle simulation model in the above method includes a virtual vehicle model corresponding to the vehicle structure, an engine model, and a vehicle controller model (e.g., ECU).

[0044] Based on this, the process of establishing a whole vehicle simulation model in the above method includes:

[0045] A virtual model of the vehicle and an engine are built on a high-intensity interconnect (HIL) simulation bench. Related vehicle simulation signals are generated through communication boards on the HIL that communicate with the virtual model of the vehicle and the engine.

[0046] The host computer and the vehicle controller model communicate with the simulation bench. The communication method between the host computer and the simulation bench can be local area network communication, and the communication method between the vehicle controller and the simulation bench can be customized wiring harness.

[0047] In one embodiment, the acquisition process of the simulated fuel injection pulse width in the above method includes: presetting different stable levels corresponding to level sampling ranges, the lower limit of the level sampling range being above the lowest level, and the upper limit of the level sampling range being 0.5 to 2V higher than the lower limit; and selecting the highest precision level within the level sampling range according to the sampling accuracy under different stable levels.

[0048] For example, see Figure 1 As shown, four levels are set: level A (0.5~1), level B (1~2), the upper and lower levels TA and LA near the low level A, and the upper and lower levels TB and LB near the high level B. That is, the level sampling range is from TA to LB (i.e., the upper limit is LB and the lower limit is TA). Point b in the figure is the maximum level point, and point a is the fuel injector start injection point. In this case, the acquisition method can be: acquiring the LA-TA segment, LB-TA segment, LA-TB segment, and LB-TB segment, thereby obtaining the injection cycle, main injection pulse width, pre-injection pulse width, and relative timing, etc.

[0049] See Figure 1 As can be seen, the voltage level will continuously increase before the highest point b. At this time, the current of the solenoid valve will continuously increase, and the suction force generated will also continuously increase. Therefore, the valve will continuously open until it reaches a stable voltage level V before it is fully opened. At this time, it will maintain this state until the injector stops injecting fuel.

[0050] Furthermore, since the injector can maintain the maximum opening angle of the solenoid valve at voltage V, the voltage level at point a is between the voltage level V and the maximum voltage level. During our normal testing, the injector voltage is 24V when stable, so the voltage V is 24V. Therefore, the slope of the ab segment tends to be smooth. Thus, selecting the LA to TA segment is the most suitable range, as the injection pulse width obtained under these conditions is the most accurate. After actual oscilloscope acquisition, it can be found that when selecting the LB-TA, LA-TB, and LB-TB segments, the pulse width is too short and not accurate enough.

[0051] If the injector voltage is 12V when it is stable during the test, the slope of segment ab is relatively low, so the difference between LA and LB will be large. If the injector voltage is 36V when it is stable during the test, the slope of segment ab is very steep, so the difference between LA and LB will not be significant.

[0052] In one embodiment, the process of forming test cases according to the required test conditions and setting the test duration and test parameters for each test condition in the above method includes: forming a configuration file with the test information, test duration and test parameters for each test condition, and associating all configuration files according to the test order to form test cases.

[0053] Furthermore, the test information for each of the above test conditions includes the type of test condition and the climate environment of the test condition.

[0054] Specifically, the operating conditions include: highway driving, national road travel, mountain road operation, traffic congestion, and vehicle parking;

[0055] Operating climate conditions include: temperature, humidity, and altitude;

[0056] Temperature includes normal temperature (which remains constant or changes), extreme high temperature, and extreme low temperature;

[0057] Humidity includes normal humidity (which remains constant or changes), extremely high humidity, and extremely low humidity.

[0058] Altitude includes normal altitude (which remains constant or changes), extreme high altitude, and extreme low altitude.

[0059] The specific values ​​corresponding to normal, extremely high, and extremely low are values ​​obtained based on specific circumstances and are not limited here.

[0060] Furthermore, the operating conditions also include: fault conditions, such as nozzle blockage, fuel leakage, etc.

[0061] Furthermore, the test information for each of the above test conditions also includes a cyclic mode, which includes at least one of WHSC, WHTC, and WNTE designed according to national standards.

[0062] Therefore, it can be seen that the present invention can obtain pulse width correction information under different operating conditions, and with the design of the cycle mode, a relatively complete injector pulse width diagram applicable to various actual situations can be obtained.

[0063] See below. Figure 2 As shown, the above method is illustrated through a specific embodiment.

[0064] S1: Build a full vehicle simulation model on the HIL platform. In addition to the above-mentioned content (building the model and establishing communication), the building process also includes the simulation environment of the engine control system, including sensors (such as oxygen sensors, throttle position sensors, etc.), actuators (such as fuel injectors, igniters, etc.) and control algorithms; ensure that the simulation environment can accurately simulate the working environment of the actual vehicle, including different working conditions and environmental conditions.

[0065] It is important to note that the injector model required for the engine model in the vehicle simulation model must be appropriately selected to ensure that it can accurately simulate the working principle and behavior of the injector. Factors such as injector response time, injection quantity, spray characteristics, and the dynamic characteristics of the injector under different operating conditions should be considered; direct connection to the actual injector load is preferred.

[0066] S2: Generate test cases based on the required test conditions, and set the test duration and test parameters for each test condition in the test cases; thereby ensuring test coverage and accuracy, improving software quality and stability, and reducing test costs and time consumption.

[0067] Specifically, test cases can be developed and executed through ECU-TEST software, which automatically runs the vehicle under various set operating conditions and collects fuel injection pulse width and timing, thereby achieving the effect of automated testing.

[0068] S3: After adjusting the working parameters of the whole vehicle simulation model according to the test cases, the simulated fuel injection pulse width under different working conditions is collected. The collected data can be displayed on an oscilloscope through the HIL test bench. The waveform obtained in this way is more stable and more accurate than that of a traditional external oscilloscope.

[0069] S4: Compare the simulated injection pulse width under different working conditions with the set target pulse width for that working condition to obtain the corrected pulse width for that working condition.

[0070] The verification results of the injector pulse width correction in this embodiment are as follows:

[0071] (1) Correction of injection pulse width (main injection / pre-injection / rear injection / tail injection) and timing under disabled conditions.

[0072] When the corrected pulse width is turned off:

[0073] Actual tailpipe pulse width = 227µs

[0074] Actual post-spray pulse width = 247µs

[0075] Actual post-spray pulse width = 268µs

[0076] Target tail jet pulse width = 227us

[0077] Target post-spray pulse width = 247us

[0078] Target post-spray 2 pulse width = 268us

[0079] Pulse width deviation = 0

[0080] This is the pulse width without any correction. You can see that the required value, the target value, and the actual collected value are completely consistent.

[0081] When the time correction is turned off:

[0082] Actual tailpipe timing = 350us

[0083] Actual tailpipe timing correction = 0

[0084] Actual rear-spray timing = 1876µs

[0085] Actual rear spray timing correction = 0

[0086] Actual rear-spray timing = 4757µs

[0087] Actual rear-spray timing correction = 0

[0088] Target tailpipe timing = 350us

[0089] Target rear-spray timing = 1876us

[0090] Target rear-spray timing = 4757us

[0091] When timing correction is turned off, the actual timing and the required timing are completely consistent. (2) All single pulse width correction detection / minimum injection pulse width correction

[0092] Detection and correction of the effect after enabling:

[0093] Pulse width correction 1

[0094] Actual tail jet pulse width = 238µs

[0095] Actual post-spray pulse width = 258µs

[0096] Actual post-spray pulse width = 279µs

[0097] Target tail jet pulse width = 227us

[0098] Demand for tailpipe pulse width = 227µs

[0099] Target post-spray pulse width = 247us

[0100] Requires a pulse width of 1 after spraying = 247us

[0101] Target post-spray 2 pulse width = 268us

[0102] The required pulse width is 268µs after spraying.

[0103] Pulse width deviation = 11

[0104] As can be seen, after correction, the difference between the actual pulse width and the target pulse width is 11, which is almost the same as the pulse width deviation.

[0105] Pulse width correction 2

[0106] Actual tailpipe pulse width = 234µs

[0107] Actual post-spray pulse width = 254µs

[0108] Actual post-spray pulse width = 275µs

[0109] Standard tail jet pulse width = 227µs

[0110] Demand for tailpipe pulse width = 227µs

[0111] Target post-spray pulse width = 247us

[0112] Requires a pulse width of 1 after spraying = 247us

[0113] Target post-spray 2 pulse width = 268us

[0114] The required pulse width is 268µs after spraying.

[0115] Pulse width deviation = 6

[0116] As can be seen, after correction, the difference between the actual pulse width and the target pulse width is 6, which is almost the same as the pulse width deviation.

[0117] Therefore, it can be seen that the corrected pulse width (pulse width deviation) obtained by the above method is basically the same as the actual pulse width deviation, that is, the verification accuracy of the above method is very high.

[0118] Secondly, embodiments of this application also provide a device for verifying injector compensation codes, which is used to implement the injector compensation code verification method mentioned in the first aspect.

[0119] Specifically, the device includes a simulation model building device, a test case generation module, and a test case execution module;

[0120] The simulation model building device is used to: implement the process of building a whole vehicle simulation model as mentioned in the first aspect;

[0121] The test case generation module is used to: implement the process mentioned in the first aspect of generating test cases based on the required test conditions and setting the test duration and test parameters for each test condition in the test cases;

[0122] The test case execution module is used to: implement the process mentioned in the first aspect of adjusting the working parameters of the whole vehicle simulation model according to the test cases, collecting the simulated fuel injection pulse width under different working conditions, comparing the simulated fuel injection pulse width under different working conditions with the set target pulse width of the working condition, and obtaining the corrected pulse width of the working condition.

[0123] The functions of each module in the above-mentioned injector compensation code verification device correspond to the steps in the above-mentioned injector compensation code verification method embodiment, and their functions and implementation processes will not be described in detail here.

[0124] Thirdly, embodiments of this application provide a device for verifying injector compensation codes. The device for verifying injector compensation codes can be a personal computer (PC), a laptop computer, a server, or other devices with data processing capabilities.

[0125] Reference Figure 3 , Figure 3 This is a schematic diagram of the hardware structure of the fuel injector compensation code verification device involved in the embodiments of this application. In the embodiments of this application, the fuel injector compensation code verification device may include a processor, a memory, a communication interface, and a communication bus.

[0126] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.

[0127] The communication interface includes input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal components of the fuel injector compensation code verification device, as well as interfaces for interconnecting the fuel injector compensation code verification device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.

[0128] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0129] The processor can be a general-purpose processor, which can call the injector compensation code verification program stored in the memory and execute the injector compensation code verification method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the injector compensation code verification program is called can be referred to in the various embodiments of the injector compensation code verification method of this application, and will not be repeated here.

[0130] Those skilled in the art will understand that Figure 3 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0131] Fourthly, embodiments of this application also provide a computer-readable storage medium.

[0132] The computer-readable storage medium of this application stores a verification program for injector compensation codes, wherein when the verification program for injector compensation codes is executed by a processor, it implements the steps of the above-described method for verifying injector compensation codes.

[0133] The method implemented when the injector compensation code verification procedure is executed can be referred to in various embodiments of the injector compensation code verification method of this application, and will not be repeated here.

[0134] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0135] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0136] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.

[0137] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.

[0138] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0139] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0140] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.

[0141] The above are merely specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the scope of the claims.

Claims

1. A method for verifying injector compensation codes, characterized in that, The method includes the following steps: establishing a whole vehicle simulation model, forming test cases according to the required test conditions, and setting the test duration and test parameters for each test condition in the test cases; adjusting the working parameters of the whole vehicle simulation model according to the test cases, collecting the simulated fuel injection pulse width under different conditions, comparing the simulated fuel injection pulse width under different conditions with the set target pulse width for that condition, and obtaining the corrected pulse width for that condition. The simulated fuel injection pulse width acquisition process includes: presetting different stable level corresponding to level sampling ranges, with the lower limit of the level sampling range above the lowest level and the upper limit of the level sampling range being 0.5~2V higher than the lower limit; and selecting the highest precision level within the level sampling range based on the sampling accuracy of different stable levels.

2. The method for verifying the injector compensation code as described in claim 1, characterized in that: The vehicle simulation model includes an engine model, a vehicle controller model, and a virtual vehicle model corresponding to the vehicle structure. The process of establishing a whole vehicle simulation model includes: A virtual model of the vehicle and an engine model are built on a simulation bench. Both the virtual model and the engine model communicate with the simulation bench through boards, which generate vehicle simulation signals. The host computer and the vehicle controller model communicate with the simulation bench respectively.

3. The method for verifying the injector compensation code as described in claim 2, characterized in that: The communication method between the host computer and the simulation bench is local area network communication, while the communication method between the vehicle controller and the simulation bench is wired communication.

4. The method for verifying the injector compensation code as described in claim 1, characterized in that, The process of generating test cases based on the required test conditions and setting the test duration and test parameters for each test condition in the test cases includes: forming a configuration file with the test information, test duration and test parameters for each test condition, and associating all configuration files according to the test order to form test cases.

5. The method for verifying the injector compensation code as described in claim 4, characterized in that: The test information for each test condition includes the type of test condition and the climate environment of the test condition.

6. The method for verifying the injector compensation code as described in claim 5, characterized in that: The operating conditions include: highway driving, national road travel, mountain road operation, traffic congestion, and vehicle parking; The operating conditions and climate environment include: temperature, humidity, and altitude; Temperature includes normal temperature (which remains constant or changes), extreme high temperature, and extreme low temperature; Humidity includes normal humidity (which remains constant or changes), extremely high humidity, and extremely low humidity. Altitude includes normal altitude (which remains constant or changes), extreme high altitude, and extreme low altitude.

7. The method for verifying the injector compensation code as described in claim 6, characterized in that: The operating condition types also include fault operating conditions.

8. The method for verifying injector compensation codes as described in claim 5, characterized in that: The test information for each test condition also includes a loop mode, which includes at least one of WHSC, WHTC, and WNTE.

9. A device for verifying injector compensation codes, characterized in that: The device includes a simulation model building device, a test case generation module, and a test case execution module; The simulation model building device is used to: implement the process of building a whole vehicle simulation model as described in any one of claims 1 to 8; The test case generation module is used to: implement the process described in any one of claims 1 to 8, which involves generating test cases based on the required test conditions and setting the test duration and test parameters for each test condition in the test cases; The test case execution module is used to: implement the process described in any one of claims 1 to 8, after adjusting the working parameters of the whole vehicle simulation model according to the test case, collecting the simulated fuel injection pulse width under different working conditions, comparing the simulated fuel injection pulse width under different working conditions with the set target pulse width of the working condition, and obtaining the corrected pulse width of the working condition.

Images