[Mugga]

Hey guys,

after quite sometime I wanted to change some coding for my nbt evo (seems its id5). Sadly I got an error when coding it, and afterwards the cafd was missing.

I don't really know what I did wrong in the first place, maybe wrong esys (was using esysplus). But now I can't revieve the unit.

The two methods I've read up is "Detect CAF for SWE" but there is got an error that the file is missing "Failed to get CAFs for SWE "swfl_00002718-006_016_004"" and the second one is redeploying CA. I tried that with the I think still valid TAL in generated earlier when flashing the whole unit, but there I just get an "write ncd error hu_nbt2_63_ethernet" error.
Current setup is running on a bench, with ZGW02-Mid-Plus, which is connected via ethernet to laptop and connected via CAN to NBT.

Any help to revive the unit is highly appreciated.

Regards,
Mugga

[Bakica]

Sounds like you got a lock on your NBT

[alb3rt]

I can look remote

[Mugga]

Sounds like you got a lock on your NBT

Any idea why that happend and how I could fix that?

The last time I did flashing/coding was like 6 years ago and I havent changed anything on the setup I've used in that time. But I have to admit I also was not quite sure of the proper procedure.

I read the FA out of my ZGW which has the same VIN like the NBT, read the coding data, changed the cafd an coded it. And then the error.
Maybe wrong PsdzData or wrong ESYS being used (was using esysplus (3.27.1 Plus 2.8)).

[Node]

You SURE it's swfl_00002718-006_016_004? That is NOT in any released version of PSdZdata. And that could very well be the cause why ESys can't detect a CAFD for it.

[RuleNormaliai]

06_16_004 is ~2018-03/2018-07 data.
if you want i can take a quick look in to your situation.

[Node]

Well, swfl_00002718-006_016_004 is DEFINITELY NOT in current 4.46.40 KIS database...

[Mugga]

You SURE it's swfl_00002718-006_016_004? That is NOT in any released version of PSdZdata. And that could very well be the cause why ESys can't detect a CAFD for it.

Pretty sure, I copy/pasted the error exactly. It is quite possible that I have a "special" version, because I think when I was doing the upgrade to id6 the firmware I got was not really official.

[Node]

So use that unofficial data to inject CAFD then. You had to do that after/along with flashing anyway before. OR if you have that TAL from back then, then use it to get CAFD into the unit.

[Mugga]

Sadly, couldnt find anything on my laptop. Just found a .pdx file which was for the flashing to id6 back then I think. Omg this was all so long ago... just cant remember.

So only chance would be to reflash everything with a newer psdzdata?