Page 1 of 1
OBD connection problems
Posted: Sun Oct 04, 2015 3:55 am
by ctsvguy
Hello,
I have a 2009 Cadillac CTS-V and a generic ELM327 bluetooth OBD adapter. I run Android. The OBD adapter works fine when I run torque, but when I try to connect via LapTimer, I do get a connection for about 1-2 minutes and then the connection drops. During the time that the adapter shows to be connected I get a 0 hertz rate for PIDS.
I have read your troubleshooting section and have tried to exclude 09020160010B0105010601100111 PIDs and I still get a 0 hertz rate. I tried to attach the log file to this forum post, but it's 300kb and over the size limit. You can download it here:
http://1drv.ms/1M8tmkD. The log file shows one connection cycle (in the middle of the connection cycle I tried to remove the PID exclusions to see if it made a difference, but it didn't.)
Thank you in advance for your help.
Oleg
Re: OBD connection problems
Posted: Mon Oct 05, 2015 9:27 am
by Harry
It seems you have excluded all PIDs, this makes sure you get 0 Hz
Excluding PIDs should not be necessary at all, it has been a workaround in former LapTimer versions.
I can't access the link, please send the log file to
Harry@gps-laptimer.de and add a link to this thread.
Thx, Harry
Re: OBD connection problems
Posted: Mon Oct 05, 2015 2:48 pm
by ctsvguy
Email sent. The log has two attempts. One with pids excluded and one without any pids excluded.
Thanks.
Oleg
Re: OBD connection problems
Posted: Mon Oct 12, 2015 12:28 pm
by Harry
Hi,
I have checked the logs, it looks like an issue with the OBD adapter's ELM327 compatibility. The adapter does not reset correctly when asked and send random replies it should have sent earlier. This screws up LapTimer's operation and makes it disconnect after some time. Please try one of the compatible devices listed on
http://www.gps-laptimer.de/compatibility/android
It is probably best to lend some adapter from a friend before ordering it.
- Harry
Re: OBD connection problems
Posted: Thu Oct 22, 2015 7:24 pm
by neonal
Hello Harry,
I'm also having problems with my OBDII adapter. It connects but shows no data then disconnects. This process repeats. However after some time (Maybe 5 mins) it connects and shows data but disconnects after 30 seconds. And again it continues to connect-show no data-disconnect loop.
I am attaching the log I collected. Could you please check?
Thanks,
Re: OBD connection problems
Posted: Fri Oct 23, 2015 5:53 pm
by Harry
Which car and which adapter please? Looking into the log it seem the request for PIDs available (0100) is not answered correctly. As the reply is mandatory for LapTimer to work at high speeds, it is requested again later - which fails again and makes LapTimer reconnect:
Code: Select all
28196991370 + 1500ms Tx: "41 54 57 53 0D 'ATWS\r'"
28196991500 + 130ms Rx: "0D 0D 45 4C 4D 33 32 37 20 76 32 2E 31 0D 0D 3E '\r\rELM327 v2.1\r\r>'" (16)
28196991500 Tx: "41 54 45 30 0D 'ATE0\r'"
28196991630 + 130ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
28196991630 Tx: "41 54 4C 30 0D 'ATL0\r'"
28196991770 + 140ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
28196991770 Tx: "41 54 53 30 0D 'ATS0\r'"
28196991900 + 130ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
28196991900 Tx: "41 54 40 31 0D 'AT@1\r'"
28196992040 + 140ms Rx: "4F 42 44 49 49 20 74 6F 20 52 53 32 33 32 20 49 6E 74 65 72 70 72 65 74 65 72 0D 0D 3E 0D 0D 3E 'OBDII to RS232 Interpreter\r\r>\r\r>'" (32)
28196992040 Tx: "41 54 41 54 30 0D 'ATAT0\r'"
28196992040 Tx: "41 54 53 54 46 46 0D 'ATSTFF\r'"
28196992170 + 130ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
28196992170 Tx: "41 54 53 50 41 30 0D 'ATSPA0\r'"
28196992170 Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
28196992170 --------- mode: 1 pid: 0x00 [PID01-20] (index: 12)
28196992170 Tx: "30 31 30 30 0D '0100\r'"
28196997100 + 4930ms Rx: "4F 4B 0D 0D 3E 53 45 41 52 43 48 49 4E 47 2E 2E 2E 0D 'OK\r\r>SEARCHING...\r'" (18)
28196997120 + 20ms Rx: "34 31 30 30 42 45 33 46 41 38 31 33 0D 31 3A 20 30 36 34 31 30 30 39 38 31 38 38 30 31 31 0D '4100BE3FA813\r1: 06410098188011\r'" (31)
28196997130 + 10ms Rx: "0D 3E '\r>'" (2)
28196997130 --------- mode: 1 pid: 0x20 [PID21-40] (index: 13)
28196997130 Tx: "30 31 32 30 0D '0120\r'"
28196997150 + 20ms --------- mode: 1 pid: 0x0C [RPM] (index: 28)
28196997150 Tx: "30 31 30 43 0D '010C\r'"
28196997230 + 80ms Rx: "34 31 32 30 41 30 30 37 42 30 31 31 0D '4120A007B011\r'" (13)
28196997240 + 10ms Rx: "0D 3E '\r>'" (2)
28196997240 --------- mode: 1 pid: 0x11 [TPS] (index: 29)
28196997240 Tx: "30 31 31 31 0D '0111\r'"
28196997300 + 60ms Rx: "34 31 30 43 30 45 46 41 0D '410C0EFA\r'" (9)
28196997300 Rx: "0D 0D 3E '\r\r>'" (3)
28196997300 --------- mode: 1 pid: 0x0B [MAP] (index: 30)
28196997310 + 10ms Tx: "30 31 30 42 0D '010B\r'"
28196997390 + 80ms Rx: "34 31 31 31 32 39 0D 0D 3E '411129\r\r>'" (9)
- Harry
Re: OBD connection problems
Posted: Fri Oct 23, 2015 6:38 pm
by neonal
Hi Harry,
I have 2nd generation 2010 Mini Cooper S and I use a generic OBDII adapter.
Re: OBD connection problems
Posted: Fri Oct 23, 2015 7:00 pm
by Harry
Please check if you have someone around with a different adapter. This type of problems without a genuine adapter is difficult to fix.
- Harry
Re: OBD connection problems
Posted: Fri Oct 23, 2015 7:47 pm
by neonal
Thank you Harry, I'll try to find that. In the mean time is there any way to increase some timeout or disable a PID to make it somehow work? It would be great since I have track day this weekend.
Re: OBD connection problems
Posted: Fri Oct 23, 2015 7:53 pm
by Harry
LapTimer needs to know which PIDs are actually available. Otherwise it requests everything it knows about - which generates timeouts all the time. So no, I do not see a quick fix.
- Harry