Jump to content

Recommended Posts

Posted

 

 

 

Actually emission code is a Federal law, unfortunately modifying / removing / tampering with is an automatic warranty void. 

The MMWA doesn't protect a buyer from tampering with a Federally mandated system. 

 

The consumer would be responsible for all court fee's and then repairs (if any needed) to fix the system and or engine problems.  

 

Most dealer's are not going to challenge you on this or deny a claim due to having a CC.

 

 

 

If you really want to get technical DOT can pull you over and do an inspection while also ticketing you for tampering with the system and driving on federal road.

 

But it's your 45-60k truck, do what you want lol. 

 

 

[mention=161433]Grumpy Bear[/mention] you would be suprised what the T1 pcm's will tell a dealer now.  They knew I had changed out my tag lights to LED's due to the pcm throwing an internal code for a voltage fluctuation.

Luckily my dealer service manager is a friend and let me see what was going on.  It might not be throwing a CEL on the dash, but when GM plugs in, they know a lot more than people think. 

 

I work for Subaru of America,  and our engineer's have to go out to dealers all the time and plug into Wrx's  / Sti's to verify warranty claims on blown engines.

You get there and they look completely stock,  Some people even go as far as repainting the bolt heads to make it seem they have never been broken loose. As soon as the engineer's plug into the pcm, they can tell if the engine has had modifications, even as something as small as a high flow filter increases air flow against the maf which the pcm flags and saves for a period of time. 

 

Now are they gonna void a warranty for a K&N filter per say, no.     But when they install tuners to the pcm (marry them), it flags the point adjustments we're made to the software and that's how they determine who's fibbing lol. 

 

 

 

And for the record, I have a CC on my 2019 LT 5.3.    Sooooooooooooooo Bleh!

   

 

This is a topic where 2 things are inappropriately intertwined. If a dealership or manufacturer refuses to honor a warranty, and the customer sues, the customer is the plaintiff and the dealership or manufacturer are the defendants. The only way the customer is a defendant is if the federal government charges the customer with violation of a law, and the customer chooses to provide a defense against the charges in court.

 

Regarding who is responsible for paying the plaintiffs' fees, it's only applicable if the defendant lost the court case.

 

Should a customer/defendant against the federal government be able to compel the court that the modification actually improves/reduces emissions, then the modification is keeping the intent of the federal emissions regulations, and no violation has occurred. Burden of proof is on the customer/defendant.

 

Should the customer/plaintiff against the dealership or manufacturer be able to compel the court that the modification actually improves/reduces emissions, then the modification is keeping the intent of the federal emissions regulations, and no violation has occurred. Burden of proof is on the customer/plaintiff.

 

As for legal fees, etc, they're only applicable if 1) the plaintiff petitions the court for said fees, and the court agrees, and 2) defense lost the court case.

 

For the record, IANAL. I also don't pretend to be one on the internet. Although I attempt to provide factual information, a lawyer should be consulted. I'm not an expert, but I've done a bit of research over the years. For liability purposes, do not take what i say as the final word on the matter. Pick and choose your battles. Remember, the dealership, nor the car manufacturers, represent the federal government. A lawsuit regarding the warranty coverage of your vehicle wouldn't be against the federal government, but don't be surprised if the federal government was brought in by the dealership or manufacturer should you challenge the matter in court.

 

Sent from my SM-N960U using Tapatalk

 

 

 

  • 5 weeks later...
Posted

Here I am, a GMC noob, searching for information on catch cans (how they work, what they do, etc) and the thread I find turns into a keyboard warrior battle that really has nothing to do with the OP. 

People who put aftermarket shiny bits on their trucks assume the risk of that shiny bit messing something up. Got it. Move on. Don't ruin what could have been an educational post by turning it into a pissing contest.

 

Thanks to the OP for the try. 

 

Posted

Agree.

This is a personal decision. I have one and think it's a good idea. Especially with the GDI engines.

:)

Posted

I must have missed the part where someone confirmed that a thimble full of oil making its way through the intake manifold over the course of 5000 miles is actually a concern. 

  • Like 2
  • Haha 1
Posted
I must have missed the part where someone confirmed that a thimble full of oil making its way through the intake manifold over the course of 5000 miles is actually a concern. 

Im seeing quite a bit more then a thimble in the catch can over 4-5000 miles. Id rather it in there then the IM but to each their own
Posted
1 minute ago, lt1z said:


Im seeing quite a bit more then a thimble in the catch can over 4-5000 miles. Id rather it in there then the IM but to each their own

Like I said, I must have missed your post with your experience. Certainly I would be concerned if there was a "significant" amount of oil in the can at every check.

Posted
Like I said, I must have missed your post with your experience. Certainly I would be concerned if there was a "significant" amount of oil in the can at every check.

I dont generally post about things that are common knowledge, at least to me. I work on LT engines everyday and have since late 13’. This is not isolated, just how the pcv system works and what GM considers normal vs what most would like to see. As I said, do it or don’t but the experience is there on this end with extensive stock and heavily modified LT based engines on top of LS.
Posted

Total Seal, Grant, TRW, Mahle, C&A would all disagree with GM on what 'normal' oil usage volume is.

So would any builder proud of his work.

GM defines normal as the level of usage they will warranty.

Has nothing to do with the physics of it. 

In 1970 they called a quart in 500 normal for the 454. 

Hey, just pour it on the ground. 

Posted
On 8/26/2020 at 8:56 AM, Daryl Casey said:

Here I am, a GMC noob, searching for information on catch cans (how they work, what they do, etc) and the thread I find turns into a keyboard warrior battle that really has nothing to do with the OP. 

People who put aftermarket shiny bits on their trucks assume the risk of that shiny bit messing something up. Got it. Move on. Don't ruin what could have been an educational post by turning it into a pissing contest.

 

Thanks to the OP for the try. 

 

Thanks. I tried to reel it back in and keep it informative, but no luck. 

  • Like 1
  • 7 months later...
Posted

if you have a new 6.6 gas you will need a can with double hookup or two separate cans for two seperate pvc valves one on each valve cover also if you are in california you will need a carb sticker.

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

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