Reduction system, bank 1 / SCR NOx catalyst, bank 1

Skoda Yeti 2.0 TDI DSG 4x4, manufactured in 2017 - the last of its kind.
Status completely okay after 30,000 km, chapeau chapeau...
The engine control unit is only reporting two error codes.
I think the amount of AdBlue is too low, don't you?
Went for the mandatory inspection today, I'm curious about what error codes he will come back with.

Error codes found:
20553 - Reductant system, bank 1.
P204F 00 [096] - Malfunction.
Sporadically - unconfirmed - checked since last deletion.

15733 - SCR NOx catalyst, bank 1.
P20EE 00 [096] - Efficiency too low.
Sporadically - unconfirmed - checked since last deletion.

Hi,

Quote:

20553 - Bank 1 reduction system. P204F 00 [096] - Malfunction. Sporadically - unconfirmed - checked since last deletion

Shot in the dark:
- Was if someone filled it with something other than AdBlue?
- Blockages in the AdBlue injection system? Check the fuel injector at the catalytic converter...
- Damage to the AdBlue injection system caused by martens?

Best regards, Rainer.

In the workshop, they said that they couldn't find any errors in the memory - and they had never seen anything like it, with these kinds of errors .

Actually, after the visit to the workshop (the first inspection at 30,000 km), there were no more errors in the engine control unit.
Okay, so it was also previously in the main menu under "Everything is OK."

Let's wait and see if he comes back.

I have only ever refilled AdBlue myself, and only at the gas station using the designated pump.

As I said, just wait and see if there's any new information in a few weeks.

I've also seen this issue with SCR catalysts even with relatively low mileage, caused by contamination from sulfur in fuel from Russian sources. Once you run the engine at high speed to get it really hot, or use a forced regeneration cycle for the DPF, and that's it.

The situation now is that the error code in the fault memory doesn't clear after the regeneration, unlike what was described a few months ago.

Also, yesterday night, on the way home, the check engine light came on. Stopped immediately and read the error codes, and it was only that specific one.
20553 - Reductant system, bank 1.
P204F 00 [096] - Malfunction.
inside. Okay, I drove home slowly and on Monday I went to...
Workshop. Now they can't deny it anymore.
Let's see...

When and who last refilled the AdBlue? Since there are no other entries in the error memory, a blockage cannot be ruled out.

Only me, and only at ARAL truck fuel pumps or TOTAL car fuel pumps - both located in Karlsruhe, so not abroad.

The NOx sensor was replaced - 5 days behind schedule - otherwise no problems - under warranty - no cost.

Hopefully, this will permanently fix the error.

Unfortunately, no...
For about 3 weeks now, I've been seeing the same error codes in the diagnostic memory as I did a year ago when this problem first started.

It has been approximately 4000 kilometers and 2 months since the NOx sensor was replaced.

Since I don't check the error memory every week, I can't say exactly when it started happening again.
After the sensor was replaced, I checked it every week for 2-3 weeks, and there were no entries.
Okay, stop now.

It's also the case that the overview says "everything is okay."
It's only when you look closely at the engine electronics that you'll find the entry.

I will only receive the sensor replacement when the motor symbol is permanently displayed on the amateur control panel.

hm....

hkss wrote:

I will only receive the sensor replacement when the motor symbol is permanently displayed on the amateur control panel.

I wouldn't agree to that. There seems to be a mistake. Whether it is displayed on the instrument cluster or not doesn't matter.

The fact is, something is broken.

So, I went there again today.
As I said, a warranty claim would only be valid if there are errors in the control panel or a "limitation" in the operation.
BUT... my warranty is expiring soon - it's only for 50,000 km and five years - whichever comes first.
My question was whether this wasn't a rework of the previously performed repair, which, as you know, was not successful. No, the error was gone (from the control panel - and it still is to this day).
Apparently, I'm the only one with this NOx error code. Well, let's see.
I'm going to order one of those sensors and put it in my car.

Enrollment letter to management, including a complaint about defects.
Please provide a VCDS excerpt.
Therefore, it is possible to prove when the defect reappeared.
The deadline has been met.
Then wait, and if the problem occurs again later, you'll have your proof for the lawyer.

Best regards, Gnasch.

Gnasch also suggested a particular course of action.

Because if you later incur high costs, even though something is already defective now, you'll be in a difficult situation once the warranty expires.

Best regards, Rainer.

Registered mail with return receipt. It seems that's the only way to do things these days. Whoever writes, remains.

Okay, so I went back to the workshop again. I left the car there for 3 days, along with printouts of the logs from VCDS, which clearly show that the error code reappeared even after the sensor was replaced, and it reappeared again just 5 days ago.

At Skoda, they emphasize that VCDS is not the ultimate authority. Only what the Skoda diagnostic tool says matters, and currently, there is NO error entry. There was only an error entry when the warning light illuminated on the dashboard, and then tests were performed according to the repair manual (quality measurement of AdBlue, quantity measurement of the injector, and ultimately, the NOx sensor was replaced – as stated in the repair manual). That's it.

"My suggestion to look into the data of the engine control unit is not valid," or "it's not possible," or "we've never done that before," or "why would we want to..." etc.

I would appreciate it if you could provide me with the output from the diagnostic device that indicates there are no error entries.

Hi,

Hypothetically, you can print a blank error memory with any diagnostic device – provided you clear it beforehand and you know that it will take some time for the error to reappear.

The easiest way is to go to another workshop and have them simply read out and print the error codes, after you know what they are.
Ideally, somewhere completely different.

Best regards, Rainer.