Frequently Asked Questions (FAQs)
1. Is there an App included with the device? How to choose the app for my vehicle?
No, an OBD2 app is required but not included. Many third-party OBD2 apps are available for download (some may require purchase) from Google Play Store and Apple App Store. Features depend on the chosen app. Recommended apps for generic OBD2 functions include Car Scanner ELM OBD2, Inforcar, or OBD Fusion (paid). Advanced apps like Carista, BimmerCode, BimmerLink, or OBD JScan may require subscriptions or be more expensive. More details can be found in the "App and vehicle compatibility guide.pdf", available on the Veepeak product page or by scanning the QR code on the device.
2. Does it work with iOS devices (iPhone or iPad)?
✔️ Yes, it is compatible with Apple iOS devices via Bluetooth Low Energy (LE), not Wi-Fi. Do not pair or connect via iOS Bluetooth Settings. Instead, connect directly within the app, which will handle the Bluetooth connection.
3. Is it compatible with Android head units?
It works with Android phones and tablets, but compatibility issues may arise with some Android head units due to limited Bluetooth profile support or manufacturer limitations. Veepeak does not maintain a compatibility list due to market complexity. For some Android head units, check Bluetooth settings for disabled or incorrect pairing PINs. If issues persist, contact Veepeak or the head unit manufacturer.
4. Does it work with hybrid plug-in (PHEV) or all-electric vehicles (BEV)?
EVs and PHEVs are low or zero emission vehicles and may not follow standard OBD II specs. A capable app is needed, such as Car Scanner ELM OBD2 (select the corresponding connection profile), Dr Prius, LeafSpy, EVNotify, EV Watchdog, MyGreenVolt, CanZE, or ABRP (iOS version). Support for the latest EVs can be complex and depends on developer plans.
5. What's the difference between OBD-II standard and enhanced/advanced diagnostics?
OBD-II Standard diagnostics are mandated by regulatory bodies (e.g., EPA in the US) for emissions-related data, providing standardized diagnostic trouble codes (DTCs) and live data parameters (standard PIDs) like engine RPM, vehicle speed, fuel system status, and oxygen sensor readings. These are readable by any compliant OBD-II scanner.
Enhanced/Advanced Diagnostics provide additional data beyond the standard, including proprietary DTCs and extended PIDs specific to vehicle manufacturers and models. This often includes detailed information on transmission, ABS, airbags, body control modules, and more, requiring more capable diagnostic tools or software.
6. Can it do enhanced diagnostics to read or reset my ABS, or airbag lights?
This depends on the chosen app. Most OBD-II apps offer basic emission-related check engine light diagnostics. Some apps provide advanced diagnostics for selected vehicles, such as OBD Fusion, OBD JScan, AlfaOBD, Carista OBD, or BimmerLink. Contact Veepeak or the app developer to check availability for your vehicle. Note: It cannot reset Oil change or maintenance required lights, and there are no error codes to read for these functions.
7. Which sensor data can I get?
Readable parameters depend on the vehicle manufacturer's OBDII system. Newer vehicles generally provide more readings and faster refresh speeds. All supported sensor data can be found in the OBD app (e.g., Car Scanner ELM OBD2 – All sensors).
8. Does it read transmission temperature?
Transmission (fluid) temperature is a manufacturer-specific PID belonging to advanced diagnostics and is not read by most generic OBD2 apps. Check advanced diagnostics availability or contact Veepeak customer support for suitable apps. You may search for custom PID information online and add it to the app. This applies to other manufacturer-specific PIDs (e.g., DPF). For GM or Ford vehicles, use OBD Fusion App: Setting -> User-Defined PIDs, then Menu -> Import built-in PIDs, select brand to see extended PIDs including transmission temperature. Car Scanner ELM OBD2 apps may also provide extended PIDs for some vehicles; select the appropriate connection profile.
9. Does it support coding of BMW G series?
Currently, it does not support all coding options in BimmerCode for G series (G01, G03, G20, G30, etc.). Other adapters are recommended by BimmerCode.
10. Does it work with BMW or Mini model year before 2008 via BimmerCode or BimmerLink App?
❌ No, it is only for MY2008 or newer. Other adapters are recommended by BimmerCode.
11. Does it work with motorbikes?
It may work with some motorbikes if they use an OBD-II protocol and a suitable OBD app is available. For BMW motorbikes, the MotoScan App is supported for diagnostics and sensor reading, but not for coding or service reset.
12. Does it support key fob programming?
❌ No, for most vehicles. Currently, only a few FCA vehicles are supported using apps like OBD JScan, AlfaOBD, or Appcar DiagFCA. Check the app page for supported vehicles.
13. Can I leave the device plugged in all the time?
You can leave the adapter plugged in for a few days if your car battery is not old or the car is driven frequently. If the car sits for more than 1 week, it is strongly recommended to remove the device.
14. Where can I find how to connect & use videos?
Visit the product page "Product guides & documents", the Veepeak website, or scan the QR code on the device for the latest user instructions, compatibility, connection & troubleshooting guides, and product usage videos.
Common Issues & Troubleshooting
1. Device does not power up (no blue light).
First, check if the vehicle's cigar fuse is in good condition. Try with another vehicle to verify. If the OBD2 port is fine, please contact Veepeak for assistance.
2. When I try to connect "VEEPEAK" with my iPhone, it tells me it is not supported.
This device uses Bluetooth Low Energy (LE) for iOS devices. You may see this error when trying to pair via iOS Bluetooth Settings. You do not need to connect with VEEPEAK here. Restart your iOS device; "VEEPEAK" should appear under "Other Devices". Then, start the app and connect directly within the app (refer to app connection tips).
3. Could not pair my Android device with "VEEPEAK".
- Turn Bluetooth off and on again. Try pairing a few more times.
- Restart your phone, disconnect other Bluetooth devices, and turn off Wi-Fi/cellular data.
- Clear Bluetooth cache/storage: Go to Settings -> Apps (show system) -> Bluetooth -> Storage & Cache, clear them, and restart the phone (the exact route may vary by phone).
- For Car Scanner ELM OBD2 or Infocar apps, initiate Bluetooth pairing within the app's settings.
- For Android head units, check Bluetooth settings to ensure the PIN is enabled and correct (default is usually 1234).
4. Device powers up, but "VEEPEAK" is not showing up on my phone's Bluetooth device list.
Ensure the device is not connected to other phones or tablets. Restart your phone, toggle Bluetooth off and on, refresh the Bluetooth list, and wait a few moments.
5. "VEEPEAK" quickly disconnects or does not show as connected after pairing (Android).
This can occur with some Android phones. As long as it's paired successfully via Bluetooth, you can start the app to connect. (For Torque Pro app, switch to the app to select the Bluetooth device after pairing). It might show as saved, paired, or previously connected, but it is actually connected.
6. App not connecting to OBD II Device (ELM connection fails).
Ensure the app is compatible, correct app connection settings are used, and app permissions (Bluetooth, or devices nearby) are granted. Try removing and reinstalling the app (especially after an OS update). Test with a different app like Car Scanner ELM OBD2 or Infocar (both are free). Note: The device can only connect to one app at a time; close other OBD apps when connecting to a new one. For example, an error in Car Scanner App might indicate the connection type is set incorrectly; set it to Bluetooth LE and select VEEPEAK as the Bluetooth device.
7. Cannot connect to vehicle (or ECU connection fails).
Ensure the device fits snugly in the OBD2 port (pushing harder might be needed, but powering up doesn't guarantee a good fit). Verify your vehicle is OBD2 compliant and the connector is in good condition. Check if your vehicle is supported by the app. Ensure ignition is ON or the vehicle is started. Try connecting to another vehicle to rule out a device issue.
8. Connection is not stable and gets disrupted during use.
Keep the device close to your phone, close other apps, and turn off Wi-Fi & cellular data. Update the app to the latest version. Try a different app to see if the issue persists.
9. No data is read after it connects to the vehicle.
Try with a different app to see if it makes a difference.
10. Could not read the trouble codes.
Try with a different app. If there are no check engine lights on the dashboard, a capable app might be needed to read these codes. Contact Veepeak with your vehicle make/model/year to identify a suitable app.
11. Could not clear trouble codes.
Multiple attempts may be needed. Try with Key On Engine Off or check for vehicle-specific procedures. Some vehicles may not respond correctly to the clearing command, and some codes require the fault to be fixed first.
Car Scanner App Connection Example
The "Car Scanner" app interface is shown, featuring navigation tabs for "Dashboard", "Live data", and "All sensors". A prominent "Connection problems" alert is displayed, warning about iOS 14 privacy restrictions related to "Local network access". It states that if "Car Scanner" hasn't been granted local network permission, it cannot connect to the ELM327 with a Wi-Fi connection type. The alert advises users to go to iOS Settings -> Privacy -> Local network and allow "Car Scanner" access to the local network. It concludes by stating "Car Scanner wasn't able to establish connection with ELM327."
