Ediabas will allow you to use both. Choose that one.

As for what they each mean? I can't say with any certainty but here is my basic understanding

• Ediabas is a ".ini" file which has some basic code in it which you can manually change to use multiple different cables. Luckily you don't need to worry about manually changing anything as ISTA will do all that for you.
• OMITEC. No clue
• The rest are ICOM/ENET specific with varying levels of network connectivity. Basically Local, ISIS (BMW's network), and Direct.

This information may be correct, or it may be completely misguided. Either way, EDIABAS is what you want.

 

Thanks man will give it a shot.

 

E series need the K+DCAN (USB:OBD), F and G need ENET.

If you set up ISTA+ to use EDIABAS like mentioned, you might want to use the EDIABAS Konfigurator tool to change the .ini settings between ENET and OBD as needed. It's much easier than editing manually.

All BMW software is written to communicate over networking protocols (TCP/IP) as the dealer uses interfaces called ICOM which are attached to a network. EDIABAS lets you connect the software to a local interface like OBD or ENET by acting as a middleman for ISTA, INPA, ESYS, TOOL32, etc.

 

If you set up ISTA+ to use EDIABAS like mentioned, you might want to use the EDIABAS Konfigurator tool to change the .ini settings between ENET and OBD as needed. It's much easier than editing manually.

Doesn't ISTA do that for you when you switch the connection type within the program settings?
I don't recall having to play with Konfigurator when I owned both an E and F chassis. This was a long time ago, however, so my memory could be foggy.

Side note on Konfigurator. I never really liked the interface and use Easyconnect exclusively to swap between OBD and ICOM. Haven't tried it for ENET though.
But again, ISTA takes care of this and you only need to swap EDIABAS settings for INPA etc.

 

ISTA doesn't have OBD as a connection type, and in my experience some versions of ISTA (including, last I tested, 4.27 and 4.39) still use EDIABAS to connect to the car over ENET. So, if you have EDIABAS' .ini set to OBD and ISTA set to ENET under Connections, you will get an error message like "PAD inactive"

I haven't tried Easyconnect, as I thought it was mostly used for ICOM. Does it reconfigure EDIABAS settings?

I'm using Konfigurator v2 which is much improved over the first one, which I haven't had a reason to use much.

 

Thanks guys, got the F10 hooked up and talking via ENET, still don't know how to do much in it yet (hopefully I won't need to). Should get a chance to try the E60 this weekend or early next week.

 

Finally got a chance to look into this a bit more. @Aeko is correct. You must reconfigure your EDIABAS file to swap between OBD and ENET even when using ISTA. What I have been doing is switching ISTA over to ICOM when using it for an ICOM cable. In which case it will ignore the EDIABAS file altogether.

The two highlighted options are what I use. I have not tried to use the ICOM/ENET option for and ENET cable since I no longer own an F chassis. But it should work?

I have also been using Easyconnect to modify EDIABAS to use the OBD or ICOM when using NCSExpert or WinKFP. Easyconnect does have an ENET option so this should work just the same as Konfigurator for that as well.

I apologize for any confusion.

 

I will check again later, but I believe those options were all greyed out when I used it last time.