Lesson 5 of 5 · GOLDS-UFSC and payload validation
GOLDS-UFSC: validate the payload and its interfaces
8 minute lesson · 3 checks along the way
Your goal for this lessonUse a documented receiver test to distinguish a payload fault, an interface fault and evidence of complete mission performance.
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 particular mission within a broader collection effort
GOLDS-UFSC is a UFSC SpaceLab mission designed to validate INPE’s Environmental Data Collector, or EDC, using a platform derived from FloripaSat 1. Its mission documentation also describes technology and radiation experiments and amateur-radio relay goals. The broader GOLDS collection system and this individual demonstration mission are different levels of the architecture. They should be connected in the learning map without being merged into a single spacecraft identity.
INPE’s October 2026 catalog calls a related UFSC-led development project EDC-UFSC: a FloripaSat 1-based satellite and for testing the Environmental Data Collector. UFSC’s project-agreement record separately names GOLDS-UFSC development and EDC testing. These documents connect the institutions, and platform lineage. They do not justify treating every FloripaSat-2 or Catarina flight as the same spacecraft. Here both documented project names are covered together, while exact flight configurations remain distinct. SpaceLab’s legacy floripasat2-doc repository name likewise does not establish an exact alias for every later flight.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A receiver can work while its command interface fails
The June 2023 design report includes a March 2022 laboratory test of EDC boards. Initially, the command did not return expected responses. Investigation identified a problem with the signal’s low logic level and considered interference from a shared RS-485 interface. A temporary software change disabled that interface, while the report recommended a more appropriate flight-board solution. The test also decoded the supplied radio packets successfully under its stated setup.
This is a useful troubleshooting lesson because silence on one interface did not establish that every part of the receiver was broken. The team separated command handling from the radio chain and examined the signal at an intermediate boundary. A successful test after a change should retain the board and software versions so the result can be reproduced. A temporary workaround and a verified flight are not interchangeable descriptions.
Trace one packet through the system
Original teaching diagram. Known input: 100 packets. Receiver decodes: 100. Computer records: 92. Locate the missing eight. Compare boundary logs. Verify the final configuration. Original example; the documented EDC laboratory tests are not an orbital mission result.
Open full-size diagram in a new tab: Trace one packet through the systemCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Design the next check around what remains unknown
For an original exercise, suppose a receiver decodes 100 known test packets but its control computer records only 92. The missing eight require investigation along the handoff and storage path; the receiver result alone cannot establish complete delivery. Compare identifiers and timestamps at each boundary to locate where the records diverge. Keep the test stimulus known, so the expected result does not depend on guessing what was transmitted.
Laboratory evidence also has environmental limits. Cable-connected radio tests do not reproduce every orbital propagation condition, and a planned mission does not prove that it has flown. The GOLDS-UFSC documentation is valuable precisely because it exposes methods, intermediate findings and remaining work. Build a simple verification table with the input, observation point, expected output and unresolved conditions. That habit turns a promising payload into a system whose performance another team can meaningfully assess.
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: UFSC SpaceLab: GOLDS-UFSC mission designJune 2023 design report: PDF page 18 states the mission purpose; pages 127–131 describe March 2022 interface and radio-chain tests. Draft plans and laboratory results are not orbital achievements.
- Read: UFSC: 2024 project agreementsAgreement 2024/0095 separately identifies development and implementation of GOLDS-UFSC for data transfer and EDC testing, with a term extending through 2027.
- Read: NASA: product realizationCompare the explanation and its assumptions with the worked example in this lesson.
- Read: INPE: October 2026 project catalogPDF page 98, printed page 95, names EDC-UFSC, its FloripaSat 1-based flight-model objective, EDC payload and ground-system work. This is a development description, not an orbital result or proof that every later spacecraft name is an exact alias.