[LiqTenExp]

Originally Posted by SOCAL.M6.ZLE

Hey Megahertz...
It's my understanding that IAT.2's come from the TMAP sensor at the back of the drivers side blower (post intercooler bricks) Which is why those numbers will / should decrease after a pull thanks to higher air velocity, and reduced heat soak from the intake runners / blower. Air is moving too fast to heat up. (this assumes your HX system is working properly) The only problem that I am aware of is that the OEM sensor is very slow acting, and does not accurately capture spikes in temp changes.

Which is why I am adding a new RIFE IAT sensor on the passenger side, as well as an IAT temp sensor on the hot side of the blower. I am not certain, but I believe I'll be the first. Doing this to better support future testing and system design. Stay tuned for more on this one!

MAT's are calculated as you noted, from RPM, Speed, ECT, EOT, Ambient Temps, Boost Pressure, etc...

I guess the logic is that it would be too risky to base your timing curve on the actual IAT.2 sensor data, and should there be an issue with the sensor the car could suffer. It seems much safer to base the timing table on a calculated number that ignores the spikes in IAT.2 if they did exist. The problem for us, is that number is heavily biased for safety, not power efficiency.

I suppose thats why many tuners will raise the IAT.3 threshold for timing being pulled?

That said, do you ever adjust that table? If so, can you share your methodology?

MAT = TMAP temp or IAT relocation temp sensor. It disconnects the temp sensor pin on TMAP and relocates it to a remote temp only sensor. TMAP now = Cylinder 2 IAT = MAT

IAT2 = IAT1+ECT math, I think this is intended to give you the temp of air going into the TB (calculated)

IAT1 = MAF temp

If you disconnect your MAF IAT1 goes away along with IAT2. If you disconnect TMAP or Relocated IAT sensor MAT will go away.

[Megahurtz]

Originally Posted by SOCAL.M6.ZLE

Hey Megahertz...
It's my understanding that IAT.2's come from the TMAP sensor at the back of the drivers side blower (post intercooler bricks) Which is why those numbers will / should decrease after a pull thanks to higher air velocity, and reduced heat soak from the intake runners / blower. Air is moving too fast to heat up. (this assumes your HX system is working properly) The only problem that I am aware of is that the OEM sensor is very slow acting, and does not accurately capture spikes in temp changes.

Which is why I am adding a new RIFE IAT sensor on the passenger side, as well as an IAT temp sensor on the hot side of the blower. I am not certain, but I believe I'll be the first. Doing this to better support future testing and system design. Stay tuned for more on this one!

MAT's are calculated as you noted, from RPM, Speed, ECT, EOT, Ambient Temps, Boost Pressure, etc...

I guess the logic is that it would be too risky to base your timing curve on the actual IAT.2 sensor data, and should there be an issue with the sensor the car could suffer. It seems much safer to base the timing table on a calculated number that ignores the spikes in IAT.2 if they did exist. The problem for us, is that number is heavily biased for safety, not power efficiency.

I suppose thats why many tuners will raise the IAT.3 threshold for timing being pulled?

That said, do you ever adjust that table? If so, can you share your methodology?

I do adjust this table but it depends on the setup. If the setup is on high ethanol content and meth, I adjust this table a lot. If it's just a bolt on car I don't move this very much as I prefer the let the car put more timing in during the lower gears and then allow it to pull it back in higher gears as the blower heats up....just like factory logic. Bolt on cars running E blends I actually reduce the IAT pull vs Ethanol content elsewhere and leave this table mostly stock or stock.

Also, the IAT sensor logic and what is used to pull temps seems to differ between the Camaro and the Corvette. The only common denominator is the main IAT table seems to affect the change we are looking for. There are definitely other temp tables at play that are not defined.