New Tuning Tutorial: WeathermanShawn

[TunasTwins]

Well, its there- just not supported??

[WeathermanShawn]

Well, its there- just not supported??

A lot of times you just need to hook the Scan Tool up to the vehicle. using the Scan Tool..under Info..hit Validate Pids..

That usually does it for me. I am not the computer 'expert', so perhaps there is a newer and better way. The bottom line is that a number of 'Unsupported Pids' only become validated when you 'Key-on the Car'..with the Scan Tool connected.

Hope that does it for you.

[TunasTwins]

A lot of times you just need to hook the Scan Tool up to the vehicle. using the Scan Tool..under Info..hit Validate Pids..

That usually does it for me. I am not the computer 'expert', so perhaps there is a newer and better way. The bottom line is that a number of 'Unsupported Pids' only become validated when you 'Key-on the Car'..with the Scan Tool connected.

Hope that does it for you.

Thats what I did. It was the first time connecting to this vehicle so I had to validate PIDs but couldnt see dynairtmp. I'll have to try again

[WeathermanShawn]

TunasTwins:

If that does not work, I have been working on a few solutions for CALC.VE Table that involves a way around utilizing the DYNAIRTMP PID. I have to think it over a little more and run it by Joecar and some other math and engineering majors.

I have to catch some sleep right now (worked night shift), but I'll get back to you on it. There are just so many OS's that do not allow DYNAIRTMP, so I am working on a few ideas.

Hopefully then more MAF-equipped vehicles (closed-loop) can utilize the method.

Later..

[TunasTwins]

great news for everyone

[WeathermanShawn]

Well, here is just a tease.

The following is an attachment of CALC. LTFTBENS utilizing a total MAF failure (SD). This was utilizing the 'canned' version of EFILive's CALC.VE (without DYNAIRTMP).

Attachment 8334

You can see the distribution of LTFTBENS across the VE Table.

It is higher when ECT is higher and airflow/Rpms are low. The LTFTBENS are lower where airflow/Rpm are higher. The distribution follows the charge temperature blending factor.

So, since you know the ECT, IAT, MAF Frequency, MAF Airflow..follows that you should be able to build a Calculated Pid that will compute this all after the fact.

Otherwise, you could add an average 'fudge factor' (not recommended at this point) or..just perform a CLSD tune. It comes out to be exactly what the CALC.VE Table looks like if properly done..

Food for thought. It still will take some work to perfect. Until then, lobby EFILive to include DYNAIRTMP wherever it is technically possible to 'Pid'..

[joecar]

Thats what I did. It was the first time connecting to this vehicle so I had to validate PIDs but couldnt see dynairtmp. I'll have to try again

Not all OS's have that pid... Paul tells me that in some OS's that pid can't be internally located (the _DMA pids are lookups of internal PCM memory).

You do either of these:

- change OS to say 12212156 (you will need to copy all your tables over).

- make a calc pid to blend IAT/ECT based on lookup of B4901, see this:

A more accurate way to do this is to do a lookup of the B4901 values as suggested by mr.prick earlier in this thread...
and this is exactly what Ninety8C5 did: showpost.php?p=118165&postcount=29

[FeetDry]

What is the purpose of CALC.LTFT? I don't see it used in any of the other CALC PIDs. So, is it needed?

The method utilizes CALC.LTFTBENS. In closed-loop it takes the average of the LTFT Trims correction and applies them to the MAF Frequency. It is an essential tool to accurately calculate an equivalent VE Table for those running MAF-Closed Loop.WeathermanShawn..

I see that both CALC.LTFTBENS & CALC.LTFT take the average of both banks (LTFT). And I see that CALC.LTFTBENS is used in the %_VE table calculation. But I'm not seeing any use of the CALC.LTFT number. That is why I raise the question. Either it is not needed, or it has some use that is "hidden".

Is this needed: CALC.LTFT = ({SAE.LONGFT1}+{SAE.LONGFT2})/2

[joecar]

...
Is this needed: CALC.LTFT = ({SAE.LONGFT1}+{SAE.LONGFT2})/2

It isn't needed other than for displaying the average in %.

We were possibly maybe going to write CALC.LTFTBEN in terms of CALC.LTFT:
CALC.LTFTBEN = {CALC.LTFT}/100+1

But it was simpler to keep CALC.LTFTBEN uncoupled from CALC.LTFT.

[joecar]

The calc_pids.txt file from post #169: calc_pids.txt


[ if you use [%] units, change the 5.669 to your engine's displacement in Litres ]