IW STi Forum banner

Is my STi done for? DAM went to zero, car running fine..

11875 Views 8 Replies 3 Participants Last post by  endrswrd
Yesterday I did two logs on my 2011 STi. DAM was at zero from the first cell on the log to the last, but the car is boosting, accelerating, generally running great. The logs are long and reflect the end of the car being warmed up and a spirited drive. Plenty of boost and load, very few knock below -1 deg, but DAM pinned at zero. Whatever sent it to zero must have happened a while ago. I drove it Saturday just casually for the first time in weeks, Sunday I took the log with the bad news.

So, I reset the ECU with the Accessport. Drove around for a while and DAM went from 0.81 where it started suddenly back to 1.0. I drove it casually and did some fifth pulls cause I figured if it was gonna get fucked, up hill in fifth would do it. Anyway, picked up a few -1.4 feedback knock events during high boost and load, but it always learned them away incrementally and quickly. Although no one wants to see knock, I see this as the computer doing it's job at least, and since it was never more severe than 1.4 deg being pulled, I feel like it's "ok". I guess with my limited understanding, fine knock learning "predictably" stayed at zero since I had just reset the ECU.

Anyone have any insight? Any pros feel like looking at a couple well formatted logs? I will email or post but can't till later. Basically, the "bad" log shows a spirited drive that would look fine except DAM at zero. I didn't look at DAM before I took off up the canyon, lesson learned #1. The log I took after reset shows DAM at 1 and the stuff I listed above. DA during load was typical, 4.57 deg.

I'm going to keep logging but I honestly barely drive the car. Saturday was the first day in a few weeks, drove through a massive rain.

2011, 20k miles, stage 1 91 cobb ots map. What has the car done to itself? Is number 4 about to shit the bed?

Thanks for any feedback!
See less See more
1 - 9 of 9 Posts
Yesterday I did two logs on my 2011 STi. DAM was at zero from the first cell on the log to the last, but the car is boosting, accelerating, generally running great. The logs are long and reflect the end of the car being warmed up and a spirited drive. Plenty of boost and load, very few knock below -1 deg, but DAM pinned at zero. Whatever sent it to zero must have happened a while ago. I drove it Saturday just casually for the first time in weeks, Sunday I took the log with the bad news.

So, I reset the ECU with the Accessport. Drove around for a while and DAM went from 0.81 where it started suddenly back to 1.0. I drove it casually and did some fifth pulls cause I figured if it was gonna get fucked, up hill in fifth would do it. Anyway, picked up a few -1.4 feedback knock events during high boost and load, but it always learned them away incrementally and quickly. Although no one wants to see knock, I see this as the computer doing it's job at least, and since it was never more severe than 1.4 deg being pulled, I feel like it's "ok". I guess with my limited understanding, fine knock learning "predictably" stayed at zero since I had just reset the ECU.

Anyone have any insight? Any pros feel like looking at a couple well formatted logs? I will email or post but can't till later. Basically, the "bad" log shows a spirited drive that would look fine except DAM at zero. I didn't look at DAM before I took off up the canyon, lesson learned #1. The log I took after reset shows DAM at 1 and the stuff I listed above. DA during load was typical, 4.57 deg.

I'm going to keep logging but I honestly barely drive the car. Saturday was the first day in a few weeks, drove through a massive rain.

2011, 20k miles, stage 1 91 cobb ots map. What has the car done to itself? Is number 4 about to shit the bed?

Thanks for any feedback!
Hi there. Sorry for your troubles.

Is the car completely stock besides the stage 1 tune? I would verify the maps shown in the REFLASH and REALTIME slots are both the stage 1 91 map (check this via the "Tune" -> "Show Current Map" menu on the Accessport).

Can you post up the logs on google docs and link them here? (make sure to set the permissions to public so they can be viewed by anyone). Are you at any kind of altitude or drive up to altitude at any time?

Bill
Hey Bill

The motor is all stock besides the tune. I will verify maps when I get home, but I don't think I'll have an issue there since I have only flashed my ECU twice, both the same day I got the accessport (did v300 then realized v301 was up online). Car has run pretty well since install.

I will definitely post up the logs on google docs, but can't until I get home. I live at around 6200 ft, work at around 5100 ft and frequently drive to 9000+ ft.

Thanks do much for being responsive! Will update around 1800 mst.
Welp, internets are not working at my house (iPhone posting now) and I'm int savvy enough to get files from my computer to my phone to here.

So, I will bring the files to work tomorrow and post them from there. They are large but should be informative.

As an aside, I drove to the dealership today to get some bullshit interior thing replaced. DAM stayed at 1.0 throughout.
I have actually seen this glitch on a 2011 and a 2012 myself. All I did was reflash the current tune on the car and it went back to normal. So I would rule that out first by unistalling and reinstalling your AP, and loading up your previous map!
I have actually seen this glitch on a 2011 and a 2012 myself. All I did was reflash the current tune on the car and it went back to normal. So I would rule that out first by unistalling and reinstalling your AP, and loading up your previous map!
To what "glitch" are you referring to?

Bill
To what "glitch" are you referring to?

Bill
Where on a reflash DAM starts @ 0 and stays at 0. Cross reference the initial DAM setting in the tune and its as expected, either .75-1. Ive seen this happen on both OS and Cobb tuning on GR platform.

On the older cars with test connectors, DAM starting @ 0 was usually a sign that you left the test connectors hooked up, but on the newer ones they dont exist.

Wasnt sure if OP had just done a reflash and that was what was going on. But after re reading it seems that wasnt his issue.
Where on a reflash DAM starts @ 0 and stays at 0. Cross reference the initial DAM setting in the tune and its as expected, either .75-1. Ive seen this happen on both OS and Cobb tuning on GR platform.

On the older cars with test connectors, DAM starting @ 0 was usually a sign that you left the test connectors hooked up, but on the newer ones they dont exist.

Wasnt sure if OP had just done a reflash and that was what was going on. But after re reading it seems that wasnt his issue.
Sometimes you see the random car not exit programming mode after a reflash, especially the later GR ECUs. We've made some improvements to the Accessport firmware to minimize this (so update to the latest), but if it does happen, disconnecting the car's battery will fix it and possibly reflashing again as you found. Not what is happening in the OP's case, but just FYI.

Bill
Yeah after I reread I definitely agree this isnt the case. But that is what I figured the issue was, because the only thing that forces 0 DAM is programming mode on the older models.

Any updates Ninja?
1 - 9 of 9 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top