cafd_0000000f.caf.005_024_221:

https://mega.co.nz/#!Ul5SxJLY!iAkRdLioFfJgjigiqgO02OZaoftzfrASxmljUlSOanE

Copy to CAFD library folder (e.g. C:\Data\psdzdata\swe\cafd).

tx_trainwreck said:

I was able to start successfully coding my F01 (2013 750i) this week and make a few tweaks. But the most important ones I want are in the CAS module. When I go through the normal steps...

- select the CAFD_00000000f-005_024_221 entry under the CAS folder
- right click and choose [Read Coding Data]

... I get error "File for "CAFD_00000000f-005_024_221 not found (C012)". I didn't get it for any other modules.

Any ideas?

Click to expand...

I don't have cafd_0000106d.caf.012_003_012.

You can inject the following replacement CAFD into the ECU, VO Code it, and then you can FDL Code ECU:

cafd_0000106d.caf.012_003_013

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the replacement CAFD from above => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

Afterwards you will be able to FDL Code ECU.

tx_trainwreck said:

Thanks Shawn. That file worked fine... no issues. Now I'm working on my last tweak for the FRM module but I'm missing the following file. Can you please send me a link for it? Thanks.

Transaktions-Report: Aktion: Codierdaten lesen
FRM [72] [C996468]
readCPS o.k.
CAFD_0000106D_012_003_012 Fehler:
File for "cafd_0000106d-012_003_012" not found! [C012]

Click to expand...

Replace your cafd_0000000f.caf.005_025_036 in C:\ESysData\psdzdata\swe\cafd with this one, and tell me if you can read and code TRSVC:

cafd_0000000f.caf.005_025_036
https://mega.co.nz/#!YtxHGJDK!LgwWLcZdBVy7C1bl9x7blnqUiai29K9zT6QqPJ3qM0E

What does TokenMaster have to do with this issue?

mcbum said:

This means we all have to say: TokenMaster thank you very much!

Click to expand...

Yes, this is true, but what does that have to do with TokenMaster?

mcbum said:

It is not issue. FDL coding is over.

Click to expand...

No non-BMW solution in the world is going to fix depreciated CAFD data.

Yep.

VadimAA said:

For compare 2 files, you can use any text viewer:
NEW_cafd_0000000f.caf.005_025_036.xml http://f-bit.ru/560659
OLD_cafd_0000000f.caf.005_025_036.xml http://f-bit.ru/560660

Soon will be trimmed all files.

Click to expand...

All the descriptive information is being removed from CAFD files, leaving them useless for FDL Coding.

The future is already here:

VadimAA said:

...
p.s. Maybe in the future, FAFP will also be trimmed.

Click to expand...

That FAFP is from 54.3.

It is not an example.

It is FP Generated from 54.3.

CODING... :violent:

VadimAA said:

No, it is not mistake. It is war.

Click to expand...

Look, and you will see first few CAFD that are 425 kb in 54.0 and 54.1 are trimmed to 12 kb in 54.2 and 54.3:

TSTE1982 said:

i took a look at the 54.3 data and compared it to the 54.2 data. it seems that the older versions are trimmed. some files with newer numbers have the same size like the 54.2 files. has someone tried a car with the 54.3 data programmed and then read it out? it could be that the older files are trimmed and only the newest are ok. i need to compare the files next week.

Click to expand...

Correct. Not every thing is trimmed, at least not yet...

hanselino said:

It was not so clear, because logical was that with 54.3 all new cafd s up from 54.3 have trimmed files, nobody said that also older cafd which normaly related to older psdzdata are affected in 54.3
Now i know it and its good to see in shawns comparison.

But not all cafd are affected, in my case older cafd from fem was not trimmed as NBT

Click to expand...

cn555ic said:

The end is near!
__________________

Click to expand...

I am sure this friend used wrong terminology in referring to it as FDL Coding from Dealer, or he is referring to it indirectly as dealer VO Coding made underlying FDL changes.

ap90500 said:

Esys is for people who develope these systems (at BMW AG and subcontractors)

I don't know how the dealer did FDl-code your friends car, but AFAIK there is already a possibility that somebody from factory connects remotely to a car. What kind of coding your friend got?

Click to expand...

ap90500 said:

Of course there are untrimmed versions out there.

Click to expand...

Nobody99 said:

...wich will sooner or later be circulated. If they are given to there dealers it's just a matter of time, isn't it?

Click to expand...

I do not think there will be different untrimmed version. Bottom line is BMW does not need untrimmed CAFD and FAFP files at all. They will know the correct memory address for each function to accomplish anything they want.

Sure they do what? Need Untrimmed CAFD files? For what? ISTA/P doesn't need then to encode Control Unit, so they are not needed for any Dealer service. Do you think their development engineers must have them? Well, they don't.

Nobody99 said:

sure they do, however no software developer would remove any comments on his source code because they're helpful and will prevent mistakes.

Click to expand...

I just don't seem them maintaining two versions when they have no need to, It's too much work.

E-Sys will still be able to read ECU and Code it with trimmed CAFD, but you won't be able to find what you are trying to code in the first place.

jimmy9980 said:

I'm reading this right so Im currently on 2.54.1 so if my car gets updated to 54.2 and higher I'm unable to code any features into the car ? do to the cafd files being trimmed ? Its this becuase esys is unable to read them or BMW just changed the way the cafd files works ?

What about modifying the VO?

Click to expand...