Added more Dallas 1990 IDs to test by default #16
Conversation
This file contains 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
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.
I added some more special IDs to test by default.
They were generated with a simple Python script which I'll share here as well.
How to use the tool:
python ibutton.py process --input inputs.in --output dallas.txt --format text --family 01 --family 08 --family 0c --family 14 --family 81(I use poetry usually, then the command ispoetry run python ibutton.py process --input inputs.in --output dallas.txt --format text --family 01 --family 08 --family 0c --family 14 --family 81)It expects to have an inputs file with just the 6 bytes in the middle of the Dallas UID, you add one or more families (for example 0x01 and 0xFF) and the tool will automatically calculate the CRC for all UIDs.
inputs.txt
ibutton.py.txt