Jump to content

Recommended Posts

Posted

Transmission cooler line will be a heavier wall. Emissions should be fine and not collapse as it is designed to support vacuum. Fuel line is too soft.

 

Make sure the checkvalves are flowing the correct direction. Away from the can.

I sent you pics as you requested however I have no reply yet.

Posted

 

Can you hear it hood shut? I could hear it if I stuck my head in the bay. With hood shut and normal idling I haven't noticed it at all.

Yes I can however not too loud. When its open there is no doubt. Plus now I smell a little warm oil in the cab and outside. Not much but not normal. Has anyone else with a 2015 5.3 get a hissing noise?

Posted (edited)

Yes I can however not too loud. When its open there is no doubt. Plus now I smell a little warm oil in the cab and outside. Not much but not normal. Has anyone else with a 2015 5.3 get a hissing noise?

 

I do not have any noticeable noise with my catch can.

Edited by fondupot
Posted (edited)

My mechanic had a good thought....why not route the PCV gases directly into the cylinders? "Direct injection" for the PCV system so to speak. It would accomplish the same goal but eliminate the valve buildup issue. Engineers need to consider this approach.

 

 

Sent from my iPhone using Tapatalk

Edited by Silverado-Hareek
Posted

But then, how will you seal against 3000 psi of force when the mixture ignites? No easy answers.

 

My solution is to just go back to having a filter on the valve cover. It worked ... and nobody died from breathing it.

Posted

But then, how will you seal against 3000 psi of force when the mixture ignites? No easy answers.

 

My solution is to just go back to having a filter on the valve cover. It worked ... and nobody died from breathing it.

I mean you can't just run a hose straight into the cylinders. There needs to be some kind of engineered piping system with a check valve if some sort to prevent back pressure. I don't know all the details but they should consider designing a system that safely routes the gases that way.

 

 

Sent from my iPhone using Tapatalk

Posted

Just another system to break and cost $$$. Imagine the carnage (and noise) when the valve lets go ... and we all know it will.

 

There was a time when I trusted automakers to design a good, reliable system. Those days are long gone. Cheap is the name of the game today, unfortunately.

 

Good idea, if they could make it failure-PROOF.

Posted (edited)

So with winter now essentially knocking, how does the Elite CC perform where weather up here can hit -30c? I don't have a heated garage unfortunately. I am a non-aggressive driver but do an easy 500km's a week. Truck just rolled 10k kms. Idling will also be more pronounced as well :sigh:

Edited by SheeB
Posted

So with winter now essentially knocking, how does the Elite CC perform where weather up here can hit -30c? I don't have a heated garage unfortunately. I am a non-aggressive driver but do an easy 500km's a week. Truck just rolled 10k kms. Idling will also be more pronounced as well :sigh:

Temperature shouldn't affect performance of the can unless you forget to empty it and let it fill up too much and freeze. But with the inlet and outlet ports located at the top, air should always flow through just fine.

 

 

Sent from my iPhone using Tapatalk

Posted

Elite, I'm looking of order one of your CCs but not sure of what bracket to order, I have the 5.3 in my sierra...please advise :)

Posted

which bracket has everyone been ordering their elite CC with, I'm assuming the 6.2 would be the same as the 5.3l....

Posted (edited)

which bracket has everyone been ordering their elite CC with, I'm assuming the 6.2 would be the same as the 5.3l....

 

That's correct. Our 62L Bracket fits both the 6.2L V8 and 5.3L V8. If you order a Catch Can, you'll specify your vehicle type during the checkout process. We'll review that information and be sure the correct bracket, fittings, and hardware are shipped to you.

Edited by Elite Engineering
Posted

So, I added a second output fitting to my Original RX catch can. I had been emailing with the RevExtreme folks about the benefits of a dual output can, and they were gracious enough to send me the parts needed to convert my single output can into a dual output can. With some simple instructions they explained to me how to add the second fitting. So this morning I gathered the tools needed and decided to document the whole process. It didn't take long at all. Maybe 2 hours (but I was filming).

 

Here it is:

 

 

  • Like 5

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

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