I’m having some trouble connecting to my new to me WRX. I’ve used this combo successfully on my 1999 Chevrolet K2500 as well as the 1999 Subaru Legacy I used to own, so I feel somewhat confident that it should work.

I am able to connect via bluetooth to the OBD, but am unable to make a connection to the ECU (using the thorough protocol scan).

At this point, I’m a little uncertain of how to troubleshoot. Is there a guide I can follow to start to troubleshoot/pinpoint what my issue might be?

Thank you,

Greg

EDIT: I’m using my wife’s old HTC One which I updated to the newest available software. My TorquePro is up to date and my Kiwi3 has the newest firmware.

Thanks for the help.

I just tried deleting all my vehicle profiles.

With the car off, I am able to make a bluetooth connection to my Kiwi device. When I turn the ignition on, TorquePro begins to do the automatic protocol search. After a period of time, the app will ask me if the ignition is on (yes it is). I’ve given it a long period of time to connect as well (I’ve driven around for 20 minutes).

What would be the next step in the troubleshooting process? I’m fairly certain the Kiwi device is OK since it works on a different vehicle.

Thank you!

here’s a picture of the status screen:

My vehicle is a 2016 Subaru WRX. I couldn’t find the protocol via google. There isn’t some sort of website database is there?

Thanks!

Hi!

If the adapter can’t find the vehicle profile, then it’s going to be one of the following:

* The vehicle does not support proper OBD2 (This is highly, highly unlikely given that every manufacturer supports OBD2 nowdays). The only caveat is if the vehicle is a JDM import where the legislation (is/was) slightly different, but in most cases should still ‘just work’

* That there’s a problem with the adapter on the protocol the vehicle uses causing it to not see the vehicle ECU – this is usually unlikely for things like the scantool and kiwi adapters given their better testing after being built at the factory

* A possible problem with the connector (damage, bent pins, etc) which could be the issue – worth having a visual inspection of the socket in the vehicle itself (and checking the adapter is seated correctly when connected)

* The ECU diagnostic harness is damaged in someway to make it non-functional, or the ECU itself is damaged – this is usually never going to happen so probably isn’t worth worrying about unless the ECU/harness has been in bits at some stage

It’s usually one of the top 2 that’s the culprit – the vehicle /should/ be using some variant of CANBUS given all the manufacturers moved to it around 2007, though with the adapter set to ‘Automatic – Fast’ in the vehicle profile, it should locate the correct protocol itself without any prodding from the app

I was having a communication problem with my 2015 Subaru Outback. Someone on a Subaru forum suggested that I change the comm protocol from “auto” to “ISO 15765-4 CAN, 11 bit ID, 500 Kbaud”. I did that and it cleared up the comm problem.

Hi all,

Back again. I took my car to the Subaru dealer just to have them hook the scanner up. All is well with the OBD port on the car itself.

I had a bunch of back and forth with the Kiwi3 folks. They ended up saying this:

Looks to be some type of CAN / ISO protocol. But pin 8 being occupied changes things up. With standard OBD2 protocols you hardly see pin 8 being occupied. This maybe something specific to your Subaru model and may cause an issue with the ELM chipset for connecting to the OBD2 protocol command and the apps that identify with it.

Does this mean the issue lies with the Kiwi itself?