Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Torque Initallization Problems / Problems reading custom PIDs

Pages: 1 [2]
Author Topic: Torque Initallization Problems / Problems reading custom PIDs
nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 9, 2016 (GMT)

The car profile as you suggested:

The custom PID:

An additional custom init string i found in a different forum, didn’t work either:

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

still wanted to see negotiates on which protocol connect Torque,
this can be seen in the Adapter State
the program can not automatically connect to 21 Sid, only external PIDs
when Torque connect to 21 Sid, it will be impossible to conduct the Test external PIDs, you must not be a connection with the c ECU
if you have connected to the ECU, then the program most likely joined by EOBD protocol
do this:
create a file .csv, with your external PID
place a csv file in a folder, .torque\extendedpids\
create on the screen device with your external PID
profile settings you have the correct

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

I hope this helps, maybe I’ll have to install the english localized version of Torque?

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

Yes, the program connects via European EOBD
try through the file .csv

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

I’m a little bit irritated… the only use of csv files I’m aware of is to add custom PIDs – and I can’t see how this could help.

Could you please explain a little bit more detailed what you want me to do?

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

Torque not find the answer on factory protocol, will attempt to connect by EOBD protocol
if you do not make a single device for external PID from a .csv file, the program will connect by EOBD protocol, but not on factory protocol 21 Sid

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 10, 2016 (GMT)

So you are suggesting that i remove the custom PID from the Torque settings and re-import it from a csv file? Can try that tomorrow.

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 11, 2016 (GMT)

didn’t work either… absolutely no difference to the manually added PID.
I also checked the adapter settings and it’s still set to European EOBD…

Anything to consider when creating the csv file?

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 12, 2016 (GMT)

try to set the OBD Header
https://yadi.sk/i/3tZzp0VSohdhh

https://yadi.sk/d/aEMx37dNoheYu

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 12, 2016 (GMT)

didn’t work either

Update: If i set the connection string to ATZ\nATSP5\ATSH8110F1\n8301\n1081 I get a CANBUS error as a response to the 21CD request.

I changed the connection string to ATSP5\nATSH8110F1\n8301\n1081 as you suggested.
Now I have a different result: Torque can’t connect to the ECU anymore, but never the less I receive a valid response for the 21CD request.
So I can’t get any other data :(

Any Idea? I already tried to change the protocol to ISO 15765-4 since I know it’s a Bosch protocol and my car’s ECU seems to be from Bosch, but still no difference.

Didn’t think that it would be THAT hard to make Torque work with my Alfa Romeo… :(

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 13, 2016 (GMT)

Now you get the desired result
when you are connected by an external PID, standard PID does not work
add a csv file all the data you need
made a request to the terminal for me, understand what other protocols are supported by your ECU
atz
atsp5
ath1
atshc133f1
0100
81
atkw
atsp6
atsh7e0
0100
atsh7df
0100

nordic81
Member
Posts: 20
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 13, 2016 (GMT)
>ATSP5
OK

>ATH1
OK

>ATSHC133f1
OK

>0100
BUS INIT: OK
86 F1 10 41 00 98 3B 00 11 AC
86 F1 02 41 00 80 18 80 00 D2

>81
83 F1 10 C1 E9 8F BD
83 F1 02 C1 E9 8F AF

>atkw
1:E9 2:8F

>atsp6
OK

>atsh7e0
OK

>0100
CAN ERROR

>atsh7df
OK

>0100
CAN ERROR

Btw: I’ve got MultiECUScan up and running, maybe I can get some more information out of this program?

cintakc
Member
Posts: 1661
Post Re: Torque Initallization Problems / Problems reading custom PIDs
on: February 13, 2016 (GMT)

by Can protocol you block ecu does not respond
I think, without the creation of the csv file, create an external PID, and so must work, if you remove the tick “Use alternative Header OBD”, do not forget to to fill in the header 8210F1
here is another PID
https://yadi.sk/d/NAakLoHzomkHG

Pages: 1 [2]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.041 seconds.

  Follow me on twitter