Forums
Forums
Notifications
Clear all
Topic starter
Hello,
I bought this program two months ago, but since then it has Neh it almost did not work.
Car - Kia Sorento 2003, diesel
Adapter - ELM327 v 1.5
Phone - Samsung Galaxy Note, with android 4.04.
I'm including a program on the phone, waiting for a while, see how the program connects to one system car, adapter and telephone.
The program says that the connection is established. All united. But ...
But nothing works. In scales dashboards do not have green dots. The green dot is only in the scale of the accelerometer, but the accelerometer is not information from the car, and part of the phone. No information from the car did not seem to come!
I am attaching screenshots. They are in Russian, but there it is evident that all the connections are, and there is no measurement
About once every few tens of inclusions miracle happens - proramme starts! But it happens very, very rarely.
What to do in this situation? How to fix it?
Thanks in advance for your help
Posted : 19/05/2013 8:39 am
I can be caused by wrong protocol recognition.
Try another app. "Efficiency" or "OBD Dashboard" - they work fine on my 2005 Sorento (and Vgate bluetooth blue dongle) while Torque does not (connection ok but no real time readings)
OBD Dashbord reports ISO 9141 after connection while Torqe tries ISO14230 probably
Posted : 03/01/2014 2:18 pm
Looking online, it looks like the Kia Sorento TD 2003 - 2007 is ISO 9141. In Vehicle Profile, set to that protocol and try it out.
Automatic scan is a feature of the OBDII dongle, and doesn't always work correctly.
Posted : 03/01/2014 4:55 pm
Is the vehicle fully obdii compliant since its a
diesel pre 2004... it may not be?
Posted : 03/01/2014 6:06 pm
There are vehicles out there that support OBD2 on 2 different protocols (though they are rare, I've seen nissans with ISO support for 9141 and canbus in the same car, on 2 seperate ECUs - very odd!)
Yes - the adpaters scan for the correct protocol in their 'auto detection', and if there's more than one protocol in use (which is definately very uncommon) then it can choose the wrong one
If you set the protocol to the other one, you may well then get a connection
Posted : 04/01/2014 8:38 am
I have a similar problem on a 2005 Kia Sorento CRDI (VGT). Profile vehicle set up for technical data. Connected via ISO 9141. Connection itself is fast and almost all the sensors are working properly (temperature, tachometer, MAF, etc.), except for the speed sensor (speed readings from the ECU ). On the dashboard speed sensor constantly flashes green and shows 0 km/h, although the list of active sensor speed sensor listed as available. Accordingly, the sensors are not working and calculating the fuel consumption.
This is a problem in the program or in the adapter? There is what that solution to the problem?
Thanks for the help.
Posted : 12/02/2014 5:34 am
I have a similar problem. The adapter and the phone pair successfully but the app says it cannot talk to the ECU. The vehicle is a 2002 Nissan almera QG15de engine. Can any help.
Posted : 26/08/2014 5:39 pm
