AlfaOBD is a software for FCA group cars diagnostics. Fiat/Alfa Romeo/Lancia cars produced in 1994-2017, and Chrysler/Dodge/Ram/Jeep cars of model years 2005-2017 are supported. Although the software is primarily targeted for car owners, it provides many of the features of professional scanners.
AlfaOBD natively supports Electronic control units installed in FCA group cars. Native support differs AlfaOBD from many other diagnostic applications providing OBD II generic support limited with engine and transmission modules.
AlfaOBD is supported on Windows PC and Android devices.
The power of a professional diagnostic tool - in your pocket:
AlfaOBD features include:
- monitoring various dynamic parameters of body, dash, code, engine, gearbox, ABS, climate control, etc. and graphical presentation as adjustable plots
- reading of static data (ECU id, system status, fault codes with probable causes and environment information where applicable)
- clearing fault codes, monitoring the system for appearance of new faults
- active diagnostics and configuration procedures for various equipment controlled by engine, gearbox, body computer, climate control, ABS, airbag, code control and other ECUs. Service light reset, engine oil change, DPF regeneration and many more.
- electronic key and RF remote control programming
For the full list of supported ECUs see Supported Units. See Supported Cars for the full list of supported cars.
Note: Starting from MY2018 FCA bults in the Security Gateway Module (SGW) which blocks access to diagnostics for the third-party software. There is no software solution yet, as a workaround please use a hardware bypass module (as an example).
Owners of Fiat 500X/Jeep Renegade/Compass (MP) : make sure that the bypass supports the second high-speed CAN bus, the one that connected to the pins 12 and 13 of the car OBD port. The bypass from Zautomotive does not currently support this bus!
Here is how to modify Zautomotive device (thanks to Fulvio from Italy for the solution and the permission to publish it) :
Open the Zautomotive device and solder two wires: connect pins A1 and A2, and connect pins A8 and A9 (see the picture). Modification is the same for the first and the second models of the device.
The software requires a compatible OBD interface. At present the following types of interfaces are supported:
OBDLink MX, LX and SX. OBDLink MX is the recommended interface for the cars with high-speed CAN bus on pins 6 and 14 and the middle-speed CAN bus on the pins 3 and 11 of the OBD plug. These are most of the Chrysler/Dodge/Ram/Jeep cars, PowerNet and CUSW-based, Fiat Tipo/Egea. No additional adapters are needed for these cars when using OBDLink MX. Note: Fiat 500X/Jeep Renegade and Compass (MP) require the "grey" adapter for the access to the second high-speed CAN bus.
LX and SX interfaces additionally require "blue" adapter for access to the middle-speed CAN bus.
OBDLink also recommended for the Fiat/Alfa Romeo/Lancia CAN-based cars. The "yellow" adapter might be needed for access to the low-speed CAN bus.
OBDKey Bluetooth/USB/WLAN. This is a universal interface supporting all the control units. Especially recommended for the non-CAN based cars.
ELM327 - based USB / Bluetooth / WLAN interfaces for PC and bluetooth/WiFi-enabled Android and Windows devices. All CAN units are supported and some of K-Line. Make sure the ELM 327 is of version 1.3 and above.
Warning: There are many suppliers of these interfaces, but not all of sold interfaces are compatible with AlfaOBD!
An ebay interface based on an ELM327 clone might work fine if you are lucky. But there are lots of defective interfaces sold which can not establish connection to car ECUs under AlfaOBD. If, when connecting to a car ECU AlfaOBD displays a message "Interface reports NO DATA" or "Interface reports CAN ERROR", this is most probably a sign that you have one of these defective interfaces. Such an interface might work fine with other diagnostic software using OBDII/EOBD protocol, but it can have issues with AlfaOBD because of a different diagnostic protocol used.
It is recommended to use an ELM327 interface tested with AlfaOBD.
For example, the interfaces sold by Electronic-Fuchs.de and Obdauto.fr have been tested for compatibility with AlfaOBD.
Kiwi 3 Bluetooth LE
(Android only). All CAN units are supported and some of K-Line. The interface features very low power consumption.
KLLine serial or USB, PC version only due to limitations of Android OS. No CAN support so it is recommended for the non-CAN based cars. For example, interfaces supplied by Electronic-Fuchs.de, Obdauto.fr , and ECUFix.com are supported.
Note: USB interfaces are supported on the Android devices via On-The-Go, check if your Android device supports On-The-Go and get a corresponding adapter.
Note: Some WLAN interfaces have built-in support for Android (like OBDLink MX WiFi), for the others the WLAN connection is only available on Android devices with ad-hoc Wi-Fi support. Before purchasing a WLAN interface for use with the Android version of AlfaOBD please check if it is possible to configure your particular Android device for ad-hoc Wi-Fi. Typically it means that the device is rooted and the Wi-Fi driver is replaced with an "adjusted" one.
It is recommended to purchase an adapter or set of adapters to be able to communicate to the Control units other than those connected to the pin 7 (K-line) and 6 and 14 (CAN line) of the car OBD plug.
The adapters are available at Electronic-Fuchs.de , Obdauto.fr , or Gendan.co.uk
For the detailed description of AlfaOBD for Windows features, installation and use see help which is also included into the download packages.
Help for the Android version is here (English) or here (German).
For more information and support contact firstname.lastname@example.org