1. Startseite
  2. Forum
  3. Wissen
  4. Fahrzeugtechnik
  5. On-Board-Diagnose
  6. OBD2 Diagnose

OBD2 Diagnose

Themenstarteram 18. Oktober 2014 um 11:09


Es tut mir leid das ich dafür ein neues Thema erstelle aber es wir fast immer nur für BMW und VAG gefragt.

Für VAG habe ich CarPort reicht zum Auslesen und Löschen völlig.

Jedoch besitzen wir auch Ford, Peugeot und einen Opel. Opel ist aber nicht so wichtig

Jetzt habe ich zwei Lösungen gefunden:


Ich besitze die Software ScanMaster schon. Darum würde ich gerne zum SX tendieren?

Was meint ihr oder gibt es eine Andere lösung?

Wichtig ist mir nur das Fehler lesen und Löschen und Messwertblöcke wären auch super. Wie die Software Grafisch ist, ist mir egal (ScanMaster ist auch nicht der Grafische Meister), es soll einfach nur Funktionieren.


Ähnliche Themen
5 Antworten

Für Ford nutze ich Shareware von Forscan

und auch Torque Pro, siehe z.B.

Für Peugeot suche ich derzeit selbst noch, vor allem nach customPID's

Untenstehendes Bild sind TorquePro PID's für 1,6 TDCI von Ford.

MX ist für Ford nach meiner Info besser als der SX geeignet !!!!



bin ebenfalls auf der Suche nach PIDs für Peugeot. Ich habe jetzt Tagelang im Inernet gesucht, aber nichts gefunden. Das kann doch fast nicht sein.

Falls ich doch auf etwas brauchbares stoße, dann melde ich mich natürlich.

Die customPID für Ford habe ich z.T auf italienischer Seite gefunden (von Google automatisch übersetzt).

Vielleicht sollte man mal bevorzugt französischen Seiten zum Thema PID für PSA durchsuchen !?!

(zur Zeit für mich NOCH nicht so aktuell, denke zur Zeit darüber nach einen 308 sw e-HDI 115 zu kaufen)


wenn jemand z.B. Zugriff auf ScanGauge II Daten hat, könnte er m.E. mit unten zitierten Rezept die erforderlichen customPID für TorquePro ermitteln.

Wie bereits gesagt denke ich über 308 sw von Peugeot nach, deshalb bin ich zwar grundsätzlich interessiert aber noch nicht in der Lage tatsächliche Erkenntnisse beizutragen.

Deshalb diese Anregung :);)



For those of you running the Torque Pro app, especially those running the 2005-2006 1-Gens who want to display ATF temp, here's a conversion routine I found on the interwebs. I haven't tested it yet, but will be doing so in the next few days or so with my brother-in-laws 2005 Toyota Tundra V8.


* * * Use at your own risk. * * *

You are directly accessing the ECU firmware with these commands, so

messing this up may influence vehicle management! Be careful!

This tutorial assumes that you are very familiar with the Torque Pro app,

its functions, and menus.


OK... to create a custom display, we need to fill in the following fields in Torque Pro:


OBD2 Mode and PID

Long Name

Short Name

Min Value

Max Value

Scale Factor

Unit Type


OBD Header


by pulling the appropriate data from the corresponding codes used by the ScanGauge II:










As we go through the tutorial I will use the following ScanGauge example of the ATF temp codes posted by SG on their website for 2005-2006 Toyotas that use the CANSF protocol:


GAUGE: Transmission Temperature

TXD: 07E021D9

RXF: 032180000000

RXD: 2810

MTH: 00070064FE70


NOTES: Degrees F


OBD2 Mode and PID

This field comes from the TXD of the SGII file. There are 2 flavors, CAN (controller Area Network) and the rest of the older OBD2 protocols. If it is CAN, you want to use all the characters after “07DF” or “07E0”. If it is “07E1”, then Torque will likely not work for this gauge as the ELM327 may need specific instructions to communicate the transmission control module. For all other protocols, you will use all the characters after the “F1”.

Our example: "21D9"

Long Name

Take this value from the GAUGE field.

Our example: "Transmission Temperature"

Short Name

Take this value from the NAM field.

Our Example: "TFT"

Min Value/Max Value Fields

These are really determined by the data you are gathering and can be set up after you have your equation. Torque does a pretty decent job of rescaling gauges if the data oversteps the range. I suggest setting minimum at "0" and maximum at "300".

Scale Factor

Leave this as 1 because we can scale in the equation if we need to.

**SGII may do some prescaling that I'm not aware of, so further testing is in order and possible offset scaling may need to be incorporated into the equation so the data displays correctly in the app.

Unit Type

Take this value for the notes field.

Our example: "Degrees F"


Now for the most complicated part: the actual equation.

Why an equation?

Well, look at what a vehicle sensor actually does... it simply measures electrical resistance. The structure and materials of the sensor are calibrated such that specific voltages correspond to a specific "real world" reading, i.e. temperature, O2 levels, etc. What the equation does is convert the machine's voltage numbers into 'human-readable' information, i.e. temperature, speed, etc and display it.

First look at the RXD field. Don’t worry about the first 2 characters. If the second 2 characters are “08”, then you have 1 byte of data and you will only need an “A” in your equation. If the second 2 characters are “10”, then you have 2 bytes of data and you will need to start off your equation with ((A*256)+B). Don’t ask why. This isn’t a lesson in hex.

Our example is “10”, so we will be starting the equation with ((A*256)+B)

Now look at the MTH field. It is separated in 3 four-character sections. The first 4 characters (0007 in our example) are the multiplier. These values are in hex so you must convert them to decimal.

Open up the Windows Calculator and makes sure it is set to 'scientific' view. Click the hex button and enter in the first 4 characters. Then click the decimal button. The value displayed is what you want to use in Torque. "7" is the result for this step. Repeat this step for the second 4 characters (0064 in our example) and you will have the divisor, which is "100" in decimal.

The final four are the trickiest. If you have an F, E, D, C, B, A, 9, or 8 as the first character -- as we do in our example -- then you will be subtracting this number. To calculate this, use Windows Calculator again and set it to Hex. Enter the value and click the 'XOR' key and enter “FFFE”. Click “=”, then click the decimal button and you will see what value you have to subtract from the equation.

If it doesn't start with one of the previous characters, then we will be adding this value.

The last four digits for the MTH piece are “FE70" which converts to “400" in decimal and will be subtracted from the equation.

Our example: (7/100)-400

The final thing to pay attention to is the RXF field, which is 032180000000 in our example. Pay close attention to the fifth character place, i.e. 0321->8-0000000. If you see a "4" here, then your data must be divided by 100. If you see an "8", then your data must be divided by 10. If it is 0, then disregard this equation entry.

Our example: 10

Completed equation: ((((A*256)+B)*(7/100)-400)/10)

OBD Header

Leave this field blank.

This is only a guide and not a bible. If Torque won't display data for a PID it can mean two things: you entered it wrong or your car doesn’t support it. Just because the ECU monitors a sensor does NOT mean the vehicle will support the PID to get that data.

If the "A" and "B" don't return results, then try the letters "E" and "F" in their place.

Note there are two ATF temperature sensors on our trucks... one in the pan/return and one in the torque converter. Both are technically available. I'll see if it is as simple as adding another PID with the letters changed, i.e. an "A,B" equation and a "C/D" equation.

Good luck. Please post up your results.

Deine Antwort
Ähnliche Themen