Hello guys,

I think I can understand the reason why soo many writes can fail as it depends on how the tool handles the checksum, So it would be good for others to share their knowledge here.

I read EDC16U3 through OBD with no problems (2MB). As I understand, FGTECH handles the checksum itself on write.

Does FGTECH want MOD file with untouched checksum and synchblocks? Or should synchblocks be corrected before write but leave EDC16V2 alone?

If i select "calculate compatibility test checksum" when import ORI file, checksum shows as NOT OK. So I assume EDC16V2 checksums should be left alone, but what about the two Synchblocks?

Thankyou.

Wod wrote:Hello guys,

I think I can understand the reason why soo many writes can fail as it depends on how the tool handles the checksum, So it would be good for others to share their knowledge here.

I read EDC16U3 through OBD with no problems (2MB). As I understand, FGTECH handles the checksum itself on write.

Does FGTECH want MOD file with untouched checksum and synchblocks? Or should synchblocks be corrected before write but leave EDC16V2 alone?

If i select "calculate compatibility test checksum" when import ORI file, checksum shows as NOT OK. So I assume EDC16V2 checksums should be left alone, but what about the two Synchblocks?

Thankyou.

i have never been a fan of Galeto i have heard of so many people having issues with this tool. i would recommend kess or Mpps is you wanting cheap tools