[mediasboy]

Hi Guys after successfully installing ISTA now I'm getting an error when I try to connect to the car.

Will see the vin but when I try to connect I get this message

"The vehicle could not be identified successfully. Check vehicle interface and 'PAD active'."

[atzebmw]

Read this...

https://f30.bimmerpost.com/forums/sh....php?t=1807761

If it doesn't help you can also read this...

https://cartechnology.co.uk/showthread.php?tid=81237

[MarcosP]

i cant figure it out either ive tried everything

[Tuerkay]

If your trying to connect to an E93 from your signature, you have to set EDIABAS.INI connection to STD:OBD.
then if you connect your car with an K-D CAN cable to your Laptop, go to device Manager, COM Connections, right click on the Cable driver, Set COM-Port to 1-5, then press on extendet settings. On the bottom, there should be something called "waiting time" or similar. on default, it is set to 16ms. change that to 1ms and confirm. In ISTA go to settings -> Vehicle interface and check "Ediabas". Restart ISTA. If you still can´t connect, the K-DCAN cable is faulty

[Dynamic Entry]

Originally Posted by Tuerkay

you have to set EDIABAS.INI connection to STD:OBD

Can someone explain exactly how to check/change/set the connection to STD:OBD?


I opened up my EDIABAS.ini file and it looked exactly like below, I didn't see any lines that mention "connection" or "STD" or "Standard"


;#################
;# EDIABAS 7.3.0 #
;#################

;================================================= ============================
[Configuration]
;================================================= ============================
Interface = REMOTE
Simulation = 0

EcuPath = C:\EDIABAS\ECU
SimulationPath = C:\EDIABAS\SIM
TracePath = C:\Windows\Temp
TraceSize = 1024

ApiTrace = 0
IfhTrace = 0
; IfhnTrace = 0

; SystemTraceSys = 0
; SystemTraceBip = 0
; SystemTraceIfh = 0
; SystemTraceNet = 0

; BipDebugLevel = 0
; BipErrorLevel = 0

UbattHandling = 0
IgnitionHandling = 0
ClampHandling = 0

RetryComm = 1
SystemResults = 1
TaskPriority = 0

; CodeMapping = C:\EDIABAS\BIN\ansi2oem.tab
; LoadWin32 = 0

NetworkProtocol = TCP

; --- neu ab EDIABAS 7.2.0 ---------------------------------------------------
ShowIcon = 0
LogLevel = 0
TraceBuffering = 1
TraceHistory = 999
TraceSync = 1
; TraceWriter = <FilePathName>

;================================================= ============================
[TCP]
;================================================= ============================
RemoteHost = LMUC203404
Port = 6801
TimeoutConnect = 2000
TimeoutReceive = 2000
TimeoutFunction = 10000
; TimeResponsePending = 5000
; DisconnectOnApiEnd = 1
; InitCmd0 = FE,04,00,03,01
; InitCmd1 = FD,05,00,03,01

;================================================= ============================
[XEthernet]
;================================================= ============================
RemoteHost = Autodetect
HeaderFormat = 0
TesterAddress = F4,F5
ControlPort = 6811
DiagnosticPort = 6801
TimeoutConnect = 20000

;================================================= ============================
[IfhProxy]
;================================================= ============================
Port = 6700

;================================================= ============================
; End Of File EDIABAS.ini
;================================================= ============================

[Dynamic Entry]

I'm also curious if anyone can confirm that this should read "Standard OBD" instead of "Standard ICOM" if things are setup correctly as mentioned above by Tuerkay

[TheNine90]

Change Interface = REMOTE to Interface = STD:OBD and change port settings to port 1 and latency 1ms

[Dynamic Entry]

Originally Posted by TheNine90

Change Interface = REMOTE to Interface = STD:OBD and change port settings to port 1 and latency 1ms

Thank you very much for this!

I made the change from "Interface = REMOTE" to "Interface = STD:OBD" in the ediabas.ini text file and now ISTA connects to my e61 and everything works!


I had already changed the port settings to COM1 and 1ms latency

[MacAir]

I have a same problem, use ENET cable not USB, is there any solution.



Thanks for help

[Homersbud]

Originally Posted by MacAir

I have a same problem, use ENET cable not USB, is there any solution.



Thanks for help

re-install ISTA if it’s throwing an error about programming. what version of ISTA are you using?

also - make sure when connecting to ISTA, the ip is set to 169.254.1.1 for the local network connection.

[MacAir]

I make a re-install ISTA, but still get same error and have IP for local network

[Homersbud]

windows pc? vm?

that version of ista is the same one i use as well. have you tried a kdcan cable?

[MacAir]

I use this files and now works very well

[Homersbud]

ok, good as that is required to set the registry correctly.