• Hello Guest, welcome to the initial stages of our new platform!
    You can find some additional information about where we are in the process of migrating the board and setting up our new software here

    Thank you for being a part of our community!

Fuel/Spark tuning for LH 2.4/EZK with TunerPro!

I have bought these chips, do you think they work for lh2.4 and do you know which address I should program to
I haven't tried them, but those Microchip (formerly Atmel) AT27C256R-70PU chips have the same pinout and should work. Note - they're OTP One Time Programmable, so you can't erase and reuse them again.
do you know where i can find an ostrich2.0 i really need one i cant get ezk to work with cobra rtp r6the tracing dosent move . only fuel works
If fuel tracing works, then EZK tracing should work too. The EZK EPROM contains 4 identical copies of the software. If you have an original Bosch EPROM board in the EZK, then the 3rd copy of software is used (IIRC). For some of the aftermarket EPROM boards, the 1st copy of software is used. For cobra tracing, try each of the 4 copies and see if tracing works with one of them.

When burning EZK chips, it's best to update all 4 copies of the tables identically. You could update just the copy that's getting used, but it might cause confusion in the future, or if you swap the chip to an EZK with a different EPROM board.
 
I haven't tried them, but those Microchip (formerly Atmel) AT27C256R-70PU chips have the same pinout and should work. Note - they're OTP One Time Programmable, so you can't erase and reuse them again.

If fuel tracing works, then EZK tracing should work too. The EZK EPROM contains 4 identical copies of the software. If you have an original Bosch EPROM board in the EZK, then the 3rd copy of software is used (IIRC). For some of the aftermarket EPROM boards, the 1st copy of software is used. For cobra tracing, try each of the 4 copies and see if tracing works with one of them.

When burning EZK chips, it's best to update all 4 copies of the tables identically. You could update just the copy that's getting used, but it might cause confusion in the future, or if you swap the chip to an EZK with a different EPROM board.
i got it working now with the ezk box. took a little while for it to start tracing. but I don't know how to see if it knocks on the knock control map, do you know how it works?
 
Last edited:
Hi,

I'm trying to start tinkering with Lh system myself, I got myself chips and programer but I'm stuck trying do find xdf files, every link or forum seems dead by the time :/
Does anyone happen to own xdf files for
932 or 595?
 
While trying to figure out in detail how LH2.4 fueling works, I ran across an obscure 740 greenbook with some great information - see attached page pics.
TP31354-2 Greenbook.png

Edit: here's the extracted text for the fueling control. I was going to post the diag code details too, but it makes this post too long.

Lambda Control
A basic program in the control unit calculates the injection durations (Tbase see fig.), based on the information on engine load, i.e. the air mass and engine speed. The resulting opening time is not used directly to control the injectors, but is modified in a lambda control circuit where the signal from the oxygen sensor is used to finely adjust the injection times to give the optimum fuel/air ratio (λ = 1).

The oxygen sensor registers the oxygen content of the exhaust gases, which gives a measurement of the fuelvair mixture ratio. The sensor sends a signal to the lambda control circuit in proportion to the oxygen content of the exhaust gases. This signal is converted into a factor Kint (integrator) which is used to calculate the actual injection times. In simple terrns, this is the basic time multiplied by the integrator. The ratio λ = 1 means that the mixture of air and fuel is perfect. If λ> 1, the engine is not receiving enough fuel, and the lambda control lengthens the injection time (Kint > 1). If λ < 1, the engine is receiving too much fuel, and the injection time is reduced (Kint<1).

This type of adjustment is very quick, and can take place several times per second. The lambda control circuit can make a maximum adjustment of +25% in the injection time calculated in the basic program ("Kint" = ±25%)

Adaptive Lambda Control
Certain factors which affect the fuel/air mix, for example the setting of the injectors, are very slow to have an effect. To compensate for this, the lambda control is supplemented with "adaptive" (self-learning) functions.

When the car is new, factor Kint (integrator) will vary in a cycle of, for example, ±5% around a nominal mean when the lambda control is working.

When setting the injectors, the integrator is displaced and works, for example, between +20% and +10%, i.e. still with an amplitude of ±5% but with a 15% shift in relation to the original nominal mean.

This permanent change can be transferred to the adaptive functions, which means that after adaptive corrections, the integrator can again work around its nominal mean and hence have access to its entire adjustment range of ±25 %.

--------------------
The adaptive functions are of two types, an additive factor (±1.0 ms on the injection times) Tadd,adap working in the idle range and a multiplicative factor (±25% of the injection times) Fmult,adap working in the part load range.

Corrections with the additive factor correspond to the basic setting, which was previously set manually using potentiometers on the air mass meter. The additive adaptations are rapid and give corrections to the right value within a few minutes.

Corrections with the multiplicative function compensate for long-term changes in the engine or its control system. In contrast to the additive adaptations, it is slow and needs some hours to compensate fully for a fault.

The adaptive adjustments of the injection time remain in the control unit after the car has stopped, which means that the right mixture ratio is set immediately after the start before the oxygen sensor has become warm enough to function. No CO control is required on the car. Another advantage is that the mixture ratio remains correct immediately after the fuel has been cut off on engine braking. when the lambda probe is disconnected from the control unit so as not to give any incorrect signals. This would normally cause a delay before the lambda control has set the fuel/air mixture to the right value.

The adaptive functions have a limited capacity for compensation, and if these are exceeded, this may cause the control unit to give a fault code. Two different fault codes may be caused by the adaptive functions: 2-3-1 and 2-3-2.

Fault code 2-3-1 is caused when the capacity of the multiplicative function is about to be exceeded, but fault code 2-3-2 indicates when the limit value of the additive function is exceeded.

[box 1]
The injection time is known as Ti
This can be expressed as:
Ti = Tbase * Kint * Fmult,adap + Tadd,adap
Tbase Time calculated in the basic program of the control unit; depends on air quantity, engine temperature and speed.
Kint Integrator, a factor which controls the injection times so that the fuel/air mixture ratio remains optimum (λ = 1).
Tadd,adap Additive factor, adjustment at low speeds. Makes lambda control easier by holding the integrator as near to 1 as possible.
Fmult,adap Multiplicative factor, adjustment at high speeds. Makes lambda control easier by holding the integrator as near to 1 as possible.

Adaptive Idle Control
A similar function applies to the idle valve. In time, deposits and wear affect the throttle so that a greater or lesser quantity of air passes through. Instead of adjusting this from a pre-programmed value, the control unit gives a signal which is based on previous driving information. The signal affects the idle valve so that it opens exactly the amount required for the engine to maintain the right idle speed.
 

Attachments

  • TP31354-2 LH2.4 diag codes 1.jpg
    TP31354-2 LH2.4 diag codes 1.jpg
    234.4 KB · Views: 38
  • TP31354-2 LH2.4 diag codes 2.jpg
    TP31354-2 LH2.4 diag codes 2.jpg
    207.8 KB · Views: 34
  • TP31354-2 LH2.4 diag codes 3.jpg
    TP31354-2 LH2.4 diag codes 3.jpg
    234.6 KB · Views: 32
  • TP31354-2 LH2.4 lambda control 1.jpg
    TP31354-2 LH2.4 lambda control 1.jpg
    181.6 KB · Views: 29
  • TP31354-2 LH2.4 lambda control 2.jpg
    TP31354-2 LH2.4 lambda control 2.jpg
    196.1 KB · Views: 32
Last edited:
Finally got around to using ipdown's software, but the damn thing isn't letting me save changes. I can export, but then when I open it to check, it is just the stock file for what I chose to import

What am I doing wrong
 
Finally got around to using ipdown's software, but the damn thing isn't letting me save changes. I can export, but then when I open it to check, it is just the stock file for what I chose to import

What am I doing wrong
my lh2.4 editor works fine but i dont use it anymore i use the checksum.dll for tunerpro now instead but send me a dm if you want me to send a copy off my editor or a dll
 

Is this a replacement for the ostrich and/or the dwindling supply of good chips?
99% of the benefit of the ostrich is the ability to trace what data is being accessed. You cannot get that info with that device or tune these ECUs well without it. You can still get DIP 28 eeprom chips brand new from reputable component sources after you've tuned the car.
 
You can't, at least with the available hardware/software. The cobra/ostrich doesn't output the hit map data in a way that can be datalogged despite what it looks like it is doing. You need a separate data acquisition device which needs to be fed into tunerpro seperately. Something that can input a load and RPM and it will then be able to plot afr points on a map.
 
You can't, at least with the available hardware/software. The cobra/ostrich doesn't output the hit map data in a way that can be datalogged despite what it looks like it is doing. You need a separate data acquisition device which needs to be fed into tunerpro seperately. Something that can input a load and RPM and it will then be able to plot afr points on a map.
So this should work ? https://www.google.com/url?q=https:...QQFnoECCYQAQ&usg=AOvVaw1AZm942dxdiAvHB-tGMtly
 
No. The problem is that address hit tracing with a Moates Ostrich in TunerPro is somewhat of a hack. As far as I know, it can't be combined with .adx serial monitoring/logging. You could join tunerpro.net and ask:
"Is there a way to include the Moates Ostrich 2.0 Address Hit Trace in a wideband O2 sensor .adx log?"
 
No. The problem is that address hit tracing with a Moates Ostrich in TunerPro is somewhat of a hack. As far as I know, it can't be combined with .adx serial monitoring/logging. You could join tunerpro.net and ask:
"Is there a way to include the Moates Ostrich 2.0 Address Hit Trace in a wideband O2 sensor .adx log?"
Om using cobra rtp motronic r6 its not the same as ostrich. This have analog inputs
 
Back
Top