Jump to content

Plugs and wires for old style 2000 Tahoe

TX-TahoeLtd

Recommended Posts

TX-TahoeLtd Enthusiast

TX-TahoeLtd

Posted
Posted

Hi,

 

I did a search and the information I found was for the 5.3L engines.

 

I've got 70k on my 'old style' 2000 Tahoe with the 5.7 - can anyone give me some suggestions on what plugs/wires I need for my truck?

 

Also - what about fuel filters? Hard to replace?

 

I've got a startup problem after it's been cool outside and the truck sits for a while. I carpool to work so it sits there for ~a week and it's starting to turn over a few more times (like 10 or so) before firing up. Once it fires, it's pretty smooth and runs very well. I haven't noticed any significant drop in mpg either.

 

Think plugs/wires/air-filter(time to change, i know it's not part of the problem)/fuel filter will help?

 

Also - once it starts up it's fine after that for the next few days until it sits for a while.

 

Maybe she's just mad at me for not driving her more. ;)

Mule Enthusiast

Mule

Posted
Posted

I bought a "tune up kit" from Summit racing. Plugs, wires, cap and rotor. All made by Accel and good quality and performance. About $100.

 

The fuel filter should be along the frame rail under the driver's door. Not too hard to change. Just go easy with the wrench, put the new one in correctly according to the arrow on the new filer, and make sure you have something to catch the small amount of gas that will run out when you remove the old one.

99-2door Senior Enthusiast

99-2door

Posted
Posted

When changing the filter go through this procedure to keep from getting sprayed in the face with fuel.

 

1. Open the hood and take out the fuel pump control relay.

2. Start the engine and let it run until it dies from lack of fuel.

3. Now you can undo the lines to the filter and there will be no pressure on them.

 

When you order wires or plugs, just make sure you tell them you have the 5.7L engine. A lot of places get confused by the carry-over models. You can just tell them 98 Tahoe if you want.

 

MSD makes a killer set of wires for the 5.7L

TX-TahoeLtd Enthusiast

TX-TahoeLtd

Posted
  • Author
Posted

Thanks all - I ran to Pep-Boys and gathered all the parts.

 

I'm 2cyl shy (back 2, psgr side) of completing it - just ran out of time yesterday.

 

This was my first time doing anything like this and it was a little more difficult than I had expected, especially getting the cap off and put back on. I had to climb into the engine bay to figure out how to get the dadgum thing off.

 

Just took a little patience and lots of elbow grease.

 

 

Anyone know what's in that box that sits up on top of the throttle body that is labled 'vortec'? Anything that needs to be changed out?

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • 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
    • davester
      Replacement Radiator

      By davester · Posted

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