[HOWTO] Debugging OBD Communication

Collection of all FAQs and HOW-TOs posted throughout the system. Read only.
User avatar
Harry
Site Admin
Site Admin
Posts: 8009
Joined: Sun Sep 12, 2010 10:32 am
Location: Cologne, Germany
Has thanked: 93 times
Been thanked: 334 times
Contact:

Re: [HOWTO] Debugging OBD Communication

Postby Harry » Sat Feb 14, 2015 9:17 am

To delete a sensor not longer used from LapTimer Android's Sensor List, long-press the sensor row and use the action menu to delete. There are always two steps included when adding BT sensors to LapTimer: a) pair the device on BT level (Android Settings) and b) add it to the Sensor List. As long as it connects for a seconds and falls back to 0 / disconnects afterwards, there is a problem with what your cars answers on OBD request. Please follow the instructions in the first post to create a log and send it to me.

- Harry


Image Image Image Image
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Sun Feb 15, 2015 4:48 am

Harry wrote:To delete a sensor not longer used from LapTimer Android's Sensor List, long-press the sensor row and use the action menu to delete. There are always two steps included when adding BT sensors to LapTimer: a) pair the device on BT level (Android Settings) and b) add it to the Sensor List. As long as it connects for a seconds and falls back to 0 / disconnects afterwards, there is a problem with what your cars answers on OBD request. Please follow the instructions in the first post to create a log and send it to me.

- Harry



It only connects for a split second, can I do a log based on that?


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2
User avatar
Harry
Site Admin
Site Admin
Posts: 8009
Joined: Sun Sep 12, 2010 10:32 am
Location: Cologne, Germany
Has thanked: 93 times
Been thanked: 334 times
Contact:

Re: [HOWTO] Debugging OBD Communication

Postby Harry » Sun Feb 15, 2015 8:19 am

Yes, when it connects in Sensor List - even shortly - there is communication.


Image Image Image Image
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Mon Feb 16, 2015 2:41 am

Harry wrote:Yes, when it connects in Sensor List - even shortly - there is communication.

OK will try to do it.

:)


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Sun Feb 22, 2015 2:12 am

Per your request I have sent by email two log files regarding the scantool obd2 mx bt not connecting to hlt.

The first log file is with just the obd2.

The second file is with the Dual 160 bt connected.

I did note a connect with the first file (don't know if it disconnected)

The second file should show a connect and a disconnect once or more.

Something in the process also caused my dash clock to reset from correct time to 1:00.

There is NO PROBLEM with the car battery or clock, this never happens unless I am trying to use HLT and sensors. I recall last time I tried using HLT the clock also reset for no good reason.

IF the first log shows a steady connect and the second a connect/disconnect I suspect it has something to do with the Dual GPS and OBD2 not playing together well on android platform, but that's just an uninformed guess on my part.

The clock thing I don't know?

Let me know if you need more, as of now it's all useless, not working, in spite of using the "preferred" Dual and Scan Tool sensors.


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2
User avatar
Harry
Site Admin
Site Admin
Posts: 8009
Joined: Sun Sep 12, 2010 10:32 am
Location: Cologne, Germany
Has thanked: 93 times
Been thanked: 334 times
Contact:

Re: [HOWTO] Debugging OBD Communication

Postby Harry » Sun Feb 22, 2015 10:45 pm

Hi Froggy,

Thanks for sending the logs. I have no easy to exercise solution but some observations. I append samples to allow OBDLink support to have a look into the pattern.

Log1: adapter connects successfully in the beginning, negotiates a protocol with the car bus (see initial part of the below sample), and shows no disconnects; answering times vary a lot more than they actually should (check the second part of the below sample - VSS is answered within 40ms one time and requires 200ms another time); this is a sign either the smartphone is "overloaded" or there is some RF source in your car disturbing the connection; the later are usually some in car stereo or hands free audio Bluetooth devices - try to disable everything that may disturb; anyway, the connection works here - even if it could get a little faster. In general, your 2004 Corvette - with no CAN bus - will hardly go beyond 2 or 3 Hz update rates - even with the very fast OBDLink MX.

Code: Select all

07226186410 +   10ms Tx: "41 54 53 50 41 30 0D 'ATSPA0\r'"
07226186550 +  140ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
07226186550          ---------  mode: 1 pid: 0x00 [PID01-20] (index: 10)
07226186550          Tx: "30 31 30 30 0D '0100\r'"
07226186650 +  100ms Rx: "53 45 41 52 43 48 49 4E 47 2E 2E 2E 0D 'SEARCHING...\r'" (13)
07226188160 + 1510ms Rx: "34 31 30 30 42 46 42 46 46 39 39 30 0D '4100BFBFF990\r'" (13)
07226189120 +  960ms Rx: "0D 3E '\r>'" (2)

...

07226260430          ---------  mode: 1 pid: 0x0D [VSS] (index: 29)
07226260430          Tx: "30 31 30 44 20 31 0D '010D 1\r'"
07226260460 +   30ms Rx: "34 31 '41'" (2)
07226260470 +   10ms Rx: "30 44 30 30 0D 0D 3E '0D00\r\r>'" (7)
07226260480 +   10ms ---------  mode: 1 pid: 0x0C [RPM] (index: 26)
07226260480          Tx: "30 31 30 43 20 31 0D '010C 1\r'"
07226260600 +  120ms Rx: "34 31 30 43 30 30 30 30 0D 0D 3E '410C0000\r\r>'" (11)
07226260600          ---------  mode: 1 pid: 0x11 [TPS] (index: 27)
07226260610 +   10ms Tx: "30 31 31 31 20 31 0D '0111 1\r'"
07226260710 +  100ms Rx: "34 31 31 31 32 35 0D 0D 3E '411125\r\r>'" (9)
07226260720 +   10ms ---------  mode: 1 pid: 0x0B [MAP] (index: 28)
07226260720          Tx: "30 31 30 42 20 31 0D '010B 1\r'"
07226260750 +   30ms Rx: "34 31 30 42 36 35 0D 0D 3E '410B65\r\r>'" (9)
07226260750          ---------  mode: 1 pid: 0x0D [VSS] (index: 29)
07226260750          Tx: "30 31 30 44 20 31 0D '010D 1\r'"
07226260950 +  200ms Rx: "34 31 30 44 30 30 0D 0D 3E '410D00\r\r>'" (9)


Log2: adapter connects successfully again, but the adapter fails to negotiate the correct bus protocol with your car; I cannot think of a reason this should be related to other BT devices (or the XGPS) - they are not involved at this time; during the initially requests, the adapter simply tries to negotiate and is coming back after around 5 seconds with "UNABLE TO CONNECT". LapTimer has no bus protocol detection build in to support the adapter during this negotiation; instead it sets automatic detection and lets the adapter do the job. What you can try is checking for the protocol implemented for your car using OBDLink's app and set LapTimer's Expert Setting "OBD Tweaks / Default Protocol" to this bus type; this in turn can help during the initial negotiation.

Code: Select all

07227044700          Tx: "41 54 53 50 41 30 0D 'ATSPA0\r'"
07227044710 +   10ms Rx: "4F 4B 0D 0D 3E 'OK\r\r>'" (5)
07227044710          ---------  mode: 1 pid: 0x00 [PID01-20] (index: 10)
07227044710          Tx: "30 31 30 30 0D '0100\r'"
07227044720 +   10ms Rx: "53 45 41 52 43 48 49 4E 47 2E 2E 2E 0D 'SEARCHING...\r'" (13)
07227049240 + 4520ms Rx: "55 4E 41 42 4C 45 20 54 4F 20 43 4F 4E 4E 45 43 54 0D 0D 3E 'UNABLE TO CONNECT\r\r>'" (20)


I cannot comment on the "caused my dash clock to reset" effect. To me it sounds like some problem with the car bus and should not happen for a proper OBD gateway implementation; in case you want to analyze this part, I need to forward you to OBDLink's support. LapTimer does not submit any write operation and requests PIDs only.

Maybe you want to revalidate the connection making is really related to the use of XGPS in parallel.

- Harry


Image Image Image Image
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Mon Feb 23, 2015 4:37 am

Thanks Harry.

For log 1, there is zero BT in a 2004 z06, the stereo was off and it's a very simple basic stereo, it does not even have a mini jack for an ipod & no satellite radio, all wiring is stock, the 2004 z06 was built to be a decent track car minimum luxury. Not sure what you mean by overloaded cell phone, I do have some apps that run, but turn off the battery saver & screen saver stuff as I thought (previous HLT questions) that they might interfere with HLT.

For log 2, again my uninformed GUESS is that the Dual 160 and ScanTool mx bt are being difficult with each other. I'll try that expert setting & run with the dual & scantool again but I really don't have the appropriate level of understanding to deal with this nor do I really want to.

Do you want another log after I ck the expert setting and attempt to get them both connected at the same time?

So is Scan Tool going to try something and contact you or me?

:)


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2
User avatar
Harry
Site Admin
Site Admin
Posts: 8009
Joined: Sun Sep 12, 2010 10:32 am
Location: Cologne, Germany
Has thanked: 93 times
Been thanked: 334 times
Contact:

Re: [HOWTO] Debugging OBD Communication

Postby Harry » Mon Feb 23, 2015 8:07 am

The log1 item is nothing too critical - maybe it is at it is for the z06... The missing connection to the car bus in log2 is not related to XGPS160 and OBDLink, it is adapter / bus negotiation. I have sent OBDLink support a pointer to my above reply.

Harry


Image Image Image Image
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Wed Feb 25, 2015 1:10 am

The Scantool obd2 helper on the forum suggested setting protocols the same.

The choices I have on the scantool are automatic, 3 sae, 7 iso, 2 user can,


He did not say which one to pick, it's (obd2) on automatic now.

He did not seem to know that protocol was under communications on his menu, he thought it was under information?

Can you help?


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2
froggy47
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 129
Joined: Tue Feb 25, 2014 2:20 am

Re: [HOWTO] Debugging OBD Communication

Postby froggy47 » Wed Feb 25, 2015 1:12 am

HLT seems to have the same or similar list of protocols, so I don't know which one to pick, the obd2 software & hlt are both automatic now.

In a few days I will need to return the scantool device to Amazon as it's not much good unless it connects to hlt.

What protocol does the Dual 160 run on?

:)


Autox & HPDE
2004 Corvette Z06
Moto X/android, Dual 160, generic OBD2

Return to “FAQs and HOW-TOs”

Who is online

Users browsing this forum: No registered users and 1 guest