Ifh 0009 ошибка inpa

(Solved) INPA Error IFH-0009: NO RESPONSE FROM CONTROL UNIT

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:Ediabasbin 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:ediabasbin 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 !

Источник

Ediabas error 19 ifh 0009 no response from controlunit

I bought the «BMW K+DCAN D-CAN CAN INPA Ediabas USB Interface CA» cable on ebay (here) and I am trying to do battery registration (new oem-same specs AGM 90ah 900cca) on my e92 m3 (ecu: mss60). trying to run these instructions:

open up Toolset 32 (under EDIABAS folder):
1. Open mss60.prg (e92 m3’s ecu model)
2. Look up steuern_batterietausch_registri. (near bottom of job list)
3. Go to Jobs menu
4. Select Run Job

When I click run job, the LED on the OBD/USB cable blinks green a couple of times before giving me this error: «EDIABAS Fehler 19 : IFH-0009: NO RESPONSE FROM CONTROLUNIT»

I try opening INPA, (two black dots- battery and ignition on) and I press Shift+F8 for «e90 (e91,e92,e93) / 3er», and I select airbag and it shows another communication error, so I try to go to engine -> «mss60 for s65 (m3)» but I get another communication error (screen shots at the bottom of the post). Weirdly enough, when I disconnect the cable from my computer both those black circles disappear from inpa. However, if I turn my car off, the two circles do not disappear from inpa. If the usb cable is plugged in it will have two solid black circles (engine/ignition circles), but it doesn’t matter if the engine is running, engine stopped but ignition on, or completely off it will always show two black circles if the usb is connected to my laptop. So I am beginning to suspect the connection between my computer and the usb cable is good (since it blinks green a couple times when i try to run a job with inpa or tool32), but the connection between the cable and the car’s ecu is bad.

I made sure (by opening the cable cover) that pin 8 isnt connected to anything, since pin8 could trip up newer cars)
I made sure that my c:ediabasbinediabas.ini file has STD:OBD
I made sure C:Windowsobd.ini has Port=Com1
I made sure that in device manager->com1 (BMW OBD Port) -> port settings the latency is set to 1. (all other non important com ports got assigned to com 4 and 5)
I tried OBD Cable mode switching software «DCAN.exe» to set the cable to work on DCAN (rather then KCAN), this switching of mode only works when the cable is plugged into my obd port recently (when the led is red), after a minute or so the led turns off. Also when I try to send a command with tool32 when the red led, the red led will turn off immediately and will start blinking green a couple of times, but will return a «communication error»

Here are some screen shots I took

If you can help in any way with this problem (short of, return it and get a newcable) I would really appreciate it, thanks for your time for even reading this post.

Источник

Не коннектиться автомобиль с INPA

Реклама

Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 3

Источник

I bought the «BMW K+DCAN D-CAN CAN INPA Ediabas USB Interface CA» cable on ebay (here) and I am trying to do battery registration (new oem-same specs AGM 90ah 900cca) on my e92 m3 (ecu: mss60). trying to run these instructions:

When I click run job, the LED on the OBD/USB cable blinks green a couple of times before giving me this error: «EDIABAS Fehler 19 : IFH-0009: NO RESPONSE FROM CONTROLUNIT»

I try opening INPA, (two black dots- battery and ignition on) and I press Shift+F8 for «e90 (e91,e92,e93) / 3er», and I select airbag and it shows another communication error, so I try to go to engine -> «mss60 for s65 (m3)» but I get another communication error (screen shots at the bottom of the post). Weirdly enough, when I disconnect the cable from my computer both those black circles disappear from inpa. However, if I turn my car off, the two circles do not disappear from inpa. If the usb cable is plugged in it will have two solid black circles (engine/ignition circles), but it doesn’t matter if the engine is running, engine stopped but ignition on, or completely off it will always show two black circles if the usb is connected to my laptop. So I am beginning to suspect the connection between my computer and the usb cable is good (since it blinks green a couple times when i try to run a job with inpa or tool32), but the connection between the cable and the car’s ecu is bad.

I made sure (by opening the cable cover) that pin 8 isnt connected to anything, since pin8 could trip up newer cars)
I made sure that my c:ediabasbinediabas.ini file has STD:OBD
I made sure C:Windowsobd.ini has Port=Com1
I made sure that in device manager->com1 (BMW OBD Port) -> port settings the latency is set to 1. (all other non important com ports got assigned to com 4 and 5)
I tried OBD Cable mode switching software «DCAN.exe» to set the cable to work on DCAN (rather then KCAN), this switching of mode only works when the cable is plugged into my obd port recently (when the led is red), after a minute or so the led turns off. Also when I try to send a command with tool32 when the red led, the red led will turn off immediately and will start blinking green a couple of times, but will return a «communication error»

Here are some screen shots I took

View post on imgur.com

If you can help in any way with this problem (short of, return it and get a newcable) I would really appreciate it, thanks for your time for even reading this post.