[markodsk]

Hi,

I've recently FDL coded BDC_BODY using eSys 3.40.2 and PSdZData 4.38.30, everything went ok, however I've noticed the following warning in the logs:

SVK_ist for ECU BDC_BODY2_40 contains the following software units not contained in SVK_soll:

[cafd_000017bd-200_049_003, cafd_00001df7-006_024_071, cafd_00001df8-109_052_001].
SVK_soll is incomplete or ECU contains unexpected software units.

The car is a G01, X3 made in 2018, which I have purchased as a used car directly from a BMW dealer a year ago.


The car is still in warranty and when I took it into service, the dealer tried to flash the newest software, however, he told me that ISTA-P shows the BDC unit as not genuine / foreign / retrofitted / etc. (I don't have the exact error message).

I think this cound be related with the warning eSys gave me. I haven't changed the BDC unit, or flashed it. The previous owner had a side collision and the right side door was exchanged for a brand new one - maybe the BDC unit was exchanged or manipulated in the past?

Is there something I can do - delete the extra CAFD files from BDC, update SVT_soll, etc.?

Thanks for any insight on how to solve this.

[TheNine90]

If you flash BDC esys will should solve any missing or extra.
Can you post the svt tree of bdc

[markodsk]

If you flash BDC esys will should solve any missing or extra.
Can you post the svt tree of bdc

Sure, I've attached a screenshot below (the "extra" CAFD files are marked in red).

According to the pictures, there are two CAFDs with label "Codierdaten (CAF)" - I guess that's not okay and there should be only one. However, the other 2 "extra" CAFDs are labeled: Codingdata "BODY FUSI" and "BODY LA", aren't they needed?

Can you please post instructions on what I should do using eSys in order to fix this?

Thanks!

[Node]

If you flash BDC esys will should solve any missing or extra.
Can you post the svt tree of bdc

Sure, I've attached a screenshot below (the "extra" CAFD files are marked in red).


Can you please post instructions on what I should do using eSys in order to fix this?

Thanks!

There are NO "extra" cafds here. ALL of them MUST be there. IMHO the reason for that message is that you used ESys incorrectly or don't know how to use it.

---

P.S. Dealer COULDN'T tell that ISTA-P said that, because ISTA-P was NEVER designed to be used on G+ series cars!!! But dealer could have said that ISTA+ requires replacement of BDC because of various potential reasons, one (among hundreds) of them could be that someone broke FA stored on the car...

[markodsk]

I did not flash the BDC, I just FDL coded ASS to "off". Since FDL coding does not inject or alter CAFDs, what's the reason for the warning?

EDIT: Should there really be two different CAFDs with label "Codierdaten (CAF)"?

[Node]

Did you code the WHOLE unit or a SINGLE CAFD???

Why not?

[markodsk]

I got the warning when coding a single CAFD.

[Node]

I got the warning when coding a single CAFD.

So the answer SHOULD be clear now! It listed ALL CAFDs which were NOT coded!

[markodsk]

Okay, that makes sense... However, the dealer told me that something is wrong with the BDC module - he hooked up ISTA-P and got some sort of a warning that BDC is not okay. Is there something I can do?

[Node]

As I said already, dealer could NOT have said anything about ISTA-P, because it NEVER worked with G+ series. Dealer could have mentioned ISTA+ instead.

However unless you provide FULL FA.xml and SVTist.xml here you will have to find someone with this fancy new BMW diag device (https://cartechnology.co.uk/showthread.p...#pid561159) to answer your question.