Torque PIDs...Take 2

Torque Control Requested (Used during shifting to reduce torque...aka torque management.)
PID 2203AF  returns 0 with car off.

Equation: (256*A)+B

Not sure if this really works or not as I never really played with it but give it a shot...
 
ecoboostsho said:
Torque Control Requested (Used during shifting to reduce torque...aka torque management.)
PID 2203AF  returns 0 with car off.

Equation: (256*A)+B

Not sure if this really works or not as I never really played with it but give it a shot...

That is only one mode of torque control...the one you are talking of is torque source 7 when logging tq source....there are probably 30 different kind of torque reduction as displayed by tq source
 
AJP turbo said:
ecoboostsho said:
Torque Control Requested (Used during shifting to reduce torque...aka torque management.)
PID 2203AF  returns 0 with car off.

Equation: (256*A)+B

Not sure if this really works or not as I never really played with it but give it a shot...

That is only one mode of torque control...the one you are talking of is torque source 7 when logging tq source....there are probably 30 different kind of torque reduction as displayed by tq source
Gotcha - I'd have to break out FORSCAN and do some investigating. I found that one ages ago when I was poking around.  I will try and do that if I have time.  The downside is you are only ever going to get the value out of torque and would need to keep the handy reference table available to correlate the actual source but at least it's a start.
 
Thank you ! That's fine trying to get all my logging in torque I should of bought sctx4 instead of a piggy back.
Is there a way I can find the pids in forscan without a sniffer?

Sent from my Nexus 6P using Tapatalk

 
Gjkrisa said:
Thank you ! That's fine trying to get all my logging in torque I should of bought sctx4 instead of a piggy back.
Is there a way I can find the pids in forscan without a sniffer?

Sent from my Nexus 6P using Tapatalk
Not that I am aware of unfortunately.

I did do sone scanning last night and the PID is definitely 2203AF but the equation is just A.

It returns a variety of values that correspond to the source I believe they will match the numbers over in the other thread on AWD shutoff...So 0 is "none requested" and 1 is "Trans Torque" 2 is speed limiter, 3 is rev limiter, etc...

I still need to drive the car and verify some of those variables...But at least you'd have an idea of what is requesting the torque reduction.



Sent from my XT1096 using Tapatalk
 
I was given this and just want to make sure I have why tourqu source would shutdown


MiWiAu said:
Perhaps "Torque Source"?

I found this on the SVT Performance forum. Perhaps AJP Turbo can comment on the accuracy of these for other Fords. 4 matches up with a rev limiter issue I was having, so maybe it's the same for all Fords??

TQ_SOURCE Identifies the source of the torque reduction requestor

0 No Torque Reduction Requested (Torque Control Off)
1 Torque truncation, transmission
2 Traction Control
3 Vehicle Speed Limiter
4 Engine Speed Limiter
5 Tip-in shock Control
6 Tip-out Decel Control
7 Torque Shift Modulation, transmission
8 Engine Oil Temperature Control
9 Fail Safe Cooling Control
11 Turbo Charger
12 Passive Anti Theft system (PATS)
13 Tip in Torque Control

TQ_SOURCE Source of torque reduction:

0 Driver Demand
1 Transmission torque truncation
2 Traction Control
3 Vehicle Speed Limiting
4 Engine Speed Limiting
5 Tipin rate limiting
6 Tipout torque
7 Transmission Shift Modulation
8 Engine Oil Over temperature
9 Target N
10 Not Used
11 ETC FMEM - RPM Guard
12 PATS
13 OSCMOD



Sent from my iPhone using Tapatalk




Sent from my Nexus 6P using Tapatalk

 
Also when I put the car in Cruse control the 2203af goes to 14 is that literally saying car is incruise or something else

Sent from my Nexus 6P using Tapatalk

 
I unfortunately don't have a table of values beyond what was shared here so I can't speculate. If you have Forscan why not run that. It has the values in it already? At least while you are diagnosing an issue.

Sent from my XT1096 using Tapatalk

 
Yea trying to get a log in torque but forscan may be better just takes longer to set up before I can start sliding in the snow

Sent from my Nexus 6P using Tapatalk

 
question on the pid's  i know i can read the tps  sensor on our 2013 and up  has anyone been able to read the 2010's have a f250 also would like to use torque for that reading also
 
Gjkrisa said:
Yea trying to get a log in torque but forscan may be better just takes longer to set up before I can start sliding in the snow
Save your Forscan profiles.  Reload as needed.  Easy Peasy.
 
Gjkrisa said:
Yea trying to get a log in torque but forscan may be better just takes longer to set up before I can start sliding in the snow

Sent from my Nexus 6P using Tapatalk
Torque is too slow for proper logging....

You need an x4!

 
Anyone know if there's a way to add a pid for the o2 sensors?  I'm only getting the downstream sensors, but not the upstreams.  Is there a way to add this?
 
Has anyone done the work to see if there is a pid for the humidity sensor and internal temp sensor?
Also codes for controlling heated/cooled seats heated steering wheel and all the other climate controls?

I'd love to be able to get rid of sync and just install a Android tablet or pioneer nex deck.


Sent from my Pixel 2 XL using Tapatalk

 
Do our vehicles possibly have a exhaust back pressure sensor?
d1e9fa4479f3a588ebe49273133e079e.jpg


Sent from my Pixel 2 XL using Tapatalk

 
In OP's CSV file with PIDs, the equation for "Bypass Valve Commanded Open" should be changed from A/256 to A/255. This will give a full value of 1 instead of 0.99609375 when the valve is open, as the hex value is FF (255) when the valve is open.

FF = 255
255/256 = 0.99609375
255/255 = 1

I know Torque will round 0.99609375 to 1 when there are no decimal places shown, but I found this issue when trying to implement the following:

If you want Torque to say Open and Closed instead of 1 and 0, use this equation:
Lookup((A/255)::0='Closed':1='Open')
 
rmkilc said:
In OP's CSV file with PIDs, the equation for "Bypass Valve Commanded Open" should be changed from A/256 to A/255. This will give a full value of 1 instead of 0.99609375 when the valve is open, as the hex value is FF (255) when the valve is open.

FF = 255
255/256 = 0.99609375
255/255 = 1

I know Torque will round 0.99609375 to 1 when there are no decimal places shown, but I found this issue when trying to implement the following:

If you want Torque to say Open and Closed instead of 1 and 0, use this equation:
Lookup((A/255)::0='Closed':1='Open')
Good catch!  I fixed the file.
 
Back
Top