Active Sound gone after latest software update?

[Stryder]

Originally Posted by aboulfad

hi, check the diff between your file and mine, not sure how critical "construction stage" is, but yours is set to werte "06", unknown ? for fun, try setting that to my value werte 03 ?

and you could alway VO code the ASD ECU to bring back to stock if there was some coding/firmware update corruption, i think but unsure !

Hmmm, is it actually possible to code the entire module back to original factory spec? I was not aware of such an option. Would you have a link to a tutorial?

[Stryder]

Originally Posted by aboulfad

Just for the record, I coded mine off since I got my car just trying to help here. Stryder should be equipped by now with diagnostic software and maybe he may discover something or not...

On a lighter note, what are the chances that the engineers got sick and tired of hearing about people complaining about ASD and decided to just fuck it and disable it all with the software update?

[Bluex]

Originally Posted by Stryder

Hmmm, is it actually possible to code the entire module back to original factory spec? I was not aware of such an option. Would you have a link to a tutorial?

Wouldn't that just be VO coding the entire module? (especially if you made backups of all your original CAFD files, right?)

[Stryder]

Originally Posted by Bluex

Wouldn't that just be VO coding the entire module?

open esys -> connect -> read VO -> activate FA -> read ECU -> select ASD -> right click -> code ?

won't that just basically recode whatever it was the car was currently already running?

[aboulfad]

Originally Posted by Stryder

Hmmm, is it actually possible to code the entire module back to original factory spec? I was not aware of such an option. Would you have a link to a tutorial?

Very easy, Shawn's instructions:

To VO Code:
Connect => Read FA => Activate FA => Read VCM => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE

But don't VO code anything else without knowing the consequences... I've read some bad stories where people VO coded I think the DME or some other important ECU... I have VO coded the ASD ECU only to date.

[Stryder]

I also did a quick run of the diagnostic software before heading to the office. Both ASD and REM had fault codes.

What does REM consist of? Rear Electronics Module right? Would it be the amp and the ASD module? Because the ASD *does* depend on the amp to function.


--------
nevermind answered myself. the REM controls a bunch of things including rear camera.

[aboulfad]

Originally Posted by Stryder

open esys -> connect -> read VO -> activate FA -> read ECU -> select ASD -> right click -> code ?

won't that just basically recode whatever it was the car was currently already running?

That's the procedure, but not entirely sure if this is the procedure to VO back to original... From a post that Shawn made:
" You can change your VO, VO Code, and change the VO back to original and VO Code it again."

You could maybe ask him nicely by posting in the coding mega thread? Or ask the procedure to reflash an ECU like ASD if it's possible, then that step would definitely confirm wether there was a firmware corruption during the update or that your ASD is really fried or like you said lightly, BMW engineers got fed up with complaints and disabled it

[Bluex]

Originally Posted by Stryder

open esys -> connect -> read VO -> activate FA -> read ECU -> select ASD -> right click -> code ?

won't that just basically recode whatever it was the car was currently already running?

Isn't that just fdl coding? When you do Read FA(VO)->Activate FA(VO)->Read ECU>Right-Click ASD -> Code I thought that is VO coding and resetting the module back to factory defaults.

dmnc02 would have the answer for this, but I know whenever the LED guys got stuck and needed to reset a module, that's how we did it. Just VO (not fdl) code and it goes back to factory default.

[Stryder]

Originally Posted by aboulfad

Very easy, Shawn's instructions:

To VO Code:
Connect => Read FA => Activate FA => Read VCM => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE

But don't VO code anything else without knowing the consequences... I've read some bad stories where people VO coded I think the DME or some other important ECU... I have VO coded the ASD ECU only to date.

Alrighty. Worth a try, given that the ASD is not working anyways. Experimentation!

[aboulfad]

Originally Posted by Stryder

Alrighty. Worth a try, given that the ASD is not working anyways. Experimentation!

What was the ASD fault? Similar to what I posted above? And where your ASD settings stock or altered by you or some gremlins?

[Stryder]

Originally Posted by Bluex

Isn't that just fdl coding? When you do Read FA(VO)->Activate FA(VO)->Read ECU>Right-Click ASD -> Code I thought that is VO coding and resetting the module back to factory defaults.

dmnc02 would have the answer for this, but I know whenever the LED guys got stuck and needed to reset a module, that's how we did it. Just VO (not fdl) code and it goes back to factory default.

Our only difference is in read SVT vs. read ECU. I thought the two operations are basically the same?

We should start a university to train F80post members to become full-on BMW master techs.

[Bluex]

Originally Posted by aboulfad

But don't VO code anything else without knowing the consequences... I've read some bad stories where people VO coded I think the DME or some other important ECU... I have VO coded the ASD ECU only to date.

That's the DME module and you can NEVER code this while the engine is running. It will just blow it up. It's the only one you have to worry about.

[Bluex]

Originally Posted by Stryder

Our only difference is in read SVT vs. read ECU. I thought the two operations are basically the same?

We should start a university to train F80post members to become full-on BMW master techs.

Yes, both are the same and that's why I edited my post to say ECU as most people know it as this way....but SVT works as well.

lol...Bimmerpost U

[aboulfad]

Originally Posted by Bluex

...

dmnc02 would have the answer for this, but I know whenever the LED guys got stuck and needed to reset a module, that's how we did it. Just VO (not fdl) code and it goes back to factory default.

I think you are right but wasn't sure anymore. I also remembered that I may have VO coded the DSC ECU to quickly undo the EuroMDM settings. And our friend dmnc02 seems to be incognito

[Stryder]

Originally Posted by aboulfad

What was the ASD fault? Similar to what I posted above? And where your ASD settings stock or altered by you or some gremlins?

There were two codes (do fault codes from multiple modules get displayed at once? Because that would explain why there was 2, one for ASD, one for REM)

One of the codes was exactly the one you posted before, I'm pretty sure that's just from me messing around with the model range.

The other code I should have jotted down, but I didn't. I'll post it later.

[Stryder]

Originally Posted by Bluex

That's the DME module and you can NEVER code this while the engine is running. It will just blow it up. It's the only one you have to worry about.

Got it.

Note to self: don't blow up the engine.

[Bluex]

Originally Posted by Stryder

Got it.

Note to self: don't blow up the engine.

Lol...technically speaking the engine itself won't blow up (don't want anyone to take me literally)....just will corrupt your CAFD. Which can be corrected if you have good backups of all your CAFD's from when you first started coding.

Shawn has saved more than a few people who have unfortunately made this mistake

[Stryder]

Originally Posted by Nachbar

I tried werte 03 and 06 today. No difference. Mine was 03 - and I got the same problem as you guys, since they updated the connected drive module.

I still remember seeing your LCI when you first got it!

It's good to know that I'm not the only one facing this issue, *especially* given that you are in EU.

[aboulfad]

Originally Posted by Stryder

...

It's good to know that I'm not the only one facing this issue, *especially* given that you are in EU.

issue for some, blessing for others

[Stryder]

Originally Posted by aboulfad

issue for some, blessing for others

Hahaha I know right? Some will get the update and think "Wow, my car feels so much better!", and then others like me being like "Hey WTF! Gimme back!"

Can't please everyone.

[Nachbar]

Originally Posted by aboulfad

issue for some, blessing for others

I'm going to sleep and hope you guys fix it in the meantime.

[Stryder]

Next steps:

1. Save fault codes. Clear them.
2. Drive around. Cycle car. Reconnect and see if there's any new fault codes being thrown.
3. If no, VO code ASD.
4. Drive around and check for codes again.
5. If still no faults, and still no functioning ASD, then *maybe* it's intentional given that there's no TSB about this? It does mean that I myself won't be able to do much of anything beyond that point, and it's better to just wait for BMW to figure their software out.