Skip to main content

DIY carkit replacement

The factory-installed UHV carkit[0] in my Volkswagen Touran worked well with a normal cellphone-holder, but in combination with the Bluetooth Touch Adapter[1], it became a very unreliable combination. I've read many succes stories with the Touch Adapter, but the flaky communication between the TA and the UHV was a nightmare sometimes.

To fix that, I ordered a replacement carkit from Kufatec[2]. The module replaces the simple factory UHV with a newer one (also original from VW). The new module does not only bluetooth sound, but also address book, call lists, etc. It doesn't offer cellphone specific holders for power and antenna connections.

Installation was quite easy, as there are many howto's describing VW Low-to-Premium modding. In the Touran (1T0), the UHV is under the passenger seat, and requires removal of the lowest drawer. A T15 Torx screwdriver does the trick. Then you can open the floor cover, get the original module out, and the new module in. Replace the drawer, and that's it. You'll just need to program the module, so that it knows how to talk to the rest of the car. You'll get phone menu's on the MFA+ display in front of the driver, and on the RNS/RCD navigation system in the central console. Any VW workshop with VAS or VCDS can do that for you.

  • [0] Factory installed unit: 3C0 035 729G. Only does sound over BT. No screen output.
  • [1] VW Bluetooth Touch Adapter: 3C0 051 435 TA. Does address book, call list, and sound with a phone, and passes the sound through to the UHV unit [0]. Has its own little touch screen.
  • [2] VW replacement part from Kufatec: 1Z0 035 729B. This does address book, call list and sound natively, and displays it on the MFA+ and RNS510 screens.
P.S. I didn't remove the passenger seat for this mod. If you don't already have a VW carkit, or you're changing to the VW Premium car kit (the one that does rSAP, and has its own antenna), that's probably a different story.
Labels:

Comments

Post a Comment

Popular posts from this blog

Volkswagen UHV bluetooth touch adapter & its problems

My Volkswagen car has the "universal cellphone preparation" UHV built-in. This is the main part of a car kit, but requires an additional adapter for connecting to a cellphone. At first, I was using an adapter for my good old Nokia 6310, even after I changed to the Nokia E71. Connecting was easy: pair the phone with the "VW UHV" bluetooth entity, and done. This has the phone connected to the car kit at all times, so even non-call-related functions use the car audio system (e.g. voice recognition). But progress will have its way, no matter what happens. So in comes the "bluetooth touch adapter". Instead of a phone-specific adapter, this is a small touchscreen device that slots into the UHV dashboard mount. Connecting a phone is very different now: the Bluetooth Touch Adapter connects to the "VW UHV" device via bluetooth the phone connects to "Touch Adapter" device, also via bluetooth The device doesn't allow step 2 if step 1 didn'...
12 comments
Read more

Reset lost root password on vSphere ESXi 6.7

VMware's solution to a lost or forgotten root password for ESXi is simple: go to  https://kb.vmware.com/s/article/1317898?lang=en_US  and you'll find that "Reinstalling the ESXi host is the only supported way to reset a password on ESXi". If your host is still connected to vCenter, you may be able to use Host Profiles to reset the root password, or alternatively you can join ESXi in Active Directory via vCenter, and log in with a user in the "ESX Admins" AD group. If your host is no longer connected to vCenter, those options are closed. Can you avoid reinstallation? Fortunately, you can. You will need to reset and reboot your ESXi though. If you're ready for an unsupported deep dive into the bowels of ESXi, follow these steps: Create a bootable Linux USB-drive (or something else you can boot your server with). I used a CentOS 7 installation USB-drive that I could use to boot into rescue mode. Reset your ESXi and boot from the Linux medium. Ident...
Post a Comment
Read more

GEM WS2 MIDI System Exclusive structure and checksums

MIDI is the standard for communication between electronic music instruments like keyboards and synthesizers. And computers! While tinkering with an old floppy-less GEM WS2 keyboard, I wanted to figure out the structure of their System Exclusive memory dumps. SysEx is the vendor-specific (and non-standard) part of MIDI. Vendors can use it for real-time instructions (changing a sound parameter in real-time) and for non-real-time instructions (sending or loading a configuration, sample set, etc.). In the GEM WS2, there's two ways of saving the memory (voices, globals, styles and songs): in .ALL files on floppy, and via MIDI SysEx. The .ALL files are binary files, 60415 bytes long. The only recognizable parts are the ASCII encoded voice and global names. The SysEx dumps are 73691 bytes long. As always in MIDI, only command start (and end) bytes have MSB 1, and all data bytes have MSB 0. The data is spread out over 576 SysEx packets, preceded by one SysEx packet with header informat...
23 comments
Read more