BMW Forum - BimmerFest BMW Forums banner

Coding Error - CAS module, CAFD_00000000f-005_024_221

93K views 549 replies 125 participants last post by  MadToha  
#1 ·
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?
 

Attachments

#4 · (Edited)
Did 54.0 work? There is a newer version, at least 54.1. 54.0 should though work, unless your car hasn't been updated recently. There is also other option, if your car still has software from factory: Sometimes at factory they install cafd versions that are not part of any psdzdata version. Solution for this is to inject new cafd via detect caf for swe and then vo-code the module.
 
#5 ·
I got it used (2 years old, 18k miles) so the code is probably still factory fresh.

54.0 worked fine for everything else. Just not the CAS module.

re: inject cafd... how do I do that? I looked into a the E-SYS user manual (v1.4 from 2007) and it briefly talks about detecting CAF for SWE... can you provide any quick steps? Thanks.
 
#8 ·
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]
 
#9 ·
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]
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.
 
#10 ·
I am also having issues reading my CAS file... The file I can't open using 54.2

Just lots of blank fields ".

CAFD_0000000F_005_025_036.ncd

I also get this error reading ,

CAFD_00000223_013_008_005 Fehler:

CPS read from ECU "ECUId:TRSVC_0x06" failed! [C070]
negative response error:

\\anyone have any ideas?
 

Attachments

#11 · (Edited)
#15 ·
Yes, this is true, but what does that have to do with TokenMaster?
 
#20 ·
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.
 
#24 ·
No non-BMW solution in the world is going to fix depreciated CAFD data.
 
#28 ·
All the descriptive information is being removed from CAFD files, leaving them useless for FDL Coding.
 
#31 ·
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.
 
#35 · (Edited)
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.
 
#37 ·
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.