Space Vehicle Testbed Architecture for In-Flight Algorithm Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current space vehicles lack a robust architecture for in-flight development and testing of operational algorithms, particularly for rideshare-capable vehicles, which limits their ability to perform complex maneuvers like rendezvous proximity operations without modifying the primary control software.

Innovation Solution

A space vehicle with a testbed architecture that includes a massless payload with dynamically modifiable software and a primary controller, allowing for real-time testing of operational algorithms without modifying the underlying control software, along with a modular liquid propellant thruster system for maneuvering, enabling transparent control of actuators and sensors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a space vehicle uses a fixed primary control software for normal operation, then reliability is improved, but adaptability deteriorates

Engineering Contradiction:
Improvecontrol software reliabilityVSAvoidalgorithm testing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The control software is segmented into a stable primary controller and a separate testable payload software module. The primary controller maintains fixed, reliable control logic while the payload software can be independently modified and tested, resolving the contradiction between reliability and adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A test controller acts as an intermediary between the primary controller and operational systems. This intermediary enables algorithm testing without modifying the primary control software, maintaining reliability while providing adaptability for testing new algorithms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the space vehicle modifies primary control software to test new algorithms, then adaptability is improved, but reliability deteriorates

Engineering Contradiction:
Improvealgorithm modification capabilityVSAvoidcontrol software stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

By separating control functions into a immutable primary controller and a modifiable payload software layer, the system allows algorithm testing without touching the core control software, thus maintaining reliability while enabling adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The test controller creates a virtual copy of the control environment to test new algorithms. This copying approach allows testing of modified algorithms in a safe environment without affecting the reliability of the primary control software.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the space vehicle uses a massless payload with dynamically modifiable software, then adaptability is improved, but device complexity deteriorates

Engineering Contradiction:
Improvesoftware modifiabilityVSAvoidcontroller architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The test controller is designed as a universal platform that can load and execute different payload software modules. This multi-functionality approach consolidates testing capabilities into a single device, reducing overall system complexity while maintaining high adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Productivity

If the space vehicle implements in-flight testing of operational algorithms, then productivity is improved, but device complexity deteriorates

Engineering Contradiction:
Improvealgorithm development efficiencyVSAvoidtestbed architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The test controller autonomously manages the testing process, automatically loading payload software, configuring test parameters, and monitoring results. This self-service capability eliminates the need for complex external testing infrastructure, improving productivity while keeping device complexity manageable.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240400232A1Space vehicle with testbed architecture for in-flight development and testing of operational algorithms
Publication Date: 2024.12.05 RAYTHEON CO
  • US20240400232A1 patent drawing
  • US20240400232A1 patent drawing
  • US20240400232A1 patent drawing

AI summary

A space vehicle includes a massless payload. The massless payload comprises dynamically modifiable software configured to indicate one or more actions to be taken by the space vehicle. The space vehicle also includes a primary controller that includes software that is not modified based on modifications to the massless payload, a test controller operatively communicating with the massless payload. The system also includes one or more operational systems including at least one of actuators or sensors of the space vehicle that are controlled based on commands from the test controller during a test condition generated to implement the one or more actions indicated by the massless payload and by the primary controller during normal operation.