Jump to content

custom air intake, size of tube


duffy

Recommended Posts

Posted

Is the size of tubing going to affect performance. First off, I have an 01 6.0 hd and also have flex-a-lite dual electric fans. That gave me more room to work with when making my kit. I used rubber plumbing connectors and pvc. I have 4 inch pvc from the throttle body over to the MAF sensor and a K&N attached directly to the other side of the MAF sensor. It is hard to tell if this made a difference and that made me wonder if the pvc could be to large. I will try to get some pics tonight. Any comments are appreciated. :cool:

Posted

Yes it does sound different, but I have actually lost mileage instead of gaining. some of the problem may be from picking up hot air from the engine since I haven't made a heat shield yet. I may try 3 inch instead of 4 inch pvc and also try putting some space between the MAF sensor and the filter. If any one else has any ideas please let me know.

Posted

I'd think your main culprit is the hot air. having a bigger intake will slow the air velocity, but shouldn't be much different than having a different size pipe if your tb is the same. Most aftermarket companies make between 3-4in intakes.

Posted

I made a heat shield and now just need to get some mile on it to see what happens. It may take a while because I'm driving the older truck and leaving the 01 with my wife. She had our first little one a few weeks back so I am leaving the good truck with her. I will post back when I find out more.

  • 3 weeks later...
Posted

It is just high gloss spray paint from an auto parts store. I'm in the process of rerouting the pvc over the radiator hose and out of the hot air that comes through the radiator. I am also making a heat shield out of plastic to block the hot air from the engine bay. I hope to get it done this weekend and get some pics.

  • 4 weeks later...
Posted

Another thing you need to watch out for it the oil from the filter putting an end to your MAF's life. This is common in many other vehicles I have had... not so much with the factory oiled unit but when people clean and re-oil they tend to get a little over zealous with the filter lube. Just my .02...

Posted

That is a good point, you can't get in a hurry. You've got to give it time to soak in.

I've got updated pics on mct.truckmocie.com under Duffy in the gallery. I can't get the pics on here.

Posted

I'm wanting to also make a heat shield out of plastic to block off the hot air from the K&N. I'm trying to make a custom CAI, what did you use to make the heat shield? I was thinking about using a black rubbermaid box and cut it down to fit, does anyone here have a better idea? Thanks, Chris

Posted

I used a big plastic tub that held minerals that my cattle can lick on. I just cut it to fit. It was round so it worked out nice. I bet the rubbermaid would work also.

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