Greetings all,
I bought a 2008 135i in December and after a very interesting baseline dyno test (it produced 250kW at the wheels; and I thought I'd bought a stock car), I wanted to install the MHD software so I could make use of the data logging package as the car was producing lean AFRs at low rpm.
Summary:
I tried to complete the MHD first write and it failed part way through. After this I couldn't flash back to stock using the backup I had created, and I couldn't flash to stage 0, and the car would crank but not start. Advice from MHD was that the ignition wasn't on properly for the initial flash (the fuel level should show on the display, which I have found only happens after pressing the start button twice after the key is inserted), and the backup was corrupt. I bought a better battery charger (25A), removed the backup from the phone and stage 0 flashed successfully. The car now starts and runs without fault (though I can't reliably scan for codes - more on that in Aftermath).
The cause of this may have been a tired battery and a low capacity battery charger (according to other posts it should be capable of producing over 20A).
I thought it might be helpful for others to write out what happened, and how it was rectified.
Setup:- Android device: Samsung Galaxy S9
- Android version: 8.0.0
- K+DCan cable: BimmerGeeks ProCable
- OTG Adapter: Samsung (came with phone)
- Battery charger: first one used was 5A, second one used was 25A
Sequence of events:- Connected the battery charger (5A)
- Connected the K+DCan cable to the OBD2 port
- Plugged the K+DCan cable in to the phone via the OTG adapter
- Turned on the ignition
- Checked the connection several times by scanning the codes, going to history, going back to see that the connection was stable
- Went to the store and bought the base software and the logging package
- Went in to flight mode
- Completed a backup
- Started a stage 0 flash. Seemed to be going ok so I went to do something else
- After about 10 minutes I heard a noise, went in and found the windscreen wipers on and a write fail message on the phone screen.
- Attempted to connect to the car by scanning codes again - couldn't read codes - specifically said "Connected" at the top of the screen, and "Cannot retrieve error codes" below the buttons.
- Turned off the ignition, then back on, and tried to communicate again but it wouldn't
- Tried to start the car - it would crank but not start.
- Tried to flash the stock tune - this went all the way through to 100%, then displayed a message saying "Failed to write to DME. DME Status: DAF Signature verification not carried out".
- Went inside & looked up a forum which said I needed a higher capacity battery charger and I should disconnect the battery for 30 minutes then try again.
- Disconnected the battery for 30 minutes
- Connected the battery again
- Tried to start the car again - no change - cranks but doesn't start
- Disconnected the battery again, for around 45 minutes.
- Went and bought a 25A battery charger, then connected it.
- Reconnected the battery again
- Tried to flash both stock and stage 0 maps - the same effect. Gets to 100 %, then displays the same message.
- Tried to communicate again using the code scanner - same effect.
Advice from MHD:
After this I wrote to Momir and Martial at MHD for advice with the description above. Momir wrote back to me with the following:
1. if the windshield wiper go on then ignition is not on properly (the fuel gauge must show the actual fuel level, key in, press start button)
2. your backup is not good (corrupted), please delete it from the MHD folder on your device (a backup is not needed, mhd has all stock files built in)
After these steps just flash stage 0 and you should be good.
I also called some Melbourne tuning shops for advice. Southern BM were the most helpful, advising that the battery needs to supply 13.5 volts to the DCM at all times during the charging process. Evolve Technik were happy to have a look at the car to help with resolution. Auto Racing Technik (who MHD list on their website as a partner) didn't answer the phone.
Issue Resolution:
I did exactly this - removed the backup from the phone and then flashed stage 0, and it worked - the car now starts and runs well. I have since had the battery replaced as the charger reported a fault saying it couldn't recover the battery back to 100% after being on charge for 3 days.
Aftermath:
I am still having trouble with loosing comms between the phone and the car when I initiate an activity (like starting a log or reading codes), and I will try a different android device and also a different OTG adaptor to see if there is any change. Not sure if the original lean afr issue has been solved or not as I haven't been able to log while driving due to these issues. The symptom is weird - the car is running and the MHD app says it connected (checked using the code scanning function). If I try to start a log or scan for codes the car will stumble (sounds like a misfire), and the MHD app will loose communication and try to connect again. The codes can't be read or the log doesn't begin. I'd appreciate advice on how to fix this.
Learnings:
- The battery should be charged before starting.
- The batter charger should be 20A or higher in capacity
- The ignition has to on and the fuel level displayed required pressing the start button twice without starting the car (in a manual)
- The MHD app doesn't provide a clear indication of its connection status
- The MHD app instructions don't specifically state the first three learnings
- I searched this thread for help while working through this: [URL="https://www.1addicts.com/forums/showthread.php?t=1342249"]
I would be interested in how others have got on with this.