-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for Acknowledge, Beacons, Data and MAC commands #21
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @blueluna! I don't have the standard, and I don't have any hardware running other implementations of the protocol, so my ability to review and test this is limited. Still, I've looked over the code and left some comments.
Let me know what you think about the comments. Once they have been resolved, I'm happy to merge.
Co-Authored-By: blueluna <[email protected]>
- Added more test cases for encoding and decoding Beacon - Fixed documentation for hopping sequence duplication
Okay, this looks good to merge. Thank you again, @blueluna! |
This PR adds support for encoding and decoding Beacons and MAC commands. This is my first time working with 802.15.4 so I might not understand all the concepts. But here goes.
There probably are opportunities for better naming in some part of the code (for example FrameContent?).
Testing done.
I have decoded
Acknowledge
,Beacon
,Command::AssociationRequest
,Command::AssociationResponse
,Command::BeaconRequest
,Command::DataRequest
,Data
from a coordinator or other devices in a PAN. I have encodedCommand::AssociationRequest
,Command::BeaconRequest
,Command::DataRequest
which has been understood (I believe) by a coordinator.