seriously???
your the man!!!
ive subscribed to this thread with huge amounts of anticipation
im in the same position as you
been using INPA for a long time now with (Chinese) round OBD
i also have carsoft cables too (Chinese also)
im hoping this will work
will give it a go tomorrow
Excellent thread, thanks for the info. Now I'm going to dig my Carsoft cables out from the box of junk and give it a try.
Edit: Got Inpa working with my Carsoft box. Still trying to get DIS to work, it seems to hang up when I go into Diagnosis (hour glass icon on screen). I'm able to get the API test working but can't go any further. I'm reinstalling DIS now, hope that helps.
A few hicups:
1. When I installed DIS base, it kept stopping at creating partition, I searched and found that I have to modify the drive parameters to match what DIS wants to see, unfortunately, I can't find that link again to post.
Solution: I created a new virtual machine with exactly 18.635GB, and this got rid of the problem mentioned. I didn't need to modify drive parameters to install DIS base.
2. Networking problem with VMware: I wasn't able to run the API test (time out error) until I reinstalled VMware and have it recreate the virtual network controllers.
Note: I only added 1 network controller under SCOadmin (that's all it found), not 3 according to some DIS installation documents I found, but other people said they didn't need 3 either.
Got Inpa and Dis working now, Coding works also but not all modules.
Last edited by TheMatrixz; 10-11-2009 at 06:24 PM.
<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
Edit.
Works now.
Last edited by Hdhntr23; 10-08-2009 at 04:10 PM.
I've followed the instructions in the first post of this thread to the letter but the INPA/EDIABAS software refuses to communicate with the Carsoft interface (or even acknowledge it's existence). The Carsoft interface is working fine with Carsoft version 6.5 and is connected via a serial interface to my laptop.
I CAN get INPA/EDIABAS software working with my VAG lead so the software I have is OK but I can only connect to a small subset of the modules on my car (E36/7) using that interface and I think it's because I need to be using an ADS interface and not OBD.
So what step am I missing in getting my Carsoft interface to work with INPA/EDIABAS?
<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
Actually I have one thought.... do I need to set specific serial port settings for speed/handshaking etc for use with INPA rather than Carsoft?
Com1, baud 9600
no error correcting
well the posts are really of great use...i am impressed and also glad....to be a member and such types of posts are very useful....
Susha BMW Performance Chip
Last edited by susha1; 11-04-2009 at 03:18 PM.
OK, got it working by uninstalling INPA/EDIABAS and then performing a re-install. It's talking to some modules but not all and does not detect the ignition status but at least it's a step in the right direction.
Now to set up GT1/DIS,
Thanks for the help so far guys...
First post but been lurking
Great post.
I'm going through this and have the carsoft 6.5 working with the 5led dongle (v6.2 ver2,rs232), this works.
Installed the INPA (v9.0.7), with both UK and USA group (as per link), and this all installs perfectly, I've edited the EDIABA.ini file with remotehost and port and run the ODBSetup.exe, all OK so far.
Edited the path and saved, then run and now get an error,
APInit:error #135
"host communication error"
API initialization error
No API calls possible.
So, I've also installed vmware 6.5.3 and DISv52 and this works and loads I can get it all working (not to the car).
I don't have a touch screen laptop so when I do the touch screen setup, it stays in this screen (as I cant "touch" the screen), I've Also tried to select the "system" button (to setup IP address etc) and this does not work.
Anyone have any ideas? I feel I'm nearly there.
trying on a ODBII e46
Last edited by ccfj1; 11-09-2009 at 02:45 PM.
If you press the 'Windows' button on your keyboard at the touch screen calibration stage it will close and then you're good to go. As for the 'system' button not working this is usually the case if you have not yet activated the DIS program disc which should be in your CD drive. Once this has been 'activated' - and this takes a VERY long time, the system button should then work and you can continue to setting up the virtual head.
Last edited by zigzagsky; 11-09-2009 at 03:05 PM.
Right, done, cheers.
Hmm, no, I don't have the cd image (only BMW GT1 Base V39.nrg) if thats any goodAs for the 'system' button not working this is usually the case if you have not yet activated the DIS program disc which should be in your CD drive.
I don't think I have this either, what should I be looking for?Once this has been 'activated' - and this takes a VERY long time, the system button should then work and you can continue to setting up the virtual head.
I have this BMW MEGA - V39 - DIS GT1 SSS CIP TIS.rar as well as the dis.52
Thanks for your help, much appreciated.
Right, done, cheers.
Hmm, no, I don't have the cd image (only BMW GT1 Base V39.nrg) if thats any goodAs for the 'system' button not working this is usually the case if you have not yet activated the DIS program disc which should be in your CD drive.
I don't think I have this either, what should I be looking for?Once this has been 'activated' - and this takes a VERY long time, the system button should then work and you can continue to setting up the virtual head.
I have this BMW MEGA - V39 - DIS GT1 SSS CIP TIS.rar as well as the dis.52
Thanks for your help, much appreciated.
Update:
downloaded and installed BMW diagnostic head v1.2 and running 192.168.68.1
activating cd now, and yes it is taking some time
Update:
Ok, activated cd with v39 and this now powers on and the DIS is up and running, I've not tried it with the car yet.
Diaghead v1.2 running and ifh_service is running
Does the diag head need to be configured in the DIS head config part?
Last edited by ccfj1; 11-10-2009 at 12:37 PM. Reason: Automerged Doublepost
Ok, I'm still having problems.
I have an e46 (so 20pin ODB II, inside the car).
Carsoft 6.5 = installed and fully working (with the 5 LED black module).
INPA 6.4.3 = Installed
EDIABAS 4.4.7 = installed
ODBSetup.exe = Ran and setup.
EDIABAS.INI file configured (remote host 192.168.68.1, 255.255.255.0 etc).
Running in background ifhsrv32.exe
Running the IPNA, fails to work, I get a communications error.
So installed Vmware v6.5.3 and DIS/GT1 V44 with TIS all installed and booting.
Installed BMW Diag head emulator.
Setup as per directions.
The emulator is "seen" by the Gt1 and sometimes reports as connected, but comms to the ODB still does not work.
I've now ordered the INPA interface (both round and oblong), so will try when the turn up.
I also can't seem to get the API setup screen, so I cant test this part.
Anyone have any ideas?
TIA
Last edited by ccfj1; 11-14-2009 at 07:22 AM.
Can you ping the virtual machine IP address form Windows?
what about pinging IP 192.168.68.30 ?
Dude, I love you. I just tested INPA and works 100% with the carsoft cable. No idea this was possible.
Good to hear!
Any help? I have everything working. I just re-coded my instrument cluster no problems and the stupid error that kept on popping up is gone.
HOWEVER I can not do any diagnosis functions in GT1. I am using the same v44 bmwecu.org version you are. When I select the car E39 the screen looks nothing like yours. When I click a module it freezes up for a bit and I am not familiar with the software but it is like the module is not in the car at this point to the software. From INPA I can diagnose the same modules and I can do coding in GT1!!??
192.168.68.1 is the Windows real PC. 192.168.68.30 is the default IP address of the GT1.
I don't know why but I had to go to SCOADMIN and remove the network adapter and add it again. At first it shows up PCI # 17 and after I do that it shows up PCI #2 and at that point it works.
If you have the bmwecu v44 go to SCOADMIN from Calibrate touch screen -> configure sco network.
I had no need to login as root -- after I did login as root it screwed everything up and I would get a black screen instead of main GT1 screen when booting... reinstalled and did not go in as root and all is ok.
Also I noticed in EDIABAS.ini put the IP 192.168.68.20 (if being consistant with the rest of the guide) or 192.168.68.30 (default IP of the GT1 in my case). In any case the IP address is of the GT1, not of Windows. You will notice in IFH-Service tray icon it is first "IFH Service" After the GT1 has connected the serial port is open and the tray icon caption now reads e.g "IFH Service 192.168.68.30"
With or without diaghead emulator does not seem to matter but in GT1 interface flows better when the emulator is used (no messages about it)
Last edited by joako; 01-12-2010 at 07:22 PM. Reason: Automerged Doublepost
Well this is how far I got before the car battery died. It took at least 20 minutes.
I was thinking to try another cable. I read about using a modified cable but the one I have is original -- RossTech "HEX+CAN" USB cable.
Resolved. I can now use the otherwise worthless China CarSoft 6.5 cable with EasyDIS after taking the following steps
1) Change emulation, or whatever it is called:
In EasyDIS go to Administration -> Calibrate touchscreen.
I forgot the EXACT option but it is in that menu and it is change the emulation from Softring to Fister.
2) For COM1: port settings go to device manager -> Properties -> Comp port COM1 -> 2nd tab -> Click advanced button buffers by default are maxed out, set input buffer to 8 and also output buffer to 8 (this is documented process for WinXP in INPA .pdf doc)
3) Create %windir%\obd.ini and also edit c:\edibias\bin\obd.ini and set UBATT=OFF this cause battery always to show ON in INPA. Ignition always shows off. I think only the c:\edibias\bin\obd.ini is used and the one in %windir% is ignored, but I have both and an extra does not hurt.
Not sure if all the processes are 100% needed but I follow all these trying to get it to work and it does. Probably only the setting in DISplus is needed since I had all in INPA already working. Now the above posted screen sees the modules in the car and I can do Car and Key Memory. Still can not auto identify car because ignition always shows off but I have a 20pin adpater on its way and I am going to try to modify an, oddly enough, genuine VAG-COM cable: HEX+CAN USB.
Last edited by joako; 01-17-2010 at 03:56 PM.
Bookmarks