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

[threewagons]

Hm, I want to do ADX extension, because my plan is tune AFR first, then will tune ignition for power

I imagine it's possible since the cobra has 3 analog inputs and they have an ADX listed on their site but it will take a little work to get it set up properly

 

[EFbI4]

Anyone know, can I find some map or table, where I will see knock if it comes? That's important

 

[threewagons]

You should see it on the first knock control map when tracing but I haven't been able to make it knock on e85 so I can't speak to that personally. If you're running pump gas i'd get a knocksense and put the LED somewhere visible

 

[EFbI4]

You should see it on the first knock control map when tracing but I haven't been able to make it knock on e85 so I can't speak to that personally. If you're running pump gas i'd get a knocksense and put the LED somewhere visible

This?

 

[threewagons]

No, I meant in the EZK bin

This?

 

[EFbI4]

No, I meant in the EZK bin

Can you upload your xdf to your favorite cloud and send a link, please?

 

[threewagons]

Can you upload your xdf to your favorite cloud and send a link, please?

I've attached it here, let me know if it doesn't work

 

[EFbI4]

I've attached it here, let me know if it doesn't work

All works, thank you!

 

[EFbI4]

I am also looking for this tool...as well as LH Logger

Do you coder or so? If yes - maybe I have something for you.

 

[EFbI4]

Anyone have ADX with gauges? RPM, CLT, TQ, Load? Something?

 

[EFbI4]

Well, guys, I have a problem and can't resolve it.

Problem with data tracing for wideband controller.

I'll cut it, because there will be a lot of screenshots.


What I want: I want to measure AFR in every block of fuel table.
What I have: Innovate LC2 and adx for it, 962 xdf, adapted 962 bin.
What I'd already do:

1. Prepare ADX, create new values: RPM and load, you can see data type and other settings on screenshots..

You can see - AFR value already exist and works correct, AFR reading from TunerPro and from Innovate LogWorks - same.

2. Then I create history table, where Z object is AFR, X and Y - RPM and LOAD values, which I created earlier.

3. Then I prepare my XDF to work with ADX

Prepare values in fuel map - floating point, that's all stuff, you can see on screenshots

Then I linked rows and colums with ADX

4. And finally! I have some shit:

Tracing fuel table keep working fine, but adx tracing goes to hell and fill just one value in wrong place.



Can anyone tell me what I do wrong??

 

[bobxyz]

I've never done much with TunerPro, but I expect to at some point. Does this thread or this one from gearhead-efi.com help?

Edit: I did a little more reading and what you want to do may not be possible.

1) For cars that can provide a serial diagnostic data stream, TunerPro supports ADX definitions, where the definition tells how to generate serial commands and how to parse the serial response into named data fields. For example, RPM, load, temperature, ign timing, etc. would all be normal stuff that could come from the diagnostic data stream.

2) The Innovate WBO2 gauge supports a very simple serial diagnostic datastream that consists of just the current AFR reading. Your trying to add Load/RPM to the Innovate ADX won't work because the datastream doesn't include them.

3) The Address Tracing feature of the Moates Ostrich 2.0 is somewhat of a hack. It seems to be hardcoded into the TunerPro software and can provide realtime active address mapping to show what regions of EPROM memory are getting accessed. This works with XDF files that define the layout and contents of the EPROM memory.

4) What you'd like is a way to combine the current Ostrich address with the other live ADX data stream values to create a 2D actual AFR table. I didn't see any way of getting the Ostrich address into the ADX. You'll need to ask if this is possible on forum.tunerpro.net

 

[EFbI4]

Well, I researched and... Stock jetronic can't do it.
I sell CobraRTP now and will build MS. Again I'm tired to fight with jetronic.

 

[baggins798]

How do I raise the rev limit? Back between pages 100-110 lookforjoe asked the same thing. There's this:

6055 RPM Limiter (rpm fuelcut threshold)
39 is original value this gives appx 6350 off and 6200 back on
38 = 6490
37 = 6640 Do remember that some EZKs have a low RPM
36 = 6780 limit too...just above the 6350 of the LH
35 = 6920
34 = 7070
33 = 7230
32 = 7390
31 = 7550

Is it that easy? I notice that the fuel map ends at 6293 rpm, so what happens when you go off the map? Does it use the last columns values?

 

[redblockpowered]

How do I raise the rev limit? Back between pages 100-110 lookforjoe asked the same thing. There's this:

6055 RPM Limiter (rpm fuelcut threshold)
39 is original value this gives appx 6350 off and 6200 back on
38 = 6490
37 = 6640 Do remember that some EZKs have a low RPM
36 = 6780 limit too...just above the 6350 of the LH
35 = 6920
34 = 7070
33 = 7230
32 = 7390
31 = 7550

Is it that easy? I notice that the fuel map ends at 6293 rpm, so what happens when you go off the map? Does it use the last columns values?

Weird stuff happens when you go off the map. Depends on what load level you're at, sometimes wacky fuel trim stuff happens sometimes not. I wouldn't recommend it under any circumstance. The 950 ecu from B204FT has a main fuel map axis that goes to 7013? around 7000 rpm. This should be good enough for most applications.

EZK axes might need to be changed too depending on how high you're going (IIRC they hold the timing value past the end of the RPM axis). But I don't remember off the top of my head and it might vary based on starting point.

 

[baggins798]

Thanks!
Regarding the EZK rev limit, back on page 84:

Mine to, also has anyone else played with the rev limit that comes in the xdf? I have changed all 4 tables to 3000rpm and the car will quite happily rev out well past 3000rpm. Also in the 208 xdf there is the knock sensitivity table, does this work?

Hi
Regarding the rev limiter that turned out to be just hearsay.
The rev limiter is probably just a constant somewhere like in the LH bins.

YS
Jaybee

The rev limit stuff is wrong, as you can see. There's something else that actually controls it that no one has found yet. There is some EZK bin based off of I think a 207 that either doesn't have a rev limit or has something above 7000rpm. I don't know what EZK unit/bin it is, though... It's probably what the chip tuners use as a base for their high rpm stuff.

So this does nothing?

05EB RPM Limiter Hard Cut (177, 148 )
Increasing this constant will increase rpm limit
stock value in bin :
208 = 0x66 (102) = 6500 rpm 7000 = 142
177 = 0x72 (114) = 6650 rpm 7500 = 181
140 = 0x5F (95) = 6410 rpm 8000 = 221
169 = 0x5F (95) = 6410 rpm 8430 = 255
When this is set to max value 0xFF (or 255 as integer) the rpm limit will be raised to appx 8400 rpm.
It will be hard cut of all sparks so best to have LH limiter 1-200 rpm lower

Perhaps they're talking about an earlier xdf that had something else mislabelled.

 

[esmth]

which bins do you use? I've progressively been raising my rev limit with no issues with LH 946 and ezk 196. I've actually done the opposite as recommended and have the EZK limter be lower than LH. It seems less aggressive on the motor. (not sure if correct ) It is not a full spark cut, it seems to cut every other spark or something. 7200 RPM rn.

 

[redblockpowered]

Thanks!
Regarding the EZK rev limit, back on page 84:







So this does nothing?

05EB RPM Limiter Hard Cut (177, 148 )
Increasing this constant will increase rpm limit
stock value in bin :
208 = 0x66 (102) = 6500 rpm 7000 = 142
177 = 0x72 (114) = 6650 rpm 7500 = 181
140 = 0x5F (95) = 6410 rpm 8000 = 221
169 = 0x5F (95) = 6410 rpm 8430 = 255
When this is set to max value 0xFF (or 255 as integer) the rpm limit will be raised to appx 8400 rpm.
It will be hard cut of all sparks so best to have LH limiter 1-200 rpm lower

Perhaps they're talking about an earlier xdf that had something else mislabelled.

Your last statement is correct. Earlier XDFs listed the rev limiter as a table with a few supposed values. Changing 0x5EB should work BUT remember to edit all four copies of the EZK bin.

 

[baggins798]

Esmth, I'm using 984 and 148 bins as they are the ECUs on the car.

I think Mrjaybeeze said earlier that the 954 is the best starting point although the 984 is the most refined. Apart from two of the six 5x5 RPM/LOAD maps, everything else seems to be near identical 954 vs 984, with the latter having the immobilise function in the bin?

 

[Boulder Dash]

Hi, I have had an Ostrich2 lying around for sometime now, but have never gotten around to purchasing the programmer.
I have my eyes on the TL866 II Plus as it seems to be the cheapest that will (maybe) do the job.
I would like to get 5-10 EEPROMS to use, preferable the kind that can be erased with the programmer instead of UV light.
What kind is the recommended type to get, and is it okay to just buy on ebay/China (links would be appreciated)?

I would like to try and see if I can improve the MPG´s a bit by going a tad leaner on the AFR´s and slighly more ignition advance at low rpm/ low to medium load. I have access to a brake dyno so I should be able to experiment with this under controlled conditions.
It would be nice to be able to log the knocks sensor, but has anybody had success with logging any useful data from the EZK?