SimulatorOne-axis ADCS · training twin

Mission run console

Software-first attitude control lab: command targets, tune PID, observe settling — honest simulator mode until a gateway connects bench hardware. For meeting captures, use presentation spacing and compact compare.

← Portal dashboard
PilotInvited? Enter your access code to start a guided pilot session.
Pilot Session →

Quick orientation

Software-first one-axis attitude twin: command Target °, then observe Actual ° response and settling. Live session is for active simulation, Replay is for post-run review, and Compare is optional A/B debrief. Mission story adds bounded teaching context (sunlight/contact/power) on top of the same simulator run.

  • Start here: New session → (optional) scenario/context/profile → Start run.
  • During live run: adjust target and controller to shape response.
  • After run: switch to Replay, select run A, then add run B only if you need comparison.
  • Use Scenario exercise and Mission framing for structured teaching context, not flight-operations realism.
Read a bit more

Target angle is the commanded attitude on this axis; actual angle is the simulated response. Replay reads stored simulator runs, while compare overlays run B against run A for debrief. Bench hardware uses a separate gateway path when enabled — this route stays simulator-first unless the telemetry path explicitly shows bench-backed mode.

Review mode controls

Live session: run the simulator now. Replay: load a completed run for debrief. Compare: add run B for A/B overlays and summary deltas. Typical flow: stop a live run, then Refresh runs, pick A, optionally pick B.

Scene behavior: the 3D panel mirrors live session data in Live mode and run A posture in Replay mode. Compare adds chart/table overlays but keeps scene focus on run A for presentation clarity.

Demo capture ready: Replay mode + run A selected + no run B, then enable presentation spacing in the hero. Select run A to stabilize composition

At a glance

Console mode

Live session

Analysis path

Live — step the sim

Run state

—

Telemetry path

—

Session

—

Target °

—

Actual °

—

Scenario exercise

—

Mission framing

—

Mission profile

default (until run starts)

Live quick actions

Connecting…

Full run controls stay in Command & control to keep this top strip capture-friendly.

3D attitude (one-axis teaching scene)

Scene-first view for live demos and classroom framing. This page teaches one-axis control only: solid cube = actual body attitude, wireframe ghost = target attitude, wheel cue = internal reaction-wheel actuation on the same axis.

Demo presentation: This simulator demonstrates spacecraft attitude control using a single reaction wheel. The 3D scene shows intuitive turning motion, while the 2D top-view provides precise angle confirmation. Use Replay mode for stable screenshots.

One-axis ADCS teaching model
ACTUAL body —TARGET —
Z — controlled hanging axisWheel idleBody holdTarget alignedFace map: +X front, -X rear, +Y right, -Y left
Body holding near target (left/right in front view)Phase: waiting

Start a run to see 3D attitude

2D top-view attitude

+X (front face reference)+Y (right face reference)-X (rear face)-Y (left face)Rotation about Z (hanging axis)
ACTUAL body —
TARGET —
ERR —
Wheel IDLE
0.0 rpm
Waiting
Motion phase

Capture tip: for clean screenshots use Replay with run A selected and presentation spacing enabled. Keep compare optional unless the screenshot specifically needs A/B evidence.

Replay demo default keeps hero stable: run A drives both 3D scene and top-view while tables/charts provide supporting evidence below.

Mission story (teaching abstraction)

Same attitude-control simulator, with a bounded mission-context overlay: profile-driven sunlight/eclipse state, duty-cycle contact opportunity, and simplified battery/load math for interpretation. This is educational mission framing, not propagated orbit analysis, not STK, and not flight-certified EPS behavior.

Start a live run to see mission-analysis fields (telemetry schema 1.10).

Operator notes — profile catalog & assumptions

Profiles ship in-repo as mission_profiles.json with a YAML mirror under docs/contracts/. See docs/twin/V110_ORBIT_AND_ENVIRONMENT_MODEL.md and docs/twin/V110_POWER_MODEL.md. Use this strip to teach operational interpretation, not to claim physical pass prediction.

Run status

More run metadata (controller, health, mission phase, scenario stage…)

Controller

—

Health

—

Settle

—

Mission mode

—

Mission phase

—

Scenario stage

—

Remote lab control plane (operator scaffold)

Supervised / developer testing only. This is not open internet hardware access. Simulator claim below; bench mode requires gateway env + local kit (see operator docs).

Command & control

Demo-safe order: choose optional scenario/context/profile, press Start run, adjust target, then use Replay for debrief.

Scenario exercise (optional)

Structured lab track from the scenario catalog (stages / objectives). Leave as free run for quick unstructured demos.

Mission context override (optional)

Bounded mission context on the same telemetry (mode/phase for debrief). Auto uses scenario-recommended context, then related-scenario fallback if available.

Mission analysis profile (optional)

Teaching-oriented orbit/contact/power abstraction (V1.10). Leave default unless you are demoing a specific exercise or compare story.

Target angle (°)

PID & controller tuning

Controller name

Kp

Ki

Kd

Live loop: idle (no steps)

Scenario presets (catalog sequences)

Each preset issues a documented simulator command sequence. For meetings/classrooms, start with one conservative preset, then capture replay before trying advanced ones.

If a live run becomes noisy, stop the run, switch to Replay, and continue the debrief from the latest saved run.

Live telemetry

Current angle (°)

—

Target angle (°)

—

Angle error (°)

—

Gyro rate (°/s)

—

Wheel RPM

—

PWM

—

More telemetry fields (health, faults, commands, framing…)

Motor dir.

—

Health

—

Fault flags

—

Settle state

—

Mode

—

Last command

—

Classroom / demo cue

No telemetry

Waiting for a session from the twin API.

Time series

Target vs actual angle (°)

Start a run to populate charts

Angular rate (°/s)

Start a run to populate charts

Wheel RPM

Start a run to populate charts

PWM command

Start a run to populate charts

Battery SOC % (mission model)

Start a run to populate charts

Power & generation (mission model)

Start a run to populate charts

Run summary and evidence

Snapshot metrics from the latest telemetry frame; peak wheel speed tracks the current run segment.

Screen-share order: show Target vs Actual, then score/outcome, then mission line.

What to notice: settle time, final error, and overshoot first; then read mission evidence line for context; use compare only when a specific A/B claim is needed.
Settle time (ms)
—
Overshoot (°)
—
Final error (°)
—
Max |wheel| RPM
0.0
Outcome
—
Scoring & narrative detail

Start a preset or configure target and PID, then run the simulator to populate this summary.

Mission design lab

Pilot experiment catalog

Structured digital twin experiments from the V1.13D catalog. Select an experiment to see setup instructions, guided start steps, and evidence guidance. All experiments run on the simulator — hardware lane is deferred. In guided pilot mode, the grid lists Pilot Ready activities only; open /twin/experiments without guided mode to browse with maturity badges, or use ?experiment_maturity=all.

Choose an Activity

Start with the card marked Start here, then review replay evidence and submit feedback.

Why this matters

This activity connects feedback control, rotational motion, and spacecraft pointing.

0 of 0

No experiments match the selected filter.

STEM outcome note

These are flexible STEM learning outcomes, not an official curriculum mapping.

Hardware path (operator bench)

This page uses the simulator. For a physical kit on the bench, operators use the separate bench API (POST /api/thin-twin/bench/sessions) with CUBETWIN_HARDWARE_BENCH_ENABLED=1 — local only, not public remote lab. enable_hardware stays rejected on simulator sessions here.

Commercial framing: Lead with software-first value (repeatable labs, no shipping delay). Position hardware as a future bundle tier—never imply this page is controlling a physical kit today.

See docs/contracts/TWIN_HARDWARE_BOUNDARY.yaml in-repo.

Local bench telemetry trust (manual lookup)

Optional local check for operator-supervised bench sessions. This reads local gateway status only; it does not expose public remote control.