Quote from Capp777 on May 10, 2017

Still curious if you tried what I suggested in
previous post…

ATH0
ATCAF1

It looks to me that Torque is parsing the
format shown on page [1] but not yours.
The message data looks similar for both
of you.

Based upon my readings CAN Auto formating
uses the x: layout.

I believe…

You are talking to the vehicle with the correct
protocol and baud rate, you are getting a proper
response from your desired pid, the layout presented
back seems to be the source of the Torque parsing
issue.

Torque has a history of not reading some users
CAN 29 Bit protocols but has worked for others
like the OP. I’m starting to believe its related to
how the CAN Auto Formating is set and the way
the multiframe data is presented to Torque.

My two cents and as always could be wrong.

I believe what you are describing is what I am seeing as well. How do I try out the ATH0 ATCAF1? I couldn’t find any settings for it in the app and searching didn’t turn anything up either. I did try other CAN protocols just to see if anything other than the CAN 29/500 by chance worked but none were successful.

Apologies for missing the previous comments on ELM 327. Looks like those comments were added after I initially read the post and I hadn’t gone back to re-read it.

I tried adding a gauge while using the initialization string atsp7\natshda1df1 and that didn’t change things, still was at -41.8. I then tried with ath0 and it worked! For reference I also tried ATCAF1 but that didn’t work either. I let it run this morning and everything looked good for a 30 minute drive! Back to using the original setup with AA.

Thanks for all the help getting this working!

I know this is an old thread but I have a 2006 Honda Odyssey EX-L and 222201 says no response Ive tried the atho odb header and the others listed and I just get response none. I seen something about creating a new device to go with the custom pid but I really dont understand where to do that unless its adding a display item.

Quote from Capp777 on May 11, 2017
Thanks for the update. The Headers ON
setting interferes with the CAN Auto Formating
according to my reading. Now we know how
to help others with the CAN 29 Bit issues in
the future.

Hopefully one day Torque will be able to parse
correctly with Headers ON or OFF.

Thanks Again!

Edited.

I have the same issue as Hawke, I either get -40F or 459400 something
I tried the ath0 or ATH0 , ATCAF1, and atsp7\natshda1df1

Under vehicle profile am I supposed to check the box for use alternate OBD header?

I feel like I’m not resetting something correctly because no matter which string I use it still give the same result.
When changing the custom string which is the correct way to reset?
Unplug from vehicle? Quit torque app? Remove gauge from app display?

Quote from Capp777 on July 4, 2020

I suggest testing the pid to see its raw
hex response. (Assuming this is the correct
pid for your vehicle).

Result -40
Command 222201
Response 027
0:6222201FFFFFF

I have a 2012 Odyssey EXL w 5 speed tranny

Using torque with a Bluetooth elm327, car sitting all day in 90 deg weather, cat temps 116deg , coolant temp 115 deg F which sound correct so I think the adapter is working correctly.

Under custom PID I don’t see an option to “override PID” anywhere

Diagnostic stop command is the last line

Quote from Capp777 on July 5, 2020
Your response reports 0x27 bytes of data
whereas you posted only one line. I am
wondering if your adapter is reading
correctly?

See page 1 of this thread for an example of
what 0x27 bytes should look like.

0:
1:
2:
3:
4:
5:

Are you using a quality brand adapter?

Are you using the latest version of
Torque Pro from Play store?

I have 2 eBay knockoff elm327 adapters one new and one that is 7 yrs old.

I just tried the old one and it worked immediately (using atsp7\natshda1df1 string) showing a bit over 100F at start up to 174 F after 20 mins of city driving.

So I guess I have a good one and a bad one