Jump to content

New from Missouri, and Air Intake / TBS question


Black57350

Recommended Posts

Posted

Hey guys, I recently joined and I have a couple questions so I figured I'd start here.

I have a '93 C1500 with a 350 small block, it's throttle body injected, and has the stock air pan / pre heater hose assembly, I'm looking for opinions on throttle body spacers and their effect on TBI setups, I know they're pointless for EFI motors, but I was thinking if I had some cash laying around after a few weeks I might get one. My second question is what could I do with my air intake setup, It's all stock except the K&N filter, but I really feel it would do better with a cold air setup, not some heat soaked short ram intake, I mean a cold air with at least a heat shield if I can't find a good enough place to position it to get decent air exposure. I would post pics of the Sierra now, but I don't have any on memory and it's a tad dark for photo ops. ...and she's filthy from all of the road salt and mud. But I can later on when it's light again. Thanks!

Posted

Welcome!

 

On a TBI 350, (or any unmodified truck really), there isn't much to be gained by spacers or CAI's. The difference in intake temp with a CAI is tiny, and sometimes the stock setup is actually cooler. If you've got the money and you feel like it, go for it. If it was my truck, I'd put the money towards future rust repair if I was going to keep it.

 

Feel free to post some pics, and once again welcome to the site.

Posted

Freshen it up. Save the money and drop in a LS1 crate engine. Its a nice 350 HP and will shock a few people

 

Sent from my DROID RAZR MAXX using Xparent Red Tapatalk 2

Posted

Sorry for the late reply, had work etc. And as for the rocker panels, that's going to require cutting and welding isn't it? I didn't really see an easier way than that. And the Throttle body spacer was tentative anyway, there were a lot of mixed opinions on the technology and i figured I could find a better use for $100+. Also, how much do you guys think labor would cost to have someone install the panels? I can get them easy enough, I just can't install them myself since I live in the city limits and it's against city ordinance to do anything more major than an oil change.

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