Code 279E??

[kimiraikkonen]

Hi. Went in for an oil change today and on the way back got a BMW code 279E that popped up on the OBD scan.

Carly lists this as a BSD Message Failure...........but I have seen this in the google search show up as an Exhaust Flap error (on other BMW model DMEs). So wanted to see if anyone has received this type of message before. Will check my negative terminal connection when I get home (currently pouring rain right now).

[deansbimmer]

The BSD line is for "Bit Serial Data" communications. On these M3's that is a network between the Intelligent Battery Sensor (IBS), Oil level sensor, and Alternator.

Since any of those three components are known to be equally problematic and worth inspecting, I would start first near the oil level sensor- especially since the oil was just serviced. It is unlikely that the technician screwed with the sensor, but if you're unable to read oil levels currently then it would be worth checking. If the sensor connection is corrupted by oil and grime it can throw a BSD code.

If all connections within those components are clean and proper, clear the code and see if it comes back.

[kimiraikkonen]

Originally Posted by deansbimmer

The BSD line is for "Bit Serial Data" communications. On these M3's that is a network between the Intelligent Battery Sensor (IBS), Oil level sensor, and Alternator.

Since any of those three components are known to be equally problematic and worth inspecting, I would start first near the oil level sensor- especially since the oil was just serviced. It is unlikely that the technician screwed with the sensor, but if you're unable to read oil levels currently then it would be worth checking. If the sensor connection is corrupted by oil and grime it can throw a BSD code.

If all connections within those components are clean and proper, clear the code and see if it comes back.

Dean. hi....thanks for the explanation. Perhaps it was something related to the oil sensor (like a dirty connection).....I did a reset of the codes with Carly...and it hasn't come back since.