Problems while flashing my DME with WINKFP/EDIABAS

[E39bmw]

Hey guys, im having a problem while trying to flash my DME. Once i click on program ECU, I get info saying that i have 13 flashes left so i click "OK".
Then i get a error code saying "IFH-0038:Interface command not implemented 10MD526"

The battery charger has been connected and charging the battery.

I tried different cars and different ECUs and still have same problem.

[TerraPhantm]

What kind of interface are you using? Which port are you accessing (OBDII or 20-pin)? Which different cars and ECUs have you tried? Did you copy the files from SP-Daten-E39\Ecu to the C:\Ediabas\ECU folder? And did you copy the files from SP-Daten-E39\Sgdat to C:\EC-APPS\NFS\SGDAT?

SG_PROGRAMMIEREN is definitely a command that's implemented in 10MDS526. My money would be placed on it being an interface issue (either the wrong type of interface, or the wrong port, or both)

[E39bmw]

Thanks for a response. Im using the OBDII plug but couple of month back i tried using the round 20 pin one under hood and still had the same exact error.

Yes i coppied everything like you stated.

I tried 98 e38 vanos and 2004 330ci manual. Both times i tried the DME ecus

[TerraPhantm]

Well just to rule out a software problem, which version of progman or Ista/P are you grabbing the data files from? I've successfully programmed E46s of all sorts with Progman v32, and Ista/P V39 and V41, so I know at least those releases have functional files (and I can't imagine any of them have faulty files).

What kind of interface are you using though? USB? Serial? ADS? OBD? BMW-specific cable or VAG-COM (or similar)?

What about configuration.... what does the option screen in your WinKFP look like? What OBD port are you using? What's the latency of your interface set to?

What version of WinKFP are you using? What version of EDIABAS?

I know those are a lot of questions, it's just that there are so many possibilities that could cause the same problem...

Just FYI, this is what the official manual says to check:


3.3 IFH-0006: Command not accepted and IFH-0018: Initialization Error and IFH-0038: Interface Command not implemented Errors IFH-0006 and IFH-0018 occur if any SGBD is loaded in the Tool Set. Error IFH-0038 is generated when loading the utility file into the Tool Set.

Reason 1: The error was caused by another programme that accessed the COM1 interface. This programme could be “HotSync” for Palm or “ActiveSync” for lpack.
Solution 1: Check the programmes that are started automatically when Windows is started (see Chapter 4.1).

Reason 2: The COM1 interface is taken by a serial printer.
Solution 2: Uninstall the printer.

Reason 3: The infrared interface is active.
Solution 3: Deactivate the infrared interface.

Reason 4: There is no COM1 interface (COM3 instead, for example)
Solution 4a): Install the COM1 interface.
Solution 4b): Create a file with the name OBD.ini and make the following entry to set the existing serial interface (COM3, for example):
[OBD]
Port = Com3

The file OBD.ini must be saved in the directory C:\WINDOWS\ for Windows XP or in directory C:\WINNT\ for Windows NT up to the Ediabas Package 1.3 and as of Ediabas Package 1.4 in directory C:\EDIABAS\BIN\. The current version of the Ediabas Package can be seen in the files C:\EDIABAS\version.txt or C:\EDIABAS\package.pdf.

Reason 5: Only for IBM notebooks: The COM1 interface is reserved for the docking
station; the COM3 interface is installed instead.
Solution 5a): see solution 4b:
Solution 5b): Set the COM3 port to COM1: In the device manager (Windows XP: Select “Start” à “Control Panel” à “System” à “Hardware” and then select COM3 from the ports under the menu item “Device Manager”. Then use the right mouse button à “Properties” à “Port Settings” à “Advanced” to reach the “Advanced Settings for COM3”. Set COM1 in the COM Port Number. The message that COM1 is already taken can be ignored in this case.

Reason 6: The old OMITEC driver wasn’t uninstalled correctly.
Solution 6: Please uninstall the old OMITEC driver with the instructions InstructionforOMITECInstallation.pdf via the GIS server.

[David Mc]

What type of interface are you using?

[E39bmw]

Im using this Ediabas interface:
http://cgi.ebay.com/ebaymotors/BMW-INPA-Ediabas-OBD-ADS-Interface-/200618009282?pt=Motors_Automotive_Tools&hash=item2eb5c3e2c2

I got the latest inpa from the 4shared link 'INpa 2010". the pass is "help". Its under NCS, INpa 2010

SO my setup is: Dell inpiron 1520, Win XP 32bit, Laptop PCMCIA to SERIAL, those wires and then my car.


http://www.4shared.com/dir/7137899/6e9cd794/sharing.html#dir=19068906

[E39bmw]

Option screen:

And Guys, thanks a lot for helping me out, I extremely appreciate it . I really need to get this thing working and for over 3 month i have been facing the SAME problem.

[E39bmw]

I have set my com port to 1 and i have OBD.ini file in windows and C:/Ediabas/Bin folders.
This is what my obd.ini looks like. (ACTUALLY i used BOTh port 3 and port 1)

I can scan the car with inpa, get access to all of my ecus and such.

When i plug my scanner into the car, Battery circle inside inpa gets balck but Ignition never changes to black even to the ignition is on

[E39bmw]

I ALSO tried using a desctop computer with dedicated Serial port and got SAME error :(

[David Mc]

You have inadvertently answered your own question, you need to be able to detect an ignition signal to program the car. I have used the do-it auto version of the same interface you are using and when connected to the round 20 pin port it does detect ignition state when used with a properly configured INPA installation and a genuine serial port.

Most likely causes of the failure are:-

1. An issue with the PCMCIA adapter - highly likely, particularly in light of the fact that no ignition signal has been detected on more than 1 car with connections via both the 16 and 20 pin port. Jarda has posted some useful info here http://forums.bimmerforums.com/forum/showthread.php?t=1633825 about setting up a PCMCIA adapter to work with an ADS interface.

2. I have seen some versions of this interface supplied with an incorrectly wired 16 to 20 pin cable, which will cause problems connecting via the round 20 pin port. My do-it auto interface is away on loan at the moment, but I have posted the correct pin connections amongst 2000 odd entries in this forum and may be able to dig them out for you given sufficient time and some luck.

3. If you attempt this procedure with INPA 2010 and DIS v44, bear in mind that INPA 2010 installs EDIABAS v7.02 by default, which is not compatible with DIS. Make sure also that if you are using the interface in ADS mode, that you have configured c:\EDIABAS\Hardware for ADS and that Interface = ADS in c:\EDIABAS\Bin\Ediabas.ini.

[E39bmw]

Alright thanks. Ill try using that guide you provided in 1st answer about PCMCIA today.

Also, what wires would you recommend me to buy that work 100% with WINKFP?

Im not using DIS at all so all i need is Ipa and WINKFP. IN this case, should i still change ediabas.ini to say interface=ads?

thanks

[David Mc]

If the car has a metal contact on Pin 15 of the round BMW 20 pin diagnostic port under the hood you should be using your interface in ADS mode and Ediabas.ini should be configured so that Interface = ADS.

[E39bmw]

Alright will check my 20 pin connector and let you know :) Thanks

[TerraPhantm]

Alright thanks. Ill try using that guide you provided in 1st answer about PCMCIA today.

Also, what wires would you recommend me to buy that work 100% with WINKFP?

Im not using DIS at all so all i need is Ipa and WINKFP. IN this case, should i still change ediabas.ini to say interface=ads?

thanks

I've read that E38s and E39s don't need the interface to be in "ADS" mode even when the L-line connector (pin 15) is present. I don't own either chassis car though, so I'm not 100% sure on that.

Also, I'm not 100% certain that ignition detect is the only issue, simply because I would think that'd throw a different error. I've never actually come across a car where my cable couldn't detect the ignition though, so I can't definitely say anything on that matter.

In any-case, I personally use a K+D-CAN interface (like this one (http://cgi.ebay.com/ebaymotors/BMW-USB-K-DCAN-D-CAN-Diagnostic-Cable-DIS-SSS-NCSExpert-/220829745241?pt=Motors_Automotive_Tools&hash=item336a7a8059), except I paid a lot more back then ><) and have never had a problem with WinKFP. I know of a few people who have succesfully used the VAG-COM 409.1 interface (the one in this (http://forums.bimmerforums.com/forum/showthread.php?t=1505990) thread) to flash the DME and EGS through WinKFP. The D-CAN interface is nice to have if you intend to work on BMWs newer than 03/2007, but otherwise it's not necessary. Though since the price has come down considerably, it might be worth just buying it anyway


Also for whatever it's worth, upgrade to WinKFP 5.1.6 or later. I've run across a lot of strange bugs in 5.1.0

[E39bmw]

Alright, i tried it again and still no go :(
I did try 5.1.6 before but that also didnt work :(

So now i wihs there was someone around my area with 100% working cables to test out..maybe afterall it is my cables that are causing the problems.

[David Mc]

I've read that E38s and E39s don't need the interface to be in "ADS" mode even when the L-line connector (pin 15) is present. I don't own either chassis car though, so I'm not 100% sure on that.

Also, I'm not 100% certain that ignition detect is the only issue, simply because I would think that'd throw a different error. I've never actually come across a car where my cable couldn't detect the ignition though, so I can't definitely say anything on that matter.

In any-case, I personally use a K+D-CAN interface (like this one (http://rover.ebay.com/rover/1/711-53200-19255-0/1?campid=5335818596&toolid=10001&mpre=http%3A%2F%2Fcgi.ebay.com%2Febaymotors%2FBMW-USB-K-DCAN-D-CAN-Diagnostic-Cable-DIS-SSS-NCSExpert-%2F220829745241%3Fpt%3DMotors_Automotive_Tools%26a mp%3Bhash%3Ditem336a7a8059), except I paid a lot more back then ><) and have never had a problem with WinKFP. I know of a few people who have succesfully used the VAG-COM 409.1 interface (the one in this (http://forums.bimmerforums.com/forum/showthread.php?t=1505990) thread) to flash the DME and EGS through WinKFP. The D-CAN interface is nice to have if you intend to work on BMWs newer than 03/2007, but otherwise it's not necessary. Though since the price has come down considerably, it might be worth just buying it anyway


Also for whatever it's worth, upgrade to WinKFP 5.1.6 or later. I've run across a lot of strange bugs in 5.1.0

+1 on the functionality of WinKFP 5.1.6. For what it is worth, I had no luck in attempting to connect to an ADS compliant E38 with an interface that was not running in ADS mode and have found the result of attempting to communicate with ADS compliant E36s with an OBD interface yields unreliable and incomplete results. Bear in mind that WinKFP has a setting for the HW interface in use and includes an option for selection of a K line/ADS interface. Since the ignition signal is required to wake up modules for diagnostics and in some cases is required to be cycled during programming, which fails when the cycling of the signal cannot be detected, I would be surprised if the lack of an ignition signal did not adversely affect programming but I stand to be corrected.

[newtoe46]

You have inadvertently answered your own question, you need to be able to detect an ignition signal to program the car. I have used the do-it auto version of the same interface you are using and when connected to the round 20 pin port it does detect ignition state when used with a properly configured INPA installation and a genuine serial port.

Most likely causes of the failure are:-

1. An issue with the PCMCIA adapter - highly likely, particularly in light of the fact that no ignition signal has been detected on more than 1 car with connections via both the 16 and 20 pin port. Jarda has posted some useful info here http://forums.bimmerforums.com/forum/showthread.php?t=1633825 about setting up a PCMCIA adapter to work with an ADS interface.

2. I have seen some versions of this interface supplied with an incorrectly wired 16 to 20 pin cable, which will cause problems connecting via the round 20 pin port. My do-it auto interface is away on loan at the moment, but I have posted the correct pin connections amongst 2000 odd entries in this forum and may be able to dig them out for you given sufficient time and some luck.

3. If you attempt this procedure with INPA 2010 and DIS v44, bear in mind that INPA 2010 installs EDIABAS v7.02 by default, which is not compatible with DIS. Make sure also that if you are using the interface in ADS mode, that you have configured c:\EDIABAS\Hardware for ADS and that Interface = ADS in c:\EDIABAS\Bin\Ediabas.ini.

My interface won't allow DIS to automatically detect the car and INPA will not show the ignition or batt LED's. With DIS I simply manually detect the car and then I am able to use DIS as intended. I also used WINKFP using the same round OBDII to ADS adapter to flash the DME out of a 328i with success.

[TerraPhantm]

+1 on the functionality of WinKFP 5.1.6. For what it is worth, I had no luck in attempting to connect to an ADS compliant E38 with an interface that was not running in ADS mode and have found the result of attempting to communicate with ADS compliant E36s with an OBD interface yields unreliable and incomplete results. Bear in mind that WinKFP has a setting for the HW interface in use and includes an option for selection of a K line/ADS interface. Since the ignition signal is required to wake up modules for diagnostics and in some cases is required to be cycled during programming, which fails when the cycling of the signal cannot be detected, I would be surprised if the lack of an ignition signal did not adversely affect programming but I stand to be corrected.

Might be something that's important on the older cars than new (not sure where the e38/39 fall since they really are in between the e36 and e46 electrically). However, since the OP got the same error on an e46, even though newe46fan was able to program an e46 without proper ignition detect, I'm willing to bet that the OP's main issue lies somewhere else.

At this point I think it may be best to reinstall from scratch; I've cleared inexplicable errors that way. But if that doesn't do it, there almost has to be an interface issue (perhaps OBD vs ADS, but that doesnt explain why he couldn't code an e46. Unless perhaps his second k-line isn't connected? Maybe he should short pins 7 and 8 and see if it works)

[E39bmw]

Still same problem. I guess il try reinstall everything on my desktop with real serial port and try again.

[E39bmw]

Tried again...still no go. same error :(

Any help guys? here its the Video of my actions as im trying to flash the DME:

Step 1:
http://s902.photobucket.com/albums/ac223/Alex_Chernal/?action=view&current=2011-Oct-1623-00-13.mp4

Step 2:
http://s902.photobucket.com/albums/ac223/Alex_Chernal/?action=view&current=2011-Oct-1623-07-01.mp4

[328 Power 04]

Apologies for the necrobump.

Today I was running into this issue all day while trying to flash/convert a spare MS41 ecu. I was doing 8+ combinations of different cables (ADS, KKL, K+DCAN), different cars, different computers, different EDIABAS versions (6.4.3, 6.4.7, 7.0.0, 7.3.0), and different WinKFPs. I even built a crude bench flashing harness, and STILL the same error!!

I gave up with a massive headache, and packed all the gear up and went inside.

However, further googling revealed the answer:
Uncheck "Programming Voltage" in WinKFP.


How annoying.

[328 Power 04]

And yes, it worked after that.

[FritzP]

And yes, it worked after that.

Interesting, what kind of error did you get with checked programming voltage.?

[328 Power 04]

The error that E39bmw was getting: IFH-0038:Interface command not implemented but for MS411.




I believe this has to do with the fact that programming voltage (enable write mode) must be applied to pin 18 of diagnostics port (or pin 60 on the MS41.1 itself) for my ECU and for the above ECU. To be able to flash with WinKFP I had to do this. So I think if I were using whatever BMW official interface that can apply and recognize programming voltage to those pins, then it would work.

In fact, after I unchecked the Programming Voltage, I attempted to flash it without putting ECU in write mode, and it bricked the ECU. (With other non BMW flashing programs, you don't get ecu bricking, it just never gets programmed.)

WinKFP revived the MS41 successfully after putting the ECU into write mode, and rewrote the new flash correctly.

[David Mc]

There are not a lot of models that require programming voltage to be applied to pin 18, so the simplest fix is to put a switch between the connections to pin 14 (battery +) and pin 18 of your interface so that you can apply programming voltage when required.

[GreatFrog]

+1 on trying out latest WinKFP version. My flash failed randomly with WinKFP 5.1.0, you can tell 5.1.0 is not very compatible with the latest Daten files when you import then. Got all sorts of errors. Switched to WinKFP 5.3.1 and everything is silky smooth. Hell, 5.1.0 was copyrighted to 2004, go figure...



I've read that E38s and E39s don't need the interface to be in "ADS" mode even when the L-line connector (pin 15) is present. I don't own either chassis car though, so I'm not 100% sure on that.

Also, I'm not 100% certain that ignition detect is the only issue, simply because I would think that'd throw a different error. I've never actually come across a car where my cable couldn't detect the ignition though, so I can't definitely say anything on that matter.

In any-case, I personally use a K+D-CAN interface (like this one (http://cgi.ebay.com/ebaymotors/BMW-USB-K-DCAN-D-CAN-Diagnostic-Cable-DIS-SSS-NCSExpert-/220829745241?pt=Motors_Automotive_Tools&hash=item336a7a8059), except I paid a lot more back then ><) and have never had a problem with WinKFP. I know of a few people who have succesfully used the VAG-COM 409.1 interface (the one in this (http://forums.bimmerforums.com/forum/showthread.php?t=1505990) thread) to flash the DME and EGS through WinKFP. The D-CAN interface is nice to have if you intend to work on BMWs newer than 03/2007, but otherwise it's not necessary. Though since the price has come down considerably, it might be worth just buying it anyway


Also for whatever it's worth, upgrade to WinKFP 5.1.6 or later. I've run across a lot of strange bugs in 5.1.0

[GreatFrog]

I've read that E38s and E39s don't need the interface to be in "ADS" mode even when the L-line connector (pin 15) is present. I don't own either chassis car though, so I'm not 100% sure on that.

Also, I'm not 100% certain that ignition detect is the only issue, simply because I would think that'd throw a different error. I've never actually come across a car where my cable couldn't detect the ignition though, so I can't definitely say anything on that matter.

In any-case, I personally use a K+D-CAN interface (like this one (http://cgi.ebay.com/ebaymotors/BMW-USB-K-DCAN-D-CAN-Diagnostic-Cable-DIS-SSS-NCSExpert-/220829745241?pt=Motors_Automotive_Tools&hash=item336a7a8059), except I paid a lot more back then ><) and have never had a problem with WinKFP. I know of a few people who have succesfully used the VAG-COM 409.1 interface (the one in this (http://forums.bimmerforums.com/forum/showthread.php?t=1505990) thread) to flash the DME and EGS through WinKFP. The D-CAN interface is nice to have if you intend to work on BMWs newer than 03/2007, but otherwise it's not necessary. Though since the price has come down considerably, it might be worth just buying it anyway


Also for whatever it's worth, upgrade to WinKFP 5.1.6 or later. I've run across a lot of strange bugs in 5.1.0


+1 on trying out latest WinKFP version. My flash failed randomly with WinKFP 5.1.0, you can tell 5.1.0 is not very compatible with the latest Daten files when you import then. Got all sorts of errors. Switched to WinKFP 5.3.1 and everything is silky smooth. Hell, 5.1.0 was copyrighted to 2004, go figure...