Mission Instrumentation

Mission Goal

Build a simple “space beacon” that continuously broadcasts an identifiable signal and can be detected and verified by another device.

Why This Matters

Early satellites proved they were alive by broadcasting simple, repeatable signals. A reliable beacon is the first step in comms, tracking, and mission confirmation.

What Data You Collect

• Beacon ID (e.g., team name + satellite callsign)
• Uptime counter (seconds since start)
• Optional: temperature (°C) or light level as a “payload byte”

Hardware / Software Needed

• 2 × BBC micro:bit (v1 or v2) or 1 micro:bit + 1 laptop/phone as receiver
• Micro:bit editor (MakeCode recommended)
• USB cables / battery packs (optional)

Inputs From Other Teams

• Comms: Agree a callsign format and what “valid message” means.
• Data: Suggest a simple logging format (CSV lines or structured text).
• Command & Control: Define “beacon online” success criteria for mission readiness.

What You Must Produce (Deliverables)

• A micro:bit beacon program that broadcasts repeatedly.
• A receiver method (second micro:bit or device) that proves messages are being received.
• A short “Beacon Spec” (callsign, message format, send rate).

Step-by-Step Build

1. Choose your callsign (e.g., MI-TEAM5-S1).
2. In MakeCode, create a loop that sends a radio message every 1–2 seconds.
3. Include: callsign + uptime counter (and optional sensor value).
4. Set radio group/channel number agreed with your class.
5. On a second micro:bit (or laptop console if you have one), display received messages.
6. Test at 1–5 meters; then test farther away and record when messages start failing.

Data Format / Output

Recommended message format (plain text):

• CALLSIGN|UP=123|T=21

Analysis Ideas

• Plot “messages received per minute” vs distance.
• Measure dropouts: longest gap between received beacons.
• Compare send intervals (1s vs 2s) and reliability.

Success Criteria

• Receiver confirms at least 30 consecutive valid messages.
• Message format matches your Beacon Spec.
• Team can explain what each field means and why it’s included.

Evidence Checklist

• Photo of the beacon running (micro:bit display or LED indicator)
• Photo/screenshot of receiver showing messages
• Beacon Spec (callsign, format, rate)
• Short note: tested range + observed dropouts

Safety & Privacy

• Do not broadcast personal data (names, phone numbers).
• Use classroom-safe radio group settings to avoid interference with other groups.
• Keep cables tidy; avoid trip hazards during range tests.

Common Failure Modes

• Beacon and receiver on different radio groups.
• Messages too frequent causing collisions.
• Receiver code only displays last message without validating format.
• Power issues (loose USB, low batteries).

Stretch Goals

• Add a checksum digit (simple sum of digits mod 10).
• Add a “heartbeat pattern” (LED blink) synchronized to sends.
• Implement message validation: ignore messages without correct callsign prefix.