BMW AUTO FORUM: Problema instalare DIS - BMW AUTO FORUM

Jump to content

Page 1 of 1

Problema instalare DIS Nu vede DIAG HEAD Emulator

#1 User is offline   Florinkim Icon

  • Nou venit
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 16-March 11

Posted 18 March 2011 - 12:25 PM

Am o problema cu dis, in momentul cand apare imagine din dis cu bmw, diag head emulator se conecteaza la alt ip, adica apare ceva de genul:
Received CMD_MT_CONNECT
Connecting via TCP to 192.168.68.32:1111
Received CMD_MT CONNECTEDHOST
gt1ap
Sending CMD_MT_KEEPALIVE
Received RESP_KEEPALIVE

Aceasta eroare apare si cu interfata in usb si fara, unde naibi gresesc ca la cat sunt de ofticat nu imi dau seama. Multumesc

#2 User is offline   DanS Icon

  • Pasyonat
  • Icon
  • Group: Admin
  • Posts: 1,425
  • Joined: 06-September 09
  • Location:Houston Tx, PH RO

Posted 18 March 2011 - 02:02 PM

View PostFlorinkim, on 18 March 2011 - 02:25 AM, said:

Am o problema cu dis, in momentul cand apare imagine din dis cu bmw, diag head emulator se conecteaza la alt ip, adica apare ceva de genul:
Received CMD_MT_CONNECT
Connecting via TCP to 192.168.68.32:1111
Received CMD_MT CONNECTEDHOST
gt1ap
Sending CMD_MT_KEEPALIVE
Received RESP_KEEPALIVE

Aceasta eroare apare si cu interfata in usb si fara, unde naibi gresesc ca la cat sunt de ofticat nu imi dau seama. Multumesc

Ai scris IP-ul si portul recomandat in Ediabas.ini?
Daca da, atunci asigura-te ca setarile de retea in VMWare sunt ok ( depinde de ce folosesti...VMWare Player are configurari putin diferite fata de Workstation...desi fac cam acelasi lucru). DIS-ul l-ai instalat tu in masina virtuala folosind Kit-ul disponibil pe torrenti, sau doar ai deschis o imagine deja existenta?

#3 User is offline   Florinkim Icon

  • Nou venit
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 16-March 11

Posted 18 March 2011 - 05:55 PM

Ip, este configurat cum trebuie in edibas, pleaca normal vmware pana deschide imaginea cu masina, apoi se conecteaza la Ip respectiv diag head si apar erorile respective, am avut imaginea respectiva pentru dis nu am instalat eu, folosesc work station pentru masina virtuala. setarile in vmware spun ca ar fi facute cum trebuie dar nu stiu ce am omis, imi ramane sa pun imaginile cu setarile de retea. Ca concluzie finala pentru diagnoza la auto merge perfect imi da erorile care trebuie, asa cum le da si inpa, dar nu inteleg de unde apare IP asta.

#4 User is offline   DanS Icon

  • Pasyonat
  • Icon
  • Group: Admin
  • Posts: 1,425
  • Joined: 06-September 09
  • Location:Houston Tx, PH RO

Posted 18 March 2011 - 07:46 PM

View PostFlorinkim, on 18 March 2011 - 07:55 AM, said:

Ip, este configurat cum trebuie in edibas, pleaca normal vmware pana deschide imaginea cu masina, apoi se conecteaza la Ip respectiv diag head si apar erorile respective, am avut imaginea respectiva pentru dis nu am instalat eu, folosesc work station pentru masina virtuala. setarile in vmware spun ca ar fi facute cum trebuie dar nu stiu ce am omis, imi ramane sa pun imaginile cu setarile de retea. Ca concluzie finala pentru diagnoza la auto merge perfect imi da erorile care trebuie, asa cum le da si inpa, dar nu inteleg de unde apare IP asta.


Dupa IP trecut in Ediabas.ini, ai trecut si acest port..Am vazut ceva DIY pe alte forumuri unde baietii cam asa le aveau facute configuratiile, dar banuiesc ca la INPA nu conteaza fiindca astia se tot conversau pe INPA ala... Parerea mea este ca e aiurea dar nu ma pricep deloc la diagnoza asa ca iti arat cum am gasit eu un ediabas.ini configurat pe undeva unde se vorbea de DIS in masina virtuala:
El cam asa tre' sa fie se pare (vezi acolo unde am scris cu rosu in special).
;=============================================================================
;EDIABAS 6.4.7 Configuration
[Configuration]
;=============================================================================

;-----------------------------------------------------------------------------
; EcuPath
; Description : ECU file path
; Default = .
EcuPath =C:\EDIABAS\ECU

;-----------------------------------------------------------------------------
; SimulationPath
; Description : Simulation file path
; Default = .
SimulationPath =C:\EDIABAS\SIMULATION

;-----------------------------------------------------------------------------
; TracePath
; Description : Trace file path
; Default = .
TracePath =C:\EDIABAS\TRACE

;-----------------------------------------------------------------------------
; CodeMapping
; Description : Character mapping file path
; Default = .
;CodeMapping = C:\EDIABAS\BIN\ansi2oem.tab

;-----------------------------------------------------------------------------
; TraceSize
; Description : Maximum size of each trace file [KB]
; Value : 0..32767
; Default = 1024
TraceSize = 32767

;-----------------------------------------------------------------------------
; 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 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
IfhTrace =0

;-----------------------------------------------------------------------------
; IfhnTrace
; Description : Enable/Disable IFH network trace (with XREMOTE)
; Value : 0 = Trace disabled
; 1 = User trace
; 2 = User trace + interface
; 3 = User trace + interface + time stamp
; Default = 0
;IfhnTrace = 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

;-----------------------------------------------------------------------------
; ClampHandling
; Description : automatic check of clamps for Ubatt and Ignition
; Value : 0 = no automatic clamp check with send_and_receive
; 1 = automatic clamp check with send_and_receive
; Default = 1
;ClampHandling = 1

;-----------------------------------------------------------------------------
; 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 = 1

;-----------------------------------------------------------------------------
; 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

;-----------------------------------------------------------------------------
; 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 : \EDIABAS\HARDWARE\OBD\ODBSETUP (nur noetig fuer WIN NT4, WIN 2000, WIN XP)
; INI-Datei : Suchreihenfolge analog zu EDIABAS.ini
; 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 : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (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 : \EDIABAS\HARDWARE\ADS\ADS32\ADSSETUP (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 : \EDIABAS\HARDWARE\EDIC\SETUP.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 : \EDIABAS\HARDWARE\EDIC\SETUP.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/XL von Fa. Vector
; Installation : keine (ausser Installation der CAN-Karte)
; INI-Datei : CAN32.INI
; Unterstuetzung : WIN95,98 16-Bit : Nein
; WIN95,98 32-Bit : Nein
; WIN NT 4.0 : Ja
; WIN XP : Ja
; 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 =192.168.68.1

;-----------------------------------------------------------------------------
; Port
; Description : IP communication port
; Value : 1000 < port < 30000
; Default =
Port = 6801

;-----------------------------------------------------------------------------
;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
;=============================================================================


In rest, citeste asta (am mai adaugat eu 3 poze)

#5 User is offline   Florinkim Icon

  • Nou venit
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 16-March 11

Posted 18 March 2011 - 09:01 PM

Da asa sunt, dar banuiesc in mintea mea seaca ca alta ar fi problema:
1. Cred din cat am citit pe net ca ip cu 32 la sfarsit este generat automat de vmware in cazul in care nu ai licenta in firea ei, scrie acest lucru la configurarea masinii virtuale la SSS, in cazul in care nu este configurata cum trebuie se foloseshte ip: 192.168.68.32 acest ip il poate recunoaste reteaua in cazul in care este o greseala la configurarea retelei.
2. Am omis eu ceva si nu stiu exact unde?
Multumesc pentru ajutor, o Sa incerc sa pun SSS progman din nou, de la 0 si pe urma iti arat daca este greseala de network configuration in vmware, si cum este recunoscuta interfata cu ip cu 32 la sfarsit.
Aici este instalare pas cu pas SSS Progman, cand l-am pus prima data mi-a iesit din prima, succes.

Attached File(s)


#6 User is offline   DanS Icon

  • Pasyonat
  • Icon
  • Group: Admin
  • Posts: 1,425
  • Joined: 06-September 09
  • Location:Houston Tx, PH RO

Posted 18 March 2011 - 09:35 PM

Ok
Nu prea inteleg ce vrei sa zici cu SSS si cu licentele de VMW, dar sper sa reusesti. Chestia cu 32 la sfarsit banuiesc ca nu are nici o treaba cu ce ai tu sau cu ce crezi c-ar fi. Am citit si eu chestia aia pusa de "roadrunner-ul" @randomy pe bimmerf. dar care de fapt nu-i apartine lui ci altuia care cred c-a fost admin pe ecu...Super realizate si documentate DIY's, dar provenienta nu are importanta in acest caz B)/> .
Vezi poate iti foloseste la DIS link-ul asta ce provine tot din seria thread-urilor lui
http://forums.bimmer...d.php?t=1312104

Bafta si astept sa ne spui unde a fost greseala. Sigur foloseste cuiva din comunitate care poate are aceeasi problema

#7 User is offline   DanS Icon

  • Pasyonat
  • Icon
  • Group: Admin
  • Posts: 1,425
  • Joined: 06-September 09
  • Location:Houston Tx, PH RO

Posted 19 March 2011 - 03:24 PM

Uitasem...in VMW, conexiunea este configurata "host only" sau "bridged" ?

#8 User is offline   Florinkim Icon

  • Nou venit
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 16-March 11

Posted 22 March 2011 - 09:45 AM

In vmware este configurata pe host-only.Acum incerc sa configurez sss si dupa ce il instalez poate vad si unde naibi am gresit. O sa vad exact si o sa o pun aici.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users