Quote:
Originally Posted by atomicalex
Sounds like early 2018 build date?
Mine was built in March, no issues so far with 5500 miles on it. (yes, I do a lot of driving. Thank goodness, as I love being in it.)
|
I'm a 12/17 build according to the placard. This sucks! Feels like it's a ticking time bomb.
Quote:
|
There's more info at this thread, and I posted some details of what the dealer did in my case:
|
Saw that and read through it all and did as much research on TSB 01-177-16 without having to pay for the document. This TSB was issued in 10/16 so it has been a known issue for a while.
Just in a rough statistical sense the amount of people that have been affected by this is quite notable when you consider how small the sample group is. 3-4 cases already? Is this a foregone conclusion for early MY18 vehicle manufacture dates?
Hauling the engine out of a brand new car to fix a defect that should have NEVER come out of the factory is a major issue! That wouldn't cotton with me!
I would not be happy with that fix at all. Too many other issues could be injected into the car, just by taking the engine in and out. One guy had a P219a issue, they did the fix (TSB 01-177-16) and he got the car back with clutch issues, he then had to fight that.
All this is not what I bought a new car for, I don't care how good it handles.
Now I have to seriously think about the major investment in aftermarket equipment that I just made in this vehicle if it's going to sh*t a code that means the engine needs to be dropped. So, instead of looking at enjoying a boosted vehicle the only thing I can look forward to is if and when it is going to sh*t that code. How am I going to get out of FI purchase? Knew I shouldn't have done it.
I have an old OBD Scanner in the garage. I may have seen the check engine light on for a second, but who knows. If it trapped a P0300 or P219a code, I am seriously pissed! Addendum: No codes yet.
Can't have any fun! F-Bomb!
I hope TylerLieberman is correct, but right now I have no confidence.