← IntegrationsGround system API

YAMCS

Open-source mission control for spacecraft and ground equipment.

Connect with a URL and an instance name. Every parameter arrives described — units, groupings, enumeration states and your own alarm ranges — with no mapping step.

Run against YAMCS 5.13.5, with security enabled.

Live dashboard on a YAMCS simulator →
What Plexus reads
  • The mission database over the REST API, paged to the end — units, engineering types, enumeration states and alarm ranges
  • The parameter archive, for history
  • The processor's active alarms: severity, trigger time, the reading that tripped it, and YAMCS's own severity word
What it does not read
  • Anything you have not pointed us at — one instance, one credential, read-only
  • Commands. Plexus cannot command through YAMCS; the capability was removed from our adapter contract rather than left as a stub, because commanding a vehicle has a different safety bar than reading one
  • Aggregates, arrays and absolute times, which have no honest representation as a time series and are dropped rather than coerced
Connecting it
  1. 1Your YAMCS URL
  2. 2The instance name, as shown in its own top bar
  3. 3A username and password, only if that instance has security enabled

Their documentation: docs.yamcs.org

Worth knowing
  • History comes from the archive's sample endpoint, so stored values are interval averages and are labelled as such. Raw parameter history is the next step, not a claim we make today.
  • Roughly a third of a YAMCS mission database is YAMCS describing itself — JVM memory, link rates, queue depth — namespaced under the server's own id. Those are shown and searchable, and deliberately not stored, because their keys do not survive a redeploy and nobody should pay to keep them.
If you build it

Plexus is not a replacement for YAMCS. Your console is for the person operating the machine; ours is for the people around them — and for the screen where this system's data sits beside everything else the team runs. If you work on YAMCS, we would rather hear where this page is wrong than have a customer find out.

Get started →Talk to us →