Adding a ExtendedMFRC522 class for writing to all sections + encoding #47
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With SimpleMFRC522 it is only possible to write to the 48 bytes of the second sector. Also the encoding is limited to ASCII chars, which does not have any technical reasons, reading and writing UTF-8 to MiFare is totally reasonable. With default parameters the ExtendedMFRC522 just writes for example up to the max of 720 bytes to a MiFare 1K. It can be configured to change first section to write to, number of sections (e.g. number of 48 bytes units) and encoding for data.