PID for LTFT Bank 2?...and others!
#1
PID for LTFT Bank 2?...and others!
Howdy, Folks!
Still working on this '06(?) swapped 5.3L running an '01 ECM that's in my '96 Tahoe.
Please see this tread too:
https://ls1tech.com/forums/pcm-diagn...-attached.html
My ScanTool Bluetooth OBD Adapter should probably be displaying LTFT Bank 2, but for some reason is not. At least not in the App they provided with the device, which actually seems pretty decent.
Anyway, I'd like to attempt to add it as User Defined PID. Except, I don't know what that PID actually is.
If anybody knows what it is and might could provide it, I'd sure appreciate it. A full list of possible PID's for this ECM would be excellent as well. The ECM seems to be Part Number: 12200411 based on the original VIN that was in it (before I had it changed to match my '96 VIN...). I don't seem to be able to see any data from the Knock Sensors either. Maybe I shouldn't be able to?
Of course, if somebody knew why it wasn't working already, that'd be great too.
Thanks,
-Kyle
Still working on this '06(?) swapped 5.3L running an '01 ECM that's in my '96 Tahoe.
Please see this tread too:
https://ls1tech.com/forums/pcm-diagn...-attached.html
My ScanTool Bluetooth OBD Adapter should probably be displaying LTFT Bank 2, but for some reason is not. At least not in the App they provided with the device, which actually seems pretty decent.
Anyway, I'd like to attempt to add it as User Defined PID. Except, I don't know what that PID actually is.
If anybody knows what it is and might could provide it, I'd sure appreciate it. A full list of possible PID's for this ECM would be excellent as well. The ECM seems to be Part Number: 12200411 based on the original VIN that was in it (before I had it changed to match my '96 VIN...). I don't seem to be able to see any data from the Knock Sensors either. Maybe I shouldn't be able to?
Of course, if somebody knew why it wasn't working already, that'd be great too.
Thanks,
-Kyle
Last edited by kpeters59; 03-16-2016 at 10:10 PM. Reason: Clarity / Added Log File
#2
OK...Found this list:
https://en.wikipedia.org/wiki/OBD-II_PIDs
09 1 Long term fuel % trim—Bank 2 -100 Subtracting Fuel (Rich Condition) 99.22 Adding Fuel (Lean Condition) % (A-128) * 100/128
Seems to be what I'm after, but what is the full PID number I enter?
Thanks,
-Kyle
https://en.wikipedia.org/wiki/OBD-II_PIDs
09 1 Long term fuel % trim—Bank 2 -100 Subtracting Fuel (Rich Condition) 99.22 Adding Fuel (Lean Condition) % (A-128) * 100/128
Seems to be what I'm after, but what is the full PID number I enter?
Thanks,
-Kyle
#3
Does anybody know if my ECM should have a Knock Sensor PID? The ECM part number is 12200411 . It's from an '01 DBC truck.
Maybe I found the PID for Knock Retard?
Knock Retard = 2630
Total KR = 2631
Burst KR = 2641
Cyl 1-8 KR are 2650-2657
But I can't tell if it's supported on my ECM or not. Or why the software wouldn't just 'detect' it.
Thanks,
-Kyle
Maybe I found the PID for Knock Retard?
Knock Retard = 2630
Total KR = 2631
Burst KR = 2641
Cyl 1-8 KR are 2650-2657
But I can't tell if it's supported on my ECM or not. Or why the software wouldn't just 'detect' it.
Thanks,
-Kyle
#5
Cool!
Thanks for replying!
I'm using the App that came with my ECM Scan Device (Scantool MX Bluetooth).
The app is called OBDLink, but appears to be the same as OBDFusion.
It turns out that the 'Display' I'd set up for LTFT Bank 1, I'd inadvertently selected the adjacent PID for STFT Bank1 and so my readings for Bank1 and Bank2 were wildly different...go figure!
It seems that the PID and Logging are working fine for LTFT, but I'll be darned if I can figure out how to see any of the Knock Sensor info.
Any chance you can divine out of HPTuners the PID's and Formulas for Knock Retard, Knock Count and any other Knock PID's that the ECM is capable of?
Apparently, if I go back to High School and finish Trig Class and then take a couple of Math Classes at the Community College, I'm supposed to be able then to learn how to manually add the PID's and Formulas for missing data...or something like that...
Thanks,
-Kyle
Thanks for replying!
I'm using the App that came with my ECM Scan Device (Scantool MX Bluetooth).
The app is called OBDLink, but appears to be the same as OBDFusion.
It turns out that the 'Display' I'd set up for LTFT Bank 1, I'd inadvertently selected the adjacent PID for STFT Bank1 and so my readings for Bank1 and Bank2 were wildly different...go figure!
It seems that the PID and Logging are working fine for LTFT, but I'll be darned if I can figure out how to see any of the Knock Sensor info.
Any chance you can divine out of HPTuners the PID's and Formulas for Knock Retard, Knock Count and any other Knock PID's that the ECM is capable of?
Apparently, if I go back to High School and finish Trig Class and then take a couple of Math Classes at the Community College, I'm supposed to be able then to learn how to manually add the PID's and Formulas for missing data...or something like that...
Thanks,
-Kyle
Last edited by kpeters59; 03-30-2016 at 10:11 AM. Reason: Clarity
#7
So, I'd found this info somewhere:
Knock Retard
PID: 2211a6
Unit: Deg. Min/Max: 0/50
Equation: (22.5*A)/256
Not sure which ECM, since it doesn't seem to be the 411.
But, does the 'Formula' look correct? On this software, I have to know and add the formula when I manually enter a PID. I also am supposed to 'know' (not sure how...) if it's Mode 22 or Mode 01.
Do you (or anybody!) know if the same formula is used for the individual cylinder 'Knocks'?
The software has a feature to 'import' all the PID's from the ECM, but it added a whole bunch that didn't work. Injector Pulse Width doesn't work. Misfire Count didn't work, but Misfire History for all 8 cylinders does work...and on and on. The manufacturer of the Hardware uses a third party for the software. It gets so close to being really good and between the 2 parties, getting info or help is worse than pulling teeth. In regards to questions like these, they near literally posted a link and said "look it up".
Anybody know how to obtain a list of all the valid PID's and the Formulas for the 411 ECM? It seems to be mystery...
Thanks,
-Kyle
Last edited by kpeters59; 03-31-2016 at 06:23 PM. Reason: Clarity
Trending Topics
#8
#10
I went ahead and purchased the Android App ' Torque ' , which, near as I can tell, is the reference App for this kind of thing. For $5 it sure does seem to be nice software. It has an available plugin called Torque Scan that queries every position a PID might be located and attempts to receive a response.
Here are the results from my scan:
Please enter the vehicle type if sending to the developer, thanks!
Scanning has started. Discovered PIDs will appear here.Command: 220001 response:6200010007ED20
Command: 220004 response:62000408
Command: 220009 response:62000980
Command: 220010 response:620010035C
Command: 220019 response:62001959FF
Command: 2210e1 response:<DATA ERROR
Command: 221100 response:62110080
Command: 221101 response:62110102
Command: 221104 response:62110460
Command: 221110 response:62111000
Command: 221119 response:62111900
Command: 221140 response:621140041C
Command: 221151 response:62115101
Command: 221190 response:62119013
Command: 221200 response:62120000
Command: 221201 response:6212010000
Command: 221204 response:6212040000
Command: 221300 response:621300048C
Command: 221301 response:6213010000
Command: 221310 response:62131002
Command: 221319 response:62131912
Command: 221900 response:62190000
Command: 221901 response:62190100
Command: 221924 response:62192420
Command: 221940 response:6219406A
Command: 223809 response:<DATA ERROR
Command: 2246c4 response:<DATA ERROR
Command: 2264e1 response:<DATA ERROR
Command: 229440 response:<DATA ERROR
Command: 229a09 response:<DATA ERROR
Command: 22c509 response:<DATA ERROR
Command: 22cd19 response:<DATA ERROR
Command: 22f0a9 response:<DATA ERROR
Command: 22fc24 response:62FC240000
Command: 22fc40 response:62FC400000
Scanning finished
Unfortunately, there appears to not be a match for the PID's that were provided above. Go figure...
To 'interpret ' this info, you can see the command sent starting with 22 and the response received starting with 62 and then (apparently) a repeat of the command followed by the actual data. according to a post on the Torque Forum, the data is in Hex.
Can anybody here make any heads or tails out of this? I'd REALLY like to get all available Knock Data I can.
Thanks,
-Kyle
Here are the results from my scan:
Please enter the vehicle type if sending to the developer, thanks!
Scanning has started. Discovered PIDs will appear here.Command: 220001 response:6200010007ED20
Command: 220004 response:62000408
Command: 220009 response:62000980
Command: 220010 response:620010035C
Command: 220019 response:62001959FF
Command: 2210e1 response:<DATA ERROR
Command: 221100 response:62110080
Command: 221101 response:62110102
Command: 221104 response:62110460
Command: 221110 response:62111000
Command: 221119 response:62111900
Command: 221140 response:621140041C
Command: 221151 response:62115101
Command: 221190 response:62119013
Command: 221200 response:62120000
Command: 221201 response:6212010000
Command: 221204 response:6212040000
Command: 221300 response:621300048C
Command: 221301 response:6213010000
Command: 221310 response:62131002
Command: 221319 response:62131912
Command: 221900 response:62190000
Command: 221901 response:62190100
Command: 221924 response:62192420
Command: 221940 response:6219406A
Command: 223809 response:<DATA ERROR
Command: 2246c4 response:<DATA ERROR
Command: 2264e1 response:<DATA ERROR
Command: 229440 response:<DATA ERROR
Command: 229a09 response:<DATA ERROR
Command: 22c509 response:<DATA ERROR
Command: 22cd19 response:<DATA ERROR
Command: 22f0a9 response:<DATA ERROR
Command: 22fc24 response:62FC240000
Command: 22fc40 response:62FC400000
Scanning finished
Unfortunately, there appears to not be a match for the PID's that were provided above. Go figure...
To 'interpret ' this info, you can see the command sent starting with 22 and the response received starting with 62 and then (apparently) a repeat of the command followed by the actual data. according to a post on the Torque Forum, the data is in Hex.
Can anybody here make any heads or tails out of this? I'd REALLY like to get all available Knock Data I can.
Thanks,
-Kyle
Last edited by kpeters59; 04-02-2016 at 09:19 PM.
#11
411 ecm
Just to verify, I went and pulled out the ECM to make sure it really is a 411 ECM.
Why the heck can't I find PID's that seem like should be there?
Thanks,
-Kyle
Definitely a 411!
Why the heck can't I find PID's that seem like should be there?
Thanks,
-Kyle
Definitely a 411!