topblog Ivoire blogs


VVDI Keytool and 2006 Hyundai Santa Fe FAQ

Here are questions and answers of 2006 Hyundai Santa Fe remote/chip cloning with VVDI Keytool error below when the user wants to clone the aftermarket generic car alarm, after the remote clone/special clone

Error information:

SN2 module detected, special clone only support wire key. Please change key model


Should I use Tpx3 chip and standard wired key?

chip - ok.
What can I do to clone the alarm remote?

now. prepare remote and programming obd

That is to get the factory keyless entry. But if I want to use the aftermarket alarm how can I do it?

Not sure that there is an option to prepare a remote for santa fe in keytool. I did for Tuсson - everything works

How to you add remote to the factory alarm? Using launch scanner tool?

Go to the special function menu of your launch. I assume Launch can do it because it had an option for Immo program for Hyundai.Just don't have the chance to use mine

Also you can program the standard with OBDSTAR X300 DP Plus


Single VCI + Multiple Diagnostic Software + One Laptop

Tips and guides:

Purpose: a single VCI - a few different diagnostic programs - one laptop - different cars diagnostics

  • BMW
  • JLR
  • Toyota
  • Mazda

may add more in the future...

There is a single VCI that can be connected to and operate with these multiple software bundles


You could cover all of these using either...

1. Autocom/Delphi 2014.3 software (2015 & 2016 versions are fake) with DS150e /CDP vci

2. Launch Pro with Launch Easydiag 2 or Easydiag 3 vci. Look in the forums for free solutions or get it with tech support from a reliable source (i’m using

Launch is up to current vehicles.

This will be sufficient for most diagnostic work needed to repair all brands of vehicles you might expect to encounter.

If you want to get into software updates or chip tuning then you will need many more expensive tools.


  1. AVDI and for the matter FVDI work as pass through's I have both gen avdi and ori fly fvdi and we use the fly for ford,jag,honda and toyota as it also has the free loader that means you can use the latest manufacture applications direct
    What you do need to be aware of is what versions of can you need to communicate over there are many ISO protocols and also pin out options of the obd2 plug
    For example ford use J1850 on pins 3 and 11 as it will work in single wire config avdi doesnt talk on this so relies on using the vehicles can interface which is ok until you have an isue on that can interface
    But Ford KA (edge 2009 on) is actually Fiat so it uses pins 1 and 8
    You need to know exactly what you need in terms of protocols (there is 6 common ones) then work out if you can find the drivers for a tool that works with your software

    4. A different option is to get a can sniffer dependent on type and software options (VXDIAG Multi Tool should a good option for you) - then you can diag every car and you can enter into many functions hidden to your scanner
    The OBD2 connector protocol is a mandated law (this started in USA but is worldwide now) that means every module on the vehicle must be accessible and programmable via this socket this goes way beyond the flashing of maps etc. Manufactures are allowed to password protect parts of the system like the incode/outcode of Ford but as manufactures are by nature bean counters and lazy they buy in there electronics so a Delphi code is a delphi code no matter if it is ford or peugeot or even geely

    I am looking at getting a ADR soon (about £3500) as they have some amazing access to modules they can tell you that at x time on x day x mileage/rpm/outside temp "colour of your pants" you entered the speedo module and reprogrammed the vin and the real vin is x from this stolen car... (even if you reprogram chip of the board as its done by snapshots)
    The police have this and its made by Bosch and anyone can buy it


Clone VCM2 Ford IDS 111 Update

Issues: VCM2 doesn't connect to the PC anymore.

Hardware: VCM2 clone (not VXDiag VCX Nano Ford) which has worked fine

Software version used: IDS v109 on VMware.... worked fine

Software updated version: IDS version 111 native...not working

Error message:

Tried the last IDS version 111 native install but at the first connection , IDS requested a VCM software upgrade. After few seconds i received an error message (there was an error updating your VCM2).

Since then I've tried recovering my VCM2 using IDS V86, VCM II manager v2.1.119.3, new SD card, with OBD power, without OBD power. The process stars good but after 2-3 minutes i receive an error message (There was an error reprogramming your VCM2 and your VCM2 requires a factory reset).



Tips & guides:

some clone vcm's are prone to this
I found that it was usually the output voltage/amps on the computers usb as I could always reset them on my trusty old Dell

To do this it had to be V86 on XPs3 and not on a VM I also powered up the vcm on its 12v power jack directly
I reset literally 20 plus for friends with this set up many times over years ago

the only other issue I found was the little reset button falls off the board very easily if you press too hard



I used a PC with a fresh windows 7 32bit and IDS86 installed without VM  .
I finally found the issue and it was actually a simple intermittent connection with the USB cable. (although the message was not the loss of communication..)
After the cable was replaced, the software update was successful.

Now IDS version 111 works like a charm!