Page 2 of 2 FirstFirst 12
Results 21 to 29 of 29

Thread: Iat Spark

  1. #21
    there is no MAT sensor, MAT is calculated based on a blend of IAT (or IAT2 if fitted) and coolant temp based on airflow etc.
    I count sheep in hex...

  2. #22
    Advanced Tuner
    Join Date
    Jul 2006
    Posts
    403
    So could we make our own IAT2 using a custom pid/equation?
    2006 Trailblazer SS - Stalled, Cammed, Tuned, Turbo'd, Built, and Stroked.
    Runs on cash, blood, sweat, and tears...... and 93 octane.

    2007 Cadillac STS-V - Stock.

  3. #23
    Quote Originally Posted by Blades View Post
    So could we make our own IAT2 using a custom pid/equation?
    no
    I count sheep in hex...

  4. #24
    Quote Originally Posted by Chris@HPTuners View Post
    The Manifold Air Temp PID will be close to IAT2 at higher engine speeds so you could use that as a guide. Or you can just look at the IAT Spark PID and estimate IAT2 by the amount of retard you are getting.
    it does seem to coincide but why only at higher engine speeds, because of larger fluctuation scale? it looks like it will swing almost 100* wot.

  5. #25
    take a look at the tables that control this, the higher airflow values have less weighting towards ECT and the filter values make the filtering faster at higher airflows. Engine -> Airflow -> Cylinder Charge Temperature
    I count sheep in hex...

  6. #26
    Advanced Tuner
    Join Date
    Jul 2006
    Posts
    403
    Was this added in the latest beta? 2.23.3567.27058
    2006 Trailblazer SS - Stalled, Cammed, Tuned, Turbo'd, Built, and Stroked.
    Runs on cash, blood, sweat, and tears...... and 93 octane.

    2007 Cadillac STS-V - Stock.

  7. #27
    THANKS CHRIS! I'm about to give it a try.

  8. #28
    chris if you would take a look at this log...something still doesn't jive with IAT2 pid. it seems that if you use standard iat table and mult, you come up with the following let's say on frame 334 and inter between cells:

    going by iat2... -1.5 *.2 = -.3
    going by mat... -5 *.71 = -3.6 which is exactly what iat advance pid said that it pulled on that frame.

    it would seem that it's the mat that uses these tables on this s/c one?

  9. #29
    Quote Originally Posted by BMBSALES View Post
    chris if you would take a look at this log...something still doesn't jive with IAT2 pid. it seems that if you use standard iat table and mult, you come up with the following let's say on frame 334 and inter between cells:

    going by iat2... -1.5 *.2 = -.3
    going by mat... -5 *.71 = -3.6 which is exactly what iat advance pid said that it pulled on that frame.

    it would seem that it's the mat that uses these tables on this s/c one?
    ok there is some hidden logic here you cannot see, the IAT2 PID displays the raw IAT2 sensor reading. The IAT Spark table uses a prediction from the IAT2 reading that is meant to compensate for the slow moving IAT2 sensor. To predict IAT2 temperatures faster than the IAT2 sensor can actually measure them.

    Now for the happy concidence

    The MAT value is calculated from this predicted IAT2 value (using the usual Bias and Filter tables) and for your application the bias tables are all 0. Meaning MAT = Predicted IAT2.

    So yes you are correct, the MAT value can be used in your case becuase it is exactly equal to the predicted IAT2 value.

    For naturally aspirated applications with one IAT sensor this compensation is not done and the IAT Spark table uses the meaured IAT value.

    (phew!!)

    Chris...
    I count sheep in hex...