#Torque pro extended pids pro#
Looking at your original equation although I was not yet familiar with the usage of the ampersand as seen I did recongnize the values of 128 as bit 7 and 64 as bit 6.Įdit: I am going to add a screenshot from Torque Pro PID editor where you can see all the aforementioned hex, decimal, and binary representations of the response to a PID request. Assuming each bit was high the values for each would be. If it's a zero it is considered "low" and if 1 it is considered "high". If there is a second byte in the response from PCM or ECM or whatever that will also be converted to decimal and represented in the equation as the token "B" and so on down the line.Ī single byte is comprised of 8 bits numbered from 0 to 7, right to left when viewed as a binary value. If there is just one byte it is converted to decimal and represented in the equation as the token "A". Torque converts the hexadecimal byte value(s) it receives to decimal. The 6 and 7 here refer to the bit you are requesting with the function "BIT()". Trying each out on my 2003 Suburban 5.3L/4L60E I got no data from the first (not available) and questionable (50% from data vs. Torque Pro has two potential Fuel Level PIDS: "Fuel Level (from ECU)" and "Fuel Remaining (Calculated from vehicle profile)". For 2002 vintage vehicles the range is 40ohms (Empty) to 250ohms (Full). Regarding fuel level, start by ensuring the resistance range from the sending unit is consistent with the resistance range for the PCM you are using. However, I believe odometer data is stored in the Instrument Cluster Panel so unless you have implemented a corresponding IPC in your vehicle the point is moot. There is a GM Odometer PID listed in Torque Pro but it is not available for my vehicle. In the image below available PIDS are highlighted in green and unavailable PIDS are not highlighted.
First, check to see what PIDs are available for your vehicle.
0 kommentar(er)
