COSMOS

Ball / OpenC3 ground software for commanding and monitoring hardware.

Pick COSMOS in the connect dialog and give it your host. Underneath it reads the QuestDB that COSMOS 7 already runs — no plugin to install in your COSMOS, and nothing written back.

Run against COSMOS 7.3.0.

What Plexus reads

Every telemetry packet table, one per packet, with the converted value where COSMOS defines a conversion
Enumeration labels, from the textual converted column beside the numeric code
COSMOS's own limit state per sample — the GREEN, YELLOW_HIGH and RED_LOW it wrote beside each value
Command history. One table per command, with the parameters that were sent and the count of how many times
Array members. COSMOS names them BRACKET[0]; the subscript is quoted, not declined

What it does not read

Anything through the COSMOS API. Plexus talks to the store, not to your instance — which is also why command history works at all, since the API declines to serve it
The command string and the operator who sent it. Both are in the store, in a JSON column beside every command record, and reachable with SQL — but they are text, not signals, so no chart picks them up on its own

Connecting it

1Publish QuestDB's Postgres-wire port — the COSMOS compose file ships it commented out
2Choose COSMOS in the connect dialog and paste the connection string
3Plexus works out which column holds the real number from the schema

Their documentation: docs.openc3.com

Worth knowing

Limit state is COSMOS's verdict on a single reading, so an oscillating value genuinely enters and leaves its limit. That is not the same as COSMOS's persisted alarm state, which lives in its API.
COSMOS defines a table per command whether or not it has ever been sent, so most command packets are empty most of the time. They are listed anyway — a command with no history is a truthful empty, not a missing one.
OpenC3 COSMOS is AGPL-3.0 with addendums, one of which restricts use of the OpenC3 name for publicity. We read a database you point us at; we do not modify or redistribute COSMOS.

If you build it

Plexus is not a replacement for COSMOS. 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 COSMOS, we would rather hear where this page is wrong than have a customer find out.

Get started →Talk to us →