Jump to content

Transmission issue, or just paranoid? 5.3L w/ 4L60


Recommended Posts

Posted

Truck has 82 000 on it, got the transmission service done, had the fluid drained and the filter replaced.

 

I noticed (even before the transmission service), the truck sometimes shifts hard when going from first to second. Sometimes it even does it from third to fourth. I don't know what actually constitutes a "hard shift" but I can certainly feel the truck shifting, but it doesn't launch me forward or anything.

 

I only really notice when I'm accelerating slowly, I usually accelerate a lot harder. Could it be the TCM adapting to "new" driving habits? Am I in for a transmission rebuilt? Is it just a 4L60 thing?

Posted

first thing i would do is clean your MAF. a dirty one can cause trans shift issues..

 

 

I'll clean that, thanks.

 

As I said you feel the shift sometimes, ya, but it's something only the driver will feel, through the gas pedal and what not.

Posted

i was a tranny guy up north for 3 yrs and i sent more than one out the door doing that and never heard another word about it

 

all shifts are of course electrcal ,the amount of throttle you have at the time of the shift is what the ECM uses to determine how much line pessure to put into the shift

 

there is no nicey slopey sliding gradual(clutch killing)shifts going when a firm shift is goin on ,

 

your right the shift adapts are what happens in a rebuild but yours are "up to date"to pick a phrase,

 

what im gonna sum up and say is ,firm shifts are better than soft shifts and that they are computor controlled ,it would take me forever trying to figure out why a firm shift happened while driving slow,

 

your truck has no TCM,the PCM does it all,Allisons have a stand alone TCM only

 

IDK what to tell ya ,maybe a few minites with a master gauge on the line pessure port and goin for a spin along with a tech 2 scanner

 

also max line pressure is also a default on alot of tranny codes to get your attn,maybe get it scanned for giggles first

 

hope this helps abit

 

 

rambling over lol

Posted

After 54k miles on my previous 04 Sonoma & now 90k miles on my Sierra, they both have acted precisely like you described. I'd not worry about it unless it stops acting like that.

  • 3 weeks later...
Posted

My truck does the exact same thing, only from 1-2 under light and slow acceleration. I do have an iffy mass air flow sensor that needs to be replaced, but I don't think that's it. I try to always have it shift 1-2 at 2000 rpm or higher and it won't do it. I try not to worry about it, think it's fairly normal. Also, it has never done it while towing.

Posted

rather have firm shifts then softs shifts.Learned that the hard way.

 

 

i bought a 700R4 (4L60 predesseor) SRTA (GM rebuilt tranny) before i was in GM for my 85 "burb" 2wd diesel and i beat the piss out of it draggin a trailer etc and it slammed into gear all the time ,when i tore her heart out and tranny to crush the shell (insert tears here) i took it apart to steal the 3-4 clutches that went for a poop in my 93 C10 i put her engine in and that tranny was as fresh as can be ---it had 250K km on it !!

 

i put a SRTA in my 93 before i left GM for the discount !! 3 yr warranty,,,no brainer

 

im chatty tonight ok ??

 

lol

Posted

I drove a buddies GMT800 with 4.8L and the 4speed, shifts pretty much the same as my truck. I can feel it a little more in my pedal than I could in his though.

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

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