VCDS - Redir Fail

Andrew

A2OC Donor
England
At the top of VCDS output when I scan my engine module there is always the rather disconcerting message 'Redir Fail!', like this

Address 01: Engine Labels: Redir Fail!
Part No: 036 906 013 F
Component: MED7.5.11 5130
Coding: 00051
Shop #: WSC 02138
VCID: 122BEA385E4E8BD14F-5140
WAUZZZ8Z65N000662 AUZ7Z0D2613505

As a relative VCDS novice I have no idea what this means and I am guessing something is not configured correctly, but it is not right and I want to fix it.

I have not been too worried as a simple forum search 'Redir Fail!' Illustrates that the majority of VCDS output put up on posts on here contains this error string! On briefly digging a little a few comments from memory appear, 'doesn't matter', 'means it's a bit slower scanning', 'still reports fault codes', 'may effect measuring blocks' ..

Can someone explain in very simple terms about this and how to fix it.

Thanks - Andy
 
Andy, you have full VCDS so this shouldn't be an issue. When did you last update your VCDS software?

Edit: I realise that I run the VCDS software on 64-bit W7. If you are using a 32-bit laptop you may have an issue over file name length for some of the label files. In that case, identify the label in question and then edit the name to shorten it by 1 or 2 letters.

But certainly if you haven't done so, you should install the latest version of the software, and if necessary update the firmware in your lead. That should sort the problem.
 
Last edited:
Seems to be a file naming bug, but has no effect on the data, so just ignore it.

Techie explanation here: https://www.ross-tech.com/vag-com/labels.html
Mac.
Thank you for the link, it is most informative.

I now have a very basic understanding of why the message appears, a missing data file that contains text descriptors for the output channels within measuring blocks. Without it VCDS takes a 'best guess' at these text descriptors and seems to do a good job so as you say nothing really to worry about and also does not effect fault code reporting.

These data files, label files as they are called, are user contributed to the VCDS download library so it appears nobody historically has submitted a file for my Audi A2 FSI ECU above.

Thanks

Andy
 
Last edited:
Andy, you have full VCDS so this shouldn't be an issue. When did you last update your VCDS software?

Edit: I realise that I run the VCDS software on 64-bit W7. If you are using a 32-bit laptop you may have an issue over file name length for some of the label files. In that case, identify the label in question and then edit the name to shorten it by 1 or 2 letters.

But certainly if you haven't done so, you should install the latest version of the software, and if necessary update the firmware in your lead. That should sort the problem.
Hi Steve,

Thanks for your interest.

I have full VCDS and I use it on an old 32 bit Dell laptop running Vista. I do not know if this has any bearing on the 'Redir Fail' message but now reading the Technik link above I think not.

A few years ago Microsoft discontinued their free Essestials security software, so instead of paying for the likes of Norton etc. I nobbled the laptop so it now can no longer join the Internet and the laptop has been become a standalone dedicated to the running of VCDS.

From memory Vista handles long file names so need to shorten and if I did surely this would contravene the file naming conventions for these files and VCDS would not see it.

I run VCDS Rev. 17.1, so I am not that much out of date, but you are right I should get round to updating to current but to be honest I have not bothered as I am not convinced of any benefit. Will Ross-Tech have fixed any bugs or added enhancements relevant to a 20 year old A2?

Thanks again.

Andy
 
I run VCDS Rev. 17.1, so I am not that much out of date, but you are right I should get round to updating to current but to be honest I have not bothered as I am not convinced of any benefit. Will Ross-Tech have fixed any bugs or added enhancements relevant to a 20 year old A2?

VCDS 17.1 is quite old now (January 2017), and yes, Ross-Tech will have fixed some bugs. not just added coverage for newer cars. So it's worth updating.

The link that @audifan provided in the earlier thread - https://forums.ross-tech.com/showthread.php?2428-Redirect-Fail - provides practical information on file renaming, and is worth reading through to the end.

My Toshiba laptop is similar vintage to yours, has 4GB of RAM, and has been upgraded from Vista to W7 x64. I have never seen the "Redir Fail" that you suffer from.
 
I've checked back and I started out with VCDS 17.8 and had no 'Redir Fail' issues at that point. If you update beyond that (the most recent version is 19.6) you should be aware that it's not supported on Vista but should work. However it requires a firmware upgrade for your cable, which might be difficult to reverse, so is probably best avoided.
 
:(
I've checked back and I started out with VCDS 17.8 and had no 'Redir Fail' issues at that point. If you update beyond that (the most recent version is 19.6) you should be aware that it's not supported on Vista but should work. However it requires a firmware upgrade for your cable, which might be difficult to reverse, so is probably best avoided.
I have just been looking at the update to VCDS Rev. 19.6 before you replied. Okay I will give the update a go in due course but I do not think, now I understand a little more, it will cure the 'Redir Fail', unless in the last two years any user has contributed to the Ross-Tech label file library a file for this FSI ECU.

Suspect the update will work on Vista, if it does not I will move to W7 even though support for this ends after Xmas.:confused:

I am pleased to note the firmware updates only apply to the latest (Wifi?) available kit.

A few more points to add later.

Andy
 
Perhaps it is a Vista problem. I run windows 10 64 and have never seen the Redir Fail error. Wasn't the scan on a tdi? Could well be to do with file name lengths. In that case even an upgraded VCDS will not fix that. If you are happy using Vista and know the error does not affect the scans stay with Vista.
 
A simple forum search of 'Redir Fail!' will list three pages which are mainly posted VCDS output by members. A closer inspection reveals an awful lot posted by FSI owners who also have the ECU 036 906 013 F. (As well though not relevant another distinct group relating to ABS controllers) that come up the same.

I have read the the RossTech page on redirection posted by PlasticMac twice (it is hard going) and the way I read it there is a data file missing containing text descriptors of the channels monitored by VCDS with this particular ECU. RossTech argue historically over the entire vag range there must be thousands of different controllers and it is not feasible for them to provide all these files and invite users to contribute files. I wonder with the comparatively small number of FSI BAD engines in the great scheme of engines no user has contributed a file for this ECU in our A2 FSI BAD engines. Hope I am wrong and it is just a Vista bug and would love to know if anybody has run VCDS on an A2 FSI with ECU 036 906 013 F that does not come up 'Redir Fail'!!!!!!!

'Redir Fail!' By the way is short for Redirection Fail which relates to something called a Redirection Table which seems to be a work around if the raw data file is missing. I seem to missing this as well; all in the RossTech link.

As to the link Audifan kindly provided what seems to being suggested therein is a work around in case the file relevant to your controller is missing. If there is a likely candidate 'near' to the missing file rename it to the name of your missing file and everything will work (you hope)! For example I need 036 906 013 F and if a file for 036 906 013 E exists it seems reasonable to rename it to F, it will be near enough! Unfortunately the nearest I have is is 036 906 014 whatever that is. Hope this is a Vista bug.

Lastly I have no explanation as to why last Friday it did the same 'Redir Fail' when I scanned a member's TDI 75, which again suggests possibly a Vista bug.

Andy
 
Andy do you have access to, or can you borrow another computer ( laptop netbook etc ) running something later than Vista JUST TO TRY VCDS on. Personally I have done countless scans using Windows 10 64 and never seen the Redir Fail error, although to be fair its been on all engines EXCEPT the 1.6 FSI mainly tdi's and 1.4 petrols.

Do we have other members that have both VCDS AND a 1.6 FSI that have done a scan to verify either it is only a missing .lbl file, it is Vista or a combination of both. Also did you rename an existing file as a work around.

Perhaps Tom @timmus can shed some light on the differences between a 013E, 013F and a 014?

Somehow I don't think Ross-Tech are able to help any further.

Cheers.
 
Not sure if this is relevant now and not sure if it has been mentioned but I came across this while looking for something else G65 related ,ignore the normal text, its the bold text that I thought might be relevant.


The "Labels: Redir Fail!" text in the address 08 scan means it found a pointer to where the label file should be, but could not find the label file itself. In your case, it's looking for the file 8Tx-820-043-3Z.CLB. I did a bit of Googling and it looks like VCDS has files similar to that in at least two regional translated versions of VCDS, but not in English. That leaves one of two possibilities: there was a packaging oops and the English label file didn't make it into the installer, or the initial label file work was done in a foreign language and hasn't been translated into English yet.
 
Sorry chaps, I've not been following this thread, but have just noticed that I'm tagged in it.

As others have said, the Redirect Failure relates to VCDS's inability to find the label file associated with a particular controller.
VCDS is made by an American company who don't have access to every VAG vehicle. As such, they're partially dependent on their customers in Europe supplying the necessary information to construct a label file. The A2 was never sold in the USA, so the VCDS labels files for certain controllers are often missing. It doesn't mean that anything is broken and should be of no concern. The label file is just a tiny text document that outlines, for the benefit of the user, what information can be found in certain measuring blocks, what can be changed in certain adaption channels, etc.

As a hypothetical example...
The AMF engine uses an ECU with part number 045 906 019 G. I could meticulously figure out the purpose of every measuring block, every coding bit and every adaption channel and then submit it to Ross-Tech (the makers of VCDS). Assuming they trusted me, they'd publish the label file with the next release of VCDS.
A user with an ATL engine (TDI90) then connects to their ECU with part number 045 906 019 F. VCDS will, quite reasonably, say that no label file exists for that controller. The reality is that the label file for the AMF ECU will also apply, but Ross Tech can't be expected to know that.

The A2 TDI90 has a unique ECU; you won't find it in any other VAG vehicle. That model of car was made in small numbers over a period of just 18 months and sold in only a handful of countries. I wouldn't therefore be surprised if nobody had yet submitted the necessary information with which to construct a label file for the ATL ECU. The same goes for the BAD ECU (from the A2 FSI).

As I say, this is a hypothetical example. It may be that there is already a label file for the ATL's ECU; just don't be surprised when you find that not all the A2's controllers have associated label files; it's simply a consequence of owning a comparatively rare vehicle.

Cheers,

Tom
 
Last edited:
Thank you all for your contributions.

Thank you Tom(@timmus) for as ever your comprehensive answer and yes that was my take after investigation of the issue, which I am now confident is not an issue at all and can be ignored as nothing dire.

@steve_c , @audifan. I will upgrade both VCDS to current and Vista but knowing what I know now I expect it will not make a difference but good to be up to date, just got to overcome the inertia and get on with it. In fact this will be forced on me with Windows 7 MS support ending in the new year, probably move to Windows 10 and a three machine license, one for the old Dell laptop running VCDS (if it can support it), one for the desktop and one for a tablet.

@johnyfartbox. Had to read it twice to get my head round the information and yes it is saying the same thing, a missing data file.

Andy
 
Andy it never was a criticism, just found it strange you were getting the error on a tdi 75. As far as upgrading Windows is concerned, if any of your machines are running windows 7 or above you can upgrade them for free to Windows 10 by providing the valid product key. Unfortunately Microsoft never extended the offer to any one running pre Windows 7. You could leave the laptop on Vista and if you only use it for VCDS, then the only real issue is the long file names support that was never "retro fitted" to Vista. Any issues or questions give me a shout. I have looked back through my logs and the ONLY FSI I have done was for an airbag light reset and that log was not saved so can't tell if I had the redir fail error myself, all tdi 75 are error free in my logs.
I understand the missing .lbl file is not generally an issue for reading and clearing errors, my fear is someone could go into adaptation and change something silly that causes problems if no .lbl file to guide you or provide limits in values.
VCDS is a powerful programme that as you well know takes a lot of time and practice to get comfortable with. It is only natural that knowledge is only built up on the versions of A2 you scan. When we scan an unfamiliar type then we all have to be extra careful.
 
Back
Top