Qstarz OBDII Compatibility for RaceChrono: A Comprehensive Guide

For automotive enthusiasts and performance drivers, the integration of OBD-II (On-Board Diagnostics II) data with RaceChrono software offers a powerful tool for analyzing and improving driving performance. Understanding which car models and OBD-II readers work seamlessly with RaceChrono is crucial. This guide focuses on the compatibility of Qstarz Obdii devices and other readers with RaceChrono, providing a detailed list based on real-world testing and user feedback.

Harnessing the power of OBD-II connectivity allows RaceChrono to display and log a wealth of real-time data directly from your vehicle’s engine control unit (ECU). This data can include parameters like RPM, throttle position, coolant temperature, and much more, providing valuable insights into your car’s behavior on the track or road. While RaceChrono is designed to be versatile, the success of this integration heavily relies on the compatibility of your chosen OBD-II reader with both the software and your specific car model.

Below is a compilation of car and motorbike models that have been tested and confirmed to work with RaceChrono’s OBD-II feature. Notably, many successful setups utilize Qstarz OBDII devices like the Qstarz BT-818X, alongside other reliable readers such as OBDKey and ELM327 based adapters. This list is continuously updated as more users contribute their experiences.

Successfully Tested Car and OBD-II Reader Combinations:

  • Audi:
    • 2000 Audi TT 165kW (v1.00, v1.35 and OBDKey, CarPal)
    • 2001 Audi S4 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • BMW:
    • 2004 BMW M3 (v1.00 and OBDKey)
    • e46 BMW 325ti (v1.02 and OBDKey)
    • BMW 135i (v1.10 and OBDKey)
    • 2008 BMW 550i (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 1995 BMW M3 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 1997 BMW M3 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 1998 BMW M3 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)

Alt text: BMW M3 E46 driving on a race track, illustrating the application of RaceChrono and OBD-II data logging for performance analysis.

  • Chevrolet:
    • 2007 Chevrolet Matiz 0.8 (v1.10 with ELM327)
    • 2004 Chevrolet Zo6 (RC v1.10, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 Chevy Corvette Zo6 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2003 Chevy Corvette Zo6 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 Chevy Corvette Zo6, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2004 Chevrolet Zo6 ( RC v1.10, Nokia E62, Qstarz BT-818X, OBDKey)
  • Dodge:
    • 2009 Dodge Viper ACR ( RC v1.10, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2009 Dodge Challenger SRT8, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Ferrari:
    • 2008 Ferrari F430 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2005 Ferrari F360 Modena (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2009 Ferrari Challenge (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 1999 Ferrari F360 Modena (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2009 Ferrari F430 Scuderia (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2000 Ferrari Challenge (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2001 Ferrari F456 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2001 Ferrari F360 Spider (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2008 Ferrari F430 Spider (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)

Alt text: Ferrari F430 Scuderia dashboard showcasing a RaceChrono setup utilizing a Qstarz OBDII device for capturing performance data.

  • Fiat:
    • 2002 Fiat Stilo 1.8 (RC v1.40)
  • Ford:
    • Ford Focus RS (OBDKey)
    • 2006 Ford Mustang, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Honda:
    • Honda Jazz
    • 2006 Honda S2000 (RC v1.30, Nokia E82, Serial ELM327 + Bluetooth RS232 adapter)
    • 2000 Honda S2000 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Lada:
    • 2002 Lada Samara 1.5i (Euro3, Bosch MP7.0) (v1.10 with ELM327)
  • Lexus:
    • 2000 Lexus IS200 (v1.10 with OBDKey)
  • Lotus:
    • Lotus Elise R (european/asian model) (v1.10 with OBDKey)
    • 2008 Lotus 211 ( RC v1.10, Nokia E62, Qstarz BT-818X, OBDKey)
  • Mazda:
    • 2003 Mazda RX8 (v0.96 and OBDKey)
    • 2003-2008 Mazda RX8 (v1.02 and OBDKey)
    • 2008 Mazda MX-5 (v1.10 and OBDKey)
    • 1997 Mazda Miata (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Nissan:
    • 2006 Nissan Primera P12 1.8 85kW (v1.10 with ELM327)
    • 2009 Nissan GTR (RC v1.40, OBDKey)
  • Opel (Saturn):
    • Opel GT 2008 2.0 265cv (Saturn Sky)
  • Porsche:
    • 2004 Porsche Cayenne (tested with v0.96)
    • 2003 Porsche 911 996 GT3 (v1.02 and OBDKey)
    • 2008 Porsche Cayman GTR ( RC v1.10, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2003 Porsche GT3 (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 1997 Porsche 993, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2005 Porsche 997S, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2009 Porsche C4S, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2003 Porsche 996, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 Porsche GT3, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2002 Porsche 996, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 Porsche Turbo (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Renault:
    • 2003 Renault Megane Coupe (v1.10 and OBDKey)
  • Seat:
    • 2008 Seat Ibiza 1.2 (RC v1.40)
  • Smart:
    • 2004 Smart Roadster (RC v1.30, Nokia E71, Elmscan 5)
  • Subaru:
    • 2007 Subaru Impreza STI (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 Subaru WRX (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2006 Subaru STI, (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Suzuki:
    • Suzuki SX4 (european model) (v1.10 with a cheap BT reader from dealextreme)
  • Toyota:
    • 2007 Toyota Sienna (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2008 Toyota Sequoia (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
  • Volkswagen:
    • 2008 Volkswagen Jetta 1.9 TDI (v1.00 and OBDKey)
    • 2003 Volkswagen Golf GTI (v1.02 and AlphaBid)
    • 2003 VW Golf GTI (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • 2007 VW R32 mk5, (RC v1.35, Nokia N95, Qstarz BT-818X, OBDKey)
  • Volvo:
    • Volvo S40 2001 2.0 petrol (ELM327)

Motorbike and OBD-reader Combinations:

  • Triumph:
    • Triumph Daytona 675 (v1.10 and OBDKey)

Combinations Reported Not to Work:

  • Lotus:
    • 2005 Lotus Elise (RC v1.30, Nokia E62, Qstarz BT-818X, OBDKey)
    • Problem: OBDKey triggered antitheft mode, requiring key fob reset. Strange beeping noises related to the alarm were also observed. While OBD data could be logged, the interaction was unstable and problematic.

Recommended OBD-II Readers:

  • Qstarz BT-818X: As evidenced by the list above, the Qstarz BT-818X OBDII Bluetooth GPS receiver is a frequently used and reliable option for RaceChrono users. Its compatibility across a wide range of vehicles makes it a strong contender.
  • OBDKey Bluetooth: http://www.obdkey.com/ – Generally works well and is considered faster than Car-Pal.
  • Car-Pal Bluetooth: Works but is noted to be more expensive and slower than OBDKey.
  • Alpha-Bid’s Bluetooth OBD-II reader: Compatible with RaceChrono v1.02 beta and later, but also reported to be as slow as Car-Pal.
  • ELM327 based readers: Various ELM327 Bluetooth adapters are used, demonstrating broad compatibility, particularly with newer RaceChrono versions.

Potential Issues with OBD-II Readers:

  • OBDKey Reader Limitation: With some vehicles, like the 2008 Jetta, the OBDKey may not resume operation after the engine is stopped or if the session starts before engine ignition. A workaround is to briefly unplug and replug the reader.
  • RPM Graph Viewer Hang (RaceChrono v1.00): Versions prior to v1.01 beta may experience hangs in the graph viewer when RPM exceeds 8000rpm. Update to v1.01 beta or later to resolve this.
  • OBD Timestamp Issues (RaceChrono v1.00 and earlier): Timestamp inaccuracies with OBD data were present in RaceChrono v1.00 and earlier. This was addressed in v1.01 beta and subsequent releases.
  • Bluetooth Interference: In some instances, a car’s built-in Bluetooth handsfree system can interfere with the OBD-II connection, causing corrupted sessions. Disabling the car’s Bluetooth may be necessary.
  • GPS Distortion: Placement of the GPS receiver near engine electronics, such as below the rear window, can potentially lead to GPS signal distortion.

Call to Action:

To further expand this compatibility resource and assist fellow RaceChrono users, your contributions are invaluable! Please share your successful (and unsuccessful) car and OBD-II reader combinations. If you have NMEA log files (*-nmea.txt under RaceChronoSessions) recorded with v0.96 and an OBD-II reader, especially sessions with all OBD-II channels enabled, please send them to tracks(at)racechrono.com. Your input helps build a more comprehensive and helpful guide for the RaceChrono community.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *