There are several types of interface. The most common use a chip made by ELM Electronics. The ELM327 is the most widely used and practical, supports all OBD protocols, i.e. KWP, PWM, VPN and CAN. The other circuits only support one protocol: The ELM320 only supports PWM; the ELM322 supports VPN and the ELM323 KWP.
Which communication for my interface?
To our knowlegde, there are 4 types of ELM327 interface:
|PC Windows software||Mac OS X software||Android App.||iOS App.
(iPhone / iPad)
Despite appearances, these 4 interfaces are practically identical, at least electronically. Only their external aspect and the connection type differ. At their heart is an ELM327 circuit. Those 4 interfaces will send back the same result during your car diagnostic.
Another thing which may be confusing is the "firmware" version. that may vary. The official versions currently in circulation are 1.3a and 1.4b. Only very advanced users can tell the difference between a 1.3 and a 1.4 as the basic diagnostic functions are identical. On the net, you will also find version 1.5. We have bought one and can confirm that it doesn't exist! It is only a copy of version 1.2 masquerading as 1.2. Check out our tips and advice section for how to know which ELM version you have.
New : Elm Electronics have just released version 2.1 of their ELM327 circuit.
Following requests from users asking where they can buy an OBD2 interface compatible with the ELM327 interface, we decided to develop our own OBD2 car diagnostic scanner : klavkarr. If you decide to purchase from our boutique, you will have of the following advantages:
|klavkarr 100||klavkarr 110
||klavkarr 200||klavkarr 210|
Most sellers come from these countries: China, Hong Kong, USA. Before buying, we recommend you check the following:
Tip : On some interfaces, there are no labels on the indicators. In this case, when you power on, the red LED lights first followed briefly by: 1. Tx OBD, 2. Rx OBD, 3. Tx PC, 4. Rx PC.
The electronic unit contains 3 main sub-assemblies to operate the interface:
The diagram below shows the main function of an interface.
After this brief presentation, the term "interface" should mean more. The role of the ELM327 is to act as an interface between 2 different environments: the car, governed by standards with a high level of reliability and a low price, and the IT world more focussed on modularity.
The interfaces do not always have the same level of quality. As we mentioned above, the software version displayed is not always reliable. Some versions of the circuit are on sale that are not even listed by the manufacturer (reminder: ELM Electronics). User returns have taught us that some versions, that do not officially exist, are in circulation. To clarify the situation:
We do not need to go into the details as to why these non-official versions exist. What is important as a user is to be able to qualify your interface. I.e. be able to verify its capacity. To do so, we recommend you do the following:
|version 1.2 et +||ATKW0||OK|
|version 1.3 et +||ATS0||OK|
|version 1.3a et +||ATFE||OK|
|version 1.4 et +||ATSS||OK|
|version 1.4b et +||ATCSM1||OK|
|version 2.0||ATAMT 40||OK|
This little test will enable you to determine what level of function is installed in your interface. Even if this is only a simplified version of our complete procedure, it is effective and fast. Our software is 100% operational with interfaces from version 1.2, even though it uses some commands from version 1.3, there is no impact on function.
If your ELM interface breaks down or if you want to create your own circuit, the diagram below will help you. It shows the circuit of anELM327 RS232 interface. The basic circuit is always the same whatever the connection mode (RS232, USB or Bluetooth). The difference lies mainly in the components connected to pins 17 and 18 of U1 (ELM327 integrated circuit).
For USB interfaces, a VCP (Virtual COM Port) component is used to "convert" an RS link into USB like USB adaptor cables <-> RS232. There are currently two families of components in the ELM327. The manufacturer FTDI with the component FT232 (more details on the FTDI site) and Silicon Labs with the component CP210x (more details on the Silicon Labs website).
Bluetooth interfaces use an RS modem.<->Bluetooth.
WiFi interfaces use an RS modem.<->WiFi allows wireless communication.
In the event of malfunction:
ELM Electronics has created a very good and practical application note with the voltage levels and a test procedure. This document can be found at the following address: http://www.elmelectronics.com/AppNotes/AppNote02.pdf.
Only ELM interfaces are supported by our software, but other companies have developed interfaces with functions similar to the ELM circuit.
For example: http://www.ozenelektronik.com and their interfaces myOBDics.
On the market, there are also professional products, such as those used by manufacturers such as Clip, Lexia, etc. They remain expensive however. In addition, their special nature makes them usable only by maker family, unlike the ELM.