Hi,

I have a PLX as well blue OBD adaptor. I tried it out with few Japanese and Korean vehicles. Most of the Japanese domestic models did not worked except Prius (It uses canbus). However Korean cars worked. I think issue is Japanese domestic models does not support OBDII (it support JOBD which is slightly different)

Zafar I am driving an ST215 caldina and havn’t had success connecting either (cheapo blue dongle/torque works on all other new OBDII cars I have tried it on). What is this other program you are using to communicate with your ECU?

There seems to be very little info around about JDM cars and OBDII. My very limited understanding is they tend to use their own protocols for each manufacturer. But as someone already mentioned there are jap plug in modules that work with just about any JDM car (blitz r-vit etc etc…)

Torque is a great app but if it can be made to work with JDM models (if that’s even possible) it would open up a massive new user base….

My car is a Toyota Caldina ’00 (JDM grey import). Have had no success talking to the ECU.

I have had success on:

Ford Falcon ’08, Toyota Aurion ’11, Mazda ute ’11 (all Aussie made or sold)

Also failed to connect on a Toyota corolla ’06 (manufactured in Japan but Australian delivered model).

Having looked at the Blitz r-vit car list (http://www.blitz.co.jp/new-product/r-vit_i-color.pdf) it seems to list all cars it supports and the protocol used. Most just say “toyota” or “subaru” etc hinting they use their own protocols. Whereas some are listed as being ISO or CAN etc etc.

Hey Ian,
Any chance to look at the logs?
requesting permission before i give out the names of the software i have used to connect to JDM cars. They are windows based but have mentioned they will remove an android app in the coming months.

Hi Ian,

I have the Kiwi Bluetooth OBD2 adaptor and works with Torque and I had some success testing with some cars:) I use it with my Samsung Galaxy Tab.

But I tried it with Toyota Fortuner 2008 and Toyota Rav4 2002 and could only connect with the adaptor. Are these cars supported? What to do?

Oh, please advise if this should be another topic 😀

Thanks!
Ogie

ohhhh…

okay, will try to ask the local dealership to confirm. Will keep you posted:)

thanks for the prompt reply!

That’s an OBD2 style connector, but it doesn’t mean that the vehicle is OBD2 compliant – basically OBD2 covers signalling, connectors, and the requests to the ECU for data, a standard requiring a couple of standards

Torque can now talk more than OBD2, so if someone enterprising can document other protocols, I can add support for them (providing there is an interface adapter that supports it)

Nissan have their own protocol, but unfortuantely at the moment it’s not compatible with any of the adapters our there – they aren’t capable of it

If someone makes an adapter that can talk to their proprietary signalling, then it will be possible to add support

Hi!

No, cars destined for the european markets will be OBD2 compliant due to legislation, so a Nissan sold in Europe or the US will be OBD2 compliant, but the same vehicle sold in japans domestic market may not be

If you are in europe or the US and have a nissan within the legeslation date range which is OBD2 compliant, then the app will work with it, so I would expect your Nissan to work as it should be OBD2 compliant.

Usually when it isn’t working it’s down to one of the following problems:

* A faulty adapter (possible if it’s a clone)

* The wrong bluetooth device being selected in the settings. (and a handsfree kit accidentally being selected or something along those lines)

* The protocol being changed from ‘Automatic’ in the vehicle profile settings to something that isn’t the vehicle protocol

* The vehicle not being OBD2 compliant

Re; Toyota Matrix 2005. Hi just wanted to let someone know what worked for me. I bought this adapter (link : http://www.amazon.com/gp/product/B005NLCGF8/ref=cm_cr_rev_prod_title) (for 23 dollars + 10 dollars for shipping) for use with my Toyota Matrix 2005 and an Acer Iconia Tab A100 Android tablet. I live in Canada (which country you live in might make a difference on the OBDII compatibility of your automobile). I wanted to use it with Torque,both the free and paid for versions – great app by the way ! I finally got it working and it works very well. You first have to pair the OBDII adpater with your Android (using 1234). When I first tried using Torque, my Iconia said ”Paired but not connected”. Then I went into the configuration of Torque as follows : when you first open Torque, press the parameters icon (on my Iconia it was the second icon to the right of the Home icon – it looks like a little spreadsheet grid), then press ”Settings” and finally press ”OBD2 Adapter Settings”. I activated the ”Faster communication” parameter and since then has worked well.

The only reason I didn’t give this product (the OBDII adapter) a 5 star rating (afer all, it did work as advertised) was the complete lack of documentation (what do the LED lights mean?) Also, I wish the makers of these adpaters would make it power-down (cut off the power) when the ignition is not on – the adapter will eventually drain your battery if you leave it plugged in. Hope this has been of help.