I recently bought a 2002 polo 9n, and now I intend to upgrade it a little starting with remote central locking.

It does not have central locking at all, so that makes it a little bit more complicated. So far I have sourced the following:

1J0959753AH FOB

3B1837015AQ door lock actuator left

3B1837016AQ door lock actuator right

6Q6827297H Boot handle lock

6Q0959433E ccm module h01/s0001

 

My current key looks like this:

I believe that has ID44 transponder, and the new one has got ID48. So simple solution is to get ID44 transponders and put in the new FOB. However, I would like to swap out the Instrument cluster for one with display (haven´t done that much research on that yet), and then it might be necessary to replace immobilizer unit as well, or am I wrong? And If I do replace instrument cluster, can I correct the milage so it matches ECU with a VagTacho copy (with proper firmware since it acted up at first but I got it sorted)?

 

 

You can if your careful split your key fob and then remove the transponder chip and put it in your new fob, or simply tape the key inside the steering column surround near to the ignition switch.

 

If you replace the instrument cluster you will first need to get the PIN code from your old cluster with VagTacho as the cluster is also the immobiliser unit, there are good youtube links on the www.ross-tech.com site  You can change the mileage with VagTacho you have to do it in KM's but as your in Finland that won't be an issue

Ok, as I suspected then.

The reason for me wanting to change instrument cluster is that when outside temperature drops below 5 degrees celcius, the cluster beeps and shows outside temperature on the clock display. Theres no harm in that, but I would like to see the clock, and there is no button or anything to switch back to clock once it alerts. If there is a way to put a switch there I would be happy,  but I doubt it, or is it something that could be done with VCDS?

There might be something you could do by recoding with VCDS not had a 9N connected recently so wouldn't like to say for certain, only other way might be to have a switch on the signal wire from the outside air temp sensor ? (pin 31 Brown/Yellow wire) 

I will have a look around with vcds when I plug in the computer next time. It would be nice with a cluster with MFD, but my wallet will be happier if I can work around it.

Looking at the dealer wiring diagrams, it only shows the outside temp sensor for the MFD not on the basic cluster, unless it's a regional/market variation ??

You mean it normally shouldn´t be there? It is very possible that it is a regional/market variation, because Finnish legislation is very strict when it comes to cars (and what they are equipped with). On the bright side, that would make a MFD conversion a tiny bit simpler.

Btw, this is what the cluster looks like.

I have my dealer manual settings on the UK and for us the outside temp display (according to my diagrams) is only for the MFD not on the basic setup, so yes it is quite possibly a regional requirement ? So as you say that would make the conversion to MFD easier, just the 3 wires from the wiper stalk to the cluster

Thank you for that diagram, it is very helpful! Where can you get wiring diagrams for this car? I was just wondering since I need to do a fair bit of wiring to get the central locking to work, so I would like connectors, pins, colours etc. if I add to my current looms, other option is to get looms that have all the connectors and wires already.

That diagram is from ElsaWin it's a copy of the dealer manuals, it covers all VAG models from 1996 to current, plenty of copies for sale on eBay around £15~20  ( €17~23)

For part numbers of pins/sockets

Here's a link to the door wiring loom https://volkswagen.7zap.com/en/rdw/polo+derby+vento-ind/po/2002-253/9/971-972035/

Today I was going to check with an unlicensed copy of VCDS Lite and my old kkl ebay cable, a setup that has worked on the car before. But today it wouldn´t connect to the car, I only got "no response from controller" message. I tried pretty much everything, uninstalling & reinstalling both drivers and VCDS, tweaking the com port settings but nothing. FYI I have an aftermarket stereo installed, but as I said it has been working before. Could the odb port be at fault? It have broken off from the mounting bracket, but as long as the wiring is ok it should work, right?

Looking at the diagrams, from May 02 they seem to have deleted the K line and only use CAN ? so your KKL lead wouldn't connect, you need a HEX-CAN lead

A month ago when I was testing if the cable were good with the 9n it worked, I could access at least the instrument and immobilizer (as far as the unregistered version allowed me to). It is however very problematic setup so I am considering buying a complete cable + license from ross-tech (or used if I can find one). Ross-tech sells HEX-v2 for DIYers for $199, and that seems to be a good deal since used HEX+CAN seems to cost a little bit more on ebay.

Any experience of these?

http://www.ebay.com/itm/VAG-Kabel-USB-Diagnosegerat-Deutsche-Vollversion-VW-Audi-Seat-Skoda-bis-2016-/172694593819?hash=item283566611b:g:U4QAAOSw4CFYxqd3#shpCntId

That ebay link, is like the one I use, only mines for an earlier version 11.1, it works well, only negative thing is you can't update to the latest versions as they come out.

 

The K & CAN lines go direct to the onboard supply control unit as the diagnostic data bus interface is part of it.  The K line goes from pin 7/16 to the supply control unit 18 pin Brown connector pin 1 and the CAN lines pins 14 & 6 to a 16 pin Black connector pins 2 & 6

I got the day off and borrowed home my work laptop. Installed everything and it worked just like it should. So, I thought its probably a driver issue, since the kkl has a CH340 Serial chip instead of FTDI, and it was quite a hassle to find the correct drivers. I downloaded and ran a program called device cleanup, and deleted every usb and serial device used and installed the last 24h. After that a reboot and install drivers again and it worked like a charm!

 

Then I plugged it in to my car, and first of all checked if perhaps the immobilizer would accept my nre FOBs, and it does! there was a 1 in the third field as it should according to ross-techs guide.

The only trouble is I can´t seem to login to the instrument with the key retreived by VagTacho. This could just be because I have drained the battery, I´ve got the charger connected now and will try again when it gets fully charged.

I am getting really frustrated with this. Instrument lock time is 40 minutes, and i leave ignition on so it counts down. I also have the battery charger hooked up. When it gets to 0, everything seems to look good. As soon as I reboot the system (remove key from ignition for a minute), the instrument lock time is back to 40 minutes! Could the cluster have taken damage when the battery ran out?

Ok,it stopped adding lock minutes now, but when I try to login I enter the pin with zero first. Then you can see the symbol for communication spinning and immo light on dash lights up but nothing else. No communication lost, no freezing. How long should it take? I left it for about 15 minutes before I aborted it...

 

It could be that the battery isn't holding full charge long enough, I have kept the charger on while waiting for the lock minutes to pass, but I will let it charge over night...

 

I am also not able to access the ECU,but that might be because of the battery as well

Ok, I got it! Turns out I was logged in to the cluster all along, and thats why I couldn´t access the ECU. New keys are coded so onto the next step!