Welcome to Bimmerfest -- The #1 Online Community for BMW related information! Please enjoy the discussion forums below and share your experiences with the 200,000 current, new and past BMW owners. The forums are broken out by car model and into other special interest sections such as BMW European Delivery and a special forum to voice your questions to the many BMW dealers on the site to assist our members!

I'm just saying that I kept getting the error and I thought to myself "what the heck, let me try going right into ESys and seeing if it will work". And it did, and it continues to. I've coded 5 cars already that way, so clearly it works. Yes, it's great to follow the steps, but when ZWG kept error-ing out on me, I just decided to charge ahead and it paid off.

@April1; Thanks. Keep the batch files coming. I started out not using ZWG_SEARCH as it does not work natively in Win7 64-Bit and serves no functional purpose. I now run it in the WinXP SP2 compatibility mode though, and it works fine that way, and while still completely unnecessary, it's just a nice confirmation that E-Sys is properly connected to the car. I've had instances where my E-net cable has wiggled loose on the the ODB II port, breaking my E-Sys connection, and having the ZWG_SEARCH window open, I can spot this.

You can use the manual procedure available on forums to install software on your laptop or follow automatic installation steps given below:

1. Create a folder on laptop or any external media and give any name such as BMWInstall. If you are creating folder BMWInstall on laptop, then you may need 45 GB of clear space as the installer will not move or delete any file from your laptop.
2. Copy folders 2_46.3 psdzdata and E-Sys_3.18.4 into BMWInstall.
3. Also copy Setup_3.18.4.v2.bat and EDIABAS.INI files into the same folder.
4. Double click on Setup_3.18.4.bat. It will install the complete software with correct settings to your laptop if the folders names are correct. Enter the password for E-Sys when asked. Installation time may vary from 1 hour to few hours. Don’t interrupt the process, let it run and finish. You are good to go now.

(Please download the files and remove .pdf at the end, that will make the file as bat file)

PS: Based on the feedback from Shawn and confirmation from Ray_S, I modified the Setup file to v2. (July 8, 2012)

You can use the manual procedure available on forums to install software on your laptop or follow automatic installation steps given below:

1. Create a folder on laptop or any external media and give any name such as BMWInstall. If you are creating folder BMWInstall on laptop, then you may need 45 GB of clear space as the installer will not move or delete any file from your laptop.
2. Copy folders 2_46.3 psdzdata and E-Sys_3.18.4 into BMWInstall.
3. Also copy Setup_3.18.4.bat and EDIABAS.INI files into the same folder.
4. Double click on Setup_3.18.4.bat. It will install the complete software with correct settings to your laptop if the folders names are correct. Enter the password for E-Sys when asked. Installation time may vary from 1 hour to few hours. Don’t interrupt the process, let it run and finish. You are good to go now.

(Please download the files and remove .pdf at the end, that will make these files as INI and bat files.)

Thanks for another useful batch file.

I have been told, and I have not yet confirmed it myself, that the SWE folder is actually only needed in "C:\ESysData\psdzdata\swe", and that it is not necessary to also have it in "C:\ESysData\SWE". Assuming this is true, and it's easy enough to test by just deleting the "C:\ESysData\SWE" folder, I would remove the following two lines from the batch file to both speed up the installation time and avoid needlessly occupying an additional 14Gb of hard drive space:

Thanks for this hint Shawn,I can confirm that the data only needs to reside under "C:\ESysData\psdzdata\swe".

Just tested succesfully!

I just stepped across this remark looking for install errors I made (software did not work and asked for missing files..) - and figured I only had the files movd into the other folder you mentioned below, thus I did not copy any of it as described as I did not want to duplicate, but only moved.
Now I moved it all back into the folder as mentioned above - and bingo, here we go.

After doing that and having my cable built today I also can claim first coding success - I coded the memory function for the Start/Stop button, so I don't need to disable it anymore in the future. GREAT!

I also had some connectivity issues earlier today - first was that I had misread the RJ45 pin, next step it still did not connect. I figured it's a Windows system (WIN7), so a re-boot always is good, and it helped. As the connection testing does not work as described under WIN7 I just test connectivity by using the good old "ipconfig" command in DOS window - it shows you if you get an IP assigned by the car... easy.

One failure on something I was hoping on, as I just started I won't give up yet:
Under DME options one can indeed select VMAX (speed limiter) values, but that max value in the pull-down offerd was 255 km/h, all other values offered were smaller ones probably for other countries outside Germany... that's a real fail, I was hoping to get an easy fix on the speed limiter.. will keep trying :-))))

Next to code will be the memory function for Drive Settings (Suspension and Gearbox), Sport,/ Comfort etc and the CLOSE button for the trunk from the inside door .

Happy coding...
Ray

PS: Can someone give me a short hint on what I need to do to download all my available coding options/files from the car so I can offline browse through them with the editiors/viewers?

PPS: Next time I'll connect the power supplies to car & laptop to provide as much time I need .. makes me a bit nervous to code w/o independent power supply..

Thanks for this hint Shawn,I can confirm that the data only needs to reside under "C:\ESysData\psdzdata\swe".

Just tested succesfully!

I just stepped across this remark looking for install errors I made (software did not work and asked for missing files..) - and figured I only had the files movd into the other folder you mentioned below, thus I did not copy any of it as described as I did not want to duplicate, but only moved.
Now I moved it all back into the folder as mentioned above - and bingo, here we go.

After doing that and having my cable built today I also can claim first coding success - I coded the memory function for the Start/Stop button, so I don't need to disable it anymore in the future. GREAT!

I also had some connectivity issues earlier today - first was that I had misread the RJ45 pin, next step it still did not connect. I figured it's a Windows system (WIN7), so a re-boot always is good, and it helped. As the connection testing does not work as described under WIN7 I just test connectivity by using the good old "ipconfig" command in DOS window - it shows you if you get an IP assigned by the car... easy.

One failure on something I was hoping on, as I just started I won't give up yet:
Under DME options one can indeed select VMAX (speed limiter) values, but that max value in the pull-down offerd was 255 km/h, all other values offered were smaller ones probably for other countries outside Germany... that's a real fail, I was hoping to get an easy fix on the speed limiter.. will keep trying :-))))

Next to code will be the memory function for Drive Settings (Suspension and Gearbox), Sport,/ Comfort etc and the CLOSE button for the trunk from the inside door .

Happy coding...
Ray

PS: Can someone give me a short hint on what I need to do to download all my available coding options/files from the car so I can offline browse through them with the editiors/viewers?

PPS: Next time I'll connect the power supplies to car & laptop to provide as much time I need .. makes me a bit nervous to code w/o independent power supply..

Ray; thank you for confirming this. I would like to update my 16 Step "E-Sys Installation Instructions", to remove Step 6 all together, and for reasons in addition to this; however, it's simply impractical now given the proliferation of the instructions. It's all over the place, in numerous E-Sys packages and as a standalone document. If it in fact did not work as written, rather than just wasting a few additional Gb of space, I would probably be more motivated in correcting it. That said, I think the batch file though should still be corrected.

For removing the Speed Limiter, please see and post any commnets or findings in this thread:

For working off-line, I just go out to the car, read all the ECU's I want, disconnect, and go in the house and peruse the CAFD Entries at my leisure. You can however, read them off the local drive once they have been initially read using the CAF Viewer. Read this document:

As for the charger, with the exception of the DME Module, I just FDL Code with the Car on, so I don't worry about the battery. It's too damn hot in H-Town to code without AC . If I was flashing a module though, I would have it turned off and hooked up to a charger.

Thanks Shawn and Ray_S. I have modified my installer file in my post above to implement the changes. Its so wonderful to learn that one step follows other automatically. I made the installer based on the old installer instructions floated by Shawn, Shawn looked at my installer and felt the need to make changes, Ray_S stepped up and verified the suggestions, April1 (myself) then modified the installer. Great Team work.

Thanks Shawn and Ray_S. I have modified my installer file in my post above to implement the changes. Its so wonderful to learn that one step follows other automatically. I made the installer based on the old installer instructions floated by Shawn, Shawn looked at my installer and felt the need to make changes, Ray_S stepped up and verified the suggestions, April1 (myself) then modified the installer. Great Team work.

I think Rterath is asking about the updated PSDZDATA files (46.5 or 46.6) that seems to be needed in order to code newer 2012 F series chassis. I'm in the same boat and cannot seem to find the newer DATA files.

Sorry but I can't upload 15GB of data... And I'm sure I have the same version like you from rapidshare.

Have not tested HU_CIC yet, only memory for start/stopp..

..and just checked, I-Step Level is F010-12-03-512, thus one level higher than in the attached list. I suppose I cannot code some modules either. will keep posted on progress...

Here we go, already was able to test:

Although the level is one level higher than in the list above - no problems reading and coding several ECus.

I can confirm DME, CAS, HU_CIC, and coded e.g. Trunk button closes, speed limit on DVDs, etc
I can also confrm adding to FA works, I added 7ME, likely without any impact on the speed lmiter but just for fun and testing.

Now, that puzzled me a bit, so I just checked the psdzdata/mainseries/F10 directory.... And guess what, the directory contained is named F10_1203_512... So it seems to be the latest dataset and it's indeed e level my car has. Thus this level was not yet included in the list above...

Let me check tomorrow if I can find the source again on rapidshare, but I'm pretty sure it was named somewhere around here in the forum in an embedded document..

..and just checked, I-Step Level is F010-12-03-512, thus one level higher than in the attached list. I suppose I cannot code some modules either. will keep posted on progress...

Here we go, already was able to test:

Although the level is one level higher than in the list above - no problems reading and coding several ECus.

I can confirm DME, CAS, HU_CIC, and coded e.g. Trunk button closes, speed limit on DVDs, etc
I can also confrm adding to FA works, I added 7ME, likely without any impact on the speed lmiter but just for fun and testing.

Now, that puzzled me a bit, so I just checked the psdzdata/mainseries/F10 directory.... And guess what, the directory contained is named F10_1203_512... So it seems to be the latest dataset and it's indeed e level my car has. Thus this level was not yet included in the list above...

Let me check tomorrow if I can find the source again on rapidshare, but I'm pretty sure it was named somewhere around here in the forum in an embedded document..

12-03-511 is psdz 46.1 and is the last listed, but the file is not new so doesn't contain the latest..

It is likely you got 46.3 from rapidshare so you have support for a higher stepping

..and just checked, I-Step Level is F010-12-03-512, thus one level higher than in the attached list. I suppose I cannot code some modules either. will keep posted on progress...

Here we go, already was able to test:

Although the level is one level higher than in the list above - no problems reading and coding several ECus.

I can confirm DME, CAS, HU_CIC, and coded e.g. Trunk button closes, speed limit on DVDs, etc
I can also confrm adding to FA works, I added 7ME, likely without any impact on the speed lmiter but just for fun and testing.

Now, that puzzled me a bit, so I just checked the psdzdata/mainseries/F10 directory.... And guess what, the directory contained is named F10_1203_512... So it seems to be the latest dataset and it's indeed e level my car has. Thus this level was not yet included in the list above...

Let me check tomorrow if I can find the source again on rapidshare, but I'm pretty sure it was named somewhere around here in the forum in an embedded document..

Quote:

Originally Posted by miotoo

12-03-511 is psdz 46.1 and is the last listed, but the file is not new so doesn't contain the latest..

It is likely you got 46.3 from rapidshare so you have support for a higher stepping

Ok, so i just checked and i have the same I-Step Level as Ray_S. I attached an image of my I-Step levels. For some reason i cannot read the HU_CIC module with 46.3 DATA files. I have attached the error i get when i try to read the HU_CIC. It seems it cannot find the CAFD file needed, so i was assuming it is a CAFD file in the newer version PSDZDATA? Ray_S, can you check what CAFD file is read in your HU_CIC module please? If it matches mine, then you might have a newer PSDZDATA version (46.5 or 46.6), if your CAFD file is different, that would narrow things down a bit.... Thanks!!