|What's new Home Download Documentation FAQ HowTo Forum Contact Us||Русский|
Ford, Mazda, Lincoln and Mercury are officially supported since version 2.0 .
Absolute majority of models of the manufacturers mentioned above from 1996 model year. Exception are quite rare: models unified with other manufacturers, for example Ford Galaxy Mk2.
Models manufactured before 1996 usually have diagnostic interfaces not supported by ELM327. However, there are exceptions too. For example, Ford Scorpio II (1994 MY).
Although Mazda was a part of the Ford concern for many years, and utilizes the same diagnostic technics, it is another brand and has significant differencies. In general, pre-CAN Mazda have not so rich diagnostic possibilities comparing with Ford models of the same generation.
FORScan is limited with ELM327 abilities. Most significant of the limitations are: unability to support MS CAN (can be partially solved with small modification of ELM327 adapter), unability to address several bus simultaneously, unability to write to flash memory, and some other. Besides, information about proprietary manufacturer protocol is very limited. A lot of features cannot be implemented without this information.
It should be counted that currently this is a freeware, uncommercial project mainly developed at our free time. As a result, there is no any strong/strict/hard shedules or obligations. However anyone who wants to help the project to move ahead faster can join this work. For example, do some translations, provide valuable technical info, participate in testing and so on.
Experience shows that a special version for Linux is not very necessary, because Wine does the job. As for Android, we plan to implement it after FORScan 2.0 beta is released.
All ELM327 adapters are supported, including clones. Situation with so-called "ELM-compatible" is more complex. Our opinion about "compatible" devices is reflected in this article: . At the moment (Feb 2013) the following ELM327-compatible devices are confirmed to be compatible with FORScan:
- OBDLink SX (STN1100 chipset) - confirmed by Naresh Seeparsad on JDM Mazda 323 BJ Familia 2002 MY
FORScan normally works with COM, USB and Bluetooth interfaces.
If you use latest version and your vehicle is Ford, Mazda, Mercury or Lincoln after 1996, then most likely your ELM327 has problems with support of certain protocols. Unfortunately, china clones have quite bad quality, escpecially recent ones. From experience, protocol SAE J1850 PWM is most problematic. However, our users had indcidents with ISO 9141 and CAN bus too.
It should be also counted that ELM327 has 3 almost independent cirucits: one for SAE J1850 PWM/VPW, second one for ISO/KWP and last one for CAN. Your adapter may have problems with e.g. J1850 PWM, but in the meantime it will work OK with rest 2 bus. This is why users who claim that their ELM327 is OK because "it works on some Hyundai, Nissan etc" may be wrong.
As our experience shows, ELM320 is already a quite rare device. It only supports Ford J1850 PWM, but ISO and CAN bus are not accessible using it. Support of it, however, requires some efforts. So the decision was made to stop official support of ELM320. Latest version which has ELM320 v2.0 support is FORScan v0.9.2 beta.
In version 1.3.0, majority of PIDs added for PWM/SCP and ISO PCM. Significant number of PIDs for CAN vehicles is supported. And only small part of PIDs for newest (CAN 14229) vehicles is supported. But we will add more pids for these vehicles in future releases.
On some cars standard OBD2 PIDs are replicated in "native" diagnostic modes along with "native" PIDs. For example, the PID "Short Fuel Trim Bank 1" can be available on 2 PIDs: 0006 (OBD2) and 1158 (Ford). Existing experience shows that OBD2 parameters are less desirable for analysis, just because they have much worser refresh rate and precision. See the graphic below as an illustration:
|Copyright © 2011-2016|