Was too eh!![]()
Very good. I do a summary of what I understand about these interfaces and some considerations on the types of connections, correct me where am I wrong:
Interfaces
Galletto v53/v54: OBDII + serial to tour + open the control unit.
KessV2 + k-tag: OBDII + serial to tour + open the control unit.
KessV2 + j-tag: OBDII + serial tour
Connections
By OBDII-read and write only a part of the ECU, when possible.
With the ECU open I can connect BDM and/or in the Boot (the Boot mode can? be Normal or Tricore) and do a full scan, depending on the type of ECU.
Usually if I do a full read in BDM, but I can not? it Boot the Normal, and vice versa.
One can not always use a single interface to flash/read/write the ecu. If one can not work than change another kit.
KESS V2 works better for new cars and encrypted cars. it supports a wide range of BOSCH, DELPHI, MARELLI, MOTOROLA, PHOENIX, SIEMENS and TRW ECU types. protocols including Line, CAN, EDC17 and MED17 and Ford J1850.
The cock 4 v54 is able to program all EDC17 and MED17 ECU chips and all the old protocols included from Bosch MExx, EDCxx, Marelli, Siemens, Delpy, Lucas and Dense.
and many other options, Galletto 1260 which is quite a work-for-DIYer, and other mpps (mpps v13 and v16)
BTW, here is a full comparison between ,mpps and galletto 1260
MPPS V13, MPPS V16 et Galletto 1260 Differences - EOBD2.fr | French Car Diagnostic Tool Co., Ltd.