UniteLabs
Connect a device

Via GroundControl

Add a device and install a connector through the GroundControl edge application.

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

This guide walks through adding a device and installing a connector. Once your connector is running, see Use a connector for interacting with your instrument and verifying the platform connection.

Make sure GroundControl is installed and you are signed in before continuing. See the Setup guide if you haven't done that yet.

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. Examples for multiple connectors within one device are a device connector and a file system connector for instruments that create large files, such as sequencers or microscopes, or an additional 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 enables 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

This option gives you the full catalogue of UniteLabs-maintained connectors. Browse the connector catalogue, select your instrument, pick a version, and click Download. GroundControl automatically fetches the correct executable for your operating system and architecture, and saves it to .unitelabs/unitelabs-app/ (~/.unitelabs/unitelabs-app/ on macOS and Linux, C:\Users\<user-name>\.unitelabs\unitelabs-app\ on Windows).

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 links 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. Five 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.
  • Logging: Can be left empty for recommended defaults (json based log files and console output). Learn how to configure it in the logging section of the "from source" guide.

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

Remote connectors (Discovered, Manual) skip this step — they are already configured and running. Capabilities such as live connector log display, start/stop, and registering connectors as a service are not available for any connectors added in this way; their lifecycle is not managed by GroundControl.

Start and Stop Connectors

Open Devicesyour deviceConfiguration tab.

Each connector shows a status badge:

StatusMeaning
onlineConnector process is active and connected
offlineConnector was stopped or is in error. — check the Activity tab for logs and start the connector

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 to take effect.

Use the connector

With your connector running, you can interact with your instrument in three ways:

  • GroundControl — read values, trigger actions, and monitor activity directly from the edge app.
  • UniteLabs Platform — view, inspect, and operate the connector from the Platform UI, and add it to workflows.
  • SDK & REST API — control the connector programmatically: discover services, explore modules and actions, and subscribe to live data.