There are some things that needs to be clear in the report and these are:

• Communication Protocol stack internal satellite
• Communication Protocol stack ground segment
• Why CAN? Which version?
• Mechanical structure standards used
• Why PC104 with only one? Why I use this over the 40 pin connector of DTUSAT?
• Why CCSDS? What are the benefits?
• Is there Error correcting protocols? CRC?
• Power consumption of each subsystem
• Why LoRa and not VHF/UHF? Why WiFi?
• What is the educational approach? How it would look a educational workshop with this CubeSat?
• Is it possible to adapt for CANSAT or nanosatellite?
• Cost of each subsystem?
• Why I reused the OBC from DTUSAT? How I adapted to my design
• Why I used ESP32 over other platforms?
• How it would be possible to add new subsystems?
• What are the existing cubesat standard? What are the missing standards?
• Why is necessary an standard?
• The importance of simulation platforms
• Why you know that the standards are being followed? Specially “de facto” standards.
• State what are the standards / protocols used, and how I implemented them
• Why PC104?

Decisions made

• Why PC104? ✅
• Why a distributed architecture?
• Why CAN and not i2c? IMPORTANT TO WRITE ABOUT ✅
• Why ESP32?
• Why LoRa? IMPORTANT TO WRITE ABOUT
• Why WiFi?
• Why not using CSP? ✅
• Why COSMOS?
• Why CCSDS? ✅

From the Master thesis of Blanca I conclude that, the chapter of theory is the one about making decisions.

Things that took me time in the thesis

The things that took me some time at the thesis was:

• Linux device tree.
• CAN Communication between OBC and subsystems. Fragmentation and reassembly.
• Mechanical structure deciding how to screw from top
• CAN libraries on ESP32S3
• Communications of the COM, first SX1272 and then RFM95

Structure of the Report

Check the rules from birte at the end of the report.

July Missing things

On the trip to Umea I want to have a close approximation of the master thesis:

Design:

• Introduction -> 90%
  • Missing: Some things about requirements and summaries from theory
• COMM -> 100%
• Prototype -> 80%
  • Missing:
    • Talk about the software
    • Define the possible CAN messages
• OBC -> 95%
  • Missing
    • Maybe a description of the possible messages(?)
• Ground segment -> 95%
  • Missing:
    • [DISCARTED] Telemetry/telecommand definition

Resuls:

• Assembled version
• Test telemetry, some pictures of graphs

Conclusion: 0%

Future work: 0%