[alexturbo]

IMHO it does not matter how connection is established as long as there is one.

From your SVT_ist I see that multiple units have their CAFDs deleted: BDC, HU, ZBE at least. You need to inject CAFDs into them and code them.

Maybe you can find better instructions elsewhere, but quick guide:
1. Go to Expert Mode/Coding.
2. Load FA, read/load SVT_ist.
3. Find a unit which has CAFD_FFFFFFFF_255_255_255.
4. Select that UNIT (not CAFD).
5. Click detect CAF for SWE.
6. Choose CAFD from a list (you can choose latest iStep, or some specific one if you know the whole car is at that step). If multiple CAFDs are shown FOR A SAME STEP, you need to select them all using ctrl key (not in these units).
7. Click code.
8. Repeat from 3 for next unit.

Let's see from there.
You can also try to execute this in transmitter: Clear all DTCs (clear DTC,clear Infospeicher,ZFS – DM_Lock,clear ZFS – DM_Clear,ZFS – DM_Unlock)

P.S. It seems you installed BDC from an older car (with older HWEL). Whatever I did I could not get ESys to calculate proper update for this BDC in this car, not even by manipulating type/time. Of course there is "actual HWEL" button, but ESys calculates replacement BDC with newer bootloader/software which according to KIS is not compatible with your HWEL. My guess it has some other hardware which is just incompatible with this BDC. It may work, but update SVT will need to be written manually if you want to flash last iStep. You may try to calculate it with an actual car connection, maybe then result would be different somehow.

P.P.S. ACSM2 is older too, but that can be calculated by setting a bit older factory level. But then you need to flash ACSM2 ONLY with such a TAL!

I've tried everything still no success.
I also think that HWEL is too new and software.
Can I revert it back to older?
Without KL 15 there is no bdc to flash.

Here is my current SVT_ist from today

[Node]

What happens when you try to switch ignition on now? At this point I would suggest battery reset. That should also clear all strange energy states.

Also how come HWEL of BDC suddenly changed? HWEL you can't change as it is hardware electronics identification. (Well you can change it by editing flash dump, but that will be asking for even more trouble).

[alexturbo]

When I turn on the ignition, I get some information in the mini panel of the instrument cluster and there is no key or remote control on the steering column in between. I checked it with VVDI 2 and the key is recognized by vehicle coil.

Battery reset done and no change.
I have already unlocked BDC with VVDI and Close transport mode. Still no change.

I think something is wrong with programming to the BDC, like coding something changes, software...
Because it is already the second BDC after programming, no ignition turns on and it changes terminals like 15N, 30B to less than 10V.
It would be best to bring BDC back to its original state.

[Node]

Have you read faults from BDC?

[alexturbo]

Have you read faults from BDC?

The error codes are as follows:
-D90D01 FBD Receiver 1 LIN
-80409A Driver KL15N1
-8040BD KL 30F reset or shutdown
-801C10/801C11 KL 30F 
-S0701 KL 15 preventer
-E12C1D Signal invalid

[Node]

At this point I'm starting to think you have something broken in the car. Faults do not indicate any coding, flashing or security fault.

I wonder... try what happens if you disconnect IBS...!? (Just because of missing LIN slave fault)

Also you may need to write SVT to BDC. Either new one or from backup unit.

If not help, calculate test plan and run test modules for these terminal controls.

[BMWzone]

Do you check ELV ?
It can break after water damage

[alexturbo]

Do you check ELV ?
It can break after water damage

ELV exchanged
The problem appeared after flashing/encoding

---

At this point I'm starting to think you have something broken in the car. Faults do not indicate any coding, flashing or security fault.

I wonder... try what happens if you disconnect IBS...!? (Just because of missing LIN slave fault)

Also you may need to write SVT to BDC. Either new one or from backup unit.

If not help, calculate test plan and run test modules for these terminal controls.

IBS disconnect but no change.
LIN slave fault was not before, only appeared after flashing/coding. Test plan Ista knows re-encode on BCD.
I don't have a backup because the old BDC is dead. I can't program the BDC either because the KL15 errors are missing.

I can't carry out Ista's action plan either, due to hardware actions: install HU, TBC and exchange CON.

[Node]

You can reencode BDC with ESys. Just go to coding, load FA, SVT, select BDC and click code.

---

But as I already mentioned you need to write SVT to it too. As your SVT is now incomplete due to missing units, it would be best to copy it from backup unit.

[alexturbo]

I have a broken BDC (but it communicates) from another similar vehicle. Can I copy all data with Esys and then reprogram bdc to vehicle? If yes, how can I do it?