Lesson 1 of 6 · ACCESS Nanosat and Maya-7
ACCESS Nanosat: learning through Maya-7
8 minute lesson · 3 checks along the way
Your goal for this lessonConnect a university satellite project with design reviews, engineering practice and reusable knowledge.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A project that teaches the whole mission
ACCESS Nanosat combines graduate study at the University of the Philippines with practical satellite engineering. PhilSA supports and mentors the work, continuing an academic pathway developed under STeP-UP and STAMINA4Space. Participants learn mission planning, design, testing and operations. AD ASTRA scholarship support has its own application and acceptance process; joining a project and receiving a scholarship are distinct decisions.
Maya-7 is the project’s two-unit CubeSat. PhilSA reported its preliminary design review in June 2023, with payload contributions from several universities. The review examined designs against mission objectives and requirements. That is a documented development milestone. The old announcement’s proposed launch year must not be mistaken for a record that the satellite actually reached orbit.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A design review asks connected questions
Consider a fictional camera payload that needs more power than the original mission allowed. Its developers cannot solve the issue by checking the camera alone. Battery capacity, solar generation, operating schedules and thermal behavior interact. The team might reduce observation time or revise the system design. A review makes those interactions visible while changes can still be evaluated against the mission’s purpose.
A useful review records the assumption, the concern and the action needed to close it. A diagram showing a connected cable does not establish that two devices exchange compatible data. Interface requirements and tests establish that. Likewise, the word CubeSat describes a standardized form factor; it does not guarantee a common payload, identical electronics or successful integration between every pair of modules.
Learning across a satellite project
Original teaching diagram. Engineering evidence. Requirements and interfaces. Design reviews and tests. Lasting capability. Train successive teams. Preserve decisions and results. A development milestone is not an orbital mission result.
Open full-size diagram in a new tab: Learning across a satellite projectCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Preserve knowledge beyond one student team
A university project must survive changes in its participants. Imagine a graduating student who leaves working software but no explanation of its configuration or test results. The next team may have to repeat avoidable work. Versioned designs, operating notes and records of unsuccessful tests help preserve the reasoning behind the hardware, making the project an educational resource beyond one launch attempt.
Success therefore has several dimensions: students develop skills, teams create documented engineering knowledge, and a spacecraft may later demonstrate a mission in flight. These outcomes support one another but require different evidence. A graduation record does not certify a satellite’s flight status. A launch does not by itself show that another university can reproduce the design. Ask which capability was demonstrated, under what conditions, and who can carry it forward.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.