You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Release notes for FrameworX 10.1 Update 6 (version 10.1.6), the new minor version of the 10.1 platform.

Home → Support Resources → Release Notes → Update 6

Update 6 installs side by side with 10.1.5, in its own installation folder. Moving your solutions to 10.1.6 is strongly recommended: this version brings important advances in connectivity, security, redundancy, displays and the AI tools that make the move worthwhile. Your 10.1.5 installation stays in place and available as a fallback while you migrate.

FrameworX 10.1 Update 6

Version: 10.1.6 RC
Release Date: October 15, 2026
Type: Features Update

Both versions run on the same computer, and you open each solution from Solution Center.

At a Glance

  • Charts. Heatmap, Pareto, waterfall, bullet, sparkline, histogram, SPC control, funnel and radar charts, on the Rich Client and the web client.
  • Displays and web client. Embedded displays accept parameters, Sankey charts render in the web client, and web client URLs carry the display and its parameter values.
  • Connectivity. Kafka Producer and Consumer connectors, a Siemens S7-1200 and S7-1500 Symbolic connector, and built-in CODESYS and ControlLogix simulators.
  • Alarms and redundancy. Alarm notifications reach a webhook, an MQTT broker, and the iPhone and iPad app. The standby server returns unreplicated history to the active server.
  • AI. AI Chat calls the custom MCP tools of the solution. The AI Designer drives the script debugger and connects display elements.
  • Security. SAML 2.0 sign-in, and stricter access rules for the MCP-over-HTTP servers and the Runtime API.
  • Designer and scripts. The display editor stays responsive on large displays. The script editors add Go to Definition and solution-wide namespace declarations.

What's Included

Main items by area. Complete list: Update 6 - Detailed Release Notes.

AI, MCP and automation

Displays and Symbols

HTML5 and web client

  • Web client URLs carry the display name and its parameter values. See Desktop, Web and Mobile Clients.
  • Web client controls carry stable automation identifiers derived from their authored names. See Desktop, Web and Mobile Clients.
  • Web client Trend Chart pen grids open a pen settings editor and color picker.
  • Web client releases memory when displays with charts, grids, gauges and maps close.

Mobile client

  • The iPhone and iPad app shows alarm notifications, including when the app is closed. See Mobile App.
  • Press-and-release buttons work with touch in the web client and the Android app.

Unified Namespace, ontology and knowledge graph

  • Runtime follows the Reference target set for each UserType instance. See Knowledge Graph How-to.
  • Per-instance start values can be set on members of nested UserTypes.
  • RDF export writes every tag instance and the asset tree in all four graph formats. See Export your UNS to RDF/OWL/GraphDB.
  • Asset tree imports keep every folder under the right parent, in any row order.

Devices and protocols

  • A Kafka Producer connector streams tag values to Apache Kafka clusters with no middleware. See Kafka Producer Connector.
  • A Kafka Consumer connector reads Apache Kafka topics into FrameworX tags. See Kafka Consumer Connector.
  • The CODESYS PLC Handler driver includes a built-in simulator that needs no controller or network. See Codesys PLC Handler Connector.
  • The Siemens S7-1200 and S7-1500 Symbolic Connector reads and writes PLC variables by symbol, including optimized data blocks.
  • The ControlLogix Simulator runs a ControlLogix channel with no PLC, launched from Devices > Channels.

Alarms, Historian and redundancy

  • Alarm notifications can be sent to a webhook or an MQTT broker. See Alarms Notifications Reference.
  • Redundancy recovers Alarm and Tag Historian records from the standby server into the active server. See Redundancy Reference.
  • The Alarms module starts faster on solutions with many alarm items.
  • Both servers of a redundant pair use the same port, and the Designer enforces it. See Redundancy Reference.

Designer and data

  • A Merge plugin import lists the objects that differ and lets you choose which to replace. See Solution Import Plugin Reference.
  • Solution Center and the Designer start in the Windows display language when a matching translation exists. See Multi-Language UI Localization.
  • The display editor stays responsive when dragging, nudging, zooming, and selecting in large displays.
  • Large displays, the symbol library, and the Component toolbox load without blocking the Designer.

Scripts

  • The script debugger attaches to solutions running on the Multiplatform (.NET 10) runtime. See Code Editor Reference.
  • Scripted AI calls support Anthropic Claude models in addition to OpenAI-compatible endpoints. See AI.Execute API Reference.
  • Global namespace declarations set once in Solution Settings apply to the scripts of the solution. See Solution Settings Reference.
  • Ctrl+click on a class, method, or namespace member in the script editors opens its definition.

Security and access

  • Operators sign in to runtime clients through SAML 2.0 identity providers. See Security Identity Providers Reference.
  • Administrators can reveal and copy a stored secret value from the Security Secrets editor. See Security Secrets Reference.
  • The Runtime API requires a signed-in session or a bearer token linked to a user. See Runtime REST API Reference.
  • The runtime server keeps stored passwords and secrets on the server.
  • The SolutionCenter API is available for administrators who enable it.

Runtime and platform

  • FxResourceMonitor records CPU and memory of every FrameworX runtime process on Windows. See FxResourceMonitor Reference.
  • Runtime diagnostics and System Monitor values work on .NET 10 runtimes on Windows, Linux and macOS. See Runtime Diagnostics Reference.
  • Opening a solution from an earlier version always saves a backup copy before the upgrade. See Upgrading Solutions Reference.
  • Designer, Solution Center and runtime clients reconnect after a lost server connection without a restart.
  • Reconnecting client stations receive the current tag values from the server.

Changes to Review Before Upgrading

These changes affect how an existing solution, script or integration behaves on 10.1.6. The complete list is in Update 6 - Detailed Release Notes.

New Behavior

Action

The MCP-over-HTTP servers of AI Designer, AI Console and AI Runtime accept connections only from the same computer until an API key is configured.

To connect from another computer, set an API key in the server settings and enter the same key in the client. See MCP and Claude Setup.

The Runtime API accepts a session token only from a Runtime API sign-in or a bearer token linked to a user, and enforces each tag's Read Security and Write Security.

Update custom Runtime API callers to sign in through the Runtime API or use a bearer token linked to a user, and review the security of the tags they read and write.

An AutoStartClient from an earlier release cannot check which redundant server is active on a server of this release.

Install the AutoStartClient from this release on every station that connects to a 10.1.6 server.

Clients on other computers receive blank values for stored passwords and secrets in the configuration tables.

Update any client-side script that read stored passwords or secrets from the configuration tables.

A user who signs in through an external identity provider and matches a user in the solution receives that user's permission groups, and the provider's group claims are ignored.

Review the permission groups of solution users who sign in through an external identity provider.

On clients connected with Windows authentication, electronic signatures and alarm acknowledgment comments check the Windows password of the user named, in the server's own domain only.

Have operators sign with their Windows password, and use accounts from the server's domain.

File and process services between FrameworX computers accept only allowed folders and FrameworX programs.

Add each folder used for remote solution loading or file transfer to the allowed folders in the machine settings, and restart the service.

On Windows, the runtime reads start settings and .NET 10 database provider registrations only from the installation folder, and a start settings file is selected by solution and profile.

Move start settings and custom provider registrations from the shared settings folder to the installation folder, and place them again after installing a new release.

Dataset filters and queries refuse to run when a value from a tag or from the signed-in user would end a quoted text in the SQL command.

Test Dataset queries and table filters after upgrading, and where a value closes the quotes on purpose, move the quotes from the query into the value.

A Linux or Docker runtime refuses to start a solution that targets Windows.

Open the solution in the Designer, change the target platform to Multiplatform in Solution Settings and run Build All.

Client stations receive tag values from the server after a reconnection or an online configuration change.

Update every Smart Client and Rich Client, local and remote, to this release.

Compatibility and Lifecycle

Security Note

This release contains security corrections and hardening. For per-item detail (affected versions, severity, required action) and the component manifest (CycloneDX) of your version, contact support@tatsoft.com.

  • No labels