Choose KESS V2 ? K-tag ? or Fgtech Galletto V54 ?

Different among Top 3 ECU Programmer KESS V2 V2.22 firmware V4.036_Ktag V2.13 firmware V6.070_Fgtech V54 Galletto 4:

Product Name	Kess V2 V2.22 SE87-C	K-tag V2.13 SE80-C	Fgtech v54 Galletto 4 SE61-G
Function	read and write the Data of Engine ECU	read and write the Data of Engine ECU	read and write the Data of Engine ECU
Support Vehicles	Cars and part Bikes	cars, trucks,traktors and bikes	Car, Truck, Motorbyke, Marine
Support Protocols	With coverage of all major brands and protocols including Line, CAN, EDC17 and MED17 and Ford J1850	Available Protocols for K-TAG: BDM MOTOROLA MPC5xx	NEW JTAG – BDM – MOTOROLA – FREESCALE – INFINEON
Method	Via OBD2	Via BDM	Both via BDM and OBD
Update	Update via Hardware	Update via Hardware	NO
Token	No tokens limitation	No tokens limitation	No
Langauge	English, German, Spanish, Italian, Portuguese, French	English, German, Spanish, Italian, Portuguese, French	English, Italian, German, French, Spanish, Portuguese, Czech, Turkish
EDC17	work with a small part	work with a small part	work with a small part
Additional remark	1)  Most customers use FGTech Galletto 4 V54. Some users prove fgtech2 v52 works 50% obd. BDM works ok and work ok with tricore and st10 micros. Fgtech galletto not disappoint them never. 2)   KESS V2 has Anti-mediation lock module, it can do new and encrypted cars better than Fgtech. Remark: no one is perfect, maybe is good to have more than one tool, but much better is to have one good tool.

Kess V2 V2.22 Firmware V4.036 Master:

K-TAG V2.13 Firmware V6.070 Master Version:

Best Quality FGTech V54 Galletto 4 Master Version:

Why Ktag / Kess checksums error and how to prevent it happens

Some users feedback they have a same problem with Ktag and/or Kess v2 Master checksums error eg. the units will not calculate checksums when loading files. And this error happens on both Chinese clone Ktag/Kess and EU clone ones.

Then why Ktag / Kess checksums error and how to prevent it happens?

At first, I also have this error, but finally I find out the reason, and I hope I share here to help others.

Let's go!

According to this ECU, you must do a full read and then straight after that you must do a full write. After you've done that, the ECU is open for you to load your tunes based on partial reads and writes. The reason for the full read and full write is that it takes off the tuning protection on the ECU.

I did a full read a month ago, and only did a full write a week ago. Whenever I tried to write the tune file, the ECU would be bricked and come back with a checksum error after the write. So the secret is to do the write directly after the read. I did this with a FGTECH V54 but the process is the same for Kess. I now write my custom tunes with Kess to the ECU, and KSuite corrects the checksums for the partial writes.

The process is different for other ECUs I'd imagine.

2.13V Ktag Master V6.070 Plus V2.15 Kess V2 Unlimited Token V4.036 with Free ECM TITANIUM V1.61 Software:

http://www.eobdtool.co.uk/wholesale/v213-ktag-and-kess-new-programming-tool.html