Jump to content

Recommended Posts

Posted (edited)

Here you go. good source or pace performance

 

http://www.gmwholesaledirect.com/oe-gm/12628371 or http://www.newgmparts.com/oe-gm/12628371

 

you will need the lower insulator part 12628371.

 

The intake manifold

 

Intake manifold bolts (10 of them). The truck bolts are not long enough.

 

upper insulator 12646904

 

cover 12643576

 

fuel rail covers are optional. if you do get those, you also need the four stud bolts for the cover 11609688. If not, you can use 10mm bolts

c7 engine diagram.pdf

c7 engine diagram.pdf

c7 engine diagram.pdf

c7 engine diagram.pdf

Edited by typhoon186
Posted

Here you go. good source or pace performance

 

http://www.gmwholesaledirect.com/oe-gm/12628371 or http://www.newgmparts.com/oe-gm/12628371

 

you will need the lower insulator part 12628371.

 

The intake manifold

 

upper insulator 12646904

 

cover 12643576

 

fuel rail covers are optional. if you do get those, you also need the four stud bolts for the cover 11609688. If not, you can use 10mm bolts

Thanks alot!
Posted

And the extra idler pulley and longer belt. Add a couple large flat washers behind the pulley to space it even with the belt and us the stock alternator bolt with this pulley.

 

you will have to splice 2 wires to move the connector for the fuel vapor purge canister to the passenger side of the inlet to the intake and extend the hose going to the canister. Not hard to do.

 

That should cover it. Have fun!

 

 

post-130401-0-82190100-1410911207_thumb.jpg

post-130401-0-23177800-1410911222_thumb.jpg

post-130401-0-82190100-1410911207_thumb.jpg

post-130401-0-23177800-1410911222_thumb.jpg

post-130401-0-82190100-1410911207_thumb.jpg

post-130401-0-23177800-1410911222_thumb.jpg

post-130401-0-82190100-1410911207_thumb.jpg

post-130401-0-23177800-1410911222_thumb.jpg

  • 3 months later...
  • 2 weeks later...
Posted

I'd love to hear the results as well. I have my C7 intake sitting in the garage... just waiting another couple months before I do it to get a full year under the belt.

  • 6 months later...
Posted

 

Intake manifold bolts (10 of them). The truck bolts are not long enough.

 

 

Do you have the part number for these? I can't find it.

Posted

No I don't but they should be available on the C7 parts diagram or through you local GM dealer.

Posted

OK. Also, can you elaborate on the mods to the wiring & purge canister? Also, do you have a part number for the plug for that back of the manifold?

Posted

 

Do you have the part number for these? I can't find it.

 

Got lucky, the intake I bought of ebay came with the bolts. FYI, no diagram I can find on the internet shows the part or the PN.

 

Any help on the plug for the back?

Posted

 

Got lucky, the intake I bought of ebay came with the bolts. FYI, no diagram I can find on the internet shows the part or the PN.

 

Any help on the plug for the back?

Have you installed the LT-1 intake yet, Tuned?

 

RT

Posted

No I'm still trying to piece everything together. I'm certain when I get done, I'll document this in detail with all the necessary part numbers. And then don't share it. :S

  • 8 months later...
Posted

Does anyone know the torques for the 10 intake manifoldmain bolts.

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

  • Latest Articles

  • Posts

    • 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?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...