📘

NOTE

For more Tetra Connector Release notes, see Tetra Connector Release Notes.

---

v1.0.1

Release date: 8 February 2024

What's New

TetraScience has released its next version of the Tetra KEPServerEX Connector, version 1.0.1. This release resolves an issue discovered in v1.0.0 where the Connector is sometimes unable to use the customer-provided TDP certificate when the Connector is behind a proxy.

📘

NOTE

Tetra KEPServerEX Connector v1.0.1 includes all of the new functionalities and enhancements that were introduced in v1.0.0. For more information, see the Tetra KEPServerEX Connector v1.0.0 Release Notes.

New Functionality

There is no new functionality in this release.

Bug Fixes

The following bugs are now fixed:

• An issue that caused the Tetra KEPServerEX Connector to sometimes not be able to use customer-provided TDP certificates when the Connector is behind a proxy is now resolved.

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

For a list of known issues, see the Known and Possible Issues section of the Tetra KEPServerEX Connector v1.0.0 Release Notes.

Security

Various security updates were applied.

Upgrade Considerations

Tetra KEPServerEX Connector v1.0.1 must be used with TDP v 3.6 or higher.

v1.0.0

Release date: 3 November 2023

What's New

TetraScience has released its initial version of the Tetra KEPServerEX Connector, version 1.0.0. This Connector leverages KEPServerEX’s ability to connect to various industrial computers, such as programmable logic controllers (PLCs), and instruments.

New Functionality

New Functionality includes features not previously available in the Tetra Data Platform (TDP). These features may or may not affect “intended use” for GxP validation purposes.

• Supports batching and uploading data from KEPServerEX to the TDP by using either a fixed upload interval timer or manual requests made by users.
• Supports parsing raw data (json format) into an Intermediate Data Schema (IDS)(common/tagged-time-series:v3.0.0) by using the following artifacts:
  • Tetra Data Schema: common/tagged-time-series:v3.0.0
  • Protocol: common/kepserverex-tagged-time-series-raw-to-ids:v1.0.0
  • Task Script: common/tagged-time-series-raw-to-ids:v3.0.0

📘

NOTE

Both successful and unsuccessful quality reads are available through an SQL interface.

Known and Possible Issues

The following are known and possible issues for the Tetra KEPServerEX v1.0.0 release.

Potential Data Loss

• When the Connector is inactive or not running, messages sent by the MQTT broker during the inoperable period will not be available for uploading. When this happens, it's recommended that customers pause the publishing of messages from the KEPServer IoT Agent and then resume publishing when a functioning KEPServerEX Connector is available.
• To control the rate of publishing to the TDP, the Tetra KEPServerEX Connector caches messages from the MQTT server in a local datastore. If the Connector is deployed by using the Cloud option, it doesn't support persistent data. This can lead to data loss if the data is cached in the local datastore and the container is destroyed. A fix for this issue is in development and testing and is scheduled for a future release.

Security

Various security updates were applied.

Upgrade Considerations

This version of the Tetra KEPServerEX Connector must be used with TDP v 3.6 or higher.