Update 6 - Detailed Release Notes

Complete list of features, improvements and corrections in FrameworX 10.1 Update 6 (version 10.1.6), by product area.

Home → Support Resources → Release Notes → Update 6 → Update 6 - Detailed Release Notes

FrameworX 10.1 Update 6, October 15, 2026

Version: 10.1.6. Summary: Update 6.

AI, MCP and automation

• AI Chat calls the solution's read-only custom MCP tools. Works in Windows and Multiplatform solutions, and the audit trail records each call with the operator's user name. See ChatSession Control Reference.
• AI Chat adds Clear and Compress conversation actions and follows the display theme. Available on the Rich Client and the web client (HTML5). See ChatClear Action Reference.
• AI Chat traffic of a solution can go out through one designated runtime server. The model endpoint and its credentials stay on one server, and AI calls from server-side scripts still go directly to the endpoint. See Local AI Configuration Reference.
• AI Designer drives the script debugger: breakpoints, stepping, call stack and local variables. The runtime of the solution must be running. See AI Designer Connector.
• AI tools create connectors between display elements by naming the two elements. Applies to Canvas displays, and moving a connected element with the arrow keys now carries its connector end along. See AI Designer Connector.
• AI tools set an Alarm Viewer to live alarms, alarm history or audit trail. Each write is checked against the element's catalog, and the reply names any property the element does not offer.
• AI Designer measures screenshots: pixel and region color sampling and comparison against a reference image. Runtime screenshots can be returned as lossless PNG images for exact comparison.
• AI Designer reaches floated editor windows, pop-up lists and menus, and configuration-grid copy and paste. It also sends mouse-wheel, held-key and mouse-move gestures and reads whether open documents have unsaved changes. See AI Designer Connector.
• AI tools pack a solution, report a running build and check for product updates. Pack and build state are available in AI Designer.
• AI Runtime calls can name the expected runtime, so each call reaches the right solution. Every reply names the solution, execution profile, host and port the call ran against. See AI Runtime Connector.
• AI tools save a local copy of a downloaded documentation example, ready to open or run.
• AI Runtime tools read control state and click buttons on a running Rich Client. Covers Trend Chart, Tab Control, Combo Box and Alarm Viewer on the Rich Client, on the Development profile in test mode. See AI Runtime Connector.
• Automated tests set tag values, wait for runtime events and sign in as a test operator. Value writes and the test operator are limited to disposable test solutions on the Development profile. See AI Runtime Connector.
• The AI tools start from the documentation content installed with the product. Startup runs entirely from the local installation.
• Runtime start, stop and hot reload through AI Designer report their real outcome. A start can open a Rich Client that signs in with Windows Authentication, or no client. See AI Designer Connector.
• AI Runtime connects only to the runtime it is pointed at. The connection reply names the bound solution, and the connector backs off when no runtime is available. See AI Runtime Connector.
• AI Designer calls return within a set time, even while the Designer is busy. The reply names the call in progress and how long it has been running.
• AI Console solution builds report progress and can wait for completion inside the call. The post-build check verifies single-row settings tables and reports the solution's target platform.
• Solution exports through the AI tools reply after the files are written and list each file. A changed solution is exported again, and an export of a solution open in the Designer completes with a clear status.
• AI tools and solution imports update the built-in alarm groups and device access types. An alarm group written without list and logging settings receives the Designer defaults.
• Display writes through the AI tools warn about settings that have no effect at runtime. Warnings cover a mismatched shape size, an ineffective invert setting, a duplicate color dynamic and Data Grid colors that are not rendered.
• AI Designer reports a Tag Provider's connection status when browsing its tags. Reads and exports include each Tag Provider's Interface setting and the complete stored value of permission settings.
• AI Designer screen reads return full text, start at a chosen element and include open pop-ups. A new tool reads the Designer Output panel, and a click reports whether it reached a handler. See AI Designer Connector.
• The AI build information report lists product folders, components, protocol drivers and Designer instances. It reports the product build number and has a compact form that returns only the product identity.
• Local AI connectors keep a durable log of their start and shutdown decisions. Replies identify the server instance and workspace that answered, and the solution session log records the outcome of each call.
• AI tool replies are more compact on repeat and filtered calls. Bootstrap calls can return a summary of the Context Package, protocol schemas filter by protocol, and repeated diagnostic records are merged.
• An AI Designer write saves only the rows it creates or changes. Adding tags to a large solution keeps the Designer responsive.
• Displays written through AI Designer keep their target engine, code-behind, background and images. Layouts keep the size and page references sent, and localization dictionaries save all their entries.
• Symbols, Trend Chart ranges, ComboBox item lists and element visibility written through AI Designer are applied. Symbols resolve with the Solution or Library prefix and render at the placed position.
• AI Designer writes displays in the documented shapes and protects the stored drawing. A write in a legacy shape returns a message naming the expected shape, and the stored drawing stays intact.
• Device point addresses, expression time triggers and tag Visibility written through AI tools are stored correctly. Addresses and times are validated at write time, and a tag written without a Visibility value is created as Protected.
• AI Designer write, delete and rename apply one rule for which objects an AI session manages. AI access to the solution stays in place across writes, and delete accepts the names that write returns.
• AI tool replies report exactly what happened, row by row. Each skipped row is named with its reason, an unknown category returns a warning, and image entries accept every image format the product supports.
• Reading configuration through the AI tools leaves the Designer page and open documents as they are.
• AI Designer grid edits, dialogs, navigation and selection confirm each change they make. Read-only pages stay protected, and only dialogs on screen are confirmed.
• Screenshots through the AI tools show the real window content and report coordinates for clicking. Captures wait for a starting client, restore a minimized window and stay separate across concurrent sessions.
• Solutions built by AI Console compile their scripts and display code and report missing rows. Windows solutions start on the Windows runtime, new solutions use the template of their platform, and linked asset folders build cleanly.
• AI Runtime alarm-history queries return every stored record, including audit-trail records. Queries take a time range and filters through dedicated parameters. See AI Runtime Connector.
• Chat actions on displays write replies to the Return Value tag and run their Expressions. AI Chat completes multi-tool conversations and continues a conversation when conversation memory is on. See ChatRequest Action Reference.
• MCP HTTP bridges report a port conflict clearly at startup. The FrameworX File Access extension works in AI clients that check tool output schemas. See MCP and Claude Setup.
• MCP-over-HTTP servers accept only same-computer connections until an API key is configured. Applies to the AI Designer, AI Console and AI Runtime HTTP servers. See MCP and Claude Setup.
• AI Designer replies and screen reads hide passwords, tokens and connection credentials. Built-in rows stay protected in the AI grid editing actions.
• AI guidance files are read only from the product installation folder.
• AI-built displays verify their tag and object bindings at write time. Binding results arrive in the write reply, so AI-built screens are ready to run within the session.
• AI Designer collapses and expands the display editor side panels. The canvas uses the full width while an AI session draws, and the panels reopen on request.
• AI-built displays show compact # placeholders for expression captions in the Designer. Buttons, labels and menu items keep a clean design view, and runtime captions are unchanged.
• AI tools list the registered tag importers and run the single-file importers directly from a file path. Each run reports the tags, alarms, historian entries, device rows and displays it added, in disposable test solutions.

Displays and Symbols

• Eight new chart controls cover operations, OEE and quality displays. Heatmap, Pareto, waterfall, bullet graph, sparkline, histogram, SPC control chart and funnel run on the Rich Client and the web client and bind to tags or a table. See HeatMapChart Control Reference, ParetoChart Control Reference, WaterfallChart Control Reference, BulletChart Control Reference, SparklineChart Control Reference, HistogramChart Control Reference, ControlChart Control Reference and FunnelChart Control Reference.
• Radar chart compares several measurements, each on its own axis and scale. An optional second series outlines a target or limit, and the chart renders the same in the Rich Client and the web client. See RadarChart Control Reference.
• Sankey chart renders in the web client as well as the Rich Client. Existing displays keep their Sankey settings, and a node with no color draws in the chart's standard colors. See SankeyChart Control Reference.
• Embedded displays accept parameters, and each instance keeps its own values. Parameter values are literals or tag references, on the Rich Client and the web client. See ChildDisplay Control Reference.
• TextBlock has a text alignment setting: Left, Center, Right or Justify. It renders on the Rich Client and the web client, and Left stays the default. See TextBlock Control Reference.
• PieChartPlus can print each slice value on the slice. At runtime the chart also draws the rows of its linked data table, on the Rich Client and the web client. See PieChartPlus Control Reference.
• TrendChart limit bands and X-axis label rotation work in the web client. Scripts and bindings can read and set these properties at runtime through the client TrendChart object. See TrendChart Control Reference.
• Holding Shift while resizing an element in the display editor keeps its proportions. It applies to corner and side handles, including rotated and flipped elements. See Keyboard Shortcuts Reference.
• Color threshold rules accept named theme colors. Fill, line and text colors driven by thresholds follow the active theme on the Rich Client and the web client.
• Trend Chart and Drilling Chart stay responsive in the Rich Client with a large alarm history. Overlapping alarm markers merge into one marker with a count, and a pen that shares its name with a tag in a folder shows its own markers.
• Display parameters work with numeric tag values inside OR, AND and XOR conditions.
• Startup display opening code and Display Action expressions inside Symbols now run. A RunExpressions write also updates the tag Quality, and expressions that read object values with the toolkit data methods refresh at runtime.
• Displays with Symbols render charts and color dynamics correctly on first open. This covers a TrendChart beside a Symbol, Group color dynamics beside a library-linked Symbol, and elements bound to a tag Quality.
• Date and time pickers keep their popup open when the on-screen keyboard is enabled. Picks follow write permission, the Min/Max range and electronic signature, and each change is written and audited once.
• TabControl and Carousel update the tag bound to Selected Index when the tab changes. A tab list driven by a text tag rebuilds on each display open with exactly one set of tabs.
• ComboBox Reload refreshes the item list in place, and RadioButton selection resets its group. In the web client, the ComboBox selected text is vertically centered at any control height. See ComboBox Control Reference.
• LinearGauge draws its content and labels inside the control at narrow widths. In the web client, scale numbers on the left or top stay inside the gauge and clear of the tick marks.
• Connector ends follow their elements when resized, rotated, flipped or moved as a group. The Designer also stays open when a ChildDisplay links to the display that contains it.
• PushButtons release the pressed look after navigation, and scaled elements keep their size on Shine hover. The shaded area behind a dialog follows the page on screen, and copying a dynamic keeps every method expression.
• Asset Tree control filters show the full subtree below a match. This applies to Initial Branch, Branch Filter and Attribute Filter on the Rich Client and the web client.
• PieChartPlus takes each slice color from a color column in its data table. Colors accept the common notations, and a pie chart and a bar chart reading the same column show each category in the same color.
• The Draw editor shows the display type chosen at creation: Portable, WPF or HTML5.
• The runtime trace names the display and element of an expression that needs attention, including on displays opened with a parameter.

HTML5 and web client

• Web client URLs carry the display name and its parameter values. A filtered view can be bookmarked or shared as a link, and display security applies to every link. See Desktop, Web and Mobile Clients.
• Web client controls carry stable automation identifiers derived from their authored names. Automated tests and web automation tools can find a control by name, and the identifier stays the same across page reloads. See Desktop, Web and Mobile Clients.
• Web client Trend Chart pen grids open a pen settings editor and color picker. Clicking a pen in the chart legend shows or hides that pen.
• Web client releases memory when displays with charts, grids, gauges and maps close. Remaining grids and charts keep responding to resize and shortcuts, and the Knowledge Graph control renders in the web client.
• Web client Trend Charts honor legend placement and scripted duration on first open. Trend and Drilling Charts stay visible after Fullscreen and restore, and draw once their library files finish loading.
• Web client popups with a Resize border pass clicks to their controls and resize both ways. Mouse position handling is corrected across the web client, including dragging, double-click detection and release actions on touch screens.
• Alarm Viewer Export to CSV downloads a file in the web client. The file matches the grid, including rows, sort order, visible columns, filters and grouping.
• A Tag Reference returns the current source value on its first read in the web client.
• The web client loads Windows-only solutions reliably across server configurations. System Monitor links for the web client open the monitor in any letter case.

Mobile client

• The iPhone and iPad app shows alarm notifications, including when the app is closed. It notifies the highest-priority active alarm once per activation. See Mobile App.
• Press-and-release buttons work with touch in the web client and the Android app. The press action runs on touch, the release action runs on lift, and a repeat action repeats while the finger stays down.
• Mobile alarm checks handle alarm messages that contain quotes or line breaks.

Unified Namespace, ontology and knowledge graph

• Runtime follows the Reference target set for each UserType instance. The Asset Tree adds a Set Reference Target action, and editing a Reference member opens the reference target editor and applies to that member. See Knowledge Graph How-to.
• Per-instance start values can be set on members of nested UserTypes. A dot-separated path addresses the nested member, and each instance keeps its own values.
• Ontology import reports list every subject and containment parent that needs attention.
• RDF export writes every tag instance and the asset tree in all four graph formats. An ontology import and export round trip keeps names, values, dates and relationship targets. See Export your UNS to RDF/OWL/GraphDB.
• Asset tree imports keep every folder under the right parent, in any row order. A re-import keeps the existing hierarchy in place, and an ambiguous parent name is reported for review.
• Updates and edits reach the right asset folder when folders share a name. Top-level folders created by AI tools or imports resolve by full path everywhere, and each top-level folder name stays unique.
• Asset tree import validates folder names and names any folder that needs a new name. With replace on, the Designer Output panel names each existing folder the import did not update.
• UserType member Descriptions are defined once on the UserType and shared by every instance. Start Value, Minimum, Maximum, Disable, Display Text and Enumeration remain overridable per instance. See EngWrapper API Reference.
• UNS browsing and JSON template apply on UserTypes handle malformed input safely. Invalid member keys are skipped, valid members still apply, and malformed JSON leaves the prior state intact.

Devices and protocols

• A Kafka Producer connector streams tag values to Apache Kafka clusters with no middleware. Runs on Windows x64 servers with the .NET Framework or .NET 10 runtime, over plain or SASL_SSL connections. See Kafka Producer Connector.
• A Kafka Consumer connector reads Apache Kafka topics into FrameworX tags. Each point takes a whole message or one JSON field, on Windows x64 servers with the .NET Framework 4.8 or .NET 10 runtime. See Kafka Consumer Connector.
• The CODESYS PLC Handler driver includes a built-in simulator that needs no controller or network. The OPC UA server simulator also scales to about 8,000 variables and can drop and restore its connection on a schedule. See Codesys PLC Handler Connector.
• OPC UA nodes in Devices > Nodes have an Import Tags action. The importer opens connected with the node settings, and imported tags and points are created on that same node. See OPC UA Client Connector.
• Modbus master channels rebuild only the changed device node on an online configuration change. The other devices on the channel keep communicating, and every other driver still restarts the whole channel. See Modbus Master Connector.
• Device channels limit pending writes and send forced and normal writes of a point in order. Above 100,000 queued writes on a channel, a new write to a point replaces its waiting value, so runtime memory stays bounded. See Devices Channels Reference.
• The OPC UA client Default certificate offers a selectable key size and hash algorithm. Nodes can connect to servers whose only security policy is Basic256Sha256. See OPC UA Client Connector.
• New Siemens channels use Siemens S7 Plus, and SorbaAI is offered as a UNS Tag Provider. Existing legacy Siemens S7 channels keep working, and the Device channel catalog lists the connectors that run as channels. See Siemens S7 Devices Legacy Connector.
• The OPC UA Server publishes a tag and an asset folder that share the same name. The server also starts cleanly, and the Designer points out such a pair when it is created. See OPC UA Server Connector.
• Large OPC UA configurations of about 8,000 points run with stable CPU and memory. Every point receives its current value after a reconnection, and reconnection attempts to an unreachable server back off to about 30 seconds. See OPC UA Client Connector.
• The OPC UA Client marks tags Uncertain when a subscription goes silent, then recovers the subscription. Applies when the server sends no data and no keep-alive for about 15 seconds, and tags keep their last value and timestamp. See OPC UA Client Connector.
• Tag Providers routed through a gateway server connect, browse and write values. The gateway machine runs FrameworX 10.1.6 with the .NET Framework gateway service. See UNS TagProvider Services Reference.
• The CODESYS PLC Handler Tag Provider imports and browses large tag trees without stalling. Every tag of a runtime polling batch reports its value. See Codesys PLC Handler Connector.
• Report Out Of Range By Exception works on MQTT Sparkplug B publisher connections. A value is published only while it is outside the tag scale range, on MQTT Sparkplug B publisher and AWS IoT Core connections.
• The Built-in MQTT Broker publishes folder tags and Decimal tags correctly in Sparkplug B. Folder tags update on the device declared in their birth certificate, and Decimal tags publish as Double metrics.
• Modbus master validates each Point when the connection is prepared, and Test applies the Point modifiers. A Point that needs a correction is reported by address while the other Points on the connection keep running. See Modbus Master Connector.
• Tags keep updating when a device reading in the same request is not-a-number or infinite. OPC UA Client read polling and NI LabVIEW Data Sockets apply tag scaling once.
• ControlLogix and Siemens S7 Plus tag imports create counter UserTypes and STRING tags correctly. Applies to counters inside a user-defined structure imported from the controller, and ControlLogix file import accepts a path that contains a semicolon.
• The Mitsubishi MELSEC FX Ethernet Connector reads and writes every supported device with the correct address. Device channels on this connector and on the LabView connector start, and FX3U-ENET and FX3U-ENET-ADP modules are supported. See Mitsubishi MELSEC FX Ethernet Connector.
• Device nodes report backup, failover and redundancy status correctly. A node with no backup partner reports redundancy as disabled, and Server-to-Server Connector points show the source quality when a Backup Station is configured.
• The Value Simulator RAMP function starts at its minimum and stays within its maximum. A point address with a decimal or non-numeric Min, Max or Step is flagged as invalid. See Value Simulator Connector.
• The SQL Database Normalized connector connects with the password stored on its station. A Secure Gateway also opens a Runtime Users database that has a logon password.
• The .NET Framework 4.8 remote device process connects to its server and reconnects automatically. Automatic reconnection applies to a process started by hand.
• The Kafka connector ships OpenSSL 3.5 LTS, maintained until April 2030. See Kafka Producer Connector.
• The Siemens S7-1200 and S7-1500 Symbolic Connector reads and writes PLC variables by their TIA Portal symbol. Tags in optimized data blocks work with no DB number or byte offset, PUT/GET stays off on the PLC, and the connection uses secure PG/HMI communication over TLS 1.3. Requires S7-1500 firmware V2.9 or later or S7-1200 firmware V4.5 or later, with a TIA Portal V17 or later project.
• The ControlLogix Simulator runs a ControlLogix channel with no PLC, for demos, training and testing. Start it from Devices > Channels. The tag list, value generators and write rules come from an editable configuration file, and it listens on the local machine by default.
• ControlLogix connector reliability options are available through Tatsoft support. They report a refused controller connection, bring the ControlLogix Tag Provider to the .NET 10 runtime, show the right text on partially configured STRING arrays and report write status on Micro850 controllers.
• The MQTT Sparkplug B and MQTT station editors explain Report Out Of Range By Exception in their tooltips.

Alarms, Historian and redundancy

• Alarm notifications can be sent to a webhook or an MQTT broker. Events are buffered while the endpoint is unreachable and are re-sent automatically, including after a runtime restart. See Alarms Notifications Reference.
• Redundancy recovers Alarm and Tag Historian records from the standby server into the active server. Closes the history gap left after a role switch, for the history streams selected for replication in the Execution Profile. See Redundancy Reference.
• Redundant pairs on PostgreSQL or TimescaleDB keep history replication current on large compressed databases. Replication resumes without a runtime restart after a database outage, restart, read-only period or dropped connection. See Redundancy Reference.
• The Alarms module starts faster on solutions with many alarm items. With server redundancy, a tag StartValue, Enumeration and Labels written at runtime also reach the standby server.
• Both servers of a redundant pair use the same port, and the Designer enforces it. Solutions saved with different ports are reported in the Output window when the solution opens. See Redundancy Reference.
• The Designer warns when the same tag is configured in more than one Historian table. At runtime only the first configured table stores the tag values. See Historian Tables Reference.
• MachineHMI solutions run hot-standby redundancy. A primary and standby pair engages and fails over the same way it does on Enterprise. See Redundancy Reference.
• A redundant pair stays redundant after a solution update is pushed to the standby server. After a failover, Hot Reload also refreshes tag Descriptions to the values defined in engineering. See Redundancy Reference.
• Alarm notifications and alarm counts stay correct after online configuration changes. Alarm areas and groups created while the solution runs start normally.
• Alarm history loads every record of a large batch and keeps quoted filter column names. Applies to the Alarm Viewer, Trend Chart and Drilling Chart, including with the Alarm Historian on TimescaleDB.
• Historian readers return the stored sample quality on PostgreSQL historian tables. Applies to REST history, CSV export, trend and drilling charts, the Data Access API and script toolkit history reads.
• Aggregated history requests return buckets computed from the stored samples. Applies to the script toolkit, REST API and AI Runtime tools, and each bucket reports when the historian sample limit truncated it.
• Historian table CSV export includes every tag and the whole selected period, under the correct headers. Normalized table exports drop the extra number that preceded the tag values in each row.
• The Tag Historian stores data on MySQL databases and on MongoDB Tag Providers. The Alarm Historian also archives on MySQL, and MongoDB numeric samples are stored as text in this release.
• The Audit Trail records MCP custom tool calls when the MCP Custom Tools option is enabled. The option is off after an upgrade. See Alarms Global Settings Reference.
• The Alarm Viewer acknowledge key acknowledges the first unacknowledged alarm when no row is selected. Available on the desktop client.
• Undo after deleting an Alarm Group leaves the alarm items in place.
• Solution updates pushed to the standby server download from the partner's Web Services port (default 10108).

Designer and data

• A Merge plugin import lists the objects that differ and lets you choose which to replace. Covers tags, displays, images, script classes, script tasks, and reports, on plugin import and plugin update. See Solution Import Plugin Reference.
• Solution Center and the Designer start in the Windows display language when a matching translation exists. A language selected in Solution Center or the Designer is kept, including after upgrades. See Multi-Language UI Localization.
• The display editor stays responsive when dragging, nudging, zooming, and selecting in large displays. Covers connected polylines, Dashboard displays, and selections of thousands of elements.
• Large displays, the symbol library, and the Component toolbox load without blocking the Designer. Display save is faster after drawing-only changes, because code-behind is recompiled only when something it depends on changes.
• Tag autocomplete navigates the tag hierarchy one folder level at a time. Applies to the tag field of display properties and to the C# and VB.NET script editors, where Tab or Enter inserts the selected tag.
• The display editor tag panel filter finds matching tags in folders that were never opened. While the solution runs, tag rows in an opened folder show their live values.
• Configuration tabs open faster, and large grids stay responsive while searching and editing. Applies to the Tags, UNS Assets, Services Monitor, Alarm Areas, and Data Servers tabs and to the tag and device point grids.
• The Designer reports a lost connection to a remote solution server right away. The current action stops at once, and the message closes by itself when the connection returns.
• The Asset Tree keeps open folders and the selection when it reloads. Applies to changes made outside the tree, such as a tag edited in the grid or an import.
• Edit Combined Rows sets a common station address for Device Nodes on different Channels. The Channels must use the same protocol.
• Esc, mouse-wheel scrolling, and the navigation sidebar respond consistently in the Designer. Esc cancels the active dialog and closes dropdown lists, pickers, and autocomplete suggestions, and keeps unsaved work.
• Imports keep skipped displays and symbols unchanged, and a multi-file import asks to skip or replace. The answer applies to every file in the import, and Cancel leaves the solution unchanged.
• Imported objects keep their links, build cleanly, and stay unique across repeated imports. Covers solution JSON imports, Import Solution, Merge plugin imports, and AI Designer bulk writes.
• JSON export follows the Auto-save preference, and Version Control Export writes every selected table. Create JSON files also writes displays upgraded from version 9.2 and names any object that needs attention.
• Designer and Solution Center menus and messages appear in the selected language. Covers the Edit menus, the code editor menus, and messages that stayed in English, and Solution Center applies the selected language on every open. See Multi-Language UI Localization.
• Dialogs and file pickers open in front of Designer and Solution Center popups. Popups move, minimize, and restore with their main window and stay in step with the rest of the desktop.
• The Data Servers page shows the current status, profile, endpoint, and port of each server. The Built-in MQTT Broker settings dialog saves the SSL protocol option correctly, so the broker opens its port.
• Designer grids, monitor views, and status texts stay in sync with configuration and runtime changes. Covers the Channels grid, the Datasets DBs list, runtime monitor views, and the UNS Services Monitor.
• Help links, F1, and built-in reference texts point to current pages and existing members. On Devices > Channels and Devices > Protocols, help opens the page of the selected connector.
• New solutions start with an empty Solution History instead of the template's build history. Displays in the AlarmsTrendLayout, HeaderLayout, and WideScreenLayout templates use C# with asynchronous code-behind methods.
• The Designer stays stable when switching chart types, packing a solution, and browsing tag providers. Opening the Code Editor from an empty new row opens an existing script and creates nothing.
• Editors opened in a separate window release their resources when closed. A closed display editor is also released from memory.
• Find References reports the object of the current page after you switch grid pages.
• OleDb database providers work on the .NET 10 runtime on Windows. OleDb remains a Windows-only technology.
• The Import Tags page offers a Migration Assessment for applications coming from other HMI and SCADA platforms. Tatsoft migrates the complete application, starting with a free evaluation, and the page layout is clearer.
• Tag imports from another SCADA platform's export bring each tag with its data type, description, alarms and history settings.
• Solution exports are leaner and carry only the content each solution defines.
• The Quick Help of UserTypes and Enumerations uses the product names, in all twelve Designer languages.

Scripts

• The script debugger attaches to solutions running on the Multiplatform (.NET 10) runtime. Available on Windows x64, with the Designer and the runtime on the same computer. 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. Ctrl+S saves, and Esc closes open dialogs.
• Scripts resolve a UNS folder ID to its asset path, and back, with one Toolkit call.
• The script debugger steps through Tasks and Classes, updates watches, and detaches cleanly. Local debugging covers Windows (.NET Framework) solutions, with breakpoints, call stack, and local values.
• Client scripts keep reaching server Script Classes under load, after failed calls, and after idle periods. The failed-call correction applies to the Rich Client, and configuration tables are read from a client cache.
• A Toolkit preload call with a property list loads only those properties of non-tag objects. This reduces memory use in solutions with many alarm items.
• IntelliSense lists only members that compile for the client the code targets. VB.NET code lists Tag and Script members, and internal-only Toolkit methods are hidden.
• Script compile errors name a missing tag path once and appear in separate editor windows. The single missing-tag error applies to C# scripts.
• TClipboard gives CodeBehind and client scripts one clipboard API for the desktop and web clients. SetTextAsync, GetTextAsync and ContainsTextAsync compile and run on both clients.
• The script debugger opens a DataRow in the data viewer, with its columns, values and table name. The viewer stays within the screen.

Security and access

• Operators sign in to runtime clients through SAML 2.0 identity providers. Applies to the Rich Client and the web client (HTML5), and excludes encrypted assertions, single logout and sign-in started from the provider's portal. See Security Identity Providers Reference.
• Administrators can reveal and copy a stored secret value from the Security Secrets editor. Each reveal is recorded in the solution history. See Security Secrets Reference.
• External sign-in applies the permission groups of the matching solution user. Group claims from the identity provider apply to users outside the solution's user list, on the Rich Client and the web client (HTML5). See Security Identity Providers Reference.
• Identity-provider groups with spaces in their names map to permission groups named with underscores. The Designer validates permission group names as they are typed. See Security Permissions Reference.
• Active Directory (LDAP) sign-in grants permissions from directory groups, as in version 9.2. Directory users outside the solution's user list sign in, and group mapping requires the runtime to run as a service on a domain computer or under a domain account. See Security Identity Providers Reference.
• Rich Client and Smart Client connect with Windows Authentication from the generated command line and URL. The Runtime Startup page offers the Windows Authentication options only when the execution profile uses it, and TLS on the Windows Authentication port is optional. See Runtime Startup Reference.
• Sign-in uses the Guest user's security policy when a user's own policy cannot be found. A clear PolicyNotFound message covers the case where the Guest policy is also missing, and the Designer keeps policy settings when an editor closes without changes. See Security Policies Reference.
• Runtime users can be created and maintained when the runtime users database is PostgreSQL. See Security Runtime Users Reference.
• The WITSML service accepts user name and password sign-ins with a valid password.
• Dataset queries with per-user database session settings pass the signed-in user name to PostgreSQL safely.
• The Runtime API requires a signed-in session or a bearer token linked to a user. Session tokens enforce each tag's Read and Write Security, and a disabled, deleted or regenerated bearer token stops working on a running runtime with online configuration on. See Runtime REST API Reference.
• The runtime server keeps stored passwords and secrets on the server. Clients on other computers receive these values masked, and remote device channels still receive the secrets their connection settings use.
• Electronic signatures and alarm acknowledgment comments always verify the password. Every security check completes before access is granted, including sign-in to the built-in OPC UA server, and Windows-authenticated clients sign with the Windows password.
• Designer grids keep stored passwords and secrets protected from display, search and paste. Reading a stored secret goes through the audited administrator reveal action, and pasting over existing rows leaves read-only columns unchanged. See Security Secrets Reference.
• Sessions relayed through a Secure Gateway with Windows authentication use the user's own identity and groups. An optional server setting lists the gateway accounts the runtime accepts. See SecureGateway Services Reference.
• OpenID Connect sign-in validates redirect destinations, provider settings and asserted names more strictly. Asserted user names and group values are validated against strict rules for control characters, spacing, reserved names and numeric forms. See Security Identity Providers Reference.
• FrameworX services read their start configuration only from the protected installation folder. Applies to the Solution Center auto-start list and, on Windows, to runtime start settings, restart requests and .NET 10 database provider registrations.
• Remote file, process and service requests are limited to allowed folders, programs and sizes. The runtime server and the Solution Center service apply a configurable request size limit.
• Logs, traces and audit records mask passwords and database credentials. Covers dataset and historian connection messages, module restart records, the Windows event log for auto-start services and the WITSML service log.
• On operator clients, the audit trail records every electronic-signature outcome: accepted, refused or canceled. Audit rows for AI Runtime connector tool calls mask argument values and record refused or failed calls as such.
• Dataset filters and queries pass tag and user values to the database safely. Applies to values taken from tags or from the signed-in user.
• The SolutionCenter API is available for administrators who enable it. It is turned on in SolutionCenterApi-Settings.json in the installation folder, serves network callers over TLS or runs in local-only mode, and keeps its setting across product updates.
• LDAP group lookups always resolve the directory account that signed in. A name such as user@domain resolves by user principal name, and every user name is escaped in the directory search.
• Runtime communication reads request data only into the product's own data types. Solutions and saved data from earlier versions, including 9.x tag snapshots and retentive values, open as before.
• Desktop clients opened with Windows Authentication follow the user's permissions for the Windows taskbar. Users allowed to switch applications keep the taskbar, and restricted users get the locked desktop.

Runtime and platform

• The runtime publishes server performance counters on a secured REST API endpoint. The Designer reports its own live counters to the AI tools, and this release is verified on Windows hosts. See Runtime REST API Reference.
• FxResourceMonitor records CPU and memory of every FrameworX runtime process on Windows. The diagnostic tool runs independently of the runtime, logs process starts and exits, and summarizes growth, high CPU and crashes in a report. See FxResourceMonitor Reference.
• The runtime REST API publishes an OpenAPI document and supports authenticated cross-origin browser calls. Login responses state when the session expires, and tag history returns stored values for tags in normalized historian tables. See Runtime REST API Reference.
• Runtime diagnostics and System Monitor values work on .NET 10 runtimes on Windows, Linux and macOS. The diagnostics file adds FrameworX process trends and TCP connections and is generated in about one second. See Runtime Diagnostics Reference.
• A runtime licensed from a remote license server tolerates outages of about 300 minutes. Runtimes with a local license behave as before.
• Opening a solution from an earlier version always saves a backup copy before the upgrade. Solution Center shows an Upgrade action for a solution whose upgrade prompt was declined. See Upgrading Solutions Reference.
• Operators see the license expiration warning only in the final week before expiration. Earlier notices and maintenance-plan expirations go to the server event log, and the warning shows the product name as its title.
• Clients connected through the Secure Gateway finish loading the solution. The service opens each listener on its own port, and the gateway can run as a foreground process for testing. See SecureGateway Services Reference.
• Startup tools report unrecognized launch parameters and why a .NET 10 runtime component failed to launch. The launch failure reason is written to the Startup log when Save log is enabled for the profile. See Runtime Startup Reference.
• The Tatsoft.FrameworX PowerShell module is installed with the product. It imports on Windows PowerShell 5.1 and PowerShell 7. See Tatsoft.FrameworX PowerShell Module Reference.
• Designer, Solution Center and runtime clients reconnect after a lost server connection without a restart. The .NET Framework edition of the TWebServices gateway releases Tag Provider connection memory when a connection closes or times out.
• A forced write updates a tag's Previous Value and Timestamp, including when the value is unchanged. Digital tags raise an event on a Device read or normal write only when the value or quality changes, and store 0 or 1.
• On Linux and Docker, a Windows-target solution gets a clear message with the step that moves it to Multiplatform. On Linux and macOS, a runtime started from a terminal stops in order on Ctrl+C or when the terminal closes. See Linux Deployment Reference.
• Solution Center Start runs a solution as a Windows Service when it is configured as one. Administrators can remove the runtime Windows service from the command line, with clear status reporting.
• Module start problems are reported clearly as Cannot Start Module, and the runtime keeps running. Value updates on the client continue throughout.
• Historian, Dataset and Device modules keep normal operation through every online configuration change. The Module Information window updates as soon as the in-process Devices module stops or restarts.
• The continuous runtime trace file is a valid tab-delimited file. Trace output stays on when an unrecognized client changes trace settings, and Device Points mapped in two channels raise no repeated warnings.
• Saving a database connection, device node or tag provider at runtime keeps its base connection settings. Applies when the solution runs on an execution profile that overrides the connection.
• The built-in MQTT broker keeps running on .NET 10 solutions.
• A computer with teamed network adapters keeps its activated license across restarts.
• Reconnecting client stations receive the current tag values from the server. Tags keep their values, quality and timestamps through client reconnections and online configuration changes, so alarms and device writes follow real process changes. Applies when every Smart Client and Rich Client runs this release.
• FxResourceMonitor also runs on Linux and macOS with the .NET 10 runtime. It records machine and process CPU and memory, follows process starts and exits, and registers to start at boot as a systemd service or a launchd daemon.
• Setup on Windows 11 24H2 and later closes running .NET 10 FrameworX processes before it updates files. Upgrades restart the FxResourceMonitor startup task, and uninstalling removes it.
• T.WpfControlParent3d.dll and TDatabaseBuilder.exe are digitally signed, like the rest of the product, and every listed protocol ships with all of its driver files.
• The Secure Gateway configuration file enables each sample setting with a single line.

Good To Know Changes

These changes need no action. They are listed so you know what to expect on 10.1.6.

Compatibility and Lifecycle

• Update 6 installs side by side with 10.1.5. Both versions run on the same computer, and you open each solution from Solution Center.
• Upgrade steps: Legacy Versions Upgrade, Managing Updates and Multiple Versions Reference and Install and Activate.
• Earlier updates: Release Notes. Support phases and end-of-support dates: Product Lifecycle and End of Support.

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.