[willisodhiambo]

I am trying to get to grips with all these confusing technologies. If you recall, one car (F10) crashed while I was trying to update it with ISTAP. A good member here brought it back to life, thanks to him again. A forensic examination of my laptop seemed to reveal a malfunctioning OS and related communication drivers. So upgraded to windows 10, reinstalled ISTA+, ISTAP, INPA, NCSExpert, Tools32 and BMW coding tool.

Connected to my car (F10) and ENET, KDCAN would not connect to car. Some fault about car not found. ICOM Connected perfectly.

An hour or two later on another F10 the ENET cable connect flawlessly, I had not touched anything since the last trial on my car!!! An hour later, KDCAN connects flawlessly to and E60. I am stumped. I am yet to find time to retry my car.

My question is,

1. Do ENET, KDCAN and ICOM use Ediabas? If yes do they need OBD.ini?
2. When using the three, how come we don't need to always change ODB.ini (Or ediabas interface) interface between USB,ENET and OBD
3. It seems there are two communication protocols in these cars, CAN and Ethernet. is that why ENET can only use Ethernet and KDCAN can only communicate via USB?

Lastly I have seen some interface tool to change between ENET, DCAN and ICOM. I cant find it though. How useful is it? Who can led me to a copy of it.

What exactly is the purpose of the line in OBD.ini for hardware "Hardware=OBD" and a more or less similar configuration line in Ediaba that reads "Interface= STD:OBD"?

I am as confused as hell