[guwakjai010]

Originally Posted by rorkor

Which cable did you buy? I need to get one for my 2011.

i found one on Ebay.... on the picture its literally said 2008-2012.... its one of the more expensive cables.... they are about 100 bucks.... USUALLY (but not always) the more expensive ones are the one that can code 08 and up

[rorkor]

Originally Posted by guwakjai010

i found one on Ebay.... on the picture its literally said 2008-2012.... its one of the more expensive cables.... they are about 100 bucks.... USUALLY (but not always) the more expensive ones are the one that can code 08 and up

Thanks, gonna shop this weekend for it. I have some electrical engineering experience so it all looks pretty straight forward.

[BmerMeUp]

Same-o, Same-o.
Thanks to Rich, I now have a working VM image () - I was trying to use MS-Virtual PC and that was giving me all sorts of crazy errors. VM is far more robust and the image seems to be working perfectly with the cable now.

Problem now points very strongly to the cable, as a result however - consistently getting "ifh-0009" errors for everything, still cannot talk to car. Cable however seems to respond to requests - RED when I first plug it into the PC, GREEN FLASHES on PC (INPA or NCS) requests, OFF in-between. So in NCS or INPA, when I trigger a read request, cable flashes green for 1-2 seconds then I get my dreaded error and the cable goes dark. Subsequent requests still wake the cable up to flash green, but error persists. This suggests to me the VM interface to the cable is working fine and the cable is responding to the VM request... but not handling the reply? I tried pin 7,8 connected and not connected also - no difference.

I dunno. Bummed out. Working up the courage to buy another (more expensive) cable as that seems to be working for others.

[guwakjai010]

Originally Posted by BmerMeUp

Same-o, Same-o.
Thanks to Rich, I now have a working VM image () - I was trying to use MS-Virtual PC and that was giving me all sorts of crazy errors. VM is far more robust and the image seems to be working perfectly with the cable now.

Problem now points very strongly to the cable, as a result however - consistently getting "ifh-0009" errors for everything, still cannot talk to car. Cable however seems to respond to requests - RED when I first plug it into the PC, GREEN FLASHES on PC (INPA or NCS) requests, OFF in-between. So in NCS or INPA, when I trigger a read request, cable flashes green for 1-2 seconds then I get my dreaded error and the cable goes dark. Subsequent requests still wake the cable up to flash green, but error persists. This suggests to me the VM interface to the cable is working fine and the cable is responding to the VM request... but not handling the reply? I tried pin 7,8 connected and not connected also - no difference.

I dunno. Bummed out. Working up the courage to buy another (more expensive) cable as that seems to be working for others.

thats exactly what happened to me... i bought a 40 dollar cable.... everything seemed to worked and software and VMware was working correctly, didnt work on my car but when i went to my friends 07, it worked, so that tells me my cable wasn't for 08+ which uses a different communication protocol.... so i bought a more expensive cable that was 98 dollars that said it was for 08+ and then it worked...

[BmerMeUp]

Update for this thread: I was shipped a replacement cable from the same company who gave me the original one, except I received a COMPLETELY DIFFERENT CABLE... which worked first try. Fyi.
http://www.e90post.com/forums/showthread.php?t=788664

[Najt]

I have similiar problem. My prog.files:

* Ediabas 7.3.0, Inpa ea90x, NCSe 3.1.0, daten v.49 (daten and sgdat in ncse, ecu copied to ediabias/ecu
* ini files are configured properly
* Cable is from one-stop shop

I can read and code any ECU, but not TCUM. I always get error:
Error in CABD! Look at CABI.ERR and ERROR.LOG!
COAPI-2020: no answer from ECU
IFH-0009: NO RESPONSE FROM CONTROLUNIT

does it mean that the ECU is dead?

[pweber84]

Originally Posted by Najt

I have similiar problem. My prog.files:

* Ediabas 7.3.0, Inpa ea90x, NCSe 3.1.0, daten v.49 (daten and sgdat in ncse, ecu copied to ediabias/ecu
* ini files are configured properly
* Cable is from one-stop shop

I can read and code any ECU, but not TCUM. I always get error:
Error in CABD! Look at CABI.ERR and ERROR.LOG!
COAPI-2020: no answer from ECU
IFH-0009: NO RESPONSE FROM CONTROLUNIT

does it mean that the ECU is dead?

Are you sure that you have TCUM?

[Najt]

It has to be there. I have paired once my mobile with the car. But it could not read the phonebook. But I've tried to make test call and it was perfect.