Page 3 of 8
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 15, 04:09
by wwhite
Have a look. Some addresses have been corrected for A1C.
SUB2 addresses all updated, for this spread sheet.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 15, 19:11
by efloth
Very nice! I added flags, tables, and functions.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 20, 13:28
by efloth
Has anyone started on the additional items? I don't want to start work that has already been completed.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 20, 16:00
by wwhite
Yes, half way through functions.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 21, 01:52
by wwhite
Here is the next version with tables and functions:
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 21, 17:43
by efloth
This is looking really good. We just need to implement the Extended VE Table and possibly datalogging patches. Many hands certainly make light work.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 21, 18:30
by efloth
As I noted in J1X the setup for the 4.9 does not use actual engine size for basemd:
(225/6) * 8 = 300
Could this have something to do with the isc weirdness in A1C? I believe changing basemd requires re-tuning the ve table.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 21, 20:38
by Sevensecondsuv
First off, thank you to you both for the work creating the new XDF. As an engineer (mechanical) with a few programming classes to my credit, I understand the concept of what you did but I would have no idea where to start if I was trying to do it myself.
As to basemd, I believe Michael had that set to the 225 c.i. value Ford used for the 4.9L in the earlier tunes and it had the same idle issues. His notes do say that basemd is for idle stability. Then again all his instructions were written for mass air strats, so we're in a kind of alternate reality with the speed density stuff. All that said, I really wasn't having what I would describe as idle stability issues. Once it switched to closed loop idle control, it stayed there. The problem was a weird timer thing where it would pull all fuel and sputter upon closing the throttle for about 5 second before going into closed loop idle control and stabilizing at stoich. That and the reported ISCDC value making huge swings without actually affecting idle. That part really seemed like an addressing issue.
I'm currently working crazy hours but will give this stuff I try as soon as I get a chance. Hopefully the adx file isn't too much work for you both. Your help has been invaluable.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 22, 01:20
by wwhite
efloth wrote: ↑2023 Mar 21, 18:30
As I noted in J1X the setup for the 4.9 does not use actual engine size for basemd:
(225/6) * 8 = 300
Could this have something to do with the isc weirdness in A1C? I believe changing basemd requires re-tuning the ve table.
The total air mass flow into the engine (AMPEM) is computed from the basic equation:
Mass = Pressure * Volume / (Gas Law Constant * Temperature in Rankine)
Because the pressure can not be directly computed it is inferred from engine speed and manifold absolute pressure and a table of volumetric efficiency a a function of engine speed and load.
BASEMD must be calibrated to provide the engine volume for this calculation as well as the Gas Law Constant.
BASEMD = 0.0234393 * Engine Displacement in Liters (lbm - deg R/in. Hg - rev).
SARCHG = Standard Aircharge = 4.4256E-05 * CID / of cylinders.
Re: SUB2 stock bin - '95 4.9L E4OD
Posted: 2023 Mar 22, 03:20
by wwhite
efloth wrote: ↑2023 Mar 21, 17:43
We just need to implement the Extended VE Table and possibly datalogging patches.
This could be the time to implement a different data logger.
Currenlty, the patch has all parameters hard coded into the patch, the ops list.
This bin already has a parameter list of PIDs built in, the ops list.
I don't see the point of patching in a list of parameters when it already exists.
Location is: 291a 29c4 :W N :Y
Instead of polling all parameters all the time, could poll only the parameters you want.
Have TunerPro request only the PIDs you ask, vs polling all the PIDs.
There also exists a method to access any strategy parameter using offset +-base address.
Just a thought.