Issue #60: Implement AOS Transfer Frames per Spec #98
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.
This PR includes AOS Transfer frame implementation based on the 'AOS Space Data Link Protocol' specification.
AOS Transfer frames spec includes a set of optional fields to be decided by the mission, so this information is captured in a new class, AosConfig, which can be populated from a kwargs map or AIT config file, within the 'dsn.sle.aos.' section.
Some refactoring was performed such that TmFrame and AosFrame classes have a common base-class, BaseTransferFrame.
TmFrame decoding was updated to include bit shifting as necessary for sub-octet fields.
A new unit test file, test/test_frames.py, exercises much of the AOS Transfer frame decoding.
Resolves #60