Force OBDII and Performance

From Force OBDII and Performance
Jump to: navigation, search

Contents

Introduction

Force OBD2 and Performance is a vehicle diagnostic and performance app for Android.

Nexus 5 force intro.png

OBDII Diagnostic

Force can be used as a diagnostic tool for your vehicle. Paired with a Bluetooth ELM OBDII module, Force provides the functionality of an OBDII code reader and much more. When your vehicle's check engine light appears, you can check for diagnostic trouble codes (DTC's) and then clear the codes to turn off the check engine light. Force contains a database of over 2,000 diagnostic trouble code definitions, allowing for descriptions of the DTC beyond the Pxxx you would normally see on a OBDII code reader. Force also supports over 200 PID's (Parameter ID's), most of which can be be logged to an external .CSV file. For instance, you can log your vehicles mass-airflow sensor and ignition timing to a .CSV file which can then be opened by any spreadsheet application for further review. Force can help keep your vehicle running, diagnose your vehicle when it stops running and save you from having to pay your mechanic every time your check engine light comes on.

Performance

Force doesn't just provide a diagnostic OBDII interface, it will also measure your vehicle's performance. Force can measure the torque, power and acceleration of your vehicle all without the need for an OBDII compliant vehicle. Instead of using the vehicle's OBDII to provide data for performance measurements, Force relies on the GPS and acceleration sensors in your phone or tablet. This means if you have an older vehicle without OBDII, you can still use Froce to measure performance. Force's dynamometer (dyno) measures torque and power based on the same principals as a chassis dynamometer providing highly accurate measurements. These measurements can be far more accurate than what you would typically get from logging the OBDII parameters and allows Force to work with older vehicles that are not equipped with OBDII systems.

Force also provides a drag race feature that measures your cars acceleration in terms of distance and velocity. You can measure acceleration based on distance like 1/8th mile, 1/4 mile, etc... and you can measure acceleration based on velocity like 0-60mph, etc... The performance data is logged to an external .CSV file which can be opened by any spreadsheet application for further review. Force even polls the local weather for ambient air temperature and air pressure so you can easily account for differences in vehicle performance based on the weather.

Home Screen

The Home Screen allows the user to navigate to the different features of Force and provides the user with key information about the selected vehicle, the device's sensor status and the local weather conditions.

Nexus 5 force home.png

Home Navigation Options

  • OBD2
  • Vehicle
  • Dynamometer
  • Acceleration
  • Logger
  • Settings

Key Information Provided

  • Vehicle Icon
  • Vehicle Name
  • GPS Sensor Status
  • Acceleration Sensor
  • OBDII Connection Status
  • General Weather Conditions
  • Ambient Air Temperature
  • Ambient Air Pressure

OBD Screen

The OBD Screen provides the interface that allows the user to connect the Force app to a vehicle's OBDII system via a Bluetooth OBDII module/adapter. Once connected, the Force app can check and clear a vehicle's check engine light, log engine sensor data to an external .CSV file, provide a list of what OBDII PID (parameter identifications) are supported by the vehicle and display key engine data gauges.

Nexus 5 force obd.png

OBD Screen Navigation

  • Connect OBDII*
  • Diagnostic
  • Gauges
  • OBD Settings

Key Information Provided

  • OBDII Connection Status
  • OBDII Interpreter (the identification the OBDII module/adapter is reporting... could be false identification depending on if it is a cloned interpreter)
  • OBDII protocol being used to communicate with the vehicle's OBDII system

Connect OBDII

To connect your phone or tablet to your vehicle's OBDII system via a Bluetooth ELM OBDII module/adapter, you must first bind your device to the OBDII module.

Bind an Android device to a Bluetooth device

The method of binding your phone or tablet to a Bluetooth device may vary depending on the device, however, in general you can follow these steps:

  1. Open the Settings app on your Android device
  2. Select Bluetooth from the Settings menu
  3. If the Bluetooth isn't already 'On', turn it 'On'
  4. Plug your Bluetooth ELM OBDII module/adapter into your vehicle's OBDII port
  5. Turn your vehicle's ignition to the 'On' position
  6. Confirm your Bluetooth module/adapter is being powered by the vehicle
  7. Make your Bluetooth module/adapter 'discoverable' (usually by pressing a button somewhere on the device)
  8. On the Android device, Scan or Refresh the list of available Bluetooth devices, the OBDII module/adapter should appear
  9. Select the OBDII module/adapter and select 'Pair Device'
  10. Follow the pairing instructions on your Android device
  11. If you are prompted for a passkey, the most common passkey's are '0000' or '1234'

Connect Force to a Bluetooth OBDII module

Once the OBDII module/adapter has been paired with your Android device, Force can connect to your vehicle's OBDII system with the following steps:

  1. Plug the Bluetooth OBDII module into your vehicle's OBDII port
  2. Turn your vehicle's ignition to the 'On' position or start the engine
  3. Confirm your Bluetooth module/adapter is being powered by the vehicle
  4. Open the Force app and navigate to the Force OBD Screen
  5. Press the 'Connect' button to connect Force to the OBDII module
  6. If multiple Bluetooth devices are available, Force will ask which device to use (select the OBDII module)
  7. Force should then connect to your vehicle's OBDII system
  8. When connected, the 'Connect' button will turn the color blue and say 'Disconnect'
  9. To disconnect from the OBDII, press the 'Disconnect' button.

Trouble Shooting Connection Problems

Force can fail to connect to the vehicle's OBDII system for two reasons:

  1. The Android device failed to connect to the Bluetooth ELM OBDII module/adapter
  2. The Bluetooth ELM OBDII module/adapter failed to connect to the vehicle's OBDII system

Force will indicate which reason the connection failed to aid in troubleshooting.

Trouble Shooting Bluetooth OBDII Module Connection
  1. Make sure the Bluetooth OBDII module is powered
  2. Verify the MAC address for the device is unique
    1. Verifying a unique MAC address can be done by scanning for local Bluetooth devices from the Bluetooth settings within the Settings app of your Android device. Each Bluetooth device should have a unique MAC address. If the the OBDII module shares a MAC address with another device, it will need to be moved out of range from that device before it will work
  3. ELM clones are cheap and illegal clones of genuine ELM OBD interpreters. They tend to exist in many of the more inexpensive Bluetooth OBDII modules/adapters, avoid these.
    1. Among the many problems with ELM clones, a MAC address of 11:22:33:DD:EE:FF, which is supposed to be unique, is appearing on a large number of ELM clones. If you have two of these ELM clones within range, you will run into the unique MAC address problem
    2. If you run into a problem with being repeatedly asked for your PIN, you will need to replace the OBDII module/Adapter as it is faulty.
Trouble Shooting Vehicle OBDII Connection
  1. Verify that your vehicle's ignition is in the 'On' position or start the engine
  2. Try to cycle the ignition by turning the vehicle 'Off' and then 'On' and starting the engine
  3. Try to connect Force a few times consecutively after connection failure
    1. Sometimes certain vehicle ECU's can be defiant when trying to connect, it may take a few tries
  4. Verify that your vehicle is OBDII compliant
  5. ELM clones are cheap and illegal clones of genuine ELM OBD interpreters. They tend to exist in many of the more inexpensive Bluetooth OBDII modules/adapters, avoid these.
  6. Some Bluetooth OBDII modules/adapters just refuse to connect to certain vehicles... The VGATE modules don't seem to like to connect to US-spec Mitsubishi Lancer EVO 8's for example. This is not a software problem with Force, but a hardware/firmware problem with the OBDII module.
  7. Some vehicle's are not 'fully' OBDII compliant and may or may not work, especially around early OBDII compliance models (around 1996 for US domestic market and 2002 for Europe)

Using the OBDII Diagnostic

The OBD Diagnostic Screen allows you to view and clear the vehicles check engine light Diagnostic Trouble Codes (DTC). The OBD Diagnostic Screen can only be opened when Force is connect to vehicle's OBDII system via a Bluetooth OBDII module/adapter.

Nexus 5 force obd diagnostic.png

Read Trouble Codes

To read the diagnostic trouble codes (DTC), press the 'Read DTC' button at the top left of the OBD Diagnostic Screen. Force will communicate with the vehicle's ECU and in a few moments, the DTCs will appear on the screen (if any exist).

OBDII DTCs come in two flavors of Pending and Stored:

  • Pending DTCs will not turn on the check engine light. Pending codes mean the car suspects there might be a problem, but it is not sure. Pending codes are common with certain emission related problems where the vehicle has to be started and stopped a certain number of times with the issue persisting to turn on the check engine light.
  • Stored DTCs will turn on the check engine light. Stored codes mean the car has found a problem that needs to be fixed.
Clear Trouble Codes

To clear the diagnostic trouble codes (DTC), press the 'Clear DTC' button at the top right of the OBD Diagnostic Screen. Force will tell the vehicle to clear the DTCs and the check engine light should turn off. Force will then recheck for DTCs. In some cases, the ECU may report the codes that were just cleared until the vehicle ignition has been cycled, but the check engine light will be off.

OBD Diagnostic Gauges

The OBD Diagnostic Gauges display key engine parameter information obtained from the vehicle's OBDII system. The Force app must be connected to the vehicle's OBDII system via a Bluetooth ELM OBDII module/adapter to view the OBD Diagnostic Gauges. Nexus 5 force obd gauges.png

The following parameters are displayed:

  • Vehicle Speed
  • Engine RPM
  • Engine Coolant Temperature
  • Air Intake Temperature
  • Mass Airflow Sensor
  • Throttle Position Sensor
  • Ignition Timing
  • Long-term Fuel Trims

OBD Diagnostic Settings

The OBD Diagnostic Settings allows the user to configure the settings for the OBDII.

Nexus 5 force obd settings.png

OBD Devices Setting
Bluetooth Devices

This allows the user to select what Bluetooth ELM OBDII module/adapter they would like to connect to.

OBD Commands
Logged OBD Commands

This allows the user to select what OBDII PID (parameter identities) should be logged to an external .CSV file. This setting applies to the Force Logger, the Force Dynamometer and Force Acceleration. If the OBDII is connected while a Logger, Dynamometer or Acceleration log is started, the PID's selected here will be logged in addition to the standard parameters for each log type, respectively.

Supported OBD Commands

When Force is connected to a vehicle's OBDII system, the user can view a list of Supported OBD PID's (parameter identities) that the vehicle reports are supported. It is important to note that many OBDII PID's are not supported by every vehicle. This is because the equipment available on the vehicle does not apply to the PID or the manufacturer simply decided not to implement the PID.

Vehicle Screen

The Vehicle Screen allows the user to manage vehicle profiles from the Garage and to review vehicle logs and statistics.

There are two navigation options from the Vehicle Scree:

  • Vehicle Garage
    • Select, create, edit and delete vehicle profiles
  • Statistics
    • Review vehicle logs and vehicle statistics

Nexus 5 force vehicle home.png

Vehicle Garage

The Vehicle Garage allows the user to manage vehicle profiles. Vehicle profiles can be selected, created, edited or deleted from the Garage. Vehicle profiles provide key information about the vehicle to Force allowing Force to organize vehicle logs and calculate performance data about the vehicle. It is extremely important that the information provided in the vehicle profile is accurate.

Nexus 5 force garage home.png

Add a New Vehicle Profile

Adding a new Vehicle Profile is a straight forward process. Simply press the 'Add' button in the Garage menu and fill out the vehicle information in the form. It may take some research to find the gear ratios for your vehicle, they are usually available from vehicle specs or from automotive magazine archives. A search on Google will usually get the information you need.

Be aware that it is possible for many different variations of the same transmission to exist and you will need to verify that the information you entered is correct. Unfortunately, it is common for vehicle manufactures to publish the wrong information about vehicle's transmission due to a number of reasons.

To verify the transmission gearing and wheel size information for the Force Dynamometer, put the vehicle into the gear you entered the information for and drive at a constant speed. Compare the RPM calculated by Force in the Dynamometer Screen to the RPM on your vehicle's tachometer. If the two RPM's are close to each other, the information you entered is valid. If the two RPM's are not close, you will need to fix errors in the information provided. Since the wheel size is easy to determine (you can look at the tires for the size), most errors will probably come from transmission gearing information. Try researching if other gear ratios for the vehicle's transmission exist.

Nexus 5 force vehicle profile home.png

Steps to create a new Vehicle Profile
  1. From the Home Screen, touch the Vehicle button followed by the Garage button
  2. Touch the 'Add' button in the Garage menu
  3. Provide a vehicle icon (an image to associate with your vehicle)... not required
    1. Force gives you the option of using a photo from your phone or tablets gallery, or taking a new photo with the camera
  4. Provide a vehicle make (the manufacturer of the vehicle)
    1. Force provides a list of common manufacturers, however, if yours does not exist you can add it by touching the 'Add Make' button
  5. Provide a vehicle model
    1. Force provides a list of common makes, however, if yours does not exist you can add it by touching the 'Add Model' button
  6. Provide a description of the vehicle... not required
  7. Provide a vehicle model year (the year the vehicle was manufactured)
  8. Provide a vehicle weight in units of kilograms. Include the weight of the driver, passengers, gasoline, stuff in the car, etc... very important that this is accurate!
  9. Provide vehicle drag coefficient... usually can be found in vehicle specifications with a Google search
  10. Provide vehicle frontal area... usually can be found in vehicle specifications with a Google search
    1. The vehicle drag is important, but usually the default values are close enough for cars... trucks will need better data
  11. Select a vehicle drive-line
  12. Select a transmission type
  13. Select the desired gear for the transmission information
  14. Provide the gear ratio for the transmission gear... very important that this is accurate!
  15. Provide the final drive ratio for the transmission... very important that this is accurate!
  16. Provide the tire width... very important that this is accurate!
  17. Provide the tire aspect ratio... very important that this is accurate!
  18. Provide the tire diameter... very important that this is accurate!
  19. Press the 'Done' button at the bottom left of the Add Vehicle Screen

Edit a Vehicle Profile

Editing a Vehicle Profile is the same as creating a new Vehicle Profile.

  1. From the Home Screen, touch the Vehicle button followed by the Garage button
  2. Select the vehicle you want to edit
  3. Touch the 'Edit' button in the Garage Screen menu
  4. Edit the information
  5. Touch the 'Done' button at the bottom of the Edit Vehicle Screen.

Delete a Vehicle Profile

  1. From the Home Screen, touch the Vehicle button followed by the Garage button
  2. Select the vehicle you want to delete
  3. Touch the 'Remove' button in the Garage Screen menu

Select a Vehicle Profile

  1. From the Home Screen, touch the Vehicle button followed by the Garage button
  2. Touch the vehicle profile you would like the select
  3. The radio button on the right side of the vehicle item indicates what vehicle is selected in the list

Vehicle Statistics

The Vehicle Statistics Screen allows the user to review logs taken with the selected vehicle and statistics calculated from the logs automatically.

You can review logs of the following types:

  • Force Dynamometer Logs
  • Force Acceleration Logs
    • Elapsed Time Distance
    • Elapsed Time Velocity

Force Dynamometer Statistics

The user can review Dynamometer logs from the selected vehicle by selecting the 'Dyno' tab from the top of the Vehicle Statistics screen. To change changes, swipe left or right.

Nexus 5 force vehicle dyno stats.png

Dynamometer Statistics
  1. Peak Torque
  2. Peak Power
  3. Peak Acceleration
  4. Average Torque Under Curve
  5. Average Power Under Curve
  6. Average Acceleration Under Curve
  7. Peak Torque RPM
  8. Peak Power RPM
  9. Peak Acceleration RPM

Force Acceleration Distance Statistics

The user can review Acceleration Distance logs from the selected vehicle by selecting the 'Distance' tab from the top of the Vehicle Statistics screen. To change changes, swipe left or right.

Nexus 5 force vehicle distance stats.png

Acceleration Distance Statistics
  • 60 foot ET
  • 330 foot ET
  • 660 foot ET
  • 660 foot MPH
  • 1000 foot ET
  • 1000 foot MPH
  • 1320 foot ET
  • 1320 foot MPH
  • 1/2 mile ET
  • 1/2 mile MPH
  • 1 mile ET
  • 1 mile MPH
  • 1.5 mile ET
  • 1.5 mile MPH
  • 2 mile ET
  • 2 mile MPH

Force Acceleration Velocity Statistics

The user can review Acceleration Velocity logs from the selected vehicle by selecting the 'Velocity' tab from the top of the Vehicle Statistics screen. To change changes, swipe left or right.

Nexus 5 force vehicle velocity stats.png

Acceleration Distance Statistics
  • Elapsed time from 0-200mph in 10mph increments

Dynamometer Screen

The Dynamometer Screen allows the user to measure the torque and power produce by their vehicle's engine. The Force dynamometer works in the same way as a chassis dynamometer in that it measures the engines ability to accelerate an object. Where a chassis dynamometer measures the acceleration of a drum rotated by the vehicles wheels to calculate the torque and power, Force measures the vehicles acceleration on the road taking into account the vehicle weight, gearing and wind resistance to calculate torque and power. Force will generate torque and power measurements comparable to a chassis dynamometer.

Force relies on your smartphone or tablet’s internal sensors (the GPS and acceleration sensor) and highly tuned digital filters to estimate torque, power and acceleration without the need for external OBDII modules or additional sensors. Force can produce highly accurate performance estimations at over 50Hz (50 times per second) which is five times faster than the 10Hz (10 times per second) that most of the vehicle performance boxes get with their GPS or OBDII.

It is extremely important that the information provided for the vehicle profile (especially the vehicle weight, gear ratios and tire size) are accurate.

Nexus 5 force dyno home.png

Key Information Provided

  • Engine Torque
  • Engine Power
  • Engine RPM
  • Vehicle Speed
  • Vehicle Acceleration
  • GPS Sensor Status
  • Acceleration Sensor Status
  • OBD Connection Status
  • Vehicle Identity
  • Current Weather Conditions
  • Ambient Air Temperature
  • Ambient Air Pressure

Performing a Dynamometer Pull

The following steps should be taken to measure the torque and power produced by a vehicle's engine:

  1. Securely mount the phone or tablet squarely and level in the vehicle.
    1. By squarely, it is meant that the screen of phone or tablet should be facing towards the back of the vehicle.
    2. By level, it is meant that the car is on a level road and the device is mounted level to the vehicle.
    3. You can use the acceleration gauge to ensure the device is level. The indicator will turn the color green when the device is considered level, otherwise the indicator will turn the color red.
  2. Put the vehicle into the gear that you entered the vehicle profile information for. The Force Dynamometer will only work correctly when the vehicle is in the gear you provided the information for.
    1. If you have an automatic transmission, this may a bit tricky. You can select the desired gear with the transmission, but be sure not to press the acceleration pedal past the "kick-down point" where the car will decide to downshift a gear. You should be able to achieve full throttle without having the transmission kick-down a gear.
    2. A higher gear that can produce full engine load is ideal. On most vehicles, 1st and 2nd gear are to low to produce full engine load.
  3. Slow the vehicle to bring the engine RPM down as low as possible, 1,500-2,000RPM is an ideal starting point
  4. Press the 'Start' button at the bottom of the Force Dynamometer Screen
  5. Apply full throttle to the vehicle's engine and accelerate to red-line (or the maximum legal speed limit)
  6. Let off the throttle. Force will automatically stop the dynamometer and save the log
    1. To view the log, you can navigate to the Vehicle Screen and then to the Statistics Screen, you can open the log with a third-party spreadsheet application in Android or you can export the log to your computer and open it with any spreadsheet application.

Units of Measure

A number of different units of measure can be selected to fit the users preferences.

Torque Units of Measure

  • Foot Pounds
  • Newton Meters

Power Units of Measure

  • Mechanical Horse Power (United States)
  • Metric Horse Power (DIN/PS)
  • Watts
  • Kilowatts

Acceleration Screen

Force provides acceleration measurements so you can see just how fast your vehicle is. Like the Force Dynamometer, the Force Acceleration does not require a vehicle's OBDII system. Unlike most vehicle performance boxes which provide measurements at 10Hz , Force can provide GPS based velocity measurements at upwards of 50Hz.

Force will measure the acceleration of a vehicle in terms of distance and velocity. Common distances like 1/8th mile and 1/4 mile are measured for elapsed time and velocity. Force also measures the elapsed time to achieve velocities in increments of 10mph from 0-200mph. This is considerably more data than other applications or vehicle performance boxes offer, usually only 0-60mph and 0-100mph. All of this data is written to an external .CSV which can be opened with any spreadsheet application for further review.

Nexus 5 force acceleration home.png

Key Information Provided

  • Elapsed time from 0-200mph in 10mph increments
  • 60 foot ET
  • 330 foot ET
  • 660 foot ET
  • 660 foot MPH
  • 1000 foot ET
  • 1000 foot MPH
  • 1320 foot ET
  • 1320 foot MPH
  • 1/2 mile ET
  • 1/2 mile MPH
  • 1 mile ET
  • 1 mile MPH
  • 1.5 mile ET
  • 1.5 mile MPH
  • 2 mile ET
  • 2 mile MPH
  • GPS Sensor Status
  • Acceleration Sensor Status
  • OBD Connection Status
  • Vehicle Identity
  • Current Weather Conditions
  • Ambient Air Temperature
  • Ambient Air Pressure

Performing a Acceleration Pull

The following steps should be taken to measure the acceleration of a vehicle:

  1. Securely mount the phone or tablet squarely and level in the vehicle.
    1. By squarely, it is meant that the screen of phone or tablet should be facing towards the back of the vehicle.
    2. By level, it is meant that the car is on a level road and the device is mounted level to the vehicle.
    3. You can use the acceleration gauge to ensure the device is level. The indicator will turn the color green when the device is considered level, otherwise the indicator will turn the color red.
  2. Bring the vehicle to a complete stop
  3. Press the 'Start' button at the bottom of the Force Acceleration Screen.
  4. Accelerate the vehicle to the desired distance or velocity (or to the legal speed limit)... The timer will start automatically when the vehicle begins to accelerate
  5. Stop accelerating the vehicle when the desired distance or velocity has been achieved... The timer will automatically stop and save the log
    1. To view the log, you can navigate to the Vehicle Screen and then to the Statistics Screen, you can open the log with a third-party spreadsheet application in Android or you can export the log to your computer and open it with any spreadsheet application.

Logger Screen

The Logger Screen allows the user to log Force parameters and OBDII parameters to an external .CSV file.

Nexus 5 force logger home.png

Create Log

  1. From the Home Screen, touch the 'Logger' button
  2. Select the 'Parameters' menu item from the top of Logger Screen
  3. Select the parameters you would like to log
    1. Force parameters are vehicle acceleration and vehicle velocity
    2. OBDII parameters that can be logged can be viewed by touching the 'Supported OBD Commands' list item
    3. OBDII parameters can be selected to log with the 'Logged OBD Commands' list item
  4. Press the 'Start' button at the bottom of the Logger Screen
  5. Live data will begin to plot on the screen and will be logged to an external .CSV file
  6. Stop the log by pressing the 'Stop' button at the bottom of the Logger Screen

Bluetooth ELM OBDII Modules

ELM OBDII Interpreters

Force is intended to work with ELM327 based/compatible OBDII interpreters. This includes STN11xx interpreters.

ELM327 Supported OBDII Protocols

  • SAE J1850 PWM
  • SAE J1850 VPW
  • ISO 9141-2
  • ISO 14230-4 (fast)
  • ISO 14230-4 (slow)
  • ISO 15765-4 CAN
  • SAE J2411 (SWCAN)
  • SAE J1939 (250kbps)
  • SAE J1939 (500kbps)

Pirate ELM Clones

The 1.0 version of the ELM327 did not implement copy protection, and the PIC code was copied and is now sold in devices claiming to have a genuine ELM327. The 1.0 version of the ELM327 was buggish and devices containing cloned ELM327's are notorious for not responding correctly as well as having poor build quality. The 1.0 version of the ELM327 did not support CAN-BUS OBDII systems, which are on every new vehicle, so cloned ELM327's will likely not work on newer CAN-BUS vehicles.

Although these pirate clones may contain the ELM327 v1.0 code, they may falsely report the version number as the current version provided by the genuine ELM327, and in some cases report an as-yet non-existent version.

Recommended OBDII Modules

OBDLink MX

Obdlinkmx.jpg

We develop Force with the OBDLink MX. It has extremely fast data transfer rates, it supports the all common OBDII protocols plus advanced Ford & GM vehicle networks (MS-CAN and SW-CAN). We have tested the OBDLink MX with a number of different phones and vehicles without issues. Note that my OBDLink MX reports itself as using a ELM327v1.3a instead of a STN1110 which seems to reported in a number of other places.

OBDLink LX

Obdlinklx.png

Very much like the OBDLink MX. Less expensive, but it doesn't offer the additional OBDII protocol support for Ford & GM vehicle networks (MS-CAN and SW-CAN). Note that my OBDLink LX reports itself as using a ELM327v1.3a instead of a STN1110 which seems to reported in a number of other places.

Clone OBDII Modules

These are OBD2 Bluetooth modules that are very likely pirated clones. Most of them report using ELM327v1.5, which does not exist. They also do not respond to special @1 and @2 AT commands. They are cheap and use stolen intellectual property, but lots of people use them (for the former reason, ignoring the later reason). Some are reliable, some are terrible.

Vgate Scan OBD Scan

Vgatescan.jpg

This is a reliable cloned ELM327. It conforms to the ELM327 command set and responds as expected. Reports using ELM327v1.5 and does not respond to the special @1 and @2 AT commands. Can be a little difficult to bind. To bind it you have to plug it into the car and then immediately refresh the available devices on the Android device. It may take a few tries.

Konnwei OBDING Bluetooth

Konnweiobd2.jpg

This is a reliable cloned ELM327. It conforms to the ELM327 command set and responds as expected. It also has LED indicator lights and a power switch. Reports using ELM327v1.5 and does not respond to the special @1 and @2 AT commands. Binding is more reliable with this device than many other clones.

Panlong Diagnostic Scanner

Panlongobd2.jpg

This is a reliable cloned ELM327. It conforms to the ELM327 command set and responds as expected. It has a very small package. Reports using ELM327v1.5 and does not respond to the special @1 and @2 AT commands. Can be a little difficult to bind. To bind it you have to plug it into the car and then immediately refresh the available devices on the Android device. It may take a few tries.

OBD Diagnostic Interface

Obddiagnosticinterface.jpg

This is a reliable cloned ELM327. It conforms to the ELM327 command set and responds as expected. It has a larger package and also has LED indicator lights. Reports using ELM327v1.5 and does not respond to the special @1 and @2 AT commands. Can be a little difficult to bind. To bind it you have to plug it into the car and then immediately refresh the available devices on the Android device. It may take a few tries.

i saddle

Isaddle.jpg

This is a less reliable cloned ELM327. It does *not* conform fully to the ELM327 command set and sometimes responds in illegal ways. It has a small package and does not have LED indicator lights. Reports using ELM327v1.5 and does not respond to the special @1 and @2 AT commands. Can be very difficult to bind. It does not seem to indicate it has successfully bound to the Android device when the binding process is complete. To bind it you have to plug it into the car and then immediately refresh the available devices on the Android device. Then you must wait for the binding process to seemingly freeze, refresh the devices and it may or may not be available. It may take many tries.