F10 Navi on head-up display disappeared . . . help!

I've been playing with the various features and codes for the HUD on my 2013 M5. I made the coding changes per the cheat sheet v.3 to enable the entertainment list, telephone book, contacts list, voice commands, navi and turn signals ("blinkers") on the HUD. Coded both the HU_NBT and KOMBI modules. Worked just fine, until . . .

I played around with a few other codes (I didn't keep a log, shame on me) and now the blinkers and the navigation info no longer appear on the HUD. I confirmed that the relevant HU_NBT and KOMBI items are coded to activ, but still no luck. Note that the "Navigation" check box is checked in the Head-Up Display settings menu. The entertainment list, phone book and contacts all still appear on the HUD.

BTW -- discovered a self-test feature for the HUD -- if you hold the head-up display button to the left of the steering wheel for >10 seconds it will cycle through various calibration screens with each subsequent press of the HUD button.

Anyway, I don't care about the blinkers but I would like the Navi back. Any suggestions?

Last ditch resort, but I'd default everything back and redo the changes you did to begin with. I just got finished coding as well.. Sounds like you tinkered with a lot more then I did though.

Last ditch resort, but I'd default everything back and redo the changes you did to begin with.

Thanks -- not a bad suggestion. Any guidance on how to do this safely? Using the "code default values" box in e-Sys, or loading a saved version of my FDL files?

Nice ride, BTW! Mine is Azurite Black Metallic.

Originally Posted by mhercz

Thanks -- not a bad suggestion. Any guidance on how to do this safely? Using the "code default values" box in e-Sys, or loading a saved version of my FDL files?

Nice ride, BTW! Mine is Azurite Black Metallic.

No! Don't ever hit the Code Defaults Button or you may be watching you M5 Flatbedded to the Dealer.

Connect => Read FA => Activate FA => Read VCM => Right-Click on KOMBI (the ECU itself not the underlying CAFD) => Select CODE.

This is a VO Code of the ECU, which will reset it, and it is not the same as FDL Code or Code Defaults.

Repeat the Process for HU_NBT module.

This should return your HUD and iDrive to your as delivered condition.

Shawn to the rescue (again)!!! Re-coding per your instructions did the trick.

Everything is working fine now, but I did get an error code in eSys when coding the KOMBI module. Should I investigate further or leave it alone? Again, everything appears to be working just fine.

Originally Posted by mhercz

Shawn to the rescue (again)!!! Re-coding per your instructions did the trick.

Everything is working fine now, but I did get an error code in eSys when coding the KOMBI module. Should I investigate further or leave it alone? Again, everything appears to be working just fine.

Umm...what is the error?

Not sure what the error was -- is there a log where I can look it up? I can also try to re-code the KOMBI and take a screen shot of what I get.

Note that I'm using the 48.1 pdz files (I upgraded per your instructions).

Originally Posted by mhercz

Not sure what the error was -- is there a log where I can look it up? I can also try to re-code the KOMBI and take a screen shot of what I get.

Note that I'm using the 48.1 pdz files (I upgraded per your instructions).

If you have no current errors, your are good.

If you have a current error, post a picture of it.

Originally Posted by shawnsheridan

If you have no current errors, your are good.

If you have a current error, post a picture of it.

Tried coding KOMBI again and attached are the error messages I received. Something about a "NoSuchMethodException" -- note that I don't get this error when I code the other modules, like HU_NBT. And by "code" I mean the process you described earlier in this thread, not editing and coding the FDL.

So what am I doing wrong?

Originally Posted by mhercz

Tried coding KOMBI again and attached are the error messages I received. Something about a "NoSuchMethodException" -- note that I don't get this error when I code the other modules, like HU_NBT. And by "code" I mean the process you described earlier in this thread, not editing and coding the FDL.

So what am I doing wrong?

Are you using 47.5 with 48.1 Adders, or the full 48.1, and if it's the full 48.1, did you delete your existent PSdZData folder and replace it with the new one, or did you just copy it on top of your old one?

Originally Posted by shawnsheridan

Are you using 47.5 with 48.1 Adders, or the full 48.1, and if it's the full 48.1, did you delete your existent PSdZData folder and replace it with the new one, or did you just copy it on top of your old one?

I deleted 47.5 and replaced with the full 48.1. Pretty sure I replaced with the PSdZData with the new one. How can I confirm?

Originally Posted by mhercz

I deleted 47.5 and replaced with the full 48.1. Pretty sure I replaced with the PSdZData with the new one. How can I confirm?

You can't.

Do you get this error only when you FDL Code KOMBI, or when you VO Code KOMBI too?

Do you get this error only when you FDL Code KOMBI, or when you VO Code KOMBI too?

The error occurs only when I VO Code KOMBI, not when I FDL Code KOMBI. I've successfully FDL Coded KOMBI several times.

Originally Posted by mhercz

The error occurs only when I VO Code KOMBI, not when I FDL Code KOMBI. I've successfully FDL Coded KOMBI several times.

Hmmm that makes no sense, unless your FA (VO) was modified.

Please try again this morning, Connect, Read FA, Read VCM, and VO Code KOMBI.

Shawn -- just tried again -- same error:

I can read and FDL Code, but not VO Code.

One more thing -- there's a string after my VIN on the Open Connection dialog that reads "_DIAGADR10" -- what does this mean?

Originally Posted by mhercz

One more thing -- there's a string after my VIN on the Open Connection dialog that reads "_DIAGADR10" -- what does this mean?

You mean on the bottom Connect via VIN? I think that is normal.

Originally Posted by mhercz

Shawn -- just tried again -- same error: Attachment 355225

I can read and FDL Code, but not VO Code.

Are these actual camera shots? No offense, but they are terrible.

You need a Screen Capture Program. See this:

http://www.picpick.org/en/



Ok, I have never seen a [C206] error, ever, and it bothers me. If it was my setup, I would blow it up, reinstall E-Sys and the 48.1 PSdZData from scratch. Something just isn't right.