Can't code MK2 RNS E as "5" A6 ?

Steve, just been out to check mine and 8 satellites sounds the norm. The symptoms are exactly like when I installed mine and forgot to connect to the gala signal.

I had to connect to the wire at the rear of the clocks as its a later car like yours with no gala signal at the stereo end.

Are there any fault codes on the instruments or ABS? Probably not but worth checking a full scan (although I am sure you probably have in your hunt for the issue!). Its a shame you are not nearer as would gladly swap mine into yours to test and vice versa.

Good luck
 
PaulA2 said:
Steve, just been out to check mine and 8 satellites sounds the norm. The symptoms are exactly like when I installed mine and forgot to connect to the gala signal.

I had to connect to the wire at the rear of the clocks as its a later car like yours with no gala signal at the stereo end.

Are there any fault codes on the instruments or ABS? Probably not but worth checking a full scan (although I am sure you probably have in your hunt for the issue!). Its a shame you are not nearer as would gladly swap mine into yours to test and vice versa.

Good luck
Click to expand...


Hi,

Thanks Paul.

I think I will take the cluster out and see if I can spot anything amiss.

No fault codes unfortunately and thanks for the input.

Steve B
 
When you downgraded it and recoded it, did you do all of this in situ? Have you ever reset the RNS-E since the recode?

A simple reset may fix it if you haven't done so or disconnected the power to the RNS-E
 
Hi Craig

i did a reset via VCDS channel 111.
So it is really looking like it is a hardware issue.
Thanks for the input.

Steve B
 
GOOD NEWS (In fact GREAT news)

My RNS E is now fully functioning and working as it should.

Guess what I did to fix it?


ABSOLUTELY NOTHING !!!!!


I decided that since all of the wiring (including the speed sensor) was as it should be, and the coding of the Sat Nav was exactly as it was before, there could not be anything else that could cause this.

So I had clutched at every straw there was to clutch at, except one!! There was only one thing I hadn't tried and that was to simply drive the car for long enough to allow the system to calibrate its speed.

After 10 minutes of driving, it was still not working but it suddenly changed the location to the right road, then froze again. After a few more minutes it again moved the position to the correct road. Bit by bit it was correcting itself and becoming more and more accurate.
After 30 minutes it had finally started acting as it should.

So now it is once again, fully operational.

I new that the car would calibrate its speed, but the VCDS instructions state that you have to set the circumference of the tyre size to 0 to force a recalibration. The controller would not accept a size of 0 (so effectively the VCDS on screen instructions are wrong when dealing with an A2 / RNS E combination).

I used the tyre size calculator to enter the correct circumference in mm and thought that was it. Because I didn't enter 0 I had assumed (dangerous!) that it would take that measurement and it would not try to recalibrate.

That was my mistake.
It was compounded because of the way that the car position was frozen and I assumed (again) that if it was merely recalibrating it would still move at least, but no.

So the cure was to just drive the car for 20 minutes or so, and because when it was not working I was merely driving around the block a few times, this was obviously not long enough for it to calibrate!!!!

This is a huge relief because I was starting to doubt my own sanity.!!

Nice to have a happy ending (no cost too)

Steve B
 
Last edited:
dan_b said:
Moral of this story - if it ain't broke leave well alone!
Click to expand...
Hi Dan
i agree with that moral.

But it doesn't apply here.

I was trying to find coding that would be useful to others too and in doing that I must have triggered a separate problem because I didn't change any coding of the RNS E, i did not change any VCDS codes at all, I was merely browsing.

I believe I may have actually caused the issue when I took the RNS E out for a long period (twice) when I borrowed the heated seat switches from mine to test out the heated seats in my grandson's A2.

Whichever one of these two it was I was not playing, or "fixing something that was not broken" and I would do the same again.

But it as I say that moral is a good one.

Steve b
 
Yes, it is.

But the unit they fitted originally failed and so rather than using a secondhand one they used a brand new one and that is why it is a "D", but it all works in an A2 of course)

But I do not know what the internal differences would be on the "D" version anyway.

Steve B
 
Last edited:
I had also some issues with the tyre circumference adaptation.
It was originally 1990mm or something (it's an A3 unit). I then put 1870 (the value for 205/40-17), but the unit never accepted this value to be saved, and it put "1" instead.

craigyb said:
A simple reset may fix it if you haven't done so or disconnected the power to the RNS-E
Click to expand...
That's what I've found with mine.
That's after I disconnected the quadlock and reconnected it, that all worked fine (DIS, etc.)
 
And thank you to Matt (wilco) for sending me the software disc.

I now have my SDS functions back as well.

Cheers
Steve B
 
You must log in or register to reply here.
Back
Top