Bought a bundle of Ktag and kess v2 last week.
And the kit arrived today. Shipped from China.
Attempting to use the ecu programmers this weekend.
Installed all appropriate software.
I run it on Windows xp
Edit: i successfully tested on some ECUs using the ktag and kess. Used without network connection.
Chinese pcb but high quality, i have this kess and ktag pcb in my old clones ( kess v2 fw: v4.036 and ktag fw: v6.070 and work well without any fault, also work with 24v)
kess and ktag tested in old ecus, works perfect (Sim 32, edc15p+, me7.5, me7.5.10, me7.5.30, Edc17c54, etc)
New Protocols Ecu Tested:
Ktag, Ford fiesta 1.6
Ecu Siemens EMS2211 Tricore
Reading OK (very fast)
Writing OK
Cheksum correction OK
Kess, Toyota Hilux 2.5 D4D Engine, DENSO 175822-887
ID OK
WRITING OK
CHEKSUM CORRECTION OK
Kess write in 2 minutes.
Ktag, Toyota Hilux 2.5 D4D DENSO 175822-887 (needs luck)
Reading ok
Wrinting ok
Backup ok
Cheksum Correction ok
Kess, Vw Amarok 2.0 163cv OBDII Writing
ID Ok
Cheksum OK
Writing ok
In short, KESS V2 is perfect for OBD use, while KTag is perfect for Jtag, BDM and all the Boot application (tricore and ST10).
With KESS V2 you programming directly through the OBD port of the vehicle, while with Ktag you need to take apart the ECU and open it, after you can make the read/write operation.
Many ECU has the advantage that can be read and write from OBD port (so KESS V2 is perfect), but there are lot ECU that need to disassemble from the car and open and this is the case for all the ECU that need to be programmed with Jtag, BDM and Boot protocols, so KTAG is needed. And that is why i bought Ktag and kess v2 together.
(big thanks to masciaro share info to us)
