Forums

Guest
Welcome Guest, posting in this forum require registration. Username Password Remember me

Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Filtering PIDs

Pages: [1]

Author	Topic: Filtering PIDs

Aberk

Member
Posts: 40

Filtering PIDs
on: January 28, 2011 (GMT)

I think the Torque app is being too “smart”. I am writing a PID that requests Trans temp. This data is returned by the TCM, not by the PCM. Looking at my log files it would appear that Torque ignores all responses from anything but the PCM. That kind of throws a wrench into my whole process because the PCM responds with a 7F, which is an error response indicating the request is not supported. But Torque is treating this PCM response as the data that I requested.

Is it possible to have torque ignore 7Fs and use the data returned by the TCM?

logfile subset…

1296227536015 **** Added:7e90562167403b3 ****
1296227536016 **** Filtered to:7f2231 ****
1296227536018 7E90562167403B3 Response from TCM
1296227536077 –> +7E8037F2231 Response from PCM
1296227536132 **** Added:7e90562167403b3 **** data that I want passed to the gauge
1296227536132 **** Filtered to:7f2231 **** data that is actually shown to the gauge
1296227536134 7E90562167403B1
1296227536192 –> +7E8037F2231
1296227536247 **** Added:7e90562167403b1 ****
1296227536247 **** Filtered to:7f2231 ****
1296227536248 7E90562167403B1
1296227536329 –> +7E8037F2231
1296227536383 **** Added:7e90562167403b1 ****
1296227536383 **** Filtered to:7f2231 ****

1fastTRX

Member
Posts: 4

Re: Filtering PIDs
on: January 31, 2011 (GMT)

If anyone can help with this that would be great. The other one I have a question about is PID 1310 which is the engine oil temp. So far I cannot get the PID to display correctly and and the reading does not change once the truck has warmed up. Hopefully someone can shed some light on these PIDs for us.

Aberk

Member
Posts: 40

Re: Filtering PIDs
on: February 3, 2011 (GMT)

I tried EOT with some success. It displays the EOT as 161F most of the time. Occasionally it will bounce to 1075F, but I cannot figure out where in the log files Torque is gathering that data to throw off the response.

PID: 221310
Long name: Engine Oil Temperature
Short name: EOT
Min value: -40
Max Value: 300
scale factor: x1
Unit type: f
equation:((((B*256)+C)/100)-40)*(9/5)+32

After you create the new PID, quit Torque and restart. Add the gauge wherever you want. Like I said, it keeps bouncing between the correct temp and one that is VERY high, but I’m not sure why.

Device Info:
—————
Brand: sprint
Board: supersonic
Device: supersonic
Build id: sprint/htc_supersonic/supersonic/supersonic:2.2/FRF91/294884:user/release-keys
Model: PC36100
Product: htc_supersonic
Tags: release-keys
Type: user
Id: FRF91
Version: 2.2
SDK: 8
UserBuildId: 3.70.651.1
Application version: 1.2.47
Fast mode: false
Disable Speed adaption: false

1296775837939 **** Filtered to:6213102bb5 ****
1296775837941 7E9037F2212
1296775838024 –> +7E8056213102BB5
1296775838078 **** Added:7e9037f2212 ****
1296775838078 **** Filtered to:6213102bb5 ****
1296775838086 7E9037F2212
1296775838145 –> +7E8056213102BB5
1296775838222 **** Added:7e9037f2212 ****
1296775838222 **** Filtered to:6213102bb5 ****
1296775838224 7E9037F2212
1296775838283 –> +7E8056213102BB5
1296775838359 **** Added:7e9037f2212 ****
1296775838359 **** Filtered to:6213102bb5 ****
1296775838362 7E9037F2212
1296775838446 –> +7E8056213102BB5
1296775838499 **** Added:7e9037f2212 ****
1296775838499 **** Filtered to:6213102bb5 ****
1296775838506 7E9037F2212
1296775838588 –> +7E8056213102BB5
1296775838641 **** Added:7e9037f2212 ****
1296775838641 **** Filtered to:6213102bb5 ****
1296775838643 7E9037F2212
1296775838698 –> +7E8056213102BB5
1296775838778 **** Added:7e9037f2212 ****
1296775838779 **** Filtered to:6213102bb5 ****
1296775838781 7E9037F2212
1296775838867 –> +7E8056213102BB5
1296775838918 **** Added:7e9037f2212 ****
1296775838918 **** Filtered to:6213102bb5 ****
1296775838920 7E9037F2212
1296775839001 –> +7E8056213102BB5
1296775839055 **** Added:7e9037f2212 ****
1296775839055 **** Filtered to:6213102bb5 ****
1296775839059 7E9037F2212
1296775839109 –> +7E8056213102BB5
1296775839188 **** Added:7e9037f2212 ****
1296775839188 **** Filtered to:6213102bb5 ****
1296775839198 7E9037F2212
1296775839284 –> +7E8056213102BB5
1296775839337 **** Added:7e9037f2212 ****
1296775839337 **** Filtered to:6213102bb5 ****
1296775839347 7E9037F2212
1296775839429 –> +7E8056213102BB5
1296775839481 **** Added:7e9037f2212 ****
1296775839481 **** Filtered to:6213102bb5 ****
1296775839486 7E9037F2212
1296775839555 –> +7E8056213102BB5
1296775839621 **** Added:7e9037f2212 ****
1296775839622 **** Filtered to:6213102bb5 ****
1296775839624 7E9037F2212
1296775839712 –> +7E8056213102BB5
1296775839759 **** Added:7e9037f2212 ****
1296775839759 **** Filtered to:6213102bb5 ****

piemmm

Administrator
Posts: 6629

Re: Filtering PIDs
on: February 4, 2011 (GMT)

I’ll have a look at sorting this out in the next version now I have the multi-ecu code working!

Ian

Aberk

Member
Posts: 40

Re: Filtering PIDs
on: February 4, 2011 (GMT)

Fantastic!

piemmm

Administrator
Posts: 6629

Re: Filtering PIDs
on: February 5, 2011 (GMT)

Hopefully this should now be working if you get the latest update from the market (1.4.4) for you!

Aberk

Member
Posts: 40

Re: Filtering PIDs
on: February 5, 2011 (GMT)

The good thing is I dont see the jump in engine oil temp anymore. It gives a good steady readout. However trans temp displays no data. It looks like you’re filtering for only header 7E8, but the data for the trans temp is coming from 7E9. Here are the traces, let me know what you think.

1296916413325 7E9056216740202
1296916413384 –> +7E8037F2231
1296916413463 **** repliedType=22 16 line:6216740202 lineData:16740202 ****
1296916413464 **** Put extra ECU into:fe1816 -9.375 for 16740202(24) ****
1296916413464 **** Filtered to:7f2231 ****
1296916413467 7E803410B66
1296916413603 **** Filtered to:410b66 ****
1296916413613 7E9056216740202
1296916413700 –> +7E8037F2231
1296916413781 **** repliedType=22 16 line:6216740202 lineData:16740202 ****
1296916413782 **** Put extra ECU into:fe1816 -9.375 for 16740202(24) ****
1296916413783 **** Filtered to:7f2231 ****
1296916413799 7E803410B66
1296916413943 **** Filtered to:410b66 ****

Aberk

Member
Posts: 40

Re: Filtering PIDs
on: February 7, 2011 (GMT)

whoops…I found the extended Ford PIDs. I’ll check TFT this evening.

1fastTRX

Member
Posts: 4

Re: Filtering PIDs
on: March 18, 2011 (GMT)

For whatever reason I can’t get that equation to work. When I click OK to save the Custom PID it says:

Equation: This value is invalid: -37.43*1.8+32

What am I doing wrong? Should I actively be connected to my truck to make it work since the values are different at that time?

Thanks

bitterbeard

Member
Posts: 2

Re: Filtering PIDs
on: May 18, 2011 (GMT)

Quote from Aberk on February 7, 2011
whoops…I found the extended Ford PIDs. I’ll check TFT this evening.

You found the extended PIDs, can you share the info? Greatly appreciated!

piemmm

Administrator
Posts: 6629

Re: Filtering PIDs
on: May 18, 2011 (GMT)

Quote from 1fastTRX on March 18, 2011
For whatever reason I can’t get that equation to work. When I click OK to save the Custom PID it says:

Equation: This value is invalid: -37.43*1.8+32

It’s probably the parser not liking the preceding ‘-‘sign. I will have a look at it as it may be a bug (incidentally, you have no ‘A’ or ‘B’ variables in there so the result from the equation will never change

1fastTRX

Member
Posts: 4

Re: Filtering PIDs
on: July 4, 2011 (GMT)

I had the same problem with the invalid equation. Try replacing the “-40” with a “+40” and that will satisfy the equation. When I tried it on my truck the values seemed fairly close, but I will need to try when cold to check with ambient temps. The conversion portion “*(9/5)+32)” made things wrong for me. I received fahrenheit information which Torque then interpreted as the celsius information and converted again to fahrenheit making the valuse extremely high so I simply omitted that part from my equation.

piemmm

Administrator
Posts: 6629

Re: Filtering PIDs
on: July 5, 2011 (GMT)

The double conversion F / C has been fixed in the latest version, so when you update, and (if) the value seems wrong, you’ll need to put the correct unit in the extended PID you created (which was one of the the original workarounds – you could also just change the equation as well)

Ian

vita_k

Member
Posts: 6

Re: Filtering PIDs
on: September 22, 2011 (GMT)

I’m sorry, could not find help for this. A means first byte and B means sencond byte received? So A is MSB and B LSB?
thanks.

piemmm

Administrator
Posts: 6629

Re: Filtering PIDs
on: September 22, 2011 (GMT)

That depends entirely on the data, not all data 2 byte. Sometimes it is singular byte, other times it can be 2 or 4 bytes.

For 2 bytes, it’s (A*256)+B, where A represents the most significant. In the equation editor in the app, bracket placement is important.

Pages: [1]

WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.05 seconds.

Forums

Forums

Guest