Versions Compared

Old Version 1

changes.mady.by.user Marcos V Taccolini

Saved on

compared with

New Version 2

changes.mady.by.user Marcos V Taccolini

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: TDEV-2956: the Ignition and InTouch Application importers do not ship in 10.1.6 (Marc, 2026-10-13)

...

  • 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. A write that names a display element property that does not exist returns a warning naming the property.
  • 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 and are refused when they reach another. Every reply names the solution, execution profile, host and port the call ran against. See AI Runtime Connector.
  • AI Designer lists tag importers and runs the Ignition and InTouch importers from a file. The direct run is limited to disposable test solutions in this release.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 Development profile in test mode, and the web client (HTML5) is not included. 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 no longer contact the online documentation site at startup. Documentation lookups use the content installed with the product.
  • 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 when the Designer is busy or not responding. 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 or fails with a reason.
  • 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 no longer blocks the Designer.
  • 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 rejects legacy display write shapes that used to discard data. The rejected write names the error and leaves the stored drawing unchanged.
  • Device point addresses, expression time triggers and tag Visibility written through AI tools are stored correctly. An unreadable address or time is refused at write time, and a tag without a Visibility value is created as Protected.
  • AI Designer write, delete and rename apply one rule for which objects an AI session manages. A write cannot remove AI access to the solution, and delete accepts the names that write returns.
  • AI tool replies report what happened, name each skipped row and fail when no row lands. An unknown category returns a warning, and image entries accept every image format the product supports.
  • Reading configuration through the AI tools no longer changes the Designer page or saves open documents.
  • AI Designer grid edits, dialogs, navigation and selection report failure when nothing changed. Edits are refused on read-only pages, and dialogs that were not displayed are no longer 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 without false errors.
  • AI Runtime alarm-history queries return every stored record, including audit-trail records. Queries take a time range and filters, and SQL text is no longer accepted. 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.
  • An MCP HTTP bridge reports a port already in use and exits with an error code. 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 cannot be deleted or renamed through the AI grid editing actions.
  • AI guidance files are read only from the product installation folder.

...

  • 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.An Ignition tag importer recreates tags, alarm items and historian tags from an Ignition tag export. UDT type definitions and displays are not imported, and items with no FrameworX equivalent are listed in the import log. See Ignition Tag Importer.
  • 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.
  • The legacy Siemens S7 and SorbaAI connectors are no longer offered for new Device channels. New Siemens channels use Siemens S7 Plus, existing legacy channels keep working, and SorbaAI stays available as a UNS Tag Provider. 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 without node-id conflict errors, and the Designer warns when such a pair 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 must run FrameworX 10.1.6, and the .NET 10 gateway service and writes to PI points are not covered. 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 Points that cannot work are refused, and Test applies the Point modifiers. A refused Point 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.

...