Torque PIDs...Take 2

Jus checked the mail...to my surprise my OBDLink Mx Bluetooth was in there...didn't finalize order until like 10 pm Monday night and picked standard free usps ...3 day was like $20...came for free that fast...looks like it might be a long night
 
After thinking I copied the attachment over to my tablet in the right folder, still couldn't find it in torque so I just manually loaded some custom PID'S ...

Noticed a difference in the equations for the 2 fuel pump pressure PID'S. ..when lookin at those 2 on 1st page they have .145 compared to 1.145 in the attachment file...haven't got to test which one is right yet.
 
Hi guys, i have been data logging, and finally, I found a situation where Learned Relative Octane Adjust will go negative, I have captured that HEX 1700 translate to -1.70% on FORScan.

This will mean that so far the 3 readings i have are:
HEX D145  = Decimal (53573) = 73.01%
HEX DCEC = Decimal (56556) = 54.81%
HEX 1700 = Decimal (5888) = -1.70%

The positive values the formula works, but it goes to 300+ when it is suppose to read -1.70%


 
SHOnUup said:
After thinking I copied the attachment over to my tablet in the right folder, still couldn't find it in torque so I just manually loaded some custom PID'S ...

Noticed a difference in the equations for the 2 fuel pump pressure PID'S. ..when lookin at those 2 on 1st page they have .145 compared to 1.145 in the attachment file...haven't got to test which one is right yet.

The PIDs on the first page show 10 * .145 which I just shortened mathwise in the csv file to 1.45.  This is in PSI...if you wanted kpa for some reason you would need to drop the .145 part on the first page OR modify the equation in the file to be just *10.

Hope that helps...

Actually now that you say that I did goof...it does say 1.145 in the file and should have been 1.45.  Nice catch.  The differential pressure still would have calculated correctly since I did it in both places but the value would be off.
 
Roger that..thx....spent many hours loading and playing with it last night and am now waiting on the woman to get home with car...man I thought she was taking the truck today
 
SHOnUup said:
Roger that..thx....spent many hours loading and playing with it last night and am now waiting on the woman to get home with car...man I thought she was taking the truck today

File has been updated!  Man that would stink!  Can't blame the wife for wanting to drive the SHO though.
 
millinnium said:
Hi guys, i have been data logging, and finally, I found a situation where Learned Relative Octane Adjust will go negative, I have captured that HEX 0117 translate to -1.70% on FORScan.

This will mean that so far the 3 readings i have are:
HEX D145  = Decimal (53573) = 73.01%
HEX DCEC = Decimal (56556) = 54.81%
HEX 0117 = Decimal (279) = -1.70%

The positive values the formula works, but it goes to 300+ when it is suppose to read -1.70%
Wow...that is going to be a tough one.  If I graph those values they look to be non-linear so I'm not sure what it is doing... Since you don't have a Taurus I am wondering your ECU and the associated PID/formula is trying to produce the -1 to +1 but Forscan is giving weird values.  I don't know why you would even get a negative percent...sorry but I'm stumped on this one.
 
millinnium said:
Hi guys, i have been data logging, and finally, I found a situation where Learned Relative Octane Adjust will go negative, I have captured that HEX 0117 translate to -1.70% on FORScan.

This will mean that so far the 3 readings i have are:
HEX D145  = Decimal (53573) = 73.01%
HEX DCEC = Decimal (56556) = 54.81%
HEX 0117 = Decimal (279) = -1.70%

The positive values the formula works, but it goes to 300+ when it is suppose to read -1.70%

HEX 0117, is this Short term fuel trim?
 
ShoBoat said:
millinnium said:
Hi guys, i have been data logging, and finally, I found a situation where Learned Relative Octane Adjust will go negative, I have captured that HEX 0117 translate to -1.70% on FORScan.

This will mean that so far the 3 readings i have are:
HEX D145  = Decimal (53573) = 73.01%
HEX DCEC = Decimal (56556) = 54.81%
HEX 0117 = Decimal (279) = -1.70%

The positive values the formula works, but it goes to 300+ when it is suppose to read -1.70%

HEX 0117, is this Short term fuel trim?
I believe he is listing values or the learned octane PID not the PIDs themselves.
 
ecoboostsho said:
millinnium said:
Hi guys, i have been data logging, and finally, I found a situation where Learned Relative Octane Adjust will go negative, I have captured that HEX 0117 translate to -1.70% on FORScan.

This will mean that so far the 3 readings i have are:
HEX D145  = Decimal (53573) = 73.01%
HEX DCEC = Decimal (56556) = 54.81%
HEX 0117 = Decimal (279) = -1.70%

The positive values the formula works, but it goes to 300+ when it is suppose to read -1.70%
Wow...that is going to be a tough one.  If I graph those values they look to be non-linear so I'm not sure what it is doing... Since you don't have a Taurus I am wondering your ECU and the associated PID/formula is trying to produce the -1 to +1 but Forscan is giving weird values.  I don't know why you would even get a negative percent...sorry but I'm stumped on this one.

yeah.. it is an odd one. but it does look like it is showing a possible range of -100% to 100%, note i quoted the wrong HEX, it should be 1700 not 0117 as posted earlier. So converted it is decimal 5888
 
wasinger3000 said:
What kind of trans temps are you guys seeing usually? My highest so far has been 208. Seems a little hot.
Depends on speed and ambient but 208 is pretty consistent going 75-80 on the highway. Sometimes higher. I have an alarm set at 230 but it doesn't get near that thankfully. I also tink that sounds a bit high though.
 
Back
Top