[shag]

Hello,

I have a 2009 328i xDrive and have been trying to code BC_DIGITAL_V and some other features in module KOMBI. I can read the KOMBI module without issue, but anytime I try to do "Basic Functions->coapiReadSgGetFswPsw" it gives me the following error after the dialog box:

COAPI-2000: EDIABAS or SGBD error
IFH-0003: DATATRANSMISSION TO INTERFACE DISTURBED

Any ideas? This is my first time coding this car.

[HomeBrew]

I get this when walking through the DIY and attempting to read from the airbag module:

From the INPA FAQ (the code and message do not line up, but the doc is attached - page 4,5):

1.4 IFH-0003: Data transmission HOST/Interface failed

• Reason 1: In the Ediabas.ini file, the interface is set to STD:OBD. However, you have connected an ADS connector.
• Solution 1: Modify the interface setting.

• Reason 2: The data transmission failed when sending (e.g. short circuit in the line).
• Solution 2: Get rid of the short circuit, for example.

• Reason 3: Connector not connected or no power supplied.
• Solution 3: Check whether the connector is connected and is supplied with power.

• Reason 4: The device manager has been used to disable the FIFO buffer for COM1.
• Solution 4: In the device manager (Windows XP: Enter “Start” ␣ “Control Panel” ␣ “System” ␣ “Hardware” ␣ “Device Manager” ␣ Ports (COM & LPT)), and then select COM1 from the ports. Then under the “Port Settings” tab, select “Advanced”. There must be a check-mark by “Use FIFO buffers” and “8” must be selected for the receive buffer and transmit puffer.

1.5 IFH-0010: Data transmission to control unit disturbed

• Reason: With Windows XP, it is not possible to automatically set the receive and transmit buffers using OBDSetup.exe, like in Windows NT.
• Solution: Set the receive and transmit buffers to 8 as shown in the following: Use Start ␣ My Computer ␣ Control Panel␣ System ␣ Hardware ␣ Device Manager ␣ Ports (COM & LPT) and then click with the right mouse button to call up the properties of the COM port that is being used. Under the Port Settings tab, set the Data bits of the receive and transmit buffers to 8.

Of course with Windows 7 (vista, etc) will need the serial registry values updated to match these.

I was about to post my own topic on my issue (reading and getting the same error). I haven't been able to figure it out, hope this helps.


EDIT:: After that post, I found the resolution to my issue, drivers. I uninstalled the devices and drivers under the windows device manager and rather than installing the drivers which came with the software (cause of the my problem). I configured windows to search windows update for appropriate drivers and now everything works.

Good luck.

[onebadmofo]

Ignition on?

[shag]

Well, I have a USB cable so those FIFO parameters are non-existent. I've determined that I can read/code the car but I need to try it 15-20 times before it goes. I think I might have a COM port conflict

[fdriller9]

Try keeping your hazards on

It prevents the module from going to sleep.

[HomeBrew]

Originally Posted by shag

Well, I have a USB cable so those FIFO parameters are non-existent. I've determined that I can read/code the car but I need to try it 15-20 times before it goes. I think I might have a COM port conflict

The FIFO params do exist, but only in the registry:

HEKY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\Serial

RxFIFO
TxFIFO

Both should be a DWORD, 32-bit, hexadecimal, and set to 8: 0x00000008

[E90aL]

did anyone find a solution to this problem? I used to be able to code, but I have been getting this error every time. I also get FA-Fehler sometimes.

[orangedawg]

Not sure if this will work for you, but I got that error when I was running just off the battery. Hooked up a battery tender and all was good. So, maybe that will work for you? If not, I don't know what else to try.

[E90aL]

Originally Posted by orangedawg

Not sure if this will work for you, but I got that error when I was running just off the battery. Hooked up a battery tender and all was good. So, maybe that will work for you? If not, I don't know what else to try.

didn't work. what message do you get when you run ncs with the cable plugged into the computer only?

[orangedawg]

I get the same message you get with cable plugged into computer, using fsw psw profile, do the f1, f3 thing, then get the exact error message comes up that you have. So, it's not reading your car somehow.

[Elliott@DetailAddict]

Double check your latency is set to 1 and not 16 in the com port advanced options.

[E90aL]

Originally Posted by Grant@DetailAddict

Double check your latency is set to 1 and not 16 in the com port advanced options.

My latency is set to 1, the two things above it are set to 4096. FIFO values are set according to the NCS DIY. It's set to COM1.

[BMW4Life2112]

If your latency settings are set to 1 then maybe you can try this...

Make sure that after you read the KOMBI that you go to the "work" folder and open the FSW_PSW (TRC File). Then, as DIY say's click File > "save as" FSW_PSW.MAN and set to read "all files" instead of "text". Then open your FSW_PSW (MAN file) and make your changes to the KOMBI. Then try doing the "Basic Functions > coapiReadSgGetFswPsw" and see what happens.

Sometimes when I go too quickly and forget this step, I get the same error message you get.

[Elliott@DetailAddict]

Originally Posted by BMW4Life2112

If your latency settings are set to 1 then maybe you can try this...

Make sure that after you read the KOMBI that you go to the "work" folder and open the FSW_PSW (TRC File). Then, as DIY say's click File > "save as" FSW_PSW.MAN and set to read "all files" instead of "text". Then open your FSW_PSW (MAN file) and make your changes to the KOMBI. Then try doing the "Basic Functions > coapiReadSgGetFswPsw" and see what happens.

Sometimes when I go too quickly and forget this step, I get the same error message you get.

LOL yea like when you never save the TRC to a MAN and then code

[BMW4Life2112]

Haha Grant, I know what you mean! Sometimes I open the .trc file and make my coding changes there! Although, I usually catch my mistake before I go to save it as a .man file.

[E90aL]

the problem is I can't get the computer to read the FA anymore. i get the error after these steps: connect car>turn ignition on/engine off>load FSW PSW MAN>F1>F3>E89

[BMW4Life2112]

Hey E90al,

A few things you can try:

1.) Plug cable into car, turn ignition on, and run INPA. Make sure both dots are black. If you do not have both black dots then close INPA and try running program again. If you do have both dots black, close INPA (but leave Ediabas server on). Don't proceed with the next step until functionality between your computer, cable, and car are established.

2.) Make sure you are running NCSEXPERTool as an administrator on Windows. To do this you can right click on the NCSEXPER icon on desktop and click "run as administrator".

3.) Update your daten files. You can do this a couple of ways, the easiest is to go to NCSEXPER folder (should be located in c > Daten > E89 > Double click and run "LADEN" file, this should update yor daten files automatically. Another way to do this is to copy and paste new daten files that you can get off the internet. Tr searching for them, or I can help point you in the right direction.

3.) Make sure you are using the correct drivers for your OBD ebay cable. The drivers for the ebay cable are located here (http://www.ftdichip.com/Drivers/D2XX.htm)

[E90aL]

Originally Posted by BMW4Life2112

Hey E90al,

A few things you can try:

1.) Plug cable into car, turn ignition on, and run INPA. Make sure both dots are black. If you do not have both black dots then close INPA and try running program again. If you do have both dots black, close INPA (but leave Ediabas server on). Don't proceed with the next step until functionality between your computer, cable, and car are established.

2.) Make sure you are running NCSEXPERTool as an administrator on Windows. To do this you can right click on the NCSEXPER icon on desktop and click "run as administrator".

3.) Update your daten files. You can do this a couple of ways, the easiest is to go to NCSEXPER folder (should be located in c > Daten > E89 > Double click and run "LADEN" file, this should update yor daten files automatically. Another way to do this is to copy and paste new daten files that you can get off the internet. Tr searching for them, or I can help point you in the right direction.

4.) Make sure you are using the correct drivers for your OBD ebay cable. The drivers for the ebay cable are located here (http://www.ftdichip.com/Drivers/D2XX.htm)

1. The dots are black but when i try to read something it has the data transmission error. This didn't happen 3 months ago.

3. When you update where do you put the downloaded files?

4. When I use the drivers from the website, I get a BSOD that has something to do with ftdi.sys(something like that). The only way to avoid bsod is using the drivers in the Ediabas\hardware\obd\winxp\usb2.0 folder.

If it is a faulty cable, i would like to return it asap because warranty for it is almost over.

[cedchung]

Hi,

I'm getting the same error with a 2008 E92 M3. Does anybody know what might be causing this?

I know for sure that it's not the cable since it works perfectly with my 2006 E92 335i.

[fdriller9]

Originally Posted by cedchung

Hi,

I'm getting the same error with a 2008 E92 M3. Does anybody know what might be causing this?

I know for sure that it's not the cable since it works perfectly with my 2006 E92 335i.

2006 and 2008 use different interfaces....one is K can the other D can.

[cedchung]

After some research, I found out that I have to remove Pin 8 for it to work on 2008+ cars

[cedchung]

Update: It worked with Pin 8 removed