Almaretto and Shawn: do you know whether NGHB can be coded on the 2019 G01? I read about success stories on 2018 model year G01s, but every one of my attempts on my 2019 X3 with production date of July 2018 (Time Criteria = 0718) ended up in incorrect operation. I am leaning toward the conclusion that BMW changed the hardware in the 2019 model year and my headlights are no longer capable of NGHB.

 

I never code GFHB in any car, because as far as I am concerned, it is has never been 100% correct in any North American Car. If solution cannot be just VO Coded, and requires subsequent FDL Coding, it is not an OEM solution. Just my $0.02.

 

Point taken. Certainly a prudent approach.

 

Hi.
I have E-sys 3.28.1 with launcher pro 2.8.2 and Psdzdata v63.3 lite.
When I try to code something in the car, I don't see the folder names, only dots. I use F020.

If I try PSdZData_Lite_v4.21.32, I cannot connect to car, as I don't have any option in Target (I-level).

Can you help me with this?

Thank you.

 

If the "Open Connection" window under "Target" is empty (no targets), verify the following:

1. That the "psdzdata" folder is installed properly (From the PSdZData_Lite or PSdZData_Full extraction, copy the "psdzdata" folder to "C:\Data\" (i.e. "C:\Data\psdzdata")
   
2. That the psdzdata chassis folders each have an empty "dist" folder. Make sure that there is an empty "dist" folder in each of the psdzdata chassis folders, and if missing, create as needed, e.g.:
   • C:\Data\psdzdata\mainseries\F001\F001_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\F010\F010_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\F020\F020_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\F025\F025_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\F056\F056_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\I001\I001_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\K001\K001_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\KE01\KE01_xx_xx_xxx\odx\dist
   • C:\Data\psdzdata\mainseries\RR01\RR01_xx_xx_xxx\odx\dist
3. The the E-Sys "Options" => "Settings" => "Directories => Data: path" is set properly (e.g. "C:\Data")

 

Yes. Esys Launcher PRO 2.8.2.162. See the photo.

 

Can be Java memory issue or can be that CAFD is just not mapped by E-Sys Launcher PRO 2.x, and newer 3.x is needed.

 

Java I have 7 version x64 and I don't know from where to get another launcher.

Thank you, anyway.

 

Java version is not issue, it has to do with limited Java memory.

Launcher PRO 3.x is only available from developer TokenMaster (fxxtokenmaster@gmail.com).

 

@Shawn,

New to VO coding. I've just used

Esys 3.28.1
Esys Pro Launcher with working tokenmaster
PSdZData_Lite_v4.21.32
I-level F020-18-11-520

Connection via Vin (presumably this correctly identifies the car type rather than selection from the list you are presented with as I cannot identify FO20-18-11-520 using this PSdZData version?)

So assuming I've not cocked up the above and following your instructions on how to VO code found here in this forum I have successfully added 6CP and 6NS to the VO list and checked those entries are loaded to the car and saved.

With specific reference to 6CP should I see any difference in the Idrive interface given this is just Carplay Prep prior to loading any new FSC and what difference should I see having coded 6NS (EBT) to the interface?

 

You will not see anything in iDrive by just VO Coding 6CP. CarPlay requires FSC Code and FDL Coding.

As for 6NS, you should have Enhanced Bluetooth, so BTAS Streaming and support for 2nd Paired Phone and Office.

 

@anyone

Can 3D maps be coded by Esys if so what is the code?

I have the 3D map check box in Map Options in ID6 but checking it doesn't give me 3D Maps

Current Maps = Europe Way 2019-3 H1835E1R

TIA

 

@anyone

Can 3D maps be coded by Esys if so what is the code?

I have the 3D map check box in Map Options in ID6 but checking it doesn't give me 3D Maps

Current Maps = Europe Way 2019-3 H1835E1R

TIA

This is not a Coding issue. Map 3D View requires many things to work:

1) 3D Map checkbox must be checked
2) Map View must be in Perspective View
3) Map Zoom must be zoomed in to certain range
4) Must be in a major downtown area that has 3D Map rendering
5) Traffic situation/grey map can NOT be checked

 

Hello--

I've been waiting about a week to hear back for the Launcher Pro 3.X access. How long does this access typically take?

Apologies if this has been said or if I am posting this in the wrong location.

 

In my case, it took a little over 4 months.

 

What is the cutoff for 2.8? I'm going to code a 2017 M240i (simple stuff like mirrors folding, no start up beeps...) and don't know if I can use the free version? Also does anyone know if Tokenmaster is responding to emails right now? I donated a few years ago and ended up waiting a bit for a token and am wondering what people's current wait times are.

 

You can use E-Sys Launcher PRO 2.8.2 for free, at least until April 2020 when it expires:
http://tokenmaster.blogspot.com/2019/05/e-sys-launcher-pro-282.html

That said though, the CAFD Mapping in 2.8.2 is becoming outdated, and not as current as the CAFD Mapping in 3.0, so while you may be able to read an ECU, it may still appear Trimmed (...), as in no Narrative Descriptions, making it impossible to FDL Code such an ECU.

 

Hi Shawn, few questions:
1. I have a G20 that was upgraded to 11/2019.55 this week. I***8217;m using Launcher Pro w/Esys 3.33.4 and PSdZData_Lite_v4.21.32. The I-Step (shpm) last octet version is slightly higher than the I-Step (target) version (this is just example version as I forgot to note the exact version: shpm 19-07-553 vs target 19-07-530.) Would the slight version difference pose an issue when coding? The reason I ask is I got errors when coding as noted in #2.
2. Do you recommend coding everything you want for a ECU then choosing ***8220;Code NCD***8221;? or code for all ECUs then choose ***8220;Code NCD***8221;? not sure if the latter would Code NCD for all ECU CAFD files that were modified or just the last one selected. Reason I asked is that I started with coding BDC_BODY3 then after Code NCD I started to get ***8220;wiper, tire pressure, rear seat belt***8221; etc errors on my dashboard. I was hoping the errors would go away once I completed each of ECU coding but I screwed up as noted in #3.
3. Do you recommend coding everything (excluding DME ECU) with the Engine ON or OFF? Because I had Code NCD ***8220;Enable Auto Start Stop Memory***8221; (DME_BAC2\TCM_MSA_MEMORY) with the Engine ON and my car crapped out. The Engine turned OFF, gave me Chassis Errors, stated my Vehicle Key could not be found, etc, the engine just would not start. Took me an hour and luckily since I saved my stock FA & SVT settings, I was able to revert to original stock settings and now my engine starts. Hopefully my experience with coding DME ECU will help others not to make the same mistake.
I appreciate your time. Thanks, Mo

 

Hi Shawn, few questions:
1. I have a G20 that was upgraded to 11/2019.55 this week. I'm using Launcher Pro w/Esys 3.33.4 and PSdZData_Lite_v4.21.32. The I-Step (shpm) last octet version is slightly higher than the I-Step (target) version (this is just example version as I forgot to note the exact version: shpm 19-07-553 vs target 19-07-530.) Would the slight version difference pose an issue when coding? The reason I ask is I got errors when coding as noted in #2.
2. Do you recommend coding everything you want for a ECU then choosing "Code NCD"? or code for all ECUs then choose "Code NCD"? not sure if the latter would Code NCD for all ECU CAFD files that were modified or just the last one selected. Reason I asked is that I started with coding BDC_BODY3 then after Code NCD I started to get "wiper, tire pressure, rear seat belt" etc errors on my dashboard. I was hoping the errors would go away once I completed each of ECU coding but I screwed up as noted in #3.
3. Do you recommend coding everything (excluding DME ECU) with the Engine ON or OFF? Because I had Code NCD "Enable Auto Start Stop Memory" (DME_BAC2\TCM_MSA_MEMORY) with the Engine ON and my car crapped out. The Engine turned OFF, gave me Chassis Errors, stated my Vehicle Key could not be found, etc, the engine just would not start. Took me an hour and luckily since I saved my stock FA & SVT settings, I was able to revert to original stock settings and now my engine starts. Hopefully my experience with coding DME ECU will help others not to make the same mistake.
I appreciate your time. Thanks, Mo

1. If error is "Missing CAFD", then yes.

2. I code one ECO at a time, making all FDL changes I need, then write them to ECU at one time, then move on ot the next ECU.

3. I always code car with MOTOR Running, with exception of DME / DDE.

 

Hi all sorry to post here but my Esys Pro token has now expired.. tried to contact tokenmaster to renew but no joy ***9785;***65039;.. anyone know how I can get up and running again?
Thanks in advance


Sent from my iPhone using Bimmerfest

 

Hi all sorry to post here but my Esys Pro token has now expired.. tried to contact tokenmaster to renew but no joy ***9785;***65039;.. anyone know how I can get up and running again?
Thanks in advance

Sent from my iPhone using Bimmerfest

Only via email to fxxtokenmaster@gmail.com.

You can use E-Sys Launcher PRO 2.8.2 for free, at least until April 2020 when it expires:
http://tokenmaster.blogspot.com/2019/05/e-sys-launcher-pro-282.html

 

Hi all sorry to post here but my Esys Pro token has now expired.. tried to contact tokenmaster to renew but no joy ***9785;***65039;.. anyone know how I can get up and running again?
Thanks in advance

Sent from my iPhone using Bimmerfest mobile app

 

Hi I am having problems with my first time coding. I use Esys launcher pro 2.8.2. Esys 3.27.1. PSdZ data lite 4.21.32.7. but when I connect and try to VO code. When I tried to code one of 4 ECU it crashed. Would you mind to correct me if I did something wrong. I am adding 2VB option Thanks in advance.

 

Paid for Code, When will it arrive?

I sent the tokenmaster a paypal and it should have cleared 2 days ago. Any Advice?

 

I sent the tokenmaster a paypal and it should have cleared 2 days ago. Any Advice?

Email him at fxxtokenmaster@gmail.com.

 

hi shawn do you have the newest NCD.mine is 5.5.203,but the GXX can't be analysised.how about yours?dear

 

No, TokenMaster has not released a newer version yet.

You can easily compare .NCD files by reading and saving them in E-Sys as FWL files and then using Beyond Compare or WinMerge to see the differences.

 

Generally speaking it does not support newer CAFD files. NCD CAFD Tool is quite old and obsolete.

That's not entirely true. First of all, there is a newer version but it does not seem publicly available and second one guy has found a way to make newer mappings work with it (and Launcher Pro 2.8.2) but as so often in this area he will not share his knowledge.

https://www.carcodingnord.de/blog

 

Just curious - is anybody getting any response from TokenMaster via email? I completed the process and engaged him via email several days back and hadn't yet received a response. I wasn't too concerned, but looking at this thread, it seems like a lot of people are not getting responses.

 

Very few. He comes and goes like the wind. Expect long delay in response.

As an alternative, you can use E-SysX:

Info@esysx.com
http://esysx.com/

 

I have emailed him once on 2/11 when I made the donation, then realized that I shouldn't have included any text in the paypal I sent, then waited 10 days for it to clear, then emailed again on the 2/17 &2/19. No response as of yet.

 

When will the wind blow in the Tokenmaster?



Well into March with no reply, Please advise.

 

Ia this the thread to ask questiosn about best BMW/Mini-specific scan tools for Fxx chassis?

Mine is F30, I read other festers use Carly, and a few recommended i910.

There are fragmented threads and posts about various tools but nothing concrete.

My needs are battery registration, and read and reset fault codes, run ABS/DSC tests, ignition coil voltages, etc, etc.

Is there a thread that compares all the popular scan tools?

The full-blown coding setup should achieve all the above(and much more) but my goal is a simple OBDII solution. Any suggestion?

 

Ia this the thread to ask questiosn about best BMW/Mini-specific scan tools for Fxx chassis?

Mine is F30, I read other festers use Carly, and a few recommended i910.

There are fragmented threads and posts about various tools but nothing concrete.

My needs are battery registration, and read and reset fault codes, run ABS/DSC tests, ignition coil voltages, etc, etc.

Is there a thread that compares all the popular scan tools?

The full-blown coding setup should achieve all the above(and much more) but my goal is a simple OBDII solution. Any suggestion?

No, this thread is for Coding and Programming software. I have no idea on Scan Tools.

 

Ia this the thread to ask questions about best BMW/Mini-specific scan tools for Fxx chassis?

Mine is F30, I read other festers use Carly, and a few recommended i910.

There are fragmented threads and posts about various tools but nothing concrete.

My needs are battery registration, read and reset fault codes, run ABS/DSC tests, ignition coil voltages, etc, etc.

Is there a thread that compares all the popular scan tools?

The full-blown coding setup should achieve all the above(and much more) but my goal is a simple OBDII solution. Any suggestion?

 

I'll purchase a token system for E-Sys but which supplier is best alternative for G30 for pain free coding even after ISTA updates?

E-SysX offers lifetime subscription where ProLauncher offers only 2.5years as I understand :confused2 Also I've heard that there are some problems from time to time to activate tokens

Which one should I purchase?


Also my G30's production ISTA is S15A-17-07-503 and current ISTA is S15A-19-1-534. Which version of E-SYS and PSdZData should I use to code my vehicle? And do I need 64bit version?

For further updates that may be done by dealer which token system would be more suitable for further update support?

 

I'll purchase a token system for E-Sys but which supplier is best alternative for G30 for pain free coding even after ISTA updates?

E-SysX offers lifetime subscription where ProLauncher offers only 2.5years as I understand :confused2 Also I've heard that there are some problems from time to time to activate tokens

Which one should I purchase?

Also my G30's production ISTA is S15A-17-07-503 and current ISTA is S15A-19-1-534. Which version of E-SYS and PSdZData should I use to code my vehicle? And do I need 64bit version?

For further updates that may be done by dealer which token system would be more suitable for further update support?

You likely cant get response from TokenMaster leaving E-SysX as your only real option.

 

Thanks Shawn I'll email him now also I'll send a reminder to EsysX :angel::thumbup:

 

Sill no response from esysx :tsk:

Is this their official website?: http://esysx.com/

Also will the license be for ISTA version on car or the ISTA version used in the activation phase (latest PSdZData loaded on the computer)? Or the E-Sys version?

They don't support version 3.33.4. Will there be any problems if I use 3.27.1 on my G30 with latest ISTA? Because E-Sys isn't reading 1 ECU under BDCbody

Also CAFD Tool 0.5.2 don't read any of my CAFD files (maybe I don't have a token that's why)???

 

Yes, that's it.

Just use one of the supported E-Sys versions. There is nothing special or better about 3.33.4.

ISTA has no affect on E-Sys installation.

CAFD Tool 0.5.2 is ancient. CAFD Mapping Database is very old.

 

my esys is 3.34 the psdzdata is 19-11-540. all cars can been coding

 

3.34? or 3.33.4? I've just purchased EsysX and it does not support versions later than 3.33 unfortunately 3.33 is also not listed in here so I don't know where to download E-Sys except the link in this forum. Will EsysX provide links?

 

I use EsysX with E-Sys 3.27.1 to code my 2019 G01 without any problems. I don't think you need 3.33.4.

 

Anyway I've uninstalled 3.27.1 and installed 3.33.4 and replaced the Java folder with JRE8 (Pro launcher needed that I assume also EsysX would need it). But I liked the 3.27.1 better even they look like the same but 3.27.1 has a better resolution at my laptop somehow :dunno: