Jump to content

Recommended Posts

Posted (edited)

Recently bought 2019 Silverado lt trailboss with 5.3 and 8spd tranny

 

What's the normal operating temp for 8speed transmission? Not towing but just driving in the city/hwy. I'm getting between 70-85 deg Celsius or 158-185 deg f.

 

Also noticed temp went really high while driving in the moderately deep snow on the back road in 4hi. 140deg Celsius! Which I think is 290f.

 

Are these temps normal? 

 

Coming off dodge  with 5spd tranny it was running at 50 for normal use and Max of 80deg Celsius these high temps are new to me, unsure if it's even normal?

 

Truck only has 1300km 

IMG_20200222_092140.jpg

Edited by Giantpeaches
Posted

That sounds high. At 285F you are close to burning the fluid although, the gauge/sensor may be inaccurate, I would get it back to the dealer.

Posted

That doesn't sound right.  If it truly was that high something is wrong.  I would think it would have thrown a code.  How long of a drive in the deep snow?

  • Like 1
Posted (edited)
19 hours ago, Black02Silverado said:

That doesn't sound right.  If it truly was that high something is wrong.  I would think it would have thrown a code.  How long of a drive in the deep snow?

Yeah.. I figured it would throw a code but it was definitely 145deg C. I should've taken some pictures at the time but didn't think to.

 

I'd say about 1-2km/ 1.2 miles? till I decided to turn around and go back.

 

not sure if tech can plug in obd reader and pull some historical data or anything.. 

 

Meant to drop it off tomorrow to have couple of things looked at.

 

 

Edited by Giantpeaches
Posted

At 290f you cooked all your fluid and probably want  a new trans. Probably a sensor issue. let it sit all night and check the temp in the morning, it should be within 10 degrees of the outside temp.(actual temp not the trucks outside temp).

Posted

What does the fluid look like?  At that temp like posted above I would think it would have effected the color and no longer be a nice pink color.

Posted
1 hour ago, BlancoSilverado said:

At 290f you cooked all your fluid and probably want  a new trans. Probably a sensor issue. let it sit all night and check the temp in the morning, it should be within 10 degrees of the outside temp.(actual temp not the trucks outside temp).

since then it's been running normally. I don't exactly know what the normal temperature for city/hwy driving is for these trucks and tranny but I find it runs between 140-180F

 

Posted
27 minutes ago, Black02Silverado said:

What does the fluid look like?  At that temp like posted above I would think it would have effected the color and no longer be a nice pink color.

Is there way to check fluid color on these 8 spd transmission? I just know there's no dipstick to check the level or anything

Posted
1 minute ago, Giantpeaches said:

Is there way to check fluid color on these 8 spd transmission? I just know there's no dipstick to check the level or anything

There is an inspection port so to speak on the side basically where a dipstick tube would go.  There is a plug over it.  Could pull the plug to check.

Posted

Just heard back from the dealer and they couldn't pull any codes or parameters all seem normal and he assured me 140-180 is normal operating temperature.. I asked in Celsius or Fahrenheit? and he said celsius.. seems wrong.... 

  • 2 years later...
Posted

To check trans temp, scroll through drivers info steering wheel, there is one blank screen before the trans temp screen. My truck has a trans oil cooler, I think, and you would think the trans temp would be cooler than 180 degrees F, with an ambient temperature of 40-50 degrees F, and an unloaded truck.

Posted

I definitely have a transmission oil cooler but it doesn't seem to change my temps. I don't think anything is going to keep them lower considering they have a thermostat that keeps them pretty warm. I could be wrong though lol.

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
  • 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, 1,903 Guests (See full list)

  • Latest Articles

  • Posts

    • 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?
    • 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
    • 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...