05-10-2016, 12:33 AM | #155 |
Mmmmm…
1152
Rep 2,426
Posts
Drives: F15
Join Date: Oct 2011
Location: New York
|
I don't have the driver's side hump with auto low beam on.
|
Appreciate
0
|
05-11-2016, 07:45 AM | #156 |
Self-Deprecating Narcissist
7272
Rep 6,561
Posts |
is your's coded correctly?
if i put the vehicle in reverse or initiate the fog lights the double hump comes back: as soon as i put in drive or auto it disappears but the passenger side remains. this is indicative of "tourist solution". i have a feeling mine is coded improperly as yours may be too.
__________________
|
Appreciate
0
|
05-11-2016, 11:10 AM | #157 |
New Member
7
Rep 13
Posts |
Hey All - I posted this to the Bimmerfest coding forum, but it seems like this might be a better place to get some insights. Thanks in advance for any help!
So, last December, following the excellent instructions on the PDF that circulated a while back (dated Dec. 14, 2015), I was able to successfully code the glare-free high beams on my pre-2016 F15. They worked amazingly well! However, unfortunately, the car was brought in for service for an unrelated issue, and the system was re-coded to factory settings. I've since re-instated all my old settings, and the only thing that doesn't work the way it used to is - you guessed it - the glare free high beams. I've checked and re-checked that the appropriate VO codes are removed and changed the appropriate values in the two LHM ECU's (all sixteen of them are correct, including werte values). However, the high beams still won't function like they used to - they're back to the very distinct on/off USA functionality. Does anyone have any ideas on how to proceed? I really miss this feature. Before anyone asks, I'm not sure what version of the F15 software was installed by the service update. For reference, the update took place in the first week of April 2016. If there's a better way to tell what version I'm using, I'd appreciate a quick tutorial. Thanks! |
Appreciate
0
|
05-11-2016, 04:53 PM | #158 | |
Mmmmm…
1152
Rep 2,426
Posts
Drives: F15
Join Date: Oct 2011
Location: New York
|
Quote:
If I put into reverse I get the double humps. Otherwise it's only passenger-side hump. If I look at the light, clearly part of the driver's side LED is shut off. They come back on when GFHB is working, with manual highbeams, when in reverse, and when fog lights are on. |
|
Appreciate
1
|
05-12-2016, 07:51 AM | #159 |
Self-Deprecating Narcissist
7272
Rep 6,561
Posts |
exact scenario i have... coding was done properly but this is the end result. as you stated above i can clearly see one of the diodes are not illuminated on the driver's side but once i go into reverse or put the fogs on or manually engage the headlights the lighting returns to the traditional NAR double hump beam pattern. very odd behavior.
__________________
|
Appreciate
0
|
05-12-2016, 09:23 PM | #160 | |
Second Lieutenant
20
Rep 208
Posts |
Quote:
|
|
Appreciate
1
|
05-13-2016, 07:47 AM | #162 | ||
Self-Deprecating Narcissist
7272
Rep 6,561
Posts |
Quote:
Quote:
__________________
|
||
Appreciate
0
|
05-13-2016, 06:15 PM | #163 | |
Major
920
Rep 1,481
Posts |
Quote:
It is normal for BMW to slightly tweak the settings from one release of PSdZData to the next and this can be due to a variety of reasons. I clearly stated in post #108 that the CAFD/NCD file was being posted only as a temporary solution and should not been used on cars with newer CAFDs (the PDF is the only relevant source for those cars). The changes you noticed refer to the operating parameters for the stepper motors in the headlight and should be left to their factory values (they are not listed in the PDF). As for the parameters that have different literal values but the same Werte values, this is due to mapping inconsistencies in E-Sys Launcher (PSdZData is now trimmed and the literal values are mapped back dynamically by E-Sys Launcher, a process that is not error-proof). The Werte values are all that matters and that is the reason they are listed in the PDF.
__________________
2015 Mineral Grey ///M4 6MT
|
|
Appreciate
1
|
05-13-2016, 07:00 PM | #164 | |
Major
920
Rep 1,481
Posts |
Quote:
In your case, if you simply update your version of E-Sys Launcher to the current version, one of the literal values that appears as "Unknown" with the version you are using will magically change to "F015Wert".
__________________
2015 Mineral Grey ///M4 6MT
|
|
Appreciate
0
|
05-13-2016, 10:43 PM | #165 | |
Major General
2376
Rep 8,364
Posts |
Quote:
|
|
Appreciate
0
|
06-25-2016, 01:47 AM | #166 | |
Captain
475
Rep 699
Posts
Drives: 2011 BMW M3
Join Date: Nov 2014
Location: Portland,OR
|
Today I got my 2016 X5 35i M-sport (with Lighting package) Anti-Dazzle function enabled and went out for test drive for 15 minutes and I thought Anti-Dazzle function was properly enabled this time...
I was following the simple steps which dmnc02 gave. Coding thread here: http://f15.bimmerpost.com/forums/sho...k+door&page=90 The software versions I used listed at below: E-SYS: 3.27.1 E-Sys Launcher Premium: V2.5.3.108. PSdZData: V.58.2_PSdZData_Lite. Vehicle: 2016 X5 Xdrive 35i M-Sport (built Oct.2015) Previously I followed the V2 PDF steps to program 22+79 and it didn't make the Anti-Dazzle function worked as expected. If you have a 2016 X5 35i with LED then you can follow this simple steps for a try. Luck that your car will be Anti Dazzle enabled!!! Quote:
Thanks dmnc02 and 08bmw128i
__________________
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
|
06-25-2016, 07:20 AM | #167 |
Enlisted Member
10
Rep 30
Posts |
I just coded my f16 build 11/15 yesterday, spent 2 hrs on change all the values,no error code during the process.
But i dont know how to enable the GFHB? Just press the "HBA" button? Does it also come active if i turn high beam on manually? I did a test drive with "HBA" turn on, but the high beam didnt turn on all the time, maybe too many street light? It is in the city. |
Appreciate
0
|
06-25-2016, 07:25 AM | #168 | |
Major
920
Rep 1,481
Posts |
Quote:
My suggestion would be to give V2 another try at some point down the road. If you send me you NCD files, I can even confirm your coding. As you mention, once you have VO coded BDC_BODY, there is no need to do it again and so recoding NGHB will not cause you to lose your other coding.
__________________
2015 Mineral Grey ///M4 6MT
|
|
Appreciate
0
|
06-25-2016, 07:32 AM | #169 | |
Major
920
Rep 1,481
Posts |
Quote:
__________________
2015 Mineral Grey ///M4 6MT
|
|
Appreciate
0
|
06-25-2016, 10:59 AM | #170 | ||
Captain
475
Rep 699
Posts
Drives: 2011 BMW M3
Join Date: Nov 2014
Location: Portland,OR
|
Quote:
__________________
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
|
06-25-2016, 08:50 PM | #171 | |
Enlisted Member
10
Rep 30
Posts |
Quote:
In my ECUs, i didn't see KAFAS, i only have KAFAS2. Is that normal? |
|
Appreciate
0
|
06-25-2016, 09:48 PM | #172 |
Major
920
Rep 1,481
Posts |
Yes, it is: that is what I have seen in all recent cars.
__________________
2015 Mineral Grey ///M4 6MT
|
Appreciate
0
|
07-14-2016, 11:20 PM | #173 |
Enlisted Member
12
Rep 47
Posts |
This video shows the Anti Glare High beam work after coding.
https://goo.gl/photos/kJYF5MtnrASw7poT9
It works extremely fine on the busy roads. |
Appreciate
0
|
07-31-2016, 05:43 PM | #174 |
Captain
123
Rep 616
Posts |
I am in the middle of coding this (intense...) and I'm wondering if I can apply my ncd file with changes to both FLE ECUs or if I have to change the properties in each one. Are these ECUs the same? The CAFD files have the same exact file name...
2016 F15 built in late July EDIT: I saw in post 108 where the CAFD was attached that you can use the same file for both FLEs. Hope that was right.. because I just did it. No errors or anything. I am going for a test drive in 1-2 hours once it gets dark enough. That was the most intense coding I've ever done... My CAFD filename is: CAFD_000024C3_008_010_000.ncd EDIT 2: It works! I used the "Appendix 2" section of the PDF from Jan. 2016 (v2) and followed the guide. I was able to test it out tonight and it's working just like I saw in the videos posted in this thread. The tunnel was appearing and none of the cars I was following or driving past seemed to be getting blinded. Very awesome. Thanks to everyone who put the time into this effort. You are all amazing. Now it's time to code the F80! Last edited by mntbiker; 07-31-2016 at 10:02 PM.. |
Appreciate
0
|
08-21-2016, 06:09 PM | #176 |
Freude am Fahren.
835
Rep 1,287
Posts
Drives: F15 X5 xDrive35i
Join Date: Jul 2009
Location: Toronto, Ontario
|
Change the last figure of the vehicle type from 3 to 1 in FA (no need to save it in the car) and code LHM or FLEs to avoid that boring Step 2
Good luck!
__________________
Freude am Fahren.
Last edited by TheUltimateDrivingManiac; 08-21-2016 at 11:17 PM.. |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|