Coolant Temps. Rising at Idle

[jariss]

Hello,

About two weeks ago, I installed a whoosh v1 intercooler. Since then, I have had a weird issue in which my coolant temps. will rise at idle pretty quickly and consistently. The highest I let it go was to 210, but it was still climbing so I don't know the actual limit. I did get a p0480 code after installing the ic, but it went away after a reset. I did go from a stage 2 ots map with no issues to stage 0 ots map after installing the ic. I had no issues before on the stage 2 map.

What I have done:
I have checked the F2 fuse and R50 relay (looks like the new one from the TSB) and the don't look blown.
I replaced the fan control module, but same result. (With the A/C on, the fan kicks in, otherwise the fan doesn't kick in)
I haven't checked the coolant temp sensor as the temps. are reading right on the ap, but it could be that?
I did notice spider cracking on the overflow tank but I dont see how that could be causing this.

After resetting KAM, and the ECU, I am not getting any codes. How exactly is the radiator fan supposed to work at idle and when does the thermostat open.

Is what I am describing actually an issue, or am I just paranoid. I dont recall the temps acting this way in the summer heat as I never saw above 200F , and now the days are 50 F. Any suggestions, advice, or tips would really appreciated as I am kind of lost and giving up.

 

[JSWhaler]

You mentioned spider cracking on the overflow tank. Are you losing any coolant? Physical levels look ok?

 

[jariss]

You mentioned spider cracking on the overflow tank. Are you losing any coolant? Physical levels look ok?

I think I may be losing a little. I am sitting at minimum, and the exhaust has a slight sweet note but I can't tell if its condensation or not with the cold since water is dripping. Would low coolant be the cause of a constant temp increase though?

 

[JSWhaler]

it could be

 

[M-Sport fan]

With the AC off/disengaged, our factory stock tune fan setting does not allow the fan (high OR low speed) to kick on until some ridiculously high coolant temp.

I believe it was around 220*F if I remember reading it correctly on threads on this site.

When you say "sweet note" regarding the exhaust are you referring to the smell?
If so, and you think it is coolant getting into the combustion chambers(s), that IS a problem, a head gasket at the very least.

Just to rule it out, are you running an E20/E30 blend at all? Since that could also give that same type of 'sweet' or alcohol tinged smell to the exhaust.

 

[jariss]

With the AC off/disengaged, our factory stock tune fan setting does not allow the fan (high OR low speed) to kick on until some ridiculously high coolant temp.

I believe it was around 220*F if I remember reading it correctly on threads on this site.

When you say "sweet note" regarding the exhaust are you referring to the smell?
If so, and you think it is coolant getting into the combustion chambers(s), that IS a problem, a head gasket at the very least.

Just to rule it out, are you running an E20/E30 blend at all? Since that could also give that same type of 'sweet' or alcohol tinged smell to the exhaust.

Running 91, and I think it was condensation. It was a cold start on a rainy day, and there was visible smoke until it warmed up. It didn't smell strong, but it was something that I thought about with head gasket and the fact that my coolant level is at minimum.
If the fan doesn't kick in till 220 on stock tune, could that be why I was seeing temps stable on the stage 2 tune? So, really there is no issue and its the fact that the tune had it set for the fans to kick in at a lower temp...

 

[M-Sport fan]

^^YES, IF that stage 2 map actually does alter (lower) the fan turn-on temp level as read by the coolant temp sensor.

You would have to ask the tuner (Cobb OTS??) if that is the case, as many do this, or have it as an option for the customer to request.

 

[bombo107]

Reviving a somewhat older thread here. I just got the P0480 code this morning. I replaced the relay but not the fuse since it doesn't appear blown. Should I just reset the code and see if it comes back or is there any way to troubleshoot the module itself?