Jump to content

95 1500 5.7 running rough and high vibes


Recommended Posts

Posted

I have a 95 1500 5.7 z71. My transfer case shifting fork broke of for 2h and 4h. So my truck was stuck in 4l. I took it to aamco and they replaced the fork and put new gaskets seals and the whole nine yard to fix my tcase. after getting my truck back, it runs rich now. They claim they are not liable for any issues. No big deal to me, but i still have the issue. My truck idles fine, but once in drive it vibrates harder the block slightly shakes and it runs rich. I cant hear a particular miss in the motor but it vibrates and you can hear out of the exhaust a continuos tsst tsst tsst sound while sitting there in drive. I replaced the plugs, wires, d cap and rotor about 8 months ago, so it should be any issues with it. they are all connected ok. occasionally my check guage light will come on now. My egr valve is new, all my vac hoses are good, i also have a new o2 sensor. When i pop the hood with it in drive, it almost seems like the tsst tsst tsst sound is kind of coming from the throttle body injector area. I have a long trip to make this weekend and it is paramount that i get my truck fixed. also at about 55 it shakes even worse. plz help

Posted

while the truck is running check out the injector spray,you could have a clogged injector or a leaky one,also spray carb cleaner on the base of the thorttle body.

Posted

it happened all of a sudden thats whats strange, i will try what you said though

Posted

long shot here

 

you may have thrown a rocker. It's happened to me twice. The engine would idle ok, but once you hit the gas it felt like it was going to fall out of the the truck. It would shake bad, and you could really smell the gas from the exhaust.

 

but you should check for vacuum leaks and the injectors first.

Archived

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

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...