Unlock Read Write PCR2.1 with Ksuite/Fgtech China Clone

PCR2.1 full flash VERY IMPORTANT. The following parts starts with KESS Alientech new SSM cable and connection, then followed with unlock/read/write PCR2.1 with Ksuite/Fgtech China clone.


In recent update Kess now can write PCR2.1 with VR-file without needing patch first with KTag.
And KTag now also has the ability to extract the password and then do full read and write thru bootmode. Such a read can then be used by Alientech in their database for vr-files.

But.. in order to retrieve password a SSM cable is used. The following first picture is new SSM cable and the second one is connection.

Already done, read the pictures below.

Need original ktag, open ecu and prepare Eeprom for cloning ECU.


Question: have anybody test this cable with ktag clone ?


PCR2.1 clone and immodata is no problem anymore, no need full flash. MCU-ID is enough, even VCP can read it.

BTW, If donor ECU from other model car, need change SW. Best read write fullflash.


Besides, For fgtech is ok today
Date Software revisions
01/18 OBD driver CAN for Siemens Simos PCR2.1 VAG Virtual Read/Write, Recovery, Checksum, Unlock by OBD

I have made hundreds of pcr 2.1 with galletto v54 china clone and galletto v54 Eu clone.
I have never met an issue.
But if you don’t make the connections carefully then you can brick the ecu with any of the clone or original tools.


Test reports & feedback on Ksuite/Fgtech China clone read write PCR2.1:

VW Golf VI 1.6tdi unlock, read and writeSimos PCR2.1.

What I tested successfully is only on Chinese clone not reworked unit : fgtech v54 , ktag 7.020 , kess v2 5.017 , ksuite up to 2.15.


Tip: pcr 2.1 needs to be as you know unlocked before writing .

I prefer ksuite to work on this ecu (kess or ktag) , ksuite seems to be more stable than fgtech on pcr but work too : i get error with fgtech on one pcr2.1 , i don’t know why , and no problem with ksuite .


In the same day I tried another pcr with fgtech and no problem , the one fgtech don’t want to work with work flawlessly with ksuite and car run ok .

So if you have both tools , prefer ksuite seem to be more stable .


After you get you ecu unlocked in boot mode , with fgtech just remove boot and left pin connection , and read or write on bench .


On ksuite tools , you can’t read or write with ktag , only unlock . (alientech need to work on it…)


with kess it’s ok , BUT , you can’t use the tricore module !


The problem is that the harness is plugged in the tricore module . so you have to build your own bench cable : just get a obd female plug on a scrapyard , and wire +12 gnd and can h/l (kline is not used but you can wire it it will make a universal bench cable) .


The trick to get communication error free on both fgtech and kess cable is to use a strong external psu .


when the tool id or read or write the ecu , the ecu will perform a kind of reset , and the big cap inside the ecu will go charging , causing a drop in voltage if your psu isn’t strong enough to handle it . THAT WILL CAUSE THE COMM ERROR . That’s the only thing you have to take care .


when i made test with many little psu (like one you get with your tools) i have seen 7 volts drop some time , so the ecu is shutting down and no comm .


you can use computer atx psu modded to work on bench (green wire plugged on ground to power on ) i think anything that can provide +12v 2A will be ok . i didn’t need more than 12v just a stable 12V . 14v unstable will not be ok lol


that’s why on the car you have no problem , car battery can handle the cap charging current .


There is no immo caused comm error on this ecu , psu is the problem !!


So to sum up : good psu and obd home made bench cable , remove tricore module on kess v2= 100% tested bench flashing solution for pcr2.1 .

-Quoted from

https://mhhauto.com/Thread-VW-Golf-VI-1-6tdi-Simos-PCR2-1-unlock-read-and-write-Help-Please?page=2 (Post:#17)


More to be continued.