[secretsquirrel]

I've been experiencing the following codes while driving for the last couple of days. The symptoms are the below codes followed by a check engine light and reduced power. I've been able to turn off the code, clear codes and resume driving, for about 80 miles until the codes reappear. The codes are listed below:

12544 -boost presssure control deactivate
12003 - Coolant temp sensor, plausibilty
12190 -charging pressure sensor - Termic oil level sensor
10887 --Outlet-VANOS variable cam control test

The issue seems to be electrical to me, being that codes from different sections of the car are being tripped. Could it be that my 3 year old Procede box is failing and is sensors to trip?

Any help in tracking this down is appreciated!

[caliguy562]

Which map/firmware are you using? Funny thing is my car was also throwing that vanos code, only after a cold start though. I recently started getting the coolant temperature sensor code too after steady driving. It appears that the coolant code is procede related for sure. Has to do with the waste gate setting. I reinstalled the map and have been back to normal for a few days now, but I'm still keeping an eye on it.

[Ilma]

Originally Posted by caliguy562

Which map/firmware are you using? Funny thing is my car was also throwing that vanos code, only after a cold start though. I recently started getting the coolant temperature sensor code too after steady driving. It appears that the coolant code is procede related for sure. Has to do with the waste gate setting. I reinstalled the map and have been back to normal for a few days now, but I'm still keeping an eye on it.

Yes the coolant sensor plausibility code is procede related.

In my case having the built-in downpipe fix active would trip this code during steady highway driving.

The problem went away once I removed two wires from the harness which feed the procede's O2 simulator....

At one point Shiv strongly recommended this patch and I always suspected the reason was because the O2 simulator drew too much current and created an overload which the DME interpreted as a "plausibility gradient" condition for the coolant sensor because it shared the same ground wire as the O2 simulator.

[Ilma]

Originally Posted by secretsquirrel

I've been experiencing the following codes while driving for the last couple of days. The symptoms are the below codes followed by a check engine light and reduced power. I've been able to turn off the code, clear codes and resume driving, for about 80 miles until the codes reappear. The codes are listed below:

12544 -boost presssure control deactivate
12003 - Coolant temp sensor, plausibilty
12190 -charging pressure sensor - Termic oil level sensor
10887 --Outlet-VANOS variable cam control test

The issue seems to be electrical to me, being that codes from different sections of the car are being tripped. Could it be that my 3 year old Procede box is failing and is sensors to trip?

Any help in tracking this down is appreciated!

I can't be of help other than to say that in the last few weeks I have seen my dash lights go haywire, similar to when the procede is not correctly connected.

It would cycle through a multitude of warning symbols and then limp out on me with a very rough idle. Pull over and restart and the problem clears.

I made recent changes to my backend flash which I stack with the procede, so I was thinking that the flash might be the culprit.....but maybe it could be a procede issue?

Are you running the piggy only, or stacking with a flash?

[secretsquirrel]

Originally Posted by caliguy562

Which map/firmware are you using? Funny thing is my car was also throwing that vanos code, only after a cold start though. I recently started getting the coolant temperature sensor code too after steady driving. It appears that the coolant code is procede related for sure. Has to do with the waste gate setting. I reinstalled the map and have been back to normal for a few days now, but I'm still keeping an eye on it.

I'm running the V5 9_10 Agressive stage 2 maps (MT). Its funny that you mentioned wastegates that because my car has been experiencing a lack of boost. I thought it was a vaccuum leak, but a smoke test revealed no such leak. My car has ~128k with stock turbos, so I know some due for some new turbos.

In an effort to resolve the problem, I've set the wastegate setting to 30% and haven't had the CELs in ~120 miles. But the car is definitely not as strong with even day to day driving (non boosted driving). I wan't to get to the bottom of this. I called Vishnu on Friday and received a callback in an hour, but I missed the call. I called them back and expect to receive a response on monday.

Originally Posted by Ilma

Yes the coolant sensor plausibility code is procede related.

In my case having the built-in downpipe fix active would trip this code during steady highway driving.

The problem went away once I removed two wires from the harness which feed the procede's O2 simulator....

At one point Shiv strongly recommended this patch and I always suspected the reason was because the O2 simulator drew too much current and created an overload which the DME interpreted as a "plausibility gradient" condition for the coolant sensor because it shared the same ground wire as the O2 simulator.

Thats interesting. I'm not running the Procede built in fix, as it was recommeded not to run (as you mentioned). However, I am running a BMS DP fix... But I'm not sure if it is having an effect as I've been running it 2 years or more.

Originally Posted by Ilma

It would cycle through a multitude of warning symbols and then limp out on me with a very rough idle. Pull over and restart and the problem clears.

I made recent changes to my backend flash which I stack with the procede, so I was thinking that the flash might be the culprit.....but maybe it could be a procede issue?

Are you running the piggy only, or stacking with a flash?

I'm seeing the exact same thing, only I'm not seeing a crazy start up lights sequence. I'm running only the the procede. No back end flash, etc.

[caliguy562]

Keep us updated. I was running the auto tune map when all this craziness was happening. It would trip the vanos code after a cold start 90% of the time. I uploaded the aggressive 9-10 maps about a week ago and everything has been back to normal. Planning a 300 mile road trip tomorrow and we will see how that goes.

I believe the coolant code is definitely wastegate related. My car was running fine and as soon as I switched from map 4 to 0 with latest map, I heard the fans kicked in and lost throttle response. Also, I would suggest removing the dp fix. Use the procede auto clear feature as it provides a cleaner signal. For smog testing purposes, rewire the procede's dp patch..if you have those on your harness or put jb dp fix in temporarily.

My suggestion is to just reload the firmware and map. I think sometimes the procede just needs a good reboot. Kinda like when your phone or computer starts glitching.

[Jeff@TopGearSolutions]

I'd start with fresh firmware and map.

Then look into removing the DP fix. You shouldn't run them long term.

Go from there.

[secretsquirrel]

Thanks for the responses, guys. I'm going to pull the dpfix, tune on auto clear and reload maps this weekend. I'll reply to this thread after a few days to report the results.

[Mike@N54Tuning.com]

Originally Posted by secretsquirrel

Thanks for the responses, guys. I'm going to pull the dpfix, tune on auto clear and reload maps this weekend. I'll reply to this thread after a few days to report the results.

And make sure you clear all codes as well and see what if anything comes back..

Mike

[secretsquirrel]

Originally Posted by Mike@N54Tuning.com

And make sure you clear all codes as well and see what if anything comes back..

Mike

Will do. Thanks!

[caliguy562]

300 miles and no coolant temperature codes after reinstalling software. I did get the vanos code on cold start. Perhaps the solenoids are sticking. Gonna switch them out this weekend.

[secretsquirrel]

I removed the dpfix, reinstalled the firmware, and changed out my vanos solenoids, and I'm good again!

It looks like vanos code was somehow linked to the Coolant temp sensor with the procede. Thanks for your help, guys.

[Mike@N54Tuning.com]

Originally Posted by secretsquirrel

I removed the dpfix, reinstalled the firmware, and changed out my vanos solenoids, and I'm good again!

It looks like vanos code was somehow linked to the Coolant temp sensor with the procede. Thanks for your help, guys.

Glad you're all set

Mike