Overview • Missions • Projects • Competitions • Team • Partners • Versioning • Licenses
SpaceLab brings together several research groups from the Federal University of Santa Catarina (UFSC), Brazil. The different groups conduct research and development activities in space systems in general, aiming to make space more accessible not only to the scientific community but also to the industry. Featured missions include FloripaSat-1, FloripaSat-2, and GOMX-5.
This organization combines repositories for different projects, files and documents. The following sections briefly describes the main repositories and their relation to the SpaceLab's major space campaigns.
SpaceLab has complete CubeSat space missions developed in-house under open-source licenses: FloripaSat-1, an 1U CubeSat, and FloripaSat-2, a 2U CubeSat.
This CubeSat mission was the first attempt to develop a complete satellite mission in-house (with some COTS subsystems). The service modules were designed and developed by the SpaceLab team, which started with prototype versions until the actual flight model. The original GitHub organization used in this mission was the FloripaSat, but it was descontinued in order to accomodate all SpaceLab projects in the same place. The mission repositories and related projects in this organization are:
- OBDH (On-Board Data Handling module)
- EPS (Electrical Power System module)
- TTC (Telemetry, Tracking and Command module)
- GRS (Ground Station Firmware)
- Payload-X (Payload-X firmware)
- Decoder (SpaceLab Packet Decoder)
- DOC (Some documentation files)
This CubeSat mission is a second generation development, which uses the FloripaSat-1 core and flight heritage. The mission consists of a 2U CubeSat designed in-house (with some COTS subsystems). The following repositories includes all the avaliable sources:
- DOC (Mission documentation)
- OBDH 2.0 (On-Board Data Handling module 2.0)
- EPS 2.0 (Electrical Power System module 2.0)
- TTC (Telemetry, Tracking and Command module)
- Battery Module
- GRS (Ground Station Firmware)
- PC-104 Adapter
- Interface Modules
- MEC (Mechanical assembly)
- FlatSat
- Decoder (SpaceLab Packet Decoder)
Besides missions, the SapceLab has standalone projects:
In order to train the next generation of undergraduate students for future opportunities, the lab supports initiatives for taking part in contests and events in the aerospace sector. Efforts are focused on attracting new students and outreach SpaceLab to the community. Currently, there are two groups associated with SpaceLab: FloripaSat, a CubeSat competition group, and the Apex Rocketry, a rocket competition team.
This list considers current members of this GitHub organization. For a more complete list, refer to FloripaSat-1 team and SpaceLab team.
Refer to the SpaceLab partners page.
The repositories have different versions depending on the development efforts and duration. Then, it is important to refer to the documentation (in the mission repository, for example) which versions are compatible with all the modules and subsystems. The scheme followed try to minimize errors and misunderstandings by synchronizing macro versions within a mission using releases and presentend simple version and status badges. The main versioning system is the GitHub release feature itself, giving the status badges only a quick overview of the project for external viewers. For example, each module within the FloripaSat-2 mission follows a vX.Y.Z versioning scheme, in which Z determines minor self contained changes, Y sets relevant amount of changes or important checkpoints, and X major mission checkpoints. In this case, the flight version might be a v1.0.0 or higher. As aforesaid, the badges are only used for quick status verification and uses the following structure:
The SpaceLab follows a strong open-source approach in order to encourage and promote knowledge. Then, refer to the LICENSE file in the GitHub page for each repository. In general, the licenses used are GPLv3 for firmware/software, CERN OHL-S v2 for hardware, and CC-BY-SA-4.0 for documents. Please, double check licenses and third-part components used with other licenses, since restrictions might apply.