[Node]

Just so you know new 4.42.20 psdzdata has a new chassis X001 which is for new bikes. And it has a "nice" surprise - secure coding. At least for now it looks like it.

[bennymx]

Great information thanks Node. I wonder if esys can still flash and code these secure coding modules.

[Node]

You can flash and you can code IF you have signed NCD. ESys will NOT be able to sign ncd which is part of normal coding process.

[bennymx]

Signed NCD comes from back end via ista? Or from technical support at elevated NSC level? Can regular Sgate user achieve this? I read in 4.42 patch notes that generation and storgae of secure tokens is not via back end. Does this mean its done locally on workshop machine?

[Node]

Secure tokens and signing NCDs are two COMPLETELY different things IMHO.

P.S. Where have you read about secure tokens? I don't see anything about that in release notes.

[bmwgstech]

Signed NCD comes from back end via ista? Or from technical support at elevated NSC level? Can regular Sgate user achieve this? I read in 4.42 patch notes that generation and storgae of secure tokens is not via back end. Does this mean its done locally on workshop machine?

Reading the UserManual of v4.45 explicitly indicates that Secure Tokens are controlled by the BMW back end:

---

I'm also not seeing any of the CAFD files mentioned for the modules now linked with secure tokens in the install directory. Did something else with the coding process also change?

[bennymx]

I haven't had to do anything with it yet. Obviously for now its mainly the 1300GS with secure coding. CAFD's are not available locally. Esys can't read the control units. I'd like to know if the CAFD was available, would Esys actually read them. Only error gave off was missing CAFD.

[Node]

ESys should NOT have any problem "reading control units". At least with the launcher. You should be able to get ncds. Normally you can write them back as is. Now if you modify them (with a launcher or if you get a CAFD file), you CAN'T write them back, because no signing key.

[RuleNormaliai]

ESys should NOT have any problem "reading control units". At least with the launcher. You should be able to get ncds. Normally you can write them back as is. Now if you modify them (with a launcher or if you get a CAFD file), you CAN'T write them back, because no signing key.

no, you can't even read modules which are secured with NCD2 as PSDZ does not have the files for that, and as i undestand it will not have it, you can only upload signed NCD, that's it.
You can't even open secured NCD in esys FDL Editor to view the parameters.