Getting ISTA to talk to my Z4

[rich48848]

I am sure I have this working in the past.

Running Windows 10, ISTA Reihngold 4.01.21.17412

A USB K+DCAN silver cable. Comes up as Com1 in DM.

I get this message in ISTA:

Reconnecting to the same vehicle wasn't possible. The newly identified vehcile is a different one.

Please reconnect the same vehicle.
IFH-0027: IFH NOT FOUND


EDIABAS.INI says:

[Configuration]
IfhTrace=0
IgnitionHandling=0
Interface=STD:OBD
LogLevel=0
ApiTrace=0
TraceSize=1024
SimulationPath=C:\EDIABAS\SIM
RetryComm=1
ClampHandling=0
TraceHistory=0
EcuPath=C:\EDIABAS\ECU
NetworkProtocol=TCP
Simulation=0
TracePath=C:\EDIABAS\TRACE
TraceBuffering=0
ShowIcon=1
SystemResults=1
TaskPriority=0
TraceSync=1
UbattHandling=0
[XEthernet]
ControlPort=6811
DiagnosticPort=6801
HeaderFormat=0
RemoteHost=192.168.68.1
TesterAddress=F4,F5
TimeoutConnect=20000
[TCP]
Port=3000
RemoteHost=LMUC203404
TimeoutConnect=2000
TimeoutFunction=10000
TimeoutReceive=2000
[IfhProxy]
Port=6801



Help!!!!

 

[skelters]

What speed is COM1 running?

 

[skelters]

This might be of some help...
http://blog.obdii365.com/2015/07/13/how-to-setup-bmw-icom-rheingold-on-inpa-kd-can-cable/

 

[rich48848]

This might be of some help...
http://blog.obdii365.com/2015/07/13/how-to-setup-bmw-icom-rheingold-on-inpa-kd-can-cable/

Will try that. Not sure why setting TCP is required and why com 9 instead of com 1, but worth a shot! Thanks.

 

[rich48848]

Managed to use INPA instead, that worked fine. Will keep trying stuff with ISTA.

 

[Chippie]

Have you checked in the setting? Tab in ISTA, there may be something not set correctly, if I remember correctly the default setting is for Ethernet connection and not OBD2

 

[rich48848]

What speed is COM1 running?

DM is saying 9600.

After trying INPA, the driver has changed from a Com port to BMCables diagnostic cable. Same error code though.

 

[rich48848]

Did manage to find the error codes document but not sure it helps.

Clearly Ediabas isn't finding the OBD interface despite setting the .ini file.

 

[rich48848]

Got it going eventually.

Dumb mistake initally, I had typed ODB instead of OBD! Doh....

No more errors but still didn't talk to car.

Next I ran INPA and saw that the Ediabas server was also started. So after exiting INPA, I tried ISTA while leaving the Ediabas server running and ISTA worked. Read codes, tested ABS pump etc.

I noticed that the K+DCAN cable shows up as BMCables.com diagnostic cable in DM and not a serial port, afer running INPA from the BM Cables launcher program, so there are obviously special drivers for it being loaded, so maybe this is what allowed ISTA to start working, along with fixing my typo.