BMW X5 and X6 Forum 2014-Current
BMW Garage BMW Meets Register Search Today's Posts Mark Forums Read


Post Reply
 
Thread Tools Search this Thread
      01-08-2016, 12:24 PM   #111
TonySCV
Captain
509
Rep
709
Posts

Drives: '18 M2; '21 X6 M50i
Join Date: Feb 2013
Location: Las Vegas, NV

iTrader: (0)

Quote:
Originally Posted by dmnc02 View Post
The only difference between this version and the one I PM'd you earlier this week is that the amber side markers are back on in this version.
Meh.. I'd rather have them off
Appreciate 0
      01-09-2016, 08:59 AM   #112
MrTookies
Lieutenant
MrTookies's Avatar
United_States
454
Rep
570
Posts

Drives: 2011 E90 328i, 2015 F15 35D
Join Date: Jan 2013
Location: Drivers Seat

iTrader: (0)

Quote:
Originally Posted by TonySCV
Quote:
Originally Posted by dmnc02 View Post
The only difference between this version and the one I PM'd you earlier this week is that the amber side markers are back on in this version.
Meh.. I'd rather have them off
Haha that's what I said
Appreciate 0
      01-09-2016, 09:21 AM   #113
dmnc02
Major
dmnc02's Avatar
United_States
920
Rep
1,481
Posts

Drives: 2015 M4
Join Date: Feb 2015
Location: PA

iTrader: (0)

Quote:
Originally Posted by TonySCV View Post
Meh.. I'd rather have them off
Quote:
Originally Posted by PlayTookies View Post
Haha that's what I said
I believe thee is an easy way to turn the side markers off starting from the coding in the PDF in post #107 by changing a single parameter (this is different from the way they are turned off in the earlier version tried by PlayTookies and TonySCV, which involves a lot of changes, although the final result is the same).

I will post once confirmed, so that people can easily switch them on or off as they like.
__________________
2015 Mineral Grey ///M4 6MT
Appreciate 0
      01-12-2016, 08:33 PM   #114
dmnc02
Major
dmnc02's Avatar
United_States
920
Rep
1,481
Posts

Drives: 2015 M4
Join Date: Feb 2015
Location: PA

iTrader: (0)

So here is the quick way to turn the amber side markers on or off on cars with the FLE ECUs (confirmed courtesy of PlayTookies).
  • To turn the side markers off, change LM_ID_LT04 and LM04_Name to F015Wert.
  • To turn the side markers back on, change LM_ID_LT04 and LM04_Name back to F015Wert_SA552_SAE.
The above should work even if anti-dazzle has not been coded.
__________________
2015 Mineral Grey ///M4 6MT
Appreciate 0
      01-16-2016, 09:54 PM   #115
9jabimmer
Private
9jabimmer's Avatar
12
Rep
62
Posts

Drives: '14 535i M Sport Carbon Black
Join Date: Jun 2014
Location: Northern Virginia

iTrader: (1)

Quote:
Originally Posted by dmnc02 View Post
So, as a temporary solution, here is a quick way of coding Step 2 for NGHB on F15s with production date after July 1, 2015.
  1. Confirm that the CAFD that appears in your SVT tree under your FLE ECUs is CAFD_000024C3_008_007_002 (this should be the case for vehicles with production dates through December 2015).
  2. If the above is the case, download the attached CAFD (which is already coded) and rename it CAFD_000024C3_008_007_002.ncd.
  3. Connect to the car, read and activate FA and read SVT as usual.
  4. Right-click on the first FLE ECU, select New > FDL and then select the downloaded CAFD.
  5. Click "Code FDL".
  6. Repeat Steps 4 and 5 for the other FLE ECU.
The above procedure is quick and error-proof, but is only temporary, as at some point newer cars will come with a newer CAFD.

Guys... need some help here... When I get to step 4, and I click "New", the FDL option is grayed out for me. Any ideas why.

The one item that I am doing is that I click "Read ECU" as opposed to "Read SVT". (Read SVT throws an error for me).

Thoughts?
Appreciate 0
      01-17-2016, 09:08 AM   #116
dmnc02
Major
dmnc02's Avatar
United_States
920
Rep
1,481
Posts

Drives: 2015 M4
Join Date: Feb 2015
Location: PA

iTrader: (0)

Quote:
Originally Posted by 9jabimmer View Post
Guys... need some help here... When I get to step 4, and I click "New", the FDL option is grayed out for me. Any ideas why.

The one item that I am doing is that I click "Read ECU" as opposed to "Read SVT". (Read SVT throws an error for me).

Thoughts?
Have you tried FDL coding something, as a check?
__________________
2015 Mineral Grey ///M4 6MT
Appreciate 0
      01-17-2016, 09:23 AM   #117
9jabimmer
Private
9jabimmer's Avatar
12
Rep
62
Posts

Drives: '14 535i M Sport Carbon Black
Join Date: Jun 2014
Location: Northern Virginia

iTrader: (1)

Yes. I have been able to both VO code, and FDL code. I must be missing something else.
Appreciate 0
      01-17-2016, 10:40 AM   #118
dmnc02
Major
dmnc02's Avatar
United_States
920
Rep
1,481
Posts

Drives: 2015 M4
Join Date: Feb 2015
Location: PA

iTrader: (0)

Quote:
Originally Posted by 9jabimmer View Post
Yes. I have been able to both VO code, and FDL code. I must be missing something else.
OK, I looked again at what I wrote and I realize that my instructions were a bit sloppy.

So, let me try again:
  1. Confirm that the CAFD that appears in your SVT tree under your FLE ECUs is CAFD_000024C3_008_007_002 (this should be the case for vehicles with production dates through December 2015).
  2. If the above is the case, download the attached CAFD (which is already coded) and rename it CAFD_000024C3_008_007_002.ncd.
  3. Connect to the car, read and activate FA and read SVT as usual.
  4. Right-click on the CAFD underlying the first FLE ECU, select New > FDL and then select the downloaded CAFD.
  5. Expand the folder that appears under the FLE ECU, select the CAFD inside the folder and click "Code FDL".
  6. Repeat Steps 4 and 5 for the other FLE ECU.
Let me know if this solves your issue.

I have also edited the original post to reflect these instructions.
__________________
2015 Mineral Grey ///M4 6MT

Last edited by dmnc02; 01-31-2016 at 08:02 AM.. Reason: Last paragraph added
Appreciate 0
      02-23-2016, 11:33 AM   #119
mephiska
Major
mephiska's Avatar
United_States
515
Rep
1,001
Posts

Drives: 2016 M3
Join Date: Apr 2010
Location: East Bay

iTrader: (0)

Garage List
Quote:
Originally Posted by dmnc02 View Post
PlayTookies had some time last night to confirm the last detail (he has really put a lot of time and effort into this), so below is the revised version of the PDF with the anti-dazzle coding.

A few remarks:
  • There are no changes in the coding for vehicles with the LHM ECUs (production date before July 1, 2015): the only changes are for vehicles with the newer FLE ECUs.
  • There are a total of 101 () parameters that need to be FDL coded in each FLE: nevertheless, FDL coding is fairly quick, since each of the parameters listed in Appendix 2 (with only one exception) need to be changed to the same "F015Wert" value. I will also mention a shortcut for coding this in the next post.
  • If you want to FDL code this, make sure you are using E-Sys Launcher v2.5 or newer, as otherwise the "F015Wert" value will not appear for some of the parameters listed in Appendix 2.
Thanks again for your help getting NGHB working in my M3.

I told my boss once I figured out how to do it on my car that I'd code his X5 M to enable it for him. His is a pre-July 2015 car.

I've read through this whole thread, and it looks like the instructions in your PDF are basically identical to the F80 that I followed. The instructions say to VO code "BDC_BODY, either FLA or KAFAS (whichever is present), both TMS and both LHM."

Earlier in this thread it sounded like you needed to VO code ALL ECUs except the DME for this to work. I assume that's not the case anymore and you guys have found that you only need to VO code the ECUs that are outlined in your PDF?
__________________
Appreciate 0
      02-23-2016, 11:45 AM   #120
dmnc02
Major
dmnc02's Avatar
United_States
920
Rep
1,481
Posts

Drives: 2015 M4
Join Date: Feb 2015
Location: PA

iTrader: (0)

Quote:
Originally Posted by mephiska View Post
Thanks again for your help getting NGHB working in my M3.

I told my boss once I figured out how to do it on my car that I'd code his X5 M to enable it for him. His is a pre-July 2015 car.

I've read through this whole thread, and it looks like the instructions in your PDF are basically identical to the F80 that I followed. The instructions say to VO code "BDC_BODY, either FLA or KAFAS (whichever is present), both TMS and both LHM."

Earlier in this thread it sounded like you needed to VO code ALL ECUs except the DME for this to work. I assume that's not the case anymore and you guys have found that you only need to VO code the ECUs that are outlined in your PDF?
The basic coding procedure is the same across different platforms.

You will find the same statement regarding the need to VO code all ECUs except DME early in the F80 thread, but there is no actual need for it. This has been confirmed by comparing the coding of each ECU before and after VO coding: VO coding other ECUs results in no additional changes.
__________________
2015 Mineral Grey ///M4 6MT
Appreciate 2
      03-29-2016, 01:35 AM   #121
Almaretto
Major General
Almaretto's Avatar
2373
Rep
8,364
Posts

Drives: Test Vehicles
Join Date: Dec 2015
Location: Mountain View, CA

iTrader: (0)

So I finally got around to coding my F15, and I had a couple questions about the NGHB values.

2016 F15 xdrive40e with Zeitkriterium 0815 & F025-15-11-503.

After removing 5AP and 8S4 and VO Coding, I used TM NCD / CAFD Tool to compare my FLE 43 (Left = CAFD_000024C3_008_010_000.ncd) to posted FLE (Right = CAFD_000024C3_008_007_002.ncd).

Besides the required posted changes (NGHB F15 v2 - Jan 8, 2016), I had some additional differences and wondered if those were required as well.

There is a set of values that are completely different:

Code:
LWR_STROM_HALT_TT	Left: F020Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F030Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F010Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F045Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert = 50

LWR_VORBEST_ZEIT	Left: F020Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F030Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F010Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F045Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00

AHL_STROM_HALT_TT	Left: F020Wert_SA552_ECE = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F020Wert_SA552_WL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_ECE = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_WL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00
Then, there is a set of values, where drop-down is different, but same werte:

Code:
LWR_V_MIN	        Left: F020Wert = 64 00	Right: F010Wert = 64 00
LWR_V_MIN	 	Left: F030Wert = 64 00	Right: F010Wert = 64 00
LWR_ACC			Left: F020Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
LWR_ACC			Left: F030Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
CORNL_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
ECO1_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
SIDEMRKLGT_Idx		Left: F015Wert_SA552_SAE = 01 01 01 0C 01 01 01 01 01 01	Right: UNKNOWN = 01 01 01 0F 01 01 01 01 01 01


LmmIdx00_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx01_Intensity	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOn		Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOff	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_Priority	Left: F030Wert_SA552_US = 0F	Right: F020Wert = 0F
LmmIdx02_Intensity	Left: F010Wert_SA552_US = 5D	Right: F015Wert = 5D
LmmIdx04_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx06_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx07_RampType	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx09_Priority	Left: F030Wert_SA552_US = 03	Right: F015Wert = 03
LmmIdx10_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Priority	Left: F030Wert_SA552_ECE_LA_RL = 02	Right: F030Wert_SA552_ECE_LA_LL = 02
LmmIdx12_Priority	Left: F030Wert_SA552_ECE_LA_RL = 03	Right: F030Wert_SA552_ECE_LA_LL = 03
LmmIdx13_Intensity	Left: F030Wert_SA552_US = 64	Right: F010Wert = 64
LmmIdx14_Priority	Left: F030Wert_SA552_ECE_LA_RL = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_Priority	Left: F030Wert_SA552_US = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_ErrorImpact	Left: F030Wert_SA552_US = 01	Right: F015Wert = 01
LmmIdx15_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64


LM06_CURRENT_BINNING_CLASS0	Left: F045Wert = 20 03	Right: F015Wert = 20 03
Also, just to confirm, FLE 43 and FLE 44 get the same changes (ie right vs left does not matter)?

Thanks
Appreciate 0
      03-31-2016, 02:34 AM   #122
alphaod
Mmmmm…
alphaod's Avatar
United_States
1148
Rep
2,426
Posts

Drives: F15
Join Date: Oct 2011
Location: New York

iTrader: (0)

Garage List
First off thanks to everyone who did the testing and stuff. I've been running these for thousands of miles in every kind of conditions it's all working spectacular.

I just have one question: How do I get rid of the 3 LED amber markers? I have the LHM ECU... Thanks!
Appreciate 0
      03-31-2016, 07:21 AM   #123
MrTookies
Lieutenant
MrTookies's Avatar
United_States
454
Rep
570
Posts

Drives: 2011 E90 328i, 2015 F15 35D
Join Date: Jan 2013
Location: Drivers Seat

iTrader: (0)

Quote:
Originally Posted by alphaod View Post
First off thanks to everyone who did the testing and stuff. I've been running these for thousands of miles in every kind of conditions it's all working spectacular.

I just have one question: How do I get rid of the 3 LED amber markers? I have the LHM ECU... Thanks!
Thank's! You can find that here in 138 & 139

https://docs.google.com/spreadsheets...9s4/edit#gid=0

Hope that helps :-)
Appreciate 0
      03-31-2016, 08:27 PM   #124
alphaod
Mmmmm…
alphaod's Avatar
United_States
1148
Rep
2,426
Posts

Drives: F15
Join Date: Oct 2011
Location: New York

iTrader: (0)

Garage List
Quote:
Originally Posted by PlayTookies View Post
Thank's! You can find that here in 138 & 139

https://docs.google.com/spreadsheets...9s4/edit#gid=0

Hope that helps :-)
Thanks, but I have a pre-July 2015 vehicle, so I don't have the FLE ECUs.

EDIT: I was able to get it working. Thanks again

Last edited by alphaod; 04-06-2016 at 06:04 AM..
Appreciate 0
      04-05-2016, 10:34 AM   #125
ssft
New Member
2
Rep
13
Posts

Drives: MY16 X5 50i
Join Date: Apr 2016
Location: Tacoma, WA

iTrader: (0)

Were you able to figure this one out? I've got the same situation on my MY16 post-June, with CAFD_000024C3_008_010_000.ncd.

Quote:
Originally Posted by Almaretto View Post
So I finally got around to coding my F15, and I had a couple questions about the NGHB values.

2016 F15 xdrive40e with Zeitkriterium 0815 & F025-15-11-503.

After removing 5AP and 8S4 and VO Coding, I used TM NCD / CAFD Tool to compare my FLE 43 (Left = CAFD_000024C3_008_010_000.ncd) to posted FLE (Right = CAFD_000024C3_008_007_002.ncd).

Besides the required posted changes (NGHB F15 v2 - Jan 8, 2016), I had some additional differences and wondered if those were required as well.

There is a set of values that are completely different:

Code:
LWR_STROM_HALT_TT	Left: F020Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F030Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F010Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F045Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert = 50

LWR_VORBEST_ZEIT	Left: F020Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F030Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F010Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F045Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00

AHL_STROM_HALT_TT	Left: F020Wert_SA552_ECE = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F020Wert_SA552_WL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_ECE = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_WL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00
Then, there is a set of values, where drop-down is different, but same werte:

Code:
LWR_V_MIN	        Left: F020Wert = 64 00	Right: F010Wert = 64 00
LWR_V_MIN	 	Left: F030Wert = 64 00	Right: F010Wert = 64 00
LWR_ACC			Left: F020Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
LWR_ACC			Left: F030Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
CORNL_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
ECO1_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
SIDEMRKLGT_Idx		Left: F015Wert_SA552_SAE = 01 01 01 0C 01 01 01 01 01 01	Right: UNKNOWN = 01 01 01 0F 01 01 01 01 01 01


LmmIdx00_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx01_Intensity	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOn		Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOff	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_Priority	Left: F030Wert_SA552_US = 0F	Right: F020Wert = 0F
LmmIdx02_Intensity	Left: F010Wert_SA552_US = 5D	Right: F015Wert = 5D
LmmIdx04_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx06_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx07_RampType	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx09_Priority	Left: F030Wert_SA552_US = 03	Right: F015Wert = 03
LmmIdx10_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Priority	Left: F030Wert_SA552_ECE_LA_RL = 02	Right: F030Wert_SA552_ECE_LA_LL = 02
LmmIdx12_Priority	Left: F030Wert_SA552_ECE_LA_RL = 03	Right: F030Wert_SA552_ECE_LA_LL = 03
LmmIdx13_Intensity	Left: F030Wert_SA552_US = 64	Right: F010Wert = 64
LmmIdx14_Priority	Left: F030Wert_SA552_ECE_LA_RL = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_Priority	Left: F030Wert_SA552_US = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_ErrorImpact	Left: F030Wert_SA552_US = 01	Right: F015Wert = 01
LmmIdx15_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64


LM06_CURRENT_BINNING_CLASS0	Left: F045Wert = 20 03	Right: F015Wert = 20 03
Also, just to confirm, FLE 43 and FLE 44 get the same changes (ie right vs left does not matter)?

Thanks
Appreciate 0
      04-05-2016, 12:52 PM   #126
matteis
Enlisted Member
9
Rep
32
Posts

Drives: bmw 118i f20 sport gp
Join Date: Oct 2015
Location: brazil

iTrader: (0)

Sorry for the dummy question, but how can I tell if a F15 has the anti-dazzle feature or can be coded to have it? I live in Brazil.

And, after coding, how can I make it work? Is it just switch on the high bean?
Appreciate 0
      04-05-2016, 01:07 PM   #127
alphaod
Mmmmm…
alphaod's Avatar
United_States
1148
Rep
2,426
Posts

Drives: F15
Join Date: Oct 2011
Location: New York

iTrader: (0)

Garage List
Quote:
Originally Posted by matteis View Post
Sorry for the dummy question, but how can I tell if a F15 has the anti-dazzle feature or can be coded to have it? I live in Brazil.

And, after coding, how can I make it work? Is it just switch on the high bean?
Do you have LED headlights? If yes, look at your build sheet or plug your VIN into any website that decodes your VIN. If it shows 5AP and 8S4, it has been disabled in the factory. Then you would have the lower 'A' button to turn on automatic headlights.

Assuming the above are all true, then you can code it following the instructions in this thread. And it would just work in place of your regular head beam assist ('A' button function).
Appreciate 0
      04-06-2016, 02:59 AM   #128
Almaretto
Major General
Almaretto's Avatar
2373
Rep
8,364
Posts

Drives: Test Vehicles
Join Date: Dec 2015
Location: Mountain View, CA

iTrader: (0)

Quote:
Originally Posted by ssft View Post
Were you able to figure this one out? I've got the same situation on my MY16 post-June, with CAFD_000024C3_008_010_000.ncd.
Nothing yet.
Appreciate 0
      04-10-2016, 11:46 PM   #129
E90325M
Captain
E90325M's Avatar
United_States
475
Rep
700
Posts

Drives: 2011 BMW M3
Join Date: Nov 2014
Location: Portland,OR

iTrader: (0)

Garage List
2016 BMW X5  [0.00]
2011 BMW M3  [0.00]
2016 X5 35i M-sport (built Oct 2015) coding

E-SYS: 3.27.1
E-Sys Launcher Premium: V2.0.
PSdZData: V.57.2_PSdZData_Lite.
Vehicle: 2016 X5 Xdrive 35i M-Sport (built Oct.2015)

Hey, guys, I finally begin my 2016 X5 coding. My car come with U.S $1900 Lighting Package so I believed that it should be able to code Anti-Dazzle, correct?

Anyway, I begin to follow the PDF V2 Appendix 2 instructions step by step. After I finished the step 1, I start to modify 22 + 79 functions both in FLE according to the PDF contents. But only modified some of them I found some functions did not have the value "F015Wert" from Edit-->drop-down menu. I checked more afterward,indeed there are a lot conflicts with the PDF table and I have to stop it.

Here are some examples:

FLE ECU "H_Plus4_Idx" does not has value “F015Wert”.
FLE ECU "WELL3_Idx" has default value "Unkown" and no "F015Wert" value to be choosen.
FLE ECU "PANICMODE_Idx" has default value "Unkown" and no "F015Wert" value to be choosen.
......

Then I download the modified ncd file provided by dmnc02 and use the method to program the ncd file into my car. Last night, I drive out and try to verify the Anti-dazzle function. but It seem Anti-Dazzle does not work as expected...

Today, I connected my car again and read out the FLE ECU config data and compared with the downloaded one. They are different on the bottom of file.

any help and thoughts?
Attached Images
 
Attached Images
File Type: pdf CAFD_000024C3_008_007_002.ncd.download.pdf (4.1 KB, 146 views)
File Type: pdf CAFD_000024C3_008_007_002.ncd.readout.pdf (4.1 KB, 160 views)
__________________
2016 F15 X5 xDrive 35i Space Grey M-Sport - BM3 Tune/ER charger pipe/afe power dry panel filter.
2011 E92 M3 DCT MW - AA intake/Akrapovic slip on/Ohlins R&T/Stoptech ST60 and ST40/Underdrive Pulleys/Antigravity H6 40ah/Alpine Tune
Appreciate 1
      04-12-2016, 03:57 PM   #130
Almaretto
Major General
Almaretto's Avatar
2373
Rep
8,364
Posts

Drives: Test Vehicles
Join Date: Dec 2015
Location: Mountain View, CA

iTrader: (0)

Quote:
Originally Posted by E90325M View Post
Today, I connected my car again and read out the FLE ECU config data and compared with the downloaded one. They are different on the bottom of file.
You mean just the signatures?

I downloaded the file you posted and it appears F015Wert is the selected value. I also have P58.0.
Attached Images
 

Last edited by Almaretto; 04-12-2016 at 04:06 PM..
Appreciate 1
      04-12-2016, 09:48 PM   #131
E90325M
Captain
E90325M's Avatar
United_States
475
Rep
700
Posts

Drives: 2011 BMW M3
Join Date: Nov 2014
Location: Portland,OR

iTrader: (0)

Garage List
2016 BMW X5  [0.00]
2011 BMW M3  [0.00]
Quote:
Originally Posted by Almaretto View Post
You mean just the signatures?

I downloaded the file you posted and it appears F015Wert is the selected value. I also have P58.0.
5 lines at end of two file are different, not sure if they are signatures of each file. It seem that you do not use F15 and E-SYS 3.27.1 for testing, your ECU structure is totally different. do you mean your PSdZData is P58.0? I use v57.2 not sure if this is the reason.

I just input the download ncd file into my E-sys and check. if forced use the downloaded ncd file, some function value were set to strange one like H_plus4_Idx was set to "F010Wert_SA552_US,F010Wert_SA552_US..." and WELL3_Idx was set to "unknown" but these Werte values were exactly set to the values of last column table in PDF.
Attached Images
 
__________________
2016 F15 X5 xDrive 35i Space Grey M-Sport - BM3 Tune/ER charger pipe/afe power dry panel filter.
2011 E92 M3 DCT MW - AA intake/Akrapovic slip on/Ohlins R&T/Stoptech ST60 and ST40/Underdrive Pulleys/Antigravity H6 40ah/Alpine Tune
Appreciate 0
      04-13-2016, 02:20 PM   #132
Almaretto
Major General
Almaretto's Avatar
2373
Rep
8,364
Posts

Drives: Test Vehicles
Join Date: Dec 2015
Location: Mountain View, CA

iTrader: (0)

Quote:
Originally Posted by E90325M View Post
5 lines at end of two file are different, not sure if they are signatures of each file. It seem that you do not use F15 and E-SYS 3.27.1 for testing, your ECU structure is totally different. do you mean your PSdZData is P58.0? I use v57.2 not sure if this is the reason.

I just input the download ncd file into my E-sys and check. if forced use the downloaded ncd file, some function value were set to strange one like H_plus4_Idx was set to "F010Wert_SA552_US,F010Wert_SA552_US..." and WELL3_Idx was set to "unknown" but these Werte values were exactly set to the values of last column table in PDF.
I have E-sys 3.27.1, E-sys Launcher Premium 2.5.3, and Psdzdata P58.0. However, I was using TokenMaster's NCD / CAFD Tool to quickly view the data and compare your two posted files. At the bottom of *.ncd's is a section called signatures.

Just as when werte values are changed to undefined values and drop-down's become UNKNOWN when loading files again, additional comma-separated menu items can appear (ie F010Wert_SA552_US,F010Wert_SA552_US..) if they have the same corresponding werte values.

Last edited by Almaretto; 04-13-2016 at 02:29 PM..
Appreciate 0
Post Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 11:22 AM.




xbimmers
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST