Well I received my cable today and did some coding already. If you're interested in coding yourself, read on
This DIY is intended for F-series BMW's alone. I'm sorry but I just received word the E-series work in a complete different way that the F-series. The E-series us INPA and NCS Expert to do their coding. This requires a different cable as well. The E-series needs to communicate with a CAN network, where as we are talking across a TCP/IP enabled network with the F-series. For the E-series, please see this thread: http://www.e90post.com/forums/showthread.php?t=451145 and in particular, this post: http://www.e90post.com/forums/showpo...8&postcount=15
What you need
- An ENET cable.
- E-Sys program, datafiles, token and PIN
- A laptop (a PC would work too but it wouldn't be comfortable in most cases lol)
Now, you could go overboard and get a power supply cable for constant supply to your car but if you minimize your coding sessions to 30 minutes and have your car running for at least 15 minutes in between, it should go a long way. Also, it's advisable to do the browsing in the code offline and only do the coding while being in your car (more about this later on).
There are basically two ways to get the ENET cable. You can buy a complete cable, or you can simply build one.
If you are not interested in building one and want to spend a little bit more money to get a working cable, then this is a site that has been confirmed working by some of our F10 friends: http://codecard.lt/electronics/tools.../prod_651.html
..I wouldn't recommend other sites, although they may work, problem is that they have not been confirmed working yet.
-> You can also buy a cable from ImSW1
, a fellow coder and he's also the one from who I, indirectly, received my own cable. His cables are great. He builds and ships them for $25 USD. Usually, after he receives payment, he can have the cable ship the next day and arrive with you only two days later (that's for the 48 contiguous states, Alaska and Hawaii might take a few days longer due to the distance (cost stays the same due to it being shipped flat rate with USPS)).
The other way is to build a cable yourself. Cost for this would probably range anywhere between 10 to 20 bucks. You will need to solder a bit but it's nothing too serious if you follow the instructions to the letter.
To build your own cable, you will need the following:
- OBD2 or OBDII connector
- RJ-45 cable and connector
- 510 ohm .25 watt resistor
The schematics of the official BMW cable can be found below in the attachments and how to solder your cable can be seen in the photos directly below (thanks to Sean [ImSW1]).
An even more comprehensive DIY for the ENET cable can now also be found in the attachments: http://www.f30post.com/forums/attach...1&d=1339310785
If you cannot find the OBD2 connector, please look on ebay. A lot of the connectors are being sold there.
E-Sys program, datafiles and such
I currently work with E-Sys v3.18.4 in combination with the v46.3 datafiles, which work like a charm for me. I have read reports about newer builds but also read about a lot of install problems and such with those builds so it seems best to stick with these for now.
You can find the link to E-Sys in this text file:
*** Link removed, see below ***
For the datafiles, please download this text file for all links (24 in total):
*** Link removed, see below ***
Little advice regarding the datafiles: It is over 10GB in total and rapidshare is VERY slow. Unless you like to spend hours and hours to download it all, I recommend buying a one-time PRO account for 10 bucks. Most of the people (including me) did this and it makes a LOT of different (up 3 hrs versus 10 minutes per file).
For installation on how to install these files, please the attached PDF file called "E-Sys Installation.pdf"
Programming Versions vs. Vehicle Data Status
Here is a worksheet
that covers what data set (psdzdata) lines up with what chassis code (for example, the F30 lines up with the F020 datasets).
Please see the 'E-Sys - Getting Started' PDF files below at the attached files to get started with coding. These are the same files I used the first time to code and should be self explanatory, just follow everything like they state there and you'll be ok
(of course, where they talk about the F10/F010, please change that into F30/F020 respectively).
Download the E-Sys - MacOSX installation and configuration.pdf
Making a Back Up
It's quite easy to make a backup of the CAF files from your car. Basically, as soon as you start reading the CAF files from your car, the E-Sys program automatically stores the files into "C:\ESysData\CAF". All you basically need to do is to copy these files and store them somewhere safe. The best is to make a new copy (and keep the old!) every time you want to code, this way you always have a copy of the last working version (just in case you break something lol).
Here are the instructions that were given to me the first time around:
1) Connect the Laptop to Car and hit the Connect synbol on the top left.
2) Pop up will appear , now select F20 not "F020 direct" and click connect (You should see your car VIN in this pop if not, close the pop up.. wait for few seconds and repeat the step 2 )
3) If step 2 is successfull you will see a small po up telling the same ...close that pop up (You will see these pop ups in most of the steps just read and close).
4) Now esys should switch to coding mode (if it didnt then go to expert mode and click on coding icon on the left vertical pane)
5) Now you will be in coding prespective... Click on Read button under the VO pane.
6) After step 6 you will see FA appearing in the VO pane
7) Now Click on Read VCM or Read button under VCM pane....you will find it it will be on your Right hand-Center
8) Once you click that you will see all the ECU's populated below VO pane and left of VCM pane
9) Now expand the ECU's... all most all ECU's will have a file starting with CAF (With green indicator) right click on the CAF file and select Read coding data
10) You have to do the step for all the ECU's. Some ECU's will not have CAF's, you can ignore them.
11) Easier way to perform step 9 and 10 : on your left hand side bottom there will be a drop down which should show "ALL" change that to "CAF" and you should see all the CAF's in the ECU pane now you dont have to dig in each ECU to find the CAF.
Note: You can use Ctrl+Click to select more than one CAF and then read coding data... Dont click on all the CAF's just do four or five at at time max.
12) Once you have complete reading all the CAF's go to c:/esydata/CAF . You will see the folder CAF has all the .ncd files generated.
Once you have done the above, simply copy those .ncd files and store them somewhere safe.
You can download the F30 cheat sheet with things I have done so far below at the attached files. The cheat sheet is called "F30_Cheat_Sheet_XXXXXXXX.pdf", where the X's are is basically the date I updated the cheat sheet (year,month,day).
Please also see a more complete cheat sheet for the F10 below at the attached files to get a general idea of it all.
Please note that the F10 coding is slightly off from the F30, meaning some of the functions are named different or located in different named modules and, of course, some things are not available to the F30 (such as the automated trunk closing). Just use the F10 cheat sheet for the F30 to get an idea, to see what might be possible and such.
These things have been coded and confirmed working by me so far:
- Video in Motion
- Turned the Seatbelt Gong off
- Side View Cameras on at all speeds
- Change DVD region code
- Remove disclaimer
- Remove PDC + cam disclaimer
- Tire pressure + temperature in TPMS
- Mirrors close by pressing doorknob (comfort access only)
- Mirrors open automatically when closed with comfort access
- Disable A.S.S. by default (can still be enabled but starts with setting 'off')
- Remember last setting of A.S.S. (works only when not disabled by default)
- Change ringtones
- More to come (or already there, check the cheat sheet!)
Little note: after coding someone else's F30 tonight (6/7/12), I noticed that some of the modules might have a slightly different name. The functions were still named the same, just the module name was a little bit off.
I added some more files that I just picked up elsewhere that might be of help:
- E-Sys Editors and Viewers.pdf
(this will help with backing up, restoring and reading the CAF files).
- E-Sys_Coding - VCM_UserManual_v1.4.PDF
An E-Sys usermanual. It's a bit dated but still pretty good for overall use
Anyways, bottom line is that the coding for the F series works. Instead of paying 155-170 USD for Video in Motion, it only cost me the cost for a cable (which you can make yourself, the cost for that could be anywhere from 7-20 dollar).
(For those living in Hawaii who need help coding their F10 or F30, or help with the install, just send me a PM and perhaps I can help you out (I wont charge but you will have to come to me, and everything I do is done at your own risk, of course.)).
coding is pretty simple to do, but it's also very simple to brick your car if you make mistakes or by other unexpected circumstances.. everything you do on your car with coding, like with everything else, is all done at your own risk. Also please keep in mind that I am doing this for educational purposes only and that I am not making any money out of it.
Credit and thanks goes out to Shawn
. They have helped me in many ways to get this far! Without them, I wouldn't be able to show you guys all this
I'm sorry guys, due to some recent developments I figured it would be safer to remove the actual links to both e-sys and the datafiles from this post.