Lesson 5 of 6 · Danfe-II aboard PHI-1
Danfe-II: run an experiment aboard someone else’s satellite
8 minute lesson · 3 checks along the way
Your goal for this lessonSeparate a hosted payload’s responsibilities from its spacecraft’s shared services.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A Nepalese experiment on a UAE platform
Danfe-II is the Nepalese payload contribution to PHI-1, the first flight of the Payload Hosting Initiative involving the Mohammed Bin Rashid Space Centre and UNOOSA. PHI-1 is the UAE host spacecraft; the APN experiment is one contribution aboard it. The program also provided a hosted opportunity to Bahrain. These partnerships let teams develop particular experiments while the host supplies shared spacecraft services.
UNOOSA’s 2025 annual report records the actual launch on 28 November 2025 aboard a Falcon 9. It identifies the Nepal experiment’s objective of testing PX4 Autopilot in orbit. Earlier APN design presentations also describe an integrated computing, power and radio approach and LoRa work. Those design objectives are useful context, but the launch report does not prove that every proposed function achieved its target performance.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Define the boundary between payload and host
A hosted experiment must agree with the spacecraft team about physical mounting, electrical supply, commands, telemetry and allowed operating times. The is the collection of support systems that keeps the mission operating. Payload ownership does not mean ownership of the entire bus, and acceptance of a payload does not remove its integration responsibilities.
Consider an invented payload allocation of two watts. A processor uses 0.8 watts, its radio needs 1.6 watts while transmitting, and supporting electronics use 0.2 watts. Running all three together requires 2.6 watts, exceeding the allocation by 0.6 watts. The team could investigate scheduling, lower-power modes or a revised allocation with the host, but cannot simply assume that unused capacity elsewhere is available.
A payload must fit its agreed power allocation
Original teaching diagram. INVENTED SIMULTANEOUS LOADS. Processor: 0.8 W. Radio + support: 1.8 W. COMPARE WITH HOST LIMIT. Total 2.6 W; limit 2 W. Excess: 0.6 W. Scheduling or a revised design needs an explicit agreement and test.
Open full-size diagram in a new tab: A payload must fit its agreed power allocationCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Compare behavior across the full command path
A ground command may pass through the host’s receiver and software before reaching the experiment. Returned data follows another chain back to the researcher. To diagnose a missing result, preserve evidence at these boundaries: was the command received by the host, accepted by the payload, executed, stored and returned? A payload that ran correctly can still have an incomplete delivery record, while a received command does not establish successful execution.
Now imagine the host allows a ten-minute experiment window, but setup uses two minutes and safe shutdown one minute. Seven minutes remain for the actual experiment. The useful window is not the whole allocation. These numbers are teaching examples, not published PHI-1 operating limits. Hosted access reduces how much spacecraft infrastructure a team must build, while making interface agreements and shared-resource planning central parts of the engineering.
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.
- Read: UNOOSA: 2025 annual report and PHI-1 launchPrinted page 32 records the actual 28 November 2025 launch and Nepal’s PX4 payload objective. Printed page 18 contains Abhas Maskey’s first-person account; its mention of Munal’s launch does not establish orbital success.
- Read: Trishna Shrestha: Nepal’s PHI-I payload designMay 2023 APN presentation separates the LoRa/system-on-chip and PX4 demonstration objectives from the host satellite.
- Read: Eliza Sapkota: Nepal’s satellite projectsJuly 2023 project-team slides describe Munal, the Thai Danfe collaboration and the separate PHI-1 payload. Old launch forecasts are not outcomes; the Aalto-1 illustration is explicitly a reference picture.