Forums

Guest
Welcome Guest, posting in this forum require registration. Username Password Remember me

Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » Mapping VW DTCs in scan tool with the raw data

Pages: [1]

Author	Topic: Mapping VW DTCs in scan tool with the raw data

soumyasen92

Member
Posts: 37

Mapping VW DTCs in scan tool with the raw data
on: March 8, 2019 (GMT)

I scanned a VW Golf TDI 2015 using a scantool (at a workshop) and it gave the following 2 codes –

Engine module: P0103 – Mass Air Flow (MAF) (G70): Signal too High
Instrument cluster module: B103E – Fuel Level Sensor 1: Short to Plus

Then I hooked my laptop (PuTTY and elm327) to read the raw data and got the following data –

For engine:
Sent: 19 02 04
Reply: 7E8075902FF001CA4AF

For Instrument cluster:
Sent: 19 02 04
Reply: 77E07590299903E1208

Can someone please help me find out how can I arrive to the fault codes from the corresponding raw data? Next time, I can find out the faults myself instead of going to the workshop.

cintakc

Member
Posts: 1667

Re: Mapping VW DTCs in scan tool with the raw data
on: March 8, 2019 (GMT)

07590299903E1208
903E = B103E
1208 – most likely an error sign

soumyasen92

Member
Posts: 37

Re: Mapping VW DTCs in scan tool with the raw data
on: March 13, 2019 (GMT)

Ohh thanks
What about the fault from engine module?
075902FF001CA4AF
001C = P001C
A4AF – most likely error sign as you said
But the fault P001C doesn’t match with what has come from the engine module (P0103)

cintakc

Member
Posts: 1667

Re: Mapping VW DTCs in scan tool with the raw data
on: March 13, 2019 (GMT)

Yes, the P001C error does not coincide with the P0103 error, I think it is necessary to check everything once again
both of these errors indicate increased voltage in different circuits – “High voltage in the electrical circuit……”

soumyasen92

Member
Posts: 37

Re: Mapping VW DTCs in scan tool with the raw data
on: March 13, 2019 (GMT)

P001C – Camshaft fault
P0103 – MAF fault

I logged it several times, so I am quite sure that this data is correct.

If I may ask, the decoding that you did (and it matches with 1 fault code), is it some standard way of decoding the codes or does it vary module to module?

cintakc

Member
Posts: 1667

Re: Mapping VW DTCs in scan tool with the raw data
on: March 14, 2019 (GMT)

The engine control unit can support two diagnostic protocols, the first is the standard EOBD protocol and the second factory protocol
in the standard EOBD protocol, the command for reading errors “03”, in the factory protocol, the command for reading errors “190204”
it is possible that the set of supported error codes may be different for these protocols.

soumyasen92

Member
Posts: 37

Re: Mapping VW DTCs in scan tool with the raw data
on: March 15, 2019 (GMT)

so is there a way of finding how to come up with the fault code from the raw data? Any particular resources you have in mind?

Also it is quite weird that instrument cluster module is giving data with a particular type of decoding, while engine module doesn’t work. Shouldn’t the decoding for a particular mode (say 19 here) be the same for all modules?

cintakc

Member
Posts: 1667

Re: Mapping VW DTCs in scan tool with the raw data
on: March 15, 2019 (GMT)

You can read in international standard ISO 14229 2006E in section 11.3 ReadDTCInformation (19 hex) service

soumyasen92

Member
Posts: 37

Re: Mapping VW DTCs in scan tool with the raw data
on: March 18, 2019 (GMT)

I gave it a read, but couldn’t find anything to decode this raw data

cintakc

Member
Posts: 1667

Re: Mapping VW DTCs in scan tool with the raw data
on: March 18, 2019 (GMT)

Table 252
Table 259 (continued)

Pages: [1]

WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.032 seconds.

Forums

Forums

Guest