Hi guys,

 

I'm in the process of creating a vcds application. Some elements already exist in a few forms, on here and other places, maps of users etc. This is to bring them into one useable and useful place if the aspirations work out!

 

I'm just pencil on paper for the actual code data bits.

 

I've got to ask as I'm not really familiar with actually investigating codes on my car...

 

Here's some lingo I'm using which is shared I believe, but to be clear.

 

Manufacturer has many Models. Each Model has many Variants*. A Variant consists of a base Model, an optionSpec and an Engine.

 

*Variants can be exchanged for derivatives, just the former is easier to type.

 

---

Q1

Are fault codes unique over all models or at variant level?

 

That is 11503;made up code,  is not used for one thing in say a yeti and another in a citigo?

 

 

 

----

Q2

When searching for fault codes I am making an assumption on searches by fault code(id) and or title.

 

e.g. Search : engine faults or Search: 11502 to show results and related items.

 

Do you or would you search on any other attribute?

 

 

The plan is to build a living/knowledgable application around fault codes, tied back into the forums(not just briskoda) search too for discussion. 

 

 

Thanks.

 

Colin.

I can't answer either, Colin but maybe a quick email to BeartheBruce at Ross-Tech would get the answer to the first question?

For sure. The engineer in me says it would be daft to overlay codes between models, but a tingle down the spine tells me there is a chance.

 

Next up is figuring out the codes...

Fault : Code: Description

00728 : 02D8 : Potentiometer in the actuator for center-left G136

 

I prefered my made up ones 

DTC's (fault codes) are generic across models (and brands)

Personally I use the Ross-Tech wiki for troubleshooting DTC's as they also give you a pointer where to look to rectify the problem.

Q1

Are fault codes unique over all models or at variant level?

 

That is 11503;made up code,  is not used for one thing in say a yeti and another in a citigo?

 

 

The OBD2 codes are a set of codes that are required to be the same across all vehicle manufacturers.  Engine OBD2 codes usually start with a P (to denote powertrain), they usually only relate to a fault that could potentially affect emissions and can be read by any OBD2 compliant reader. Manufacturers have found that having OBD2 codes isn't quite enough so they have their own specific codes that fill in the gaps and they can only be read by manufacturer specific software.

 

If you look at the Ross Tech wiki:

 

http://wiki.ross-tech.com/wiki/index.php/Category:Fault_Codes

 

You can tell the manufacturer specific codes as they haven't got a P code associated with them.

 

Your made up 11503 code above (which has the format of a VW specific code) will be the same whether it is found in a Felicia or a Superb

 

 

Q2

When searching for fault codes I am making an assumption on searches by fault code(id) and or title.

 

e.g. Search : engine faults or Search: 11502 to show results and related items.

 

Do you or would you search on any other attribute?

 

 

When I use Google to search for codes I usually type in 'VW code 11503' and see what comes out.

 

As mentioned above the Ross Tech wiki is an excellent resource, but I have found that some of the codes that I have to find a solution for are not always listed on there.

Ooh how interesting!

Yeah as said before? The coding of an error is very much set in a standard ODB2.

In your example, the P stands for powertrain

But the number also means something like urgent or intermittent

You'll find decent fault code readers and Ross techs software display both the VAG specific code and OBD variant (if applicable).

Some obd fault codes can become slightly lost in translation especially if you cross brands I.e a p1234 code might translate slightly differently between a ford and say a Renault but still represent the same fault.