Token generator is the latest.
And before that was hacked e-sys, NCD / CAFD Tool.

ap90500 said:

Ok. BTW TokenMaster was not the first person to publish token generator for free, he actually didn't want to publish it because he said that BMW will likely introduce new protection systems if generator is released. So don't blame him.

Click to expand...

: popcorn:

mcbum said:

Token generator is the latest.
And before that was hacked e-sys, NCD / CAFD Tool.

Click to expand...

Maybe a lot of things in the past make sense. Like the token battle. And maybe a paid solution from someone special will appear in some weeks.
Only discussion theory

Who knows

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

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.

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...

@ vladim Can you explain a little more, had a look but i am not familiar with xml.

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

See picture.
http://www.bimmerfest.com/forums/showpost.php?p=8783429&postcount=10

No more Function Names.
No more Parametr Names.
So not possible FDL coding.

No need NCD/CAFD Tools anymore. :rofl:

Ok, same picture that i made with screenshot from my cafd.

VadimAA said:

See picture.
http://www.bimmerfest.com/forums/showpost.php?p=8783429&postcount=10

No more Function Names.
No more Parametr Names.
So not possible FDL coding.

Click to expand...

I predicted and warned about this a while ago. There will come a time when the software is out of everyone's reach, including mine. Sadly, some people are either too arrogant or naive to realize this, and now, BMW acted on it. While I am right with this prediction, I'm not happy either. It was a long time coming, though.

This is why it's "sold", it's limited. If there's one good thing that comes out of this, is that those using unsecured solution will finally be protected. That was the whole point of my Launcher app. I also have another weapon that is based on PSdZdata and is guaranteed to work with any E-Sys, both released and future versions. But with PSdZdata changing, that is now worthless.

Anyway, I'm traveling and can't look at it now. No tools at my disposal, but I'm not too hopeful. One thing I'm almost certain though, these are all just UI deep. Coding parameter format remains as-is. It would be very very expensive (and risky) to change that.

It was good while it lasted.

Well, there's one person who's happy to see NCD/CAFD Tool go.

VadimAA said:

See picture.
http://www.bimmerfest.com/forums/showpost.php?p=8783429&postcount=10

No more Function Names.
No more Parametr Names.
So not possible FDL coding.

No need NCD/CAFD Tools anymore. :rofl:

Click to expand...

Would not it be your program, we are now quietly continue coding.

TokenMaster said:

Well, there's one person who's happy to see NCD/CAFD Tool go.

Click to expand...

You mean "you" continually code and charge, right? It wasn't so much the tool as it is your unsecured solution. BMW can't afford to fix the possible risks that these unsecured solutions brought.

What are you talking about?
About my program "NCD-Tools"?
I did it in 2011, not for sale or distribution.
Access to my program has a limited number of people. Maybe you have it? Or did you see that someone using it? If so, show it to me.

So than my solution, after 4 years, could hurt BMW, unlike your solution, which 1 year old and it has become a popular and can be found in many public places, and hundreds of people use it.

This was my first thought and will probably work quite good. Only problem is that when new parameters are added, we won't know their names or meanings. This is not a real problem for now, and it is still possible to use ncd-cafd tool's what-if features to find new parameters which depend on some specific FA-code. I wouldn't say that FDL coding is dead, but yes it is in trouble.

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...

Before this thread crapping escalates to a different level, I decided to spend the energy looking into it.

I think this is just a fluke based on the 10 minute I spent on it, looking at V54.2:
Yes, CAFD_0000000f.caf.005_025_036 is messed up, but CAFD_0000000f.caf.005_025_037 is not. Obviously, the latter is newer.

CAFD_00000794.caf.012_035_117, which is new in 54.2, looks OK. Interestingly enough, 116 is missing in 54.2

This pattern goes on an on. Older files are messed up, but a newer files are just OK. Some of the files are:
cafd_00000909.caf.004_002_027
cafd_0000090a.caf.004_001_016

New NBT CAFD from V54.2: cafd_00000ded.caf.003_013_025 is OK

Again, I didn't look too much into it, but just seeing the pattern is enough for me. I don't have 54.3 yet but I think I'll wait for something newer before I spend more energy into it.

Bottom line is, no, FDL coding is not dead. Worst case, it just makes it more challenging. Best case, it's only a fluke.

54.3
Compare the file size.

That means, if i would like to do some FDL coding with the v.54.2 it is basically necessary to update the car´s software fist. Otherwise my car has still the old NBT CAFD which is messed up.

Of course this is just a estimation.

This means that in the future, all CAFD-files will be not suitable for FDL-coding.
For NBT, this has already happened.