Hi Guys, my 2ND post i got the BMW Scanner Ediabas/INPA 4 compatible OBD2 Interface UK — from ebay — serial connection(not USB)
I Have a BMW 120d — SE — 2007 — i think its a E87? — Computer is HP6220 — XP SP3 — NO VMWARE, installed locally.
I cannot get INPA to talk to my car installed 4 differnet installs(ghosting machine each time back to original state) followed different guides. This is what i have concluded to be common to all the installs i have seen.Installed as instructed — INPA 5.02 — EDIABAS — 6.4.7
and made the following changes after install.
YOU WILL GET ISSUES IF YOU DO NOT COPY FILES FROM CD TO THE ROOT DRIVE OF C:INPA BEFORE INSTALLING AT THE BEGINNING.
AND RUN FROM c:|inpa ISSUES START WHEN YOU GET TO THE CHOOSING WHAT TO INSTALL.
aNY WAY AFTER INSTALL:-1
EDIABAS.INI
Lives in
C:EDIABASBin
;——————————————————————————
; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD
Interface =STD:OBD
; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!
; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : EDIABASHARDWAREOBDODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
———————————————————————————
2—————————————————
3
Environment Variables — system Variables — find the PATH one in the list highlight and EDIT — add this to the end of the paths(NO SPACES but remove quotes)»;C:EDIABASBin;C:INPABIN»—————————————————
4
EDIT OBD.ini — copy to windows directory — C:WINDOWS
[OBD]
Port=Com1
Hardware=OBD
RETRY=ON
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xF0000000
;Tracelevel=0x0000FFFF
; Bit 0 = Funktionsaufruf
; Bit 1 = io Ergebnis
; Bit 2 = nio Ergebnis
; Bit 3 = Detailinfos
; Nibble 0 = readchar_wait
; Nibble 1 = main
; Nibble 2 = cmd
; Nibble 3 = obd
; Nibble 4 = send_and_receive_…
; Nibble 5 = read_telegram_…
; Nibble 6 = send_telegram
; Nibble 7 = SendData
—————————
5
————————————————
6
————————————————————Note.
In INPA i do get the Battery black circle and ignition when turned on black circle but i have had numerous errors when testing i select E87 — status Busy then i get — from IFH-0009 — SYS-0005 — API etc i have checked these in the INPA-FAQ.pdf. I have copied contents from
Any Help would be appreciated — i think it must be an .ini or something.
Thanks in advance.Firstly Guys — thanks for your reply at BMWLAND — I checked the SGBD folder doesn’t exist — so i put it there.
ODB.ini put in the sysyem and system32 folder(although the path in the env variable points to this.)
As can be seen from the screen shot the lead is sensing the connection — maybe «minesavolvo» is correct in the fact that i do not have the correct files for the E87?? i have attached the DIR of the entire c’drive hope someone can point me in the right direction — man hours is shooting through the roof.lol
«TheEnd» — you were correct the OBD.ini was a little short i did so to keep the page shorter.
EDIABAS.ini — underlined the OBD bit — I’m also wondering why it shows E89 in the INPA window under model?? is it the same as E87.
As always thanks for your help.;================================================= ============================
;EDIABAS 6.4.3 Configuration
[Configuration]
;================================================= ============================;——————————————————————————
; EcuPath
; Description : ECU file path
; Default = .
EcuPath = C:EDIABASEcu;——————————————————————————
; SimulationPath
; Description : Simulation file path
; Default = .
SimulationPath = C:EDIABASSIM;——————————————————————————
; TracePath
; Description : Trace file path
; Default = .
TracePath = C:DiagProgTrace;——————————————————————————
; CodeMapping
; Description : Character mapping file path
; Default = .
;CodeMapping = C:EDIABASBINansi2oem.tab;——————————————————————————
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0..32767
; Default = 1024
TraceSize = 5120;——————————————————————————
; ApiTrace
; Description : Enable/Disable API/User trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + time stamp
; 3 = User trace + time stamp + process id (Win32)
; 4 = Function trace
; 5 = Function trace + time stamp
; 6 = Function trace + time stamp + timing
; 7 = Function trace + time stamp + timing + process id (Win32)
; Default = 0
ApiTrace = 0;——————————————————————————
; IfhTrace
; Description : Enable/Disable IFH trace
; Value : 0 = Trace disabled
; 1 = Trace enabled
; 2 = Trace enabled
; 3 = Trace enabled
; Default = 0
IfhTrace = 0;——————————————————————————
; SystemTraceSys
; Description : Enable/Disable system trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceSys = 0;——————————————————————————
; SystemTraceBip
; Description : Enable/Disable BIP trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceBip = 0;——————————————————————————
; SystemTraceIfh
; Description : Enable/Disable IFH system trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceIfh = 0;——————————————————————————
; SystemTraceNet
; Description : Enable/Disable network trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceNet = 0;——————————————————————————
; BipDebugLevel
; Description : BIP debug level of ECU files
; Value : 0..32767
; Default = 0
BipDebugLevel = 0;——————————————————————————
; UbattHandling
; Description : Ubatt ON/OFF handling
; Value : 0 = Ubatt ON/OFF: No EDIABAS error
; 1 = Ubatt ON/OFF: EDIABAS error
; Default = 1
UbattHandling = 0;——————————————————————————
; IgnitionHandling
; Description : Ignition ON/OFF handling
; Value : 0 = Ignition ON/OFF: No EDIABAS error
; 1 = Ignition ON/OFF: EDIABAS error
; Default = 1
IgnitionHandling = 0;——————————————————————————
; TaskPriority
; Description : EDIABAS process/thread priority (only Win32/16)
; Value : 0 = Optimal EDIABAS performance = 8
; 1 = Minimal EDIABAS performance
; ..
; 10 = Maximal EDIABAS performance
; Default = 0
TaskPriority = 0;——————————————————————————
; LoadWin32
; Description : Map EDIABAS Win16 calls to EDIABAS Win32
; Value : 0 = Win16/32 Mapping disabled (Win16—>Win16)
; 1 = Win16/32 Mapping enabled (Win16—>Win32)
; Default = 0 for Windows 9x/Me
; Default = 1 for Windows NT4/2000/XP
;LoadWin32 = 0;——————————————————————————
; SystemResults
; Description : Enable/Disable system results (ubatt/ignition/jobstatus)
; Value : 0 = Disable system results
; 1 = Enable system results
; Default = 1
SystemResults = 1;——————————————————————————
; RetryComm
; Description : Repeat failed communication automatically (1x)
; Value : 0 = Retry disabled
; 1 = Retry enabled (1x)
; Default = 1
RetryComm = 1;——————————————————————————
; Simulation
; Description : Enable/Disable ECU simulation
; Value : 0 = Simulation disabled
; 1 = Simulation enabled
; Default = 0
Simulation = 0;——————————————————————————
;
; Description : Connected diagnosis interface
;Default = OBD
Interface = STD:OBD
; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : EDIABASHARDWAREOBDODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : OBD.ini nur benutzt wenn im Windows-Verzeichnis
; Unterstuetzung : WIN3.xx : Nein
; WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = STD:FUNK
; Beschreibung : Funk-Diagnose Interface MDA von Fa. Siemens
; Installation : keine
; INI-Datei : FUNK.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = ADS
; Beschreibung : Serieller Pegelwandler (Anschluss an Diagnose-Dose)
; Installation : EDIABASHARDWAREADSADS32ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = KBUS
; Beschreibung : Serieller Pegelwandler (Anschluss direkt an K-Bus oder I-Bus)
; Installation : EDIABASHARDWAREADSADS32ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = EDIC
; Beschreibung : Serielles , PCMCIA , PC-Card Interface von Fa. Softing
; Installation : EDIABASHARDWAREEDICSETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = EDICC
; Beschreibung : EDIC-Card C oder EDIC-Card 2 CAN-Interface von Fa. Softing
; Installation : EDIABASHARDWAREEDICSETUP.EXE
; INI-Datei : XEDICC.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja; Interface = STD:CAN
; Beschreibung : PCMCIA CAN-Interface CanCardX von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CANRTTP.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : ?
; Ansprechpartner: Hr. Jusko
; Telefon : +49-(0)89/382-35891 (Hotline)
; email :FLASH.SERVICE@BMW.DE (Hotline)
; Interface = STD:ADS4MOST
; Beschreibung : Most-Interfaces von Fa. Oasis
; Installation : keine (ausser Installation der Oasis-Karte)
; INI-Datei : ADS4MOST.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email :Michael.Rowedder@bmw.de
; Interface = REMOTE
; Beschreibung : Anbindung eines EDIABAS-Interfaces �ber TCP/IP
; Installation : Anpassung der Eintr�ge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email :Michael.Rowedder@bmw.de
; Interface = REMOTE:name
; Beschreibung : Anbindung eines EDIABAS-Interfaces �ber TCP/IP
; Installation : Anpassung der Eintr�ge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : REMOTE.INI (insbesondere f�r Parallelbetrieb notwendig)
; In REMOTE.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port)
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email :Michael.Rowedder@bmw.de
;——————————————————————————
; NetworkProtocol
; Description : Network protocol
; Default =
NetworkProtocol = TCP;================================================= ============================
;TCP/IP Configuration
[TCP]
;================================================= ============================;——————————————————————————
; RemoteHost
; Description : server address/name
; Default =
RemoteHost = WMUC102911;——————————————————————————
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
; Default =
Port = 3000;——————————————————————————
;TimeoutConnect
; Description : Timeout for establishing the connection
; Default = 5000
TimeoutConnect = 2000;——————————————————————————
;TimeoutReceive
; Description : Timeout for receiving a message
; Default = 5000
TimeoutReceive = 2000;——————————————————————————
;TimeoutFunction
; Description : Timeout for a long function
; Default = 59000
TimeoutFunction = 10000;——————————————————————————
;DisconnectOnApiEnd
; Description : Enable/Disable Disconnection with function call ApiEnd
; Value : 0 = Disconnection disabled
; 1 = Disconnection enabled
; Default = 0
;DisconnectOnApiEnd = 1;——————————————————————————
;InitCmd<n>
; Description : Initialization command <n> (normally for OPPS)
; Default =
;InitCmd0 = FE,04,00,03,01
;InitCmd1 = FD,05,00,03,01;================================================= ============================
; End Of File EDIABAS.ini
;================================================= ============================
EDIABAS.INIСодержание
- Thread: INPA problems
- INPA problems
- INPA problems on serial lead
Thread: INPA problems
Thread Tools
INPA problems
whats going on everyone. so i installed inpa 5.0 last night and i keep getting these error messages. now i get
apiInit : error #37
ifh-0027: ifh not found
api initialization error
no api calls possible
what can i do to make it work? thanks you all for the help.
sorry this is my first time here and using this software can you be more specific on what you mean. i am using a usb obdII cable and i changed the note pad file from ads to obdII cause i got another error before but now i get the api. thank you btw
I dont use INPA 5.x, but you have to install INPA 3.x/Ediabas 6.4.3 first, then update to INPA 5.x/Edibas 6.4.5
What interface are you trying for this car?
INPA problems on serial lead
Hi Guys, my 2ND post i got the BMW Scanner Ediabas/INPA 4 compatible OBD2 Interface UK — from ebay — serial connection(not USB)
I Have a BMW 120d — SE — 2007 — i think its a E87? — Computer is HP6220 — XP SP3 — NO VMWARE, installed locally.
I cannot get INPA to talk to my car installed 4 differnet installs(ghosting machine each time back to original state) followed different guides. This is what i have concluded to be common to all the installs i have seen.
Installed as instructed — INPA 5.02 — EDIABAS — 6.4.7
and made the following changes after install.
YOU WILL GET ISSUES IF YOU DO NOT COPY FILES FROM CD TO THE ROOT DRIVE OF C:INPA BEFORE INSTALLING AT THE BEGINNING.
AND RUN FROM c:|inpa ISSUES START WHEN YOU GET TO THE CHOOSING WHAT TO INSTALL.
aNY WAY AFTER INSTALL:-
1 
EDIABAS.INI
Lives in
C:EDIABASBin
;——————————————————————————
; Interface
; Description : Connected diagnosis interface
; Default = STD:OBD
Interface =STD:OBD
; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!
; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : EDIABASHARDWAREOBDODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
———————————————————————————
2 Right Click — my computer- — device manager — ports — com1 — port setting — advancd — fifo buffers ticked — and TX and RX set to 8 — OK to save
—————————————————
3 Right Click — my computer- sytem properties — advanced —
Environment Variables — system Variables — find the PATH one in the list highlight and EDIT — add this to the end of the paths(NO SPACES but remove quotes)»;C:EDIABASBin;C:INPABIN»
—————————————————
4 THE OBD.ini — lives in C:EDIABASBin — well on some installs or can be created manually.
EDIT OBD.ini — copy to windows directory — C:WINDOWS
[OBD]
Port=Com1
Hardware=OBD
RETRY=ON
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xFFFFFFFF
;Tracelevel=0xF0000000
;Tracelevel=0x0000FFFF
; Bit 0 = Funktionsaufruf
; Bit 1 = io Ergebnis
; Bit 2 = nio Ergebnis
; Bit 3 = Detailinfos
; Nibble 0 = readchar_wait
; Nibble 1 = main
; Nibble 2 = cmd
; Nibble 3 = obd
; Nibble 4 = send_and_receive_.
; Nibble 5 = read_telegram_.
; Nibble 6 = send_telegram
; Nibble 7 = SendData
—————————
5Run the OBDSetup.exe in the C:EDIABASHardwareOBD to update the registry for OBD settings and then reboot re run the above and all should show OK.
————————————————
6 Ensure you run the INPALOAD.exe — from C:EC-APPSINPABIN — WHEN USING INPA
————————————————————
Note.
In INPA i do get the Battery black circle and ignition when turned on black circle but i have had numerous errors when testing i select E87 — status Busy then i get — from IFH-0009 — SYS-0005 — API etc i have checked these in the INPA-FAQ.pdf. I have copied contents from
Any Help would be appreciated — i think it must be an .ini or something.
Thanks in advance.
Firstly Guys — thanks for your reply at BMWLAND — I checked the SGBD folder doesn’t exist — so i put it there.
ODB.ini put in the sysyem and system32 folder(although the path in the env variable points to this.)
As can be seen from the screen shot the lead is sensing the connection — maybe «minesavolvo» is correct in the fact that i do not have the correct files for the E87?? i have attached the DIR of the entire c’drive hope someone can point me in the right direction — man hours is shooting through the roof.lol
«TheEnd» — you were correct the OBD.ini was a little short i did so to keep the page shorter.
EDIABAS.ini — underlined the OBD bit — I’m also wondering why it shows E89 in the INPA window under model?? is it the same as E87.
As always thanks for your help.
;——————————————————————————
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0..32767
; Default = 1024
TraceSize = 5120
;——————————————————————————
; ApiTrace
; Description : Enable/Disable API/User trace
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + time stamp
; 3 = User trace + time stamp + process id (Win32)
; 4 = Function trace
; 5 = Function trace + time stamp
; 6 = Function trace + time stamp + timing
; 7 = Function trace + time stamp + timing + process id (Win32)
; Default = 0
ApiTrace = 0
;——————————————————————————
; IfhTrace
; Description : Enable/Disable IFH trace
; Value : 0 = Trace disabled
; 1 = Trace enabled
; 2 = Trace enabled
; 3 = Trace enabled
; Default = 0
IfhTrace = 0
;——————————————————————————
; SystemTraceSys
; Description : Enable/Disable system trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceSys = 0
;——————————————————————————
; SystemTraceBip
; Description : Enable/Disable BIP trace (runtime system)
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceBip = 0
;——————————————————————————
; SystemTraceIfh
; Description : Enable/Disable IFH system trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceIfh = 0
;——————————————————————————
; SystemTraceNet
; Description : Enable/Disable network trace
; Value : 0 = Trace disabled
; Trace levels 1..7
; Default = 0
SystemTraceNet = 0
;——————————————————————————
; BipDebugLevel
; Description : BIP debug level of ECU files
; Value : 0..32767
; Default = 0
BipDebugLevel = 0
;——————————————————————————
; UbattHandling
; Description : Ubatt ON/OFF handling
; Value : 0 = Ubatt ON/OFF: No EDIABAS error
; 1 = Ubatt ON/OFF: EDIABAS error
; Default = 1
UbattHandling = 0
;——————————————————————————
; IgnitionHandling
; Description : Ignition ON/OFF handling
; Value : 0 = Ignition ON/OFF: No EDIABAS error
; 1 = Ignition ON/OFF: EDIABAS error
; Default = 1
IgnitionHandling = 0
;——————————————————————————
; TaskPriority
; Description : EDIABAS process/thread priority (only Win32/16)
; Value : 0 = Optimal EDIABAS performance = 8
; 1 = Minimal EDIABAS performance
; ..
; 10 = Maximal EDIABAS performance
; Default = 0
TaskPriority = 0
;——————————————————————————
; LoadWin32
; Description : Map EDIABAS Win16 calls to EDIABAS Win32
; Value : 0 = Win16/32 Mapping disabled (Win16—>Win16)
; 1 = Win16/32 Mapping enabled (Win16—>Win32)
; Default = 0 for Windows 9x/Me
; Default = 1 for Windows NT4/2000/XP
;LoadWin32 = 0
;——————————————————————————
; SystemResults
; Description : Enable/Disable system results (ubatt/ignition/jobstatus)
; Value : 0 = Disable system results
; 1 = Enable system results
; Default = 1
SystemResults = 1
;——————————————————————————
; RetryComm
; Description : Repeat failed communication automatically (1x)
; Value : 0 = Retry disabled
; 1 = Retry enabled (1x)
; Default = 1
RetryComm = 1
;——————————————————————————
; Simulation
; Description : Enable/Disable ECU simulation
; Value : 0 = Simulation disabled
; 1 = Simulation enabled
; Default = 0
Simulation = 0
;——————————————————————————
;
; Description : Connected diagnosis interface
; Default = OBD
Interface = STD:OBD
; Additional information (in German) :
; Bitte beachten: Der HW-Treiber fuer das Interface muss installiert sein!
; Interface = STD:OBD
; Beschreibung : Serieller Pegelwandler (Nachfolger von ADS / Anschluss an OBD-Dose)
; Installation : EDIABASHARDWAREOBDODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : OBD.ini nur benutzt wenn im Windows-Verzeichnis
; Unterstuetzung : WIN3.xx : Nein
; WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = STD:FUNK
; Beschreibung : Funk-Diagnose Interface MDA von Fa. Siemens
; Installation : keine
; INI-Datei : FUNK.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = ADS
; Beschreibung : Serieller Pegelwandler (Anschluss an Diagnose-Dose)
; Installation : EDIABASHARDWAREADSADS32ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = KBUS
; Beschreibung : Serieller Pegelwandler (Anschluss direkt an K-Bus oder I-Bus)
; Installation : EDIABASHARDWAREADSADS32ADSSETUP (nur fuer WinNT4 noetig)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = EDIC
; Beschreibung : Serielles , PCMCIA , PC-Card Interface von Fa. Softing
; Installation : EDIABASHARDWAREEDICSETUP.EXE
; INI-Datei : EDICFW.INI, EDICHW.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = EDICC
; Beschreibung : EDIC-Card C oder EDIC-Card 2 CAN-Interface von Fa. Softing
; Installation : EDIABASHARDWAREEDICSETUP.EXE
; INI-Datei : XEDICC.INI
; Unterstuetzung : WIN95,98 16-Bit : Ja
; WIN95,98 32-Bit : Ja
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Interface = STD:CAN
; Beschreibung : PCMCIA CAN-Interface CanCardX von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CANRTTP.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : ?
; Ansprechpartner: Hr. Jusko
; Telefon : +49-(0)89/382-35891 (Hotline)
; email : FLASH.SERVICE@BMW.DE (Hotline)
; Interface = STD:ADS4MOST
; Beschreibung : Most-Interfaces von Fa. Oasis
; Installation : keine (ausser Installation der Oasis-Karte)
; INI-Datei : ADS4MOST.INI
; Unterstuetzung : WIN95,98 16-Bit : ?
; WIN95,98 32-Bit : ?
; WIN NT 4.0 : Ja
; WIN XP : Ja
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de
; Interface = REMOTE
; Beschreibung : Anbindung eines EDIABAS-Interfaces ьber TCP/IP
; Installation : Anpassung der Eintrдge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : keine
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de
; Interface = REMOTE:name
; Beschreibung : Anbindung eines EDIABAS-Interfaces ьber TCP/IP
; Installation : Anpassung der Eintrдge in [TCP] auf beiden Seiten (ins.: RemoteHost, Port)
; INI-Datei : REMOTE.INI (insbesondere fьr Parallelbetrieb notwendig)
; In REMOTE.INI stehen unter [name] spezif. Einstellungen(z.B.: RemoteHost, Port)
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Ja
; WIN NT 4.0, XP : Ja
; WIN XP : Ja
; Sonderfall : Interface OPPS
; Ansprechpart.: Hr. Rowedder
; Telefon : 089 / 382-29159
; email : Michael.Rowedder@bmw.de
;——————————————————————————
; Port
; Description : IP communication port
; Value : 1000
; Description : Initialization command (normally for OPPS)
; Default =
;InitCmd0 = FE,04,00,03,01
;InitCmd1 = FD,05,00,03,01
Last edited by VWMAN; 10-17-2010 at 06:21 AM . Reason: Automerged Doublepost
Источник
Here is my write up for communicating with my BMW using cheap USB interfaces.
Background:
The protocol
BMW uses a KKL system. The K line is a bi-directional serial bus with a 10.4kbaud data rate. L line is some sort of RTS/DTS line that wakes up the modules on older cars. As such the BMW is not dierctly compatible with RS232, either in baud or signalling levels, and could damage your PC’s RS232 port if directly connected.
With the ignition on, the L Line is not needed, since the modules are already awake.
It’s called the KKL since there are 2 K lines. One for the engine and Gearbox, the other for everything else.
The car
The car in this case is a 1999 and has both the 20 pin and 16 pin OBD diagnostics.
The pinouts
The 16 pin
4 GND
5 GND
7 K line (1)(D_TXD2)
8 K Line (2)(D_TXD1)
15 L Line (Not fitted)
16 12V
The 20 Pin
1 Engine rotation speed
2 OBD2 Diagnostic
7 Oil service and inspection reset
14 12V
15 L Line
16 IGN 12V
17 K line (2) (D_TXD2)
18 Programming line (PGSP) (not fitted)
19 GND
20 K line (1) (D_TXD1)
Which connector do you need?
If you want to talk to the engine and gearbox you only need the 12V, GND and K line found on the 16 pin connector. If you want the ABS, Airbag or anything else, you need the 12V, GND, and both K lines found on the round connector. Handily both K lines can be shorted to get a simple OBD2 K USB adaptor to work.
[For those of you with pin 7 & 8 fitted on your 16 pin OBDII socket, the pins can be shorted in your USB adaptor and you don’t need the 20 pin connector. For those of you without pin 8 fitted, pin 25 on the socket X11175 (right instrument cluster connector) carries a White/Violet wire with D_TXD1 and you can add the additional wire to your OBDII port.]
The adaptors
I bought a £12 USB OBD2 adaptor (FTDI prolific based is mandatory and also common). [You don’t want the CAN (CANBUS) version for this age of car, you want a KL or KKL version (pin 7 on the 16 pin socket will be populated).]
Since you will probably want the full suite of modules I N P A software offers, you need a £6 BMW to OBD2 adaptor. This has a wire inside that shorts pins 17 and 20, and connects them to 7.
Here you can see Power and GND (4, 5, 16) are populated and pin 7 (K) pin 15 (L).
So the USB adaptor does the conversion to OBD2 KL protocol. The 16 to 20 pin connects 17 and 20 together and feeds them into the OBD2 convertor.
The software.
EDIABAS=The communication layer to the car
INPA=Module interface
NCSExpert=Programming/flashingsoftware/USB support (?)
1) Create a system restore point and backup your registry.
2) Use the Worlds Most Resiliant torrent site to download INPA.iso. It is 326MB and the only file matching that word at the time of writing.
3) Extract the iso using winrar to a folder called INPA_CD. Place it on C:.
Open the folder C:INPA_CDProgramminstallation and run setup.
Click through all the options, install INPA, EDIBAS and NCSExpert as a minimum (I left the install options as default Full Installation). When prompted, tell it you are using OBD and tick the USB to Serial box. Make sure you keep the add desktop icons ticked.
4) Complete the installation and go to C:EDIABASHardwareOBD. Open USB-OBD.pdf and follow the instructions to change the latency timer from 16ms to 1ms. Force the USB/serial adaptor to COM1.
5) Run OBDSetup.exe. Do not close the DOS box yet. If it says «Warning, some values do not match, malfunction can occur» then the registry needs to be hand edited until those values match. It’s DWORD values like buffer sizes and FIFO settings. Run OBDSetup again to verify all the warnings have gone away. Reboot if you have changed the registry.
6) [url=hXXp://vlaurie.com/computers2/Articles/environment.htm]Add the Environment variable[/url]C:EDIABASBIN to your system.
7) Open the file OBD.ini from C:EDIABASBIN add in the UBAT item manually. Check the Hardware=USB
Code: Select all
[OBD]
Port=Com1
Hardware=USB
RETRY=ON
UBAT=OFFCopy the file OBD.ini from C:EDIABASBIN to C:Windows
You have now installed the EDIBAS communication handler, configured all of it’s FIFO settings, and installed the INPA «whitescreen» framework.
Now you need to install the guts of INPA.
Open C:INPA_CDReferenzINSTALL and run Installprog.exe. Chose the English language and install BMW Group Rectification programs UK. Select Upgrade or prefereably Complete when possible. Complete and exit the installation program.
Now when you run INPA from the desktop icon you should see INPA and EDIABAS load, and along the bottom of INPA you can select your car and the modules therein.
9)Wah! It’s not working?
If you get EDIABAS initialising errors you need to check the registry DWORDS above, and the USB/Serial latency timer.
If you get INPA IFH-0018 INITIALIZATION ERROR then check the com port.
Download a file called INPA_FAQ for detailed error code help.
Use Teraterm to open COM1 at 9600 baud to see if you can echo characters to prove you are connected to the car.
Use the Search button before posting newbie questions about hard tops and fitting kits, footwell speaker amps, water in the boot, hood maintainance and those horrific angel eyes. We get like 10 threads a week on the same subject, it’s obvious that you haven’t searched.
|
09-01-2012, 05:01 PM
|
#1 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Help with INPA !!! Did the INPA software install to the tee from vassilov’s DIY. I keep getting I have windows 7 starter edition. Anyone successfully done this with starter edition? Or do I need to install the pro edition?? __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
09-01-2012, 06:09 PM
|
#2 |
|
Captain
Drives: 2010 535i M Sport Join Date: May 2008 Location: Ellicott City, MD |
Verify that your environment variables are set correctly (no typos) and that your PATH statement is correct. __________________ 2010 535i M Sport — Platinum Gray/Dakota Black/Anthracite Bamboo |
|
09-01-2012, 06:40 PM
|
#3 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Quote: Originally Posted by DJtoad Verify that your environment variables are set correctly (no typos) and that your PATH statement is correct. Done. Still have same issue __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
09-01-2012, 11:59 PM
|
#4 |
|
Lieutenant
Drives: 2008 135i Coupe Join Date: Jan 2012 Location: Cleveland, TN |
Anybody still around that feels like volunteering some time on this to help a few people out. I’m having issues also. I thought it was the cheap ebay cable so I purchased the good one and still having problems reading the airbag and doing things in ncs. __________________ 2008 135i — MHD/JB4, MS DP’s, AMS IC, UI CAI, CDV delete, M3 control arms/Links, RE Toe Link, ECS Trailing Arm, M3 rear SF & Trans bushings, SS brake lines, Michelin PSS. |
|
09-02-2012, 06:39 AM
|
#5 |
|
Captain
Drives: 2010 535i M Sport Join Date: May 2008 Location: Ellicott City, MD |
Quote:
Originally Posted by Chrisred Done. Still have same issue What year is your car and what cable did you purchase? If your car was manufactured in 3/2009 or later you need to make sure your cable has pin 8 disconnected. Did you purchase one of the recommended cables (not all of the cheap knock-off cables will work)? If so and the cable drivers have been installed, you’re sure your environment variables are correct, the s/w was installed in the correct locations, etc. you’re probably better off posting about your issue in the coding subforum here and/or in one of the several other forums dedicated to BMW coding. BTW, I don’t think your problem has anything to do with running Windows 7 Starter Edition. __________________ 2010 535i M Sport — Platinum Gray/Dakota Black/Anthracite Bamboo |
|
09-02-2012, 10:06 AM
|
#6 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Cable was purchased by a buddy of mine from china. It’s a clear/see thru looking cable and it comes with a small cd but I didn’t install drivers of it as the DIY says not too. So I just plugged in USB and followed DIY Car built is 1/2009. So it’s either the windows 7 starter edition or maybe I should install drivers from that cd… __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
09-02-2012, 12:00 PM
|
#7 |
|
Captain
Drives: 2010 535i M Sport Join Date: May 2008 Location: Ellicott City, MD |
Quote:
Originally Posted by Chrisred …. but I didn’t install drivers of it as the DIY says not too. So I just plugged in USB and followed DIY If you’re using vassilov’s DIY, that’s not what it says:
__________________ 2010 535i M Sport — Platinum Gray/Dakota Black/Anthracite Bamboo |
|
09-02-2012, 12:49 PM
|
#8 |
|
Second Lieutenant
Drives: N54 335xi Join Date: Feb 2011 Location: Cleveland, OH |
You will need the drivers in order to get the COM port. It’s critical that you see the serial device for the cable in you device manager and that its assigned COM port is the one defined in the OBD.ini file mentioned in the DIY. |
|
09-02-2012, 01:12 PM
|
#9 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
[QUOTE=pinky_and_me]You will need the drivers in order to get the COM port. It’s critical that you see the serial device for the cable in you device manager and that its assigned COM port is the one defined in the OBD.ini file mentioned I’ll try the cd install now…. __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
09-02-2012, 02:16 PM
|
#10 |
|
Mad Linux Guru On The Loose
Drives: 2008 335i Sedan, 2023 M3 Join Date: Aug 2009 Location: Chicago, IL |
In the majority of the cases, you might be able to get away with the FTDI drivers for USB to Serial interfaces. That should be your last resort if no other driver works: http://www.ftdichip.com/Drivers/VCP.htm __________________ 6MT | COBB | AR | AE | Forge DV | HPF | P3 Gauge | Hybrid Intake | O.S.Giken TCD | All M3 bits | TCKLine | StopTech | UUC | ER | SPEC |
|
09-02-2012, 05:04 PM
|
#11 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Cd drivers installed. Still get that error msg……I’m gonna upgrade to win 7 pro and see what happens. I’ll try those last resort drivers. Thanks Vasillalov __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
09-02-2012, 11:05 PM
|
#12 |
|
Captain
Drives: e90 335 Join Date: Feb 2011 Location: okc |
also make sure you set to bypass map and turn off any code clearing. that’s what i usually forget. |
|
10-01-2012, 10:42 PM
|
#13 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Installed win7 ultimate edition and did DIY over. It connects and I can choose MSD80 N54 engine. But when I go and press SHIFT F4 to choose injectors, I get error#100 sys-0010: initialization error. I checked the FAQ guide and I really don’t understand what it says….something about connecting controller __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
10-02-2012, 01:31 AM
|
#14 |
|
Brigadier General Drives: it has 4 wheels Join Date: Jul 2008 Location: San Francisco |
Is it possible you have a faulty Cable? |
|
10-02-2012, 06:52 AM
|
#15 |
|
Drives: 335i Join Date: Jun 2007 Location: US |
I offered to help OP but he declined so there is no helping him. |
|
10-02-2012, 10:56 AM
|
#16 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Quote: Originally Posted by cn555ic I offered to help OP but he declined so there is no helping him. Lol. I just installed the program again last night. Then got excited when i saw that it did connect finally!!! Thanks for the offer but all my cpu settings are good as it wouldn’t connect right??? If u want u can take a look…..faulty cable might be reason…. __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
10-02-2012, 12:29 PM
|
#17 |
|
Drives: 335i Join Date: Jun 2007 Location: US |
What color is the circuit board of your cable. If your cable has a blue circuit board instead of the white or green one, Then it’s your cable for sure. The blue circuit board cables floating around that people are selling are defective and will never work. I am still surprised vendors are still selling this shit. |
|
10-02-2012, 04:13 PM
|
#18 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Quote: Originally Posted by cn555ic What color is the circuit board of your cable. If your cable has a blue circuit board instead of the white or green one, Then it’s your cable for sure. The blue circuit board cables floating around that people are selling are defective and will never work. I am still surprised vendors are still selling this shit. Green __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
10-02-2012, 05:48 PM
|
#19 |
|
Drives: 335i Join Date: Jun 2007 Location: US |
If its green then it should be good. |
|
10-02-2012, 08:39 PM
|
#20 |
|
Captain
Drives: BMW 335xi coupe Join Date: Jan 2010 Location: Montreal, Canada |
Just to be sure: JB4 to map 0 and all guage high jacking to default….right?? __________________ JB4 Trebila tuned cp-e IC AMS exhaust BMS DCI AR DP’s METH RB TURBO |
|
10-02-2012, 09:11 PM
|
#21 |
|
Drives: 335i Join Date: Jun 2007 Location: US |
Yes map 0 |
|
10-15-2012, 03:17 AM
|
#22 |
|
Major
Drives: BMW 3 series Join Date: Sep 2008 Location: Irvine |
sorry to revive this thread, But I am experiencing the same error/problem. SYS 0010: INITIALIZATION error. Right when I hit the injector screen. I already tried Vasillalov’s and cn555ic package. Both did not work. I’m pretty computer literate so I’m positive I got everything set up right. My cable is also from china, green circuit board, clear see-through casing. How did you guys get it to work? |
Here is my write up for communicating with my BMW using cheap USB interfaces.
Background:
The protocol
BMW uses a KKL system. The K line is a bi-directional serial bus with a 10.4kbaud data rate. L line is some sort of RTS/DTS line that wakes up the modules on older cars. As such the BMW is not dierctly compatible with RS232, either in baud or signalling levels, and could damage your PC’s RS232 port if directly connected.
With the ignition on, the L Line is not needed, since the modules are already awake.
It’s called the KKL since there are 2 K lines. One for the engine and Gearbox, the other for everything else.
The car
The car in this case is a 1999 and has both the 20 pin and 16 pin OBD diagnostics.
The pinouts
The 16 pin
4 GND
5 GND
7 K line (1)(D_TXD2)
8 K Line (2)(D_TXD1)
15 L Line (Not fitted)
16 12V
The 20 Pin
1 Engine rotation speed
2 OBD2 Diagnostic
7 Oil service and inspection reset
14 12V
15 L Line
16 IGN 12V
17 K line (2) (D_TXD2)
18 Programming line (PGSP) (not fitted)
19 GND
20 K line (1) (D_TXD1)
Which connector do you need?
If you want to talk to the engine and gearbox you only need the 12V, GND and K line found on the 16 pin connector. If you want the ABS, Airbag or anything else, you need the 12V, GND, and both K lines found on the round connector. Handily both K lines can be shorted to get a simple OBD2 K USB adaptor to work.
[For those of you with pin 7 & 8 fitted on your 16 pin OBDII socket, the pins can be shorted in your USB adaptor and you don’t need the 20 pin connector. For those of you without pin 8 fitted, pin 25 on the socket X11175 (right instrument cluster connector) carries a White/Violet wire with D_TXD1 and you can add the additional wire to your OBDII port.]
The adaptors
I bought a £12 USB OBD2 adaptor (FTDI prolific based is mandatory and also common). [You don’t want the CAN (CANBUS) version for this age of car, you want a KL or KKL version (pin 7 on the 16 pin socket will be populated).]
Since you will probably want the full suite of modules I N P A software offers, you need a £6 BMW to OBD2 adaptor. This has a wire inside that shorts pins 17 and 20, and connects them to 7.
Here you can see Power and GND (4, 5, 16) are populated and pin 7 (K) pin 15 (L).
So the USB adaptor does the conversion to OBD2 KL protocol. The 16 to 20 pin connects 17 and 20 together and feeds them into the OBD2 convertor.
The software.
EDIABAS=The communication layer to the car
INPA=Module interface
NCSExpert=Programming/flashingsoftware/USB support (?)
1) Create a system restore point and backup your registry.
2) Use the Worlds Most Resiliant torrent site to download INPA.iso. It is 326MB and the only file matching that word at the time of writing.
3) Extract the iso using winrar to a folder called INPA_CD. Place it on C:.
Open the folder C:INPA_CDProgramminstallation and run setup.
Click through all the options, install INPA, EDIBAS and NCSExpert as a minimum (I left the install options as default Full Installation). When prompted, tell it you are using OBD and tick the USB to Serial box. Make sure you keep the add desktop icons ticked.
4) Complete the installation and go to C:EDIABASHardwareOBD. Open USB-OBD.pdf and follow the instructions to change the latency timer from 16ms to 1ms. Force the USB/serial adaptor to COM1.
5) Run OBDSetup.exe. Do not close the DOS box yet. If it says «Warning, some values do not match, malfunction can occur» then the registry needs to be hand edited until those values match. It’s DWORD values like buffer sizes and FIFO settings. Run OBDSetup again to verify all the warnings have gone away. Reboot if you have changed the registry.
6) [url=hXXp://vlaurie.com/computers2/Articles/environment.htm]Add the Environment variable[/url]C:EDIABASBIN to your system.
7) Open the file OBD.ini from C:EDIABASBIN add in the UBAT item manually. Check the Hardware=USB
Code: Select all
[OBD]
Port=Com1
Hardware=USB
RETRY=ON
UBAT=OFFCopy the file OBD.ini from C:EDIABASBIN to C:Windows
You have now installed the EDIBAS communication handler, configured all of it’s FIFO settings, and installed the INPA «whitescreen» framework.
Now you need to install the guts of INPA.
Open C:INPA_CDReferenzINSTALL and run Installprog.exe. Chose the English language and install BMW Group Rectification programs UK. Select Upgrade or prefereably Complete when possible. Complete and exit the installation program.
Now when you run INPA from the desktop icon you should see INPA and EDIABAS load, and along the bottom of INPA you can select your car and the modules therein.
9)Wah! It’s not working?
If you get EDIABAS initialising errors you need to check the registry DWORDS above, and the USB/Serial latency timer.
If you get INPA IFH-0018 INITIALIZATION ERROR then check the com port.
Download a file called INPA_FAQ for detailed error code help.
Use Teraterm to open COM1 at 9600 baud to see if you can echo characters to prove you are connected to the car.
Use the Search button before posting newbie questions about hard tops and fitting kits, footwell speaker amps, water in the boot, hood maintainance and those horrific angel eyes. We get like 10 threads a week on the same subject, it’s obvious that you haven’t searched.
Location Offline
Junior Member
Reputation:
0
Thanks Given: 23
Thanks Received: 13 (6 Posts)
Posts:
44
Threads:
14
Joined: Aug 2013
10
07-27-2017, 03:49 PM
Anyone have any luck with this. I tried and have failed
Thanks given by:
meiguang
Location Offline
Senior Member
Reputation:
12
Thanks Given: 106
Thanks Received: 92 (53 Posts)
Posts:
224
Threads:
2
Joined: Mar 2014
11
09-11-2017, 06:23 AM
(07-27-2017, 03:49 PM)Garsam85 Wrote: Anyone have any luck with this. I tried and have failed
So do I, it won’t connect, but don’t loss hope….hihi
Thanks given by:
Jcorb2987
Location Offline
Junior Member
Reputation:
3
Thanks Given: 29
Thanks Received: 14 (9 Posts)
Posts:
25
Threads:
0
Joined: Oct 2017
12
11-02-2017, 08:05 PM
(This post was last modified: 11-02-2017, 08:54 PM by Jcorb2987.)
(09-11-2017, 06:23 AM)meiguang Wrote:
(07-27-2017, 03:49 PM)Garsam85 Wrote: Anyone have any luck with this. I tried and have failed
So do I, it won’t connect, but don’t loss hope….hihi
hey guys, i got a jbox2. and after many hours. i have it scanning the full car in ISTA-D working perfectly. i dont have the terminal 15 and 30 voltages reading but i got the vehicle map up and scanned all codes from all modules. what a PAIN if you guys still need help with this let me know ill try to get a good guide together tonight for what i had to do.
just an update. i was able to pull info for f10 newer model, just tried an e70 and the jbox tries to communicate but fails to identify the vehicle but still working on f10. this makes me sad.
Thanks given by:
gtitonta 
Location Offline
Senior Member
Reputation:
1,300
Thanks Given: 435
Thanks Received: 1794 (72 Posts)
Posts:
247
Threads:
62
Joined: Mar 2018
13
04-06-2018, 07:17 PM
(11-02-2017, 08:05 PM)Jcorb2987 Wrote:
(09-11-2017, 06:23 AM)meiguang Wrote:
(07-27-2017, 03:49 PM)Garsam85 Wrote: Anyone have any luck with this. I tried and have failed
So do I, it won’t connect, but don’t loss hope….hihi
hey guys, i got a jbox2. and after many hours. i have it scanning the full car in ISTA-D working perfectly. i dont have the terminal 15 and 30 voltages reading but i got the vehicle map up and scanned all codes from all modules. what a PAIN if you guys still need help with this let me know ill try to get a good guide together tonight for what i had to do.
just an update. i was able to pull info for f10 newer model, just tried an e70 and the jbox tries to communicate but fails to identify the vehicle but still working on f10. this makes me sad.
I also have jbox2. How exactly did you install ISTA-D/P? I have been struggling too. Could you please tell me how you did it? Did you use vmware? I have 5 different OEM software in my laptop now. Thanks a lot!
Thanks given by:
kirukisu
Location Offline
Senior Member
Reputation:
141
Thanks Given: 398
Thanks Received: 310 (101 Posts)
Posts:
680
Threads:
140
Joined: Aug 2017
14
08-18-2018, 01:26 AM
(This post was last modified: 08-18-2018, 01:29 AM by kirukisu.)
(10-19-2016, 09:55 AM)Gini Wrote: Hi guys,
I can help via Teamviewer if needed1. Install your Passthru driver
2. Install BMW PTT Configuration Tool available here http://mhhauto.com/Thread-BMW-INPA-PROGM…-Interface
3. Run BMW PTT, select your Passthru driver and OK
4. Copy the content of C:Program Files (x86)BMW AGPassThruD to C:EDIABASBin
!!! DO NOT OVERWRITE EXISTING FILES !!!
5. Modify C:EDIABASBINEDIABAS.INI -> Interface = STD
ASSTHRUDThis is how it ends, any tips why?
—————————
EDIABAS-Error
—————————
ApiInit: Error #28
IFH-0018: INITIALIZATION ERROR
API initialization error
No API calls possible !
—————————
OK
—————————
—————————
EDIABAS-Error
—————————
ApiJob: API initialization error
No API calls possible !
Continue script processing ?
—————————
Yes No
—————————
Thanks given by:
morek0
Location Offline
Junior Member
Reputation:
35
Thanks Given: 50
Thanks Received: 94 (16 Posts)
Posts:
87
Threads:
11
Joined: Aug 2016
15
08-30-2018, 09:52 PM
(This post was last modified: 08-30-2018, 09:52 PM by morek0.)
What tool do you use?
Thanks given by:
kirukisu
Location Offline
Senior Member
Reputation:
141
Thanks Given: 398
Thanks Received: 310 (101 Posts)
Posts:
680
Threads:
140
Joined: Aug 2017
16
08-31-2018, 10:59 PM
(08-30-2018, 09:52 PM)morek0 Wrote: What tool do you use?
Me? VAS5054 xD
Thanks given by:
morek0
Location Offline
Junior Member
Reputation:
35
Thanks Given: 50
Thanks Received: 94 (16 Posts)
Posts:
87
Threads:
11
Joined: Aug 2016
17
09-03-2018, 11:09 PM
Try this:
Connect your tool and make sure is detected by your system correctly. Then run Passthru Configuration (I’m using version 2.0.9.4), choose your tool from list and click on Lauch config. Tool. In your passthru tool manager make a test and ensure that connection is established. Close the passthru tool manager. And before opening any diagnostic software run program called Easy Connect Utility, in MODE choose PASSTHRU and click check. If battery, ignition and voltage is detected then INPA, ISTA and other software should work.
Coping files from BMW AG folder to EDIABAS folder isn’t really nesseary, mine machine works without it.
papiarea
Location Offline
Junior Member
Reputation:
1
Thanks Given: 38
Thanks Received: 26 (16 Posts)
Posts:
146
Threads:
18
Joined: Feb 2018
18
09-05-2018, 06:54 AM
(10-19-2016, 09:55 AM)Gini Wrote: Hi guys,
I can help via Teamviewer if needed1. Install your Passthru driver
2. Install BMW PTT Configuration Tool available here http://mhhauto.com/Thread-BMW-INPA-PROGM…-Interface
3. Run BMW PTT, select your Passthru driver and OK
4. Copy the content of C:Program Files (x86)BMW AGPassThruD to C:EDIABASBin
!!! DO NOT OVERWRITE EXISTING FILES !!!
5. Modify C:EDIABASBINEDIABAS.INI -> Interface = STD
I have a jdiag 2534 can u make it work on my ista d and ista p?
Its working fine on my ista+
Thanks given by: