Ifh 0009 ошибка inpa

INPA error IFH-0009 No Response usually means a break down (or lack of) communication between the vehicle itself, and the laptop. More often than not, IFH-0009 errors in INPA are caused by the following reasons.

The hardware for INPA can be:
BMW ICOM A2;
INPA KDCAN USB cable;
EDIABAS OBDII interface;

1) Poor quality, or incorrectly wired interfaces. IFH-0009 errors are the most common in D-Can+K usb interface leads. Often these low-quality can be badly constructed, incorrectly wired, or contain the wrong chip set drivers or come with no drivers at all!. Whilst not all Chinese interfaces are poor quality, buying cheap imported leads is a gamble and when problems occur the seller probably won’t be interested. It is therefore important that you buy an interface lead from a good quality, reputable Vendor.

2) Wrong or Incorrect Interface Drivers. Again, mass produced interfaces can often contain cd’s with the wrong chipset drivers or come with no CD at all. Without the correct (latest) USB drivers, your interface lead will not install under windows properly. Our software package comes complete with a popular driver which is compatible with most Chinese and Western produced USB Interfaces, which will often work if the one supplied from your interface lead vendor doesn’t or hasn’t been included.

3) Incorrectly configured interface lead. Again, one of the most common problems with USB type leads. When installing a D-Can or Usb Interface lead, you will need to reconfigure the Windows based com port settings, so that the USB lead, appears to replicate an old RS-232 serial port. To replicate the port correctly, you need to change the existing Com port setting of the USB interface within Windows to Com Port 1 and change the latency setting to ‘1′ and check any ‘Fifo’ box

4) Incorrectly wired interface. Once again, there is no set standard as to the wiring pin configurations used within D-Can + K interfaces, by the various manufacturers. Some interface leads have pin 8 disconnected, some have pin 8 physically linked (bridged) to Pin 7, and some have pin 7 & 8 connected individually with no bridge link. If you still have problems connecting to the vehicle, and still get ‘IFH’ style errors then you should open the OBD Socket of the lead and check the pin wiring to see which type of interface you have. You should consider trying your interface lead, with the following configurations….

i) Pin 8 joined to Pin 7 using a small wire link

ii) Pin 8 physically disconnected

iii) Pin 7 and Pin 8 individually connected to their own pins with no link.

More often than not, one of these configurations will work with your vehicle, I recommend trying it with pins 7 & 8 linked together first, as this is by far the most popular vehicle configuration.

Also don’t assume that once you have found the pin 8 solution which works with one vehicle, that it will automatically work with a different model. If you have more than one D-Can equipped vehicle, you may need to obtain a second interface lead and configure ‘pin 8′ differently.

If you don’t own a soldering iron, or if you don’t feel confident about soldering electrical connectors, then there are adaptors available which will bridge pins 7 & 8 together, without any need to open the OBD socket or solder.

5) Incomplete Versions of INPA. There are many versions of Inpa around, many of which are incomplete or simply lack the various configuration files in which to work correctly. If you try all of the above and the IFH-0009 problem still remains, then you will need to consider buying and installing the full version of Inpa which includes Ediabas and BMW Standard Tools

Real case solved by one of solutions above:
Background:
1. I have a 2004 325ci

2. I purchased the k+dcan cable from obdexpress.co.uk. It is an under-the-dash OBD to USB cable.

3. It came with what was described as INPA 5.02 EDIABAS 6.4.7. You have to install BMW Tools first, and then update. (Updating INPA, it shows a check mark next to INPA 5.01 “update,” and loading INPA, it says version 5.00 at the top bar.) I also installed NCSExpert.

4. I am using windows XP SP3 32 bit. Firewall disabled, no anti-virus. No other software is installed. (I’ve had the same problem using Win 7 and Vista).

5. C:\Ediabas\bin is in the path.

6. Installed the USB cable and set the COM port to 1. Latency is set to 1ms. There is no option to use FIFO buffer.

7. Ediabas.ini has STD:OBD as interface. It is also set so loadwinxp = 1

8. OBD.INI is in C:\ediabas\bin and \system32. COM port is set to 1 and hardware = USB (when hardware = OBD the battery circle is black even when not plugged into the car).

9. When loading INPA, I get black battery and ignition when plugged in and starting car.

10. I can successfully read the ECU. I can read and clear errors.

11. When trying to read any other module, I get the IFH 0009 No Response From Control Unit.

How to solved:
I took about the connector and pins 7 and 8 are indeed soldered together!

I verified that both pins 7 and 8 had voltage and that the connection from the chassis wires to the obd plug under the dash were solid.

I then looked closely at pin #8 on the OBD/USB wire and noticed that it was bent slightly. It was not lining up in the pin #8 slot! I straightened it out and it worked!

(Visited 13,131 times, 5 visits today)

1. Hi,

   I’ve tried searching the forums and the web and found nothing that has helped me. I have a USB — OBD cable which should work fine with a Mini Cooper R56.

   I have installed all the software in a Windows XP 32-bit VM-Ware machine.

   What I’ve done is install drivers (I’ve tried several): 1) I found here. 2) I found it on a large MINI-forum and 3) I found it on the manufacturers website. Same situation with all.

   I’ve installed INPA, Ediabas and NCS Expert according to the instructions I’ve found on this forum, on the MINI forum and from the seller. All installations are similliar or the same though it has been both INPA 5.01 and 5.02 as well as both Ediabas 6.4.7 and 7.0.2.

   I’ve changed port settings to latency 1 and using COM 1. I’ve checked the ediabas.ini and obd.ini and interface is set to OBD com 1.

   I’ve added the environment variable and also the obd.ini to the windows directory (even though it seems redundant).

   I am not a computer illiterate and feel comfortable that I have followed the instructions exactly.

   What I’m trying to do now is figuring out if this is a hardware or software problem.

   What I can do is start inpa and get 2 black dots, the ignition one becomes white when ignition is off so there seems to be some communication with the car.

   Other than that everything throws IFH-0009 No response from controlunit. I’ve tried to read everything in INPA with the same error.

   Thanks for any help!

   ---

2. Courtesy of Google translate
   IFH-0009: SG is not connected or not found

   Reason 1: In the file as an interface is Ediabas.ini STD: ADD set, but you
   an OBD connector connected.
   Solution 1: Adjust the interface setting.

   Reason 2: ignition is turned off.
   Solution 2: Turn on the ignition.Reason 3: For COM1 is disabled on the Device Manager of the FIFO buffer.
   Solution 3: In the Device Manager (Windows XP: «Start» -> «Control Panel» -> «System» ->
   «Hardware») to select among the ports COM1 and select from the Reggisterkarte
   Connection settings «Advanced». It has the hooks in
   Be «Use FIFO buffers», and the input buffer, the maximum
   Setting must be selected.
   3.6

   Make sure that your interface is identified in Ediabas.ini as «Interface = STD:OBD» and that your interface is equipped to detect an ignition signal.
   If both of these settings are correct and you have already configured buffer settings, the problem could be due to an incorrectly configured COM port or defective USB to serial adapter.

   When installing INPA, did you initially install v3.01/EDIABAS v6.4.3, then upgrade to v5.02/EDIABAS v6.4.7?

   Also bear in mind that versions of EDIABAS later than v6.4.7 are not compatible with DIS.

   Last edited by David Mc; 05-07-2012 at 04:52 AM.

   ---

3. Hi,

   Thanks!

   I have though already found that exact text with 3 reasons and solutions. Other than my drivers for the com-port not having «FIFO-buffers» as an option but instead the newer ones with Latency (where I have selected 1) I’ve done everything in that list.

   Do you know of any known working drivers for USB-to-serial converter?

   Thanks again!

   ---

4. When installing INPA, did you initially install v3.01/EDIABAS v6.4.3, then upgrade to v5.02/EDIABAS v6.4.7? Post a picture of your interface and I will try to help you further.

   Last edited by David Mc; 05-07-2012 at 04:55 AM.

   ---

5. No, I don’t think I have ever installed v3.01 and certainly not on the last laptop I tried it on (I’ve tried it on windows vista before but then I couldn’t get ignition recognition to work).

   ---

6. No ignition signal fits the criteria for an IFH-0009 error. Make sure that the LoadWIN32 = * statement in Ediabas.ini is set to «LoadWIN32 =1» so that the program is correctly mapped for your 32 bit OS. Do you know what type of chipset your interface is based on and is it designed to be used with a USB or true serial port?

   Last edited by David Mc; 05-07-2012 at 05:36 AM.

   ---

7. Hi,

   I will check the ediabas.ini as soon as I get home tonight. But I don’t know if that could be the problem as I have checked with a 64-bit installation on windows 7 as well and have the same error.

   In win 7 and XP (32bit) I get both battery and ignition but IFH-0009 errors all over. In win Vista I got only battery and never got it working either.

   The chip is an ft232r? I have checked that pin 7 and 8 are bridged. They are!
   Don’t know if that is correct, but from what I understand, it is.

   The cable is a USB -> obd2. There are no serial port on it.
   http://www.ebay.co.uk/itm/1208941874…ht_4938wt_1163

   Thanks again!

   Really appreciate it!

   ---

8. Hi,

   I have checked ediabas.ini and LoadWin32 was commented out.
   I haven’t had the chance to test it again but I have changed from:
   ;LoadWin32 = 0
   to
   LoadWin32 = 1

   Hopefully that will solve my issue.

   Thank you!

   Mike

   ---

9. I have issues with my INPA also with similar errors. I am able to see the airbag and that is all. I am operating XP PRO which I believe is 64bit. Can this be my issue? If you can I also change setting to operate as a 32bit system? I am using the carsoft interface as OBD. This is on a 94 325IS

   Thanks for any help.

   ---

10. Using the Carsoft interface for DIS/INPA is trying at best.

    But..when using it on ADS cars, (Pre-95 and ALL E36/Z cars) its shooting yourself in the foot.

    You need an ADS interface set to ADS in the ini file.

    95 840Ci, Calypso Red/Silver, 83k — 99 740i, Black/Black, 185k, Alpina Mods — 01 740i, Titanium/Silver, 40k, Sport Pkg
    Complete Turnkey Diagnostic/Programming systems available…PM for details.
    
    http://www.8Coupe.com — Please register, spot, and help the project.

    ---

11. are pins 7 and 8 supposed to be bridged for a mini cooper… if im not mistaken, the mini cooper platform is like an e46…. I put a switch on pins 7 and 8 so I can do all chassis…. if pins 7 and 8 are bridged, i can read old old bmw with 20 pin adapter, e46, e53 and e83… if they are bridged, cant read any of those and I think I get that error, For sure I dont get Ignition signals.
    something to look into.

    ---

12. Depends on the Mini model you are trying to work with. Anything before the R56 requires pins 7-8 bridged. R56 and up only need pin 7.

    There’s a wiki article over at bmwcoding that has a definitive list of what cars need the pins bridged and which ones don’t. (information direct from BMW)

    ---

13. Hi,

    Well. I certainly have a r56 and I tested pin 7-8 bridge with ohm-meter (best (only) equipment I have at hand) and got the same resistance as when shorting the leads. I.e. it is bridged.

    By the way, chaning it to loadwin32 = 1 did not help at all. I think it defaults to 1 if you have winXP installed (at least the ediabas.ini said so).

    Then I have a question regarding the pin 7/8 bridge, non bridge thing. If it shouldn’t be bridged, would I need it at all or could I just solder it out (if I get the hold of a soldering iron) or maybe insulate it.

    Also a link to that list would be appreciated. Meanwhile I will be searching the bmwcoding forum for that site.

    Thanks,
    Mike

    ---

14. Hi,

    The seller didn’t want me to modify the cable unsoldering pin 7-8. I returned the cable and got a full refund minus the return shipping.

    I ordered a new cable from ECUtools which also have pin 7-8 connected. Finally tested it last night and it works!!
    Same installation, same drivers, same everything as the first cable and it just worked.

    Got error message SGDB version doesn’t match, but I could re-initialize my windows so that my passenger side window now dips when I open the door!

    Thanks for all the help!

    Mike

    ---

15. OK, I have the OBD cable with pins 7/8 jumped. It works fine on my E46 but on my R56 Mini I get the IFH-0009 error. I can see the battery and ignition but that’s it.
    Do I need to un-jump pins 7 and 8 to get it to work on the MINI?
    Thanks!

    ---

16. Originally Posted by roosm
    

    Hi,

    The seller didn’t want me to modify the cable unsoldering pin 7-8. I returned the cable and got a full refund minus the return shipping.

    I ordered a new cable from ECUtools which also have pin 7-8 connected. Finally tested it last night and it works!!
    Same installation, same drivers, same everything as the first cable and it just worked.

    Got error message SGDB version doesn’t match, but I could re-initialize my windows so that my passenger side window now dips when I open the door!

    Thanks for all the help!

    Mike

    I have the same problem with my E46 BMW, after reading your post i suspect its the cable,,i open it up, resoldered pin 7-8 (the are already soldred, but i think it was not enough contact) ….
    Woalaaaa… problem solved…

    ---