CubeSat
A C&DH unit that can host the onboard software, with every interface carried over PC/104.
- SpaceWire
- I²C
- SPI
- CAN
- RS422
- RS485
- RS232
- GPIO
02 Platform
The onboard computer should not care who built the subsystem.
MA61C adapts between the communication interfaces and protocol standards of different suppliers, and presents one standard to the onboard software. That is the whole idea: integration stops being a negotiation.
01
Connect
Any subsystem, any supplier, through the interface it already has.
02
Recognise
MA61C matches the device against its embedded driver database.
03
Configure
The node installs the driver and adapts the protocol — no user intervention.
04
Route
Data is buffered, converted and forwarded to the onboard computer.
Without MA61C
- One harness, one driver and one test campaign per supplier
- Protocol translation written by hand, then re-validated
- Integration work that scales with the number of subsystems
With MA61C
- The node recognises the device and installs its driver
- Protocols are converted inside the adapter
- Integration work stays flat as the stack grows
SmallSat
The same plug-and-play behaviour for larger platforms, including a MIL-STD-1553 bus.
- SpaceWire
- MIL-STD-1553
- I²C
- SPI
- CAN
- RS422
- RS485
- GPIO
cPCI
Intelligent plug and play for a cPCI serial space processing unit — the backplane ESA and the EC chose for upcoming Copernicus missions.
- SpaceWire
- I²C
- CAN
- RS422
- RS232
- MIL-STD-1553B
- GPIO
Why it matters
One node, a longer shelf life.
When the interface is abstracted, a component can be reused across missions instead of redesigned. Suppliers stay interchangeable, and the bill of materials stops dictating the architecture.
- Fewer redesignsRe-use the same subsystem in a different scenario with minor changes.
- Shorter schedulesIntegration is configuration, not development.
- Wider supply chainComponents from more suppliers become candidates.
Next step
Bring your subsystem list. We will map the interfaces.
Send the components and the bus each one uses. We will tell you where MA61C sits, which variant fits, and what disappears from your integration plan.