#Fgtech v54 eu clone reworked install
#Fgtech v54 eu clone reworked update
#Fgtech v54 eu clone reworked driver
#Fgtech v54 eu clone reworked full
#Fgtech v54 eu clone reworked software

There is no immo caused comm error on this ecu, psu is the problem !! That's why on the car you have no problem, car battery can handle the cap charging current. i didn't need more than 12v just a stable 12V. 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. FGTech Galletto 4 V54 Master chip tuning tool for all cars, trucks, motorcycles, Marine, BDM MPCxx, BDM Boot Mode, checksum.Fgtech v54 with multi langunage and with 2014 V54 software.Unlock Galletto v54 master can use directly,there is no need to activate.Obd2repair recommend you the hot sale FGTech Galletto 4 V54 Master and offer you the.

#Fgtech v54 eu clone reworked software

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. Software Free Download of FGTech Galletto 4 V54 Master. That's the only thing you have to take care.

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. The trick to get communication error free on both fgtech and kess cable is to use a strong external psu. 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 problem is that the harness is plugged in the tricore module. With kess it's ok, BUT, you can't use the tricore module ! On ksuite tools, you can't read or write with ktag, only unlock. Īfter you get you ecu unlocked in boot mode, with fgtech just remove boot and left pin connection, and read or write on bench. So if you have both tools, prefer ksuite seem to be more stable. 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. 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. Tip: pcr 2.1 needs to be as you know unlocked before writing. 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. VW Golf VI 1.6tdi unlock, read and writeSimos PCR2.1. Test reports & feedback on Ksuite/Fgtech China clone read write PCR2.1: I have made hundreds of pcr 2.1 with galletto v54 china clone and galletto v54 Eu clone.īut if you don't make the connections carefully then you can brick the ecu with any of the clone or original tools.

#Fgtech v54 eu clone reworked driver

Best read write fullflash.Ġ1/18 OBD driver CAN for Siemens Simos PCR2.1 VAG Virtual Read/Write, Recovery, Checksum, Unlock by OBD MCU-ID is enough, even VCP can read it.īTW, If donor ECU from other model car, need change SW.

#Fgtech v54 eu clone reworked full

PCR2.1 clone and immodata is no problem anymore, no need full flash. Question: have anybody test this cable with ktag clone ? Need original ktag, open ecu and prepare Eeprom for cloning ECU.

The following first picture is new SSM cable and the second one is connection. in order to retrieve password a SSM cable is used. Such a read can then be used by Alientech in their database for vr-files.īut.

#Fgtech v54 eu clone reworked update

In recent update Kess now can write PCR2.1 with VR-file without needing patch first with KTag.Īnd KTag now also has the ability to extract the password and then do full read and write thru bootmode.

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. and try to open the Obd2 again.Ĭheck ftd2xx.dll file. If this file was read only and you have to change this unmarking read only in location – widows/system32/2.1 full flash VERY IMPORTANT. If Fgtech v54 not open in OBD2, re-install again without deinstalar the v54. (if you uninstall all previous versions). That is, you need to remove all previous installs system files of fgĬheck your fgtech drive, check if all is well, there’s driver for 32bit and 64bit. Remove the old fgtech from system totally Here are tips of “ Galletto V54 cannot start to run after installation”….

#Fgtech v54 eu clone reworked install

If your Fgtech 4 hardware does not support just one of the instructions used on the virtual machine then no matter what os you use or how many times you install it, simply will not work.Īnother common problem is drivers mixture with other ft232 based devices you may have installed, Chinese fgtech only runs on their own drivers. And that is why many people have problems and hungs running galletto sw on their laptops and working good on other machines. Chinese FGtech galletto v54 software runs into his own virtualized environment, that is why is so machine resources hungry app, maybe your processor is not “compatible” with the virtualmachine generated for that executable.