CDH member @whatdoes3plus1equalsto has found some open-source satellite projects that we could benefit from reverse engineering and analysis of their code bases. There are three parts to this task that I will list here.
Reverse engineer the given satellite codebase:
Take a deep dive into the satellite's codebase. Try to determine what type of code they have written things like "how do they control peripherals?", "Are they using a real-time operating system? If they are what type of tasks do they have and how are they organized" things like that. Also, take extra care to evaluate their error correction code like CRC checks on their memory and other corruption preventative measures.
Identify modules that could improve our design:
Now that you have your footing in the codebase and how it operates, try to identify some useful parts that are missing from our codebase that we could implement in our satellite. Once you find some bring it up with @GrahamDrive or @DaighB and we can discuss how it could be used.
Finally some coding!:
Now that you know what you want to add to the satellite you can try making a test project for a proof of concept. Go ahead and create a brand new project for your dev board and try to implement the given feature you have decided on. Have fun with it play around and add your ideas and flair.
Show off your work:
Now that you have completed the code and tested it you can show it off in a meeting!
University of Waterloo (UW Orbital)
This task will be regarding the University of Waterloos cube sat "UW Orbital" that won CSDC 2023 alongside UMSATS. The link to their repo can be found here.
As always if you have any questions don't hesitate to ask!
Reverse Engineer A Satellite Codebase
CDH member @whatdoes3plus1equalsto has found some open-source satellite projects that we could benefit from reverse engineering and analysis of their code bases. There are three parts to this task that I will list here.
Reverse engineer the given satellite codebase: Take a deep dive into the satellite's codebase. Try to determine what type of code they have written things like "how do they control peripherals?", "Are they using a real-time operating system? If they are what type of tasks do they have and how are they organized" things like that. Also, take extra care to evaluate their error correction code like CRC checks on their memory and other corruption preventative measures.
Identify modules that could improve our design: Now that you have your footing in the codebase and how it operates, try to identify some useful parts that are missing from our codebase that we could implement in our satellite. Once you find some bring it up with @GrahamDrive or @DaighB and we can discuss how it could be used.
Finally some coding!: Now that you know what you want to add to the satellite you can try making a test project for a proof of concept. Go ahead and create a brand new project for your dev board and try to implement the given feature you have decided on. Have fun with it play around and add your ideas and flair.
Show off your work: Now that you have completed the code and tested it you can show it off in a meeting!
University of Waterloo (UW Orbital)
This task will be regarding the University of Waterloos cube sat "UW Orbital" that won CSDC 2023 alongside UMSATS. The link to their repo can be found here.
As always if you have any questions don't hesitate to ask!