It works with cars and light trucks (including hybrids) sold in the United States in or after 1996. Vehicles in other regions that are OBD II / EOBD / JOBD may also be supported (Canada – 1998, European Union – 2001 (gas), 2004 (diesel), Australia – 2006 (gas), 2007 (diesel), etc.)

Most OBD2 apps can only read check engine light. However, enhanced diagnostics on selected makes and models are also available when using the appropriate application. Please check with the application developer.

The OBDCheck BLE works with Android & iOS devices. Note: many Android head units are incompatible.

Normally you can leave it plugged in if you are driving the vehicle frequently. However, it’s always recommended to unplug the OBD2 device when it’s not in use.

A third-party OBD2 app is required (see above compatible app list). There are free and paid ones and some apps provide in-app purchase. Please check the product page for compatible apps and the app page for more information about the features and prices.

Try the following ways: disable and enable Bluetooth (most efficient way; try a few times if the first time does not work); restart your phone; turn off WiFi; clear Bluetooth cache/storage.

If VEEPEAK is paired with your Android phone, but stays connected for only a few seconds then becomes previously connected device, don’t worry, usually it’s still connected. You just start the app, and see if you can select VEEPEAK as the Bluetooth device to connect.

Please do not try to connect VEEPEAK through the iOS Bluetooth Settings. No regular Bluetooth pairing is needed for Bluetooth LE. Please directly connect in the app.

It reads standard SAE PIDs such as O2 Readings, EOT, EGT, Throttle, Speed, Fuel Trim, DPF Temp, Balance Rates and more.
Remember readable parameters depend on what’s installed on the OBDII system by the manufacturer. Generally, newer vehicles will give more readings and faster refresh speed. Please also note that more sensors you have on the list the refresh frequency is lower due to limited vehicle bus/OBD device throughput. Some readings like transmission temp are manufacturer-specific and you will need the custom PID or a capable App. Contact the app developer to verify if it’s supported.

Check if the device is powered on (blue LED light). If not, check the cigar fuse of your vehicle. If the device is powered on, make sure you are using a compatible phone/tablet and seeing the right place: Bluetooth list for VEEPEAK. 

Check the app compatibility and make sure the correct connection settings is made in the App. If it does not help, try the following: remove the app and re-install it; try with a different App.

Verify if your vehicle is OBD2 compliant and the ignition key is at ON (check the car manual for the right mode for diagnostics or just start the engine); Check if the OBD II connector is in good condition: no bad pins or wires, no corrosion; try with another vehicle.

Please contact the app support in the app or through their website.

It works with cars and light trucks (including hybrids) sold in the United States in or after 1996. Vehicles in other regions that are OBD II / EOBD / JOBD may also be supported (Canada – 1998, European Union – 2001 (gas), 2004 (diesel), Australia – 2006 (gas), 2007 (diesel), etc.)

Most OBD2 apps can only read check engine light. However, enhanced diagnostics on selected makes and models are also available when using the appropriate application. Please check with the application developer.

The OBDCheck BLE works with Android & iOS devices. Note: many Android head units are incompatible.

Normally you can leave it plugged in if you are driving the vehicle frequently. However, it’s always recommended to unplug the OBD2 device when it’s not in use.

A third-party OBD2 app is required (see above compatible app list). There are free and paid ones and some apps provide in-app purchase. Please check the product page for compatible apps and the app page for more information about the features and prices.

Try the following ways: disable and enable Bluetooth (most efficient way; try a few times if the first time does not work); restart your phone; turn off WiFi; clear Bluetooth cache/storage.

If VEEPEAK is paired with your Android phone, but stays connected for only a few seconds then becomes previously connected device, don’t worry, usually it’s still connected. You just start the app, and see if you can select VEEPEAK as the Bluetooth device to connect.

Please do not try to connect VEEPEAK through the iOS Bluetooth Settings. No regular Bluetooth pairing is needed for Bluetooth LE. Please directly connect in the app.

It reads standard SAE PIDs such as O2 Readings, EOT, EGT, Throttle, Speed, Fuel Trim, DPF Temp, Balance Rates and more.
Remember readable parameters depend on what’s installed on the OBDII system by the manufacturer. Generally, newer vehicles will give more readings and faster refresh speed. Please also note that more sensors you have on the list the refresh frequency is lower due to limited vehicle bus/OBD device throughput. Some readings like transmission temp are manufacturer-specific and you will need the custom PID or a capable App. Contact the app developer to verify if it’s supported.

Check if the device is powered on (blue LED light). If not, check the cigar fuse of your vehicle. If the device is powered on, make sure you are using a compatible phone/tablet and seeing the right place: Bluetooth list for VEEPEAK. 

Check the app compatibility and make sure the correct connection settings is made in the App. If it does not help, try the following: remove the app and re-install it; try with a different App.

Verify if your vehicle is OBD2 compliant and the ignition key is at ON (check the car manual for the right mode for diagnostics or just start the engine); Check if the OBD II connector is in good condition: no bad pins or wires, no corrosion; try with another vehicle.

Please contact the app support in the app or through their website.

The device works with OBD II compliant vehicles (year 96 or newer in the US). It does NOT work with OBD I vehicles. For OBD II compliant vehicles, there should be a 16 pin DLC (Diagnostic Link Connector) usually under the dash or behind ashtray AND a note on a sticker or nameplate under the hood: “OBD II compliant/certified”.

It reads check engine light trouble codes (sometimes called service engine soon).

No, it does not read or reset these. Only supports check engine light.

Check the cigar fuse of your vehicle and try on another vehicle to see if the OBD connector is in good condition.

Make sure your vehicle is OBD2 compliant, the device is plugged in well and the ignition is at ON. Also start the vehicle to try again. Try it on another vehicle to see if the device is defective or incompatible with your vehicle.

First check if you have any other dash lights on. Sometimes fault from other systems will also cause the check engine light on. Or it’s a manufacturer-specific code that is not in the code library of the device.

Please note that not all codes can be cleared in this way. For some codes (especially confirmed or permanent), if the problem causing the code hasn’t been fixed, it won’t be cleared or it may be cleared, but will come back again right away. We usually suggest that you first use the code to check your car and fix the problems.

Not all vehicles support all the OBD II modes (depends on the car manufacturer).

It’s specially designed for Ford, Mazda, Lincoln and Mercury vehicles: 99% of models after 2000 and around 92% of models after 1996 (the year when OBD2 became a standart in USA).

FORScan and you can get it here: https://forscan.org/download.html

Many advanced features are only available in FORScan for Windows extended license. You can get 2-month free Extended License via this link: https://forscan.org/download.html, or purchase longer license at a small price.

Please check if the device is recognized as “USB-SERIAL CH340” in Device Manager. If not, please install the driver first.

1. Your vehicle is too new for current FORScan version;
2. Your vehicle has custom PCM tune (changed calibration). Please contact the developer at contact@forscan.org.

Windows 2000/XP/Vista/7/8/8.1/10.

contact@forscan.org

The device works with OBD II compliant vehicles (year 96 or newer in the US). It does NOT work with OBD I vehicles. For OBD II compliant vehicles, there should be a 16 pin DLC (Diagnostic Link Connector) usually under the dash or behind ashtray AND a note on a sticker or nameplate under the hood: “OBD II compliant/certified”.

It reads check engine light trouble codes (sometimes called service engine soon).

Check the cigar fuse of your vehicle and try on another vehicle to see if the OBD connector is in good condition.

Make sure your vehicle is OBD2 compliant, the device is plugged in well and the ignition is at ON. Also start the vehicle to try again. Try it on another vehicle to see if the device is defective or incompatible with your vehicle.

First check if you have any other dash lights on. Sometimes fault from other systems will also cause the check engine light on. Or it’s a manufacturer-specific code that is not in the code library of the device.

Please note that not all codes can be cleared in this way. For some codes (especially confirmed or permanent), if the problem causing the code hasn’t been fixed, it won’t be cleared or it may be cleared, but will come back again right away. We usually suggest that you first use the code to check your car and fix the problems.

Not all vehicles support all the OBD II modes (depends on the car manufacturer).

It works with vehicles (including hybrids) sold in the United States in or after 1996. Vehicles in other regions that are OBD II / EOBD / JOBD may also be supported (Canada – 1998, European Union – 2001 (gas), 2004 (diesel), Australia – 2006 (gas), 2007 (diesel), etc.)

The OBD2 devices are normally designed to read check engine light. However, enhanced diagnostics on selected makes and models are also available when using the appropriate application. Please check with the application developer.

The VP11 only works with Android & Windows. The Bluetooth 4.0 LE model (OBDCheck BLE) is required for iOS devices.

Normally you can leave it plugged in if you are driving the vehicle frequently. However, it’s always recommended to unplug the OBD2 device when it’s not in use.

A third-party OBD2 app is required. There are free and paid ones and some apps provide in-app purchase. Please check the product page for compatible apps and the app page for more information about the features and prices.

O2 Readings, EOT, EGT, Throttle, Boost, Speed, Fuel Trim, DPF Temp, Balance Rates and more.
Remember readable parameters depend on what’s installed on the OBDII system by the manufacturer. Generally, newer vehicles will give more readings and faster refresh speed. Please also note that more sensors you have on the list the refresh frequency is lower due to limited vehicle bus/OBD device throughput. Some readings like transmission temp are manufacturer-specific and you will need the custom PID. Contact the app developer to verify if it’s supported.

Check if the device is powered on (red power LED). If not, check the cigar fuse of your vehicle. If the device is powered on, make sure you are using a compatible phone/tablet and seeing the right place: Bluetooth list for OBDII. 

Check the app hardware compatibility first. Then make sure the ignition key is at ON (or start the engine) and the correct connection settings is made in the App. Fully quit the app and re-start it to connect again.

Verify if your vehicle is OBD2 compliant and the ignition key is at ON (check the car manual for the right mode for diagnostics or just start the engine). Check if the OBD II connector is in good condition: no bad pins or wires, no corrosion. If it works with another vehicle, submit the connection log in the app so the app support can further check.

It works with vehicles (including hybrids) sold in the United States in or after 1996. Vehicles in other regions that are OBD II / EOBD / JOBD may also be supported (Canada – 1998, European Union – 2001 (gas), 2004 (diesel), Australia – 2006 (gas), 2007 (diesel), etc.)

The OBD2 devices are normally designed to read check engine light. However, enhanced diagnostics on selected makes and models are also available when using the appropriate application. Please check with the application developer.

The VP01 is compatible with iOS & Android phones and tablets. For Android, be sure to change connection method to WiFi.

We do not suggest that you leave the WiFi version plugged in if it’s not in use. WiFi consumes significantly more power than Bluetooth.

A third-party OBD2 app is required to work with our wireless OBD2 devices. There are free and paid ones and some apps provide in-app purchase. Please check the product page for compatible apps and the app page for more information about the features and prices.

O2 Readings, EOT, EGT, Throttle, Boost, Speed, Fuel Trim, DPF Temp, Balance Rates and more.

Remember readable parameters depend on what’s installed on the OBDII system by the manufacturer. Generally, newer vehicles will give more readings and faster refresh speed. Please also note that more sensors you have on the list the refresh frequency is lower due to limited vehicle bus/OBD device throughput. Some readings like transmission temp are manufacturer-specific and you will need the custom PID. Contact the app developer to verify if it’s supported.

Check if the device is powered on (it should become warm after being plugged in). If not, check the cigar fuse of your vehicle. If the device is powered on, make sure you are using a compatible phone/tablet and seeing the right place: WiFi list for WiFi_OBDII. 

Check the app hardware compatibility first. Then make sure the ignition key is at ON (or start the engine) and the correct connection settings is made in the App. Fully quit the app and re-start it to connect again.

Verify if your vehicle is OBD2 compliant and the ignition key is at ON (check the car manual for the right mode for diagnostics or just start the engine). Check if the OBD II connector is in good condition: no bad pins or wires, no corrosion. If it works with another vehicle, submit the connection log in the app so the app support can further check.

If you are using an Android device, there is nothing to do to help for the moment.