Recurring LEO SmallSat programmes spend weeks on the same integration workload every time: interface alignment, command/telemetry mapping, inhibit verification, EGSE setup, and generating the evidence that the configuration actually works. Block 01 packages that entire layer — CAN · UART · CSP OBC adapter, S-band radio interface, EGSE software, automated test scripts, and a real verification report — so missions configure and verify a proven baseline.
Across recurring LEO small satellite programmes, teams still repeat the same interface clarification, EGSE setup, command/telemetry mapping, inhibit verification, and evidence-generation work. Tesseral Orbital Systems turns that repeated work into a reusable integration package.
Even when ICDs exist, mission-specific alignment often remains unresolved until AIT: message formats, connector assumptions, timing, inhibit polarity, and test procedures. Tesseral Orbital Systems pushes those definitions into a controlled baseline early.
Test procedures, acceptance matrices, and command/telemetry dictionaries are repeatedly adapted mission by mission. Tesseral Orbital Systems packages them as version-controlled artefacts linked to the building block.
Acquiring a TT&C transceiver opens an integration campaign that typically takes weeks: OBC driver porting, CMD/TM mapping, inhibit verification, EGSE setup, test scripting, and evidence generation. Tesseral Orbital Systems packages all of it as a single validated artefact.
The TT&C FlatSat Integration Kit is a complete, validated integration package covering the full spacecraft-side TT&C layer: OBC adapter (CAN · UART · CSP), S-band radio interface, CMD/TM dictionary, ICD, EGSE software, automated test scripts, configuration templates, and a documented verification report — a single repeatable element that recurring LEO SmallSat missions configure and verify from a proven baseline.
Block 01 delivers a validated S-band RF integration path: interface characterisation, acceptance test evidence, and end-to-end flat-sat verification that the radio-to-OBC link performs correctly under realistic conditions.
The integration layer between the TT&C radio and the OBC. CAN for primary spacecraft-bus control, UART for direct serial configuration, CSP for CubeSat Space Protocol-compatible OBC ecosystems — fully defined and documented in the ICD package.
Structured Interface Control Document and defined CMD/TM dictionary — intended to reduce interface re-definition work at the start of each integration campaign.
EGSE software, automated test scripts, and test procedures packaged as version-controlled artefacts. The verification matrix is pre-populated from the flat-sat campaign — AIV teams inherit a completed, evidence-backed test baseline from day one.
The kit ships with a documented verification report from the flat-sat campaign — evidence that the configuration was assembled, tested, and signed off in a realistic setup. This is the artefact that compresses the first integration review cycle on the next mission.
TT&C is present in nearly every LEO small satellite mission. Yet despite its recurring nature, the integration work remains custom on almost every programme: RF interface alignment, OBC driver porting, command/telemetry mapping, inhibit verification, EGSE scripting, and evidence generation.
TT&C is the highest-leverage entry point for the block family. Nearly 2,800 smallsats were launched in 2024 — 97% of all spacecraft by count — and the average mass is rising toward 223 kg, meaning more capable missions with tighter integration schedules. Every one of them has TT&C. Validating the kit approach here — with well-understood requirements, a constrained interface envelope, and a direct dependency from mission-level verification milestones — creates the reusable framework that subsequent blocks (EPS, ADCS, OBC, payload) replicate and extend.
Each of these touchpoints is typically addressed independently per mission — even when a COTS radio is used. The TT&C FlatSat Integration Kit pre-solves and packages all of them as a single repeatable artefact.
The first Tesseral Orbital Systems product concept is an engineering demonstrator and pretotype. Its purpose is to turn the S-band TT&C interface envelope and verification baseline into a repeatable package that can later mature toward qualification.
ENGINEERING STATUS: The TT&C Building Block v0.1 is an engineering demonstrator and pretotype. Its scope is integration architecture, interface definition, EGSE workflow, flat-sat logic, and verification evidence. Qualification, environmental testing, and flight acceptance are planned development steps, not current-stage claims.
The Block 01 roadmap is structured around progressive demonstration confidence — from interface definition through flat-sat validation toward a qualification-ready TT&C building block. Each phase builds the validated framework that the block family will extend to additional subsystems.
Define the kit scope and interface envelope. Build the engineering demonstrator around a validated COTS radio with CAN · UART · CSP OBC adapter. Develop ICD, CMD/TM dictionary, configuration templates, and EGSE software baseline. Engage early mission partners to validate the pain point and kit structure.
Execute the flat-sat demonstration campaign: assemble the full kit (COTS radio + OBC adapter + EGSE + test scripts), run automated test scripts, and generate the verification report with real test evidence. This is the milestone that makes Block 01 a credible, repeatable commercial product.
Subject the EM to a relevant environmental test programme, such as thermal-vacuum and vibration where applicable, to characterise behaviour and establish a qualification baseline. Update the verification matrix with test results and maintain ECSS-style documentation discipline.
Integrate the validated TT&C building block into a real LEO small satellite mission as a flight model candidate. Collect integration feedback, measure recurring effort reduction versus baseline, and iterate toward a repeatable commercial product offering.
Tesseral Orbital Systems is building a family of modular subsystem integration blocks for recurring LEO SmallSat missions. Block 01 — TT&C — is the entry point: a complete integration element covering interfaces, ICD, CMD/TM dictionary, EGSE, and verification evidence.
For recurring LEO SmallSat teams, the target is simple: fewer late interface surprises, faster bench readiness, and less repeated work around ICDs, CMD/TM dictionaries, EGSE setup, inhibit verification, and acceptance evidence.
Start a Pilot →