Settings in GT1/DIS to use the INPA Interface ?

[Enforc3r]

I have downloaded form your ftp Base V52 and dis 57 how to install same as v44?

[Beemer187]

I have downloaded form your ftp Base V52 and dis 57 how to install same as v44?

Use easyDIS base v44 + DIS V57, it's not so difficult to configure than Base v52.

[Enforc3r]

Okay know API tests work (without FISTER Protocol). I had an bad EDIABAS version (funny). IFHSrv32 shows the IP adress 192.168.68.32
Again some Questions to the Leets
1. How can I test that DIS has a connection to my car
2. Can I delete the "error memory" with DIS
3. I am able to delete the airbag error with INPA but when I try to delete the error and lock from the "parking heater" I get an error. How to release the lock?

[rebel.ranter]

VMWare needs 3 virtual network adapters to VMnet1.

Do you know why it needs 3 adapters? Mine works with only one & no gt1ap1 line. I don't understand why it would need the three. IFHSRv32 only ever shows 192.168.68.30 for me.

EDIT: Just out of curiosity I modified by hosts file to include the gt1ap1 line (192.168.68.31) & I also added two more Network Adapters to my Virtual Machine. I restarted the whole thing I ran DIS. Here's the interesting bit, I could always ping 192.168.68.30 (gt1ap) from my real machine, and I could always ping 192.168.68.1 from inside the virtual machine. Both before & after the changes I could not ping 192.168.68.31 & 192.168.68.32. This leads me to the conclusion that these two lines are not needed. Beemer187 do you feel like doing a similar experiment with your set up to see if it actually makes any difference?

[Beemer187]

Do you know why it needs 3 adapters? Mine works with only one & no gt1ap1 line. I don't understand why it would need the three. IFHSRv32 only ever shows 192.168.68.30 for me.

I always use this setup and I really need 3 virtual network adapters.
http://dvsntt.com/GT1/

[rebel.ranter]

I always use this setup and I really need 3 virtual network adapters.
http://dvsntt.com/GT1/

Thanks for getting back, I was curious as much as anything. I have a networking background & it doesn't make sense to have multiple cards to me.

[Enforc3r]

Okay know API tests work (without FISTER Protocol). I had an bad EDIABAS version (funny). IFHSrv32 shows the IP adress 192.168.68.32
Again some Questions to the Leets
1. How can I test that DIS has a connection to my car
2. Can I delete the "error memory" with DIS
3. I am able to delete the airbag error with INPA but when I try to delete the error and lock from the "parking heater" I get an error. How to release the lock?

please need HELP

EDIT: So I tried to read out DME without Success. I don't have changed to FISTER config. I will give it a try. My Interface is http://www.doitauto.de/index.php?lan..._id=179&cat=31

EDIT2: Diagnostic works but coding not! I can't delete the fault memory form my parking heater

[rebel.ranter]

EDIT2: Diagnostic works but coding not! I can't delete the fault memory form my parking heater

Coding was removed after v44, you use Progman for coding after that. Not sure on the parking heater error deletion.

[RobertV1]

I have GT-1 loaded and running, but am having issues configuring my INPA compatible OBD/ADS Interface from China. I think that I have gone down the wrong path and wanted to ask the experts before I did more software damage I turned the VM off and switched to FISTER in DIS. I have three network adapters setup in VM v.6. I thought this was all I needed to do, but no go. I have a 93 525i with a connector on pin 15 and switch the Interface to ADS. When the key is on the IGN light is on.
What am I doing wrong?
TIA
RobertV

[David Mc]

Robert, you need to read the "Read this first" pdf in the Easy GT folder on the 4shared website here Easy GT folder http://www.4shared.com/dir/ccW_Gr3x/Easy_GT.html password is help

[RobertV1]

David,
Thank you for the link to that file. I did follow those directions and I am getting much further. All the bar lights are lit for the monitor, but the bar lights for the yellow diag head are not lit. Now I'm getting a Warning: There is no connection to a diagnostic head.
EDIT to add more info :
I click on OK to manual connect and then the IFH-Server then shows 192.168.68.30. I try to run any diag at this point and get the system error: -1 and IFH-0003 Datatransmission to interface disturbed.
I'm sure there is something simple I'm missing. I am attempting to search on this error here with no luck. I am running Dis V44 windows XP and this is a link to the interface I have: http://cgi.ebay.com/ebaymotors/BMW-I...p;toolid=10001

EDIT: YES it was something simple. I needed to set and load the ADS in INPA. Running a brief test right now

Bummer: no control unit found. Must still be doing something wrong.
No free diag heads either.

TIA
REV

[kneescrap]

After mutch reading and failing trying and some thinking... i have finally got DIS innstalled on the VM. I'm running Windows 7 64 bit. But now i'm stuck..
I have the modified VAG KKL cable with soldered pin 7 and 8, no ignition mod yet.
I start the IFHSrv32
I start the diagheademulator
start the VM and once DIS loads i press RUN on the diagheademulator
But when i press connect on the connection setup i got this message

Any solution here ?

the "config" diagnostic head menu


And the "config" system menu





Can someone tell me whats wrong here ?

i feel close.. but i'm sure i'm still far away..

[RobertV1]

David,
Thank you for the link to that file. I did follow those directions and I am getting much further. All the bar lights are lit for the monitor, but the bar lights for the yellow diag head are not lit. Now I'm getting a Warning: There is no connection to a diagnostic head.
EDIT to add more info :
I click on OK to manual connect and then the IFH-Server then shows 192.168.68.30. I try to run any diag at this point and get the system error: -1 and IFH-0003 Datatransmission to interface disturbed.
I'm sure there is something simple I'm missing. I am attempting to search on this error here with no luck. I am running Dis V44 windows XP and this is a link to the interface I have: http://cgi.ebay.com/ebaymotors/BMW-INPA-Ediabas-OBD-ADS-Interface_W0QQcmdZViewItemQQ_trkparmsZalgoQ3dLVIQ2 6ituQ3dUCIQ26otnQ3d3Q26poQ3dLVIQ26psQ3d63Q26clkidQ 3d6305132556306716258QQ_trksidZp5197Q2em7QQcategor yZ43989QQitemZ160499165761?amp;mpre=http%3A%2F%2Fc gi.ebay.com%2Febaymotors%2FBMW-INPA-Ediabas-OBD-ADS-Interface_W0QQcmdZViewItemQQ_trkparmsZalgoQ3dLVIQ2 6ituQ3dUCIQ26otnQ3d3Q26poQ3dLVIQ26psQ3d63Q26clkidQ 3d6305132556306716258QQ_trksidZp5197Q2em7QQcategor yZ43989QQitemZ160499165761&toolid=10001&am p;mpre=http%3A%2F%2Fcgi.ebay.com%2Febaymotors%2FBM W-INPA-Ediabas-OBD-ADS-Interface_W0QQcmdZViewItemQQ_trkparmsZalgoQ3dLVIQ2 6ituQ3dUCIQ26otnQ3d3Q26poQ3dLVIQ26psQ3d63Q26clkidQ 3d6305132556306716258QQ_trksidZp5197Q2em7QQcategor yZ43989QQitemZ160499165761%3Famp%3Bmpre%3Dhttp%253 A%252F%252Fcgi.ebay.com%252Febaymotors%252FBMW-INPA-Ediabas-OBD-ADS-Interface_W0QQcmdZViewItemQQ_trkparmsZalgoQ3dLVIQ2 6ituQ3dUCIQ26otnQ3d3Q26poQ3dLVIQ26psQ3d63Q26clkidQ 3d6305132556306716258QQ_trksidZp5197Q2em7QQcategor yZ43989QQitemZ160499165761%26amp%3Bamp%3Btoolid%3D 10001&toolid=10001

EDIT: YES it was something simple. I needed to set and load the ADS in INPA. Running a brief test right now

Bummer: no control unit found. Must still be doing something wrong.
No free diag heads either.

TIA
REV

I can ping 192.168.68.1 in windows. I did change the LoadWin32 = 1 since I'm running XP. I have tried running the BMW DiagHead sofware with the ifhsrv32 before running DIS. I disabled my ethernet adapters. I'm still in the same spot as quoted above no control unit found nor are there any bar lit for the yellow diag in DIS. Any suggestions on what I'm missing? I feel that I'm close, but need some help to get over this last hurdle(s).

[David Mc]

Robert,
Why have you disabled your ethernet adapters and why are you running a Diaghead Emulator??? If you have DIS installed on the EasyDIS base, translator set to Fister and processes configured so that vm is set to not run, you do not need a diaghead emulator and similarly, since you are connecting directly to your interface you do not need the coloured signal strength bars on the DIS home screen.

You need to use the virtual network you have created in order for DIS (running on UNIX in the virtual machine) to communicate with your interface using EDIABAS running on your normal Windows operating system. By disabling your ethernet adapters, DIS knows you have an interface, it just can't talk to it because the interface can't access EDIABAS.

[RobertV1]

Robert,
Why have you disabled your ethernet adapters and why are you running a Diaghead Emulator??? If you have DIS installed on the EasyDIS base, translator set to Fister and processes configured so that vm is set to not run, you do not need a diaghead emulator and similarly, since you are connecting directly to your interface you do not need the coloured signal strength bars on the DIS home screen.

You need to use the virtual network you have created in order for DIS (running on UNIX in the virtual machine) to communicate with your interface using EDIABAS running on your normal Windows operating system. By disabling your ethernet adapters, DIS knows you have an interface, it just can't talk to it because the interface can't access EDIABAS.

David,
I was just attempting different options while I waited for a response. I was only attempting to find a solution when I disabled my wireless and nic cards on the laptop. I tried the diaghead emulator just to try and see if it made a difference.
Glad to hear that I don't need the bars in DIS for the diag head since I have never had them. I am only running IFH-Service with DIS and have the setting to Fister and vm set not to run. I have the ignition on and selected the ADS on my interface. When I load DIS and attempt to a diagnostic I get Warning: There is no connection to a diagnostic head. I click on OK to manual connect and then the IFH-Server then shows 192.168.68.30. I attempt to check an individual module and it fails with an error message of Control unit selected has not been found. The ignition was on and I tested the lamp control module which I know I have.
Any ideas?

[David Mc]

Robert, I am assuming you are running INPA v3.01 (the installer is v4.4.7)/EDIABAS v6.4.3 and have made the necessary changes in Ediabas.ini for Interface=***, RemoteHost =192.168.68.1 and Ports =6801. Make sure that there is not a firewall, antivirus or antispyware program running on your computer as these are notorious for killing diaghead comms. If all this is good, test your interface on someone else's installation.

[RobertV1]

David,
Thank you for the reply. I'm away this weekend and will check the version when I get back. I did make all the changes in the .ini file. I know I'm not running any antivirus nor firewall, but I could still have the antispyware running. THX again for the reply.
CHEERS

[kneescrap]

After mutch reading and failing trying and some thinking... i have finally got DIS innstalled on the VM. I'm running Windows 7 64 bit. But now i'm stuck..
I have the modified VAG KKL cable with soldered pin 7 and 8, no ignition mod yet.
I start the IFHSrv32
I start the diagheademulator
start the VM and once DIS loads i press RUN on the diagheademulator
But when i press connect on the connection setup i got this message

Any solution here ?

the "config" diagnostic head menu


And the "config" system menu





Can someone tell me whats wrong here ?

i feel close.. but i'm sure i'm still far away..

AHH CRAP !!! i can't figure this things out... maybe i just should buy an yellowhead cable to dis

[KB120D]

Hi David!

Ive also installed easyDISv44. I "think" ive done all the necessary stuff. I can ping all 3 interfaces from he Host. Apitest is sucessfull. I havent switched to FISTER / VM OFF because i have no ADS Interface. Normal OBD Interace. This works with SSS & Inpa. I have done the complete DIS Configuration with the EASY DIS CONFIGUR-MATIC without using root acess by hand, so no file is edited via vi.

Now i have the problem that there is no free DiagHead Interface. maybe you have an hint for me

[David Mc]

KB120D, setting the translator to FISTER and configuring processes so that vm is set to not run is required unless you are intending to use a genuine OPPS or Siemens yellow DK Head interface with a diaghead emulator. Once this has been done, you will not even seen the network configuration screen, so don't worry about not seeing a free diaghead interface.

You may be one of the lucky ones for whom the default EasyDIS values work, so I would be connecting to your car and attempting a diagnostic before doing anything else.

[KB120D]

KB120D, setting the translator to FISTER and configuring processes so that vm is set to not run is required unless you are intending to use a genuine OPPS or Siemens yellow DK Head interface with a diaghead emulator. Once this has been done, you will not even seen the network configuration screen, so don't worry about not seeing a free diaghead interface.

You may be one of the lucky ones for whom the default EasyDIS values work, so I would be connecting to your car and attempting a diagnostic before doing anything else.

The only thing where i must use scoadmin was to set bdflushr from 600 to 30. All other network settings can be done by the configuration tool very easy. So why many users go to the shell... Also apitest can be done under the configurator. And network settings can be set easy with mouse :-)

This is much easier in my opinion.

Ok, then i will change the needed things (fister+vm) with easy configurator. Restart the system, check connection with ping. Ifshsrv32.exe must run, then i click directly on diagnose. I hope it works....

[IIIM]

Hellow!

I can`t fix the (picture) problem in GT1 settings. Pleac help Thanx!!

[KB120D]

So, i can report a FULL SUCCESS ;-)

thx@David_MC!!!

[David Mc]

Kneescrap, from where did you obtain the IP address and name for your diaghead?

[kneescrap]

Kneescrap, from where did you obtain the IP address and name for your diaghead?

hmm. That is a good question..

I run this on a windows 7 64 bit machine. I Have a modifyed vag.com cable. in INPA i can see 2 black dots. I'm running the latest FTDI driver for this cable and set it to 2 msec and flashed the chip with inverted R# and DSR# and put it into com 1 with mprog. I installed the ediabas 6.4.3 and INPA 4.4.7 and then installed the Ediabas 6.4.7 and INPA 5.0.2. have installed the registerfile for windows 7. and installed obd setup.
Followed the instructions for installing the VMvare machine for the DIS setup.
changed the ediabas.ini file. ip 192.168.68.1 and port 6801. Checked if ediabas.ini file is correct in DIS and the vi hosts.
removed and installed the new PCI card in the scoadmin functions. When i check the subnet on the edit setings on the VMachine it says 192.168.68.0 and subnet 255.255.255.0. When i push the OK button here it says that the IP adress is in use. so i cant push OK and apply as everyone else does in the scoadmin where i can fill in the ip adress 192.168.68.30 it fills out netmask broadcast adress and TCP and Pseudo ttys. i have changed BDFLUSHR =30. When i run the fister protocol with the vm machine set to NOT run then the free diagnostic head dissapears. there is where i am now.. i can altso run the aptitest. and that is ok..

This is a very short explanation on what i have done.. but you see the basics. maybe a bad explanation but.. so sorry if it dont help. i can't check the interface to the car because i'm offshore at work. i would love to see an good HOW TO install on windows 64 bit. because there is so many how to's on other versions on windows. many screenshots from xp is used on the 64 bit win 7 guide. I have ordered a INPA interface from Ebay because i want real ignition detection i think my soldering on the FDTI chip is a bit bad. so in case i ordered that one to.

and at least sorry the english