OBD Warning Lights: Are They a Legal Requirement?

Hello,

My former AFN (Air Fryer Network) only blinked with the heating element when there were actual defects.
Even when I once adjusted the RWG (rotary wing gyro) and then readjusted it correctly, the constant blinking stopped on its own after 2 or 3 motor starts.

Here's the translation:

Different from the Polo:

I once removed the glove compartment, including the airbag switch, and then briefly turned the ignition on.
The yellow airbag warning light stayed on for about a week, despite numerous engine starts, even though the switch was properly connected again.
Only by deleting the error did I manage to turn the lamp off again.

Now, the general warning light seems to be behaving the same way, because yesterday morning I accidentally drove off with the MAF sensor connector unplugged. I then stopped and plugged the connector back in, but the light still doesn't turn off .

Is this just an attempt to force hobbyists to take their cars to a workshop to have error codes cleared, even for minor, accidental mistakes (especially if they don't have a VAGCOM or similar device)? Or do any regulations (OBD??) require the error light to remain on until the fault is cleared?

It's also annoying because you can't identify any new defects as long as the lamp keeps complaining about old, already fixed issues.

Does anyone know if the "killer number" of 50 still applies (automatic deletion of errors that occurred for the last time more than 50 engine starts ago)?

Hi Ulf,

Your assumption about the OBD2 requirement is the reason for the strange behavior of the warning light.
The regulation only stipulates that there must be an error detection system in place, which can only be cleared through an OBD2 interface (or VAGCOM). This is intended to make any tampering with the engine control units immediately detectable.
In the future, even the software version of the engine control units (ECUs) will be able to be checked by the authorities (currently, some are already doing so). This is intended to prevent illegal chip tuning.

Unfortunately, I cannot tell you whether the deletion feature after 50 engine starts is still present.


By the way, a small note on the side:
It was precisely this regulation that almost prevented the last beetles from Mexico from being approved.
There was no parking sensor installed, and it cannot be retrofitted.
As a compromise, these cars now have to undergo an annual technical inspection (AU), despite having a catalytic converter and meeting EU3 emissions standards.

Bertil wrote:

The regulation only states that there must be an error detection system, which can only be cleared through an OBD2 interface (or VAGCOM). This is intended to make any manipulations of the engine control units immediately detectable. In the future, even the software version of the engine control units (ECUs) will be monitored by the authorities (currently, some are already doing so). This is intended to prevent illegal chip tuning. Unfortunately, I cannot tell you whether the deletion after 50 engine starts is still in effect.

Hi Bertil,

Thank you for your reply!

If you're serious about only being able to clear the error codes through an OBD2 interface (or VAGCOM), then the automatic clearing after 50 starts should also be disabled.
Because that would be a loophole to circumvent the regulation: repeatedly starting and stopping the engine in a deserted parking lot until the light goes out...

Regarding the software-based data extraction devices for the police: It's astonishing how many billions are probably being invested – but whether the expected or actual results can justify the effort...

First, hidden power boxes and 10c tunings will probably experience a resurgence .
And then, some clever people will find ways to disguise manipulated software from the regulatory testers. It's illegal, but who cares...

Hello!

I'm still having problems with my Climatronic system.
and as a result, I pushed my workshop to the limit.
Performance delivered!

'There's a big problem with my Polo, Ulf.'
'has written that when the mass airflow sensor connector is disconnected, the...'
'The warning light is on, but for me? The control unit doesn't care!!!'

No matter what I disconnect, whether it's the LMM connector or the oil pressure sensor, it's like this...
'minor issues' - the control unit doesn't store any error codes.
'The lamp isn't working either - no emergency mode or anything.'

I have now driven 70 km without the MAF sensor - nothing - absolutely nothing.
The car is at the workshop, but I don't think they can fix it there.
It felt like the service technician was putting me to sleep.
I hate it when you have to talk to customer service representatives who make you jump through hoops.
Electric shock is needed for them to move - grumble.

He was just surprised that the car didn't lock when using the remote key.
He honked the horn briefly, and then he opened and closed the car door ten times.
and left with a shrug.
allowing them to be activated as if a new key had been programmed.

One is always surprised.

TheBeer wrote:

However, there's a significant issue with my Polo. Ulf wrote that when the MAF sensor connector is disconnected, the "warning light" comes on, but in my case? It doesn't matter to the engine control unit!!! Bitte gib mir den deutschen Text, den du übersetzt haben möchtest. I have now driven 70 km without the MAF sensor - nothing - absolutely nothing.

What exact model, engine code (MKB), and year of manufacture is your car?

Is there anything related to OBD (On-Board Diagnostics) listed in your vehicle registration document?

Does the warning light at least illuminate briefly when you turn on the ignition (for a function test)?

Hi!

I drive a Polo 9N 1.9 TDI with 74 kW.
The engine is an AXR and the car was manufactured in February 2003.

I just checked the vehicle registration document, and it doesn't mention anything about OBD.
checked.

When I turn on the ignition, the light comes on.
Briefly, for 1-2 seconds. So, just put it in order.

It's possible to read the error memory with VAG-COM, but it doesn't really matter.
'No errors detected in what I'm doing.'

My Polo is so dumb .

I drive a Polo 9N 1.9 TDI with 74 kW.
The engine is an AXR and the car was manufactured in February 2003.

I just checked the vehicle registration document, and it doesn't mention anything about OBD.
checked.


Exactly...

ulf ASZ is already compliant with OBD2 (EU4) standards (approved in 2004), so it immediately and permanently displays any issues related to emissions.
Our ASZ (presumably a type of device or system) is from 2003, and it doesn't care about things like that at all.

CU Gremlin.

I drive a Polo 9N 1.9 TDI with 74 kW.
The engine is an AXR and the car was manufactured in February 2003.

I just checked the vehicle registration document, and it doesn't mention anything about OBD.
checked.


Exactly...

ulf ASZ is already compliant with OBD2 (EU4) standards (approved in 2004), so it immediately and permanently displays any issues related to emissions.
Our ASZ (presumably a type of device or system) is from 2003, and it doesn't care about things like that at all.

CU Gremlin

Okay, I understand that. What surprised me, though, was that...
...and no error is stored in the control unit.
This was clarified 3 minutes ago.
The workshop just called; it seems there's a defect in the memory.
...in both the STG 01 and the STG 08 modules, ensuring that no errors are logged.
can be, and the STG 08 of the Climatronik could not.
to be addressed

Both control units will be replaced, along with a wiring harness (the specific type is unknown).
It will take until tomorrow evening. So, more motorcycle riding in the rain .

Hi,

Quote:

I drive a Polo 9N 1.9 TDI with 74 kW. The engine is an AXR and the year of manufacture is 2/2003

.

The AXR engine is therefore "only" D4. If it met OBD2 standards, it would be EU4.

Okay, so... I had the opportunity to get a brand new ALH (Octavia) under my laptop earlier.

Allowed 3 weeks ago, WITH OBD registration and WITH MIL (Malfunction Indicator Lamp) illuminated in the cockpit.

I wanted to destroy the AGR right away, but unfortunately, I could only convince my colleague to drive around the block with a defective AGR. NO entry in the vehicle documents, NO error messages. Now I just need to convince him to deactivate the AGR (yes, he has seen all the pictures and still doesn't want to). I wasn't allowed to inspect the MAF sensor (variant with or without a protective tube?), otherwise he would have killed me .

EDC: 038 906 012 HA 1.9L R4 EDC 0000SG 4922


Maybe I can log a bit more information in the future...

noticeably in a direct comparison: my ALH runs much more robustly, but both turbochargers are whining loudly .


CU Gremlin.

Hmmmmmmm...
*speculation mode on*
The ALH probably only meets Euro3 standards, and the AGR (agricultural regulations) likely don't play a significant role, which might be the reason.
*speculation mode off*

Doesn't the ULF ASZ also only have Euro 3 emissions standards?

Sure, here is the translation of the text from German to English:

'Cu Gremlin'

Gremlin wrote:

Doesn't the Ufls ASZ also only have Euro 3 emissions?

Sure!

But, thanks to the OBD error messages caused by a faulty EGR valve, I at least figured out how to prevent it (-> by increasing the target air mass adaptation).

Perhaps this has already been implemented in the new ALH.
Or, despite being new, his LMM might be broken in such a way that the difference between the actual value and the target value does not exceed the error threshold.

But if I remember correctly, it sometimes takes longer than just "around the block" for the warning light to come on due to the EGR system.