[SOLVED] Problems logging MAT with 88590715
[SOLVED] Problems logging MAT with 88590715
I have FINALLY gotten around to running and installing the sensor wire for the MAT I installed ages ago.
; my DD talon needed like $1500 worth of repairs and now it is back on the road... I have run into a snag and cannot log the MAT temperature.
Oh, this is on an 06 IX MR...
I tested the sensor resistance against the chart {here} and the MAF IAT. Both seem to line up around 84.5F after the car sat all night. I also checked that I had the 4.73V on the sensor wire so I know I had at least got the pin seated in the ECU connector. quadruple checked that I had pin 96 in the ECU...
I decided the best thing to do was go back to the last 88590015 stock ROM I had running and patch it with mrFred's patches. After flashing nearly every block in the ECU I got it running and I can read the MAT via EvoScan...Humm...
So now I guess I have narrowed it down that mrFred's patches do not work with the 88590715 v7 tephra ROM. Does anyone know what I am missing here? I guess that I either overwrote something in the MUT that is used for MAT or I am reading the wrong MUT. Any ideas?
Edit: I followed this: Patch how-to: manifold air temperature logging
; my DD talon needed like $1500 worth of repairs and now it is back on the road... I have run into a snag and cannot log the MAT temperature.
Oh, this is on an 06 IX MR...
I tested the sensor resistance against the chart {here} and the MAF IAT. Both seem to line up around 84.5F after the car sat all night. I also checked that I had the 4.73V on the sensor wire so I know I had at least got the pin seated in the ECU connector. quadruple checked that I had pin 96 in the ECU...
I decided the best thing to do was go back to the last 88590015 stock ROM I had running and patch it with mrFred's patches. After flashing nearly every block in the ECU I got it running and I can read the MAT via EvoScan...Humm...
So now I guess I have narrowed it down that mrFred's patches do not work with the 88590715 v7 tephra ROM. Does anyone know what I am missing here? I guess that I either overwrote something in the MUT that is used for MAT or I am reading the wrong MUT. Any ideas?
Edit: I followed this: Patch how-to: manifold air temperature logging
Last edited by dingus; May 6, 2012 at 12:37 PM. Reason: Found problem...
On an IX I believe that ECU pin 96 is the Evap Fuel Temperature input. I followed mrFred's writeup: Patch how-to: manifold air temperature logging
Found this: I guess that I am just pointing EvoScan to the wrong MUT...
https://www.evolutionm.net/forums/7618360-post373.html
https://www.evolutionm.net/forums/7618360-post373.html
Did some more tests today. I have confirmed that the install is correct. I was able to log MUT87, which from Merlin's "How to Tune an Evo" shows is the 8bit ADC output from pin 96. This was confirmed with reading against a DMM.
Sensor Plugged: 125 counts from EvoScan; 2.470V from DMM
Sensor UnPlugged: 242 counts form EvoScan; 4.768V from DMM
I also measured 2.26kohms from the sensor...but had to be quick since the second the sensor is unplugged it starts cooling off.
Something interesting (for us nerds I guess) is I could measure the sensor self heating. It would read 128 counts after sitting for a while and work work its way to 125-124 counts after a couple minutes of the ignition turned on. Pretty cool/interesting.
Guessing that the tephra mods turns the original Fuel Temp routines (and this explains why I didnt get a CEL when I did this mod) and moved it elsewhere.
Anyone know which MUT I need to log or what ECU address I need to put in the MUT table?
Sensor Plugged: 125 counts from EvoScan; 2.470V from DMM
Sensor UnPlugged: 242 counts form EvoScan; 4.768V from DMM
I also measured 2.26kohms from the sensor...but had to be quick since the second the sensor is unplugged it starts cooling off.
Something interesting (for us nerds I guess) is I could measure the sensor self heating. It would read 128 counts after sitting for a while and work work its way to 125-124 counts after a couple minutes of the ignition turned on. Pretty cool/interesting.
Guessing that the tephra mods turns the original Fuel Temp routines (and this explains why I didnt get a CEL when I did this mod) and moved it elsewhere.
Anyone know which MUT I need to log or what ECU address I need to put in the MUT table?
It looks like I have figured it out.
When I said something about not getting a CEL I got to thinking that this code may be turned off by a periphery bit. Started comparing the periphery bits between my original ROM which worked and the tephra-v7 and found the fuel sensor bit turned off.
I had to change FDA.11 (ECU Periphery3 bit.11) from 0 to 1. I have not driven the car but logging MUT09 with the car off looks okay. Not sure if I am going to get a CEL or not but we will see...
EDIT: I have also been converting (and double checking) a tephra-v7 speed density ROM and that also has FDA.11=1.
When I said something about not getting a CEL I got to thinking that this code may be turned off by a periphery bit. Started comparing the periphery bits between my original ROM which worked and the tephra-v7 and found the fuel sensor bit turned off.
I had to change FDA.11 (ECU Periphery3 bit.11) from 0 to 1. I have not driven the car but logging MUT09 with the car off looks okay. Not sure if I am going to get a CEL or not but we will see...
EDIT: I have also been converting (and double checking) a tephra-v7 speed density ROM and that also has FDA.11=1.
Trending Topics
That does make it easy. I bought the SoopIn Up harness but was wanting to be able to log MAF load and MAT/MAP so I can at least get my VE table close before the SD swap. But when I do swap to SD I am going to rescale my original IAT for the GM sensor I welded into my new intake pipe and use the harness with that sensor...and maybe work out a way to use the baro ADC for the sensor in my LICP. Or build a microcontroller board to read it.
Thread
Thread Starter
Forum
Replies
Last Post
rampant
General Engine Management / Tuning Forum
2
Jul 20, 2015 09:56 AM








