[Audi TT Malta]

Ive bought the plug and play plug by fakra from ebay could you please lead me what to buy and my audi is a 2001 model. Is yours the same?

Sent from my iPhone using Tapatalk

 

[Audi TT Malta]

Yellow TT my audi TT 2001
Could you lead me what can i do with my rns-e
This can bas adaptor where can i buy it?
And can you give me some information about it.
Sorry but i need help on this

Sent from my iPhone using Tapatalk

 

[Audi TT Malta]

The console fitted perfectly as i had to cut some pipes of the a/c. What is confuseing me is that the rns-e wont illuminate the buttons when i turn the lights on and after an hour playing the radio goes off. There is something wrong with the wires throught the radio. Can anybody help pls

Sent from my iPhone using Tapatalk

What year is your TT ? sounds like it is a pre can bus car 2001 or earlier as these are the same problem you get when fitting a late can bus radio to a pre can bus TT
If this is the case I got a can bus adaptor from German eBay

Yellow_TT pls help

Sent from my iPhone using Tapatalk

 

[Chapster]

How did you code RNSE to car any help would be appreciated

John

 

[Nomadiccustoms]

There is a company that makes iphone 6 plus, iPad mini dash kits.

 

[pcbbc]

Just completed my retro install. Here's a picture:

The double DIN fascia is made by a guy called Mani in Germany, and is an extremely professional product. It comes completely upholstered (in a very close match to the factory TT interior trim), and as close to a plug a play solution as you can get. The only work required is the actual installation and obviously the small modification of the TT a/c ducting to accommodate the larger unit. It's also available in a variety of different formats to suite different navigation units.

My donor RNS-E is from an A4, a 2010+ PU unit HW03.

I have just about everything working with the unit coded for A4:
* Auto on/off via ignition
* Dash illumination and auto day/night mode with side lights
* Bose (original install was Chorus unit with Bose)
* 6 disk auto changer (again original factory fit install with the Chorus)
* RNS-E clock settings obtained from DIS
* Navigation directions display in DIS (Need to code instrument cluster for navigation)
* After-market 3rd party Bluetooth kit via TEL IN/MUTE on RNS-E

The only thing that is currently escaping me is the speed sensor signal. In the RNS-E diagnostic screens under Nav Sensors, it is showing all zeros for the speed sensor data. I've narrowed this down to one of two things:
1. Either the RNS-E is missing v-signal line on B3. Unless I'm mistaken the Chorus didn't have a v-signal, even though it has GALA. I'm assuming the Chorus got it's speed data over CAN. If this is the case, then I believe I need to wire B3 to the v-signal pin on the back of the instrument cluster?
2. Or the RNS-E is attempting to read the speed data over CAN, which I think requires a CAN Gateway does it not? And the 8N doesn't have a gateway....

Also, the e-bay A3/A4/A6/TT/AllRoad to Chorus/Concert harness I purchased was supplied with RNS-E B3 connected to the old BOSE pin of the Chorus plug III pin 1. And that pin can be v-signal on some head units (without BOSE), can it not? So that makes me think that it's probably option 1 above?

Has anyone attempted this with a RNS-E 2010+ PU unit?
Does anyone know if this unit expects v-signal over CAN or via the dedicated v-signal line? (when coded as A4)
What's the situation with speed sensor data on the pre-2010 units?
Am I perhaps missing some coding?
Adaptation channels 1 and 2 are obvious candidates. But at the moment it appears the unit isn't getting any speed pulses at all...

Any help appreciated - thanks guys and gals.

 

[Ian_W]

Wow, not a mod that I would say would generally interest me but that looks bloody great! So factory 8) 8)

 

[pcbbc]

Wow, not a mod that I would say would generally interest me but that looks bloody great! So factory 8) 8)

Thanks Ian, Exactly the look I was going for - so it means a lot.
TBH almost all of the credit must go to Mani for all the work he's obviously put into designing and making the consoles. Not cheap, but 100% worth every Euro.

Now if only I could work out how to get the speed sensor to work... Anyone?

 

[ReTTro fit]

Hi mate
It's a long time ago since I used to retro fit stuff on a regular basis but from memory when I used to install a rns-e in a 8l S3 it was the same issue
In a S3 you needed to install a unit from an A4 ( like you ) but coded it as an A6, that got round everything mate
But that was a mk1 rnse

A ml 2 rns-e or a later mk1 for an A4 requires canbus

A way round it is to down grade the sw to 150 and code as a A6

If it was me I'd just run it from your cluster mate, job done then

Nice install mate, well done

On iPhone using Tapacrap

 

[pcbbc]

In a S3 you needed to install a unit from an A4 ( like you ) but coded it as an A6, that got round everything mate

Thanks for your input - Actually I tried that. But it didn't help...

Another problem is that a 2010+ RNS-E wont actually accept the coding as a A6, unless you first downgrade to FW 150. Once set as A6 with FW 150 you can re-flash to the latest firmware and it keeps the A6 coding?! But it's anyone's guess what the unit is actually coded/doing in this case!
Edit: Perhaps I didn't read your post fully, as re-reading I see you've already told me that!

Plus the A3/S3 has a CAN Gateway (according to Ross-Tech) and the TT Mk 1 8N doesn't. My (admittedly very limited) understanding says that if the RNS-E is getting speed signal from CAN Bus then I think it must be going through the Gateway to get it?

On the other hand it is possible to fit a 2010+ PU RNS-E to a 8E/8H A4 (I see installers offering this as a retro fit service), and those A4 models don't have CAN Gateways either. So my assumption (and hope is) is that when coded for an A4 it must use v-signal?

I suppose suck it and see. Nothing to be lost except time removing dashpod...

 

[ReTTro fit]

Correct the earlier b6 a4 had k-line so must of worked off v-signal
BUT with a 2010 pu unit what would it be coded as ?
What would the FW have to be ?

The earlier A3 8l (2001 ) example, didn't have can gateway mate, The canbus for infotainment connects directly between the RNS-E and the cluster.

Where abouts are you mate ?
I don't mind helping, I love doing stuff that's not ment to be done aswell ! Lol

On iPhone using Tapacrap

 

[pcbbc]

Ok 1wheelonly, that's a very generous offer - and I might just take you up on that if I get stuck with this.

Some more research....

From this post it seems to confirm that for a PU unit coding for A6 is the only way to read speed from v-signal (B3) and reverse from RFSL (C2). A4 coding always reads over CAN, which would require installation of a suitable gateway (which could be done if all else fails). Even then the A6 coding will only work for certain hardware versions before they removed the required input circuitry from the RNS-E (bummer). That's presumably why later firmwares disallow coding of A6 once they realised it was of no more practical use for the models still in production and using the PU version.

Also HW02 is recommended by that thread, but my unit is HW03. But at least it still has the relevant pins labelled on the sticker, which makes me hopeful. The last post on this French forum page has a side compare between a HW04 and HW06 units labels showing the pins have definitely been deleted on newer hardware.

My first test is going to be to hardwire RFSL to 12v and see if the reverse is detected as active on the engineering mode Nav Sensor page when coded as A6. A lot easier than removing the dash pod to get at v-signal! Mind you, dash pod has got to come out for repair at some point too, as of course it's beinging to go faulty as they all eventually do.....

 

[ReTTro fit]

Even RFSL (C2) was removed on certain 2012 & 2013 units
I found that out when fitting my reverse camera

C2 is not a reverse input mate, it is just a switch pin and the unit needs to be coded for TV for it to switch over

On that post he was using a can gate reverse module to switch the screen ( which doesn't work on the later models )

If you read on Craig removes the module and uses the switch pin

Here's mine

On iPhone using Tapacrap

 

[pcbbc]

Even RFSL (C2) was removed on certain 2012 & 2013 units

Yes. At the same time as the v-signal input (B3) if you read the French forum posts (via Google translate) and if the labelling of the pins on the sticker is anything to go by....

C2 is not a reverse input mate, it is just a switch pin and the unit needs to be coded for TV for it to switch over

Errr.... Not sure I see the difference? If it requires coding to make it work (and coding is implemented in software after all) then it must be some kind of "input" for the software to be able to decide to "ignore" when not coded correctly (and when you don't have a camera of course!). And if not an "input" what is the point of the REV OFF/ON display on the Nav Sensor diagnostic page if not to display the state of that "input" (when coded for A6 and therefore by implication to use hard wired inputs, when still present in the HW version)?

Here's mine

Will take a look. Thanks!

BTW: What HW version do you have?

 

[ReTTro fit]

No mate you miss understand me, coding is required to have TV mode, TV mode is an input on the 32 pin av plug

Pin C2 ( rfsl ) is just a switch, a NC circuit that when 12 volt is added switches / over rides the screen mode

On iPhone using Tapacrap

 

[andersmandersen]

Hi guys. i am thinking of making this in my TT.
Where do you guys place the cd changer to the RNS-E ? do it fit in the original place or should it be in the glove department?

 

[Sandy]

Looks good although I'm personally not into traditional radio units. I would prefer a tablet set up with a DAC and an amp (unless Apple ever bring out there own double din unit).

One day I'll get around to fitting such a setup with this :

see that in a lot of posts :lol:
One day ay?.

 

[Sandy]

Just finished this last week.....

The frame was bought from satnavsystems (the last one they had) and came wrapped in leather.

Had a bit of a nightmare with this as the audi unit would not fit with the leather so ended up stripping off the leather and wrapping in carbon wrap instead.

I also had to do quite a bit of modding air net supply pipe in order to fit the larger head unit in place.

Next step will be to get the mk2 steering controls linked up and also the dash pod display. :wink:

That looks brilliant Darthawkeye [smiley=thumbsup.gif]

 

[pcbbc]

Sorry, forgot to update you all with progress on this mod...

One little niggling problem with the RNS-e retro in the MK1 is that the RNS-e firmware was never tested with the MK1 red DIS display. The command set is basically the same as the MK2 display (the MK2 employs internal pixel doubling to get the extra resolution over the MK1 DIS), but as a result of a few small technical differences in the implementation and capabilities, there are a couple of bugs:

1. If you press the stalk button and go away from the DIS navigation page (to view trip computer for example), when you later return; the navigation page is blank. You must stop and start navigation on the RNS-e to get the navigation directions to resume displaying on the DIS. This is due to the RNS-e not listening for the correct "page changed" flag coming back from the cluster (its different between MK1 and MK2 clusters).

2. The DIS display appears only partially, or is corrupted, for many of the direction diagrams. Especially those with more complex layouts (e.g. Roundabouts). This is due to an internal buffer overrun in the number of 8 byte CAN packets that can be sent to the DIS for a single message block. The MK2 cluster has a larger buffer capability (more packets per individual message can be sent).

Turns out these are fairly simple limitations in the CAN protocol between MK1 and MK2 clusters, and not too hard to fix with RNS-e firmware patches. i.e. It's not down to a fundamentally different command set differences between cluster generations (DIS nav direction display was after all an option on the MK1, but with the factory fit basic navigation in the trunk and never RNS-e), but rather some small misunderstandings and limitations in the underlying messaging protocol.

Therefore the above can both be fixed with a few tweaks to the RNS-e firmware. Before and after video here.

Also I went on and changed the MI/KM and AM/PM labels to a more aesthetically pleasing lowercase. So now my RNS-e is no longer SHOUTING at me about time or distance to destination on the DIS. These final patches also suitable for my MK2 TTS.

 

[hansdevogel89]

@pcbbc

Intestering, you experiencing the same 2 DIS related issues as me with 2013 rns-e pu 193g in mk1 tt
Do you have a mk1 rns-e coded to A6 or something else? a4 perhaps?

in a few weeks i will try 2010 193B, which @ FW 0150 will code to A6 4B (which has physically the same lcd display, resolution and protocol as the mk1 tt magneti marelli clusters. I think this will solve all dis related issues.
Besides it will accept GALA speed signal instead of over CAN bus