Torque Pro’s fault scan is failing to report any DTC history that was stored on my 2005 Prius. This is with a Bluetooth ELM327 clone adapter for which Torque has accumulated zero errors/faults.

I have additional information that might help debugging, but wanted to find out: What would be most helpful?

Also, how do I get application debug logs? I found an old posting on turning on debugging through the “Realtime Information” menu, but I didn’t see any debug logs below there on the version of Torque I’m running (v1.8.81).

< Lionel

After taking your clue that the instructions I read to turn on debugging were incomplete, I did gather and submit the app’s logs to demonstrate the problem. No response as yet.

Although I did find one similar-looking problem report ([no default or history dtcs][http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3968.0]), one chief difference is that these are DTCs that Torque displayed when they were active or pending.

I wonder who else is effected by this problem. People may not know they’re being affected if they didn’t know that the DTCs had been set previously. I had been using Torque Pro for quite a while before I noticed the problem.

Hi!

Torque already has the functionality to read all the trouble codes from the vehicle including historic and does this automatically in the fault code reporting for you when you scan for faults. It retrieves any fault that was or is current(etc) in the ECU

If it’s not showing up, then it means one of two things:

* You’re using one of the bugged Chinese clone adapters that don’t work properly on CANBUS protocols (they can prevent some faults from being read)

* There’s no fault history stored in the OBD2 fault logs on the ECU and they have been cleared, or have expired as part of several driving cycles

Hi

Yes.

Debug logs are sent direct to me from the app – enable debugging in the general settings, then restart the app. Connect, run the fault code request, then go to the realtime data screen, menu, send debug log and put your forum name in the dialog box so I can find you. I’ll have a look and post it’s response to confirm what’s going on

I’m checking back to find out what the logs showed.

I most recently submitted logs taken with a ScanTool adapter, demonstrating that this isn’t a “cheap clone” problem.

Also, Torque has been failing to show history even when factory-type tools were showing previously-current codes known to be in the history (e.g., several in the P3000s, B1826, et al.).

Hi

Got the latest debugs, thanks

From your debugs:

1461293423319 {-- 03 (current request)
1461293423422 --}  4300
1461293423423 --} +4300   -- nothing in the log. P0A80
1461293423423 --} +4300   
1461293423812 {-- 07  (pending request)
1461293423917 --}  4700
1461293423918 --} +47010A80   -- there's one pending code
Pending fault code found: P0a80
1461293423918 --} +4700
1461293423918 {-- 0A  (historic request)
1461293424039 --}  7F0A11
1461293424039 --} +7F0A11
1461293424039 --} +7F0A11     -- 7F is a negative reply to the request.

There was one code, but it was not historic, it was a pending code. There was nothing in the historic log – all the ecu’s replied with 7F reponses.

Bear in mind that historic codes do automatically clear themselves from the log after a number of driving cycles have been completed with no further problems. The same goes for pending codes.

Those look like manufacturer specific
codes that are beyond the legislated
emissions and generic DTCs.

B1xxx.

I believe your TechStream was using manufacturer
specific commands to return the DTCs by status
and function.

Beyond the modes previously mentioned.

https://torque-bhp.com/forums/?wpforumaction=viewtopic&t=4553.0