I know that I have one or more bad fuel lever sensors. Guage is stuck on empty with low fuel light on. Later today after work I will attach to the car and see what happens.
Well after a few weeks of research, trial and error, I finally made the connection between DIS and shown below in the attached screen shot below. I'm close.but not quite there :rolleyesĪhhh 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 :) 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 reset the airbag light on my E39 and the SES light on my E53. Also have the ODBII to 20pin for under the hood. Yes I'm using INPA/Ediabas on a Fujistu (XP Pro) tablet with USB to OBDII adapter. 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. when running apitest IFHServ starts to show "192.168.68.32" edited /etc/ediabas.ini RemoteHost = Diaghead (also tried 192.168.68.1) Edited c:\ediabas\bin\ediabas.ini to RemoteHost = 192.168.68.1 and Ediabas/Inpa runs fine usin my Interface
I can also succesfully Ping 192.168.68.1 using the console-comand. it only shows when entering the apitest command. The Dissoftware shows me the same IP in the admin-menu for GT1AP.īut how do I get DIS to use Ediabas? IFHServ shows nothing when I start the DIS-appl. 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. I got myself an Interface which works fine with Ediabas/Inpa. 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.
0 kommentar(er)
