Settings in GT1/DIS to use the INPA Interface ?

[MPower2007]

Hi,

does anybody know the settings in GT1/DIS to use the same diagnose interface for INPA/Ediabas, without use the expensive diagnostic head ?

(Sorry for my English...)


Regards

[nuvola rossa]

I know how to do it, but I need something in change:

WinKFP, NFS, NCS Expert and password, fully working...

[kirbykirbykirby]

Hey, Nuvola...how would you do it? I have some nice app's to trade ;) Including EDIABAS, Gt1 V29-49. and a few goodies.

[eleet]

It was pretty clear over there, if you have that thread you know everything you need.

[kirbykirbykirby]

Could you post the thread? I'd be more then happy to help ;) I just need something to go on, haha.

[Daved]

I know how to do it, but I need something in change:

WinKFP, NFS, NCS Expert and password, fully working...
Please don't make this look like a warez site where people trade...

I was hoping everyone would help everything without waiting anything in return.

[vpower17]

@MPower2007
On the DIS Mainscreen you must put Strg+Alt+F1 to go to the first sco console.
Login as root and pwd "password". Then change to the directory /etc and modify (vi ediabas.ini) the file.
[TCP]
RemoteHost = Diaghead
Port = 6801
Then extend the file /etc/hosts with following information:
"192.168.68.30 Diaghead"
after reboot, go to the console and type
/usr/ediabas/bin/apitest"
if it runs and give you a menu then the comminucation between ediabas-SCO and ifhsrv is ok.

@ eleet
What settings must be done to connect DIS to the SCO ediabas ? DIS -> Services -> Settung up a connection -> Free Diagnostic heads are empty. Please help me - Thx

Sorry for my bad english.

[vpower17]

Hello MPower2007

Sorry this was the wrong IP. In /etc/hosts must stand
"192.168.68.1 Diaghead" and your windows system with ifhsrv running must have this ip. After the change you can "ping Diaghead" and execute apitest.

What for a Interface you are using ?

@all other
What settings must be done to connect DIS to the local ediabas - In DIS Administration - Free Diagnostic heads are empty. Please help - Thx

[vpower17]

Can you ping to 192.168.68.1 / Diaghead ?

[eleet]

Is nobody there who have experience and tell us the correct settings (maybe a "how to") to use the "inpa" interface, without waiting anything in return ... ?

Thx

Just put the IP address in ediabas.ini instead of 'Diaghead'

I am writing some articles to help with these simple things. Please send me an email.

[kirbykirbykirby]

Rapidshare deleted. :(

[eleet]

Thanks Mpower, it was nice to get the articles I posted on the other board back.

[moja750hamann]

Hi,

does anybody know the settings in GT1/DIS to use the same diagnose interface for INPA/Ediabas, without use the expensive diagnostic head ?

(Sorry for my English...)


Regards


Hallo

Weist du was es bedeutet wd(1) now is using polled interface.Bei der Instalation der Basi CD mit VMware.Was mus ich umbedingt beachten.

Gruß

Christoph

[Vince S.]

I know how to do it, but I need something in change:

WinKFP, NFS, NCS Expert and password, fully working...

I take it that you know your way around WinKFP, NFS, NCS Expert ?

[saulyss]

Could you reshare or send private to email OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

Thank's in advance

[dfitz21]

It was pretty clear over there, if you have that thread you know everything you need.

Any chance of getting a copy of that post? dfitz21@gmail.com

Thanks
Dan

[parkjw]

Thanks!!

[seans1]

I know how to do it, but I need something in change:

WinKFP, NFS, NCS Expert and password, fully working...
Please private email with info regarding this ...Thank you in advance.

[seans1]

Could you please private email me the link for this? Thank you in advance
seanshultz@hotmail.com

[Dudeldi]

Anybody use an ADS Interface for DIS?

i need so much help ....

sincerly

[HugoE38]

Please somebody send me link or file OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

Thanks.
engine387@gmail.com

[fraatti]

I would like that have that zipped thread also..

thanks,
fraatti@suomi24.fi

[ashamlawi1]

Can you share the Zip file OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip as well

I would really apreciate it.
Abed.Shamlawi@Y-Consult.com

[puschel]

Hey, can anybody how got this *.zip re-up it on rapidshare?
Trading per Mail is awful...

Thanks,
Puschel

[kevintuggy]

after doing this insruction. On the DIS Mainscreen you must put Strg+Alt+F1 to go to the first sco console.
Login as root and pwd "password". i get and error incorrect logon can someone help me please.

[thinman]

Hi!

Could you please send me the OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip file to steve_k2400 [at] yahoo.co.uk
Thanks in advance!

Steve (Thinman)

[umba]

After a new install following the instructions (Article: Getting started with VMWare) my "apitest" works fine and the LED's on the DIS main screen lighting up ;-) !!!

Thx to " ecubb.bmwecu.org/board/index.php "

Have you managed your DIS to work with ADS or ODB interface through IFH Service?

P.S. could someone share OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip on rapidshare or send it to email umba@bk.ru thanks.

[bmwtechie]

NET:0015 : Host Not found,

Anyone know what this means, i have IFH server running, i can ping 192.168.68.1 and 192.168.68.30?

Any help would be appreciated?

[kevintuggy]

how do i login as root on vmware, please help


@MPower2007
On the DIS Mainscreen you must put Strg+Alt+F1 to go to the first sco console.
Login as root and pwd "password". Then change to the directory /etc and modify (vi ediabas.ini) the file.
[TCP]
RemoteHost = Diaghead
Port = 6801
Then extend the file /etc/hosts with following information:
"192.168.68.30 Diaghead"
after reboot, go to the console and type
/usr/ediabas/bin/apitest"
if it runs and give you a menu then the comminucation between ediabas-SCO and ifhsrv is ok.

@ eleet
What settings must be done to connect DIS to the SCO ediabas ? DIS -> Services -> Settung up a connection -> Free Diagnostic heads are empty. Please help me - Thx

Sorry for my bad english.

[kevintuggy]

how do i login as root my email is kbeckford_02@hotmail.com


@ vpower17

Thanks for this... ;-)

[wiki]

could anyone of u guys also send me the OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip file.
thanks a lot

[lechuk]

Please reshare or send private to email OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

Thanks

[schulrog]

Hi all,

I'm looking for the DIS software.. any help is much appreciated! please PM me:)

[wissoaj]

hi i tried the whole prossess i didnt know where to put the etc/host file and i couldnt login on the dis main screen i tried to login with root as login and password as password but still nothing could somebody please help me and if somebody can send me detailed insrtructions by email or anything i will be verry greatfull and thanks

[mike19730]

I have a copy of the thread in www 318ti org
where everything is described, but I need help in settings VMware and GT1/DIS to work with the Inpa/Ediabas Interface....

hello, have anybody this file or can me tell what title this file at 318ti.or have?
kind regards

i mean this file:
hxxp://rapidshare.com/files/47861612/OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

[tobiasvdp]

hi guys,

somehow i don´t seem to get this whole thing to work, my config is working inpa 5.02 with ediabas 6.4.7 running xp sp3 and vmware 6.5.1. gt1/dis installation has been done with the shoulders method (thanks a lot for this comprehensive documentation)

pinging the host outside the vmware session works, ifhrsrv32 shows the ip adress of the vmware machine apitest shows me the menu, but when trying to use the diagnose button, dis freezes, and needs an init6... ip addresses and ports have been entered on both ini files and the hosts file, do i need to make any changes inside the dis administration screen? (konfig-system, konfig-diagnosekopf?)

thanks a lot for your support guys...

Cheers

[flink182]

Hey i need help too...

I cant login to sco after press CTRL ALT F1, Root and password - it says login incorrect :(

Could anybody help?

[gabileung]

Hi everyone
I need help too
anyone got the instructions?

I'm cant even get the interface working with the expresscard com port on my vista.......

also anyone here is memer of bmwecu.org ? I reckon there are info about this. can someone invite me into this forum ?
thanks

[flink182]

Hi everyone
I need help too
anyone got the instructions?

I'm cant even get the interface working with the expresscard com port on my vista.......

also anyone here is memer of bmwecu.org ? I reckon there are info about this. can someone invite me into this forum ?
thanks

Oh, need to be invited too! My mail for invite (and maybe an instruction) is miet.mich@gmx.de

thanks!

[gabileung]

I think the 318ti zip file is definately help
anyone still have this file in any case ??
my email is gabileung@hotmail.com

thanks

[Sparkz]

Hello Guys!

Maybe someone here can help me with the same problem most people here are thinkin about: How to get DIS to use a Ediabas interface.

I got myself an Interface which works fine with Ediabas/Inpa. I've installed now DIS V44 on my Laptop via VMWare using the guide "getting stated with VM-Ware" - and after editing the "ediabas.ini" and /etc/hosts like mentioned on the first page on this thread, IFHserv32.exe shows me the IP 192.168.68.32 when I enter the /usr/ediabas/bin/apitest command. The Dissoftware shows me the same IP in the admin-menu for GT1AP.
But how do I get DIS to use Ediabas? IFHServ shows nothing when I start the DIS-appl. - it only shows when entering the apitest command. I can also succesfully Ping 192.168.68.1 using the console-comand.

So, anyone got any hints for me?
As allready said:
-Ediabas/Inpa runs fine usin my Interface
-Edited c:\ediabas\bin\ediabas.ini to RemoteHost = 192.168.68.1 and
Port = 6801
-Installed DIS V44 using the "getting started with VM-Ware" guide (why do I add 3 LAN-Adapters: GT1AP 192.168.68.30, GT1AP1 192.168.68.31 and GT1AP2 192.168.68.32 ?)
-edited /etc/ediabas.ini RemoteHost = Diaghead (also tried 192.168.68.1)
Port = 6801
-edited /etc/hosts 192.168.68.1 Diaghead
-when running apitest IFHServ starts to show "192.168.68.32"
-DIS->Admin->System shows "GT1AP/192.168.68.32"

Hope you can help me - both shoulders and the "getting started..." guides only help you to successfully install DIS using VM-Ware but don't tell you how to configure DIS to work with an Ediabas/Inpa Interface.

Greetings from germany
Frank

PS: Hope my english is ok

[gabileung]

Frank

you seems know most these days
no one seem have this useful information anymore
I've tried contact some ppl in this thread who sucessfully get that working but no reply.....

[David Mc]

I may be wrong, but I thought only DIS v39 was compatible with the INPA interface. Experts in this field are on the ecubb.BMWECU.org forum.

[jamz]

That might well be the case. This should not be that difficult to do but I can't seem to make it work correctly. I'm close..using DIS v55.

The ecubb.BMWECU.org forum is in lock down mode and access is by invitation only. There is no method to ask for an invite that I can find.

I'm sure the missing information is probably there and would save many hours of wasted time if this is the case :rolleyes.

Thanks for the nfo..

Jamz


I may be wrong, but I thought only DIS v39 was compatible with the INPA interface. Experts in this field are on the ecubb.BMWECU.org forum.

[gabileung]

so anyone can send me an invite to ecubb.BMWECU.org ??

[flink182]

me too!

[Sparkz]

I guess nobody here can invite us to the BMWECU Forum, so I hope someone knows how to get DIS workin.

Jamz: You are usin an Inpa/Ediabas Interface, too?

I don't see any reasons why only Dis V39 should work. That wouldn't make any sense. And I've read a lot of ppl are usin also Dis V57 (latest released version).

I think I'm only missin something so Dis "talks" to IFHServ. As allready said - when I use the apitest everything looks fine, but in Dis no Diaghead shows up.

Greetings
Frank

[jamz]

Hi Frank,

Yes I'm using INPA/Ediabas on a Fujistu (XP Pro) tablet with USB to OBDII adapter. Also have the ODBII to 20pin for under the hood. Working great. I reset the airbag light on my E39 and the SES light on my E53. No problems there.

I have DIS v55 running on VMware player and can ping all IP addresses from the host ( Tablet) to the VMware DIS virtual (XP Pro) machine and back.

I'm close...but not quite there :rolleyes


Ahhh I just re-read your post above and you seem to be exactly where I am - missing that last piece to make the communications between the two :)


Jamz


UPDATE -------------------------------------------------



Well after a few weeks of research, trial and error, I finally made the connection between DIS and IFHserv32.exe..as shown below in the attached screen shot below. APITest is good also. Later today after work I will attach to the car and see what happens. I will report my findings!



I must get to bed now..works comes early.

Jamz :buttrock

http://img382.imageshack.us/img382/7651/status1.jpg

[gabileung]

good work Jamz
keep it going
if you could guide us thruogh or make a write up on this it would be really great !

[flink182]

Yeah Jams, good work! Please guide us!!

[Sparkz]

@Jamz: Congratz - but you were allready further before your success than I'm actually. As I could read in your other Topic you managed to get DIS to show you the Diaghead but got an errormessage when connecting.

My Problem is, that I don't see a Diaghead when DIS is running - even so the comunication between apitest and IFHserv seems to work fine.

I'd be very happy if you'd share how you got your DIS workin'

Greetings from germany
Frank

[flink182]

So i still have connected the DIS System with a Diagnostic Emulator ... that works fine ...

abload.de/img/dis5bvq.jpg <-- thats a link!

But it wont work with IFHserv or Ediabas ... :( the Apitest works too so where is the Problem?

[lorkar]

@Jamz: Congratz - but you were allready further before your success than I'm actually. As I could read in your other Topic you managed to get DIS to show you the Diaghead but got an errormessage when connecting.

My Problem is, that I don't see a Diaghead when DIS is running - even so the comunication between apitest and IFHserv seems to work fine.

I'd be very happy if you'd share how you got your DIS workin'

Greetings from germany
Frank

Great post guys, this is exactly where I'm at, I also don't see a Diaghead when Dis is running.

[jamz]

I believe the system now works. My E39 has a fuel guage problem. Guage is stuck on empty with low fuel light on. I know that I have one or more bad fuel lever sensors. ( I actually ran out of gas today..I thought I filled the tank!!! Need to get this fixed :( ) Good thing I had a gas can. So I know this is a current issue and will use this for my test. Some of the screen shots might be out of order as I was clicking all over the place. I don't know how to use DIS very well as this is my first try. After clicking on the following screen shots, you will be taken to a small image @ Imageshack. Click on the Image and it will grow to full size.

Below is a screen shot after connecting the system and identifying the vehicle. I wanted to run dianostics on the fuel guage.

http://img21.imageshack.us/img21/3192/ident3c.th.jpg (http://img21.imageshack.us/i/ident3c.jpg/)

The next screen is after running a diag test. I believe the fuel guage electronics are in the IKE/MID. The screen shows what looks like some type of error/notification x DME and !MID.

http://img200.imageshack.us/img200/7079/ident5.th.jpg (http://img200.imageshack.us/i/ident5.jpg/)

The next screen shot shows some fault codes that are stored I believe.

http://img127.imageshack.us/img127/3026/ident4.th.jpg (http://img127.imageshack.us/i/ident4.jpg/)

The last screen shot ..cant remember what I clicked..diagnosis document?
Indeed takes me to the section that explains the fuel lever sensors...

http://img127.imageshack.us/img127/6827/ident2.th.jpg (http://img127.imageshack.us/i/ident2.jpg/])

So is the system working? I think so..or am I just clicking and causing the errors myself. I need to go back and try more tests..a DIS manual would be nice :). I have to find proof somehow that DIS is actually talking to the ECU. If I knew DIS then maybe I already proved it? :)

Jamz

[gabileung]

Jamz

I think you have made it
as least the connection is up and listing the operation menu !
I cant even go beyond selecting or identifying the vehicle, just got stuck on the first page.
my DIS is running really slow, maybe it's trying to look for connection to the head where I cant join them properly...

btw, have you tried to run the instrument test and check the fuel gauage needle works properly? it sounds like fuel level sensor to me too but I would also try to eliminate other possible causes whlie we having the fantastic system !

keep us updated

gabi

[jamz]

Ok The system is working. I ran a complete diagnostic and watched the cursor move down the list of modules. My headlights came on during the lighting test. I have to figure out how to view the results :rolleyes

So the keys to make this work - you need the BMW Virtual Diagnostic Head runnning along with ifsrv32. There might be another solution out there but this worked for me! Do not run INPA / Ediabas Server - not needed! Just ifsrv32. The network settings in VMware and the host have to be correct including bridging. This I tweaked to fix my DIS to head communications error. Anyone needs help just ask.

Also to everyone who thinks their system is configured correctly but don't see the diagnostic head - you need the BMW Virtual Diagnostic Head app. If you have the application running in the background and still not able to connect then I suspect you have a network configuration issue between the host and VMware. I'm running the VMware Player. To check your VMware (Player) network settings - find and run the vmnetcfg.exe in your VMware directory. VMnet0 must be bridged to your main network adapter ( 192.168.68.1) on your host system (XP side). Disable automatic bridging and specify the adapter you want to bridge in VMware network config.

If you have more than one network adapter, make sure bridging is disabled on one of them. In my case I have two NICS. My main wireless and onboard . My main wireless is set to 192.168.68.1 and VMware bridging is activated ( network adapter properties). ON board NIC -VMware bridging not selected. IF your running VMware Workstation then the settings are in the GUI. If you are not sure your settings are correct, I will document my settings in XP and Vmware Player if requested.

At this pont I probably need a little help actually using DIS correctly. It does not seem that difficult and I ran through it quickly. If I spend enough time with it I'll figure it out eventually. Good Luck! Lets work to together to finally put this much requested topic to rest :).

Bonus:: #1: Google "diagheadinstall.rar" and you will find the app out there easily :)

L8R

Jamz

I came across some nfo on possibly editing a file on the SCOUnix side that might eliminate the need for a head all together! I will test and report..

[gabileung]

Hey Jamz

do you pick the setting of "Bridged Netowrking" or NAT while setting up DIS on VMware ?
a detail walk thruogh would be great from setting up the VMware ip address and GT1 configuration.
btw, do you get you inpa interface working with USB adaptor or raw com port ?

thanks
gabi

[flink182]

I still have two Problems:

#1 When i start the Virtual Head with IP ..68.1, dis gives an error "There is an IP reserverd with the name "diaghead" ??? What´s to do? I named my PC diaghead, but it wont work.

#2 The Virtual Head needs an activ ethernet connection! What´s up, if i am outside without any w-lan or internet? Then there isn´t any activ ethernet connection and the virtual head wont work ... :(

[Driiven]

flink - you need to remove the hostname/ip address you added originally on the unix side (ediabas.ini) . Are you familiar with using vi?

[flink182]

flink - you need to remove the hostname/ip address you added originally on the unix side (ediabas.ini) . Are you familiar with using vi?

Ah i added nothing - i´ve downloaded a complete image and i cant login to the unix sco system!

[Sparkz]

Hello,

thanks @ Jamz - seems my DIS is workin' now, too
I'll do a check tomorrow usin' my E46

Since I'm workin @ a BMW-Garage usin' DIS is everyday-work for me

Greetings
Frank

[flink182]

I still need help with my network config. What´s to do, when i have no Internet oder Network round about my car!? The virtual head wont run without an activ network!

[gabileung]

can you tell us more detail what you have done so far after the installation ?

[Sparkz]

Hi!

After usin' the Virtualdiagheadtool my DIS works fine, too.

I set up DIS usin the "getting started with VMWare" Guide, then changed some of the settings as mentioned on the first page of this thread. But you don't have to change /etc/hosts - or you'll get the errormessage flink182 has. After that I just start IFHServ, Virtualdiaghead and boot up my VMWare GT1. When the DIS-Software is ready, I press "start" on the virtualdiagheadmenu and DIS shows up a Diahead which I can connect the software to.
And after that I just can plug in the interface to my car, choose the model and here we go...

Note: Before you start tryin to get DIS alive, you've got to make sure, your INPA/Ediabas runs and you can connect it to your car. After that you can start to get your DIS workin'

Greetings
Frank

[steeee]

i have been trying to get a hold of these files, have the Vmware running v55 and the DIS on it. i have got a hold of the DiagHeadInstall. But i dont know where to get the, OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

It seem to be quite helpfull to most people. And no one want the let it go for free. so you can email me on stee.ac@gmail.com. And where can i get the ifhrsrv3.exe file. please please guy. help. help.

[gabileung]

i have been trying to get a hold of these files, have the Vmware running v55 and the DIS on it. i have got a hold of the DiagHeadInstall. But i dont know where to get the, OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip

It seem to be quite helpfull to most people. And no one want the let it go for free. so you can email me on stee.ac@gmail.com. And where can i get the ifhrsrv3.exe file. please please guy. help. help.


I believe ifhrsrv3.exe is located in INPA or EDIABAS folder
simply search for it


Hi!

After usin' the Virtualdiagheadtool my DIS works fine, too.

I set up DIS usin the "getting started with VMWare" Guide, then changed some of the settings as mentioned on the first page of this thread. But you don't have to change /etc/hosts - or you'll get the errormessage flink182 has. After that I just start IFHServ, Virtualdiaghead and boot up my VMWare GT1. When the DIS-Software is ready, I press "start" on the virtualdiagheadmenu and DIS shows up a Diahead which I can connect the software to.
And after that I just can plug in the interface to my car, choose the model and here we go...

Note: Before you start tryin to get DIS alive, you've got to make sure, your INPA/Ediabas runs and you can connect it to your car. After that you can start to get your DIS workin'

Greetings
Frank


Hi Frank

congrats with your working GT1npa
would you mind make an instruction for the configuration for the INPA and GT1 setting ? I'm so confiuse with the IP config setting. like windows IP and VMware's IP as well as GT1's ip........:eyecrazy


gabi

[steeee]

Have seen it the file.
I do not have the DIS doing anything at all. i have not been able to get it to diagnose. Plus i have the INPA/EDIABAS runing but i dont now why i wont connect to the car. I purchase the Ediabas/INPA rs232 (DB9) cable on ebay the and i dont know what the problem is.

And how that i have both i dont even know where to go and how to make the talk to each other.

[turbo1973]

Hi, i'm a newbie to the forum but have been following this thread with great interest and it finally inspired me to buy an image of DIS and SSS which i've now installed on a IBM X22 laptop with serial port. I'm using a Edibas serial lead with Inpa 5.02 / Edibas installed alongside DIS and SSS both running under VMWARE. I also have the 'diaghead' emulator installed and running.

Inpa currently works fine when connected to the OBD socket and I can access. Unfortunately, despite printing out, reading and re-reading this thread about 25 times, I am having difficulty in getting DIS to actually connect successfully using the Edibas interface.

So far, I can load and run DIS (with the head emulator and IFH-Service running in the background), and my interface appears on the list of 'Free Diagnostic Heads' as Chris 192.168.68.1 in DIS Administration > Config > Diagnostic Head, and when I click on the head from the list, the following fields get automatically filled in

Hostname:- Chris 192.168.68.1
IP Address:- 192.168.68.1
Network Mask:- 255.255.255.0
Default Gateway:- <blank>

I then try and click on 'OK' but nothing happens, probably because the default gateway field is blank. So I then add 192.168.68.1 to the default gateway field and I can then click on 'OK'. However after about 15 seconds an error is reported, namely that the Interface cannot be correctly configured

So I go into Admin > Connection Setup

Again, the head appears in the list as Chris 192.168.68.1 however when I click on the 'connecting' tab, I get the message

"The IP address of the selected diagnostic head is also entered under the name 'diaghead' in the system. Each IP address may only be allocated once. Rectify the mistake in the relevant configuration mask".

How do I rectify this or stop the confiction?

In VMWARE my network settings appear as follows under summary

VMnet0 (bridged) Bridged to BN-WD54G Wireless Network (my network card)
VMnet1 (host only) A priivate network shared with the host - Subnet 192.168.68.0 DHCP Enabled
VMnet8 (NAT) used to share the hosts IP address - Subnet 192.168.153.0 DHCP Enabled

Both VMnet0 and VMnet8 appear as enabled and operating in network connections

I have manually edited (using wordpad) the C:\Edibas\bin\edibas.ini file with the following information

TCP / IP Configuration. Server Address/name. Remote Host = 192.168.68.30

Port = 6801

(i've also tried diaghead, Diaghead and 192.168.68.1 entered as the remote host without any success)

I am a little confused about this, do I only need to physically alter the settings in /bin/edibas.ini or is there another edibas.ini file within the Unix virtual environment which also needs editing?. I can log into the panel using root and 12345, but have no experience of editing or accessing files within there. Any guide on doing this would be great.

Also when I click ifhsrv32.exe nothing pops up or opens, but it does appear on the taskbar as IFH-Service. There is no IP address next to it though.

I've spent most of the weekend on this, and its driving me nuts. Its really so frustrating to be so close and yet still feel like being miles off.

I would appreciate any advice from those who have trod this path and found success. Both me and my 320D would be very grateful of any advice, and it would probably save one laptop from flying out of the nearest window.

Thanks in advance

[embmw]

turbo try to add default gateway: 192.168.68.128. when you config diagnostic head.

[MadMonkeyMan]

Hi

I finally got GT1 to work with my ediabas interface..(not so hard if you do it right, but took some time).
Bay the way not all the information in the instructions we get is correct, at least not for me.

but over to my questions:
Is any body else able to automatic identify model? I only get this messages.

hxxp://img73.imageshack.us/img73/1172/gt1v39.png


and a am also not able to use the "coding/programing" or the "key programing" only get this message: (note: screen shot taken after "diaghead" turnd of" so dont mind the signal)


hxxp://img73.imageshack.us/img73/1172/gt1v392.png



And last question.
in NCS-Expert my E39 is identified with EWS/IKE/KMB.
but the FG number is not the same for all the modules. IKE/KMB is the same but EWS is different. should thay be the same?







turbo1973:




"The IP address of the selected diagnostic head is also entered under the name 'diaghead' in the system. Each IP address may only be allocated once. Rectify the mistake in the relevant configuration mask".

How do I rectify this or stop the confiction?

I think you have added in your etc/host file
192.168.68.1 dighead ??

ok , just remove it!

if not i suspect the "VMware Network Adapter VMnet1" in the host computer that you have VMware workstation. is using ip 192.168.68.1 then you can just change it to .5 or so.




I have manually edited (using wordpad) the C:\Edibas\bin\edibas.ini file with the following information



the ediabas.ini on the "diaghead" eumaltor / INPA pc, you dont have to change at al. as this is sett up to "interface=STD:OBD

it is only the /etc/ediabas.ini at the DIS you need to change



I am a little confused about this, do I only need to physically alter the settings in /bin/edibas.ini or is there another edibas.ini file within the Unix virtual environment which also needs editing?. I can log into the panel using root and 12345, but have no experience of editing or accessing files within there. Any guide on doing this would be great.

You only have to edit etc/ediabas.ini

to edit files i unix u can use "vi" just type it in the command promt.

Do a google "linux vi" first as this is a litle hard to use at first.



Also when I click ifhsrv32.exe nothing pops up or opens, but it does appear on the taskbar as IFH-Service. There is no IP address next to it though.


and the ip beside ifhsrv32.exe on the task bar will only aper once DIS is connected.



I've spent most of the weekend on this, and its driving me nuts. Its really so frustrating to be so close and yet still feel like being miles off.


I know exacting what you mean... but what i feeling when you get i to work!!!


regards
mmm

[embmw]

I try to make it working but failed. I need to know this settings you have in your windows and in vmware:
1. windows:
vmnet1: ip, subnetmask, default gateway, bridged or not
main network adapter:ip, subnetmask, default gateway, bridged or not
2. vmware:
in settings what network adapter you use (vmnet0, vmnet1)?
what settings do you have in vmware network config?
I have this problem. ping 192.168.68.1 work, /usr/ediabas/bin/apitest work, ifh service shows ip from vmware adapter(192.168.68.20). when I reboot and dis come up, the diag head don't appear.
my settings are:
1. windows:
vmnet1 : IP: 192.168.68.1
subnet mask: 255.255.255.0
default gateway: 192.168.68.20
bridged
2.vmnet :
in settings :network adapter: vmnet1 (host only)
network adapter : IP: 192.168.68.20
subnet mask: 255.255.255.0
default gateway: 192.168.68.1
edited etc/ediabas.ini: remote host : diaghead, port: 6801
edited etc/hosts: 192.168.68.1 diaghead
my etc/hosts looks like this:
127.0.0.1 localhost
192.168.68.1 diaghead
192.168.68.20 gt1ap
what is rong?
tell me please you entire configuration
thanks anticipated

[MadMonkeyMan]

Ok.

Here are some screenshots:
just ask if something is uncleare.

hxxp://profile.imageshack.us/user/madmonkeyman


hope it helps.


regards
mmm

[turbo1973]

Thanks for the help so far.

I still cannot get the Edibas head to connect. It constantly appears in the list of Free heads but when I click on it, and try to connect, it just gives a 'cannot be correctly configured error'

One thing I have also noticed, is that in the BMW Head Emulator program is running, the GW address appears as 0.0.0.0

This is what appears in the Emulator program window when it is started

Detected System Name:- CHRIS
Using network adaptor [00000011] VMware virtual ethernet adaptor for VMnet1
IP:192.168.68.1 MASK:255.255.255.0 GW:0.0.0.0

IFH-Service still does not display an IP address even when DIS is running. I guess this means that its not connecting properly

I think that I need to access /etc/edibas.ini in order to edit it because this has not been done, so i think that this is where my current problems lie. But how do i do this?

So far I have got the DIS menu up and pressed ctrl+alt+F1 and then logged in with "root" and "12345"

I then typed 'vi' but got a 'command not recognized error'

Typing 'scoadmin' loaded the menu

Where do I go now in order to edit edibas.ini? does this file already exist or do i need to create it?

I think I now need to be at photo 15 on the image link that MMM kindly added, but how to get there and edit the IP and Port?

I've searched the forum and google but cannot find any instruction on doing this. As you may have guessed i've never used VMware before, LOL

Thanks.

[MadMonkeyMan]

ok.

Yes i think you defiantly need to change the ediabas.ini file or at leas look and see if change must be made.

first the easiest think to try is Changing the name of the pc CHRIS to DIAGHEAD and add gateway ip 192.168.68.1

if this does not work.

then you go to terminal/console on DIS "ctrl + alt +F1"

at the command line:

"cd /etc"

"vi eidabas.ini"

(file is already there) (if you have the same version i have "vi" program should be there. if not you can try use "nano eidabas.ini" or "pico eidabas.ini"

after edit reboot by typing "init 6" in command.

regards
mm

[embmw]

thanks, man. I'll try those settings and tell what's happent

[turbo1973]

Well I feel like i'm a bit closer to sorting this (thanks to the help given here) but DIS is still not playing fair and allowing the Ediabas interface to connect and i'm now tearing out what little hair I have left.

I've now managed to change my /etc/ediabas.ini file (Thanks MMM) and also checked the /etc/hosts file

This is the contents of etc/ediabas.ini

[TCP]
Remotehost = 192.168.68.1
Port = 6801

-----------------------------------------

and this is the contents of my /etc/hosts file

SCCS IDENTIFICATION

127.0.0.1 localhost
192.168.68.30 gt1ap gt1ap
192.168.68.1 mobilteil

-----------------------------------------


The diaghead is still appearing in the list of 'free heads' however when I click to select it, there is a delay of about 30 seconds and then the diaghead emulator program crashes and gives the error "The established connection failed because the connected host failed to respond".

This is what is logged in the head emulator window

Sending CMD_MT_FREE
Received CMD_MT_CONNECT
Connecting via TCP to 192.168.32:1111
Sending CMD_MT_FREE
Sending CMD_MT_FREE (appears many times)
The connection has failed because the host has failed to respond
Sending CMD_MT_FREE (appears many times)
Could not connect to host 192.168.32

When I try to ping 192.168.68.1 in the console I get the message 'Host is Down'

I can ping 192.168.68.30 ok and also 192.168.68.32 ok

When I try to run apitest in the console, I get the error 'Fehlertext: NET-0009: TIMEOUT

[MadMonkeyMan]

ok

Have you enabled VMCI in the virtual machine settings??


hxxp://img526.imageshack.us/img526/8026/vmci.th.jpg




regards
mmm

[turbo1973]

ok

Have you enabled VMCI in the virtual machine settings??


hxxp://img526.imageshack.us/img526/8026/vmci.th.jpg




regards
mmm

I don't seem to have that option. I only get the two 'guest isolation' check box options.

Guest isolation was showing 'disabled, disabled' in the left hand box. Since checking box options They now show enabled,enabled but with no VMCI box or options?

[embmw]

I have a problem. in administration/ connection setting I click on connecting and after the connection is made it tells me to update the diagnostic head but don't work. before to ask me to update the diagnostic head it shows for some seconds a message: " software version inquiry". what I made rong?
mad monkey, you wireless is connected?
in my diaghead emulator shows : Using Network Adapter[00000015] Atheros Wireless Adapter, not Using Network Adapter[00000001] VMware Accelerated AMD PCNet Adapter like to you. where is the problem?
I have the VMCI activated
my v39 didn't work and I find a v52 base( its a vmware made with v52 base cd) but I have v51 cd installed.
can anybody help me to have some newer vertions( base and progman cd's) then what I have?

[bmwnolo]

looks like i've just got it working and i'm celebrating by signing up to bimmerforums and rubbing some of your faces in it a little bit :)

gt1, dis and tis are all working. dis is connecting to diaghead emulator which in turn is connecting to ifhsrv when i go to diagnose something

couldn't have done it with out shoulders, nuvola rossa, ducati and a good few of your comments, thanks!! now i'm off to bed and hopefully when i plug in to my car in the morning everything with still work. Thanks again!

[gabileung]

looks like i've just got it working and i'm celebrating by signing up to bimmerforums and rubbing some of your faces in it a little bit :)

gt1, dis and tis are all working. dis is connecting to diaghead emulator which in turn is connecting to ifhsrv when i go to diagnose something

couldn't have done it with out shoulders, nuvola rossa, ducati and a good few of your comments, thanks!! now i'm off to bed and hopefully when i plug in to my car in the morning everything with still work. Thanks again!

yey congrat
keep us update !
:)

[embmw]

bmwnolo look to my posts here and give those settings I need to help me connect to my car . thanks

[bmwnolo]

where abouts are you stuck gabileung? is it on the networking side? i can upload any screenshots that you need.

embmw, i didn't come across that error so i dont think i can help, other than to say that mine is working on v39 and also make sure you havnt changed any of the defaults in diaghead software.

i need to reprogram my DME but i've chickened out because i dont have a good quality battery charger :(

[gabileung]

where abouts are you stuck gabileung? is it on the networking side? i can upload any screenshots that you need.

embmw, i didn't come across that error so i dont think i can help, other than to say that mine is working on v39 and also make sure you havnt changed any of the defaults in diaghead software.

i need to reprogram my DME but i've chickened out because i dont have a good quality battery charger :(

thanks for the head up bmwnolo :)
yeh dont risk it where I seen ppl saying programming ECU would take a lot of power, maybe get the batt charging by another running car on jumper lead ?

after a like 1+month trial and error I m running out of ideas.....maybe I have to live with the edibas inpa, but better than nothing :stickoutt

currently I've set VMware on bridged networking mode, I've spent like 2 weeks to get the proper bootable installation disk working with shoulder's installation instructions

but for some reason it still running very slow after few fresh installation when get into DIS regardless how much RAM I'm allocating, it seems looking for network connection of the head or some sort. I occassionaly got frozen at the admin ip config page, and it takes like 3 mins ( not joking ) for every click I made, so I dont even get a chance to alter those IP setting in DIS

I understand the concept at some point (correct me if I'm wrong) is forcing GT1 to look for the signal from ediabas side instead of the yellow head via ip address ( luckily we could do that due to the yellow head has its own ip for the wireless connection ), and on the ediabas side it capture and forward the signal from the interface for the GT1.

I used the setting same as embmw, which are
Vista :
IP: 192.168.68.1
subnet mask: 255.255.255.0
default gateway: 192.168.68.20
bridged


VMware:
network adapter : IP: 192.168.68.20
subnet mask: 255.255.255.0
default gateway: 192.168.68.1
edited etc/ediabas.ini: remote host : diaghead, port: 6801
edited etc/hosts: 192.168.68.1 diaghead
my etc/hosts looks like this:
127.0.0.1 localhost
192.168.68.1 diaghead
192.168.68.20 gt1ap

what about yours ? did you change the ip setting in DIS admin?

thanks in advance:stickoutt

gabi

[bmwnolo]

just to make sure, the principle instructions i used were the one by ken fister. He explains the entire procedure for setting up the networks and also installing the program. did you use the same instructions? make sure you have your firewall turned off in Windows or else GT1 won't be able to communicate with diaghead/ifhsrv32

www bmwecu org/article001

I didn't edit anything on the dis side other then what he says. On the Windows side i edited C:\windows\system32\drivers\etc\hosts and C:\ediabas\bin\ediabas.ini with the settings you listed (apart from gt1ap has ip 192.168.68.30 in hosts and also on windows side the default gateway is 192.168.68.1). I'm using Windows XP so i'm not sure where the hosts file is located in Vista

do you have the three ethernet adaptors setup in vmware?

The only thing i think i found that didn't work in his instructions was the first time that GT1 booted the touchscreen calibration came up, you get out of that by pressing the windows button and it won't show up on further boots.

On a side note, i saw some people saying that the mouse doesnt register clicks well in vmware. I have found that theres a certain nack to it and it works perfectly. I'm using a mousepad on my laptop. When you want to press a button on the screen you bring the cursor over to the button but leave your finger on the pad, then with another finger you press the left mouse button and release, then just slightly move the finger on the pad to the side.

[ArnoUK]

I just got it working (well almost...)

The key thing for me (which wasn't really clear from all the different instructions) was to chance the TCP port settings in C:\EDIABAS\Bin\ediabas.ini on the host pc to 6801 (same as in /etc/ediabas.ini). If you read the ediabas manual it says that this port should be the same for the host and the virtual pc.

I haven't had much chance to test it yet, but now there seems to be a problem with the communication with the car. I have INPA working, but when I do a brief survey/test in DIS, it says "No control unit found!"

Anyone else had this before?

[bmwnolo]

Yeh same issue here, everything else seems to be working apart from testing, ohh and measuring. Is your measuring section working? Mine won't even go into the section, just throws up errors.

[steeee]

i need help, i have spent my entire weekend trying to get DIs to work, i have the other parts working (inpa,wmware,diaghead). I can not connect to the diaghead in DIS. please please please help.

Here are the massages i keep getting,

hxxp://s984.photobucket.com/albums/ae325/stee-01/ <---Link

[turbo1973]

I know what you mean Steeee, i've been sat in front of this every weekend throughout the summer, and i've still not got past the stage which you are at.

I give up!, my family have forgotten who I am and I want my weekends back, LOL. All I wanted to do was to recode a new injector and clear some adaption settings, and it turns into reinventing the wheel.

Unfortunately, i've come to the conclusion that there is no 'one size fits all' solution out there as there are far too many variables, even this thread contradicts itself on the IP addresses and settings with different people giving different solutions in what works for them, however when non of these options work, then the problems begin, and if you read the settings and experiences on other forums then it gets even more confusing, still i've learned a lot of Russian along the way!.

I'm sure somebody clever out there, could come up with a commercial solution for those in society who don't have a PHD in computer programming and which works 100% on all machines using an install which is just as easy as Inpa / Carsoft, and i'm sure when they do get around to it, that it would make them very rich. I would have bought it months ago.

Until then, its time to visit the dealer, and pay him his pound of flesh...far cheaper than a divorce, LOL

[bmwnolo]

steee, your going into the wrong menu, i spent a couple of hours trying to get past that stage when i was doing it, you need to go into connection setup under the title Admin. in the Administation screen. Once your in there click on the free diagnostic head and then click on "connecting"

turbo1973, you can clear the adaptions in INPA, on my version anyway its not listed on the main screen but it is written on one of the buttons down the bottom on one of the sceens (half your problem)

[embmw]

MadMonkeyMan I need more pics with some settings you have in your computer for making my gt1 to work with inpa interface:
- pic with network connections from windows
- both 'general' and 'support' from all of your network connections from windows
And I have another question: you have a vmware machine with windows xp installed( with all programs in it-inpa, bmwdiaghead) and use those 2 machines gt1 and bmw diagnostic, or use gt1 virtual machine and win xp from your computer?
thanks for answers and for help.
have a nice day.
PS you can send me your answer directly to my email: embmw25@yahoo.com or embmw25@hotmail.com

[steeee]

bmwnolo - I have already tried that, I get a percentage bar showing 0% then it disappears and brings a massage saying it cannot connect. I have uploaded the image on my previous post.
Does any one know of a boot floppy disk image for DIS? I am using V53 does any one know of any problems with this version. And has anyone got it to work with V53 or V55.
Has any one else got the same problem will using other version?

[embmw]

guys the key to make it working is the settings must be made in windows network connections. will be great if somebody have this working to take some snapshots of all connections that appears in network connections and share them with us.

[bmwnolo]

heres my screen shots,

hxxp://s804.photobucket.com/albums/yy329/bmwnolo

i have both GT1 V39 and XP running in VMWare but you can just use your main windows, works the same. Instead of configuring the network adapter in network connections on the VMware xp you just configure the VMnet1 network adapter in network connections on your main windows.

make sure you have firewall turned off AND also that you've setup the 3 network cards correctly in 'scoadmin network' as described by hxxp://www bmwecu.org/article001/

if theres something i'm missing let me know

[steeee]

could provide a copy of the scoadmin network setup, as described by hxxp://www bmwecu.org/article001/

that is a private forum and most of use don't have acess to it.

ThAnk bmwnolo

[bmwnolo]

i dont have access to the forum either but that link works

(i've taken out the 'tt' and the dot between www and bmwecu from the link)

[ArnoUK]

Yeh same issue here, everything else seems to be working apart from testing, ohh and measuring. Is your measuring section working? Mine won't even go into the section, just throws up errors.

My measuring section isn't working either, but as far as I understand it you'll need some special cables for that anyway.

Made any progress?

[bmwnolo]

My measuring section isn't working either, but as far as I understand it you'll need some special cables for that anyway.

Made any progress?

None, only to say that i've tried both v39 and v44 with the same results. I can see network communication going on between windows and DIS but nothing is coming out of the serial port during diagnosis.

[embmw]

soon I'll give you some new informations. madmonkeyman made a virtual machine with windows xp on it and installed all programs in it(inpa, diaghead, etc) with inpa interface connected directly to vwmare machine. he have started both machines on vmware(with gt1 and windows) and I think its working . didn't tried yet on my car cause I need a powerfull laptop( has 512mb RAM memory and I need at least 1GB RAM memory. I'll take the laptop from my sister to try it and I will told you if it works. you can try too and see if its working

madmonkeyman( thanks a lot for his help) posted here a link with his settings look to those pics and use them. I think will work.
hxxp://profile.imageshack.us/user/madmonkeyman.
watch them carfully and you will see those 2 virtual machines

[bmwnolo]

soon I'll give you some new informations. madmonkeyman made a virtual machine with windows xp on it and installed all programs in it(inpa, diaghead, etc) with inpa interface connected directly to vwmare machine. he have started both machines on vmware(with gt1 and windows) and I think its working . didn't tried yet on my car cause I need a powerfull laptop( has 512mb RAM memory and I need at least 1GB RAM memory. I'll take the laptop from my sister to try it and I will told you if it works. you can try too and see if its working

madmonkeyman( thanks a lot for his help) posted here a link with his settings look to those pics and use them. I think will work.
hxxp://profile.imageshack.us/user/madmonkeyman.
watch them carfully and you will see those 2 virtual machines

thats the way i mine setup, look at my screen shots

hxxp://s804.photobucket.com/albums/yy329/bmwnolo

you dont need to have a windows in vmware but it works either way

[embmw]

thanks for pics and informations. today I'll test on machine and see what is happent. I'll let you know. anyone of you can help me with dis software v52 or later?(base cd, program cd,etc)

[embmw]

bmwnolo when its making the connection, it ask me to update the diaghead and, of course, is not working? I tested on a dis v55 installed on v52 base cd. what's happent?

[MadMonkeyMan]

embmw: in the diaghead emulator is it sett to version 999 ?


mmm

[e39dream]

anyone ever have an issue getting base to recognize the DIS programs disk? driving me nuts.

[embmw]

I set it to 55 madmonkeyman? is it rong?

e 39 you must activate the cd.
2 posibilities:
1. use image cd under vmware:
- mount dis program image with daemon tools
- set the virtual machine ( click on VM, select settings, click on CD/DVD, select autodetect)
- in DIS go to Administration, under "CD drive alocation" will see CD drive 1 DIS vXX , click on it, will become black and go in the right and click on Activate CD
2. use CD inserted in your CD/DVD driver:
if you use vmware set the virtual machine ( click on VM, select settings, click on CD/DVD, select letter of your CD/DVD driver, example: E: )

I finally did it! thanks all of you guys!!!
PS: you re right madmonkeyman!! I lost a lot of time cause I modified the version software. must be 999! I'll go to test it on my car and s tell you later how it works.

[e39dream]

thanks for some tips EM. I know about activating the disc, I have this installed on a desktop without any issues. Went to put it on the laptop and for whatever reason it does not recognize the disc. for example when I load the disc onto the desktop and open "my computer" the disc is titled something like "dis programs" but if I do the same thing on the laptop it is not even titled under "my computer". Maybe I need to burn it to a cd-r rather than a dvd-r. I will try that and if not I will do the mounted iso method.

it would be awesome if someone did a write up detailing how to use the USB KKL interface with inpa/gt1. There are so many tutorials out and none for my hardware setup. It's kind of scary doing trial and error testing with a daily driver or my mom's car. :)

[MadMonkeyMan]

I set it to 55 madmonkeyman? is it rong?

e 39 you must activate the cd.
2 posibilities:
1. use image cd under vmware:
- mount dis program image with daemon tools
- set the virtual machine ( click on VM, select settings, click on CD/DVD, select autodetect)
- in DIS go to Administration, under "CD drive alocation" will see CD drive 1 DIS vXX , click on it, will become black and go in the right and click on Activate CD
2. use CD inserted in your CD/DVD driver:
if you use vmware set the virtual machine ( click on VM, select settings, click on CD/DVD, select letter of your CD/DVD driver, example: E: )

I finally did it! thanks all of you guys!!!
PS: you re right madmonkeyman!! I lost a lot of time cause I modified the version software. must be 999! I'll go to test it on my car and s tell you later how it works.



Good to hear you finally got i working.. I never changed the version number... but I was just reading around some russian forum`s and somebody was talking about the version in the emulator..had to be 999.

can you check if "auto identify of car" is working for you?


mmm

[embmw]

madmonkeyman, thanks again for helping me to setting dis to work with inpa interface. that was the problem: must not modify the option settings in emulator( software version must be 999). when I realize that, thanks to you, I was very mad cause I could have all this functionally since 1 month ago.

my interface use USB port and is STD/OBD type. my DIS is V55 (US), and automatic identification of my car(e90) is working(type, engine, VIN, ECU installed on it). what version of DIS do you have? maybe your copy has an error. if you want my version send me an email to embmw25@yahoo.com and I'll answer you how to download it.
P.S. my v55 is installed on v52 base. and if your interface is STD/OBD type I'll also send you a file named OBD.ini to use it under ediabas. its helping to recognise the contact and battery when you open INPA.

e39dream sometime appear this kind of issues. cd wrote on a computer can't be read on other. more simple is to use ISO files. I had the same problem when I tired to install v39. I wrote the base cd on a blank and when I use it on laptop give me error on instalation. so I used ISO file and worked.
don't loose time writing cd's.

[MadMonkeyMan]

embmw: you got mail!

I am using v39 base with v44 update and a serial -> obdII -> 20pin.
But I use a "USB to serial" device so this may be the case. I`m waiting for my new PCMCIA serial card to drop down in the mailbox. maybe it helps.

Im using: Interface = STD:OBD and have OBD.ini in windows folder.

Do you have it like this also?


mmm

[embmw]

I heared those adapters make some problems. my interface is directly USB and is dedicated for INPA( not an universal interface). with the software? will be better to have new version but if you need coding must also have SSS. yes OBD.ini is also in windows folder

[Dayclone]

embmw I sent you and email.

But basically guys I have a few questions.

I currently have the BMW GT1 VMWare V53 installed it on my mac...
and then running windows XP via Parallels.

I can't seem to get the GT1 computer to communicate with the BMW Virtual Diag Head on XP via Parallels.

Any one have any idea?

Also is this set-up okay, where I have GT1 -> Virtual Diag Head -> USB -> OBD II??

Thanks for the help!

[bmwnolo]

USB to serial adapters work fine as long as they use the FTDI chip and have all of the pins on the serial plug connected (not like the cheaper ones which only use four of the pins)

[Dayclone]

USB to serial adapters work fine as long as they use the FTDI chip and have all of the pins on the serial plug connected (not like the cheaper ones which only use four of the pins)

Yes mine has the FTDI chip because first time I tried it... it didn't have that chip and there was no communication at all.

Basically... I'm having a hard time trying to get it running on my mac right now because GT1 is running on VMware, then XP on Bootcamp or Parallels and there's no connection between VMware to Bootcamp/Parallels in order for GT1 to detect that the virtual head is running...

Any ideas?

[ian s]

Hi guys, just wanted to thank you all for the screenshots. I'm another one on the list of people having problems trying to connect to the diaghead although DIS can see it.

I'm sure I'll get there eventually, but wouldn't have got as far as this without your help.

Ian

I'm still testing and cleaning up my install but I can connect successfully to the diaghead! I re-read this thread about 100 times, made notes and experimented a little.

I have installed GT1 within VMware and I am connecting back to the host computer that is running Vista. I'm using the USB KKL interface.

Initially I bridged back using the Wifi adapter but that was causing problems so in the end I installed the Microsoft loopback adapter and bridged back to that. I assigned that the IP 192.168.68.1 and then disconnected from all other networks.

Within SCOadmin I didn't modify the hosts file but I did modify the ediabas.ini with the IP 192.168.68.1. I also did the network config as described within scoadmin.

Unfortunatly I am unable to connect to my car but could see ifhsrv32 get an IP etc. Inpa can still connect and on the host I have modified C:\ediabas\bin\edibias.ini to include the remote host. When I go to connect I get an error about the signal strength and get offered to select the car manually but it still doesn't work!

Slowly getting there!

Ian

[jamz]

To those who PMed, sorry I never got back to you. I am back again. Now I'm currently troubleshooting fuel gauge issues ( see E39 DIY Level Sensors)

Later...Jamz

[randomy]

Does anyone have a copy of the thread form 318ti.org that explains how to accomplish this?

I have INPA and EDIBAS running, but am not certain how to make it communicate over the cable. Thanks.

[jamz]

..you say you have INPA running. Do you mean you have the software installed and configured correctly? What type of cable / connection are you using?



Does anyone have a copy of the thread form 318ti.org that explains how to accomplish this?

I have INPA and EDIBAS running, but am not certain how to make it communicate over the cable. Thanks.

[randomy]

I ordered what I beleive is a INPA compatible cable (http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&item=140302955212&viewitem=&sspagename=STRK%3AMEWNX%3AIT).
I don't know if it is isntalled correctly, there were many optiosn to select during install, many of them install in German language only, so I selected one that was a "Developer" type since it installed in English. I selected OBD as the interface, and then ...

... So a few hours later and some tinkering, I have INPA running and communicating with my E36. Using the USB\OBDII cable from ebay allows me to only read the engine.

But I discovered that using the carsoft interface on the 20 pin diag socket under the hood lets me read alot more modules. I could read airbag, air conditioning, oh geez I can't remember, but others as well.

Which leads me to a question, I may start a new thread on it, but I saw that when I connected to "Automatic Air Conditioning" there is a feature called "Park Ventilation" that is turned Off...I want to turn it ON!!!! How do I do that?

http://dvsntt.com/offsiteimg/328i/OBC%20park%20ventilation.jpg

[suparmutt]

I know what you mean Steeee, i've been sat in front of this every weekend throughout the summer, and i've still not got past the stage which you are at.

I give up!, my family have forgotten who I am and I want my weekends back, LOL. All I wanted to do was to recode a new injector and clear some adaption settings, and it turns into reinventing the wheel.

Unfortunately, i've come to the conclusion that there is no 'one size fits all' solution out there as there are far too many variables, even this thread contradicts itself on the IP addresses and settings with different people giving different solutions in what works for them, however when non of these options work, then the problems begin, and if you read the settings and experiences on other forums then it gets even more confusing, still i've learned a lot of Russian along the way!.

I'm sure somebody clever out there, could come up with a commercial solution for those in society who don't have a PHD in computer programming and which works 100% on all machines using an install which is just as easy as Inpa / Carsoft, and i'm sure when they do get around to it, that it would make them very rich. I would have bought it months ago.

Until then, its time to visit the dealer, and pay him his pound of flesh...far cheaper than a divorce, LOL
Hello.
I am new to this forum BUT i finally made it.
I fought with this settnigs whole week :) sleepless :)
Had same problem as you had and found this topic via google.
Please dont give up :) i know this feeling :) but i found a solution so my inpa coonects to DIS and holds its signal.
I did play with settings now i will verify what settings were right and i will let you know what was a goal for me .
PS. strange but i can not find how to send private message to you

[randomy]

Can you elaborate on how you were able to get the INPA interface to work with DIS? I'm close, but still not accomplishing this.

Here is a recap of what I have acheived:
-successfully installed GT1\EasyDIS v.44
-succesfully installed INPA\EDIABAS
-succesfully read EWS\DDE and Airbag module with INPA using VAGCOM USB\OBDII interface
-succesfully read even further modules using carsoft interface with INPA

My results with DIS:
-launch ifhrsrv32, then boot DIS.
-ifhsrv32 displays IP 192.168.68.30 (I believe)
-Start Diagnosis, and returns message that battery voltage is less than 9 volts or not present, and that auto-detect cannot work. If I perform this without ifhsrv32 running, then it says that it can't communicate with the interface.
-Manually select my car, then start EWS\DDE diagnose, and after about 5-7 minutes it returns error that it can't communicate with the module.

It seems I am close, as DIS seesm to try to communicate with ifhsrv32, but it doesn't seem to be communicating with the cable. Any suggestions here?

[suparmutt]

TO randomy
i think you missed to run this diagnostic head emulator LINK IS NOT VERIFIED !!! http://thepiratebay.org/torrent/4416354
You need to run ifhserv32 and this diaghead emulator
Then after DIS is loaded click on administration-connection and set connection.
but i can not connect to my cars (93 320 and 95 328)with DIS though i connect to 95 328 via INPA
i believe it is cause they are not OBD but ADS i need to cofigure my inpa adapter but could not get it yet.

[embmw]

randomy, if you made the connection and DIS identify your car. that warning about battery voltage is real. it seems your battery has under 12v and DIS is stopping, in that case. you have 2 possibilities:
1. start the engine and make your diagnosis with engine running at idle speed;
2. if you have a good battery charger, connect it to the battery( engine stopped) and after your battery will have at least 12v DIS will work.

[randomy]

DIS is not identifying my car, I manually select it, start the DDE test, and then after several minutes it gives an error about no communication. I'm going to try running the daighead emulator.

[nele]

randomy; you need to modify (hardware) your interface (if its usb i assume) to get autoidentify work thought gt1 dis...

[randomy]

I'm not getting even that far though, I'm not concerned about auto-identify at this point.

I am running the diagnostic head emulator now, but has had no difference so far
Ifhsrv continues to report that the IP of DIS connects to it (at least that is how I am interpreting it when the ifhsrv icon displays the IP address of DIS in the taskbar), however nothing appears under Free diagnostic heads in DIS.
Apitest is succesful at starting (do not get time-out messsage and goes to a menu in German) but BMW diagnsotic head tool neer gets any response, it continues down the screen with 'Sending CMD_MT_FREE' no matter what I do in DIS...i feel so close but light years away still.

I have now further discovered that when I Click under Admin. > Connection Setup, I receive an hour glass, and then the cursor returns. The screen never opens up. This is DIS v.44

I'm going to reinstall it all from the beginning.

Reinstalled GT1\DIS and have the same results....Fark!

[nele]

randomly: try disabling your other network devices if you have, go to windows network connection disable all except vmware connection, then go to dis, admin, quit connecting then connect again. Scroll down diag head and check if connection is ok?

[randomy]

I have disabled all network adapters, I can ping the DIS machine and from the SCO cmd line I can ping my Windows machine.
APItest works, but I still cannot get anything to show up in diagnostic heads, and the daighead emulator never receives any commands from DIS.
I don't understand why apitest works, but DIS cannot find the diag head, even though the emulator is running.

[chromax]

I have disabled all network adapters, I can ping the DIS machine and from the SCO cmd line I can ping my Windows machine.
APItest works, but I still cannot get anything to show up in diagnostic heads, and the daighead emulator never receives any commands from DIS.
I don't understand why apitest works, but DIS cannot find the diag head, even though the emulator is running.

I have the same problem ...
connection with ifhrsrv32 seems to be ok but i can't make diaghead emulator to work... apears "Sending CMD_MT_FREE" and status is "disconnected".

LE: The firewall is disabled.

[nele]

And when you go to administration, test, "Quit connection" then "Reconnect" again nothing appears, "Test" also?

[randomy]

I figured out how to get it to work, it probablly was ready to work a long time ago, I jsut never tried a diag test in a awhile, expecting to see somethign appeare uunder diagnostic heads in administration before I could run a test. It turns out, it is running tests. I'm about to make a post announcing this article I wrote: http://dvsntt.com/INPA/

[lbijl]

Hi cummunity,

i have so far all running. Still the apitest drives me crazy. Recieve a net-0009 TIMEOUT and in DIS app while diagnosting a Error impairment failure. Communication to diagnostic head faulty.
I can ping the head from the console
I have a LED sign for signal strength of diaghead.
IFHSRV32.exe is running
ediabas.bin configured
hosts configured,
and so on and so on. Something i did not read here before.
Has someone an idea ?
thanks to all

[LPCapital]

Hi cummunity,

i have so far all running. Still the apitest drives me crazy. Recieve a net-0009 TIMEOUT and in DIS app while diagnosting a Error impairment failure. Communication to diagnostic head faulty.
I can ping the head from the console
I have a LED sign for signal strength of diaghead.
IFHSRV32.exe is running
ediabas.bin configured
hosts configured,
and so on and so on. Something i did not read here before.
Has someone an idea ?
thanks to all

Very same situation here... If it might help in any way, when I run the APITEST the EDIABAS version shown is 6.4.4 while the EDIABAS I've installed it's 6.4.3.

Here's what I get when I run the API test...

http://i259.photobucket.com/albums/hh284/lpcapital/DIS/DISError1.jpg

[cerixen]

Hi

I finally got GT1 to work with my ediabas interface..(not so hard if you do it right, but took some time).
Bay the way not all the information in the instructions we get is correct, at least not for me.

but over to my questions:
Is any body else able to automatic identify model? I only get this messages.

hxxp://img73.imageshack.us/img73/1172/gt1v39.png


and a am also not able to use the "coding/programing" or the "key programing" only get this message: (note: screen shot taken after "diaghead" turnd of" so dont mind the signal)


hxxp://img73.imageshack.us/img73/1172/gt1v392.png



And last question.
in NCS-Expert my E39 is identified with EWS/IKE/KMB.
but the FG number is not the same for all the modules. IKE/KMB is the same but EWS is different. should thay be the same?





Hey mmm,
Did you solve the auto identification issue when trying to use the coding part of DIS?

I'm thinking it could be a hardware issue?

I would like to thank everyone on this forum for making this possible. I now have the DIS V44 working fine and I can use the diagnosis part of DIS, but not the coding part...??? any help?

thanx

[cerixen]

Hi guys,

I just thought I would contribute a little with what I have been able to do.

I've got my ediabas interface working with both DIS V39 and DIS V44 using VMware.
I did both versions just to see if there would be any difference etc.
The DIS V39 was installed using the shoulders method. Found the software on eMule.
DIS V44 i found on rapidshare. The links for the files are in this forum:
http://forums.5series.net/lofiversion/index.php/t80934.html
(You need the BASE V44 and the PROGRAMM V44)
Here you will also find the diaghead emulator software.

One very nice feature of this DIS V44 is that it's already set up to work through VMware. I think some mad science freak from bmwecu has hacked it or something, but it works very well. All you have to do is install the software using this guide: (hope it's okay i link to it?) http://dvsntt.com/GT1/

The EDIABAS/Inpa which is linked above together with DIS V44, is not that good. I had much better results using this version instead:
http://rapidshare.com/files/158493016/INPA.part1.rar
http://rapidshare.com/files/158498122/INPA.part2.rar
http://rapidshare.com/files/158502247/INPA.part3.rar

The instructions are not in English, but the program is. This is the FULL version of EDIABAS and Inpa, including NCS-Expert (used to code/program)

I started doing all this because I wanted to enable the daytime running lights on my E46 Coupe from 2003. This setting is a part of "CAR Memory" so I needed to be able to code the car, not just diagnose it!

I got DIS working fine on VMware and I can diagnose the car just fine. However I cannot programe it using the "Code/Program" part of DIS. It comes up with this message: http://img73.imageshack.us/img73/1172/gt1v392.png (picture from madmonkeyman)
This is very strange to me because the Auto identification works fine for the diagnostics part of DIS. Anybody knows how to get this working?

Anyway I turned to the software NCS-Expert. This software is included in the INPA package I've linked. NCS-Expert works fine for me and I can change the settings in car/key-memory. So I'm happy!

To get the NCS-Expert configured and running I used this:
http://www.x5drivers.co.uk/viewtopic.php?f=1&t=4901&start=0

I also found that if you make your VMware hdd size of exactly 18.635 gb's, everything works alot better. This is probly the size of the original DIS machine or something.
In the end I had better results using the windows software (Inpa, NCS-expert etc.) rather than using DIS. I do believe DIS is a better solution for diagnosis, rather than INPA.

Hope somebody can benefit from this. Just wanted to share my info.

Has anybody been able to use the coding/programming part of DIS (for key/car-memory)?

happy coding
cerixen

[j4m35]

Hi cerixen,

I am glad to hearing that you've got your DIS V44 to work. Can I ask you a couple of questions coz I seem to be hitting a snag where I cannot seem to get the DIS system to ping my host computer (and vice versa); my host computer's firewall is turned off. I configured all 3 network adapters on the DIS system to VMnet1 and my host computer's VMnet1 is configured to 192.168.68.1/255.255.255.0.

Which version of VMware are you running? I installed DIS V44 (from the 5series.net forum) on VMware Workstation 6.5.3 Build-185404, and my host is running Vista SP1. I followed Randomy's guide to the letter (from dvsntt.com). Even reinstalled multiple times but always having the same issue with the network communication.

First I couldn't get to command prompt using CTRL+ALT+F1. But later found that CTRL+Sys Rq did the trick.

Anyway, that aside, from inside the command prompt ifconfig shows that there's 1 network adapter net1 configured as 192.168.68.30/255.255.255.0; and the standard loopback lo0 configured as 127.0.0.1. (I was expecting to see 3 network adapters but only found 1.) In the command prompt, I am not able to ping my host computer (192.168.68.1) and vice versa. :help

I've tested by using Windows XP as another guest OS in VMware. From inside Windows XP, I can ping my host computer (192.168.68.1) and vice versa without problems. :confused This shows that the VMnet1 is configured correctly and there's no firewall interfering.

So it leads me to believe that the problem lies with the DIS V44 installation. Either the installation disc is spoilt (but this shouldn't be the case as it was retrieved from the same location and there were no CRC errors unraring it) or the VMware is not giving the DIS installation the 'hardware' it expects causing the installation to be screwy.

Any input on my situation would be gladly appreciated.

Thanks!
-James


Hi guys,

I just thought I would contribute a little with what I have been able to do.

I've got my ediabas interface working with both DIS V39 and DIS V44 using VMware.
I did both versions just to see if there would be any difference etc.
The DIS V39 was installed using the shoulders method. Found the software on eMule.
DIS V44 i found on rapidshare. The links for the files are in this forum:
http://forums.5series.net/lofiversion/index.php/t80934.html
(You need the BASE V44 and the PROGRAMM V44)
Here you will also find the diaghead emulator software.

One very nice feature of this DIS V44 is that it's already set up to work through VMware. I think some mad science freak from bmwecu has hacked it or something, but it works very well. All you have to do is install the software using this guide: (hope it's okay i link to it?) http://dvsntt.com/GT1/

...

happy coding
cerixen

[cerixen]

Hey James,

I think I know what's wrong. I was probably a little fast when I wrote that this DIS V44 was 100% setup and ready to go.

You seem to have everything ready, except you need to configure the unix system for your network. Here is how you do it:

Boot up DIS, when it's started you type the ctrl+sysrq command. This will bring up the login menu. Login as root with your password (I think this version of DIS will ask you to choose a password the first time you login)

At the # unix prompt, type scoadmin

This will start a configuration tool. Using the tab and arrow keys, scroll to networks. Then choose network configuration manager.

Here you delete all the drivers, except the loopback driver (should be the first one)

Then you ADD a new driver. The tool should automatically detect your VMware network adaptors. Choose the first one. Then choose SCO TCP/IP.

The first adaptor should have the name: gt1ap
and the ip address: 192.168.68.30
The subnet should be filled out automatic, otherwise it should be: 255.255.255.0

Then you repeat this step for the remaining 2 adaptors. no. 2 should have name gt1ap1 and ip: 192.168.68.31

the 3rd should have name gt1ap2 and ip: 192.168.68.32

When this is setup you should have a total of 4 drivers. 3 adaptors and the loopback driver.

Now you exit the manager. At some point it will ask you to rebuild, re link and boot of this kernel. just answer yes to all this.

Now at the unix prompt, you type init 6 to reboot the whole thing.

And now you should be able to ping DIS from windows. Try it and let me know.

Here is a link to shoulders installation guide for the DIS V39. For this DIS V44 you don't need all the mouse and hdd drivers that he mentions, this is much simpler.
The procedure I described for you is also in this quide, starting from step no. 44
http://robmw.altervista.org/dis/

I hope it works,
cerixen

[j4m35]

Hi Cerixen,

Thanks for the quick reply; and your diagnosis of the situation was spot on! :) I am now able to ping 192.168.68.30-32 from my host computer and vice versa.

I had assumed the network adapters would have been configured as part of the installation sequence. I didn't know I had to manually configure the 3 adpaters and relink the linux kernel. Thanks for pointing me in the right direction!

- James


Hey James,

I think I know what's wrong. I was probably a little fast when I wrote that this DIS V44 was 100% setup and ready to go.

You seem to have everything ready, except you need to configure the unix system for your network. Here is how you do it:

...

And now you should be able to ping DIS from windows. Try it and let me know.

Here is a link to shoulders installation guide for the DIS V39. For this DIS V44 you don't need all the mouse and hdd drivers that he mentions, this is much simpler.
The procedure I described for you is also in this quide, starting from step no. 44
http://robmw.altervista.org/dis/

I hope it works,
cerixen

[cerixen]

I'm glad I could help!

Does everything work now?
You were almost there, just needed the final settings regarding the network.
I just thought I would try to make a step by step instruction for this problem in case anybody else were having these problems.

What are you going to be using DIS for? And what car? Im just curious :D
Are you planning on trying to change some settings in car/key-memory, because I cannot get that part of DIS to work. Only the diagnosis part works for me!

I'm currently installing DIS V39, just to see if that is better. Because for that version I have a disc called "CIP V13 for DIS V39" perhaps this will make me able to use the coding/programming part of DIS. I hope so.

I would really appreciate it if you would try out the coding part and see if it works.

I simply love this geeky hazzle... :D

[j4m35]

I'm still waiting for my USB KKL cable to arrive in the mail. Once that comes, I'll let you know how it goes. As of now, DIS in VMware is able to communicate with ifhsrv32.exe and connect to the BMW Diagnostic Head emulator running on my host computer. So everything looks set.

I'm going to use it on a 2006 E60. First I want to run the diagnostics to see if I've set everything up properly. I'm also planning to DIY my Inspection 1 so hopefully running the diagnostic will let me know of any problems the car has.

As for coding, I was hoping I can turn on the feature that changes the intensity of the brake lights with respect to the amount of brake input (can't remember the exact name of the feature offhand). I'll let you know if it works.

Once again, thanks for all your help!

- James


I'm glad I could help!

Does everything work now?
You were almost there, just needed the final settings regarding the network.
I just thought I would try to make a step by step instruction for this problem in case anybody else were having these problems.

What are you going to be using DIS for? And what car? Im just curious :D
Are you planning on trying to change some settings in car/key-memory, because I cannot get that part of DIS to work. Only the diagnosis part works for me!

I'm currently installing DIS V39, just to see if that is better. Because for that version I have a disc called "CIP V13 for DIS V39" perhaps this will make me able to use the coding/programming part of DIS. I hope so.

I would really appreciate it if you would try out the coding part and see if it works.

I simply love this geeky hazzle... :D

[chr9984]

Hi guys,

I just thought I would contribute a little with what I have been able to do.

I've got my ediabas interface working with both DIS V39 and DIS V44 using VMware.
I did both versions just to see if there would be any difference etc.
The DIS V39 was installed using the shoulders method. Found the software on eMule.
DIS V44 i found on rapidshare. The links for the files are in this forum:
http://forums.5series.net/lofiversion/index.php/t80934.html
(You need the BASE V44 and the PROGRAMM V44)
Here you will also find the diaghead emulator software.

One very nice feature of this DIS V44 is that it's already set up to work through VMware. I think some mad science freak from bmwecu has hacked it or something, but it works very well. All you have to do is install the software using this guide: (hope it's okay i link to it?) http://dvsntt.com/GT1/

The EDIABAS/Inpa which is linked above together with DIS V44, is not that good. I had much better results using this version instead:
http://rapidshare.com/files/158493016/INPA.part1.rar
http://rapidshare.com/files/158498122/INPA.part2.rar
http://rapidshare.com/files/158502247/INPA.part3.rar

The instructions are not in English, but the program is. This is the FULL version of EDIABAS and Inpa, including NCS-Expert (used to code/program)

I started doing all this because I wanted to enable the daytime running lights on my E46 Coupe from 2003. This setting is a part of "CAR Memory" so I needed to be able to code the car, not just diagnose it!

I got DIS working fine on VMware and I can diagnose the car just fine. However I cannot programe it using the "Code/Program" part of DIS. It comes up with this message: http://img73.imageshack.us/img73/1172/gt1v392.png (picture from madmonkeyman)
This is very strange to me because the Auto identification works fine for the diagnostics part of DIS. Anybody knows how to get this working?

Anyway I turned to the software NCS-Expert. This software is included in the INPA package I've linked. NCS-Expert works fine for me and I can change the settings in car/key-memory. So I'm happy!

To get the NCS-Expert configured and running I used this:
http://www.x5drivers.co.uk/viewtopic.php?f=1&t=4901&start=0

I also found that if you make your VMware hdd size of exactly 18.635 gb's, everything works alot better. This is probly the size of the original DIS machine or something.
In the end I had better results using the windows software (Inpa, NCS-expert etc.) rather than using DIS. I do believe DIS is a better solution for diagnosis, rather than INPA.

Hope somebody can benefit from this. Just wanted to share my info.

Has anybody been able to use the coding/programming part of DIS (for key/car-memory)?

happy coding
cerixen
Hi,
Great info
Does all this works on windows vista?
Which are the better cables to use with this?

[Rallyfinnen]

Since this new info about configuring IP's came up, I decided to give DIS another try.
I created a new virtual machine and did a clean install (again).
Luckily this time I learned how to create snapshots ;)

I was only able to add two adapters, the third was never found in the scoadmin network config. I have three in vmware, and they are active with similar settings. (..68.0 ..78.0 ..88.0)


I'm hoping somebody could explain the 'path' to me, how DIS interacts with the INPA interface. I'm not an expert in this stuff, but trying to learn..
The path as I understand it is DIS->some kind of Ediabas remote-service in unix-> vmware virtual adapter-> (diaghead emulator??) -> ifhserv -> serial port-> OBD interface..
Correct? I just cant understand the settings.. too many variables :rolleyes
I'm confused by the IP settings with .68.0 .68.1 .68.30 .68.31 .68.32 etc..

I have read diffrent instructions, some saying you need three virtual adapters and diaghead emulator, and randomy who seems to have it working without this emulator.
Seems only the first adapter (.68.0) is in use anyway?
Maybe diffrent IP's are used in diffrent instructions, and I now ended up with a mix of those?

I will try to sum it up:

Ipconfig in unix ediabas config:192.168.68.1, (same menu as the apitest)

scoadmin network adapters:
-loopback driver
-device #18: 192.168.68.30
-device #19: 192.168.68.31
-third one not found

vmware adapters:
192.168.68.0
192.168.78.0 (tried without this one)
192.168.88.0 (tried without this one)

windows:
vmware adapters have no firewall or similar active
should they be set to dhcp or not? i tried both..
I get 192.168.68.1 in the win properties for VMnet1

ediabas.ini
192.168.68.1 port 6801
(i have also looked in remote.ini, seems there is some info that could be relevant too?)

INPA is working(via USB adapter), it is the same install as before.


Last DIS install, the apitest actually worked, but i had no communication on the serial port. Tried it with and without diaghead emulator and changed a lot of settings..

This time I can't even get past the apitest.. :help

Would be so nice to get this to work!

[TheMatrixz]

Rallyfinnen,

Try to ping 192.168.68.1 from your Unix prompt, and ping 192.168.68.30 from Windows. Make sure the virtual machine is communicating with Inpa.

[j4m35]

Hi Rallyfinnen,

From what I gathered and configured, all 3 adapters in VMware should be configured to VMnet1 running on the 192.168.68.0 subnet. (You don't need .78.0 and .88.0)

The VMnet1 adapter on your host (i.e. PC running VMware) should be configured to 192.168.68.1.

Inside DIS, running the scoadmin to configure the network adapters, when adding the 3rd adapter, scoadmin initially listed the adapter as '????'. I then deleted the 3rd adapter and tried adding it again. It worked after that. So I can't give you much advice here except keep trying.

As for the DHCP service on 192.168.68.0, I left it turned on in VMware. It technically doesn't matter because we're staticly assigning IP addresses in DIS and the IP address range configured in the DHCP service doesn't conflict with our staticly assigned addresses in DIS.

This is actually how far I've gone with the DIS system. I have no idea how it works with INPA yet as I'm still waiting for my USB KKL cable to arrive.

Hope this helps.

Best regards,
James

[Rallyfinnen]

Can't get them to communicate, no luck pinging..
Tried diffrent settings. Removed and added network adapters etc, but no connection.
It never finds the third adapter in scoadmin either.
Can't understand it.. Last try apitest was ok without any changes at all, but now there is no way I can get a connection..

James, I'm not sure what you mean by 3 adapters configured with the same IP? It's not possible to configure them with the same IP, i get a message that the IP is allready in use if I try to give the same IP to vmnet2 or 3.

If only .68. is used, then why do we need more than one adapter?

For sure there is a lot of stuff going on that I don't know about. I have no idea how the virtual machine is set up(easy dis), and what it needs to work. Guess my patience is not good enough to keep trying over and over again :)

[j4m35]

Hi Rallyfinnen,

I guess there was a miscommunication somewhere because I wasn't clear... I wasn't asking you to configure all three adapters to the same IP address. I was asking you to configure them onto the same _subnet_. I.e. All three begin with 192.168.68. and end with a different number in the last octet. In essence, the 3 adapters in DIS should be configured to 192.168.68.30, 192.168.68.31, 192.168.68.32 respectively. And not 192.168.68.30 for the first adapter and 192.168.78.30 for the second adapter.

Why you need 3 adapters, I have no idea yet. However, in VMware all 3 should be configured to VMnet1 in the hardware settings. Look in this website: http://dvsntt.com/GT1/ and search for 'Add 2 additional Ethernet adapters and also assign them VMnet1'. All 3 Ethernet adapters should be configured similarly in VMware. With the Radial button for Custom selected; and 'VMnet1 (Host-only)' selected in the drop-down list.

Lastly, before trying to ping, you have to turn off any firewall on your host computer. Windows XP and Windows Vista's built-in firewall in its default settings will prevent you from pinging DIS.

Hope this helps.

- James

[Rallyfinnen]

Thank you for your patience! :)
I'm a bit slow, so no fault on your side ;) Had three adapters in vmware (vmnet 1-3), that was my confusion, all clear now! Firewall is off (by default on my computer).

Well, here is a summary of what I have done today..

After some tinkering I was able to see a free diaghead in DIS, but when i tried to connect it was asking for some diskette..(the 1,44M plastic squares from the time when I was young :) ) and I there was nothing I could do.. DIS was saying 'no interface connected', or similar, when i tried to run diagnosis.

Anyway, I was not able to add all three adapters in DIS/scoadmin, so I went back to the snapshot I made after finishing the DIS base install.

Then I did the setup of the DIS network cards before installing the programs in DIS, and it found all three! :)
I was then able to ping -30, .31, and .32 from windows and apitest was ok.

I then continued with the programs install in DIS. I had ifhserv and diaghead emulator running in the background (for no good reason I guess).

After the programs-install, apitest and pinging 30,31,31 from win was still ok, but no free diaghead in DIS even if diaghead emulator was running.
ifhserv was showing .31 as IP after apitest.

I then went to Administration/Config/System and entered 192.168.68.20/255.255.255.0/192.168.68.1 per Randomy's instruction.
After this i was not able to ping 30/31/32 any more, but .20 instead.
ifhserv changed to showing .20 as IP, and apitest still ok

If i tried to run diagnostics I could see that there is no blinking on the interface (usb-serial with LED's). I did not try it in the car though.

Next I tried to remove 2 network adapters from the virtual machine(Randomy method), after this DIS would not start, it would only go to the propmt and ask me to log in, and after logging in noting happened.
I went back to the previous snapshot with 3 adapters

As it is now, I can ping both ways (.68.20 from win, and .68.1 from the virtual machine) but there is no connection when I try it in the car, and LED's are not blinking.
INPA still connects fine to the E38 (LED's blinking when it communicates).

Seems the connection to ifhserv is there, but it's not connecting to the interface..
ediabas.ini settings are .68.1 port 6801

I was actually expecting a happy ending the way things were going, but it seems I'm now back to where I started :(

Any recommendations? (or do you just wish I would shut up and disappear? :D )

[cerixen]

Hi Rallyfinnen,

It sounds to me like you still need to configure DIS to use the correct IP.

You need to modify both the c:\ediabas\bin\ediabas.ini and the \etc\ediabas.ini (the last file is on the unix system)

You also need to modify the file \etc\hosts

There is more info on this in the first pages of this forum.

Hope it helps.

[Rallyfinnen]

Hmm, I'm totally lost when it comes to unix commands.. :rolleyes
I could change directory and open the file using 'vi ediabas.ini' but i have no idea how to edit and save..
I only used DOS commands when I started with computers, and now I can only click the mouse ;)

It also seems that the ones earlier in the thread had no connection when pinging and running apitest?

I can ping both ways using the IP's 68.20 and 68.1.
If i ping diaghead in win 192.168.68.1 answers
If I ping diaghead in DIS machine there is no such host.

Is the hostname needed by DIS-Ediabas too, not only the ip?

I'm not even sure what route to go, should i use the diaghead emulator or not?
Seems Randomy got it working with a few simple moves withouth the emulator?
If i go with the diaghead emulator i guess the .30-.32 IP's should be in use, not the .20? If they need to be restored i would have to run a new installation, because I have no idea how to change it back in DIS.

[cerixen]

You just need to google "vi unix commands" and you will quickly be able to edit and save files using the vi editor. You're on the right track. In unix you need to edit \etc\ediabas.ini and \etc\hosts using the vi editor.

Here is how my hosts file looks:

127.0.0.1 localhost
192.168.68.30 gt1ap gt1ap
192.168.68.32 gt1ap2 gt1ap2
192.168.68.31 gt1ap1 gt1ap1
192.168.68.1 mobilteil

The hosts file can also be edited using the scoadmin configuration tool, but I don't remember how.

In the file \etc\ediabas.ini you just need to make changes in 2 lines. Under the section [TCP] you should change remotehost to 192.168.68.1 and port to 6801. Don't change or add anything else.

also in the c:\ediabas\bin\ediabas.ini you should only add the same 2 lines under the [TCP] section
You can change the IP's of the different adaptors in the scoadmin tool. at the unix prompt (#) just type scoadmin

Then go to networks => network configuration manager
Then highlight the line called SCO TCP/IP, under the adaptor you want to change. Then goto the protocol menu, choose modify protocol conf....

Now you can change the IP. Repeat this on all the adaptors. Don't touch the loopback driver.

When using dis you need the emulator and the ifhsrv32 software running. You only need the ifhsrv32 running to actually use the interface, you should be able to make dis connect to the diaghead, with only the diaghead emulator running.

keep at it! :D

[jokerthepoker]

can i use the EDIABAS - DIS GT1 to program the DME using the OBD interface?

[aise]

Hey James,

I think I know what's wrong. I was probably a little fast when I wrote that this DIS V44 was 100% setup and ready to go.

You seem to have everything ready, except you need to configure the unix system for your network. Here is how you do it:

Boot up DIS, when it's started you type the ctrl+sysrq command. This will bring up the login menu. Login as root with your password (I think this version of DIS will ask you to choose a password the first time you login)

At the # unix prompt, type scoadmin

This will start a configuration tool. Using the tab and arrow keys, scroll to networks. Then choose network configuration manager.

Here you delete all the drivers, except the loopback driver (should be the first one)

Then you ADD a new driver. The tool should automatically detect your VMware network adaptors. Choose the first one. Then choose SCO TCP/IP.

The first adaptor should have the name: gt1ap
and the ip address: 192.168.68.30
The subnet should be filled out automatic, otherwise it should be: 255.255.255.0

Then you repeat this step for the remaining 2 adaptors. no. 2 should have name gt1ap1 and ip: 192.168.68.31

the 3rd should have name gt1ap2 and ip: 192.168.68.32

When this is setup you should have a total of 4 drivers. 3 adaptors and the loopback driver.

Now you exit the manager. At some point it will ask you to rebuild, re link and boot of this kernel. just answer yes to all this.

Now at the unix prompt, you type init 6 to reboot the whole thing.

And now you should be able to ping DIS from windows. Try it and let me know.

I hope it works,
cerixen

Thanks! I had DIS 44 installed and this is what i needed to get my PC and DIS to communicate. I don´t have the vagkkl usb i/f yet (it´s on the way). When i run the apitest it gives me the TIMEOUT error (IFH-Service is running). What´s missing here?

[j4m35]

Hi Rallyfinnen,

Firstly, sorry for the late reply, I was away on work and wasn't able to access the internet.

I think when DIS is asking you for a 1.44M disk, it's trying to save or load the configuration. From what I can gather, DIS in the free diagnostic head section, loads and saves to floppy disks.

I didn't perform Randomy's change the IP to 192.168.68.20. Hence my DIS is still running on .30/.31/.32.

As for communicating with the car, I am still waiting for my USB KKL cable to come in the mail. So this is as far as I have gone with my DIS setup. I'll let you know more after my cable arrives.

Lastly, I would never want anyone to shut up and disappear. So please don't.

Cheers,
James

[randomy]

I don't think the IP change is necessary, I only put it int to be complete with the procedure that allowed my car and computer to finally communicate. I also don't think any editing of the hosts file is necessary, but I'll double-check to see if I have anything listed on either of hosts file of the hard system or virtual machine.

[aise]

Problem solved, apitest is working both way now. I have F-Secure installed and it was blocking the 6801 port, i should have known it lol.

[Rallyfinnen]

I have been concentrating on mechanical things for a while now.. It's good to do some real wrenching to clear out the computer headaches ;)

As far as I understand about general networking (no expert), you can either use a IP, or specify a IP for a host (like in the win hosts-file) and then use the host name instead of the IP in the applications.
That is why I find it hard to understand why both IP and hostname is needed. Feel free to correct me if I'm wrong :)

Based on my assumptions above I suspect my problem is somewhere else, since there is a connection between win/ifhserv and the virtual machine.

Could it possibly be some incompability between ediabas versions in virtual machine and windows?

[j4m35]

Hi Rallyfinnen,

The USB KKL cable just arrived in the mail today so I can try and move further ahead with my 'GT1'...

I know what you mean about doing some real wrenching to clear out the computer headaches. When I had trouble getting the GT1 virtual machine to ping my host computer, I decided to take out and clean all 8 spark plugs in my Honda Civic Hybrid.

On to networking... You are absolutely right about using IP address or a host name with the hosts-file. If you are comfortable using IP alone (like me), you can use IP addresses only (I configured it all using IP addresses alone).

Here are a few questions to see if they help:
1. Did your GT1 pass the API-test? As seen from http://dvsntt.com/INPA/; do a search for “API test” and look at the screenshots around it.

2. Is the DiagHead emulator on the host PC? *EDIT* I found out that the DiagHead emulator needs to be running to perform diagnostics on the car. While the car was performing a 'Quick Test' I closed the DiagHead emulator and the 'Quick Test' in DIS screeched to a halt.

3. Is the firewall on the host PC turned off?

Hope this helps! Best regards,
James


I have been concentrating on mechanical things for a while now.. It's good to do some real wrenching to clear out the computer headaches ;)

As far as I understand about general networking (no expert), you can either use a IP, or specify a IP for a host (like in the win hosts-file) and then use the host name instead of the IP in the applications.
That is why I find it hard to understand why both IP and hostname is needed. Feel free to correct me if I'm wrong :)

Based on my assumptions above I suspect my problem is somewhere else, since there is a connection between win/ifhserv and the virtual machine.

Could it possibly be some incompability between ediabas versions in virtual machine and windows?

[Rallyfinnen]

Hi!

Hope you get it working with your interface!

To answer your questions:

1 Yes apitest is ok, and has been ok most of the time during my experiments

2 Yes, diaghead emulator running in win (host). I have tried with and without it, because Randomy got it working without. That is also why I have been changing the IP numbers, because Randomy is using .20 (if I remember correct) instead of .30 .31 .32

3. Yes, XP firewall is off.

[j4m35]

Hi Rallyfinnen,

First of all, the only way I could get INPA to work correctly is to make sure that the Cable is attached as COM1 and the latency of the Virtual Com Port driver is set to 1ms (it was defaulted to 16ms).

I also did the following mods on the Cable later:
1. Shorted Pin 7 & 8 at the OBD II end; apparently to send the signal to both K-lines on the BMW car side.
2. Shorted leg 17 & 18 of the FTDI chip (on the circuit board); to force the Battery signal to be ON.
3. Then I spent a few hours in the afternoon doing the transistor and resistor mod to allow for ignition detection (which in turn allows for automatic detection of the vehicle).

So with the modded cable and latency set to 1ms, I was able to perform diagnostics on the car. Haven't tried any coding yet though.

The funny things I've noticed are:
1. ifserv (from EDIABAS) is connected to DIS's IP of 192.168.68.32.
2. DiagHead emulator is also connected to DIS's IP of 192.168.68.32.
3. When performing diagnostics, the only network adapter having any communication is the one with 192.168.68.32.

This leads me to believe that only 1 network adapter (and not 3) is required for the whole system to run. I've gotta look into this further though.

- James

[aise]

i did the ignition mod and inverted the RI# with mprog (FT232RL chip), DIS works great:redspot

[Rallyfinnen]

Hi!

INPA has always worked (via COM1) during my trials (and errors!) with DIS.

I had the apitest working in several configurations/installations, but never any communication with the car.

I have tried a number of installations and configurations on two different laptops, of which one has a built in serial port, but no luck so far..

I think even a monkey should have been able to get it to work with so many tries! :)

[aise]

is it normal that when i connect the cable under admin -> connection setup the lower line of LED´s go off? diagnosis work normal.

[ian s]

is it normal that when i connect the cable under admin -> connection setup the lower line of LED´s go off? diagnosis work normal.

Interesting. I get the same when I connect to the diaghead but am unable to perform any diagnosis. Out of interest how long goes it take to perform a diagnosis?

When I configure the VM networking as described (using VMNet1) I have no connectivity to the host - even though it's bridged in the virtual network editor. When I bridge to it by specifiying VMNet0 for all three guest nics I have connectivity between host and guests and APItest run's succesfully. However, as described I lose all the lower LED's (network?).

The only thing I have noticed is that when I am using VMNet 1 for the guest networking, the vmware virtual network adapter on the host has an apipa IP address? Windows also mark's the connection as having limited connectivity. Not sure if this is a problem as we are specifying the IP address manually? Or should I start playing with Nat'ing?

I have tried every guide I can find! I can connect to my car using Inpa fine.

Any advice? Is using VMnet0 is acceptable and having the indicator bar for the network with no lights/blobs normal?

The other thing I have learnt that may help others, is that in Vista there is an registry fix that will change the default network option for the virtual adapters to default to private network instead of public.

All help will be much appreciated as this is driving me crazy!

Ian

[j4m35]

Hi Rallyfinnen,

In my case, once the apitest works, and the Diaghead is connected (the yellow diaghead icon's 'LED's turn on at the top of the DIS screen) I am able to perform diagnostics on the car.

At this juncture, I can only give you moral support and say keep at it!

- James


Hi!

INPA has always worked (via COM1) during my trials (and errors!) with DIS.

I had the apitest working in several configurations/installations, but never any communication with the car.

I have tried a number of installations and configurations on two different laptops, of which one has a built in serial port, but no luck so far..

I think even a monkey should have been able to get it to work with so many tries! :)

[aise]

Interesting. I get the same when I connect to the diaghead but am unable to perform any diagnosis. Out of interest how long goes it take to perform a diagnosis?

When I configure the VM networking as described (using VMNet1) I have no connectivity to the host - even though it's bridged in the virtual network editor. When I bridge to it by specifiying VMNet0 for all three guest nics I have connectivity between host and guests and APItest run's succesfully. However, as described I lose all the lower LED's (network?).

The only thing I have noticed is that when I am using VMNet 1 for the guest networking, the vmware virtual network adapter on the host has an apipa IP address? Windows also mark's the connection as having limited connectivity. Not sure if this is a problem as we are specifying the IP address manually? Or should I start playing with Nat'ing?

I have tried every guide I can find! I can connect to my car using Inpa fine.

Any advice? Is using VMnet0 is acceptable and having the indicator bar for the network with no lights/blobs normal?

The other thing I have learnt that may help others, is that in Vista there is an registry fix that will change the default network option for the virtual adapters to default to private network instead of public.

All help will be much appreciated as this is driving me crazy!

Ian

diagnosis work fast.

i get this error after i choose my car model under diagnosis:
www.hot.ee/aise/Decision.png (http://www.hot.ee/aise/Decision.png)
when i press cancel i get an auto id success notification:
www.hot.ee/aise/IDENT.png (http://www.hot.ee/aise/IDENT.png)

about those lower leds, when i ping 192.168.68.30 from windows side they will light up as long as i ping...

i can´t ping 192.168.68.1 from unix side, i can ping it only from win. i can ping all other IP´s from win or from unix (.30 .31 .32)

[ian s]

That's very helpful, thank-you. I set up a continuous ping from the host and the LED's lit up.

Time to take a look at the host side of things...

Ian

[aise]

i´ve got it. i removed network adapters .31 and .32 from unix and both leds are on:) before that the ifhservice took .32 but i figured it should take .30 wich is DIS´s IP so i removed those 2 devices:D

[susha1]

what do you mean ......i mean i am not very much clear with it.....you want a cheap one??

Susha BMW Performance Chip (http://www.engineperformancechip.com/bmw-performance-chip-c-3)

[capstorm]

Hello guys,

I'm trying to run EDIABAS / INPA on WinXP laptop, and to connect to Diagnostic Head over cross-over cable and TCP/IP.
I'm not sure what IP to put for RemoteHost in ediabas.ini. IP of PC running INPA or Diagnostic Head IP?

I tired with both but same result, always timeout error. I also cannot start ifhserv32.exe. Double-click on it does nothing. I cannot see that process in Task Manager. So I think there lies a problem but I don't know hoe to solve it

Can anybody help?

Thanks in advance!

[Rallyfinnen]

So you have a real yellowhead connected via LAN, not a OBD cable?
I think you don't need ifhserv with the yellowhead, you only need to get the virtual DIS machine to be able to connect to your network card in the host (XP?)
Try to use vmnet0 in the virtual machine and make sure vmnet0 is connected to you LAN card. Hope that helped.

[capstorm]

So you have a real yellowhead connected via LAN, not a OBD cable?
I think you don't need ifhserv with the yellowhead, you only need to get the virtual DIS machine to be able to connect to your network card in the host (XP?)
Try to use vmnet0 in the virtual machine and make sure vmnet0 is connected to you LAN card. Hope that helped.

Yes, that is correct. I have real yellowhead . Is it possible to use it only with INPA without DIS?
IP of EDIABAS station is 192.168.68.50 and yellowhead has IP 192.168.68.22. What IP address should I put in ediabas.ini?

Thanks!

Just one update to my previous post. I also have OPPS head. My intention is to use only INPA and heads, connecting to them remotely over TCP/IP.

In ediabas.ini under "Interface" I tried "REMOTE" and "REMOTE:Remote.ini" parmeters but it doesn't help

When using REMOTE I'm getting error:
EDIABAS Fehler 159, NET-0009: TIMEOUT

When using REMOTE:remote.ini I'm getting error:
Fehler 45, IFH-0035: CONFIGURATION ERROR

Durin INPA installation it is possible to install EDIC drivers for heads. Does anybody knows where can I download drivers for OPPS and yellowhead?

Also where is location of drivers files after installation?

Thanks!

[Rallyfinnen]

It should be possible, but since I have not tried it myself, maybe somebody else has some info?

[steeee]

Does anyone know how ifhserv32.exe works, what are the parameter of the program and what it does. I think I might be close but I just cant ifhserv32.exe to display an ip address on the taskbar. What can I do to get it working properly?

And secondly to any one who has DIS/GT1 V44 working, does V44 or V39 need the Diaghead program to run or does it work without it.

[zigzagsky]

There are a couple of things to see if IHFServ is running properly and display an IP address.

Firstly, drop down to the command line mode in GT1 and run the APITest. This should connect to the IHFServ app running under Windows and it should then show an IP address.

The second thing to try is to actually connect to the car. This should also then get the GT1 to connect to the diaghead via IHFServ and the Ip should get displayed.

As for the Diaghead emulator, you need it with both V39 and V44 in order for the GT1 to 'see' the OBD adapter running under Windows.

[capstorm]

Regarding my issues with LAN connection between OPPS head and PC, I finally found source of problem.

ediabas.ini should contain:
Interface = REMOTE
RemoteHost = 192.168.68.XX
Port = 6801

For OPPS to work wtih INPA station, OPPS head should first be unregistred form current station (you can do that through web interface connecting over LAN to head IP). After that INPA has found head and registered. Now everything works like charm now.

Thanks for help!

[vantaam5]

Please,guys I need help!
When I try to run the API test I only get the error message:
"fault in execution of the function chosen.
Fault number:-2"

Thanks!

Have the DIS reconizing the car with the INPA interface and the diaghead emulator running

[Beemer187]

Please,guys I need help!
When I try to run the API test I only get the error message:
"fault in execution of the function chosen.
Fault number:-2"

Thanks!

Have the DIS reconizing the car with the INPA interface and the diaghead emulator running

Make sure ifhserv32.exe is running too.

[vantaam5]

It is running!
And it detects the car,reads the modules and so on...

[steeee]

Finally done it, it works:redspot, DIS, thanks to zigzagsky for that last crucial part of information that I needed. Not how do I get automatic detection working:buttrock.

[shzeps]

Hi Group, I need to ask the experts about my DIS install. I have installed V44 on VMware and set up ip configs so that when running diaghead emulator it shows connected both in DIS and on the emulator. I have installed INPA and using a VAG-COM hex can serial interface (with pins 7 + 8 bridged), on a physical port (com1) can communicate with various modules on an e46 thru obdII. INPA does not recognize the ignition being on but still works.

When I run DIS and go into diagnosis it does not auto identify, nor does it connect to any control units manually. The error shown is a communication problem to the diagnostic head code 200.159. Yes I do have ediabas server, ifhserv32, and diaghead all running.

Is there a way to test the connection between my interface and diaghead emulator? Can my interface work only with INPA and not DIS?

I would appreciate any suggestions. Thanks

[zigzagsky]

Finally done it, it works:redspot, DIS, thanks to zigzagsky for that last crucial part of information that I needed. Not how do I get automatic detection working:buttrock.

What are you using as your interface? If it's based on the FTDI USB chip i.e. a VAG one then you need to get inside the interface and solder pins 17 & 18 of the actual FTDI chip to ground. Note that this is NOT for the faint hearted as the pins are tiny.

[shzeps]

The cable is a VAG-COM HEX-CAN serial RS232 (not USB) original cable.

[steeee]

i am using a rs232 port on my laptop, so i have a rs232 cable that connects to the my bmw. from ebay like this one Ebay Uk Item number:280420080631

[shzeps]

Thanks for the advice. I am not going to fight the system. I am going to order up some cables first like the ones you referenced and see where that takes me.

[kennycoder]

Hey guys.. finally I've managed to put DIS to communicate with my computer via VMware... it pings and so on. The problem is that EVERY time i rebuild the kernel after using scoadmin, DIS won't boot.. The only thing i see is a black screen with a cursor. What am I doing wrong?

Thanks in advance.

[randomy]

does it accept commands?

try running: init 5

[aise]

Hey guys.. finally I've managed to put DIS to communicate with my computer via VMware... it pings and so on. The problem is that EVERY time i rebuild the kernel after using scoadmin, DIS won't boot.. The only thing i see is a black screen with a cursor. What am I doing wrong?

Thanks in advance.

i had the same issue at the beginning. this is what i did, i configured all parameters nessesary (etc/hosts, scoadmin etc.) and then changed to fister translator. every time i changed to fister before other parameters were configured it wouldn´t boot to DIS.

DISv55 and SSSv32 are both running perfect:evil2 no need for newer software.

[ccfj1]

How do you get to the GT1 console, I run it on a laptop and can use the mouse and only "crtl+alt" seems to work.

[kennycoder]

Hello. Thanks for help ;)

Finally I've got everything running smoothly :p Now I have two virtual machines.. one with DIS V57 just for diagnostics (dunno why SSSv32 won't install on it) and another with DIS V44 for possible future coding.

I've ordered EDIABAS / INPA interface from ebay (china stuff..). With this interface and IFHSrv32 / BMW Diagnostic head emulator I will be able to do everything, correct? I don't need the "yellow box" that is for sale everywhere, right?

Cheers

@ccfj1: ctrl+alt+f1 or f2 or f3.. (F2 is for X server where DIS is running)

In a virtual machine on VMware it's ctrl+alt+space+f1..2..3.

[darkstarmedia]

So I have everything working except automatic detection... I am using the carsoft west cables... is there a trick to this? I am not using any usb adapters...

[ccfj1]

OK, have it all installed gt1/dis v44, inpa and ediabas,

dis/gt1 finds the bmw diag head, and from the dis console I can ping 30,31 and 32 but it would not ping .1.

I'v done the scoadmin, and deleted the 3 drivers and added them again(as per shoulders readme), rebuilt the kernal and init 6 to reboot.

however when I reboot the dis I get the
error portmapper 192.168.68.20 not found twice and the dis now sits at a black screen and mouse pointer, I can get into the console, but thats it.

Any one have any ideas.

thanks

======Update from here===

My INPA/EDAIBAS lead turned up today and I can report success.

Here is a recap of what I have achieved:
-successfully installed carsoft
-successfully installed INPA\EDIABAS
-successfully installed GT1\DIS v.44
-successfully installed TIS
-successfully read modules using Carsoft interface
-successfully read car with INPA using INPA OBDII interface
-successfully read car with GT1 using INPA OBDII interface

My results with DIS:
-launch ifhrsrv32, then boot DIS, from console run the /usr/edaibas/bin/apitest
-ifhsrv32 displays IP 192.168.68.30.
-BMW diaghead running and connected.
-Start Diagnosis, and auto-detect car works.

Problems;
- used scoadmin and followed shoulders config setup, now bottom row of lights stay out (tablet touch screen).
- reconfigured the network interfaces and this seems to work.
- still can't ping 192.168.68.1

Config
-remotehost=192.168.68.1, port=6801 in ediabas.ini
-/etc/hosts like this:

127.0.0.1 localhost
192.168.68.30 gt1ap gt1ap
192.168.68.32 gt1ap2 gt1ap2
192.168.68.31 gt1ap1 gt1ap1
192.168.68.1 mobilteil

-laptop name = mobilteil

Diaghead found in DIS as 192.168.68.1 mobilteil

I will be able to test a bit more tomorrow, but may well trash everything and start again, now that I know the steps needed.

Thanks for all the posts and help.

[aise]

ccfj1, you need only 1 network driver for dis.

127.0.0.1 localhost
192.168.68.30 gt1ap
192.168.68.1 mobilteil

[ccfj1]

Thanks aise, (you the same asie from xoutpost mate?)


ccfj1, you need only 1 network driver for dis.

127.0.0.1 localhost
192.168.68.30 gt1ap
192.168.68.1 mobilteil

So delete .31 and .32 from the "/etc/hosts" file only?

I trashed and reinstalled all again last night and all the lights light up when dis/gt1 in running, just need to test in car.

Still can't ping 192.168.68.1 from dis console????

[aise]

Thanks aise, (you the same asie from xoutpost mate?)



So delete .31 and .32 from the "/etc/hosts" file only?

I trashed and reinstalled all again last night and all the lights light up when dis/gt1 in running, just need to test in car.

Still can't ping 192.168.68.1 from dis console????

yes the same:)

delete them under scoadmin (DIS only needs the loopback driver and 1 network driver 192.168.68.30).

you should be able to ping 192.168.68.1 from unix. something is blocking from windows side. windows firewall or antivirus firewall. i had the same thing with F-Secure so i added vmnet1 to trusted network adapters list.

[ccfj1]

yes the same:)

Thought it was, lol small world mate.


delete them under scoadmin (DIS only needs the loopback driver and 1 network driver 192.168.68.30).OK, will try that, thanks


you should be able to ping 192.168.68.1 from unix.That's what I thought.


something is blocking from windows side. windows firewall or antivirus firewall. I've added exceptions for the firewall, I have a look at avira (antivirus), thanks for the tip.


i had the same thing with F-Secure so i added vmnet1 to trusted network adapters list.OK, will look at that.

It did sort of work in the car, it detected the car (in the diagnosis), but when I went to coding it said diaghead does not have good signal (or similar).

Thanks.

[aise]

diaghead -> options, signal quality (default is 75%).

[ccfj1]

diaghead -> options, signal quality (default is 75%).

Yeah worked that out, which diaghead is preferred? left or right?

Also, just deleted the network drivers and added the .30 one, reconfigured the kernel, and init 6 (then init 5) and now only have a black screen, and getting "init command is respawning too rapidly. check for possible errors." in console screen.?

Any ideas mate?

[aise]

left (default), i never used commands init 5 or 6 and everything is working perfect. i just installed dis, configured networks, configured etc/hosts and then changed to fister (dis -> admin -> calibrating touch shield). so start over:D (i did 5-6 installations myself before i got it working)

is your vmnet1 ip 192.168.68.1? look it up under windows network connections, also NAT should be disabled under vmware virtual network editor

[kennycoder]

Does anyone have a solution for a automatic identification problem? Everything works fine except car/key coding. In the diagnostic menu if I select the car manually, it works but auto identification doesn't.

[darkstarmedia]

Does anyone have a solution for a automatic identification problem? Everything works fine except car/key coding. In the diagnostic menu if I select the car manually, it works but auto identification doesn't.

I am in the same situation... I think it's a cabling issue.... the carsoft cables don't pass-through a certain voltage signal so the software won't do the auto-detect.

On some cables there is a mod you can do but I am not sure what to do on these cables....

Richard

[randomy]

I am also uncertain how to get auto-detect to work on the carsoft cable. I'd be willing to try and mod mine if anyone had a compelling suggestion?

[darkstarmedia]

I am also uncertain how to get auto-detect to work on the carsoft cable. I'd be willing to try and mod mine if anyone had a compelling suggestion?

As would I but I have no idea where to start... I have fair soldering skills and basic electronics knowledge but that's it.... I don't know where to start...

Richard

[darkislight]

Anybody still have a copy of OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip ?

please pm for email

[kennycoder]

Actually I'm not using carsoft cables.
I've got one of these (http://cgi.ebay.co.uk/NEW-Ediabas-INPA-4-BMW-100-compatible-OBDII-Interface_W0QQitemZ290376649082QQcmdZViewItemQQptZ UK_CarsParts_Vehicles_CarParts_SM).

[valymad]

hello,
i see many of you guys configured gt1 to work with INPA interface or a vag/kkl modificated.
i have a question,i have the gt1 and the vag kkl interface modificated with ignition circuit,work fine with diagnose and autodetect,but in coding/programing work only the ZCS/FA coding menu ,because i activated a signal stalk with BC button and it work.
But the car/key memory don't work it says can't read zcs....
the question is at you guys work this menu (car/key memory)?

[shony]

hi,
When i'm trying to connect Dis with diag head emulator it gives an error .
GT1 has a bad or no connection with usb floppy drive... please use some Teac floppy..
Searching doesn't give any result. What have I done wrong?

[randomy]

hello,
i see many of you guys configured gt1 to work with INPA interface or a vag/kkl modificated.
i have a question,i have the gt1 and the vag kkl interface modificated with ignition circuit,work fine with diagnose and autodetect,but in coding/programing work only the ZCS/FA coding menu ,because i activated a signal stalk with BC button and it work.
But the car/key memory don't work it says can't read zcs....
the question is at you guys work this menu (car/key memory)?

That menu does not work for me (E36).
Can you tell me how you modified the cable to get auto-detect to work?

[Voyd]

That menu does not work for me (E36).
Can you tell me how you modified the cable to get auto-detect to work?

^^^
This please!

[notease]

Following this topic for a while, willing to give it a try myself now :)

Could someone please send me a file/url with /OBD_diagnose_with_round_20pins_-_318ti_org_forum.zip file ? Thanks out of Holland

[fcanha]

Greetings,

I have been reading this post and all relevant posts from other major resources for weeks now. I have d/l all the software, got an IBM T30 for $200 here in San Diego, CA. But I could not find the following:

OBD_diagnose_with_round_20pins_-_318ti_org_forum.zipCan someone please share this?

Also, why doesn't someone just share a working VMware ISO?

Regards,

Frank
(http://forums.bimmerforums.com/forum/showthread.php?t=803202&page=9#)

[notease]

Could anyone please invite me to bmwecu site ?
My mail zz1900 (at) hotmail.com
Much thanks out of The Netherlands

[shzeps]

Hi again, I finally have bought a "NEW Ediabas/INPA 4 BMW 100% compatible OBDII Interface" http://motors.shop.ebay.com/cheery-shopping/m.html?_nkw=ediabas&_sacat=&_trksid=p3911.m270.l1313&_odkw=&_osacat=0 (http://rover.ebay.com/rover/1/711-53200-19255-0/1?campid=5335818596&toolid=10001&mpre=http%3A%2F%2Frover.ebay.com%2Frover%2F1%2F711-53200-19255-0%2F1%3Fcampid%3D5335818596%26amp%3Btoolid%3D10001 %26amp%3Bmpre%3Dhttp%253A%252F%252Frover.ebay.com% 252Frover%252F1%252F711-53200-19255-0%252F1%253Fcampid%253D5335818596%2526amp%253Btool id%253D10001%2526amp%253Bmpre%253Dhttp%25253A%2525 2F%25252Frover.ebay.com%25252Frover%25252F1%25252F 711-53200-19255-0%25252F1%25253Fcampid%25253D5335818596%252526amp% 25253Btoolid%25253D10001%252526amp%25253Bmpre%2525 3Dhttp%2525253A%2525252F%2525252Fmotors.shop.ebay. com%2525252Fcheery-shopping%2525252Fm.html%2525253F_nkw%2525253Dediab as%25252526amp%2525253B_sacat%2525253D%25252526amp %2525253B_trksid%2525253Dp3911.m270.l1313%25252526 amp%2525253B_odkw%2525253D%25252526amp%2525253B_os acat%2525253D0).

I have installed a few different versions of INPA. The instructions that came with it were vague. My question, I have 95 E36 with 20 pin connector. I connect to the car with the 20pin interface to obd2 interface thru inpa and get battery on but NO ignition signal. It will ONLY connect to airbag and ews nothing else. Should interface type be set to OBD or ADS? I think OBD.

Does the ignition on only work with the newer cars that use obd2 interface without 20 pin, and my car is too old?

One more question. I am also trying to get DIS to work. What does the apitest test? I can ping back and forth in vm and windows and even have the diaghead connected, but when I run an apitest I can't pass it. I get NET-0016 HOST ERROR. I changed some settings and now I get 0002-ILLEGAL VERSION. Do I need to be hooked up to a car to run the test? Do I need diaghead running? or just ediabas and ifhserv to pass the test. Now for some reason the lower set of leds are not lit up for the tester, the diagnostic head leds are lit. Does this have something to do with the system config in admin?

As always any help would be appreciated.

[valymad]

Hi again, I finally have bought a "NEW Ediabas/INPA 4 BMW 100% compatible OBDII Interface" http://motors.shop.ebay.com/cheery-shopping/m.html?_nkw=ediabas&_sacat=&_trksid=p3911.m270.l1313&_odkw=&_osacat=0.

I have installed a few different versions of INPA. The instructions that came with it were vague. My question, I have 95 E36 with 20 pin connector. I connect to the car with the 20pin interface to obd2 interface thru inpa and get battery on but NO ignition signal. It will ONLY connect to airbag and ews nothing else. Should interface type be set to OBD or ADS? I think OBD.

Does the ignition on only work with the newer cars that use obd2 interface without 20 pin, and my car is too old?

One more question. I am also trying to get DIS to work. What does the apitest test? I can ping back and forth in vm and windows and even have the diaghead connected, but when I run an apitest I can't pass it. I get NET-0016 HOST ERROR. I changed some settings and now I get 0002-ILLEGAL VERSION. Do I need to be hooked up to a car to run the test? Do I need diaghead running? or just ediabas and ifhserv to pass the test. Now for some reason the lower set of leds are not lit up for the tester, the diagnostic head leds are lit. Does this have something to do with the system config in admin?

As always any help would be appreciated.



yes,in INPA with 20 pin connector on my e36'96 i don't have the ignition signal ON but on cars with obd2 conector i have ,this is because the 20pin adapter that you have don't have the pin1 from obd2 to pin 16 on 20 pin connector .
my INPA work good on E36 without ingnition ON ,and is set it on STD:OBD.

In GT1 folow the instructions that are here on forum ,config the ediabas.ini with port:6801 and use the diaghead emulator .mine work without to connect the interface to the laptop.

[shony]

Still can't understand what I'm doing wrong. Tried to install 4 different dis versions and I always get the same error trying to setup the diag head or host settings. Any ideas?
http://img130.imageshack.us/img130/1128/73903041.jpg

[valymad]

try to disable the floppy drive in vmware,mine is disable.

[shony]

I removed floppy in vmware workstation every time I installed DIS.

[randomy]

I could post my vmware image of DIS, maybe pm for info, I may not want to post it here publicly.

[shony]

I could post my vmware image of DIS, maybe pm for info, I may not want to post it here publicly.
Thanks!! But it looks like I've found the answer on different forum.
I was trying to add the diaghead instead of configuring connection on another page :) so simple.. finally I got my DIS up and running!

[darkislight]

Thanks!! But it looks like I've found the answer on different forum.
I was trying to add the diaghead instead of configuring connection on another page :) so simple.. finally I got my DIS up and running!

So share the other forum...always nice to share:cool

[crapsnack]

I am trying to download this working vm ware image, but it is on bad host. Does someone have this already and can send to me?

http://sharecash.org/download.php?file=201491
http://sharecash.org/download.php?file=201608
http://sharecash.org/download.php?file=201547
http://sharecash.org/download.php?file=201545
http://sharecash.org/download.php?file=201492
http://sharecash.org/download.php?file=201572
http://sharecash.org/download.php?file=201489
http://sharecash.org/download.php?file=201487

[crapsnack]

I have found working DIS on host, but download is bad. Does someone have this and can send to me?
It's a working vm ware file.

[shzeps]

Hi, by some miracle after playing with 6 different installations and trying every combination possible I succeeded in in running an apitest. My question, is there a way to save the setting for the apitest so that dis will reconnect the next time I start ifhserv and dis or do I need to go into the apitest every time? I ran the test, then selected 0, then in the bmwecu version chose 1 to restart ediabas and update settings. Dis does not seem to retain that info, when I restart ifhserv it does not show an ip.

One more question, is there a proper way to power down dis or is it ok to just hit the stop button in vmware?

[randomy]

As would I but I have no idea where to start... I have fair soldering skills and basic electronics knowledge but that's it.... I don't know where to start...

Richard

Check out this thread I found, I think this is what we need:
http://www.socalbavarians.com/bmwecu/

[darkstarmedia]

[QUOTE=randomy;18217935]Check out this thread I found, I think this is what we need:
[url]

yep.. I can use that to create a simple bridge circuit to enable igition sensing... I am awa for the holidays but I will be back after the first of the year...

richard

-From Palm Pre

So I finally got around to looking at my carsoft interface.... from what I can tell the unit is not passing Batt or ign to the db9 port.... it is passing the data lines but it looks like the only place the batt voltage is going to is the power led.... I have a recient chinese unit bought from carsof west... on the back of the pcb in the box it says CS6.5 and has a date in 2008..... Really dissapointed as i spent $70 on this but I am going to try a different interface cable when I can afford it....

Richard

Richard

[randomy]

If you can decipher what needs to be done from the information in that post, I'd be very grateful if you could return and let me know what you did, and what you attempted.

[Dayclone]

Guys I think I got my GT1 v55 and USB - RS232 - Ediabas connector working.

It won't do the auto recognition but I can manually select the car model. I haven't yet hooked it up to my vehicle as the weather has been shitty here but I'll keep you guys posted.

[aise]

i installed DIS v57 with v44 coding, used v52 base. autodetect and diagnostics work, haven´t tried coding yet.

[gege21]

Hello

you know the login and password for the console SCO is normally
login: DIS
PWD: admin

but this does not work

Thank you for your response

gerald

[aise]

root
password

usually!

[gege21]

jai also try

root
password

it does not work

we just reset the password console sco?

Thank you for your response

Gerald

[crapsnack]

You can reset password, directison are on other forum here http://www.digital-kaos.co.uk/forums/f68/bmw-dis-base-v52-sco-unix-66332/

[asids]

Hello all,

I can't get to work SSS Progman in VMWare with BMW Diag Head emulator v1.2 software. GT software works fine, Progman works fine with real OPS head, but do not see emulator software. I check everythingand have to be fine. I think I have not fully working diag head emulator software. May be some one who have this working can share his Diaghead emulator software?

Thanks a lot,
Andris.

[aise]

progman doesn´t need diaghead, only ifhsrv. u need to use correct changes.iso image to use inpa interface.

[crapsnack]

I am trying to download this working vm ware image, but it is on bad host. Does someone have this already and can send to me?

http://sharecash.org/download.php?file=201491
http://sharecash.org/download.php?file=201608
http://sharecash.org/download.php?file=201547
http://sharecash.org/download.php?file=201545
http://sharecash.org/download.php?file=201492
http://sharecash.org/download.php?file=201572
http://sharecash.org/download.php?file=201489
http://sharecash.org/download.php?file=201487

This is working image! Had to register to download it is only bad thing.

[asids]

progman doesn´t need diaghead, only ifhsrv. u need to use correct changes.iso image to use inpa interface.

Thanks for reply!

Could you share this correct image?

BR,
Andris.

[crapsnack]

[/URL][URL]http://rapidshare.com/files/166005128/changes.rar (http://rapidshare.com/files/166005128/)

[asids]

Thanks a lot!

As I understand after I look trough scripts, this permanent changes do not allow to use real OPS or OPPS head in future. I have heard from one of my neighbors he has installed SSS Progman v32 and running with OPPS and INPA adapter in parallel. When I describe my problem with my SSS Progman installation he reply - he don't remember all details, but he done installation when Emulator is needed for INPA adapter and if you connect real OPPS head also all works fine.

Do some one have such knowledge?

[primeral]

It did sort of work in the car, it detected the car (in the diagnosis), but when I went to coding it said diaghead does not have good signal (or similar).

Thanks.


diaghead -> options, signal quality (default is 75%).

I've been scouring this thread and other resources linked from it ... I feel so close yet so far. apitest happens as directed, emulator connects when DIS is loaded, but when doing diagnostics I get the signal quality message as well. As recommended, I increased the signal quality, and those changes are reflected in DIS. 85%, 90% ... 100%, and I still get the signal quality error. What am I missing?

details: unmodified blue USB-KKL cable from Germany, OBD2 port in 02 E39 M5, V44 on VMware 6.5, Windows 7, APItest from DIS works, INPA from Windows works.

Thanks for the pages of information, though. I couldn't have gotten this far without you guys!

[Snowcatxx87]

I've been scouring this thread and other resources linked from it ... I feel so close yet so far. apitest happens as directed, emulator connects when DIS is loaded, but when doing diagnostics I get the signal quality message as well. As recommended, I increased the signal quality, and those changes are reflected in DIS. 85%, 90% ... 100%, and I still get the signal quality error. What am I missing?

details: unmodified blue USB-KKL cable from Germany, OBD2 port in 02 E39 M5, V44 on VMware 6.5, Windows 7, APItest from DIS works, INPA from Windows works.

Thanks for the pages of information, though. I couldn't have gotten this far without you guys!

I too have signal quality message. It evenually finds my car, 04 330ci, diagnosis seems ok - intermittent errors though. This is using an eBay inpa compatible cable. No coding with gt1 umfortunately??

Anyone know how to install tis with easydis?

[thomashood]

No idea if this works but it came up when I was googling:

http://www.demonoid.com/files/download/HTTP/1515480/775222

Caveat emptor

[darkislight]

To Snowcatxx87


Anyone know how to install tis with easydis?

1. Mount TIS in Daemon Tools
2. Launch GT1 in VMware
3. Goto Admin in GT1
4. Activate CD in GT1 (it should show TIS)
5. Select Installion under TIS

You should know the rest its the same as installing DIS

Good Luck

[Snowcatxx87]

Hey dark, I have blamed it on my TIS disc not being absoulte kosher. I have done exactly what you have explained before I posted. Thanks for the confirmation.

[acha]

hi guys

How can i edit my /etc/hosts file.

cause this is how it looks

etc/hosts file
172.0.0.0.1 localhost
172.20.251.212 gt1ap
192.168.68.32 gt1ap2 gt1ap2
192.168.68.30 gt1ap gt1ap
192.168.68.31 gt1ap1 gt1ap1

the 172.20.251.212 also shows in DIS under system configurations

To what IP should i set it to and where and how can i do this?

thanx in advance

hi randomy

can u maby send me the VMware dis immage plz?


I could post my vmware image of DIS, maybe pm for info, I may not want to post it here publicly.

[vantaam5]

I got a V39 where diagnosis and coding work and a V54 where only diagnosis works.
On both of them I can't use the arrow(right side bottom) in the start screen where it is possible to get in the component test!

Anyone of you got that working and can activate Vanos solenoides or ifnition coil,...

[Katvis]

Hi guys
This thread has helped me a lot to get INPA up and running but I still have problems to connect the GT1 to the vehicle.

A few questions though, if you have a look at the screen shots you will see that my DIS is connected to the BMW head emulator, does this means the path to the emulator works correctly?, because if I try to do a diagnostic it gives the following error...

http://i895.photobucket.com/albums/ac152/coenraadg/DISFault.jpg

If this path works correctly is there another place to do fine adjustment between the BMW head emulator and the INPA cable? The LED light at the bottom of the emulator does not light up at all?

http://i895.photobucket.com/albums/ac152/coenraadg/BMWEmulatorhead.jpg

Is there a place to edit the ifhsrv.exe server settings?

If I start the APITEST file it automatically start another server with the name of EDIABAS server for Win32, is this correct? Can you use this server instead of the ifhsrv.exe server to run the BMW head emulator?

Any help will be appreciated
Cheers
C

hi again
I got it to work..
Had to delete and reinstall the networks in SCOADMIN a few times before it worked, again thank you very much for everybody who gave input and advise here
Cheers
C

[Katvis]

Hi guys
Update for the interested...;)
I did not battle to setup DIS on VMWare but what I did battle with was to access the diagnostic pages in DIS. Even after I did the D-Bus diagnostics and all the tests pass I could not diagnose the DME, so I went back to the many webpages I saved that explained the inner workings and eventually I could diagnose the DME to get to the "expert" menu in DIS. At the moment I can monitor many components, I can read the live data from the Vanos position but when I try and run the Vanos test I get the message that the engine must run to be able to test the Vanos.

I suspect my DIS can not see the engine running because Pin no 9 on the OBDII plug is not connected. Does anybody have advise for me regarding this please?

Cheers
C

[ecuconnection]

I have tryed everything. I can only seem to one set of the led's to light up .
I dont know where to go from here .

[Katvis]

I have tryed everything. I can only seem to one set of the led's to light up .
I dont know where to go from here .


Don't give up..! What I did was to remove the three LAN networks in SCOADMIN and reinstall them. I know there are some people who say you only need one but I followed the many write ups who asked for three. Remember to add the new networks as TCP/IP networks. Exit Hardware, rebuild the kernel and exit till prompt, input "init 6" to restart DIS and go to the System page again to see what IP address you have. I found that if I did not have 192.168.68.32 my bottom lights went out if I connect to the emulator. (This is for the LAN settings on my laptop)
If it does not work the first time delete the three networks and do it again, that worked for me and was the only way I could get the IP to change to the .32 at the end.

Cheers
C

[ecuconnection]

Don't give up..! What I did was to remove the three LAN networks in SCOADMIN and reinstall them. I know there are some people who say you only need one but I followed the many write ups who asked for three. Remember to add the new networks as TCP/IP networks. Exit Hardware, rebuild the kernel and exit till prompt, input "init 6" to restart DIS and go to the System page again to see what IP address you have. I found that if I did not have 192.168.68.32 my bottom lights went out if I connect to the emulator. (This is for the LAN settings on my laptop)
If it does not work the first time delete the three networks and do it again, that worked for me and was the only way I could get the IP to change to the .32 at the end.

Cheers
C

Thank you! I finally got it . Turns you you were correct about going back and adding the adapters over and over (3times) :) Now I wonder if I can install v57 over v44 and not have to many problems or should I keep the current version ?

[Katvis]

I am very glad you managed..;)
If you want to do programming on your car you will need DIS 44, I have both although I do not know if there were improvements made for our old series car in the DIS 57 and if they simply added new version of cars on DIS 57.

Cheers
C

[ecuconnection]

Anybody know where you can turn of the DRL's on a e46 in the programing ?

How to steps would be nice :)