Different types of ICOMs and Cables

Different types of ICOMs and Cables

ICOMs


ICOM A
A multi-functional vehicle interface. It was developed for use in workshop and service applications and supports service consultation, diagnosis and vehicle programming/encoding processes. It can be used to process all vehicles of the BMW Group.
 


ICOM B  
Needed for MOST modules (BMW E series from 2001 till 2012).

The ICOM B is the external MOST (Media Oriented Systems Transport) interface of the ICOM A. It is connected to the ICOM A using the supplied cable or a commercially available USB cable of the type A-B. The power supply is fed across the ICOM A via USB.


Electrical operation:

Power supply via USB 2.0 interface: 5 V
Maximum current consumption: 250 mA
Environmental conditions during operation:
Ambient temperature range: 0°C ... +45°C
Relative atmospheric humidity at max. 25°C: 10% ... 80%, non-condensing
Temperature gradient: 5°C/h
Environmental conditions for mount:
Ambient temperature range: -20°C ... +60°C
Relative atmospheric humidity at max. 25°C: 10% ... 80%, non-condensing

Temperature gradient: 5°


  


ICOM C
Needed for BMW older than June 2001.

The ICOM C is an intelligent interface adapter that adapts the physical OBD II to the BMW circular socket. As an extended supplementary module, it connects ICOM A to vehicles without an OBD II interface.



 
​
ICOM D
Needed for BMW Bikes (Motorrad).





CABLES:

K+DCAN cable for BMW E Series

For BMW E Series from 1998 till 2011


 



ENET cable for BMW F series

BMW ENET Interface Cable (OBD2 to Ethernet) is used for coding, programming & diagnostics.

This can be used with Rheingold ISTA/D, E-SYS, INPA, and ISIS.

 

Specifications:

Gold-plated RJ-45 connector; CAT6 Cable; Black OBD Interface connector; 7ft length.

 

Compatible BMW Models:

BMW 1-series: F20, F21, F44, F45, F46

BMW 2-series: F22, F23

BMW 3-series: F30, F31, F34, F80

BMW 4-series: F32, F33, F35, F36, F82, F83

BMW 5-series: F07, F10, F11, F18

BMW 6-series: F06, F12, F13

BMW 7-series: F01, F02, F03, F04

BMW i-series: i3 (I1), i8 (I12)

BMW X-series: F15, F16, F25, F26, F48

BMW ///M-series: F80, F82, F83, F10, F06, F12, F13

ALPINA Models: D3, B3, B4, XD3, D5, B5, B6, B7.




    • Related Articles

    • BMW Group doesn't sell or build any ICOM(s), all other ICOMs like the NEXT version are third party build

      Our certified software set (or Tablet system) is not guaranteed to work with any third party ICOM like A2/ A3 or NEXT, it’s only certified to work with our certified ICOM A. BMW Group doesn't sell or build any ICOM(s), all other ICOMs like the NEXT ...

    • ICOM NEXT with ISTA Software

      Problem:  ISTA/P certified software works with USB K+DCAN interface via the loader emulator but cannot get it to recognize an ICOM NEXT interface (purchased from a BMW dealer). The interface works fine with ISTA+ and INPA (also shows fine in ...

    • PRO ICOM vs ICOM A2/ A3 or NEXT

      Question: Do third party ICOMs work with OBD HAWK Software? Answer: We received many positive feedback from customers who use their own third party ICOMs and it worked for them, but we still cannot guarantee it to work with our certified software.   ...

    • ICOM Stuck in RESERVED State

      If the ICOM is stuck is a RESERVED state, it is usually due to more than one application running at the time.  ICOMs can only receive data from one application at a time, so either ISTA/D or ISTA/P but not ISTA/D and ISTA/P together.  Attempting to ...

    • ICOM Compatibility

      Our software set (or Tablet system) is not guaranteed to work with any third party ICOM like A2/ A3 or NEXT, it’s only certified to work with our PRO ICOM A, BMW Group doesn't sell or build any ICOM(s), all other ICOMs like the NEXT version are third ...