Cytiva, Biacore T200 Control Software Configuration Guide

Purpose 

To provide details about the necessary steps to implement the Cytiva, Biacore T200 Control connector for use with the Benchling Connect platform.

Introduction

The Cytiva, Biacore T200 Control connector is a component used in the context of the Benchling Connect platform to parse data from Cytiva Biacore T200 SPR System to an Allotrope Simple Model (ASM) and make those data available within the Benchling UI in the context of a Run.

The Benchling Connect, Cytiva, Biacore T200 Control connector is a ‘file-based’ based connector, meaning that it processes .blr exports generated by the Cytiva, Biacore T200 Control software. The data within the file export is then accessed by Benchling Connect through the use of a ‘watched’ file directory on the local computer hosting a Benchling Gateway, which has been configured via a Connection from within Benchling.

In order to successfully implement the Cytiva, Biacore T200 Control connector for use with the Benchling platform, there are several steps that need to be followed across both the Cytiva, Biacore T200 Control software and Benchling user interfaces. 

This guide details the steps to be taken in both applications in order to configure the integration. 

Steps within Cytiva Biacore T200 Control Software

From within Cytiva Biacore T200 Control, a user must:

1. Configure a .blr export compatible with the Benchling Connect, Cytiva Biacore T200 Control connector.
2. Execute the export of that file from their Cytiva Biacore T200 Control session.
3. Ensure that the file is placed with the watched directory.

Generating .blr Biacore T200 Control file

Following execution of an experiment utilizing either method/wizard template/manual run (including addition of report points), users should:

- Open the File menu from the Menu and toolbar

- Select Save As...

- Save the .blr results file with their appropriate experiment name and select the file saved in the watched file directory configured via their Benchling Connection

Current Limitations:

- The Cytiva Biacore T200 Control connector has to-date only been tested with example data from the Kinetics/Affinity and Immobilization Wizards. Additional Methods/Wizard Templates may be compatible with the connector but must be verified by the user.

- The Cytiva Biacore T200 Control connector only is compatible with the .blr file extension for raw data capture from SPR experiments, support from the Biacore T200 Evaluation and/or Biacore Insight Software aren't available at present.

These limitations can be eliminated with your help! If you would like to see any additional functionality to this connector, or other connectors, please reach out to your Benchling representative and let them know you would like to see a specific feature(s) added to the connector! 

Steps within Benchling

From within Benchling, a user must:

1. Enable the Cytiva Biacore T200 Control connector on the tenant [internal admin console]
   
   
2. Configure a Cytiva Biacore T200 Control Connection
   
   
3. Create a Result schema to structure the data to be recorded
   
   
4. Configure a Run schema to accept data from Cytiva Biacore T200 Control and records Results
   
   

For steps 1 and 2, please reference the Benchling Connect Installation Guide for details related to creating and installing a Gateway and configuring a Connection.

Creation of Result schema for Cytiva Biacore T200 Control data

In order to record results returned via the integration a Result schema must be created. This can be done prior to configuration of the Run schema, or within the context of the Run schema Output File configuration. 

The Benchling Connect - Cytiva Biacore T200 Control connector uses the Allotrope Simple Model (ASM) to structure the information parsed from the Cytiva Biacore T200 Control file export. The data is handled in a two step process; step one from Cytiva Biacore T200 Control export to the .json based ASM, and step two from the ASM .json to a .csv file available for ingest to Benchling. 

These data are structured using the Allotrope Binding Affinity Analyzer ASM data model. Details about this ASM schema can be found here:

https://github.com/Benchling-Open-Source/allotropy/blob/main/src/allotropy/allotrope/schemas/adm/binding-affinity-analyzer/WD/2024/12/binding-affinity-analyzer.schema.json 

The connector then converts the ASM to one of:

sample file .csv - structured such that each row of the file represents a sample

measurement file .csv - structured such that each row of the file represents a measurements

datacube file .csv - structured such that each row of the file represents a datacube data point, specifically for sensorgram data

report point data file .csv - structured such that each row of the file represents report point data/metadata of a sensorgram

sample file .csv files can contain the following columns (if available within the data):

• Device ID
• Model #
• Brand Name
• Product Manufacturer
• Analyst
• Measurement Time
• Experiment Type
• Analytical Method ID
• Sample ID
• Sensor Chip Identifier
• Sensor Chip Type
• Product Manufacturer [Sensor Chip]
• Ifc Identifier
• Last Modified Time
• Last Use Time
• First Dock Date
• Measurement ID*
• Detection Type
• Method Name
• Ligand Identifier*
• Device Type
• Flow Cell Identifier*
• Flow Rate (µL/min)*
• Flow Path*
• Dilution Factor (%)*
• Contact Time (s)*
• Number Of Flow Cells
• Number Of Spots
• Buffer Volume (mL)

* To account for cases of multiple measurements per sample (sample & sample-separate-unit-column files only), these fields will include an index
(e.g. _1, _2, _3,...) corresponding to the number of measurement.

measurement file .csv files can contain the following columns (if available within the data):

• Device ID
• Model #
• Brand Name
• Product Manufacturer
• Analyst
• Measurement Time
• Experiment Type
• Analytical Method ID
• Sample ID
• Sensor Chip Identifier
• Sensor Chip Type
• Product Manufacturer [Sensor Chip]
• Ifc Identifier
• Last Modified Time
• Last Use Time
• First Dock Date
• Measurement ID
• Detection Type
• Method Name
• Ligand Identifier
• Device Type
• Flow Cell Identifier
• Flow Rate (µL/min)
• Flow Path
• Dilution Factor (%)
• Contact Time (s)
• Number Of Flow Cells
• Number Of Spots
• Buffer Volume (mL)

datacube file .csv files can contain the following columns (if available within the data):

• Measurement Time
• Experiment Type
• Analytical Method ID
• Device Type
• Flow Cell Identifier
• Flow Rate (µL/min)
• Flow Path
• Dilution Factor (%)
• Contact Time (s)
• Number Of Flow Cells
• Number Of Spots
• Buffer Volume (mL)
• Sample ID
• Measurement ID
• Detection Type
• Method Name
• Ligand Identifier
• Data cube label
• Elapsed Time (s)
• Resonance (RU)

report point file .csv files can contain the following columns (if available within the data):

• Measurement Time
• Experiment Type
• Analytical Method ID
• Device Type
• Flow Cell Identifier
• Flow Rate (µL/min)
• Flow Path
• Dilution Factor (%)
• Contact Time (s)
• Number Of Flow Cells
• Number Of Spots
• Buffer Volume (mL)
• Measurement ID
• Detection Type
• Method Name
• Ligand Identifier
• Sample ID
• Data Cube Label
• Absolute Resonance (RU)
• Report Point Identifier
• Identifier Role
• Relative Resonance (RU)
• Time Setting (s)
• Diode Row
• Window (s)
• Quality
• Baseline
• Slope
• Min Resonance (RU)
• Max Resonance (RU)
• LRSD
• SD (Standard Deviation)

Cytiva Biacore T200 Control Connector Requirements

* This is the version of Biacore T200 Control with which the connector has been developed and tested. The connector may work with other versions of Biacore T200 Control, but that must be verified by the user.

Revision History

03/19/25

Initial Version