[HX_Guy]

What kind of stupid shit is this?


The car never exhibited the things they are pointing out, all I got was the check engine light. Took it in and they cleared it, but in the process also wiped out all my custom changes I had made (5x blinker, no nav warning screen, no seat belt chime, etc).

If this shit happens 2 more times before they can actually fix it, isn't there some lemon law that applies?

[Zooks527]

Originally Posted by HX_Guy

If this shit happens 2 more times before they can actually fix it, isn't there some lemon law that applies?

Interesting question.

We did one of the first lemon law returns in MA back about 30 years ago, when my wife's car continually set an engine overheat light, even though the engine wasn't overheating. Chevrolet took about 5 tries to fix it, then gave up, but they fought the lemon return as the car wasn't actually overheating.

6 weeks of spitting contests ensued before they finally took it back, accepting our argument that even though the car didn't have a problem, we couldn't reliably use it as we couldn't be sure it wasn't actually overheating at any point in time.

In your case, I believe that an SES light is emissions related, which may give you a bit of a leg up in the argument.


EDIT: Then again, you coded your car, changing BMW default software in the process. I'm not sure I'd mention the custom changes you made to the car's operating software. You may find yourself SOL on any warranty coverage as it looks to be a software fault and they'll certainly claim that you caused it.

EDIT 2: You know, I realize it's veering into Black Helicopter territory, but if someone from BMWNA saw the post above, they could identify your car from the PUMA number in the picture and, if they wanted to be a pain about it, start sending "you kissed your warranty goodbye" letters.

Interesting times.

[hyperzulu]

I agree with Edit 2... I wouldn't post stuff like that on here. It isn't out of the realm of possibility that it could come back to bite you in the ass.

[Racer20]

So it sounds like your check engine light is on because there's was a one time issue with the fuel level detection sensor reading. They cleared the light and found the sensor to be fine, and confirmed that there will be a permanent fix for the issue in an upcoming software update.

I don't understand what you're complaining about. It should be obvious that taking the car in for a CEL might result in your custom coding being erased. There should be no effect to the drivability of the car.

As far as having the BMW Lemon Law the car over this issue? That's a bit extreme, especially considering you modified the software.

[midwest 340xi 6sp]

Originally Posted by hyperzulu

I agree with Edit 2... I wouldn't post stuff like that on here. It isn't out of the realm of possibility that it could come back to bite you in the ass.

Legal system Darwinism...

[HX_Guy]

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

[335BOY]

Originally Posted by HX_Guy

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

Did you do it all through nav screen? Why 5 clicks for turn signal and more importantly why shut off seatbelt reminder?

[overcoil]

Originally Posted by HX_Guy

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

I though the tech did a pretty cool diagnosis, even gave you a little gas.
More important I didn't realize you could nix the seatbelt chime through iDrive.

[hyperzulu]

Originally Posted by HX_Guy

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

If it's a toggle switch, button or iDrive setting, I'd agree. If it's something you configured using internally leaked, hacked software...... I mean, come on.

[Zooks527]

Originally Posted by HX_Guy

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

The issue isn't whether you modified the software or simply changed default settings. The issue is that you made unauthorized changes within the ECU. BMWNA could use that to deny warranty claims.

But, hey, you're right. What do we know? Give BMWNA a call (1-800-831-1117). Make sure you give them your VIN. Tell them you've been making coding changes within the ECU settings, and make sure they know you're disabling safety features (seatbelt chime and NAV warning). Ask them if you've voided your warranty for sensor and software faults.

Originally Posted by 335BOY

Did you do it all through nav screen? Why 5 clicks for turn signal and more importantly why shut off seatbelt reminder?

Originally Posted by ScottSinger

More important I didn't realize you could nix the seatbelt chime through iDrive.

You can't do any of this through iDrive. The OP is accessing the ECU through the OBD port using 3rd party software and making changes to normally inaccessible settings within the ECU.

[escobar929]

Originally Posted by hyperzulu

If it's a toggle switch, button or iDrive setting, I'd agree. If it's something you configured using internally leaked, hacked software...... I mean, come on.

Exactly, i don't why OP is mad. Yea it's annoying to have to recode the car but that's something you have to deal with if you want custom settings. And yes they are custom, it's not a regular setting, it's something you're doing through software on a laptop.

Very minor changes so I doubt BMW would go after the OP but I agree that I certainly wouldn't post about it if possibly going after lemon law

[overcoil]

Originally Posted by Zooks527

You can't do any of this through iDrive. The OP is accessing the ECU through the OBD port using 3rd party software and making changes to normally inaccessible settings within the ECU.

I know, was just facetiously inferring that if it's not in iDrive settings then...
To read the printout I don't see how you could fault the tech.

[Zooks527]

Originally Posted by ScottSinger

I know, was just facetiously inferring that if it's not in iDrive settings then...
To read the printout I don't see how you could fault the tech.

Looking at the level the tech went to, I'd buy the guy a beer, and still be ahead with the cost of a full tank.

[Racer20]

Originally Posted by HX_Guy

You guys are funny...what modified software? This is stock BMW stuff that can be turned on/off, it's nothing "custom".

Sorry man, maybe you were lead to believe something different, but "coding" is not authorized by BMW and can absolutely void your warranty if BMW decides to do so.

[pruettfan]

Originally Posted by HX_Guy

What kind of stupid shit is this?


The car never exhibited the things they are pointing out, all I got was the check engine light. Took it in and they cleared it, but in the process also wiped out all my custom changes I had made (5x blinker, no nav warning screen, no seat belt chime, etc).

If this shit happens 2 more times before they can actually fix it, isn't there some lemon law that applies?

If you have three identical failures you can pursue a lemon law claim in AZ but I have to say it is unlikely that you will have a chronic problem with a code like this. The tech is pointing out that some times topping off the tank can send fuel down one of the breather hoses that causes a check engine light to trigger, I have had this problem with my E90 during the hot summers here in AZ but I just reset the light myself with my code scanner.

How did you program those custom settings?

[HX_Guy]

Originally Posted by Racer20

Sorry man, maybe you were lead to believe something different, but "coding" is not authorized by BMW and can absolutely void your warranty if BMW decides to do so.

I understood that coding...as in engine tuning...*could* void your warranty, but not BMW built in options that are just turned on/off for our US market...how could that ever void a warranty?

Its like with car mods...an auto manufacturer would have to prove that the specific mod caused the failure and then they could only void that part of the warranty, not the warranty on your whole car...at least that's how I've understood it to work.

[HX_Guy]

Originally Posted by pruettfan

How did you program those custom settings?

Like this: http://www.2addicts.com/forums/showthread.php?t=997749

And I have a OBDII Bluetooth dongle thing as well, so I assume I can probably clear the code if it comes back.

I do have to say that the car feels world peppier for some reason, maybe it's in my head, but it feels great. Whatever software update they did was a good thing.

[Zooks527]

Originally Posted by HX_Guy

I understood that coding...as in engine tuning...*could* void your warranty, but not BMW built in options that are just turned on/off for our US market...how could that ever void a warranty?

Its like with car mods...an auto manufacturer would have to prove that the specific mod caused the failure and then they could only void that part of the warranty, not the warranty on your whole car...at least that's how I've understood it to work.

You're right that modifications can only void the warranty on the piece you've changed (i.e. - if you changed your springs to modify the car's stance, they couldn't claim that caused a turbocharger failure).

But, look at the case you've presented. You're changing elements of the ECU. Granted, you're only turning some options on and off, but there are options in there that may require equipment you don't have (none of the ones you've listed fall into that category). The tech is coming back and saying he's seeing inconsistent readings between sensors read by the ECU.

It wouldn't take much effort for BMW to claim that your setting selctions created an unvalidated configuration of the ECU, and that's why they're seeing sensor discrepancies. Will you still have a warranty on your turbos? Sure, but BMW could blow off any sensor related failures as your fault.

Could you fight it? Probably. Could you fight it cost-effectively? Maybe not.

[DSTR]

Originally Posted by Racer20

So it sounds like your check engine light is on because there's was a one time issue with the fuel level detection sensor reading. They cleared the light and found the sensor to be fine, and confirmed that there will be a permanent fix for the issue in an upcoming software update.

I don't understand what you're complaining about. It should be obvious that taking the car in for a CEL might result in your custom coding being erased. There should be no effect to the drivability of the car.

As far as having the BMW Lemon Law the car over this issue? That's a bit extreme, especially considering you modified the software.

+1 - the OP is risking his warranty and no maker will be taking this car back. He coded it. End of story. He should wait for the update and push his radio button upon fueling as directed. This is a non issue made an issue by the OP.

My dealer in Germany would be submitting a report to BMW about his coding. He would not be pleased with the feedback from Munich.

[delvec03]

stupid question....

if your car seems slugglish could that be a fuel pump issue? there was a recall for 2014 2ers. figured I'd bring it up.