[ATPCR]

ADDED: Moderator, please move my thread to the BE/EA section if appropriate?
I have been working in an EEC-V BEB file in Binary Editor. I wrote the BEB file to the Moates QuarterHorse and it cost me a $48 token.
I want to make more changes but don't want to mess up my file. I would think after using a token, it would be a .bin file then BE would let the file "read" happen with damaging it and requiring token which I now have 0 of. This pop-up box makes me wonder and hesitant to click on read until someone that has experienced this working with Binary Editor with 4 bank EEC-V and give me a recommendation.
Here is the snip and what does this mean?

BE wanting to read QH back to BE.JPG (66.61 KiB) Viewed 27379 times

[86GT]

When using BEB files they are locked to a VIN and strategy. Once you consume a token the BEB is marked and saved. You will notice the tune name in the status bar will change to a green color indicating it is tokened. If you try to read back a tune from a vehicle while you have the tokened BEB open then BE will warn you that reading the tune will overwrite the tune that you have open. Since the tune that you have open has a token BE simply warns you.

Once a tune is tokened you should never need to read it back. You have the mater copy on your PC already. Simply open that master copy and save it as rev 2 or something like that. You can make as many copies of that tune as you want.

It is never recommened to read a tune back. Each time you start a datalog, BE inserts a so called patch code into the Moates Quarterhorse to allow for datalogging. This patch code is NOT inserted into the tune on your desktop. If you read a tune back it may have a patch code in it from a previous datalog session.

If for some reason that tune was ever used for some other software and this so called other software uses a different patch code for datalogging it can corrupt the tune and cause all kinds of problems.

This is the main reason to never READ tunes unless you are 100% sure it is a factory tune or you are absolutely sure it was a BE created tune in the first place without a patch code in it.