[Mwahab]

I was wondering how can i connect E-sys to my AOS/SGATE backend etc so it can validate certicates automaitcally, and what other options i can benefit from.
thanks

[Sedoy]

E-Sys is a developer tool and has nothing to do with AOS/S-Gate. Only for BMW Developers and Suppliers.

[oros]

E-Sys is a developer tool and has nothing to do with AOS/S-Gate. Only for BMW Developers and Suppliers.

what about signing NCD's for coding 2.0 and in future 3.0 ?

[Sedoy]

E-Sys is a developer tool and has nothing to do with AOS/S-Gate. Only for BMW Developers and Suppliers.

what about signing NCD's for coding 2.0 and in future 3.0 ?

Definitively not direct with E-Sys and BMW-Backend, again its only access for developer. Maybe with hacking.

[st1]

Just get 24 hours access to TIS/AOS and work with ISTA?

[oros]

E-Sys is a developer tool and has nothing to do with AOS/S-Gate. Only for BMW Developers and Suppliers.

what about signing NCD's for coding 2.0 and in future 3.0 ?

Definitively not direct with E-Sys and BMW-Backend, again its only access for developer. Maybe with hacking.

Yup, seems so. Attached extract from Esys says it all

There's tiny possiblity that somehow this can be spoofed by certifacate, but that's wishfull thinking IMHO.

---

Just get 24 hours access to TIS/AOS and work with ISTA?

This will get you as far as encoding a module, but not sure how it'll work for coding (modifications of NCD) seems ISTA is not permiting any changes to CAF files.

[st1]

It resolved my issue where I couldn’t code a VTG with Esys with SC requirement.

[2013m5]

I spoke with people at BMW center/dealer and they did not know E-Sys. They’re only using ISTA and ISTA-P, yesterday for my F36 maintenance. The good thing is they had the BMW field service on that day and he said E-Sys is factory tool internal use only, not for dealer.

[anstr]

It resolved my issue where I couldn’t code a VTG with Esys with SC requirement.

You have successfully encoded your module to the car, meaning adopted stock values to module. Try modyfying werte values thru ISTA and saving this to a module 

If you tell me how I'll bring you full bucket of gold

---

I spoke with people at BMW center/dealer and they did not know E-Sys. They’re only using ISTA and ISTA-P, yesterday for my F36 maintenance. The good thing is they had the BMW field service on that day and he said E-Sys is factory tool internal use only, not for dealer.

This part is clear mate, think the overall doubt is around how esys will work with coding 2.0 when connection to BMW backend will be required to sign the NCD before sending them to module. For basic modules replacement and programming ISTA is way to go.

Let's see what future will bring

[Node]

This will get you as far as encoding a module, but not sure how it'll work for coding (modifications of NCD) seems ISTA is not permiting any changes to CAF files.

This thread went off topic, but common guys, its the whole REASON secure coding is being introduced - to stop BMW losing money on things they can sell to people in form of subscriptions and FSCs. Of course they say it's about security, but that's mostly the BS for lamers.

I have no access to any secure coding car for tests so don't know how it actually works. But from pure logic if I were BMW then I don't see any reason why should servers (which ISTA contacts) be just signing the locally made NCD. It would make more sense that server prepares NCD and signs it. ISTA just receives it and uploads to the car. Whether ISTA sends actual FA to server or they just use factory FA with official retrofits, that is a different question. Of course there will be servers for internal and supplier use which sign NCDs but I don't expect these to leak to public. If they would - the high number of requests from different IPs will clearly give away leaked account which can be easily removed.

So I would say enjoy while you still can use ESys for custom codings as that is going bye bye.

I'm sure there will be developments like they there are now with tunings and similar things. In the end there will have to be something like bench flashing modified BTLD with modified (hence known) coding keys and then using ESys or custom tool to prepare NCD and sign it with that fake key. Or just bench flashing modified coding. Of course these will be much more involved (and hence expensive) operations.

In the end I don't think CAFDs will even be distributed in PSdZ data so ESys will become even more useless.