I have added a few addresses to the standard S14 KA24DE xdf as follows:
•EA22 - Low MAF Voltage Enrichment Trigger
•E55A - Amount of time timing retard is applied
•E55B - Timing retard amount
•E559 - Delta TPS % position change trigger point for timing retard
•E200 - Injection Response
•E230 - TP Accel Enrichment
•E038 - O2 Sensor Flag (doesn't do anything though)
•E038 - KS Sensor Flag
•E390 - TTP Min
•Corrected the addresses for the VE Tp scale and Rpm scale and conversion.
The following do not alter unless you have a S14 Launch control bin:
•DFF2 - Launch Control Off Speed
•DFF0 - Launch Control Limiter

The modified xdf file is attached, however I had to change the extension to .txt in order for the upload manager to allow it. Please change the extension back to .xdf to use. I am posting this since there are a few Ka-t tuners who use this forum...and I caint post attachments on Ka-t.org I did a brief look-around and didn't see anything like this posted before, please forgive me if its a repost.

Awesome, thanks for the post!! I've got most of these constants except for the O2 and KS sensor flags. I'm interested in taking a look at the updated VE stuff. :)

Thanks again

Oh and by the way, if it smells sweet you might also be running E85 :)

After looking at the VE table in a new light, I'm wondering if it would be a good idea to scale it's TP scale along with my fuel and ignition scales. I've never had the opportunity to see the true VE map scales. I've heard that the 95 ECU doesn't use the VE scale, but do we really know that? I'll give it a try and see if I can see a change with trims (alpha and alpha SL).

Furthermore maybe making this map completely flat (effectively voiding it out) would give greater control to your primary fuel map, if the VE map is in fact being used. Maybe I'll try that too.

Fun stuff. :)

OK, I tested whether the VE table was being used by the software in a 95 ECU and without a doubt it most certainly is.

I tested this by selecting the entire table in TunerPro and adding 40 to all cells. The engine started up and idled fine. I pulled out onto the street, tipping the throttle in and all of the sudden the car bucked and misfired like crazy! :) I couldn't decide whether I was happy about this or not. LOL :) I backed out of the throttle and slowly accelerated up to speed without incident. Then I started Logworks and monitored AFR's. In a tall gear I slowly tipped the throttle in and watched as the AFR's plummeted to an insane level enrichment. I was seeing .6 lambdas! I think it was trying to get into the .5s, but I may have run out of injector, I have yet to check on those.

I further played with this function by translating the entire table up and down by much less increments, such as 10. Every change resulted in a change in open loop and closed loop operation from what I could tell.

If all of this is already known by everyone except me, then disregard this post, but if not, then those few of us with S14 RT's have something new to play with. :)

With bolt on mods trims change and are hard to nail down in closed loop operation, this may help tune those regions. Plus, we may be able to make our calculated AFRs in our Primary Fuel map match what we see and therefore be meaningful.

I gotta give credit to LigouriRd and anyone else who played a part in discovering those VE table attributes.

Are you guys tuning the 70F00 bin?

Are you guys tuning the 70F00 bin?

70F00, that would be 95/96? I am tuning a 95 ECU with a 95 base. I don't think we can use a 96 and up bin.

I am currently trying to tune the VE map of the 95 bin. I disable the O2 using the flag/switch and started with a totally flat VE table and Primary Fuel map. I try to achieve a lambda=1 at all RPMs and all loads. So far I'm doing pretty good I think. I think I've just about got the VE table tuned right. My plan is that after I tune the VE table I'll add back in the power enrichment from the Primary Fuel map. But this time hopefully the AFRs in that map will be correct and correspond with actual AFR's

70F00, that would be 95/96? I am tuning a 95 ECU with a 95 base. I don't think we can use a 96 and up bin.


70F00 is the rom label in the bin, and also part of the ECU part number on the sticker. What ECU part number are you using?

Thanks,
Dave

70F00 is the rom label in the bin, and also part of the ECU part number on the sticker. What ECU part number are you using?

Thanks,
Dave

Yes, my bin part number suffix is 70F00 and I think the two characters are 3C. This suffix tends to have something to do with model year. I've noticed a lot of parts on my 98 will have an 83F00. I've seen 79F00, 70F00, 59F00, 50F00, 40F00, etc. For example, the differential case cover gasket was XXXXX-40F02. I'm guessing this means the original design was in the late 80s and they've revised it twice since then. IDK, just a guess.

I am glad this was helpfull. I have done the majority of my tuning straight from the VE map. I set up the primary fuel map to have the air/fuel ratios that I wanted to see at various tp levels and rpms and then tweaked the values in the ve map until I got the real air/fuel values that I wanted. I still don't have the control of the fuel that I would like, there is some strange richness at startup and with light throttle input. I have noticed it takes quite a change in the ve map to get a corresponding change in a/f.

For my next round of tuning I plan to flatten the ve map with 128 (zero correction values) then start over trying to find the proper k-value and latency. I hope this will aleviate some of the issues I am finding.