Jump to content

Recommended Posts

Posted

I'm having an issue I can't resolve with my Tahoe. It's a 95, 4x4, 2dr, 5.7, with a 5 speed manual in it. It wants to miss on acceleration and pop a lttle through the exhaust. It doesn't matter if its cold or up to temp. When it first started, about 3 weeks ago, it was only in 3rd gear under medium acceleration. Then it started in 5th gear under a load, like pulling a hill. Now it's in every gear but 1st.

 

I have replaced, since the issue plagued me,

TPS & connector

MAP

EGR

CTS

Distributor

 

I have replaced the fuel pump since I've owned it (little over 3 years). The tune up is less than a year old. Knock sensor is less than 2 years old. IAC is maybe 3 years old. All with Delco/Delphi parts with the exception of the distributor. It's NAPA, Cardone I think.

 

I replaced the distributor because the trigger wheel(reluctor?) had a pretty good crack in it. So last night after replacing, setting time, and clearing the code, I drove it about 20 miles with no problem. Get in it this morning and pull out on the road, get to 2nd and feel a tremble, go to 3rd and it bucks and misses. I feather it out, hit 4th, bucks and misses.

 

Disconnecting the battery is the only thing that makes it go away, temporarily. On the next startup, it's back to bucking. Any fresh ideas would be appreciated.

Posted

No takers?

 

I drove it yesterday afternoon, a good 40 miles of stop and go on backroads. Eventually the problem went away. By the time I got close to home I couldn't make it miss. Get in it this morning and it misses like hell. I put about 30 mile on it this morning and the problem fades away. O2 sensor not heating up maybe?

Posted

The code was form disconnecting the timing wire. Which also answers lee123's question, I set the timing with a light.

 

I pulled the plugs Thursday afternoon to find they were all frosty white(bad lean). I brushed them off, checked gaps, put them back in, and disconnected the battery to clear the CTS code. It set the CTS code because I wanted to see if being unplugged made a difference in anything. It idled a little higher, which I expected, but didn't resolve the main problem. I only drove it a couple of miles with the CTS unplugged, I squirted a little WD-40 on the grounds by the water neck and took of on a test drive. It never acted up for the 40 or so miles of starting and stopping I did on the backroads, and I didn't expect it to.

 

I jumped in it Friday morning and expected the miss and nothing happened. Drove out like a champ. And it's been good since. So either the plugs were that big of a problem, which I doubt, the issue finally reset with a battery disconnect, or the grounds needed WD-40. I found someone with a live-data scanner that won't rape me like the dealer would if I went to them. When the issue hits again I'll be ready.

  • 2 weeks later...
Posted

The miss came back about 10 days later. It started small, occasionally in third, then worse and worse by the day. Always bad on first start of the day and getting better the longer it ran. It acted up until the scanner was hooked on it. Then it didn't miss a beat. It was a nice SnapOn scanner, but it couldn't tell us anything usefull. Only whether or not it was in open or closed loop, the temp, rpm's, and lean/rich from the 02 sensor. No live data, like TPS % or IAC and O2 counts.

 

So I think I'm gonna throw another 20 bucks at it and put an oxygen sensor on it. If that doesn't do it, I'll start replacing connectors.

Posted

Yep. I've waved an unlit torch around about everywhere I can think of.

 

This things got me. I went home for lunch, spit and sputtered. Came back to work, it didn't miss a beat at first. I slowed to make a turn, had to downshift to 2nd, accelarated with no miss, shifted to 3rd, hit the gas and wham, big miss. Then nothing the rest of the way. And it doesn't seem like it's wanting to settle into it's idle. Like it's a fuzz higher than usual. Got a different tone to it or something. Just doesn't seem right.

Posted

My truck had somewhat similar issues when my dad had it. I am not very knowledgable but after a new ground wire was installed it fixed the issues.

  • 2 weeks later...
Posted

I had the distributor cap off of it Tuesday afternoon and noticed the center terminal, coil terminal, was loose. I put a cap on it yesterday and fixed the problem. That was the third time I've had the cap off since this issue started. I touched the terminal just right to feel it wiggle.

 

Thought I would post back because I've seen so many topics on forums all over yet nobody ever posted the fix. But my fix may not be someone else's.

  • 1 year later...
Posted

I know this is an old thread but thanks for posting the fix, I'll definitely remember it if and when needed.

  • 3 years later...
  • 10 months later...
Posted
On 7/17/2014 at 9:05 AM, jham0077 said:

I am having almost identical problem in my 1997 GMC Sierra C1500 4X4.

 

 

No takers?

 

I drove it yesterday afternoon, a good 40 miles of stop and go on backroads. Eventually the problem went away. By the time I got close to home I couldn't make it miss. Get in it this morning and it misses like hell. I put about 30 mile on it this morning and the problem fades away. O2 sensor not heating up maybe?

 

On 7/17/2014 at 9:05 AM, jham0077 said:

No takers?

 

I drove it yesterday afternoon, a good 40 miles of stop and go on backroads. Eventually the problem went away. By the time I got close to home I couldn't make it miss. Get in it this morning and it misses like hell. I put about 30 mile on it this morning and the problem fades away. O2 sensor not heating up maybe?

 

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,858 Guests (See full list)

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