Jump to content

Recommended Posts

Posted

Now im confused, i just saw a post 07softail posted.

PCV line from under the Throttle Body goes into the catch can and the outlet goes to the side of the intake manifold.

 

RT

PCV side goes to the inlet, and outlet to manifold.

 

RT

Posted

Now im confused, i just saw a post 07softail posted.

The line under the throttle body connects to the inlet on the catch can. The outlet hose connects to the side of the manifold.

Posted

The line under the throttle body connects to the inlet on the catch can. The outlet hose connects to the side of the manifold.

Correct. Think about it like this:

If you place filter media in the provided area, you would want the dirty air from the throttle body to enter there (inlet) and exit through the suction side (outlet) going to the manifold.

Posted

Now im confused, i just saw a post 07softail posted.

 

Lol sorry about that. I've been sick with the flu so not thinking straight haha
Posted (edited)

Installed mine 3-1 and was somewhat startled by what I found in just a day of driving...

 

Here is by bracket... If anybody has access to a water jet, laser or HD plasma I can send you the file.

 

post-140464-0-84161500-1425260935_thumb.jpg

 

My last truck was an '05 Duramax

I blocked the EGR at 40k miles and added a finger stick (eliminated codes)

Sold that truck with 390k miles with the original injectors and still ran very strong and smooth. These mods are key to achieving higher mileages in my humble opinion. Thanks to all that provide the knowledge base here.

post-140464-0-84161500-1425260935_thumb.jpg

post-140464-0-84161500-1425260935_thumb.jpg

post-140464-0-84161500-1425260935_thumb.jpg

Edited by wacko
Posted

Installed mine 3-1 and was somewhat startled by what I found in just a day of driving...

 

Here is by bracket... If anybody has access to a water jet, laser or HD plasma I can send you the file.

 

attachicon.gifimage.jpg

 

My last truck was an '05 Duramax

I blocked the EGR at 40k miles and added a finger stick (eliminated codes)

Sold that truck with 390k miles with the original injectors and still ran very strong and smooth. These mods are key to achieving higher mileages in my humble opinion. Thanks to all that provide the knowledge base here.

Wacko can you hear a suction sound under the hood now after installing the catch can. Just wondering after my install mine did.

Posted

I recently installed mine and I don't have any suction sounds. Is anyone adding any filter media or are you using the can empty?

Posted (edited)

I recently installed mine and I don't have any suction sounds. Is anyone adding any filter media or are you using the can empty?

I had some scotch brite pad in mine for filter took it out still had suction sound. I could hear the suction with the hood closed also.I used 3/8 fuel hose could be trying to suck together but couldn't find where it might be. Had the can mounted at the battery box and all hoses were hooked up correct.I also could hear a slight buzzing sound in the cab when starting off slowly.Took off hose put stock hose back on and all sound went away. I always have problems that no one else has oh well.

Edited by southern_sierra
Posted

I do not have the suction sound and I am using Stainless Steel scouring pad material in the small chamber filter area. I would check for a vacuum leak at a connection. The quick disconnect fittings did go on further than I originally thought they needed to. I did catch it before I put the air box back on but I would check them first.

 

Fyi mine is a 6.2L

Posted (edited)

I do not have the suction sound and I am using Stainless Steel scouring pad material in the small chamber filter area. I would check for a vacuum leak at a connection. The quick disconnect fittings did go on further than I originally thought they needed to. I did catch it before I put the air box back on but I would check them first.

 

Fyi mine is a 6.2L

5.3L here all the connection were secure I checked all 6 conection points clean and dirty side (are secure and snaped in place) and felt around each one to see if it would make any differance in sound. I checked the can it self to make sure the inlet and outlet were clear and open. I loosened the dip stick in the can and pull up on it and it was very good suction there. My hose lenghts are 24 inches from the crackcase and 21 1/2 inches from the intake. I think the crankcase side is sucking to just enough to cause this and when it gets 90 degrees and its over 200 under the hood the hose is just going to be softer. If a go back with a can going to use trans oil cooler hose or hydraulic hose.

Edited by southern_sierra
Posted

I was surprised at how much suction there is when the dip stick is opened. I used 3/8 Napa PCV tubing. Maybe since mine is further inboard and lower it is helping with the noise.

Posted (edited)

I was surprised at how much suction there is when the dip stick is opened. I used 3/8 Napa PCV tubing. Maybe since mine is further inboard and lower it is helping with the noise.

Had mine mounted the same place as yourspost-137309-0-71922300-1425345647.jpeg

post-137309-0-71922300-1425345647.jpeg

post-137309-0-71922300-1425345647.jpeg

post-137309-0-71922300-1425345647.jpeg

Edited by southern_sierra
Posted

Is anyone adding any filter media or are you using the can empty?

Im running mine empty and have no suction noises at all. Cant tell its there.

Posted

I do have a suction noise...but I can't hear it in the truck or after I shut the hood. I have Gates PVC hose and used thread tape on everything with a thread.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)


  • Latest Articles

  • Posts

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