ECU Error Code

[MH3.0R]

Guys,

During the Melbourne Cruise (last Sunday), while I was driving the 2nd unplanned leg (Reefton Spurs), I felt the engine stall when the accelerator was pressed to the floor. The car then started to hop and shudder until I backed off and proceeded with gentle acceleration. I noticed the Engine Malfunction warning light come up on the dash, as did the VDC warning light, along with the Cruise light flashing. Well, after I backed off, toggled the cruise control twice and took it a bit more gentlemenly (for about a kilometer!), it happened again. Throttled back somewaht for the remainder of the descent on the Reefton without further incident.

Stopped at Warburton, had a chat, then we went our merry ways home, and after turning off the Warburton Hwy to head south through the back of the Dandenongs, it happened again.

Took the vehicle to STi@Docklands in my lunch hour and they put the monitor on the OBD-II port and found a Performance Code P1026. They said it was an overrevving error. I thought that was strange since the engine is electonically governed by the ECU. In any case, they indicated I should take to a place the does dyno tuning to have it re-tuned (after recent heads removal and refurbish).

Anyways, on the way home tonight, I setup the ECUDatascan to monitor Left and Right banks Intake V V T Advance and I observed there is no Left Bank Intake V V T Advance happening at all. Remains firmly at zero. Right bank is operating so I thought the left should have displayed similar numbers. Feels like a very bad case of Turbo lag and the engine is slow to spin up.

Could this be a loose or broken connection somewhere? Any hints?

Anyway, might just get a tune as well to optimise the power, torque and efficiency with the refurbished heads, subject to ministerial approval of course!

[Sentinel]

Well you were sayin that you had a lag...

So I'm also guessin that you found out that STi Docklands ditched your VIN tune too then??

[MH3.0R]

Yes, well the lag turns out to be the left bank V V T Advance not working, so the engine is fighting with itself. Not good at the revs we were pulling. I found this problem myself using the ECUdatascan on the way home.

I spoke with STi today and they assured me that they have not touched the V tune, just suggested that it needs to be "touched-up" after the head work. They suggested I should do this before any further spirited driving.

I am thinking that I have just spent 4500 on head work less than 4 weeks ago and now a whole bank of the valve timing is not working! I think this will be another trip back to see them tomorrow.

[MH3.0R]

Spoke with STi@ Docklands today and the car is booked in for next Wednesday. After I explained the observations I had made after their initial diagnosis, they agree that they will need to re-check the Cam Sensors. I will post the results after next Wed.

Has anyone been able to find the performance code 1026? It does not appear in any of the regular lists.

[MH3.0R]

Well, the left bank CAM Sensors were cleaned and all now seems to be well. I know that the V-Tune is still intact as the old performance has come back! How sweet she is! And the fuel economy has returned (when I can keep my foot off the pedal).

Only thing buggin me now is the DBW "turbo lag" that is built into the MY05 3.0R. Dropped by the guys at Rev Zone this week and they assure me they can remap the DBW and remove all this. They did a test connect to the ECU while I was there and said no problems foreseen. So this will be the post head work tune that has to be done (for the ministerial approval pitch). Booked in for late Sep.

Has anyone yet resolved the Performance Code 1026? I think it is the result of converging sensors giving different indications and results in similar engine stress to overrevving, so that is the code presented. Not indicated in any other forums, so this may be my contribution to the knowledge base!

[Kekotic]

Good to hear things are back on track Mark, good luck getting the non turbo - turbo lag removed