[Fejwin]

Ignition must be ON =) just in case you have programmed like CAS (with ignition OFF)...

[darknmy]

Ignition is On.

The voltage atm is 12.4. I believe it drops to 11-12 when the ignition is on.

I will let it sit on a charger now.

Could it be that K+DCAN Usb wire is not usable? Or machine cuts off because of low voltage?

From what I see the protocol is KWP2000 I have PreFL X3 and I have to connect 7+8 PINs for OBD2 but I'm not sure whether this is important for DME write..

And because my DME is flashed successfully I believe i'm in a pickle now...

[Ecutech]

USB Serial K+DCAN

It started to work with my other cable 2% and failed

I'm shitting bricks

You really should be using an enet cable. Your balls must be that big they have their own gravity field!
Edit..just read what car you have so no need for enet. You need a quality charger on it though. Cheaper than a new car!

[darknmy]

Update: I connected a charger and a 2nd car to my battery. I got a constant 13.8V but the same error appears after 100% flash and 0% update.

Should I be looking for ICOM Computer?

[Enabled]

At this point, I would pull DME on desk and flash directly.

Send me teamviewer on PM and I can look at your settings.

MS45 can flash with "Fast Baudrate" on.

Does the DME say MS45.1 or MS45?

---

There is nothing wrong with using K+DCAN, I think there's another module interfering with your communication.

[darknmy]

I can't connect TW right now.

That is strange. I have USB K+DCAN cable, I was reading/writing ASZL for DRL but now I cannot write DME. I can get to 2% and fail.

I will try "Fast Baudrate". It is late now and I'm a bit over-stressed.

I will try tomorrow or find a guy with experience

DME is MS45.0 ZUSB 7561490 Engine M54 170kW

I tried latest FTDI drivers and 2008 drivers

[Enabled]

You should probably turn on "Force Program Programming in Comfort mode" to make sure that your programming section gets flash updated too.

Try 2ms cable latency, as I have seen connection issues with 1ms.


Feel free to message me anytime. The DME is recoverable, do not worry. Last resort is BDM, but I doubt you damaged any areas that would force you to need BDM.

You can flash it very easily on desk if you pull a few wires to it. This one will not fail.




Can you post your current WinKFP configuration?

[atomantmk]

Is your charger capable of sustaining at least 13.5V on the car while it is flashed? You need quite powerfull charger for that! Trickle chargers won't do. Alternatively: connect quality cables from another car with running engine.

Find someone who has ICOM or any other quality interface. IFH-0003 means that protocol errors between you computer and car happened. Causes: 1: low car voltage, 2: shit quality interface, 3: you are doing something on a car while its flashing like switching things on/off, also must ensure that ignition stays on.

It's not a good idea to update DME or DDE with running engine...

Gesendet von meinem HTC 10 mit Tapatalk

[darknmy]

Fast Baudrate managed to get me to 9% and failed IFH-0003: Datatransmission to interface disturbed

I also checked "Force Program Programming in Comfort mode"

I was looking at eventvwr and did not see any events when IFH happened.

At this point I'm not sure what is causing this issue.

I have a laptop windows 10 x64 all programs worked fine INPA, NCS, ISTA-D.

If everything fails (I haven't tried 2ms), I might try flashing it on the desk. Where is the DME located? In the glovebox? VIN: WBAPA91000WA01354

[Enabled]

The dme is under the bonnet, in this box by the firewall
http://www.realoem.com/bmw/enUS/showpart...Id=12_0899

This is my favorite way to connect to MS45 (there is more than 1 way)

   



On K+DCAN side:
K-line goes to pin 7
+12 V goes to pin 16
ground goes to pin 5 (or 5&6)

12.5V or more is enough for MS45 on desk.



Maybe your K+DCAN has a problem, but I doubt it. I think another module is interfering with your flashing.