Skip to content
English
More support
Ask Flow Support
  • There are no suggestions because the search field is empty.

Timebase 1.1 Release Notes

Overview of the release and full release notes for all versions of Timebase 1.

Version 1.1.1

May 21, 2025

Windows Installer

Docker Hub

Historian

  • MCP Server (BETA): Added a Model Context Protocol "MCP" Server to allow AI Agents and Assistants to interact with and use the Timebase Historian as context. See Historian MCP.
  • Fixed an issue where deleted tags would "reappear" after a restart of the Historian.

Collector - MQTT Plugin

  • Fixed and issue where the TagnameIncludesTopic setting was not being used correctly for some payload types.

Explorer

  • Added ability to click on a Timeline Frame Number (circled number) to the center the relevant Frame in the Context Band.
  • Added a convenience feature where toggling between Frame start/end times being "Fixed" or "Relative" would automatically convert the current values.
  • Fixed an issue where some browser language settings caused gridlines and labels to render incorrectly.
  • Fixed formatting inconsistencies on timelines and date/time pickers.
  • Fixed an issue where the header, context band, and time frames lost their "stickiness" at the top of the page.

 

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.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.