|
|
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read | |
| TireRack Garage | Homepage | Supporting Vendors | Articles | Online Store | Photo Gallery | Forum Rules | Advertising |
| Diagnostic Software Do you need help with diagnostic software or have installation questions? DIS, INPA, EDIABAS, IBUS, CANBUS, CARSOFT |
 |
|
|
Thread Tools |
|
#151
10-09-2009, 11:22 AM
|
||||
|
||||
|
Quote:
Great info Does all this works on windows vista? Which are the better cables to use with this? 
|
|
#152
10-09-2009, 05:21 PM
|
|||
|
|||
|
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  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..  Would be so nice to get this to work!
|
|
#153
10-09-2009, 10:48 PM
|
|||
|
|||
|
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.
__________________
<img src="http://members.roadfly.org/thematrixz/twin.jpg">
540IT, Dinan CAI, DME and Tranny software. M5 rear sway bar, M-Technik Aerodynamic, Phatbox, MBQuart all around. 528IT, bare bone stock. 07 530XiT, need this for bad NE winters. Album: http://forums.bimmerforums.com/forum...hp?albumid=174 E39 540 Secondary airpump forsale: http://forums.bimmerforums.com/forum...0#post17763980
|
|
#154
10-10-2009, 01:57 AM
|
|||
|
|||
|
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
|
|
#155
10-10-2009, 07:28 AM
|
|||
|
|||
|
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 
|
|
#156
10-11-2009, 09:24 AM
|
|||
|
|||
|
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
|
|
#157
10-11-2009, 01:52 PM
|
|||
|
|||
|
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?  )Last edited by Rallyfinnen; 10-11-2009 at 01:57 PM..
|
|
#158
10-11-2009, 02:08 PM
|
|||
|
|||
|
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.
|
|
#159
10-11-2009, 03:05 PM
|
|||
|
|||
|
Hmm, I'm totally lost when it comes to unix commands..
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.
|
|
#160
10-11-2009, 06:24 PM
|
|||
|
|||
|
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!
|
|
#161
10-15-2009, 07:45 AM
|
|||
|
|||
|
can i use the EDIABAS - DIS GT1 to program the DME using the OBD interface?
|
|
#162
10-17-2009, 08:22 AM
|
|||
|
|||
|
Quote:
|
|
#163
10-17-2009, 09:59 AM
|
|||
|
|||
|
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
|
|
#164
10-17-2009, 10:14 AM
|
||||
|
||||
|
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.
__________________
|
|
#166
10-19-2009, 03:33 PM
|
|||
|
|||
|
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?
|
|
#167
10-20-2009, 11:47 AM
|
|||
|
|||
|
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 Quote:
Last edited by j4m35; 10-20-2009 at 11:50 AM..
|
|
#168
10-21-2009, 11:55 AM
|
|||
|
|||
|
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.
|
|
#169
10-22-2009, 04:46 AM
|
|||
|
|||
|
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
|
|
#171
10-22-2009, 02:02 PM
|
|||
|
|||
|
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!
|
|
#173
10-24-2009, 04:00 PM
|
|||
|
|||
|
Quote:
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
|
|
#174
10-25-2009, 12:42 AM
|
|||
|
|||
|
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 Quote:
|
|
#175
10-25-2009, 12:50 PM
|
|||
|
|||
|
Quote:
i get this error after i choose my car model under diagnosis: www.hot.ee/aise/Decision.png when i press cancel i get an auto id success notification: 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) Last edited by aise; 10-25-2009 at 01:25 PM..
|
|
| Bookmarks |
| Thread Tools | |
|
|
|
