Hi,
I’m new to Torque and must say that I really appreciate the app and the work the developer put into this. Thank you!

But unfortunately I discovered a problem: The main reason for me to buy Torque was to be able to read the DPF clogging status from the ECU of my Alfa Romeo 159 2.4 JTDM. I already know the correct header and the pid for this command.

When I connect to the ECU using PuTTY, i can get the DPF state using the following commands:

ATZ
ATSP5
ATSH8110F1
ATFI
21CD

This works perfectly fine.

Torque can connect to my ECU using the ISO 14230-4 protocol without any sign of problems. It reads many values from the ECU that show it’s working.
But when I enter the 21CD PID with 8110F1 header as custom PID, I only receive the 7F2111 message.

I already tried to set the header using the ATSH command in the custom init string with the result that torque can’t connect to my ECU anymore. I have to enter the ATZ and ATFI commands as well to make Torque connect again.

But this still doesn’t make the 21CD custom PID work. I either get the 7F message or no return value at all.

I discovered that the 21CD PID works fine with Torque after I connected to the ECU using AlfaOBD without turning off the ignition. This and the fact that i can read the 21CD PID from my laptop lead me to the conclusion that it’s merely an initialization problem…

Can anyone help me on this? Will it help to provide debug information?
Is there any way to see the commands Torque is sending to the OBD interface and the corresponding return values?

Kind regards
Norbert

Already tried this one. The connection string works, the custom PID doesn’t.

Have you tried leaving the header
blank or Auto?

There are others more versed in
custom init strings so hopefully
they will step in.

You might try reading thru the links
in the thread link I posted above in
the slim possibility that more info
can be found.

I think I have to make clear that Torque DOES connect to the ECU. Many of the pre-configured PIDs can be read.

My only problem is that I get the return value 7F2111 for my custom PID which afaik means something like “service 21 not available”

But I can perfectly read the PID using PuTTY.
And I can also read the PID using Torque AFTER I connected to the ECU using AlfaOBD

ok, i tried 8301, 1A97 and 2180 first. The reply for 21CD (which I’m pretty sure is the correct PID for the DPF clogging) works as expected.

>atz
OK

>atsp5
OK

>atsh8110f1
OK

>atfi
BUS INIT: OK

>8301
C3 01

>1a97
5A 97 FD 86 BF 04 9B

>2180
7F 21 12

>21cd
61 CD 16 A6

Then I tried your second recommendation:

>atz
OK

>ath1
OK

>atsp5
OK

>atsh8110f1
OK

>1a97
BUS INIT: OK
5A 97 FD 86 BF 04 9B

>2180
7F 21 12

>21ca8001
7F 21 12

>atsh8010f1
OK

>1a97
5A 97 FD 86 BF 04 9B

>2180
7F 21 12

As you can see, the 2180 and 21CA8001 return error messages.

I’ll try the two additional headers you mentioned, but I’m not very confident that they’ll do the job.

Based on your answers, I now try to see

Could this be a tester present or diagnostics
enable issue like Jeep TFT pids?

Just thinking out loud…

You were right, i must have forgotten the ATH1 command.

Here are the correct response messages:

>ath1
OK

>atsp5
OK

>atsh8110f1
OK

>1a97
BUS INIT: OK
87 F1 10 5A 97 FD 86 BF 04 9B 5A

>2180
83 F1 10 7F 21 12 36

>21ca8001
83 F1 10 7F 21 12 36

>atsh8010f1
OK

>1a97
80 F1 10 07 5A 97 FD 86 BF 04 9B 5A

>2180
80 F1 10 03 7F 21 12 36

Had to change the custom init string to start with ATZ in order for it to work.
The response of the custom PID is still 7f2111

Changed the car profile to use the alternative OBD header, but no difference. I’m still getting the 7f2111 response.