[TheNine90]

Originally Posted by vomba

Yes, I'm using E-Sys 3.30 with full Psdzdata and valid token. I adapted FA/FP and injected new FA/FP with expert mode => VCM. I generated new CAFD's for the affected ECU's by using "coding verification" (following an instruction I found in another thread) and injected them (coding tab => CAFD => new => select new CAFD => FDL coding). This works fine except CAFD 222D in the new FLM. There, I get errors when I try to code it as well when trying to read old coding data or ECU ID. I want to try flashing the ECU next, as proposed in another thread; but I'm afraid that I might again get no access to do so.

Does the method i provided work? Which error do you get?
I can have a look at it if you are interested

[vomba]

Originally Posted by TheNine90

Does the method i provided work? Which error do you get?
I can have a look at it if you are interested

Thank you. Of course I'm interested. Will try your proposal tonight and then report success or quote the errors I get. Fortunately, I managed to connect new headlight without actually inserting it into the car, which takes hours.

[vomba]

Problem solved; flashing the new FLM's was the solution.

@TheNine90: your proposal already put them in usable mode. But because they were used and had older firmware (at least that is the reason I assume) I could not inject newest CAFD version, merely older ones. Flashing brought everything on the newest level though.