interfaces4beemers.com you missed a S ;-)
My M3 is 1 of 2
You can read all about it and see it in action here http://www.repairdynamics.com/Rv8flyboy_Review.pdf
Hello my name is Stefan, I'm from Germany, I have an original of DISPlus BMWgekauft with a broken touch screen (the screen is black but the touch still works). Previously I had always connected a USB mouse, and it worked perfectly. Now I was no longer a power failure and the tester. So I reinstalled it with the BASE cd, cd and CIP programs. But now is not the Mouse. I now have the defective touch panel next to the DIS and take the field to touch her work. How can I bring back the mouse to run?
Ive had this software for 2 years and I just realized there was a thread on it. To this day im having issues with it, so i will be reading this thread step by step to get it up and running.
*I'm unable to post links because I don't post much here, so bare with me.*
Alright, this is a long-ass thread.
I have an '03 E46 M3, so that means I don't have the round diag port.
I assumed I would need the discontinued Siemens diag head in order to do coding on the car, and then I read about Rv8flyboy's unit:
repairdynamics dot com slash Rv8flyboy_Review.pdf
I saw in the last few pages of this thread this site, which appears that it might be where I can purchase one:
interfaces4beemers dot net slash adsobd.html
So it looks like the aluminum box has been replaced by the compact round-plug adapter, and I would have to buy the OBD adapter in addition to it? Can someone confirm that this is all I would need in order to use the GT1 with an E46 without a round port?
I got to the 'Mount' DIS part but it's grayed out. Am I missing something here?
Thanks
I found how to click mount, but it'll only select a file, not the whole folder. Any solutions?
Last edited by TheLadiesMan; 02-17-2013 at 08:06 PM. Reason: Automerged Doublepost
- Sean
RIP Blitzkrieg
Hi,
i have installed easydis and dis.v44 but i still get a packet loss about 50% if i ping 192.168.68.30.
the other two 192.168.68.31 and 192.168.68.32 are working well. Does anyone have an idea why i have a packet loss if ping the 192.168.68.30
The rest of the programm works well too.
Regards
Check that antivirus software and firewalls are disabled.
firewall is disabled and antivirus software is not installed
Make sure that you have the latest MicrosoftNET updates installed as well.
i installed the latest microsoft net update. same as before. i noticed that in dis the bar after the computer lights up randomly
Open DIS without starting the IFHSrv32 and use the Administration tab and "configuring touch screen" option to access the configure-matic main menu. Make sure that Fister is set as translator, then configure processes so that vm is set to off (i.e. not run) and nsw and dsm are set to run. Exit DIS from the configure-matic main menu using option 0 when you are done. Start the IFHSrv32, then re-start DIS and the problem should be fixed.
i did what you told me, but it isn´t working. i deleted in scoadmin menu the the lan adapter with the ip 192.168.68.30 and installed it again. the result is that this adapter is now the last in the list and works well. now the first one is 192.168.68.31. but now this one has the same packet loss as the old one
You only need to set up one LAN adapter on the SCOAdmin Network. Check your installation using this:READ THIS FIRST.pdf
Anyone have any good links to download the software? I can't find anything that still works...
http://forums.bimmerforums.com/forum....php?t=1940213
Since 4 shared is giving people issues, don't mess with the 4shared. If those torrents aren't working you are doing something wrong.
Sent from my SCH-I535 using Tapatalk 2
Last edited by IcemanBHE; 02-23-2013 at 07:28 PM.
My M3 is 1 of 2
Hi Guys, maybe sombody of you can help me. I think DIS is kidding me!!!
I installed INPA and DIS according to the installation guide (READ THIS FIRST...). INPA is working fine (I think so), as I see 2 black circles at the top when I run INPA and ignition is on. Unfortunaltely e90 model is not listed. I didn't care about this as I want to work with DIS. APITest passed successfully but DIS doesn't detect my car!!! I tried to switch the protocols and also vm set on/off. APITest always succeeds but the car won't be detected. Does anybody have any idea what could be wrong??? Sorry for my english, I'm German Cheers!
Last edited by xx325; 03-08-2013 at 01:49 AM.
There is nothing wrong with your installation. It sounds like you are running DIS v44, which was released in December 2005 when the E90 series had only recently been released. You need to install DIS v57, which covers more variants of the E90 (including the 325d, which was not available in DIS v44).
Installation is a breeze, just create another identical virtual machine and install the v57 program file.
Hi David, yes I installed DIS v44. That's funny as I have a 325d
Ok, I will install DIS v57. So the installation of DIS v57 is the same as for DIS v44? I already thought it is an issue with my cable as I'm using KKL -EDIN INTERFACE of "doitauto" and my car is from 06/2007. Everywhere I'm reading that BMWs after 03/2007 only can be connected via D KAN cable... But if it is so, I wouldn't be able to connect to my car with INPA!?!?!
Different models switched to DCAN over a period of about 6 months but E90's built after 03/2007 are definitely DCAN, so you will need a DCAN interface as well. INPA being able to read a battery and ignition signal is not an indication that it can communicate with your car's diagnostic system.
David, ok I agree but how can you explain that I CAN code my car with NSCExpert and the same cable? It's another VM where INPA and NCSExpert is running. I'm pretty sure that my car is from 06/2007 (VIN Decoder). If my car is DCAN I think I weren't able to code with NSCExpert and this cable!?!? Please correct me if I am wrong
BTW: my car is a pre facelift e90 model with original FRM2 (which also indicates that it is a 2007 model)
Last edited by xx325; 03-08-2013 at 04:06 AM. Reason: Automerged Doublepost
There still has to be some functional similarities between the K-CAN and D-CAN bus networks. My K-CAN/D-CAN interface has connections to Pins 1, 4 & 5, 6, 7, 10 & 15 and can be configured to work with both protocols, so I suspect the calls for coding are independent of the diagnostic layer.
Bookmarks