Release Candidates & Version History
      Back to home
      1. Timebase Knowledge Base
      2. Start Here
      3. Release Candidates & Version History

      Release Notes, Version History, and Upgrade Instructions

      How to upgrade an existing version of Timebase and information about each new release as well as beta release candidates

      Release Notes
      How to Upgrade
      Previous Versions

       

      Version Release Notes

       

      Version 1.1

      April 17, 2025

      Windows Installer

      Docker Hub

      Security and User Management

      • User Management: Pulse serves as the Timebase Identity Provider (IdP), enabling administrators to add users to ensuring only authorized personnel can configure components.​ Version 1.1 provides for "built-in" user accounts, but future versions will allow for external IdPs, like Active Directory, to be plugged in to Pulse.

      • Client Management: Pulse facilitates secure machine-to-machine communication by registering applications or components (i.e. Clients) authorized Client Ids and Secrets, utilizing OAuth 2.0 and OpenIDConnect (OIDC) standards to maintain secure data exchange.

      • Historian's UI and API can be protected by configuring its HTTPS network communication and authorization settings. See Component Settings
      • Collector's UI can be protected by configuring its HTTPS network communication and authorization settings. See Component Settings. Each Historian configured in a Collector's logging sessions can be configured to securely transport data to a protected Historian.
      • Each source in Explorer can be configured to securely connect to a protected Historian for tag discovery and data retrieval.
      • External client applications or custom-built applications can make use of the OAuth 2.0 and OpenIDConnect standards to access Historians securely (e.g. Ignition, Grafana, etc.)

      Historian

      • API Data Retrieval: Added GET endpoint where multiple tags can be specified, allowing a single request to return data for many tags. See REST API
      • Write Performance: Improved thread safety. Optimized tag metadata updates.
      • Integration with Pulse IdP where required.
      • Bug fixes and general product hardening.

      Collector

      • OPC UA Plugin:
        • Optimized Namespace browsing.
        • Ability to extract tag metadata Fields directly from topic structures.
      • MQTT Plugin - Type 3 Payload:
        • Ability to extract tag UOM definitions directly from the MQTT payload.
        • Ability to extract tag metadata Fields directly from topic structures.
        • Ability to extract tag metadata Fields directly from MQTT payload.

      Explorer

      • Live Mode: Trend with live updates.
      • Optimized to make use of Historian's multiple tag data GET endpoint.
      • Integration with Pulse IdP where required.
      • Bug fixes and general product hardening.




      How to Upgrade

      Moving to a new version of Timebase is simple and straightforward. For Windows, stop all Timebase services and run the new Timebase installer. In Docker, update the containers to use the new image(s).

      Configuration files should not be affected by the upgrade.

      However, as a precaution, it is always advised you back up the appsettings.json files as well as the Config folders for each of the Timebase components, including the Service Starter, Historian, Collector, and Explorer.

      For Windows installations, back up the Config folders by navigating to the C:\ProgramData\Flow Software\Timebase\ directory and within each of the folders for Historian, Collector, Explorer, and Service Starter, copy the Config folder into a temporary directory.

      Do the same for the appsettings.json file for Historian, Collector, Explorer, and Service Starter from the C:\Program Files\Flow Software\Timebase\ directory.

      For Docker installations, back up the folder that your Config volume references.


      Previous Versions

      Version 1.0.2

      January 28, 2025 - Windows Docker

      Historian

      • Fixed an issue related to the datatype conversion of tag values. The issue caused a 500 (Internal Server Error) response from the Historian. After applying the fix, any tags previously set as Double will handle incoming String values such that, if the String value cannot be converted to a Double, it will be stored as a null value in the Historian.

       

      Version 1.0.1

      January 21, 2025 - Windows Docker

      Historian

      • IMPORTANT - Fixed an issue relating to the Purge Age of Datasets not being set correctly, potentially leading to unintended data loss under specific conditions after restarting the Historian.

      To avoid unintended data loss, make sure to shutdown v1.0.0, perform this upgrade, and ONLY THEN RESTART the Historian.

       

      Version 1.0.0

      December 18, 2024

      Initial versions

      • Historian
      • Collector
      • Explorer (Beta)
      • Windows Service Starter