[M3ighty]

Can anyone help??

Getting an error only with KOMBI, everything works fine...
Using Esys 3.24.3. Coding anything else works fine.


Error Code:

Transaktions-Report: Aktion: Codierdaten lesen

KOMBI [60] [F720116]
readCPS o.k.
cafd_000009c8-006_000_030 Fehler:
NCD read from ECU "ECUId:KOMBI_0x60" for CAF "cafd_000009c8-006_000_030" failed! [C069]
Error processing XML data [1660]

[shawnsheridan]

What are you using for your Target Connection?

[PaulT_M5]

I have just got my coding cable and was doing some backups to ensure everything works before purchasing my token.

I too am getting exactly the same error message (albeit with a different VIN)

I have the following software as provided by the links you PM'd me:

E-Sys 3.24.3
psdzdata lite 52.3
No token as yet

I can read FA, VCM and can read all the CAFD's apart from the one under KOMBI.

I have a 2014MY (NBT with iDrive Touch) F30 manufactured in July 2013

My Target is:

TargetSelector: Project=F020_14_03_503; VehicleInfo=F020

Connection via VIN: WBA...._DIAGADR10

My I-Step (for all 3 boxes) is F020-13-07-501


Any advice or further checks I can do to identify the problem.

--- update, just looked at the files in psdzdata folder for the cafd number and spotted that all files have pretty much the same time stamp apart from the one relevant to this CAFD read which is failing:

C:\data\psdzdata\swe\cafd>dir *9c8*
Volume in drive C is System
Volume Serial Number is 1EC2-4B8F

Directory of C:\data\psdzdata\swe\cafd

27/03/2014 20:26 694,017 cafd_000009c8.caf.004_001_012
27/03/2014 20:26 694,149 cafd_000009c8.caf.004_001_013
27/03/2014 20:26 691,423 cafd_000009c8.caf.004_002_007
27/03/2014 20:26 697,231 cafd_000009c8.caf.004_002_023
27/03/2014 20:26 699,759 cafd_000009c8.caf.004_002_024
27/03/2014 20:27 772,867 cafd_000009c8.caf.005_000_028
27/03/2014 20:27 773,197 cafd_000009c8.caf.005_000_029
27/03/2014 20:27 773,237 cafd_000009c8.caf.005_000_030
27/03/2014 20:27 774,405 cafd_000009c8.caf.005_000_051
27/03/2014 20:28 1,081,372 cafd_000009c8.caf.006_000_027
27/04/2014 21:59 1,080,686 cafd_000009c8.caf.006_000_030
27/03/2014 20:28 1,081,082 cafd_000009c8.caf.006_000_031
27/03/2014 20:28 55,281 cafd_000009c8.caf.006_000_047
13 File(s) 9,868,706 bytes

[shawnsheridan]

Let me connect with Team Viewer and look at it.

[PaulT_M5]

PM me details and I'll go back out to the car

[shawnsheridan]

Originally Posted by shawnsheridan

Let me connect with Team Viewer and look at it.

Originally Posted by PaulT_335i

PM me details and I'll go back out to the car

Not sure why really, but injecting newer CAFD version into Kombi solved the problem.

[PaulT_M5]

Thank you very much for sorting this out for me. I would like to thank you for your excellent service.

[shawnsheridan]

No problem. Free help isn't exactly a "service", though.

[Grippy]

Hi chaps
I'm getting the same error. What exactly do we mean by injecting a newer version into KOMBI? does it involve changing the file in swe\cafd named cafd_000009c8-006_000_030? or do I need to get a newer version of the one I am trying to code?
I have tried selecting code on the KOMBI ECU. I've tried read code and deleting fld and adding a new one. All get the same error.
Thanks for your time.

[Grippy]

Found this from the man himself ShawnSheridan on bfest. Amazing what searching does eh!? Sorry chaps...

You need to try and inject new CAFD into NBT and then Code it:

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

Gonna try this and get back to you all.

[Grippy]

No dice...

Any ideas? I don't think i am doing the right thing though when it says select cafd from latest istep. I see many folders and lots of numbers. I picked the one with a higher number than the one i have. This was against KOMBI by the way, not HU_NBT as this copy says. Is this right? arghh

Apologies for my grammar, I'm balancing the lappy on my steering wheel.

[shawnsheridan]

Originally Posted by Grippy

No dice...

Any ideas? I don't think i am doing the right thing though when it says select cafd from latest istep. I see many folders and lots of numbers. I picked the one with a higher number than the one i have. This was against KOMBI by the way, not HU_NBT as this copy says. Is this right? arghh

Apologies for my grammar, I'm balancing the lappy on my steering wheel.

Send me a PM when I can connect with TeamViewer and look at it.

[Frogman]

Originally Posted by Grippy

Hi chaps
I'm getting the same error. What exactly do we mean by injecting a newer version into KOMBI? does it involve changing the file in swe\cafd named cafd_000009c8-006_000_030? or do I need to get a newer version of the one I am trying to code?
I have tried selecting code on the KOMBI ECU. I've tried read code and deleting fld and adding a new one. All get the same error.
Thanks for your time.

I got this same error coding someones car 2 weeks ago using 2.52.3.

I reverted back to 2.52.2 and was able to read / code his KOMBI without error.

Later, I compared all of the 52.2 vs 52.3 CAFD files and found that the cafd_000009c8-006_000_030 file is different between the 2 versions. it was the only file that was different.

I did a binary compare of the 52.2 vs 52.3 cafd_000009c8-006_000_030 files and found that although both files contain exactly the same number of bytes, the 52.3 version is all NUL (0x00) bytes!! Oops! There's no useful data in there at all!

So, I'm back to using 52.3, but I just copied the 52.2 version of cafd_000009c8-006_000_030 into the 52.3 directory.

To me, this technique is easier than trying to inject a new CAFD into the KOMBI.

[shawnsheridan]

If you happen to have your previous PSdZData version lying around (most don't), you are right that it is easier to just replace cafd_000009c8.caf.006_000_030.

If you do not have previous PSdZData version lying around , it is much easier to just inject a new CAFD into ECU than find a download location for previous PSdZData version and download a 5.6 Gb file and extract it to get one CAFD from it.

To make it real easy, here is cafd_000009c8.caf.006_000_030:

cafd_000009c8.caf.rar.pdf

Remove .pdf from file name and Extract CAFD, and copy to ...\psdzdata\swe\cafd folder overwriting existing one.

[Timelessky]

hi shawn,

while today I am retrofit(CC) my f20 , after VO Coding, I try to code kombi , ICM, Fem. I recieved error at KOMBI section.

e-sys 3.25.3
pszdata 2.53.0.5

Then I couldn't fdl coding or read coding data e.t.c . I try to fix with ''Detect Caf for swe'' no result :/

my error report as you ve seen: http://postimg.org/image/6a00hmj1v/

what should I do ?

[shawnsheridan]

CIC Retrofit should have no impact on Kombi coding.

What happens when you try and VO Code Kombi with E-Sys 3.23.4 or 3.24.3 instead of 3.25.3?

[Timelessky]

Originally Posted by shawnsheridan

CIC Retrofit should have no impact on Kombi coding.

What happens when you try and VO Code Kombi with E-Sys 3.23.4 or 3.24.3 instead of 3.25.3?

Sorry for my misspeling, I ve tried Crusie Control retrofit. I am not related with CIC.

I dont have any admiration for using 3.25.3 If I recieve better performance, I can use 3.23.4 or 3.24.3. I just one question; Can I use current patch and token for them ?

[shawnsheridan]

Originally Posted by Timelessky

Sorry for my misspeling, I ve tried Crusie Control retrofit. I am not related with CIC.

I dont have any admiration for using 3.25.3 If I recieve better performance, I can use 3.23.4 or 3.24.3. I just one question; Can I use current patch and token for them ?

No, 3.25.3 is not admirable...it has bugs. I have had 3.25.3 since December last year, 8 months now, and I still use 3.24.3.

Did you modify your FA for CC Retrofit? If so, are you able to code Kombi with factory original FA?

And did you first try what I wrote above in Post #14?

http://f30.bimmerpost.com/forums/sho...5&postcount=14

[Timelessky]

Originally Posted by shawnsheridan

No, 3.25.3 is not admirable...it has bugs. I have had 3.25.3 since December last year, 8 months now, and I still use 3.24.3.

Did you modify your FA for CC Retrofit? If so, are you able to code Kombi with factory original FA?

And did you first try what I wrote above in Post #14?

http://f30.bimmerpost.com/forums/sho...5&postcount=14

Ok, I will downgrade to 3.24.3, Can I use same patch or token ?

I've completed code KOMBI. I ve coded with ''Detect CAF SWE'' I ve choosen .502 instead of .506 . But while another ECUs coding succesfully, why did I forced to apply this steps for KOMBI?

[shawnsheridan]

Becuase .506 CAFD not compatible with ECU SWFL. ECU would need to be flashed to use newer CAFD.

No, Token solution is entirely different for 3.25.3 than older E-Sys 3.24.x versions.

[shawnsheridan]

After looking at this some more, the cafd_000009c8.caf.006_000_030 file is simply corrupt. It won't even open in E-Sys CAFD Viewer, yet cafd_000009c8.caf.006_000_031 opens just fine.

The solution here is to inject a different CAFD file into KOMBI:

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on KOMBI ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level that is not cafd_000009c8.caf.006_000_030 => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

[Timelessky]

[QUO