Torque PIDs...Take 2

[SHOdded]

Thank you both

 

[askoncemore]

I have been using the TPMS sensor PIDs for Torque for two years now.
Tablet crapped out... all other PID work on new tablet but these.

What gives?

 

[ecoboostsho]

I have been using the TPMS sensor PIDs for Torque for two years now.
Tablet crapped out... all other PID work on new tablet but these.

What gives?

What year is your flex again? (I'm on Tapatalk and can't see signatures). What is the module address you are accessing? (Header in Torque pro I believe?) If 2013+ then it should be set to 726.

Sent from my XT1650 using Tapatalk

 

[SHOdded]

2013 flex

 

[Gjkrisa]

I have been using the TPMS sensor PIDs for Torque for two years now.
Tablet crapped out... all other PID work on new tablet but these.

What gives?

What year is your flex again? (I'm on Tapatalk and can't see signatures). What is the module address you are accessing? (Header in Torque pro I believe?) If 2013+ then it should be set to 726.

Sent from my XT1650 using Tapatalk

On taptalk you can tap the top right then select view web page then make it jump to the last post

Sent from my Pixel 2 XL using Tapatalk

 

[jman]

I was recently looking for a way to detect knock and was pointed to this awesome thread. I followed the instructions and installed four of the custom PID's. Most don't work and the AWD one throws a constant value. What am I missing?
I have not read all 51 pages of this thread, do these work on the 2010 SHO?

Attached are pics of what I am seeing and what I get when I "test" the Knock PID.

 

[ecoboostsho]

I was recently looking for a way to detect knock and was pointed to this awesome thread. I followed the instructions and installed four of the custom PID's. Most don't work and the AWD one throws a constant value. What am I missing?
I have not read all 51 pages of this thread, do these work on the 2010 SHO?

Attached are pics of what I am seeing and what I get when I "test" the Knock PID.

It should definitely work on a 2010 Taurus. I'm assuming you can get the standard gauges (say like (RPM) to respond? I just want to make sure your adapter is actually talking to the car properly.  Also can you send a screenshot of your custom pid screen in Torque? Just close that error message window for starters.

Sent from my Pixel 3 XL using Tapatalk

 

[jman]

All built-in Torque Real Time Monitoring gauges work.

The AWD one throws a number, but why is it always at 50.4?

Attached is a pic of the Knock PID.

Thanks !

 

[sm105k]

Jman,

adjust your minimum value to -7.0

adjust your maximum value to 7.0

make sure your scale factor is x1

then test

 

[Gjkrisa]

All built-in Torque Real Time Monitoring gauges work.

The AWD one throws a number, but why is it always at 50.4?

Attached is a pic of the Knock PID.

Thanks !

I see that's for knock and your main issue was with awd I believe just making sure your scale factor is 1x should fix the issue that's how mine is and works

Sent from my Pixel 2 XL using Tapatalk

 

[ecoboostsho]

All built-in Torque Real Time Monitoring gauges work.

The AWD one throws a number, but why is it always at 50.4?

Attached is a pic of the Knock PID.

Thanks !

If the previous suggestions don't work just delete your equation and temporarily put in an A for your equation. You should at least get a value back that is non scaled. That will help narrow down the problem for me...

Sent from my Pixel 3 XL using Tapatalk

 

[jman]

I changed the scale limits and verified that all PID's are set at x1. Still no luck.
I'll try deleting the equation and report back,

Here are some additional pics and also the Bluetooth thingy I am using. As you can see, built-in Torque ones do work.

 

[jman]

If the previous suggestions don't work just delete your equation and temporarily put in an A for your equation. You should at least get a value back that is non scaled. That will help narrow down the problem for me...

Sent from my Pixel 3 XL using Tapatalk

Replaced the Knock equation with an A, same response when tested: NO DATA.

 

[ecoboostsho]

If the previous suggestions don't work just delete your equation and temporarily put in an A for your equation. You should at least get a value back that is non scaled. That will help narrow down the problem for me...

Sent from my Pixel 3 XL using Tapatalk

Replaced the Knock equation with an A, same response when tested: NO DATA.

Okay well then something isn't communicating with the car properly or the pid is wrong somehow for your car. It looks like it but that is "zero" in the 2203EC correct? It's been a long time since I messed with torque pro (I use obdlink) so I don't think it matters but try a capital EC just for fun. Also what is in your header field?

Sent from my Pixel 3 XL using Tapatalk

 

[jman]

Yes, two, two, zero, three.
I've tried uppercase before, it auto turns back to lower case.
Header is blank.

 

[ecoboostsho]

Yes, two, two, zero, three.
I've tried uppercase before, it auto turns back to lower case.
Header is blank.

Okay just checking. Try using AUTO in the header. If that doesn't work I'm stumped unfortunately. I would try a different app just to see if it's something weird in your Installation of torque.

Sent from my Pixel 3 XL using Tapatalk

 

[jman]

Neither the "A" or the "auto" fixed it.
Weird thing is that the AWD does return a value (steady 50.4) but all others don't.

When I was playing with Forscan I read that the 2010 doesn't have a BCM (or cannot be accessed), could this be why?

 

[ecoboostsho]

Neither the "A" or the "auto" fixed it.
Weird thing is that the AWD does return a value (steady 50.4) but all others don't.

When I was playing with Forscan I read that the 2010 doesn't have a BCM (or cannot be accessed), could this be why?

Well on the 2010-12 there is a smart junction box (SJB) on the MSCAN bus and not a BCM on the HSCAN bus.  First your adapter has to have the ability to speak MSCAN (medium speed CAN bus) and second Torque can't (to my knowledge) access both the MSCAN bus and HSCAN bus at the same time.  That said if I recall correctly the AWD gauge is actually reading the AWD module (not a SJB or BCM) and that is why the header needs to be "761" for that gauge.