Fighting Hard Limp Mode with Airflow Mod
Fighting Hard Limp Mode with Airflow Mod
I have been playing with this 3076 car now for about 3 weeks. The car will dyno tune just fine. I was able to completel;y remove hard cut with airflow and torque tables. Then the car goes sideways completely and will hardcut on light throttle which it wasn't before. Last session I no hard cuts but mil lights and 1235 high idle. Now all the time hard cuts. It is a 52680020 I went after the airflow codes by changing out 0x393a0 to FF00. I no longer have driveablity hard cut but something else is seriously wrong. If anyone has a file for a large turbo they want to share I am baffled. Or if there is other airflow deletes out there I am not using. Now it is code 1238.
Cheers C
Cheers C
Last edited by LIGHTSPD; Aug 19, 2009 at 10:41 PM.
DTC P1238: Mass Airflow Sensor Plausibility (Torque Monitor)
What have you done in regards to the Torque Limit tables?
Have you got a log showing load and rpm up to the point you get the CEL?
What have you done in regards to the Torque Limit tables?
Have you got a log showing load and rpm up to the point you get the CEL?
I spent along time tuning the airflow and torque tables on the dyno. Do both the torque and airflow tables have to be the same as each other. 1-1 2-2 3-3 etc if so this may be my problem. I went to look at the logs and the evoscan one is garbled the ecutek one seems to be missing data as well but this is probably because I did the mode 23 mod and now it won't log properly.
I think I am going to have to spend some time dissassembling to get a better understanding of what is going on. I am really frustrated by these trustflow codes. If there was a way to understand by logging where the range was it would make this much easier.
C
C
https://www.evolutionm.net/forums/ev...-evo-x-mr.html
Should help a bit dialing in the airflow and torque limiter tables. Remember that dyno loads and street conditions are going to be slightly different as well. Be sure to not make the values too high as the ECU will flag "not enough airflow" and limit throttle until you turn the car off and restart it again. The only time mine triggers now is around 2500-3000 at 80-100% load after sitting for a bit and heat soaked. I'll have to verify what TPS that equates to and lower that area of my tables slightly but I'm close.
There is also some chance for it to trigger when doing a stutter box launch so I'll have to lower my values a bit to accomodate that as well. Seems like temperature will reduce the airflow values a bit as these never cropped up until it got 90 F outside.
Should help a bit dialing in the airflow and torque limiter tables. Remember that dyno loads and street conditions are going to be slightly different as well. Be sure to not make the values too high as the ECU will flag "not enough airflow" and limit throttle until you turn the car off and restart it again. The only time mine triggers now is around 2500-3000 at 80-100% load after sitting for a bit and heat soaked. I'll have to verify what TPS that equates to and lower that area of my tables slightly but I'm close.
There is also some chance for it to trigger when doing a stutter box launch so I'll have to lower my values a bit to accomodate that as well. Seems like temperature will reduce the airflow values a bit as these never cropped up until it got 90 F outside.
I hear your pain, I may log for what TPS it takes to reach -10 , -5, 0, 5 , 10, 15, and 20 psi to get an idea of where I should worry about upping the limits based on RPM. With a bigger turbo you definitely need to keep the numbers lower for 500-1000 rpms later in the tables but then put in larger values once the turbo is at full song, usually 4000+.
Trending Topics
I found most of my values to make the launch control work were in that 250-255 range in the70 percent throttle areas and greater. Right now the stutter works great jiust nothing else does LOL. I took a very quick look at what you were saying in your thread and it is very similiar to what I was doing.
Last edited by LIGHTSPD; Aug 20, 2009 at 01:11 AM.
I think I am going to spend the day figuring out where each one of these tables comes into play then I will go back to the 3076 car. I have been a commercial software guy for the last 6 years before that it was all hex editor looks like I am going back. Is there a publically avail partial or complete disassembly. I need to come up to speed on this code fast. Any help is appreciated.
Cheers C
Cheers C
whats your ROMID - I want _you_ to test a fix out.

edit - add this for 52680015 -> 52680020
<table name="DTC P1238 Disable 0x384 -> 0xFFFF" category="Misc" address="631ae" type="1D" scaling="Hex16"/>
ONLY DO THE MODIFICATION IF THE CURRENT VALUE IS 0x384!
Let me know how it goes - it *should* work, but may not!
This is ONLY for P1238!

edit - add this for 52680015 -> 52680020
<table name="DTC P1238 Disable 0x384 -> 0xFFFF" category="Misc" address="631ae" type="1D" scaling="Hex16"/>
ONLY DO THE MODIFICATION IF THE CURRENT VALUE IS 0x384!
Let me know how it goes - it *should* work, but may not!
This is ONLY for P1238!
Last edited by tephra; Aug 20, 2009 at 11:20 PM.
Rom ID on that car is 52680020. I also spent the day doing some testing in the 1238 (torque) tables today still analyzing the results. Quite a few peculiar things going on. You would be the guy to ask is there a public or a shareable diassembly of the rom or even partial disassembly available to someone?
Cheers C
Cheers C
I just looked at it in the hex editor it is 0384 at 0x631ae.
I ws forcing a code 1238 today playing with the tables on my 0017 rom and was finding some interesting things. I do have to look at a couple things because this car I origionally tuned with ECUTEK. I will let you know tommorow what happened.
Side bar what command are we shutting down
I ws forcing a code 1238 today playing with the tables on my 0017 rom and was finding some interesting things. I do have to look at a couple things because this car I origionally tuned with ECUTEK. I will let you know tommorow what happened.
Side bar what command are we shutting down
Try my mod first 
Essentially, we are bumping the timer for P1238 occuring from 900 milliseconds to lots more
So you should never hit it.
Be interesting to see if it works.
I have found the other timers (P1241, P1235) so I need someone to test them too!

Essentially, we are bumping the timer for P1238 occuring from 900 milliseconds to lots more
So you should never hit it.Be interesting to see if it works.
I have found the other timers (P1241, P1235) so I need someone to test them too!
Something I discovered today was that only one of the 1238 tables seems to be in play. This is not based on code only observation. I was droping each one of the tables by over 50 percent. and only one of the tables actually put the car into limp mode.



