Communications constellations
- What gets flown
- RF front-ends, SDRs, power conversion and baseband processing.
- Typically characterised
- Power per mode, thermal drift of frequency and output power, SEFIs in processing.
What your team controls on a single-payload mission, what gets flown per segment and what fits in the slot.
Power-ups, duty cycle, voltage and temperature sweeps and logging cadence are defined for your DUT at kick-off and adjusted in orbit if the data calls for it.
Parts from the same family, lot or process in the same payload slot. Power, channels and test time split agreed before flight.
SEE, SEL, thermal drift and TID degradation measured over months, to check against your beam and TVAC campaigns and tune your rate models.
Platform TM —per-line V/I, temperatures, attitude, position— is logged on the same time base as your channels: every event comes with its context.
Raw and processed data belong to the customer, with no licence reserved: publishable, usable in a qualification package or shareable under NDA.
A certificate with dates, orbit, accumulated environment and observed behaviour, cross-referenced to the performance report and the dataset.
Propagation, eclipses and β angle of the reference orbit, live.
Open mission control
Indicative. The actual measurement plan is closed at kick-off, against the channels and resources in the ICD.
ITAR or EAR content? See export control.
Power, computing, memory, baseband RF, sensors without line of sight, detector electronics without their own optics.
Optics and detectors with an aperture, antennas, magnetometers or other field sensors away from the bus. External access for the payload: [PENDING].
Propulsion, cryogenics, fine pointing, high continuous power, bulk data download or more than 1U of volume.