VCDS: Error on Maintenance Interval Display

Hello forum,

I'm new to this forum and have only been the owner of the VCDS device from Kaufmann for a few days.
During the initial testing, everything worked well except for reading the service intervals. The German version gives me an error message: "No information is available for this control unit regarding the automated reset of the maintenance interval display," as shown in the attachment.
VCDS SW: RKS 17.8.0

With the English version, it works, at least no error message appears...

Perhaps this is a common beginner's mistake, so please excuse me...

Thank you in advance for your support.

Best regards,

Hi,

Please also pay attention to "Similar topics" below, I'm intentionally not posting the link because the information shown below seems not to be recognized.
"Technical articles and guides will be listed first (in black)."

Short version: Click on that and read the instructions on how to do it via the adjustment channels.

Best regards, Rainer.

Hello Rainer,

Thank you for the quick response.
The post that you are referring to, I "naturally" had already read beforehand, and another post also already deals with the topic.

Perhaps I'm just misunderstanding: It's not about resetting the service indicator, but about the fact that the VCDS assistant isn't showing me the current service data! And this only happens in the German version, not in the English version. The English version at least shows me the essential data.

I just don't understand that .

Thank you in advance.
Regards,

Long Waldi.

Okay, have you checked whether the instrument cluster (by directly clicking on control unit address 17) can be accessed via UDS or not?

Unfortunately, you don't specify which specific versions you tested (17.8.0 only refers to the VCDS version, and there are multiple data sets with updated control unit descriptions/labels). Regarding service routines, there may still be slight differences at this time, as the label files are not identical between the German and English VCDS versions, but rather prioritize models that are particularly common in each market.

By the way, there's a data update available for the German (merchant) VCDS in the customer account. Please test that. It's brand new, and there hasn't been a customer notification yet because I'm testing it myself.

Best regards, Rainer.

Hello Rainer,

Unfortunately, the control unit with address 17 uses the UDS protocol.
Unfortunately, even with the latest data, I'm still getting the same error message.

"The label file DRV\5G0-920-XXX-17.clb is obviously missing!"

My car: Golf VII Variant, manufactured in 2016.
VCDS -- A VAG/VAS emulator based on Windows, running on Windows 10 x64.
VCDS Version: RKS 17.8.0.1 HEX-V2 CB: 0.4407.4
Data as of: 20171117 DS276.6
http://shop.dieselschrauber.de
"Die Sonne scheint hell, und die Vögel zwitschern fröhlich. Ein leichter Wind weht durch die Bäume, und die Blätter rascheln leise. Es ist ein wunderschöner Tag, um draußen zu sein."
Vehicle type: AU-VW37 (5Q0)
Scan: 01 03 08 09 10 15 16 17 19 20 42 44 52 5F

Address 17: Control panel module (J285)
Label file: | DRV\5G0-920-XXX-17.clb
Part number SW: 5G1 920 751 B, HW: 5G1 920 751 B.
Part: COMBINATION UNIT 304 8311
Encoding: 07A411002380000801086A001400000000000000
Operating number: WSC 00028 028 00068
ASAM Dataset: EV_DashBoardVDDMQBAB 009051
ROD: EV_DashBoardVDDMQBAB_009_VW26.rod
VCID: 270A0B900F6DE6BF3A0-8072

No error codes found.

Quote:

With the English version, it works, at least no error message appears...

And why don't you simply use UDS and the individual channels? The link explaining how to do it is in the technical article...

Hello Rainer,

The reading process works for the individual channels, which is even more surprising considering that the assistant doesn't work.

Is there perhaps a software bug in the German version of VCDS?

I can live with the solution, but for a quick overview, I'll just use the English version.

Thank you very much for your help.

Best regards,

LangerWaldi.

No, there is no error; it's exactly as the dialogue you posted here shows. Just be patient.

Best regards, Rainer.

I'm also getting the same error message on my 2010 Polo 6R as the user "langerWaldi" is.

"When I try to reset the values manually using VCDS, it shows that the control unit (instrument cluster) has accepted the new values. However, when I turn the ignition off and on, it still displays 'SERVICE'."

I've always followed the same pattern for the past few years, and it's always worked, but today, nothing seemed to work at all.

I installed the latest German version of VCDS software, but the entire reset and coding menu, along with all the tabs, seems different than it did two years ago. I might be mistaken, though.

Has anyone sent a diagnostic report from an AI device to the manufacturer in the past 8 years? After 8 years, shouldn't this process be automated through service recalls? Or is it happening with the Skoda Fabia, where the system resets, displays that everything has been done, but then when you turn the key, everything is back to the way it was?

You can also remind me of the steps, like 17, then 10, and then... I'm not saying I was completely lost today, but I was kind of in the woods because it didn't work. I don't do this every day, but something went wrong today.

"Something else I noticed today is that I had a sporadic error message related to the trailer hitch. I tried to read the error codes and automatically clear them, but the errors were still there after another reading. It wasn't until I accessed the control module of the trailer hitch itself and cleared the errors there that the error messages finally disappeared."

Hi,

You've probably missed one of the adaptation channels; just take a closer look at them.

Okay, gib mir den deutschen Text, den du übersetzt haben möchtest.
/viewtopic.php?t=28677

Best regards, Rainer.

You were absolutely right, I forgot something, and it is this:

WIV:Rücksetzen der WIV .... OMG!

I still had the rest completely in mind, but this one... I think I'm getting old and forgetful.

However, this time there was something positive about it: I always experienced this "KEY BAT" problem on the MFA device immediately before the service indicator appeared.
Interestingly, this message has now also disappeared.
I don't understand at all what the "Key Bat" has to do with service resets, because, according to forum posts in another forum, it's supposedly a software error related to AI, where the voltage values used for detecting the battery status of the vehicle have an insufficient +/- range.

Well, whatever, the service is postponed, and I've managed to kill two birds with one stone.

With the current version of VCDS 18.2.0, an automatic reset is also not possible. I thought I already had the latest version installed, but it was previously 17.8.x, but now I have the newest version.

When I tried to fix a Fabia once, I probably also forgot to reset that point. It didn't work automatically back then either.

Have a lovely Sunday.

Thank you for the feedback .

"Key Bat" I would translate as "key battery." How far does the remote control still work?

Best regards, Rainer.

Yes, many people think that the problem is with the battery in the key fob.
I once read about this in a forum. The problem was discussed in detail, and it was traced back to the car's control unit (ECU), software, or firmware. It seems that on Polo, Seat, and Skoda platforms from 2010, this issue tends to occur after 6-7 years. Apparently, it's related to a voltage parameter that, in older car batteries or when using the second key, can lead to the "Key Battery" error message.
The friendly technician will need to install a modified software update in the AI system to prevent the error from recurring, and this will cost around 30 euros.
Apparently, there's also a technical instruction (TI) document about it, but I can't find the forum where I read about it anymore.

I also told my friend about this and asked him to look into it, specifically regarding the software, but he's not familiar with it, so he doesn't know about this AI software update and the error it's causing.

The strange thing about this error is that it only appears after 6-7 years; before that, the problems are not known or have not occurred. It only happens when using the spare key, which is quite curious. However, it's not related to the battery in the key fob; I've tested both batteries and even replaced them.

The wireless range depends on the environment, including interference. In everyday situations, it's typically 10-30 meters without issues.

Just type "VW Key Bat" into Google, and you'll find tons of results for people who have it.

[Translating...]

http://www.polo6rfreunde.de/index.php/Thread/7253-Anzeige-KEY-BAT-Schl%C3%BCssel-Batterie/?postID=427121&highlight=schl%25C3%25BCssel%2Bbatterie#post427121

Thank you for the information!

So, as I understand it, it's the comfort control unit in conjunction with certain pocket manufacturers, and the comfort control unit is supposed to receive an update.

It would be interesting to know the VW technical information (TI) number for this issue.