I recently bought a Bluetooth obd2 reader. I am wondering if anyone know of any app that may communicate better with my 00 acura tl. Ive downloaded dash command and torque. They both work well with my for and have the option to buy extended parameters. Neither have this option for the acura.
Thanks in advance guys.

 

I have a 99TL and I also have the Torque app. Many of the parameters/sensors are not available, probably due to the car's age. My newer cars have much more sensors that I can display on the app.

 

I'm with schen72. Different cars/newer cars allow for more data to come accross.

 

I have torque pro. It shows everything that our ECUs have available to read (i have confirmed next to my live data reading scan tool). Our ECUs are old, and quite frankly minimalistic pieces of crap. Nothing out there will read more as there isnt anything else to read that the paid for apps dont already show.

 

Thanks for your responses. I just wanted to make sure I was not missing anything. I bought one that connected through wifi. I kind of regret it because when connected to my phone I have no service. But I plan on buying a tablet to use with my reader. What reader did you choose?

 

Wait.. your OP and title says Bluetooth.. now you're saying you bought one that connects through wifi..

 

yea it connects through wifi. Had I said wifi some people may have not known its the same as the Bluetooth. With the exception of the way it connects.

 

Bluetooth is the connection to the ECU, but then when it looks up those codes it uses Google (Wi-Fi)

Frankly I just make sure I'm close to a Wi-Fi spot when looking up codes. Otherwise I have Wi-Fi off when I drive in my car anyway.

 

There's OBD readers that use an ADHOC wifi signal like a gopro camera does. They're not Bluetooth.

 

The cheap bluetooth ones use a chip called the ELM327. It basically converts your cars OBD2 data into serial (similar to what an old PC used to have, except a different type of serial). The ELM327 sends that data to a bluetooth chip that transmits that serial data over bluetooth to your Android phone. Those two chips are very cheap.


The problem is with iOS devices, Apple omitted the bluetooth serial ability for developers to use. How the manufactures got around it was to put a mini webserver and WiFi access point inside instead of the bluetooth chip (the thing that hosts a website and a part similar to your home WiFi router). Alternatively, some expensive bluetooth readers that are compatible with iOS have implemented an expensive custom bluetooth workaround not using the cheap bluetooth chip.