N
Since someone in https://autogmt.com/threads/bmw-ista-d-4-39-20-standalone-activated.1493/ asked about use of a K+DCAN cable with ISTA let me first give you some background and then let me show how to configure ISTA.
Background:
The OBD2 K+DCAN interface is used in the older BMW Series (E model numbers). Roughly speaking it is based on an serial communication interface. The adapter cables typically have an OBD2 plug on one side and an USB plug on the other. The USB appears on a PC as a serial port or COM port. This is how it was done in the old days (even officially within BMW when the old INPA system was used for programming and diagnosis). Essentially through the era of the BMW E-models, the architecture was: CAR <-> K+DCAN <-> PC where the PC side consisted of a software named EDIABAS and the INPA software, thus the whole architecture was: CAR <-> K+DCAN-cable <->EDIABAS-software <-> INPA.
With the more modern ISTA/Rheingold system, the alternate (and more modern and expensive) way is an ICOM interface. The ICOM interface is basically a small computer which communicates in two directions (with the car and with the diagnosis PC). On the car-side it communicates using the serial CANBUS protocol. Toward the the PC it appears as a network device (WLAN or Ethernet). Essentially the ICOM replaces the "K+DCAN <-> EDIABAS" combination, so that the architecture is: CAR <-> ICOM <-> ISTA.
Side note: Even newer car models are now able to act like a network device themselves (the protocol called ENET), so for these the ICOM is no longer necessary and a simple OBD2/ENET cable replaces the complex ICOM interface. So there the architecture is: CAR <-> ENET-Cable <-> ISTA.
Now, since it is possible for ISTA also diagnose the older E-models, there are two options to do this:
1) Use of an ICOM interface: In that case the ICOM appears on the network (WLAN or Ethernet) and hides the fact that on the car side it uses the old protocol.
2) Use of the old EDIABAS system: ISTA can pose as a client to the EDIABAS-software (like INPA or NCSEXPERT do) and let EDIABAS do the communication with the car, like it was in the old days.
Alternative 1 is more reliable, but ICOM interfaces are rather expensive (price for original BMW ICOMs is in the thousands, while Chinese knock offs start around $200). Alternative 2 is inexpensive $20 to $80) but less reliable (especially for updating/programming control devices), but good enough for diagnosis, resetting error codes etc.
Configuration:
Hardware and COM-Port:
Assuming you don't yet have a K+DCAN cable, when you shop for them, look for two things:
1) have them based on the FTDI chip (this USB/serial chip works very well with Windows without the need for extra drivers)
2) make sure they have a switch to accommodate for differences between very old models (like E46) and newer E-models (like E87)
When you plug it into computer, the cable it will get assigned a COM port. Here is how to find out which:
1) Right-click Windows menu
2) Choose Device Manager
3) Look for Ports (COM & LPT)
4) If you see multiple ports, plug your cable out and back in to see which one disappears/appears
Configure OBD:
1) Use the Windows explorer to go to the C:\EDIABAS\bin folder or to C:\EC-APPS\EDIABAS\bin (with typical modern installations, both are actually the same folder).
2) Find the OBD.ini file, right click it and choose Open With > Notepad (or another editor of your choice)
3) Find where it says can use below it make sure the Port setting matches the COM port of your K+DCAN cable.
Configure EDIABAS:
1) Again, use the Windows explorer to go to the C:\EDIABAS\bin folder or to C:\EC-APPS\EDIABAS\bin (with typical modern installations, both are actually the same folder).
2) Find the EDIABAS.ini file, right click it and choose Open With > Notepad (or another editor of your choice)
3) Near the top you need an entry that says "Interface=STD:OBD" (without a leading semicolon) where other such entries are either absent or need to have a semicolon in front.
4) Alternative: You can use a program named Konfigurator.exe to switch to STD:OBD. Afterwards when you look at the EDIABAS.ini file it should also look similar to this:
Recap:
Now:
- you plugged in your cable
- told the OBD.ini file which COM port it is on
- told EDIABAS.ini to use OBD for communication
Test with INPA (Optional):
Optional step: If you have the old school tools installed, you can now start INPA (not ISTA) and see if it recognizes ignition and battery. For that the two circles at the upper right should turn from black circles filled with white into filled black discs. If this does not work, try to set the switch on the K+DCAN cable to the other position.
Configure ISTA:
The final step is to tell ISTA to use EDIABAS for communication (rather than an ICOM interface or the even more modern ENET).
- start ISTA
- click the wrench icon (upper right)
- choose Vehicle Interface
- select Ediabas settings (ediabas.ini)
- click OK.
Test and Start a Diagnosis:
- click "Operations" (or "Vorgänge")
- click "Read Out Vehicle Data" (or "Fahrzeugdaten auslesen")
- in the lower right corner click "Identification without test"
With that, after a minute or so you should see the VIN and some vehicle data.
Now you can use "Complete Identification".
Background:
The OBD2 K+DCAN interface is used in the older BMW Series (E model numbers). Roughly speaking it is based on an serial communication interface. The adapter cables typically have an OBD2 plug on one side and an USB plug on the other. The USB appears on a PC as a serial port or COM port. This is how it was done in the old days (even officially within BMW when the old INPA system was used for programming and diagnosis). Essentially through the era of the BMW E-models, the architecture was: CAR <-> K+DCAN <-> PC where the PC side consisted of a software named EDIABAS and the INPA software, thus the whole architecture was: CAR <-> K+DCAN-cable <->EDIABAS-software <-> INPA.
With the more modern ISTA/Rheingold system, the alternate (and more modern and expensive) way is an ICOM interface. The ICOM interface is basically a small computer which communicates in two directions (with the car and with the diagnosis PC). On the car-side it communicates using the serial CANBUS protocol. Toward the the PC it appears as a network device (WLAN or Ethernet). Essentially the ICOM replaces the "K+DCAN <-> EDIABAS" combination, so that the architecture is: CAR <-> ICOM <-> ISTA.
Side note: Even newer car models are now able to act like a network device themselves (the protocol called ENET), so for these the ICOM is no longer necessary and a simple OBD2/ENET cable replaces the complex ICOM interface. So there the architecture is: CAR <-> ENET-Cable <-> ISTA.
Now, since it is possible for ISTA also diagnose the older E-models, there are two options to do this:
1) Use of an ICOM interface: In that case the ICOM appears on the network (WLAN or Ethernet) and hides the fact that on the car side it uses the old protocol.
2) Use of the old EDIABAS system: ISTA can pose as a client to the EDIABAS-software (like INPA or NCSEXPERT do) and let EDIABAS do the communication with the car, like it was in the old days.
Alternative 1 is more reliable, but ICOM interfaces are rather expensive (price for original BMW ICOMs is in the thousands, while Chinese knock offs start around $200). Alternative 2 is inexpensive $20 to $80) but less reliable (especially for updating/programming control devices), but good enough for diagnosis, resetting error codes etc.
Configuration:
Hardware and COM-Port:
Assuming you don't yet have a K+DCAN cable, when you shop for them, look for two things:
1) have them based on the FTDI chip (this USB/serial chip works very well with Windows without the need for extra drivers)
2) make sure they have a switch to accommodate for differences between very old models (like E46) and newer E-models (like E87)
When you plug it into computer, the cable it will get assigned a COM port. Here is how to find out which:
1) Right-click Windows menu
2) Choose Device Manager
3) Look for Ports (COM & LPT)
4) If you see multiple ports, plug your cable out and back in to see which one disappears/appears
Configure OBD:
1) Use the Windows explorer to go to the C:\EDIABAS\bin folder or to C:\EC-APPS\EDIABAS\bin (with typical modern installations, both are actually the same folder).
2) Find the OBD.ini file, right click it and choose Open With > Notepad (or another editor of your choice)
3) Find where it says can use below it make sure the Port setting matches the COM port of your K+DCAN cable.
Configure EDIABAS:
1) Again, use the Windows explorer to go to the C:\EDIABAS\bin folder or to C:\EC-APPS\EDIABAS\bin (with typical modern installations, both are actually the same folder).
2) Find the EDIABAS.ini file, right click it and choose Open With > Notepad (or another editor of your choice)
3) Near the top you need an entry that says "Interface=STD:OBD" (without a leading semicolon) where other such entries are either absent or need to have a semicolon in front.
4) Alternative: You can use a program named Konfigurator.exe to switch to STD:OBD. Afterwards when you look at the EDIABAS.ini file it should also look similar to this:
Recap:
Now:
- you plugged in your cable
- told the OBD.ini file which COM port it is on
- told EDIABAS.ini to use OBD for communication
Test with INPA (Optional):
Optional step: If you have the old school tools installed, you can now start INPA (not ISTA) and see if it recognizes ignition and battery. For that the two circles at the upper right should turn from black circles filled with white into filled black discs. If this does not work, try to set the switch on the K+DCAN cable to the other position.
Configure ISTA:
The final step is to tell ISTA to use EDIABAS for communication (rather than an ICOM interface or the even more modern ENET).
- start ISTA
- click the wrench icon (upper right)
- choose Vehicle Interface
- select Ediabas settings (ediabas.ini)
- click OK.
Test and Start a Diagnosis:
- click "Operations" (or "Vorgänge")
- click "Read Out Vehicle Data" (or "Fahrzeugdaten auslesen")
- in the lower right corner click "Identification without test"
With that, after a minute or so you should see the VIN and some vehicle data.
Now you can use "Complete Identification".
Download attachments
-
Capture2.PNG -
Capture1.PNG