GM IAT (MAT) all over the place.. 200.. -8 F
I'm just running the Tephra 9417 option 3 ROM with very minimal tweaks. Should I upload it?
Was there any configuration that needed to be done to it? It was my understanding that it was very "plug and play" aside from scaling, etc.
Was there any configuration that needed to be done to it? It was my understanding that it was very "plug and play" aside from scaling, etc.
Any thoughts on what settings could cause such behavior? I've clicked through all of the settings, and checked what I believe to be relevant several times. That said, I'm new to evoscan/ecuflash (coming from ECMLink/DSMs).
Any thoughts would be much appreciated. I can upload the ROM if anyone cares to look at it.
Any thoughts would be much appreciated. I can upload the ROM if anyone cares to look at it.
Crap. Too big to attach.
I tossed it on rapidshare:
http://rapidshare.com/files/37100806...-mine.zip.html
If that doesn't work I'll figure something else out. Or if you want to e-mail me, I could e-mail it to you..
Thanks for the help, very appreciated.
I tossed it on rapidshare:
http://rapidshare.com/files/37100806...-mine.zip.html
If that doesn't work I'll figure something else out. Or if you want to e-mail me, I could e-mail it to you..
Thanks for the help, very appreciated.
With the 9563 v7 SD versions, the MAT is prepatched. You log MAT through the Intake Air Temperature option. The same one you'd previously have used for logging the IAT inside the MAF.
That's how mine works and I haven't changed anything. Just GM IAT sensor attached to pin 77.
That's how mine works and I haven't changed anything. Just GM IAT sensor attached to pin 77.
No. You log 09 = fuel aka pin 77. If you're using the Maf/IAT for logging you log 11
Requestid09 = Fuel Temp
Requestid11 = IAT/MAT
All the patches and code a based on fuel. ONly for people like myself that have the gmIAT tapped into the maf/iat then we change all codes accordingly.
Requestid09 = Fuel Temp
Requestid11 = IAT/MAT
All the patches and code a based on fuel. ONly for people like myself that have the gmIAT tapped into the maf/iat then we change all codes accordingly.
Is this what you're looking for? From Evoscan data file..
<DataListItem DataLog="Y" Color="" Display="Manifold Air Temp" LogReference="MAT" RequestID="09" Eval="1.8*x-40" Unit="deg F" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-40" GaugeMax="300" ChartMin="-40" ChartMax="300" ScalingFactor="1" Notes="" />
I assume if you look at my log you see the same strange numbers? If so, it shouldn't be my evoscan..
<DataListItem DataLog="Y" Color="" Display="Manifold Air Temp" LogReference="MAT" RequestID="09" Eval="1.8*x-40" Unit="deg F" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-40" GaugeMax="300" ChartMin="-40" ChartMax="300" ScalingFactor="1" Notes="" />
I assume if you look at my log you see the same strange numbers? If so, it shouldn't be my evoscan..
Actually, now that I think about it, I still need to double check that I'm actually getting readings from the GMIAT and not the one in the MAF. It's still plugged in since I'm working on setting up my SD right now.
I think I'm getting the right reading though. My intakes temps aren't climbing much over ambient even while sitting and idling and I have an open air filter under the hood.
I think I'm getting the right reading though. My intakes temps aren't climbing much over ambient even while sitting and idling and I have an open air filter under the hood.


