FrameworX 10.1 Update 5d is the latest release in the 10.1 platform — delivered August 11, 2026, as a free upgrade for every FrameworX 10.x customer. It follows Update 5c (June 22, 2026) and concentrates on AI-driven authoring and automated testing, display and symbol fidelity, the Scripts and Code Editor experience, ontology round-tripping, redundancy reliability on large projects, and faster web delivery.
Release Notes → Update 5d
The Update themes:
See Update 5d - Detailed Release Notes for the complete item-by-item list.
This release makes AI-driven authoring safe to use on existing solutions and extends automated testing across the whole product.
Symbol size, rotation, and legend now survive the JSON display import round trip. Library symbols with a theme-color FillColor dynamic render correctly in the Designer editor, fill color is applied to the intended object when another object is clicked immediately after, and selecting a button whose Action method was renamed keeps its Action target intact. Trend Chart shows accurate live data on dual-value (XY) pens, stays populated across display navigation, and captures rapid value spikes and quality transitions in online mode.
A broad pass over the scripting experience: multi-line string literals and string interpolation with Tag/Info references compile correctly in both Scripts and Display CodeBehind; IntelliSense exposes every class in a Script Namespace, refreshes for newly created classes, and works with tuple destructuring in a foreach header; namespace creation keeps using directives clean; and third-party DLLs in Script References load correctly alongside a same-name bundled library.
Ontology import and export round-trip correctly: RDF/OWL imports create object relationships and the asset-tree hierarchy, the ISA-88 template’s mapping rules are applied, and an exported UNS graph preserves its asset hierarchy on re-import when entities carry a source IRI. In the asset tree, GUID tag initial values are retained, case-only tag renames work, and folders and tags list in order after importing an existing solution’s UNS.
Adds the Toyopuc (JTEKT) PC10G, SIC Marking laser, and PEER communication drivers, plus store-and-forward local buffering for the Azure IoT Hub / MQTT driver. Siemens tag import now covers PLC tag tables (Input/Output/Memory) as well as Data Blocks and writes STRING values within their exact bounds. OPC UA UDT array members are sent by the OPC Server, Modbus TCP master frames are well-formed, the DataHub Tag Provider brings online tags from devices running outside the TServer, and the MQTT Client Connector keeps CPU steady on invalid broker credentials.
Historian and Alarm redundancy replication keeps up on large projects, so the standby database synchronizes fully, and Historian and Alarm data is drained to the standby before a redundancy handover completes. The Historian module starts reliably when logging to large Normalized tables on TimescaleDB / PostgreSQL, alarm history keeps recording through configuration changes and brief database interruptions, diagnostic tools can connect to the standby server, and Alarm Viewer respects a custom alarm-history table name.
The HTML5 web client loads significantly faster through compressed delivery and browser caching, connects smoothly through reverse proxies and Cloudflare Tunnel, and client tag preload and first access are faster through the TK API. The runtime starts with all modules in place on the .NET 10 build and runs continuously on macOS with the standard launcher.
OIDC single sign-on signs HTML5 users in through a correctly configured identity provider, PostgreSQL dataset connections can enforce per-operator row-level security, and machine settings file access is scoped to its intended folder. Security identity providers and secrets authored through the AI tools store their type and stay encrypted.
The SolutionCenter API can no longer be enabled on a released build. The API has shipped disabled by default since 10.1.5 GA, pending security hardening work on the underlying service surface. Until this update, an operator could override that gate by setting both SolutionCenterApi.Enabled and SolutionCenterApi.AcceptRiskOnOldBuild to true in MachineSettings/TWebServices.json. That override is no longer available in a released build, and no configuration setting re-enables the API in the 10.1.5 line. Installations that had enabled the API this way will find it stops responding after this update. The API remains planned to become available in a future release once the hardening work completes.
Windows-Authentication logins relayed through a Secure Gateway now require the gateway’s Windows-Authentication mode. The runtime honors a Windows-Authentication claim as proof of identity only when the connection itself was Windows-authenticated. If you run TSecureGatewayService with WA=false, set WA=true so the gateway relays over the runtime’s Windows-Authentication port — otherwise Windows-authenticated users through that gateway are refused after this update. Password-authenticated users through the same gateway are unaffected. The runtime must be started with /wa on .NET Framework for the Windows-Authentication port to exist.
Update 5d ships on August 11, 2026 as a free upgrade for every FrameworX 10.x customer, with the platform’s standard within-major-version 100% compatibility commitment — every 10.1.x solution opens and runs without migration or rework. See Breaking Changes and Deprecations above for two configuration-level changes that may require an adjustment on affected installations.
The full lifecycle policy, version support phases, and end-of-support dates for older FrameworX and FactoryStudio versions are documented on the Product Lifecycle and End of Support page.