21 captured repliesPartial discussion capture · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHShould I risk it?
Leading reported evidence
Run pretty much normal
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm not sure what's under the "check engine" umbrella of codes but it could be related to the repairs like an O2 sensor if that is a code within that segment.
Leading evidence: 'Run pretty much normal' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check engine" umbrella of codes' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm not sure what's under the "check engine" umbrella of codes but it could be related to the repairs like an O2 sensor if that is a code within that segment.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
If it's running well, not overheating, losing oil or antifreeze, I'd drive it back with extra vigilance at each stop checking fluid levels.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I did a Google search for a European repair shop and routed to the nearest one, which was ~17 miles away.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
Did you only change the oil change or did you some other things?
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
Check engine" umbrella of codes
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'm not sure what's under the "check engine" umbrella of codes but it could be related to the repairs like an O2 sensor if that is a code within that segment.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
21 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Planet-9: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Update: I took it for a ~5 minute warm up drive before an oil change this weekend and the CEL was gone!
So I'm driving on a trip from the DC area and the car was running fine for 400+ miles, then in around Charlotte NC I hit some traffic. I was stuck in stop an go traffic on I-85 and the car broke something in the exhaust and sounded like a truck! I took the next exit in about a mile of that traffic to assess the situation. The car was running fine, but just sounded like something broke in the exhaust. I couldn't determine the cause from my stop, but there was no oil leaking or anything else. And as i said, other than the exhaust noise the car was running fine - maybe down on power just slightly.
I did a Google search for a European repair shop and routed to the nearest one, which was ~17 miles away. This was around 3:30pm and they were open until 7pm, so there were not many options so I decided to risk it an drive there. It was not the type of shop I expected (I'll post more on that in another post if anyone is interested, but will keep it shorter here), but they were nice enough to point me to another shop about a mile away, so I headed there. They were very nice, but fully booked and couldn't work on the car, but we determined that it was just the that the bolts between the the cat and the exhaust pipe that had broken, and it was safe to drive the remaining 190 miles to Atlanta.
So long story short I made it to Atlanta, took it to a nearby shop the next day who reluctantly worked on it and bolted the flange back together, an halleluiah, it sounded perfect! But when I left the shop a check engine light lit up, which I've never had before. I didn't bring my Foxwell scanner against my better judgement, so I have no way to read the codes. But the car is running perfect, and I need to drive 600 miles back tomorrow. Do you think I should worry?!
If it's running well, not overheating, losing oil or antifreeze, I'd drive it back with extra vigilance at each stop checking fluid levels. I'm not sure what's under the "check engine" umbrella of codes but it could be related to the repairs like an O2 sensor if that is a code within that segment. Given the exhaust was loose and freshly repaired it's the first place to look either way. Have a good trip, don't worry, that never helps.
Air getting in the exhaust system during the problem will throw o2 values off and trigger a CEL.
Might self clear, might need to be reset.
Another possibility is while the exhaust system was a little loose, an O2 sensor wire got damaged or unplugged.
The CEL didn't come on while the flange was loose. It only came on after it was repaired, so I'm thinking the latter is more likely. I'll scan the codes with my Foxwell as soon as I can to see what comes up.
The first place I took it to in Charlotte is called European Motorwerks, which is basically a part of McLaren Charlotte dealership! They were nice enough to point me to Eurowise Service about a mile away.
Lots of the bigger auto parts stores will pull codes for you for free. Quick google search will hopefully set your mind at ease whlle you are away from home and personal tools.
Yes, I thought about that and would definitely have tried to do that if I thought it was something major. Luckily everything turned out OK, but I still haven't had a chance to read the codes (I've misplaced my Foxwell scanner TBH!)
I haven't done anything yet. I was going to take a better look at is when I jack the car up for an oil change, but haven't had a chance to do it yet and I haven't driven the car since then. I wanted to do it this weekend but my back has been killing me.
Sorry, forgot to reply to you. I was just passing by Charlotte on the way to Atlanta. The issue happened in some stop an go traffic on I-85 in Charlotte. I drove the rest of the way to Atlanta after the stop at Eurowise.
Update: I took it for a ~5 minute warm up drive before an oil change this weekend and the CEL was gone! I did the oil change and general check up from under the car and nothing seems to be afoul. Drove to some friends' house ~30 miles away for dinner Saturday night and all is well - still no CEL. The exhaust flange is holding fine so far and the car is running well.
Just the oil change and a general inspection for any damage. I'm not aware of anything else needed other than a permanent fix for the exhaust flange - one of the three studs was broken so there are only 2 bolts holding it. But it is holding fine so far. I'm wondering if there could have been a root cause of the break to begin with, such as a broken engine mount. I couldn't tell if either was damaged from my visual inspection though.
This is a source reference. Confirm exact model applicability in the original material.