Jump to content

Mishimoto Radiator

jsumner83

By jsumner83
in Modifications & Accessories

 Share

Recommended Posts

jsumner83 Enthusiast

jsumner83

Posted
Posted

I have a 2017 gmc sierra 1500 5.3 4x4 that I use to tow my travel trailer here in Arizona. While towing on grades, I notice the engine temp will keep up to 240 degrees, but then go back down once the truck levels out. I have been reading a lot about different mods, changing the thermostat, etc. but what I really want to do is as the Mishimoto radiator. There isn’t a lot of info out there in terms of anyone doing it and what results they had. I did read somewhere that some guy purchased an all aluminum 3 core radiator (not Mishimoto) and it worked so well that he had all kinds of warning lights in his Silverado cause the motor never got up to temp. My question is, will I need to also change the thermostat and have the fan settings changed after I purchase this radiator, or do we think stock settings will Be fine. Let me know. Thanks! 

IMG_1084_Original_Original.jpeg

  • Like 1
rav3 Senior Enthusiast

rav3

Posted
Posted

I cannot give you any info on the Mish radiator. However, your coolant temperature is regulated by the thermostat. If I were you (and you're not) I would buy a EL327 OBDII Bluetooth dongle & download an OBDII App to my phone & read the actual coolant temperature versus what the dash gauge says it is. on my 2017 5.3l with Max tow package, shows just a hair under 210F on the dash gauge, however, when i read it from via the OBDII app, it is actually 175 to 190F, which is cooler that I originally thought. Also, running a cooler thermostat is a cheap & easy 1st mod to try over the cost of a $1000 radiator. 

Good luck & try the simple things first.

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted

I agree to a point. The thermostat sets the temperature. UNTILL the capacity of the radiator is overtaken. When the thermostat is wide open the temperature is still on the rise well over the set point (health motor naturally) then there is not enough reserve, and a larger radiator is the cure as a colder thermostat will not help.  

 

No special setting or tune is required for this modification. 

  • Like 2
CajunFries Enthusiast

CajunFries

Posted
Posted

I’m running a Mishimoto radiator and Katech Tstat. I love it. No more overheating in 110+ day + towing up the hills. It is a lil bit thicker than the factory one just a heads up. image.thumb.jpeg.46142423ed4018d11cf56438edfeeacf.jpeg

  • Thanks 1
Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted
12 hours ago, CajunFries said:

I’m running a Mishimoto radiator and Katech Tstat. I love it. No more overheating in 110+ day + towing up the hills. It is a lil bit thicker than the factory one just a heads up. image.thumb.jpeg.46142423ed4018d11cf56438edfeeacf.jpeg

 

Is it plug and play? Or do mounts need modification and so on? 

CajunFries Enthusiast

CajunFries

Posted
Posted
6 hours ago, jsumner83 said:

Just ordered mine. Do I need to order the chill coolant or can I use an over the counter brand? 

Regular coolant is fine. I would suggest replacing the thermostat while you’re there. Either another factory AcDelco one or one from Katech. Nothing else. If you do get one from Katech, get the warmer opening one or else it might throw a CEL. 

CajunFries Enthusiast

CajunFries

Posted
Posted
12 hours ago, jsumner83 said:

🤔 I have a 180 degree thermostat that I ordered from summit that I planned on throwing in. I’ll look at the katech ones now. 

Looks like the highest one they have is a 174. I’m not sure what the threshold is for the ecu to not throw a CEL. My 160 keeps my coolant temp right at 160-165 even on a hot day as long as the truck is somewhat moving. That would definitely throw a CEL if it wasn’t tune for it. 

Buckwild27 Enthusiast

Buckwild27

Posted
Posted

I believe the 174° will throw some codes. I put the corvette 195° in mine not a huge drop. But it doesn't throw codes. 

Grumpy Bear Senior Enthusiast

Grumpy Bear

Posted
Posted (edited)
1 hour ago, Homewrecker007 said:

I believe the 174° will throw some codes. I put the corvette 195° in mine not a huge drop. But it doesn't throw codes. 

 

Nope. I run a Reische Racing 170 F and zero codes over several years. The 160 F stat will toss a code and requires a tune. 

Edited by Grumpy Bear
  • Like 2
Buckwild27 Enthusiast

Buckwild27

Posted
Posted
8 hours ago, Grumpy Bear said:

 

Nope. I run a Reische Racing 170 F and zero codes over several years. The 160 F stat will toss a code and requires a tune. 

I stand corrected.  

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

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...