You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be useful to have a write with verify command. It would first see if the tag can be read, then writes, then checks the write. This way it will be known if the write was a success. This can currently be done with a few different commands, but in certain circumstances one command would be extremely helpful -- for instance if the tag must be held with one hand while the other types.
The text was updated successfully, but these errors were encountered:
usually we don't do automated verify. We added it to most LF clone commands but otherwise no.
It never made sense to automate it since we don't know what you want to write. You can write what every you want, good bytes, bad bytes, keeping a check for what is doable after a write would make it take too long.
Hence we encourage to do a manual verify after a write command.
If you know your own specific use-cases, you can use lua / python script to do it in one go instead.
I think it would be useful to have a write with verify command. It would first see if the tag can be read, then writes, then checks the write. This way it will be known if the write was a success. This can currently be done with a few different commands, but in certain circumstances one command would be extremely helpful -- for instance if the tag must be held with one hand while the other types.
The text was updated successfully, but these errors were encountered: