I've got a new F11 (built on 10. Octobre 2012), what data do I need to code this thing? Could someone send me a link please?
As I see, the turn signals in HUD are not possible with the new navi?

Thanks
Tee

Quote:

Originally Posted by kitster

Hi,

Also interested in coding my car, I'm about to take delivery of a F31 (Nov Build). If someone could send me a link?

On another note, if I make a change will my dealer be able to detect this?

Thanks.

Maybe look here:

Quote:

Huge thanks to Telefax for sharing this and providing the files.
I've never created a torrent before, this is my first one, so hopefully it works.
The torrent file can be downloaded from here: http://www.sendspace.com/file/ngwhjf

I'm leaving my computer on with it seeding so hopefully we can get the ball rolling for everyone. Let me know how it works. Thanks!

Generally, normal coding will not be detected. If your car goes in for service, and needs programming, the Dealer will just hook up to the car, and program it and wipe out your coding. If you do some advanced things like alter your VO and write it to the car, then the Dealer's ISTA/P will likely recognize it, and depending on what exactly was done, it may or may not program the car.

Your coding info is GREAT! Please send me a working torrent link. I have a F10 M5 and F30 335i xDrive that I would love to code. Still need to acquire a cable and wish there is some way to capture all of these tips and a how to get started. Any tips would be most welcomed.

Your coding info is GREAT! Please send me a working torrent link. I have a F10 M5 and F30 335i xDrive that I would love to code. Still need to acquire a cable and wish there is some way to capture all of these tips and a how to get started. Any tips would be most welcomed.

This worked perfectly, I didn't have any real errors. This forum has been amazing help with figuring out coding and getting help - shawn especially has been really helpful.

One question - has anyone coded the auto high beam assistant yet? I do have the driver assistance package (rear camera, park distance control, blind spot detection, side&top camera) but don't have SLI, high beam assistant, lane departure warning. Seems like SLI needs an FSC code, but was wondering if high beam assistant was possible. Looking at the F10 thread it seems like it just need coding the following changes below:

However, I couldn't find KAFAS module in my module list though, and I'm wondering if I'm just missing the appropriate hardware. I also saw some mentions about VO coding/changing FA for SLI but not sure I entirely followed all of it.

This worked perfectly, I didn't have any real errors. This forum has been amazing help with figuring out coding and getting help - shawn especially has been really helpful.

One question - has anyone coded the auto high beam assistant yet? I do have the driver assistance package (rear camera, park distance control, blind spot detection, side&top camera) but don't have SLI, high beam assistant, lane departure warning. Seems like SLI needs an FSC code, but was wondering if high beam assistant was possible. Looking at the F10 thread it seems like it just need coding the following changes below:

However, I couldn't find KAFAS module in my module list though, and I'm wondering if I'm just missing the appropriate hardware. I also saw some mentions about VO coding/changing FA for SLI but not sure I entirely followed all of it.

If anyone has gotten this working, any advice/help would be great.

Did you see this Post:

Quote:

I'm not 100% sure it's the same camera. I saw a BMW 7 Series LCI at the SF Auto Show the other day. It did not have a driver assistance package (LDW, etc.), just AHB. It was a separate camera mounted at the base of the mirror - not the "KAFAS" camera referenced above.

This is the standalone HBA camera:

This is the KAFAS camera [representation only], that can do HBA, collision avoidance, LDW, SLI, etc. It's wedge-shaped and mounted above the mirror:

Crazy enough, I've also seen cars with both with some early models.

It seems there may be a newer AHB Only camera, that does not use KAFAS camera.

Has anyone noticed that after they make a change as outlined in svache's original cheat sheet that when the re-read the data into E-Sys those changes are marked as "INVALID" or "UNKNOWN".

IOW, if you go through the entire coding process and then reload that item, even though it accepted your input and uploaded it to the ECU, the hardware deems it invalid.

I had this happen with SV_Activate_Speed_Limit and SV_Deactivate_Speed_Limit. Both were accepted -- and they actually did what I expected.

But I hated having the side view cameras on at any speed (it's comic -- you should try it at 95mph). When I went to set them back to their defaults, I noticed they were invalid.

Curious about this, myself and I do not see a response. Are any changes we make using e-sys flagged with an "unknown" or "invalid" even if replaced with our original (backed up) CAFD meaning we will always leave a trail even if we put eveything back using the backup CAFD files (e.g. incase of warranty issue)?

Perhaps he simply changed the value back and did not restore the original CAFD? In othe words, I assume if we restore using the orignal CAFD files, there will be NO trail?

Curious about this, myself and I do not see a response. Are any changes we make using e-sys flagged with an "unknown" or "invalid" even if replaced with our original (backed up) CAFD meaning we will always leave a trail even if we put eveything back using the backup CAFD files (e.g. incase of warranty issue)?

Perhaps he simply changed the value back and did not restore the original CAFD? In othe words, I assume if we restore using the orignal CAFD files, there will be NO trail?

This is not normal. Can someone post a picture of an "INVALID" or "UNKNOWN" entry?

Regardless, and in theory, if you restore all the original CAFD from backup is there likely still some sort of trail (I assume there always is with software, but hoping nothing this obvious or noticeable)?

Regardless, and in theory, if you restore all the original CAFD from backup is there likely still some sort of trail (I assume there always is with software, but hoping nothing this obvious or noticeable)?

Yes, I think in that instance, incompatible Werte Values were used.

There may be some way to tell, but again with normal FDL coding nothing is obvious, especially after the coding is removed and the module is returned to the original state. Now if you alter your VO Options, and / or change your Production Date and write it to the car, and do not reverse that, that will easily be discovered. If you flash the firmware on an ECU, which can't be reversed, that may or may not be noticed.