Settings in GT1/DIS to use the INPA Interface ?

[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?

Originally Posted by 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.

[randomy]

I ordered what I beleive is a INPA compatible cable.
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?

[suparmutt]

Originally Posted by 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

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]

Originally Posted by 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.

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]

Originally Posted by 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

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

[cerixen]

Originally Posted by 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?

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/lofiversio...hp/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...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.

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

Originally Posted by 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/lofiversio...hp/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

Originally Posted by 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:

...

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

[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

Originally Posted by 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
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...