Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]

Pre LCI FEM doesnt accept LCI VO coding options
29-12-2017, 18:28 PM,
Post: #1
Pre LCI FEM doesnt accept LCI VO coding options
Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

All my knowledge is free for exchange with valuable information
Sharing->Development
  • FSC Repair kits - FSC Retrofits and Conversions Service history
  • Secure Coding 2.0 Type Key, FA, SFA, LCS Switch, SecOc, EOS Tester bypass after SME/HV Replacement
  • NBT/EVO/EntryNav2/MGU
  • MGU Carplay/Android auto W/O Telematics/CP/Patching in Middle East and Northern Africa
  • Feature Installer codes B2B
  • DME VIN ISN Working Hours IMMO OFF File and Remote Service/SWIFTEC - MG1 MD1 IMMO OFF
  • (E,F,G) 7DCT - DKG - 8HP - 6HP - EGS7 ISN Reset
  • KAFAS4 Virgin and Patching Remote
  • CAS2/3/4 Full IMMO & LOCKSMITH Customization Dump & Remote
  • HUF5663_434Mhz NO REMOTE SIGNAL FIX
  • F&G Series Headlight Customization
Visit this user's website
Quote this message in a reply
29-12-2017, 18:47 PM,
Post: #2
RE: Pre LCI FEM doesnt accept LCI VO coding options
I have same problem with led headlights retrofit to f30 2012.

Setubal-Portugal
Quote this message in a reply
29-12-2017, 18:50 PM,
Post: #3
RE: Pre LCI FEM doesnt accept LCI VO coding options
(29-12-2017, 18:28 PM)Mwahab Wrote:  Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

you have to flash it with fresh istep first

BMW tuning & retrofitting, https://www.instagram.com/cebepspb/
* lifetime EVO, ROUTE codes, Carplay, ECU Remap and other crap
Quote this message in a reply
29-12-2017, 18:56 PM,
Post: #4
RE: Pre LCI FEM doesnt accept LCI VO coding options
(29-12-2017, 18:50 PM)CEBEP Wrote:  
(29-12-2017, 18:28 PM)Mwahab Wrote:  Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

you have to flash it with fresh istep first

That's not the solution.
I try it for about two months at my F32.
Flashed it before with newest I-Step and try to add 5A1 but FEM made an error.

If my post helped you hit the thanks and reputation button. handshakehandshakehandshake

BMW F32 435d xDrive Coupe 12/2016 - Stage 2 drivedrivedrive
609 + 7XP NBT EVO | 6NW Wireless Charging | 6WD WLAN-Hotspot
Retrofits:
6WB Black Panel Cluster| 337 M-Sport Package | 715 M-Aerodynamic Package | 7XA M-Steering Wheel + Shift Padles | HELC LCI Tail lights | 3AG Rear View Camera | 5A1 LED fog lights | 552 adaptive LED Headlights | 430 Interior/Exterior Mirror Package | 760 Shadow-Line | 8TN Option iDrive DRL | 8TL DRL with Rear lights | OMSA SSA Memory | 4WD Laptimer | 6CP CarPlay | 6NR BMW Apps | 248 Steering heating | 6AS Driving Assistent with Front Collision Warning, People Warning and Lane Change Warning
+
Yamaha R6 RJ09 10/2004 - Stage 1 bikerbikerbiker
Quote this message in a reply
29-12-2017, 19:09 PM,
Post: #5
RE: Pre LCI FEM doesnt accept LCI VO coding options
(29-12-2017, 18:56 PM)bmw335coding Wrote:  
(29-12-2017, 18:50 PM)CEBEP Wrote:  
(29-12-2017, 18:28 PM)Mwahab Wrote:  Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

you have to flash it with fresh istep first

That's not the solution.
I try it for about two months at my F32.
Flashed it before with newest I-Step and try to add 5A1 but FEM made an error.

That is the only solution to add led fog lights on old car. Done many times.
code it adding K5A1 to Ho-Wort section in FA

BMW tuning & retrofitting, https://www.instagram.com/cebepspb/
* lifetime EVO, ROUTE codes, Carplay, ECU Remap and other crap
Quote this message in a reply
29-12-2017, 19:12 PM,
Post: #6
RE: Pre LCI FEM doesnt accept LCI VO coding options
(29-12-2017, 19:09 PM)CEBEP Wrote:  
(29-12-2017, 18:56 PM)bmw335coding Wrote:  
(29-12-2017, 18:50 PM)CEBEP Wrote:  
(29-12-2017, 18:28 PM)Mwahab Wrote:  Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

you have to flash it with fresh istep first

That's not the solution.
I try it for about two months at my F32.
Flashed it before with newest I-Step and try to add 5A1 but FEM made an error.

That is the only solution to add led fog lights on old car. Done many times.
code it adding K5A1 to Ho-Wort section in FA

Sorry, when the fingers are faster as the brain.laughing

5A1 for LED fog lights can be successfull added after i-step upgrade at my F32.
But not 5A2 for Led Headlights without adaptive, because an LCI have only led headlights with adaptive. (552)

If my post helped you hit the thanks and reputation button. handshakehandshakehandshake

BMW F32 435d xDrive Coupe 12/2016 - Stage 2 drivedrivedrive
609 + 7XP NBT EVO | 6NW Wireless Charging | 6WD WLAN-Hotspot
Retrofits:
6WB Black Panel Cluster| 337 M-Sport Package | 715 M-Aerodynamic Package | 7XA M-Steering Wheel + Shift Padles | HELC LCI Tail lights | 3AG Rear View Camera | 5A1 LED fog lights | 552 adaptive LED Headlights | 430 Interior/Exterior Mirror Package | 760 Shadow-Line | 8TN Option iDrive DRL | 8TL DRL with Rear lights | OMSA SSA Memory | 4WD Laptimer | 6CP CarPlay | 6NR BMW Apps | 248 Steering heating | 6AS Driving Assistent with Front Collision Warning, People Warning and Lane Change Warning
+
Yamaha R6 RJ09 10/2004 - Stage 1 bikerbikerbiker
Quote this message in a reply
29-12-2017, 21:34 PM,
Post: #7
RE: Pre LCI FEM doesnt accept LCI VO coding options
(29-12-2017, 19:12 PM)bmw335coding Wrote:  
(29-12-2017, 19:09 PM)CEBEP Wrote:  
(29-12-2017, 18:56 PM)bmw335coding Wrote:  
(29-12-2017, 18:50 PM)CEBEP Wrote:  
(29-12-2017, 18:28 PM)Mwahab Wrote:  Hey guys!

It happened to me 2 times, just as the title.

Some FEM doesn't accept the VO for LED headlights or LED Fog lights, they act as there is nothing written.

After VO coding with 5A1 as an example, removed the 520 or whatever the old salapa for Halogen fog light as well as changing the time criteria to a higher one, it act as there is no fog lights coded, all NSW related are nicht_aktiv.

Same story happened in the Headlights and taillights also, i have managed to get over this by manual FDL coding, but i am really curious about an answer, why the FEM didn't accept the VO?
and i don't think its an Istep issue, one of the car was prod date late 2014 and the issue was present. its an open discussion

you have to flash it with fresh istep first

That's not the solution.
I try it for about two months at my F32.
Flashed it before with newest I-Step and try to add 5A1 but FEM made an error.

That is the only solution to add led fog lights on old car. Done many times.
code it adding K5A1 to Ho-Wort section in FA

Sorry, when the fingers are faster as the brain.laughing

5A1 for LED fog lights can be successfull added after i-step upgrade at my F32.
But not 5A2 for Led Headlights without adaptive, because an LCI have only led headlights with adaptive. (552)

No, even in LCI models 5A2 is present without 552, it is available, some cars has got these specs.

All my knowledge is free for exchange with valuable information
Sharing->Development
  • FSC Repair kits - FSC Retrofits and Conversions Service history
  • Secure Coding 2.0 Type Key, FA, SFA, LCS Switch, SecOc, EOS Tester bypass after SME/HV Replacement
  • NBT/EVO/EntryNav2/MGU
  • MGU Carplay/Android auto W/O Telematics/CP/Patching in Middle East and Northern Africa
  • Feature Installer codes B2B
  • DME VIN ISN Working Hours IMMO OFF File and Remote Service/SWIFTEC - MG1 MD1 IMMO OFF
  • (E,F,G) 7DCT - DKG - 8HP - 6HP - EGS7 ISN Reset
  • KAFAS4 Virgin and Patching Remote
  • CAS2/3/4 Full IMMO & LOCKSMITH Customization Dump & Remote
  • HUF5663_434Mhz NO REMOTE SIGNAL FIX
  • F&G Series Headlight Customization
Visit this user's website
Quote this message in a reply
01-01-2018, 15:51 PM,
Post: #8
RE: Pre LCI FEM doesnt accept LCI VO coding options
Would an LCI FEM (treated/cloned with Autohex II) work OK on non-LCI?
Quote this message in a reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  FDL coding BMW Apps Mugga 3 99 36 minutes ago
Last Post: Mugga
XZBMW Coding a F80 M3 race car PeterY 10 468 Yesterday, 23:32 PM
Last Post: Furgus
  NBT Evo CAFD missing after coding error Mugga 13 596 24-04-2024, 22:47 PM
Last Post: Mugga
XZBMW 6wb cluster swap and coding xMoses 4 228 22-04-2024, 19:07 PM
Last Post: NikolaIMRS
XZBMW M performance brake DSC2 SBRE coding Ckh091020 3 217 22-04-2024, 12:58 PM
Last Post: Ckh091020
  pulling both paddles put transmission into neutral coding tintoverano 1 118 22-04-2024, 12:42 PM
Last Post: raresh.tazz
XZBMW F20 LCI2 black panel cluster coding sqorpius 9 2,010 21-04-2024, 12:38 PM
Last Post: Adekborys69
XZBMW G01 2019 X3 - ATM Replacement/Coding Help Needed jchisholm17 10 458 18-04-2024, 21:44 PM
Last Post: jchisholm17
  TMS FRM3 F10 Coding issue mj_mj_mj 17 1,929 16-04-2024, 09:30 AM
Last Post: user_530d
  BMW F10 RHD to LHD coding? morto 12 1,489 13-04-2024, 17:32 PM
Last Post: pablito94

Forum Jump:


Users browsing this thread:
1 Guest(s)

Return to TopReturn to Content