The following are release notes for the prerelease versions of the Tetra LabX Connector. The Tetra LabX Connector is a standalone, containerized application that accesses the Mettler Toledo LabX system integration service, extracts tasks, and related data. The Connector then outputs that data in JSON format and uploads it to the Tetra Data Platform (TDP).

🚧

IMPORTANT

The Tetra LabX Connector is available through a beta release) currently and is activated for customers through coordination with TetraScience. For more information, or to activate the Connector in your environment, contact your customer success manager (CSM).

v0.1.2

Release date: 30 May 2025

What's New

TetraScience has released its next version of the Tetra LabX Connector, version 0.1.2. This alternative to the LabX Agent can be deployed through the platform, and allows connection to multiple LabX instances from a single connector.

Prerequisites

Tetra LabX Connector v0.1.2 requires the following:

• Linux OS
• Docker installed
• Outbound network access to Tetra Data Platform (TDP) v4.0.0 or higher
• Outbound network access to all LabX instances the Connector will contact

📘

Host Connector on a Tetra Hub

Many of the requirements above are automatically fulfilled by hosting the connector on an existing Tetra Hub. If you already have a Tetra Hub, you can install the Tetra LabX Connector there. However, it is not required to use a Hub with the Tetra LabX Connector.

New Functionality

New Functionality includes features not previously available in the TDP or Tetra LabX Connector.

• There is no new functionality in this patch release

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

• The client used by the Connector to contact LabX will now load certificates stored in the TDP organization that's hosting the Connector.

Bug Fixes

The following bugs are now fixed:

• The Connector now loads proxy settings set at the Hub or standalone-host level.

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

There are no new known and possible issues in this release.

Security

Various security updates were applied.

Upgrade Considerations

This version is compatible as a direct upgrade from LabX Connector v0.1.0 and v0.1.1.

v0.1.1

Release date: 3 April 2025

What's New

TetraScience has released its latest version of the Tetra LabX Connector, version 0.1.1. This release fixes an incorrect field name from v0.1.0.

Here are the details for what's in Tetra LabX Connector v0.1.1.

Prerequisites

Tetra LabX Connector v0.1.1 requires the following:

• If LabX is running in an on-premise network, the LabX Connector should run either on a Tetra Hub or as a standalone deployment on an on-premises Linux server.
• Tetra Data Platform (TDP) v3.6.0 or higher (for standalone operation, v4.2.0 or higher).

New Functionality

New Functionality includes features not previously available in the Tetra Data Platform (TDP) or Tetra LabX Connector.

• There is no new functionality in this release.

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

• There are no enhancements in this release.

Bug Fixes

The following bugs are now fixed:

• Scalar fields contain ValueMember instead of Value for consistency with the existing IDS parser.

Limitations

The following are known limitations of Tetra LabX Connector v0.1.1:

• The LabX API does not provide a way to determine the time zone of the LabX instance. Because of this, customers must choose the time zone for each connected LabX instance when configuring the Connector on the TDP. If the time zone of the instance changes, there may be a mismatch between the Connector and the LabX instance, which can result in data affixed with incorrect time zones.

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

There are no known and possible issues in this release.

Upgrade Considerations

This version is compatible as a direct upgrade from LabX Connector v0.1.0.

v0.1.0

Release date: 31 March 2025

What's New

TetraScience has released its first version of the Tetra LabX Connector, version 0.1.0. Previously, integration with Mettler Toledo LabX system integration service required using the Tetra LabX Agent. Like the Agent, the LabX Connector continually scans LabX for new tasks to upload, but offers more convenient deployment and several new features.

Here are the details for what's in Tetra LabX Connector v0.1.0.

Prerequisites

Tetra LabX Connector v0.1.0 requires the following:

• If LabX is running in an on-premise network, the LabX Connector should run either on a Tetra Hub or as a standalone deployment on an on-premises Linux server.
• Tetra Data Platform (TDP) v3.6.0 or higher (for standalone operation, v4.2.0 or higher).

New Functionality

New Functionality includes features not previously available in the Tetra Data Platform (TDP) or Tetra LabX Connector.

• Ingest tasks from multiple LabX instances.
• For each LabX instance the Connector communicates with, it continually polls for new tasks. When those tasks terminate, the Connector then uploads a JSON file containing task, method, and task results data to the TDP. This file is compatible with the existing RAW-to-IDS parser associated with the Tetra LabX Agent.
• Customers can create a task and associated sample series in LabX through the TDP by using the TDP command service.

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

• There are no enhancements in this release.

Bug Fixes

• There are no bug fixes in this release.

Limitations

The following are known limitations of the Tetra LabX Connector:

• The LabX API does not provide a way to determine the time zone of the LabX instance. Because of this, customers must choose the time zone for each connected LabX instance when configuring the Connector on the TDP. If the time zone of the instance changes, there may be a mismatch between the Connector and the LabX instance, which can result in data affixed with incorrect time zones.

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

There are no known and possible issues in this release.

Upgrade Considerations

To install and run the connector see the Tetra LabX Connector documentation.

Other Release Notes

To view other release notes for Tetra Connectors, see Tetra Connector Release Notes.