Jump to content

Recommended Posts

Posted

But in that guys case he runs his engine for a long enough time to remove the water from the oil. If there was any build up of condensation over night, it would turn into steam and go away.

 

It's likely a safe bet to say that people who install a catch can and do check it/drain it on the regular, make more short trips or live in cooler climate that can build up more condensation inside the engine. That why you see milky cheese looking stuff come out of the catch can.

Posted
57 minutes ago, Jdkno said:

Not saying anything one way or the other, this is just my experience. My 17 had 86k on it when I traded it in for my 19 about 2 weeks ago. Never had a single engine issue and it was only at the dealer once about 2 months ago for an AC issue and fixing the chime volume. I changed the oil when the DIC was showing between 10-15%, and checked the dipstic every 2 weeks or so. The dipstic NEVER read below the full mark. Unless I was a rare exception I cant see how I had any oil left between changes listening to what people are supposedly getting out of the can on a weekly basis. If you do the math I'm putting alot more miles per week on my truck than most. 

I ain't sharp?  But that is many miles sir!

Posted
13 hours ago, CamGTP said:

But in that guys case he runs his engine for a long enough time to remove the water from the oil. If there was any build up of condensation over night, it would turn into steam and go away.

 

It's likely a safe bet to say that people who install a catch can and do check it/drain it on the regular, make more short trips or live in cooler climate that can build up more condensation inside the engine. That why you see milky cheese looking stuff come out of the catch can.

Not really. I have 2 long drives per day ~40 miles each to and from my office. My day starts with me making fairly short drives for the better part of the morning until I head to my office a little before lunch. 

  • 2 years later...
Posted

Anybody got any pictures of the intake after 100k miles with a catch can and without? Same climate and conditions? I’ve never seen any. 

Posted (edited)

T1's have 0 need of a catch can. Valve cover's filter out any oil (same as k2). But the T1's don't have a pcv valve coming from the valley. Which is largely responsible for any oil that creates carbon buildup. 

Edited by M1ck3y
  • Thanks 1
Posted
On 6/7/2019 at 9:57 PM, CamGTP said:

But in that guys case he runs his engine for a long enough time to remove the water from the oil. If there was any build up of condensation over night, it would turn into steam and go away.

 

It's likely a safe bet to say that people who install a catch can and do check it/drain it on the regular, make more short trips or live in cooler climate that can build up more condensation inside the engine. That why you see milky cheese looking stuff come out of the catch can.

Is the condensation actually from the engine.  My bet is the catch can is the source of 99% of it.  I have seen a lot where they are mounted where the can cool down quickly and they can lead to a lot of condensation forming the CC IMO.

  • Like 1
  • Thanks 1
Posted

I have used catch cans on a few vehicles, found them to be useful but have no comparative proof. I will say that if you do install one stay away from Mishimoto, the one(s) I have used and seen are garbage.

  • Like 1
Posted
19 hours ago, elcamino said:

Is the condensation actually from the engine.  My bet is the catch can is the source of 99% of it.  I have seen a lot where they are mounted where the can cool down quickly and they can lead to a lot of condensation forming the CC IMO.

 

Moisture builds up in everything including engine and transmission.

 

But like you said 😉 catch can's are largely responsible for that milky color some people see.

Posted
22 hours ago, M1ck3y said:

T1's have 0 need of a catch can. Valve cover's filter out any oil (same as k2). But the T1's don't have a pcv valve coming from the valley. Which is largely responsible for any oil that creates carbon buildup. 

You are 100% WRONG. I put a JLT catch can on my truck(6.2L) when I got home from the dealer with 30 miles on it. I changed the oil at 1000 miles because I like to do a short first oil change to get the break in junk out of it. I had at least 2 ounces of oil in the catch can. The direct injection motors are worse than traditional fuel injection motors because there is no fuel in the intake tract to help wash the oil back into the cylinder.

Posted
1 minute ago, GETGONE said:

You are 100% WRONG. I put a JLT catch can on my truck(6.2L) when I got home from the dealer with 30 miles on it. I changed the oil at 1000 miles because I like to do a short first oil change to get the break in junk out of it. I had at least 2 ounces of oil in the catch can. The direct injection motors are worse than traditional fuel injection motors because there is no fuel in the intake tract to help wash the oil back into the cylinder.

 

Nope, I'm not wrong. 

 

I'm happy your happy though 😉

Posted
3 minutes ago, M1ck3y said:

 

Nope, I'm not wrong. 

 

I'm happy your happy though 😉

So all that oil just magically ended up in the catch can when you say no oil gets out of the PCV? You realize there is NO valve on the valve cover. It is a baffled hole.

Guest
This topic is now closed to further replies.

  • Latest Articles

  • Posts

    • 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
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...