Jump to content

Recommended Posts

Posted (edited)

I got a 2006 Tahoe that needed an engine.  found a remanufactured (z code engine) had installed with new water pump, radiator and thermostat ( have replaced 3 times with factory 187 degree stat). Now the engine runs about 165 to 175 on the road. When idling it will get up to about 210 and will stay there all day idling fans turning on and off working normally. But when I drive temp drops back down to 165-175. Has anybody sean this and know what the issue might be? I’m checking coolant temperature with ODBII scanner and gage. 

Edited by Mfriend3
Add info
  • Mfriend3 changed the title to 2006 Chevy Tahoe Coolant temperature low
Posted

If you are positive you have no air in the system and the gauge doesnt jump past 210, you are within specs.  Your heater works as it should I am guessing since you didnt list that as a symptom.  Since you have went through and did all this work, you may want to stick another coolant temp sensor in, for what they cost, it would eliminate at least one possible issue to whats going on with your gauge.  

Posted

I have replaced the coolant temp sensor and harness when replacing the engine. The heater gets warm not as hot as I would think but is putting out heat.  As far as bleeding all the air I have been trying to find the best way to make sure it’s all out but it’s hard to know. As many times as I have drained and filled the system you would hope I don’t have any air pockets. 
Thanks for help alway open to suggestions. This is driving me crazy. 

Posted

It should get hot, a clogged Heater core might be giving you issues.  Get a pipe and bypass the core and see if this resolves your issue.  

Posted

I will do that it does make sense. I will have to figure out how to bypass heater hoses but the hose to the surge tank (return)connects to the heater hoses. 

Posted
3 hours ago, Mfriend3 said:

I will do that it does make sense. I will have to figure out how to bypass heater hoses but the hose to the surge tank (return)connects to the heater hoses. 

2 things you can do.  First get the HVAC coupler removal tools, and remove the heater hoses where they plug into the HVAC.  Then get a pipe that they will fit (its only to bypass the Heater core for the test.  The other thing you can do, if the hoses are old, and its been a while since you have changed them, go ahead and just cut the hoses on inlet and outlet about 8 - 12 inches from where they plug into the HVAC and get a pipe to just slide them over using screw down clamps.  Keep in mind that a known issue is the plastic coupler for the inlet is a common fail point, so you may just want to plan on replacing that coupler, anyway.   This should allow you to bleed out the system again, and get a reading on your temp issue. Obviously if the temp is stable it would have been because of air in the system or your heater core.  Flushing it out with the lines off with a garden hose on the outlet side without high pressure sometimes helps to free any clogs. 

Posted

Well I decided before I bypassed the heater.  I would try and restrict the return hose from the coolant surge tank to the water pump/ heater hose. Then started it up and let it run came right up to temperature about 197 degrees and then I drove it stayed around that temperature fluctuates a few degrees up and down. Not sure if this is a fix but I will drive around some and test. I’m sure I will need to adjust how much flow and see how it does. I’m still looking for a fix and other suggestions or ideas. 
Thanks everyone for your advice!

Posted

I believe it is fixed and it turns out that the radiator has a restrictor on the small hose that goes to the surge tank. But what I think is that the restrictor was letting to much coolant flow to the surge tank and bypassing the thermostat and keeping the engine cool. I added a brass shutoff to that hose and the temperature I’d now running around 195-200 and I can adjust the flow and temperature. Thanks for everyone’s help. I will let you know if I have any other issues. 

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Latest Articles

  • Posts

    • I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...