Forums
Forums
Notifications
Clear all
Topic starter
Hi there,
Using the latest free version – 1.1.26 with a ELM327 via Bluetooth in a Samsung Galaxy S updated to Froyo.
I already ordered two of these from eBay - one with 1.2 version and the new one on this log with 1.4 version but both are failing to talk to the ECU.
I am trying to talk to an Opel Vectra B 2.5V6 from year 2000 which I am told uses the ISO 14230-4 protocol.
I can pair with Bluetooth interface with no problems but there is no way I can talk to the ECU - it always fails to determine the protocol 🙁
Any help welcome cause I really want to get this to work - You have a client in me if it supports my configuration and I will provide any information you need.
Thank you in advance for your help! 🙂
Best regards,
J
Device Info:
---------------
Brand: samsung
Board: GT-I9000
Device: GT-I9000
Build id: samsung/GT-I9000/GT-I9000/GT-I9000:2.2/FROYO/XWJPA:user/release-keys
Model: GT-I9000
Product: GT-I9000
Tags: release-keys
Type: user
Id: FROYO
Version: 2.2
SDK: 8
UserBuildId: FROYO
Application version: 1.1.26
Fast mode: false
Disable Speed adaption: false
1289326805628 **** Connect requested, commsThread=null ****
1289326805639 **** OBD Comms thread starting ****
1289326805642 **** Connecting to OBD via bluetooth ****
1289326805650 **** Connecting to OBD via bluetooth... ****
1289326805650 **** Connecting to: 00:0D:18:B2:7C:03 ****
1289326806663 **** Standard bluetooth API connect ****
1289326812592 **** Connected to OBD interface, configuring ****
1289326812593 **** Sending reset sequence ****
1289326812622 --> ELM327 v1.4
1289326812693 ATD
1289326812748 --> +OK
1289326812955 ATZ
1289326813808 --> +ELM327 v1.4
1289326815460 ATE0
1289326815541 --> +OK
1289326815549 OK
1289326815625 OK
1289326815672 OK
1289326815828 OK
1289326815874 OK
1289326816161 **** Sending reset sequence ****
1289326816262 OK
1289326816520 ATZ
1289326817392 --> +ELM327 v1.4
1289326819032 ATE0
1289326819076 --> +OK
1289326819091 OK
1289326819180 OK
1289326819247 OK
1289326819427 OK
1289326819505 OK
1289326819769 OK
1289326819868 SEARCHING...
1289326825191 --> +UNABLE TO CONNECT
1289326825216 **** Protocol 0 was not successful ****
1289326825217 **** Sending reset sequence ****
1289326825317 OK
1289326825572 ATZ
1289326826423 --> +ELM327 v1.4
1289326828080 ATE0
1289326828128 --> +OK
1289326828136 OK
1289326828216 OK
1289326828273 OK
1289326828460 OK
1289326828527 OK
1289326828813 OK
1289326828909 NO DATA
1289326829074 **** Protocol 1 was not successful ****
1289326829074 **** Sending reset sequence ****
1289326829175 OK
1289326829436 ATZ
1289326830305 --> +ELM327 v1.4
1289326831951 ATE0
1289326832014 --> +OK
1289326832020 OK
1289326832098 OK
1289326832161 OK
1289326832329 OK
1289326832419 OK
1289326832710 OK
1289326832807 CAN ERROR
1289326832915 **** Protocol 6 was not successful ****
1289326832915 **** Sending reset sequence ****
1289326833015 OK
1289326833268 ATZ
1289326834120 --> +ELM327 v1.4
1289326835773 ATE0
1289326835814 --> +OK
1289326835817 OK
1289326835864 OK
1289326835908 OK
1289326836061 OK
1289326836144 OK
1289326836399 ?
1289326836477 +OK
1289326850771 OK
1289326850849 OK
1289326850908 OK
1289326851064 OK
1289326851110 OK
1289326851408 OK
1289326851525 NO DATA
1289326851684 **** Protocol 2 was not successful ****
1289326851684 **** Sending reset sequence ****
1289326851786 OK
1289326852045 ATZ
1289326852899 --> +ELM327 v1.4
1289326854551 ATE0
1289326854601 --> +OK
1289326854609 OK
1289326854682 OK
1289326854759 OK
1289326854952 OK
1289326855017 OK
1289326855298 OK
1289326855433 BUS INIT: ...ERROR
1289326858325 **** Protocol 4 was not successful ****
1289326858325 **** Sending reset sequence ****
1289326858426 OK
1289326858690 ATZ
1289326859543 --> +ELM327 v1.4
1289326861201 ATE0
1289326861245 --> +OK
1289326861246 OK
1289326861294 OK
1289326861363 OK
1289326861536 OK
1289326861599 OK
1289326861857 ?
1289326861930 ?
1289326861977 OK
1289326862050 BUS INIT: ERROR
1289326862985 **** Protocol 5 was not successful ****
1289326862985 **** Sending reset sequence ****
1289326863085 OK
1289326863339 ATZ
1289326864195 --> +ELM327 v1.4
1289326865855 ATE0
1289326865893 --> +OK
1289326865904 OK
1289326865950 OK
1289326866035 OK
1289326866194 OK
1289326866272 OK
1289326866565 OK
1289326866659 CAN ERROR
1289326866762 **** Protocol 8 was not successful ****
1289326866762 **** Sending reset sequence ****
1289326866862 OK
1289326867118 ATZ
1289326867983 --> +ELM327 v1.4
1289326869627 ATE0
1289326869666 --> +OK
1289326869672 OK
1289326869718 OK
1289326869763 OK
1289326869911 OK
1289326869980 OK
1289326870237 OK
1289326870329 CAN ERROR
1289326870433 **** Protocol 7 was not successful ****
1289326870433 **** Sending reset sequence ****
1289326870533 OK
1289326870786 ATZ
1289326871650 --> +ELM327 v1.4
1289326873289 ATE0
1289326873331 --> +OK
1289326873337 OK
1289326873415 OK
1289326873465 OK
1289326873613 OK
1289326873660 OK
1289326873932 OK
1289326874037 CAN ERROR
1289326874141 **** Protocol 9 was not successful ****
1289326874141 **** Sending reset sequence ****
1289326874241 OK
1289326874495 ATZ
1289326875358 --> +ELM327 v1.4
1289326877002 ATE0
1289326877096 --> +OK
1289326877101 OK
1289326877158 OK
1289326877219 OK
1289326877366 OK
1289326877414 OK
1289326877681 OK
1289326877763 SEARCHING...
1289326883052 --> +UNABLE TO CONNECT
1289326883055 **** Protocol 0 was not successful ****
1289326883055 **** Sending reset sequence ****
1289326883155 OK
1289326883413 ATZ
1289326884298 --> +ELM327 v1.4
1289326885919 ATE0
1289326885960 --> +OK
1289326885967 OK
1289326886074 OK
1289326886130 OK
1289326886275 OK
1289326886319 OK
1289326886565 OK
1289326886672 BUS INIT: ...ERROR
1289326889542 **** Protocol 3 was not successful ****
1289326889542 **** Sending reset sequence ****
1289326889643 OK
1289326889897 ATZ
1289326890749 --> +ELM327 v1.4
1289326892401 ATE0
1289326892456 --> +OK
1289326892460 OK
1289326892516 OK
1289326892572 OK
1289326892717 OK
1289326892776 OK
1289326893037 OK
1289326893115
Posted : 09/11/2010 7:25 pm
I used to have this same issue with an old code reader I had. The issue ended up being some old dirt/grit/grease that ended up in the ODB port from a previous reading. Try spraying some electronics cleaner in the port followed up by some canned air. That should verify there isn't anything in there fowling up the connection.
Posted : 09/11/2010 10:44 pm
Same problem...
I have a Vectra B 2.0i 1998, and the same odb2 reader, but the lastest torque app dont see the ecu.
Is there any solution for this problem?
Posted : 21/02/2012 6:57 pm
Hi
You need to make sure the vehicle is OBD2 complaint (just having the correct shaped connector doesn't automatically mean it's compliant)
From the debug in the first post, the adapter isn't able to find a protocol to talk to the ECU. At each stage the adapter says it's unable to connect (or for the other protocols, unable to understand the response)
It matters what country you are in. If you are in the EU/US, then petrol vehicles should be OBD2 compliant from 1996 onwards (with diesels being compliant from 2004 onwards, though some manufacturers implemented support before these dates). Other countries such as japan don't have the same legeslation regarding OBD2 so you may find it's not implemented in vehicles that are destined to be sold in that particular country
It could also be the adapter, if it's a clone. Some adapters don't work on certain protocols (but work ok on others) - the most notable of these are the J1850-PWM protocol that some Fords use being faulty on some of the clone adapters (as well as some other clones having issues with CANBUS protocols (due to lack of termination resistors))
If the vehicle is OBD2 compliant, then Torque should definitely work with it. If it's not OBD2 compliant, and you have the correct bluetooth device selected in the settings (and the protocol set to 'automatic' in the vehicle profile in the pro version) then it may well be an adapter issue
Hope this helps!
Posted : 21/02/2012 8:49 pm
Thx your reply.
This vectra is petrol, and its securely have obd 2 (and Hungaryan - EU)
The device is an ELM327 type.
When i tested with this, i dont have any profile in turque app, it just a simple virgin app.
In truth, today i bought the turque app, and i wanted to buy the odb 2 device (elm327). In the shop, the guy istalled the device, started the car, paired the BT and started the app. The app was find the devcie, but not the ecu. As i say, that app was a non profilled app, but the guy had it a year ago to test the cars before he sell the BT devicees, so it was worked with other cars.
So, if i go back to this guy with my mobile, and i create a profile with auto protocol scan, maybe it will work for me? Or when i have no profile, the app set automaticly to auto protocol scan?
Or look for another BT odb2 reader device? Witch offer you?
(sorry for the bad english, i hope you understand what i want to say 🙂 )
Posted : 21/02/2012 9:23 pm
