Jump to content

Not another catch can debate

SquireSCA
 Share

Recommended Posts

SquireSCA Enthusiast

SquireSCA

Posted
Posted

Not looking for advice on them, there are a thousand threads on that already...  I have good results on my 2018, based on the amount of oil trapped in it, and the fact that the return line from the can to the manifold that is under vacuum, is pretty much bone dry. 

 

Mine has a very fine steel wool "filter" inside the can, filtering the line coming in from the PCV which forces the atomized oil in the hot air to condense and form droplet and drain into the bottom of the can, rather than just get sucked into the can and right back into the motor where I don't want it.  Used this way, it appears that like 98% of the oil is trapped and doesn't make its way into the manifold.  For $40, that's good enough for me.

That said, looking under the hood, this motor and setup on the 2019 LT Trail Boss appears quite a bit different than the 2018... Intake is on the other side and things are moved around and the front end seems more compact and cramped...

So where is that line?  Is it still under the throttle body?  It's hard to see down in there on this model...  Wondering where it is, what size hose I need to get and how much, etc...

Thanks!

SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted

So I found this video.


Interesting, it seems that the new 5.3L doesn't use that line underneath the throttle body...  The motors up to 2018 had 3 vent lines essentially... Two at the valve covers, and one under the throttle body...  That throttle body one is the one that went to a catch can when you installed one.

Now it seems that the passenger side valve cover dumps to the intake tube, and the one on the driver side connects to the manifold...

I am guessing that the one going to the intake tube isn't too bad because the vacuum drawn is minimal, and the one going directly to the manifold via the vacuum line is the one getting the most oil?

Texasdeere Enthusiast

Texasdeere

Posted
Posted

I've been researching different catch can options for my 2019 5.3.  On the 19's the pass side valve cover hose is a fresh/clean air source "into" the engine through the valve cover.  It's pulling a small amount of air from the airbox. (Filtered Air Before The Throttle Blade)  It has to be able to pull clean air into the engine.  All the suction and vacuum is on the drivers side through the PCV valve. 

Texasdeere Enthusiast

Texasdeere

Posted
Posted

I'm considering trying the ADD-W1 V series. 

 

Looks like it has a "dip stick" and a drain option other than that looks well made and simple while not too expensive.

 

There are no 2019 pictures, so I'm not sure where it mounts?

 

The JLT can looks good too.

SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted

Mine should be here some time today, and I will see where I can mount it.  Last time I just took a black "L" bracket from Home Depot and used that as a mounting bracket.  I will take pics of the install and post them up when I am done.

SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted

Install was easy.  Mounted it right up with an L bracket from Home Depot and a lock-nut to that mounting screw for the washer fluid reservoir...

Connected the two hoses, done.

I did make sure to unscrew the internal filter that the "in" line with the oily mist flows through, and filled it with steel wool... this "filter" forces the hot oily air to breath through that, and very effectively separates out the oil before the vacuum line draws that air into the manifold.  Those droplets form inside that inner filter, and then drip into the bottom of the can...  

Here it all is, installed.

IMG_0460.JPG

IMG_0459.JPG

  • Like 1
  • Thanks 2
SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted
1 hour ago, Londart2020 said:

Looks like quite the pain to empty when the time comes...

You do have to contort your wrist a bit to unscrew it...  lol

SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted

I mean, it gets cold at night here.  I have had the same one on my 2018 Z71 for a year now.  No issues.  Collects a decent amount of oil, several ounces ever 1000 miles, and it doesn't seem to be letting much if any into the return line that goes to the manifold...

BlancoSilverado Enthusiast

BlancoSilverado

Posted
Posted

Blanco getting a catch can. After 2000 miles pulling 1/3 cup of oil/water mix.

i have around 12k miles on it and pulled alot of crap. Intake after throttle body is OIL FREE (paper towel test).

 

 

  • Thanks 2
wurgs Senior Enthusiast

wurgs

Posted
Posted
On 12/24/2019 at 7:01 PM, Bobv07662 said:

Call me back after you evaluate it's operation in a low temperature environment!

I had one in my 2015 up till I traded it in and worked great in the cold winters here.

SquireSCA Enthusiast

SquireSCA

Posted
  • Author
Posted

Was at the dealer for one of the recalls and my first oil change yesterday... They are cool with catch cans...  They say that as long as the person drains it and maintains it and it's installed properly, they see them a lot and don't have issues with people using them...  I also discussed the DFM concerns that I have, and he said that if Range puts out a box to disable it, to get one.  He said less headaches for me and them if we disable AFM/DFM and keep the valves free from crud with a Range box, etc...

He pointed out that to deny a warranty claim, there would have to be something faulty with the catch can that clearly CAUSED the problem...  Which I knew to be the law, but it was cool to see the service manager bring that up...  They know that AFM/DFM and GDI has longevity issues, and so taking steps to avoid those issues are in both party's best interests...

RaisedByWolves Enthusiast

RaisedByWolves

Posted
Posted
On 12/26/2019 at 8:26 PM, BlancoSilverado said:

Blanco getting a catch can. After 2000 miles pulling 1/3 cup of oil/water mix.

i have around 12k miles on it and pulled alot of crap. Intake after throttle body is OIL FREE (paper towel test).

 

 

Thanks for the video.

 

I placed an order with RXP mid November and Im hoping to have it soon.

 

Where did you put your drains?

BlancoSilverado Enthusiast

BlancoSilverado

Posted
Posted
2 minutes ago, RaisedByWolves said:

Thanks for the video.

 

I placed an order with RXP mid November and Im hoping to have it soon.

 

Where did you put your drains?

I put the drain leading to the front of the passenger tire. works great.

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...