GroundControl

GroundControl is our edge application that helps you with the local setup on each machine. From providing you access to the UniteLabs registry and with that our connector library, installing and configuring connectors, to communication with the connectors and the platform. It has three main areas: the Discovery dashboard (auto-detected Connectors or 3rd party SiLA servers on your local network), the Devices list (your configured instruments), and Settings.

In it's current state, GroundControl is not fully integrated into the Unitelabs Platform yet. Future iterations will enable full remote control of GroundControl via the platform to enable deployment and management of all edge applications with IaC.

This guide walks through adding a device, installing a connector, and interacting with your instrument.

Add a Device

A device in GroundControl represents a physical instrument. Connectors are then attached to devices to provide the communication layer. Multiple connectors can be associated to a device. Good examples are a device connector and a file system connector for instruments that create large files, such as sequencers or microscopes, or a power connector to switch the device on and off remotely.

1. Click Add Device in the Devices page.
2. Fill in the device metadata:
   • Name: a human-readable label (e.g., Hamilton STAR)
   • Manufacturer, Model, Serial Number: optional but useful for auditing
   • Description: any notes about this instrument or its location
3. Click Next to proceed to connector selection.

Add a Connector

A connector is an executable that enable communication with your instrument. Connectors use SiLA 2 for communication with GroundControl and the UniteLabs Platform. You can add a connector in four ways:

Download from Registry

Browse the connector catalogue, select your instrument, pick a version, and click Download. GroundControl fetches the correct binary for your operating system and architecture automatically, and saves it to ~/.unitelabs/unitelabs-app/.

Upload Local File

If you are deploying in an air-gapped environment or do not have access to our registry, reach out to you UniteLabs contact or the responsible IT contact in your organization to get the respective connector executable for manual upload:

1. Choose Upload mode in the wizard.
2. Browse to your connector executable (or drag-and-drop it).
3. GroundControl reads the connector's type and version automatically from the binary metadata.

Discovered (mDNS)

If a connector is already running on your machine or a machine elsewhere in your network and broadcasting via mDNS, GroundControl will list it on the Discovery dashboard and in the wizard.

1. Choose Discovered mode.
2. Select the connector from the list of auto-detected SiLA servers.
3. No local installation is needed — GroundControl connects to the remote process directly.

Manual Remote

If the connector is running on a known host but not broadcasting via mDNS:

1. Choose Manual Remote mode.
2. Enter the hostname or IP address and port.
3. GroundControl queries that address and lists the available SiLA services to connect to.

Configure a Connector

After selecting a connector (Download or Upload), the wizard shows a configuration form generated from the connector's own schema. Four categories of configuration parameters are displayed:

• General Configuration: Device specific parameters, such as serial port or module configuration. May be empty.
• SiLAServerConfig: All SiLA 2 specific parameters required for local connectivity, including the connection back to GroundControl. Make sure to set a defined, unoccupied port. The default port 0 will result in random free port selection.
• CloudServerConfig: Defines the direct connection to the UniteLabs Platform. Relevant parameters are the hostname and port (use 443 as default).
• DiscoveryConfig: Only relevant if auto-discovery is required and not working with default settings.

Fill in the fields and click Save. GroundControl writes a config.json file alongside the connector executable.

Start and Stop Connectors

Open Devices → your device → Configuration tab.

Each connector shows a status badge:

Use the Start, Stop, and Restart buttons to control the connector process. The connector must be running for workflows to reach your instrument via the UniteLabs platform.

By clicking on the connector, the configuration is shown and can be edited. Make sure to save the changes and restart the connector for changes tot ake effect.

Interact with a Connector

Open Devices → your device → Operations tab to directly read values and trigger actions on your instrument — useful for testing and verification before running workflows. If a connector does not show up in the platform yet, check here if you can control the instrument. The configuration may need to be adjusted.

Properties, Sensors, and Controls

Every action the connector exposes is one of three types. GroundControl groups them into three sections when you expand a module:

• Properties — scalar values you can read (server name, whitelist entries, current status)
• Sensors — live streams you can subscribe to; clicking one opens a panel that updates in real time until you close it
• Controls — triggerable commands, some with parameters; controls show a parameter form and an Execute button

Long-running Controls stream progress updates while they run — useful for operations like a centrifuge spin or a PCR cycle. See Action for the full model.

Activity Tab

Devices → your device → Activity shows a timestamped log of every operation executed on the device: which action was called, the parameters sent, and the result returned. The default logging behavior also stores this activity log to file. The default logging settings are:

WIP

Use this to confirm that actions triggered from a workflow actually reached the instrument, or to debug unexpected behavior.

Verify the Platform Connection

Once your connector is running, open the UniteLabs Platform and navigate to Connectors. Your connector should appear as online within a few seconds.

From the platform you can also add the connector to workflows and interact with it programmatically via the SDK. See Use a Connector — Python or Add a Connector — Platform for the next steps.