Subsystem · RF

Communications

Link budget, antenna selection, latency under load at range over uneven ground — with an eye toward an aerial repeater for non-line-of-sight comms.

Lead position openTaking members

The rover has to stay reachable from an operator station that may be a kilometer away, over terrain that will not cooperate. Trees, rises and the rover’s own chassis all sit between the antennas at some point in a run, and the link has to carry control, telemetry and enough video for an operator to drive an arm.

That makes this a measurement problem before it is a hardware problem. We need real numbers for what the link actually does at range and under load — not datasheet numbers — and a documented failure mode for what happens when it drops mid-task.

What makes it hard

Range and reliability trade against bandwidth, and the operator needs all three at once. Video wants throughput; control wants low, predictable latency; range wants a narrow, well-aimed link that the terrain keeps breaking. Resolving that is the job.

The non-line-of-sight case is where an aerial repeater comes in — a relay that buys back the geometry the terrain takes away. Scoping whether that is worth the weight, power and regulatory overhead is an open question this subsystem owns.

What you’d get out of it

Practical RF: link budgets you can defend, antenna measurements you took yourself, and a field-proven radio system. Very little of this is taught in a class and all of it transfers directly to aerospace, defense and telecom work.

What you'd work on
Link budget math for a kilometer-class ground-to-ground link
Antenna selection, placement and pattern measurement on the rover
Latency and throughput characterization under real load (video + telemetry + control)
Fallback and failsafe behaviour when the link degrades or drops
Scoping an aerial repeater for non-line-of-sight segments

Tools

GNU Radio / SDR Spectrum analyzer, VNA Ubiquiti / RFD-class radio hardware Python for link characterization

Lead opening

Owns Communications end to end — the technical direction, the schedule, and the people.

Subsystem lead

Own the link end to end — architecture, hardware selection, and the field test plan that proves it.

LEAD OPEN

Member openings

Join the subsystem and own a piece of it. No lead experience needed.

RF test engineer

Build the range-test rig and produce the measurements the rest of the team plans against.

OPEN

Network / telemetry engineer

Video and telemetry transport, bandwidth budgeting, and graceful degradation.

OPEN
Apply to Communications