[BMW-ALPINA]

Thanks for the update. Seems like you have almost the same issues like me except of the pulsing (and non light in the right door pocket). We will try some other things (use grey modules instead of violet, check codings etc).

[larbel]

I did a BCD NCD compare with my MY23 without factory door pocket lights to a friend's MY22 with factory door pocket lights, and I believe below are all of the ambient related coding differences. But since my has other mods, I'm not sure if my BCD coding are factory, let me know if you guys' are different?

NCD1 is my MY23
NCD2 is friend's MY22

[BMW-ALPINA]

larbel Ill check and confirm when i get the car back from the dealer workshop.

[JoB01]

Originally Posted by BMW-ALPINA

larbel Ill check and confirm when i get the car back from the dealer workshop.

I think we’re on to something with these two values… I experimented with them a bit, and they turn some of the ambient lights off/on , and others respond to the auto dim and some don’t, depending on what value im using. I’m thinking the answer is at least partially in these two…

[larbel]

Ok, I think I've figured it out... Here's the procedures to fix it:

1) Revert back to completely original and check if your BDC3 CAFD-000051DD-017.072.004 - CODINGDATA BODY_INNENLICHT matches the attached G26NoLights zipped NCD file, if not, then code it to match then do an Auto-Addressing (Auto-Addressing seems to be able to make change to the coding, so if you have done Auto-Addressing before, your coding might not be factory anymore).

2) Install your customs/OEM wiring loom and the LEDs.

3) Code the attached G26With_Lights zipped NCD file.

4) THEN do an Auto-Addressing.

Everything should now work as with factory door pocket lights. The INNENLiCHT coding seems to AFFECT the correctness of Auto-Addressing, so do NOT Auto-Address before the coding are done.

G26NoLights_000051DD_017_072_004.ncd is MY23 without door pocket light's factory coding.

G26With_Lights_000051DD_017_072_004.ncd is MY22 with factory door pocket light's factory coding.

[JoB01]

Perfect, this makes sense! Thanks!!!

[JoB01]

Originally Posted by larbel

Ok, I think I've figured it out... Here's the procedures to fix it:

1) Revert back to completely original and check if your BDC3 CAFD-000051DD-017.072.004 - CODINGDATA BODY_INNENLICHT matches the attached G26NoLights zipped NCD file, if not, then code it to match then do an Auto-Addressing (Auto-Addressing seems to be able to make change to the coding, so if you have done Auto-Addressing before, your coding might not be factory anymore).

2) Install your customs/OEM wiring loom and the LEDs.

3) Code the attached G26With_Lights zipped NCD file.

4) THEN do an Auto-Addressing.

Everything should now work as with factory door pocket lights. The INNENLiCHT coding seems to AFFECT the correctness of Auto-Addressing, so do NOT Auto-Address before the coding are done.

G26NoLights_000051DD_017_072_004.ncd is MY23 without door pocket light's factory coding.

G26With_Lights_000051DD_017_072_004.ncd is MY22 with factory door pocket light's factory coding.

Interesting, but I've run into a slight hitch...

my MY23 i4 has some different values in the NCD than your original values....specifically LIC_LCI_VERSION_DATA, which mine has as Werte 117, not Werte _108.

I'm also running a different software version in the 51DD CAFD-
mine is

BDC3 CAFD-000051DD-017.073.008, vice 72.004

When I try to switch the first three values-

LOG_LAMP_2_PHYS_LAMP_DATA
LOG_LAMP_2_PHYS_LAMP_INDEX
LCI_VERSION_DATA

to the G26_Lichtpaket_code1 and Werte 9 respectively, none of the Ambient lighting will turn on. all of those values have to stay as the default, or all my ambient shuts off (I tried various combinations of the three enabled, but ultimately, unless they are all set to the FA default; no ambient lights at all). did you run into this issue?

I coded everything else in the NCD compare, except the signature and CAF_ID (as I didn't think they'd be relevant to the issue... but maybe that's why the first three values are causing the ambientes to not work at all?)

I've tried re-addressing this way, but without going back to stock first, and the ambient behavior is still broken. Do you think the "going back to the stock setup and re-addressing" is really necessary, or was that portion just to ensure you had a "baseline" initial configuration?

[larbel]

Originally Posted by JoB01

Interesting, but I've run into a slight hitch...

my MY23 i4 has some different values in the NCD than your original values....specifically LIC_LCI_VERSION_DATA, which mine has as Werte 117, not Werte _108.

I'm also running a different software version in the 51DD CAFD-
mine is

BDC3 CAFD-000051DD-017.073.008, vice 72.004

When I try to switch the first three values-

LOG_LAMP_2_PHYS_LAMP_DATA
LOG_LAMP_2_PHYS_LAMP_INDEX
LCI_VERSION_DATA

to the G26_Lichtpaket_code1 and Werte 9 respectively, none of the Ambient lighting will turn on. all of those values have to stay as the default, or all my ambient shuts off (I tried various combinations of the three enabled, but ultimately, unless they are all set to the FA default; no ambient lights at all). did you run into this issue?

I coded everything else in the NCD compare, except the signature and CAF_ID (as I didn't think they'd be relevant to the issue... but maybe that's why the first three values are causing the ambientes to not work at all?)

I've tried re-addressing this way, but without going back to stock first, and the ambient behavior is still broken. Do you think the "going back to the stock setup and re-addressing" is really necessary, or was that portion just to ensure you had a "baseline" initial configuration?

The revert back step was essential at least for me, since the addresses of the LEDs were all messed up from the previous auto-addressing based off the wrong coding I guess.

I don't think CAF_ID and Signature matters as they're more of a checksum for the coding, and we're running on 3/23 i-step I think, because over here, CarPlay is disabled in the local ConnectedDrive server, and if we have enabled CarPlay, we have to disable the online features hence, no OTA... But still, don't think the different software version would matter much.

The only thing might be an issue would be factory options and if you have different numbers of interior lightings? But I don't think there's any extra option besides ambient correct? So, in theory, should be fine here as well?

I'd backup your current, or if you have a copy of the stock NCD, then revert back to stock and auto-address and make sure all the LEDs functioning correctly. And instead of doing the coding one by one, just load the NCD and code it all at once with BU? And then auto-address it to see?

[JoB01]

Originally Posted by larbel

The revert back step was essential at least for me, since the addresses of the LEDs were all messed up from the previous auto-addressing based off the wrong coding I guess.

I don't think CAF_ID and Signature matters as they're more of a checksum for the coding, and we're running on 3/23 i-step I think, because over here, CarPlay is disabled in the local ConnectedDrive, and if we have enabled CarPlay, we have to disable the online features hence, no OTA... But still, don't think the different software version would matter much.

The only thing might be an issue would be factory options and if you have different numbers of interior lightings? But I don't think there's any extra option besides ambient correct? So, in theory, should be fine here as well?

I'd backup your current, or if you have a copy of the stock NCD, then revert back to stock and auto-address and make sure all the LEDs functioning correctly. And instead of doing the coding one by one, just load the NCD and code it all at once with BU? And then auto-address it to see?

Thanks again!

I’ll reset to default and then try with the updated ncd values. Thanks!

[JoB01]

Originally Posted by larbel

The revert back step was essential at least for me, since the addresses of the LEDs were all messed up from the previous auto-addressing based off the wrong coding I guess.

I don't think CAF_ID and Signature matters as they're more of a checksum for the coding, and we're running on 3/23 i-step I think, because over here, CarPlay is disabled in the local ConnectedDrive server, and if we have enabled CarPlay, we have to disable the online features hence, no OTA... But still, don't think the different software version would matter much.

The only thing might be an issue would be factory options and if you have different numbers of interior lightings? But I don't think there's any extra option besides ambient correct? So, in theory, should be fine here as well?

I'd backup your current, or if you have a copy of the stock NCD, then revert back to stock and auto-address and make sure all the LEDs functioning correctly. And instead of doing the coding one by one, just load the NCD and code it all at once with BU? And then auto-address it to see?

BU won’t let me load the entire ncd since it’s an older software version than what’s in my car- so I’m kind of stuck doing it one by one- but no problem there.

One question for you… to get the “mostly functional” pocket lights, I had to switch pins 3&4 on the passenger side door pocket light connector on my harness. The other 3 harnesses worked as is. Was this the case for you as well? Or were all 4 of your harnesses identical?

[larbel]

Originally Posted by JoB01

BU won’t let me load the entire ncd since it’s an older software version than what’s in my car- so I’m kind of stuck doing it one by one- but no problem there.

One question for you… to get the “mostly functional” pocket lights, I had to switch pins 3&4 on the passenger side door pocket light connector on my harness. The other 3 harnesses worked as is. Was this the case for you as well? Or were all 4 of your harnesses identical?

All harnesses are the same, I did not need to switch any pins at all.

[JoB01]

Originally Posted by larbel

All harnesses are the same, I did not need to switch any pins at all.

I did all the coding today, and re-ran the autoaddressing, and it worked!

The only coding “variance” I had to make was I set Werte 118 for “LCI_VERSION_DATA”, since 109 did not work for me: my original value was WERTE_117…

I also did not code the signature or CAF_ID.

I didn’t have to “revert back to original harnesses” and recode the default ncd, either- I just coded the “with lights” ncd with the change I described above, re-ran the autoaddressing and it all works now perfectly.

Thank you for your help finding the “with lights” ncd! This is a big win!

[BMW-ALPINA]

Ill just tap into to say this coding solved the problems. Thanks to larbel and JoB01 for good work!

[Jax327]

Originally Posted by BMW-ALPINA

Ill just tap into to say this coding solved the problems. Thanks to larbel and JoB01 for good work!

Attachment 3584127

Attachment 3584128

How do you go about installed the LEDS in the door panel? Do you have to drill them?

[JoB01]

Originally Posted by Jax327

How do you go about installed the LEDS in the door panel? Do you have to drill them?

The mounts for the leds and holes for the fibre optics already exist in the door panels, so all you need to do is buy the parts (4 led light modules, 4 fibre optics, and build or buy 4 wire harnesses) and install them. There is a thread here that discusses fabricating your own wire harness and which parts to buy… total cost is somewhere around $125, depending on where you source the parts. Time to install is about an hour. About 20 minutes to do the coding in the BDC (using bimmercode expert mode, or bimmerutility), and about 5 minutes to address the new led modules (using ISTA+)

[BMW-ALPINA]

Originally Posted by Jax327

How do you go about installed the LEDS in the door panel? Do you have to drill them?

As JoB01 mentioned. Everything is ready in the door panels, so you just need wiring harness, LED modules and fiber optic.

[Jax327]

Originally Posted by JoB01

The mounts for the leds and holes for the fibre optics already exist in the door panels, so all you need to do is buy the parts (4 led light modules, 4 fibre optics, and build or buy 4 wire harnesses) and install them. There is a thread here that discusses fabricating your own wire harness and which parts to buy… total cost is somewhere around $125, depending on where you source the parts. Time to install is about an hour. About 20 minutes to do the coding in the BDC (using bimmercode expert mode, or bimmerutility), and about 5 minutes to address the new led modules (using ISTA+)

In regards to the wire harness, can you buy oem ones? Didnt see a write up on that?

[phani_ch]

Originally Posted by larbel

This is the cable I made, I couldn't find the part number for the OEM TE connectors so this is what I used https://vi.aliexpress.com/i/33030044...yAdapt=glo2vnm For me, the wires are about 30" long to route along the OEM harness on the G26 GC.

The part numbers for the fiber optics and LED modules are:

63316998139 Fibre-optic conductor door pocket front left X 1
63316998140 Fibre-optic conductor door pocket front right X 1
63316998141 Fibre-optic conductor door pocket rear left X 1
63316998142 Fibre-optic conductor door pocket rear right X 1
63319891437 LED module violet X 4

If we buy the above mentioned parts, do we have to modify or alter the existing wire harness or still buy the custom adapter?
Can we code it using Bimmercode?

[larbel]

Besides the fiber-optics and LED modules, you'll either need to modify your harness or buy the OEM harness. And no, only ISTA can perform the auto-addressing needed.

[phani_ch]

Originally Posted by larbel

Besides the fiber-optics and LED modules, you'll either need to modify your harness or buy the OEM harness. And no, only ISTA can perform the auto-addressing needed.

Can you share the part number for OEM harness?

Thanks.

[BMW-ALPINA]

Originally Posted by phani_ch

Can you share the part number for OEM harness?

Thanks.

LHD cars:
Front left: 61 12 5A362A7
Front right: 61 12 5A362B2
Rear both sides: 61 12 5A362B5

[Jax327]

Do those fiber optic parts work for the 3 series as well? Not sure if these were for the 4 series.