NASA-AMMOS / NASA-AMMOS/AIT-Core
Packet support should include an implementation of a variable size packet (uplink)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
This is typically used for string arguments for commands that may be inconsistently-sized.
An example would be a command that exists to echo a string sent in uplink down as an evr - a "we are here" type command, or a command that executes an arbitrary FSW function.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing packet and uplink implementations, then determine how variable-size packets represent string arguments and how they are encoded and decoded. Done means an uplink packet implementation supports inconsistently sized payloads, including the example command cases described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100