EECV timing explained
Another quote from boss96. Bob I hope you don't mind
Quote:
|
Re: EECV timing explained
No problem, thanks for posting it. I hope it is not too complicated and helps people out.
Bob |
Re: EECV timing explained
My observations on the BASE and ALTITUDE spark tables are that from the eec-iv codes I've seen on MAF equipped cars the two tables appear to be a hang over from the pre MAF and very early MAF equipped cars that still ran BAP sensors. The code for the base spark calculation interpolates between the two tables according to barometric pressure. Now on later MAF cars the BAP sensor was dropped because there is no need for it and Ford set the tables to the same values in virtually all of the cells (I've only seen the odd couple of cells that differ in most codes and these typically only by 0.25 degrees). For tuning purposes both tables should be altered and set to the same value to avoid the interpolation shifting away from what we desire (or causing us to enter a false value to compensate).
For normally aspirated tuning, as an alternative to having to update both tables, I change the address of the ALTITUDE table within the spark table lookup routine to point to the BASE table, this means I can zero the values in the ALTITUDE table and ignore it. |
Re: EECV timing explained
sailorbob,
This would not be a good idea on the later model EEC-V cars that are running a blower or turbo setup........something lets say like the '03-'04 Mach 1's etc. |
Re: EECV timing explained
Thanks Dale, could you enlighten me further, I must admit I don't know much about how the eec handles forced induction. My post is aimed at normally aspirated tuning and to try to clarify the function of the altitude spark table, I've edited my post to suit.
|
All times are GMT -6. The time now is 08:27 AM. |
Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.