MagicCarpet
Well-known member
- Joined
- Mar 8, 2019
- Messages
- 67
On the subject of e-SYS coding, I am doing this with an OBD2 cable with 2017 e-SYS with PSdZDATA on my 2017 i3.
It took me 5 hours to download and install onto a spare PC and another 5 hour day to hook up and alter the first coding settings, using all the info I could find on the various Bimmerpost etc. forums. OK taking it slow I dont want a bricked car...
I'm seeking help with how the cars various ECUs store data / config files and how to change these files.
So far I have listed some of the functions; if anyone can add to the knowledgebase that would be appreciated:
FA : factory order
VO : vehicle order coding - changes options globally without having to enter changes to each affected ECU
FDL : function data list - list of activ attributes within each ECU - FDL coding just changes individual ECU attributes by overwriting the VO coding
VCM : vehicle configuration management- (a) FA = vehicle order profile, VIN, options
(b) SVT = software variant table, lists ECU name, CAFD id, firmare but no coding parameters
(c) CAF
(d) CAFD = the processed CAF = need to know the CAFD id in order to load into FDL editor
(e) NCD = the net coded data - the compiled data ready to be activated using the FDL editor
I'd like to understand exactly which of the software and hardware / firmware systems are configureable fot he different i3 country markets.
The hardest issue to date is figuring where the HU-H nav system gets its configuration settings from.
Not asking about USB enterable files such as map updates.
Does the nav unit need a different software set for each country / region?
Does the car already have all files required for selection of the various country settings?
Does e-SYS contain files which may need to be loaded depending on an option / region change for the car?
Are there files which are not in e-SYS but need getting from BMW?
What I'm currently working on is my i3 imported from Japan. A similar situation exists for UK cars operating in this country.
I'm unable to purchase the local Australia / NZ maps download online from the website because of VIN zone mismatch.
Once this is fixed, I will need to get the nav HU-H to operate with the different country type map data files.
The car already displays local weather widgets etc. so i know Connected Drive is already working. The GPS knows the cars is 4,000km away from its last position but cannot plot a new route due to lack of route data.
The BMW dealer says they will get the VIN registration changeover done.
They cannot (or are not allowed to) get the nav maps to work, this is done for their customers cars by engaging a 3rd party company 500km away to come and do the car. like about 3 days and $800 to do the car.
I respect the company for what they do and their independent IP in doing this task, however I expect its nothing different to the way I have already got e-SYS working for my car and started coding the simple things.
If its all too difficult, I will just use a tablet for Nav as the live chargepoint info is probably better than Connected Drive can provide
It took me 5 hours to download and install onto a spare PC and another 5 hour day to hook up and alter the first coding settings, using all the info I could find on the various Bimmerpost etc. forums. OK taking it slow I dont want a bricked car...
I'm seeking help with how the cars various ECUs store data / config files and how to change these files.
So far I have listed some of the functions; if anyone can add to the knowledgebase that would be appreciated:
FA : factory order
VO : vehicle order coding - changes options globally without having to enter changes to each affected ECU
FDL : function data list - list of activ attributes within each ECU - FDL coding just changes individual ECU attributes by overwriting the VO coding
VCM : vehicle configuration management- (a) FA = vehicle order profile, VIN, options
(b) SVT = software variant table, lists ECU name, CAFD id, firmare but no coding parameters
(c) CAF
(d) CAFD = the processed CAF = need to know the CAFD id in order to load into FDL editor
(e) NCD = the net coded data - the compiled data ready to be activated using the FDL editor
I'd like to understand exactly which of the software and hardware / firmware systems are configureable fot he different i3 country markets.
The hardest issue to date is figuring where the HU-H nav system gets its configuration settings from.
Not asking about USB enterable files such as map updates.
Does the nav unit need a different software set for each country / region?
Does the car already have all files required for selection of the various country settings?
Does e-SYS contain files which may need to be loaded depending on an option / region change for the car?
Are there files which are not in e-SYS but need getting from BMW?
What I'm currently working on is my i3 imported from Japan. A similar situation exists for UK cars operating in this country.
I'm unable to purchase the local Australia / NZ maps download online from the website because of VIN zone mismatch.
Once this is fixed, I will need to get the nav HU-H to operate with the different country type map data files.
The car already displays local weather widgets etc. so i know Connected Drive is already working. The GPS knows the cars is 4,000km away from its last position but cannot plot a new route due to lack of route data.
The BMW dealer says they will get the VIN registration changeover done.
They cannot (or are not allowed to) get the nav maps to work, this is done for their customers cars by engaging a 3rd party company 500km away to come and do the car. like about 3 days and $800 to do the car.
I respect the company for what they do and their independent IP in doing this task, however I expect its nothing different to the way I have already got e-SYS working for my car and started coding the simple things.
If its all too difficult, I will just use a tablet for Nav as the live chargepoint info is probably better than Connected Drive can provide