UniteLabs
Reference

Device Guides

Step-by-step guides for each supported instrument: requirements, connector setup, a first working script, and known quirks.

Each device guide takes you from an unboxed instrument to your first successful command. For anything beyond that, such as operating the instrument itself, refer to the vendor manual and the connector's SiLA feature and endpoint descriptions.

Find your instrument in the catalog below. Devices are grouped by what they do.

Liquid handlers (Hamilton STAR and Vantage, Agilent Bravo, and Tecan Fluent and EVO) aren't listed here. Don't call their connectors directly. Use the SDK's liquid handling abstraction layer instead, and find the how-to guides under Operate.

Catalog

DeviceVendorGroupConnector
BioShake (3000, 3000-T, 5000, D30, Q1, Q2)QInstrumentsHeater-shakersQINSTRUMENTS BioShake
ColdPlate / ColdPlate slimQInstrumentsHeater-shakersQINSTRUMENTS BioShake
Thermoshake (AC, AC LC, Classic, RM) (coming soon)InhecoHeater-shakersInheco TEC Controller
SCILA (coming soon)InhecoIncubationInheco SCILA
ODTC (96, 96XL, 384, 384XL) (coming soon)InhecoThermal cyclersInheco ODTC
Gen5-driven readers (Synergy, Cytation…)Agilent BioTekReadersgen5
Synergy H1 (direct serial) (coming soon)Agilent BioTekReadersAgilent Synergy H1
Tecan Infinite 200TecanReadersTecan Infinite 200
TiltStationQInstrumentsTilt & turnQINSTRUMENTS BioShake
TurnStationQInstrumentsTilt & turnQINSTRUMENTS BioShake
PreciseFlex 400 (standard and XR, rail)BrooksRobotsBrooks PreciseFlex 400

Your device isn't listed? The UniteLabs Hub lists all 220+ supported devices. If you need help with a device that has no guide yet, reach out to your UniteLabs contact or email support@unitelabs.io.

What every guide contains

  1. What you need: the model, cable, drivers or vendor software, and the connector to install.
  2. Install and configure the connector: the GroundControl steps, plus the configuration fields that matter for this device.
  3. First successful test: a copy-paste script that takes you from connected to a first working command.
  4. Known quirks and errors: what each error means and how to fix it, collected from customer onboardings.
  5. Next steps: more snippets, the connector reference, and a pointer to the vendor documentation.

Last updated