NOS3

Documentation:

  • Home
    • Introduction
    • Modules
    • FAQ
      • Why should NOS3 be used?
      • When should NOS3 be used?
      • How should I go from NOS3 as is to my specific mission?
      • How to move from software / simulator to hardware once it arrives?
      • What can NOS3 give me during Integration and Testing (I&T) ?
      • How to a move from software / simulator to hardware once it arrives?
  • Getting Started
    • Installation
    • Running
  • Igniter
    • The Configuration Tab
      • Master Config
      • Spacecraft Config
    • The Build Tab
    • The Launch Tab
  • Architecture
    • Satellite(s)
    • Middleware - NOS Engine
    • Dynamics
    • Directory Layout
  • Flight Software
    • Standalone Checkout
    • core Flight System (cFS)
      • Operating System Abstraction Layer
      • Platform Support Package
      • Hardware Library
      • cFS Heritage Applications
    • cFS Tables
      • DS Tables
      • SC RTS Tables
    • F’
      • Configuring NOS3 to Use F-Prime:
      • Sending a Sample NOOP Command:
      • Creating an F-Prime Component in NOS3:
      • F-Prime NOS3 Time Component (Nos3Time):
      • F-Prime Documentation links:
  • Ground Systems
    • YAMCS - Yet Another Mission Control System
      • YAMCS Studio Integration
      • YAMCS and OpenMCT
    • COSMOS 4
      • COSMOS 4 to cFS Command and Telemetry Link Up
    • COSMOS 5
      • COSMOS 5 to cFS Command and Telemetry Link Up
      • AIT
      • F Prime GDS
    • Selecting Ground System
    • Packet Formatting
  • Components
    • Generic Components
      • Component Information
      • Component Development
    • Integrated Algorithms
      • Attitude Determination and Control System (ADCS)
      • CryptoLib
      • OnAir
      • Synopsis
  • Simulators
    • Architectural Whys
      • Why NOS Engine?
      • Why Hardware Models, plug-ins, abstract factories, etc.?
      • Why Data Providers?
    • Background and Supporting Concepts
      • Abstract Factory Design Pattern
      • XML Configuration
    • Implementing Your Own Hardware Model (and Data Provider, and Connections)
      • Configuration Data Property Tree
      • Hardware Model
      • Data Provider
      • Connections
        • Command Connection
        • Time Connection
        • UART Connection
    • Writing Your Own Simulator
    • Example Simulator
  • Design Reference Mission
    • Concept of Operations
    • Limited Performance Test
    • Comprehensive Performance Test
    • Operations Cheat Sheet
NOS3
  • NASA Operational Simulator for Small Satellites
  • View page source

NASA Operational Simulator for Small Satellites

Welcome to the NASA Operational Simulator for Small Satellites (NOS3) User’s Manual and Developer’s Guide. This documentation is designed to provide information for users and developers that intend to utilize, enhance, and extend NOS3.

Documentation:

  • Home
    • Introduction
    • Modules
    • FAQ
  • Getting Started
    • Installation
    • Running
  • Igniter
    • The Configuration Tab
    • The Build Tab
    • The Launch Tab
  • Architecture
    • Satellite(s)
    • Middleware - NOS Engine
    • Dynamics
    • Directory Layout
  • Flight Software
    • Standalone Checkout
    • core Flight System (cFS)
    • cFS Tables
    • F’
  • Ground Systems
    • YAMCS - Yet Another Mission Control System
    • COSMOS 4
    • COSMOS 5
    • Selecting Ground System
    • Packet Formatting
  • Components
    • Generic Components
    • Integrated Algorithms
  • Simulators
    • Architectural Whys
    • Background and Supporting Concepts
    • Implementing Your Own Hardware Model (and Data Provider, and Connections)
    • Writing Your Own Simulator
    • Example Simulator
  • Design Reference Mission
    • Concept of Operations
    • Limited Performance Test
    • Comprehensive Performance Test
    • Operations Cheat Sheet
Next

© Copyright 2025, NASA-JSTAR.

Built with Sphinx using a theme provided by Read the Docs.