With A=3 this would return 3.Ĭar Scanner doesn’t support formula, that points to another sensor or another PID. If A greater than 5, return 5, else return A. A+13.54īitwise unary complement: AND: exclusive OR: left: – bitwise shift left, same as for comparison.Įxample: if(A>5 5 A). You can use floating point numbers in formula using dot “.”: e.g. To change calculation order use brakets ( ), like: (A*256+B)/4 You can use mathematical operators like *, /, –, +. Letter A would mean 0C, letter B would mean 9C mode 01 -> response marker 41) and PID id.Įxample: request 010C (engine RPM) would give you response: 7E804410C 0C9C, where Car Scanner would skip 7E804410C. To determine first byte, Car Scanner skips some bytes in response from ECU: header bytes, data length, response to certain mode marker (e.g. , where letter A stands for 1st byte in response, letter B stands for second byte in response, etc. To point at certain bytes in response use latin letters: A, B, C, D. How to decode received data: Formula (Equation). Most of custom PIDs requires correct header!Ģ. In that case default functional header for current protocol would be used. Header = address where to send request, e.g. How to make a request to ECU to get the data you need:Ĭommand = Mode + PID, e.g. To create custom sensor you need to know at least 2 things:ġ. I've also scanned Mode6 PIDs, the result is this in Torque: Mode1_Mode6_PIDs.pngĪnd the decoded result: OBD_Mode1.jpg, OBD_Mode6_CAN.jpgįinally if you want to see all your supported PIDs in Torque, you only have to add them one-by-one or via csv (don't forget to equations!, for details see the Wikipedia).Car Scanner allows you add custom sensors (also known as “custom PIDs”) to get data, defined by your car manufacturer. Here is my exported csv, if you don't want to bother editing the extended PIDs: supportedPIDs.csv When you have all the supported PIDs, the most simple way to decode them is this program: The same extended PID has to be created, the difference is, that the Equation will be B, C and D for the 0x00 PID.įor 0x20, 0x40. The result will be decimal, so you have to convert it to binary/hex. Max value: 255 (Torque will change it 255.0, but don't bother) Min value: 0 (Torque will change it 0.0, but don't bother) Short name: PID0120A (or whatever you want) Long name: PIDs_Mode1_01_20 (or whatever you want) Most significant byte: A (PIDs from x01 to x20) Since the response is 4 byte long, you have to set 4 extended PID. Torque is capable to read this via extended PIDs. are the coded PIDs, where the supported PIDs are encoded. OBD2 PID scan or at least decoding the supperted PIDs is not a rocket science.

Torque pro custom pid