Active Sound gone after latest software update?

[dmnc02]

OK, here is my $0.02.

• VO coding will reset all the coding parameters in the ECU to the default values for the specific vehicle order, as detailed in the FA. However, this will occur automatically at the end of a software update by the dealer: so if ASD was not working after the update, VO coding the ECU will not make a difference.
• According to the CAFD, Werte=06 is the correct FDL value for “Construction Stage” in cars with a build date from July 2015 onward: the change in this value likely reflects the hardware change in the ASD unit on 2016 models.
• I personally believe there is zero chance BMW would deliberately turn ASD off retroactively through a software update. At most, they would make this change only for newer cars or provide a selection in iDrive (and even this seems unlikely without a substantial change in the exhaust system). Moreover, if BMW had deliberately turned ASD off, the ECU would still be responding to the dealer's diagnostic scan.

So this leaves two possibilities: either a hardware failure or a software bug. A hardware failure seems less likely, especially given that both Stryder and Nachbar are experiencing the same issue after an update. I personally would not rule out a software bug, since I believe I saw one before when trying to get Euro LED to work on OneRib's car.

Knowing exactly what the fault codes in ASD and REM are might help, although I do not think the latter plays any role in the operation of ASD.

[Stryder]

Originally Posted by dmnc02

OK, here is my $0.02.

• VO coding will reset all the coding parameters in the ECU to the default values for the specific vehicle order, as detailed in the FA. However, this will occur automatically at the end of a software update by the dealer: so if ASD was not working after the update, VO coding the ECU will not make a difference.
• According to the CAFD, Werte=06 is the correct FDL value for “Construction Stage” in cars with a build date from July 2015 onward: the change in this value likely reflects the hardware change in the ASD unit on 2016 models.
• I personally believe there is zero chance BMW would deliberately turn ASD off retroactively through a software update. At most, they would make this change only for newer cars or provide a selection in iDrive (and even this seems unlikely without a substantial change in the exhaust system). Moreover, if BMW had deliberately turned ASD off, the ECU would still be responding to the dealer's diagnostic scan.

So this leaves two possibilities: either a hardware failure or a software bug. A hardware failure seems less likely, especially given that both Stryder and Nachbar are experiencing the same issue after an update. I personally would not rule out a software bug, since I believe I saw one before when trying to get Euro LED to work on OneRib's car.

Knowing exactly what the fault codes in ASD and REM are might help, although I do not think the latter plays any role in the operation of ASD.

That makes a lot of sense. With that being true, however, I don't think there is anything that can be done other than to wait for BMW eng to release another update, correct?

[aboulfad]

Originally Posted by Stryder

That makes a lot of sense. With that being true, however, I don't think there is anything that can be done other than to wait for BMW eng to release another update, correct?

Hmmm, thinking out loud here, if and if the software "bug" introduced is in the ASD ECU, would it be useful/possible to downgrade the firmware of the ASD ECU?

I know some people updated the firmware for other specific ECU (read Kombi to gain the new HUD), so could the reverse be possible?

It's really funny/ironic, that out of all the features the car has, that ASD has stopped working post this update...

[dmnc02]

Originally Posted by Stryder

That makes a lot of sense. With that being true, however, I don't think there is anything that can be done other than to wait for BMW eng to release another update, correct?

The CAFD you mentioned (cafd_00000f9b-001_020_003) was in PSdZData 57.0. PSdZData 57.1 is now out, so the update might already be available. If that is the case, BMW will instruct your dealer accordingly: let's see what they say.

In any case, it would be interesting to know what faults you are seeing in Rheingold: it is a tool well worth having on hand, since, as aboulfad says, "It's fun and we learn things along the way".

[Stryder]

Hmmmm. I cleared the fault codes, but they came back. Weird.

Here they are:

80489D: lamp implausible

8053A5: ASD coding not equalising

I've manually checked rear turn signals, brake lights, parking lights and backup lights. All are functioning normally.

Ideas?

[Stryder]

Complaints about rear lamps not being "plausible" seems like it could be caused by a 2016 somehow being programmed to be on 2015 pre-LCI software?

Make sense logically, doesn't it?

[Nachbar]

Originally Posted by Stryder

Hmmmm. I cleared the fault codes, but they came back. Weird.

Here they are:



I've manually checked rear turn signals, brake lights, parking lights and backup lights. All are functioning normally.

Ideas?

Is that Rheingold? Where did you get it?

[Stryder]

.

[aboulfad]

Originally Posted by Stryder

Hmmmm. I cleared the fault codes, but they came back. Weird.
...

I've manually checked rear turn signals, brake lights, parking lights and backup lights. All are functioning normally.

Ideas?

It seems there is a fault with the ASD ECU, assuming everything is programmed correctly. You can follow the calculate plan, but it will propose to re program the ASD... (Not coding)
Unsure about the other alarm, but the test plan will describe in most cases what to do next, and some of the steps may require tools/measuring devices we don't have access to. That's possibly as far as you can go!

[aboulfad]

Originally Posted by Stryder

Complaints about rear lamps not being "plausible" seems like it could be caused by a 2016 somehow being programmed to be on 2015 pre-LCI software?

Make sense logically, doesn't it?

You can further double click on each fault in the above screen to gain more information about the fault. But even then, some faults remain very mysterious.to figure out.

[dmnc02]

Originally Posted by Stryder

Hmmmm. I cleared the fault codes, but they came back. Weird.

Here they are:



I've manually checked rear turn signals, brake lights, parking lights and backup lights. All are functioning normally.

Ideas?

That fault in ASD shows why ASD is no longer working, as it is the same one that people get when they code off ASD by changing the "Model Range" to an incorrect value for the car. Since aboulfad already checked your CAFD against his and the only difference was in "Construction Stage", this does look like a software bug somewhere.

Did the "lamp mapping" fault come back too after you cleared it?

Originally Posted by Stryder

This must be the production year, right?

Yes, but it shows the calendar year, not the model year.

[Nachbar]

I VO Coded the ASD, but I think theres something wrong. At the place where "Harman Kardon" should be selected, there was "unknown". Changed that back to HK but no luck. Could someone post all correct values from a working 2016 M3 in here please? Printscreens or whatever.. Thanks!

[Stryder]

Originally Posted by dmnc02

Did the "lamp mapping" fault come back too after you cleared it?

Yes. Both codes came back when I cleared them.

[Stryder]

Originally Posted by aboulfad

It seems there is a fault with the ASD ECU, assuming everything is programmed correctly. You can follow the calculate plan, but it will propose to re program the ASD... (Not coding)
Unsure about the other alarm, but the test plan will describe in most cases what to do next, and some of the steps may require tools/measuring devices we don't have access to. That's possibly as far as you can go!

That would be the next step. Shawn has kindly given me some directions on flashing an individual ECU.

Originally Posted by aboulfad

You can further double click on each fault in the above screen to gain more information about the fault. But even then, some faults remain very mysterious.to figure out.

Will definitely check.

[dmnc02]

Originally Posted by Stryder

Yes. Both codes came back when I cleared them.

Have you modified your FA/VO in any way (for VO coding)?

[Stryder]

Originally Posted by dmnc02

Have you modified your FA/VO in any way (for VO coding)?

I coded the ASD module again and left all parameters default as a "reset to default" step. No difference whatsoever. Same behavior, or lack thereof, and same codes.

The lamp error has been there since I got back from the dealer yesterday morning. No idea what's going on there.

[Stryder]

Originally Posted by Nachbar

I VO Coded the ASD, but I think theres something wrong. At the place where "Harman Kardon" should be selected, there was "unknown". Changed that back to HK but no luck. Could someone post all correct values from a working 2016 M3 in here please? Printscreens or whatever.. Thanks!

Which subsection is that? I remember only seeing "System" or something like that, and none of the options mentioned Harman Kardon. Mine was labeled "Top Hifi/Branded HiFi" I think.

[aboulfad]

check the attached pic for the audio level values, in my older and your current ASD cafd, it is both set to werte 03, Top HiFi.

[aboulfad]

@stryder, check the fault description, here's the one corresponding to me changing model range to F01 in order to disable ASD. I found the comment below funny, ensure the latest version
You can also use the "call up ECU functions" on ASD, there's few operations you can try: reset ECU, mute, ...

Also, when you calculate the test plan, there will be options to test every individual speaker, and through ASD ?!? Have fun !

Fault description The fault is set when an invalid vehicle type is encoded.
The coding data is effectively invalid, although the coding procedure was successful.
...
Condition for fault memory entry The fault is entered if the check does not correspond with the predefined value.

Action in service Re-encode ASD control unit.

Ensure that the latest version of the program including the current software update is used for programming. Check whether message faults are stored in the vehicle. If necessary, run the system analysis test module.

Repeat programming/encoding.
...

[Stryder]

Originally Posted by aboulfad

@stryder, check the fault description, here's the one corresponding to me changing model range to F01 in order to disable ASD. I found the comment below funny, ensure the latest version
You can also use the "call up ECU functions" on ASD, there's few operations you can try: reset ECU, mute, ...

Also, when you calculate the test plan, there will be options to test every individual speaker, and through ASD ?!? Have fun !

I have the *exact* same error, except my model range is F080.

Where are you finding things like "call up ECU functions"? I can't see anything like that.

P.S. on a positive note, the REM fault code went away for good! It was something about the bulb encoding not being correct. Whatever the case is, it's gone now! ASD is the only thing left acting up.

[aboulfad]

It's at the bottom of the main screen where the ECU tree is displayed in Rheingold. To be exact: Vehicle Info->Control Unit Tree, select ECU, then click "Call up ECU functions". And here's a pic, follow the arrow

[dmnc02]

Stryder do you have an F80 or an F82?

Based on the picture in post #20, your "Model Range" is set to F082 = 16, but your signature says you have an F80, in which case the correct value for "Model Range" should be F080 = 15.