Implemented 0x8D module programming, PC5200 support, Zones 33-64 bypass/fault/restore status messages #283
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
Just an local dump to show work in progress, will be redone.
|
Hi @kricon - thanks for the RF5132 work! Heads-up that I've updated the code structure in Feel free to keep this commit as-is with the existing structure, I can manually merge once this is ready because I know it can be a pain to retroactively adjust code that you're in the middle of working on. |
Decoded by Alviunta taligentx#295
kricon
changed the title
Contributed by Alviunta (https://github.com/Alviunta) In taligentx#295
kricon
changed the title
Following decoding in taligentx#188 Separated 0x8D and 0x94 cmd, messages only for 0x8D Added checks for printing correct options/data/signal strenght etc Cmd 0x8D data omitted for AVR/Arduino to fit into memory Massively tested with RF5121 v3.14/two v5.0/v5.1 modules
Sketch fits into Arduino Uno memory size - using 31422 bytes
kricon
changed the title
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.
Following #188 I started to implement decoded protocol into
dscKeybusPrintData.cppfor 0x8D cmd as much as I can, with massive testing on RF5132 v3.14, v5.0 and v5.1 modules. I'm still not sure that all messages can be correctly indentified.For 0x94 cmd, it's impossible to distinguish for which module version it is from just single line (so probably emit messages and just print raw data).
Also on 0x94 cmd ESN data starts with first digit on byte7 bit6 and sixth digit ends on Byte10 bit7. Maybe somebody can help me with shifting the bits from bytes so we can print out ESN data of 0x94cmd.
Note: this is just an dump from local PC, to show work in progress. There is still a lot to implement, test, and redo the code.