[jaki]

Can you share the files you read? I read the MSD using another tool and there are also changes of several bytes in one place. I want to compare whether it looks similar.

I sent PM to You. I don't really understand how can I post files here

[sixcode]

Can you share the files you read? I read the MSD using another tool and there are also changes of several bytes in one place. I want to compare whether it looks similar.

there are only changes in eeprom when you power ecu off and on in eeprom

[jaki]

there are only changes in eeprom when you power ecu off and on in eeprom

In external, yes. That is the only changes I have noticed. So, looks ok.
I assume DME saves some engine etc parameters to those places.

[jaki]

First MSD81 clone done!
Total time 40min incl laptop power on  open carrying case, making pin connections  etc etc, not bad at all.

Car starts ok

EDIT: when i tested my system with single ECU (read & write to same device) it didn't naturally complain about checksum because all data was consistent all the time.
But!!!
when I wrote data to new (containing some other car data) ECU MultiProg asks if I want to calculate checksum!!! or not (I choose no, because all data will be consistent in the end anyway)
This means that I can read data, modify it (tuning files) and wrote it back and MP calculates cheksum for me, brilliant. That I didn't expect at all.
Am I right?

[ravager]

Can you share the files you read? I read the MSD using another tool and there are also changes of several bytes in one place. I want to compare whether it looks similar.

there are only changes in eeprom when you power ecu off and on in eeprom

Yes, to add: it's working hours

Not to disagree, but to clarify:
When reading it through bench mode, it will always have power thus always change working hours aka you will always have changed bytes in eeprom when reading

[jaki]

Yes, to add: it's working hours

Not to disagree, but to clarify:
When reading it through bench mode, it will always have power thus always change working hours aka you will always have changed bytes in eeprom when reading

So, if I change all of those (changed data) to FF, I will zero working hours?
Is that also the method for other DMW's if I like to zero working hours those?

1. Read data from ECU
2. put ECU to car and power on
3. Read again data
4. Compare data and zero what looks different

Maybe it is not that easy, just wondering.

[jaki]

Update for the system came.
Now it can clone (if i understood correctly) also 8HP gearboxes, cool.

i have only clone one MSD80 for an other vehicle. that also went well. So other wxperiences about other type ECU's, yet.

[r0my81]

First MSD81 clone done!
Total time 40min incl laptop power on  open carrying case, making pin connections  etc etc, not bad at all.

Car starts ok

EDIT: when i tested my system with single ECU (read & write to same device) it didn't naturally complain about checksum because all data was consistent all the time.
But!!!
when I wrote data to new (containing some other car data) ECU MultiProg asks if I want to calculate checksum!!! or not (I choose no, because all data will be consistent in the end anyway)
This means that I can read data, modify it (tuning files) and wrote it back and MP calculates cheksum for me, brilliant. That I didn't expect at all.
Am I right?

Thanks jaki for share your impressions
I was also wondering about checksum capabilities of Multi prog.
I saw in Xhorse web store someone asking about this  and the answer was "multi prog can't do checksum ecm calculation, send it to us for do calculation"