[pcbbc]

Hello , anybody try solder missing parts from board RFSL contact on RNS E PU? or maybe just change board from older RNS E ? RNS PU software support RFSL signal ? Thank you for advance

User andy55070 on here transplanted a 192 backplane into a 193 unit. He now, after quite a bit of effort, has this working without any external hardware.

He tried previously without my patched firmware and was unsuccessful. I have no idea why that was, personally I suspect incorrect wiring or testing the first time (sorry Andy). There's nothing I've changed in the patched firmware that would make a transplanted backplane "magically" work.

You'll have to ask Andy if you want any more details.

Soldering the missing parts would be possible, but tricky. There's a lot of small SMT parts, and what are the values?

The dual voltage comparator IC (TA7522) that conditions the signals was discontinued by Toshiba.
Datasheet
Normally you'd just replace with an equivalent part. Unfortunately the Toshiba part has a non-standard pinout. I've not been able to find an equivalent.

Pure conjecture, but I suspect this was the sequence of events that resulted in the component removal:
* They weren't needed any more (all vehicles in production when the 193 units came out were using CANBUS for the RFSL/VSIGNAL but this point)
* The units continued to get manufactured until the supplies of the TA7522 were exhausted
* A readily available alternative part was not available
* Rather than re-spin the board layout for a different SMD footprint, the components where just omitted

 

[andy55070]

Hi all,
After many months and head scratching and help from pcbbc, i finally got the 193 unit to switch in reverse to enable the rear view camera to work and V signal. Story from the start I wanted the 193 unit due to better screen resolution, black surround and chrome knobs. Audi stopped populating the rear panel with hardware. I sourced an new 192 backplane from a guy in Germany (new /old stock) and carefully disassembled the RNSE. Fitted and on first try did not work so nearly gave up. Sourced an old 192 RNS-E complete unit to eliminate the wiring and found that all was good and switched with 650 SW and the 192 unit when fitted. So back to the drawing board after several cuts of firmware from pcbbc finally decided to give it another go. Fitted the Multimedia adapter wired via relay and fitted the camera into one of the rear number plate lights on the roadster. All internal trim came off for the second time and completely hard wired this time. By this time I had the Arduino from pcbbc and thought great finally I will solve this. I did the first install without the Arduino and it worked, so fantastic, ferrite bead also solved the interference. All in all not an easy job but extremely satisfying now that this conversion is completed. So yes the 192 backplane can be changed successfully in a 193 unit as long as the hardware is there. Running 260 SW on the 193 unit.
Happy to answer any questions

 

[wiltrix]

Hi all,
After many months and head scratching and help from pcbbc, i finally got the 193 unit to switch in reverse to enable the rear view camera to work and V signal. Story from the start I wanted the 193 unit due to better screen resolution, black surround and chrome knobs. Audi stopped populating the rear panel with hardware. I sourced an new 192 backplane from a guy in Germany (new /old stock) and carefully disassembled the RNSE. Fitted and on first try did not work so nearly gave up. Sourced an old 192 RNS-E complete unit to eliminate the wiring and found that all was good and switched with 650 SW and the 192 unit when fitted. So back to the drawing board after several cuts of firmware from pcbbc finally decided to give it another go. Fitted the Multimedia adapter wired via relay and fitted the camera into one of the rear number plate lights on the roadster. All internal trim came off for the second time and completely hard wired this time. By this time I had the Arduino from pcbbc and thought great finally I will solve this. I did the first install without the Arduino and it worked, so fantastic, ferrite bead also solved the interference. All in all not an easy job but extremely satisfying now that this conversion is completed. So yes the 192 backplane can be changed successfully in a 193 unit as long as the hardware is there. Running 260 SW on the 193 unit.
Happy to answer any questions

Thank you for info, i have old 192 RNS E unit for parts, with all components on rear pcb,if i good understand i can swap pcb in to 193 RNS E PU with update software 260 and everything is fine ? 192 and 193 rear pcb is different :? one more question, My project now is put RNS E PU on audi 4B platform. After update 4B instrument cluster work lcd info with RNS E PU? thank you for helping

 

[pcbbc]

Sorry for the delay replying. Usually best if you PM me to alert me if I don't reply...

Thank you for info, i have old 192 RNS E unit for parts, with all components on rear pcb,if i good understand i can swap pcb in to 193 RNS E PU with update software 260 and everything is fine ? 192 and 193 rear pcb is different :?

They are different, but compatible for transplants according to andfy55070.
You'll need him for any more details as I haven't tried this procedure myself.

My project now is put RNS E PU on audi 4B platform. After update 4B instrument cluster work lcd info with RNS E PU? thank you for helping

4B = A6, correct?

As far as I know my firmware has fixed all of the outstanding bugs in 193 units with A6 coding. This is going by the things I needed to fix to get it to work on the TT 8N platform which also uses the A6 coding. But I've never actually had any dealing with an A6 myself.

These bugs weren't ever fixed by Audi because the 4B A6 was long since discontinued by the time the 193 PU came along. let me know if you think I've missed anything and I'll be happy to look into it.

 

[Kryton]

Sorry I've still not got round to updating mine. I will sort & send beer tokens at some point before the clocks change & evenings are dark. Luckily I've still been insanely busy during lockdown but means my cars have not been touched

 

[Kryton]

Finally bought a DVD burner for laptop as doesn't look like I will be back in the office for a while. Getting error where its not seeing / reading the ISO on the disk. Is it literally a case of sticking it in the DVD / Map part of the RNS-E & waiting for it to kick into life or is this as fussy with CD's as it is SD cards?

Cheers

 

[pcbbc]

Finally bought a DVD burner for laptop as doesn't look like I will be back in the office for a while. Getting error where its not seeing / reading the ISO on the disk.

On the RNS-E?
What exactly does it say and where?
How does it identify the disk on the screen with the screen open?
Does it read map DVDs okay?
What FW version currently, and what are you upgrading to?

Edit:
"reading the ISO on the disk". Ummm.....
The ISO should not be on the disk - The ISO IS the contents of the disk!
If when you look in the root of the disk you see a file #########.ISO you burnt it wrong.

Did you burn to a CD-R/CD-RW and not a DVD?
Reading CDs is a lot less exacting than a DVD and shouldn't present any problems, assuming your RNS-E is able to read an original navigation DVD.
If it cannot read an original nav DVD then it is likely the drive/laser is life expired and needs repair/replacement.

What files do you have in the root of the update CD?

Is it literally a case of sticking it in the DVD / Map part of the RNS-E & waiting for it to kick into life or is this as fussy with CD's as it is SD cards?

Instructions here.

It's not "fussy" with SD cards:
192 units require (non-HC) SD cards of 4GB or less.
193 units require SDHC (or legacy SD cards) of 32GB or less.

You could claim it is fussy with navigations DVDs if your definition of "fussy" is booktype=DVD-ROM layertype=READONLY
Basically that should indicate a pressed disk - although a few older DVD burners don't stick to that standard.

 

[Kryton]

Ok thanks, I will have another go when not half asleep in the next day or so

Thanks again

 

[Kryton]

Just had another go but using Verbatim disc rather than Sony, everything else done exactly the same; worked first time!! Changed all settings and changed language to English and all seems to work as expected. Only issue I have is when pressing car, it doesn't seem to understand my voice commands and just keeps repeating suggested options to me twice before cancelling. Am I doing something wrong or is it my Naaaaarfolk accent lol? I know the bluetooth mic works perfectly as been speaking to the missus from home whilst she was driving it the last couple of weeks

 

[Kryton]

Also just donated £20 of beer tokens as promised. Thanks for your help

 

[pcbbc]

Also just donated £20 of beer tokens as promised. Thanks for your help

Thanks.

Have you re-wired the Bluetooth mic through to the RNS-E?

Standard (non-SDS) setup:
MIC -> Bluetooth module

SDS Setup:
MIC -> RNS-E -> Bluetooth module

Also you will need to recode the Bluetooth module so it knows it is working with the RNS-E in SDS mode.
See Ross-Tech
001x0x
The values for the x fields will depend on your installed options/requirements.

 

[Kryton]

Oooooh that would definitely explain it then. So it's not my accent?! I will report back but weather isn't looking great so may be a few days (or I might just use hey Siri for now)

 

[pcbbc]

Just to update you all on the firmware front, as per my announcement in the MK2 forums.

The latest Beta RNS-E firmware with optional Feature Pack now enables exciting new features for RNS-E owners...

• MP3 Album Art
• Audible POI Alert
• Custom Splash Screens
• SD Card Maps
• VIM Unlock

Plus the return of full 7-digit UK postcode lookup and custom POI.

Visit RNS-E Firmware for details and to download our custom RNS-E firmware.