BimmerBoost Beta Flash 188.8.131.52
1a) Set your JB4 to map 0 first to disable it.
1b) Run installer package to install BimmerBoost flash application on laptop.
2) Plug Bavarian Technic cable in to OBDII port.
3) Turn on ignition. This means all lights showing in dash including SES light.
4) Turn off your radio, climate control, lights, and any other unnecessary accessories to avoid draining your battery.
5) Connect USB to laptop.
6) Open BB flash program and select "ID ECU".
7) If properly connected you should see the software fields fill in. The most common files are IJE0S and 18A0S. This ID field will be used later to download the proper TunerPro XDF file to modify your DME. DME Voltage should show. If you do not see DME voltage there is an issue communicating with your DME. Do not continue.
8) Select "READ ECU" to start the read process. The software will default the name to your VIN.org. Reading the BIN out will take approximately 70 minutes. In some cases a battery charger should be connected before reading.
9) Once reading is complete save a copy of this original file in a safe place. This is your only DME backup. Loose this file or accidentally modify it and you'll have a headache later. Note while it is saved with the extension ORG it is actually a BIN file.
10) Download the appropriate tuned BIN below for your DME type, mods, fuel, intended usage, etc.
11a) Note for 2007 KLINE models. You MUST have a 10amp+ battery charger connected for a full write. The gateway between the OBDII port and DME will shut down if it drops below 11.5v which is common during a full write without a charger. When this happens you will get authentication failure messages, file mismatch errors during and after write, etc.
11) Copy the modified BIN over to your laptop and repeat steps 2-6. Once connection is verified select "WRITE ECU" and select the modified BIN. The write process will begin. The first write takes ~15 minutes and subsequent writes will take ~2 minutes. Expect the fuel pump to run and all error lights to appear in dash and NAV screen while flashing. The most common write failure is due to a low or old battery so a charger is highly suggested for full writes.
12) After writing is complete wait 15 seconds and then remove the key from the ignition. Put the key back in the ignition and start the car. Programming is now complete. iDrive cars will experience a SES light on until the car has been restarted a few times. This is normal and will be corrected in future builds.
13) Note with the JB4 now that fueling has been transferred over to the flash you'll need to set your AFR & CPS values in the JB4 interface all to 0. You should also select "G5 ISO w/ BMS flash" under settings.
1) This software requires a Bavarian Technic cable. The software does not use the BT licensing so it does not matter whether or not the BT cable is VIN locked and it will not consume a VIN within the cable. This software DOES NOT work with other USB->CAN cables such as those used for INPA & coding.
2) This is open source software and no vendor support is provided. As such if you run in to a problem or need help you'll have to seek assistance on BimmerBoost. No flash support will be provided by the tuners who have written flash maps so do not attempt to contact them for assistance.
3) It would be wise to only flash the car at home in your garage so if something does go wrong requiring you to seek support you're not stranded during that process.
4) Flashing your DME involves some risk including the risk of bricking the DME. The way this software works chances of bricking your DME are close to zero but understand some risk exists with any flashing product. If you did manage to brick your DME you would need to remove it and have it bench flashed somewhere or do a full software write using an INPA system.
5) If the car has been previously flashed (with say Dinan, GIAC, etc) you may run in to problems as these tuners delete the commands used to read out your BIN. Consult the BB Open Source community for additional information.
6) The AT back end flash maps are programmed for low factory load and are designed to improve post shift timing advance for high boost automatic cars. One drawback with these maps is due to the lower factory load targets dialing in your fuel trims may require more effort. You may need to raise or lower the bank1&2 fuel scalar to get your trims neutral under full boost.
Where do I get flash maps?
With regard to flash maps we will provide our popular JB4 back end flash maps which can be loaded for free using this software and any BT cable. The JB4 back end flash maps work with the JB4 piggyback to shift fueling, timing, VANOS, and other functions over to the flash side while allowing the JB4 to retain its superior absolute boost control, on the fly map changes, in dash gauges, shift light, auto learning/self tuning, gear dependent boost control, data logging, methanol control, 2STEP/NLS, etc. It's simply the best of both worlds. And since the back end flash is now virtually free we've also released pump gas back end flash maps as well. In the coming months we expect to do a lot of flash map development exploring areas of tuning previously not possible running either piggyback system or flash tune alone.
Our canned flash maps are attached at the end of this post. After taking a backup of your original file upload just write the appropriate flash map. Currently maps are not available for the 335is or 1M but all other DME versions should work on one of the two software versions below. Most 2008 and earlier cars are MSD80 and take the I8A0S BIN, while most 2009 and newer cars are MSD81 and take the IJE0S BIN. If your 2007-2008 models has an IJE0S software version though be sure to upload the IJE0S file. Loading the wrong file for the DME type will result in a "PAF Mismatch Error" after writing and you'll need to rewrite the correct file.
Something went wrong, what do I do now?
I'll use this area for notes on common problems/mistakes and how to recover from them.
1) The most common problem is an "authentication error" during a write. The write process happens in three stages so if it fails at any one of these stages the DME will be left without all of its firmware and unable to operate the vehicle. The most common reason for failure is low battery voltage. So if you experience this ensure you have a battery charger on both the vehicle and the laptop and try again. We suggest at least a 30-40amp battery charger. In some cases the DME can be left in a state that is unable to accept a write command and if this happens just disconnect the negative battery cable for a minute to reset it. In short your only solution here is to keep trying until you get it to work. Sometimes the issue is laptop related and trying another laptop resolves it.
2) The second most common problem is the write completes successfully but you receive a DAF/PAF mismatch error. BMS is pioneering a method to allow any MSD81 to load a BIN file from any other MSD81 without issue. But this is still a somewhat experimental process. If you load a canned BIN and experience this sort of an error then load back your original BIN to get the car running again and using TunerPro and the proper XDF file for your software version go through your original BIN to make the same various table edits BMS has made in their modified BIN. This will effectively port the tuning changes over to your original BIN. Be sure to save it as .BIN so you don't overwrite your original .ORG. This error can also occur if you attempt to write an MSD80 file to an MSD81 DME and vice versa.
3) If you load a poorly modified BIN the car may crank without starting. In this case write a known good BIN to resolve it.