Jump to content

2017 Silverado 1500 engine temp fluctuating *new 5.3l owner*

Rene Celaya

By Rene Celaya
in Troubleshooting & Recalls

 Share

Recommended Posts

  • 1 month later...
04/17GMZ714WD New Member

04/17GMZ714WD

Posted
Posted

This is not normal. Pops just bought a 17 Z71 from canada, has a 1 row radiator, trucks in hotter climate needs the 2 row radiator. Checked on a truck with 2 row/ Ac on ran at 181. Pops ran at 201 with Ac on. Get the 2 row if you want to get rid of the fluctuating.

  • 4 months later...
sierrathewhitesierra Enthusiast

sierrathewhitesierra

Posted
Posted

My 2016 Sierra 1500 5.3l does the exact same and my dads 2015 silverado 1500 6.2l does it less but it will doing when wheeling up hills and stuff. From my research it’s the stock thermostat opens slowly to reduce pressure in the cooling system to stop the radiator from cracking. It’s very annoying thinking about trying aftermarket thermostats 

  • 10 months later...
teamaed Enthusiast

teamaed

Posted
Posted

I just got a 2018 Z71 and ran into the same identical issue.  Literally going up to Pinetop and the mountains from the Valley to Payson I noticed the temps lifting identical to yours.  Took it to the dealership and they told me nearly the same explanation minus the air ****** deal.  I was so worried as I will be towing my buddies side by side soon and didn't want to overheat.  I guess I'm happy to see its normal and not me.

HeySkippyDog Senior Enthusiast

HeySkippyDog

Posted
Posted

[emoji849] it's the shutters, guys. It's likely been doing that the entire time you have owned the truck. You just weren't looking. The effect is more pronounced in hot weather or towing, but it isn't gonna hurt anything.

Sent from my SM-J810F using Tapatalk

  • 3 years later...
Sergio Antillon New Member

Sergio Antillon

Posted
Posted

Hey guys I have a 2018 Chevy with the 6.2L with 35k on it. I been having the same issue. So I took out all the shutters, replaced the thermostat with a bit lower one I believe it a was a 194 and replaced the temp sensor next to the thermostat housing. And I noticed today that it’s keeps on having the same problem temp goes up past 210 and back down. Any suggestions? 

  • 9 months later...
Tim-1 New Member

Tim-1

Posted
Posted
On 10/8/2023 at 8:39 PM, Sergio Antillon said:

Hey guys I have a 2018 Chevy with the 6.2L with 35k on it. I been having the same issue. So I took out all the shutters, replaced the thermostat with a bit lower one I believe it a was a 194 and replaced the temp sensor next to the thermostat housing. And I noticed today that it’s keeps on having the same problem temp goes up past 210 and back down. Any suggestions? 

Did you figure it out? 

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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   4 Members, 0 Anonymous, 2,189 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...