koanga
  •  koanga
  • 76.6% (Friendly)
  • Member Topic Starter
2021-09-03T08:49:57Z
I stumble on something quite strange. I did read the P & D Flash via bench and saved the data and after that I did a read via OBD, when comparing the files I notice the OBD read has a different VIN number, wondering how this "virtual read" is working.....

vin is stored at offset on both files
00010000 (short vin)
00010030 (long vin)

also the files are not identical ....
Sponsor

Start ECU Repairing, ECU Cloning, and Chip Tuning today, all from an incredible price of just USD 385.00.

No annual fees, no extra charges: You pay only when you have a job.

Visit Hexprog II page

BMWZG
  •  BMWZG
  • 100% (Exalted)
  • Advanced Member
2021-09-03T10:41:00Z
Virtual read works in such a way that the file is downloaded from the server after identifying the ECU and not read from the ECU.
Autohex_II_BMW
2021-09-04T08:07:52Z
Originally Posted by: koanga 

I stumble on something quite strange. I did read the P & D Flash via bench and saved the data and after that I did a read via OBD, when comparing the files I notice the OBD read has a different VIN number, wondering how this "virtual read" is working.....

vin is stored at offset on both files
00010000 (short vin)
00010030 (long vin)

also the files are not identical ....



Never write OBD read via on bench method. because OBD is virtual read from server. The OBD file must be written OBD itself.
koanga
  •  koanga
  • 76.6% (Friendly)
  • Member Topic Starter
2021-09-04T19:27:53Z
So, I can do a read via OBD (virtual read), alter the file (maps tweaks) and write it back same way (virtual write), correct?
Autohex_II_BMW
2021-09-05T05:08:43Z
Originally Posted by: koanga 

So, I can do a read via OBD (virtual read), alter the file (maps tweaks) and write it back same way (virtual write), correct?



yes you are right.