Skip to content

Releases

v4.0.0-beta.5

v4.0.0-beta.5 Pre-release
Pre-release

Choose a tag to compare

@asckye asckye released this 17 Nov 01:35

v4.0.0-beta.5 — fifth 4.0 pre-release

This is the fifth 4.0 pre-release of Automation Engineering Workbench (formerly TIA Portal Openness MCP).
It is a pre-release on GitHub: it is never marked as the latest release, and is not offered by the
3.3 updater or the Workbench update check of a 3.3 installation. Download it by hand from the
releases page to test it.

Unless a release is named below, the changes apply to all eight supported TIA Portal releases, V14 SP1, V15.1 and V16–V21.
The beta.5 changes have not run on a real TIA Portal. A separate real-machine regression session follows publication.

Behavior changes you must know

  • Unknown writes no longer lock the session. An unknown result belongs to its call. Later independent requests can run,
    subject to their normal project, preview and approval checks. GetSessionState keeps unconfirmed request IDs in
    data.sessionState.unsettled, and the Workbench shows their count. SaveProject and SaveProjectCopy warn with
    UNSETTLED_CALLS in preview and apply. Inspect the actual target before deciding on another write; never replay an
    unknown write automatically
    . Recovery does not replay it either.
  • A wait budget is not an operation deadline. A native call that outlasts the client's wait returns in-progress with
    OPERATION_IN_PROGRESS, while the worker continues. Read the final result with GetCallResult(requestId), available
    in lite and while busy. Other native calls return a temporary busy refusal until it finishes; disconnect and worker restart refuse
    while it is running. Identical writes remain guarded until their result is read. Results live in the current session's
    memory, with at most 16 completed full results plus running calls; retained summaries identify guarded unread writes
    whose full result has been evicted. Reading a result does not prove an unknown write safe to repeat.
  • TIA dialogs are visible with running calls. Running-call replies, busy state and the Workbench include reported
    dialogs. Unanswered confirmations promptly return in-progress; notifications and confirmations with only Ok are
    acknowledged after recording. Read-only window observations can identify an unhandled modal window. Compile, transfer,
    import/export, archive and library-update wait budgets are 300 seconds; the native operation can continue beyond them.
  • Abandoned attachments can give way. Within one host, ConnectPortal(processId, takeOver=false) can take an eligible
    idle attachment after ten minutes without requests. takeOver=true permits a more recently active idle holder. Running
    calls, approval waits, Workbench participation, operator ownership and worker-started TIA instances keep their guards. Handover is audited,
    carries unsettled IDs and leaves the previous session able to reconnect. Cross-host lease refusals identify the holder's
    host PID and release. An unclean previous owner produces PREVIOUS_OWNER_UNCLEAN on a new explicit connection.
  • Lost workers recover on the next native call. Recovery rebinds the recorded TIA process and exact project, reports
    WORKER_RESTARTED and retains export handles and unsettled calls. A new TIA PID is selected only when exactly one matching
    project is open without attached Openness clients. Running calls and live workers that started their own TIA retain their
    stop guards. Recovery changes the binding generation: make a fresh preview if the old plan is stale. Disconnect allows a
    new connection in the same MCP session and reports disconnected; the old TIA-restart fields are removed.
  • Reset fields and the reset error are removed. This is a hard cut under ADR 0001, with schemaVersion still 4.
    meta.requiresSessionReset and SESSION_RESET_REQUIRED are gone. Read meta.outcome for the call and
    GetSessionState.data.sessionState.unsettled for unconfirmed writes. Typed results rename data.requiresSessionReset to
    data.outcomeUnknown for device add, document import/export, batch export, batch document import/export, external-source
    tools and special export, keeping the values unchanged. Batch import keeps only data.nativeOutcomeUnknown.
  • Some unknown writes can be settled by evidence. Eligible calls use definite read-back on the existing worker lane or
    after rebind. The original result remains OUTCOME_UNKNOWN; data.settlement and sessionState.settled record the
    evidence. Settled calls stop save warnings, and not-applied releases the identical-write guard. Ambiguous reads, compile
    and overwrite imports remain unsettled. Optional settlement reads use a separate request identity and a five-second
    budget; each rebind attempts one eligible entry, rotating the rest on later rebinds. These checks never replay writes.
  • Errors point to declared fields. DES-4R2 uses RFC 6901 JSON pointers and details.expected, including batch row prefixes
    and allowed values where applicable. Undeclared caller keys stay private. Missing targets identify known declared
    parameters; otherwise their target remains null. ALREADY_EXISTS.details.target is now a declared JSON pointer, or null
    when no catalog can verify the parameter. Known unchanged refusals use
    typed errors such as NOT_FOUND, INVALID_ARGUMENT, ALREADY_EXISTS and UNSUPPORTED_CAPABILITY; writes whose effects
    cannot be established remain OUTCOME_UNKNOWN.
  • Native reasons remain useful after redaction. DES-4R3 keeps the redacted first-line native reason and error.innererror
    with the worker's short exception type, numeric HResult and request correlation ID. GetNativeInvocationLog accepts
    diagnosticId and bounded offset paging, excludes its own rows and returns empty pages after journal rotation. Redaction
    covers URL userinfo, private keys, structured credential echoes and scoped one-character secrets as whole tokens,
    including JSON-escaped and URL-encoded forms. Runtime-channel and per-item failures retain the safe reason.
  • Compile and import defaults are safer. CompileDevice now previews by default; execution needs dryRun:false, its
    preview's expectedPlanHash and the exact bound expectedProjectFile. ImportTechnologyObjectsFromDirectory defaults
    to overwrite:false on V16–V21. Replacing existing technology objects requires explicit overwrite:true.
  • Previews disclose what they checked. Generic write previews say targetVerified:false for the cached target and expose
    data.targetBound; an unbound apply refuses with PROJECT_NOT_BOUND. PreviewToolCall reports effective dry-run state
    and data.changesState, validates prefill fields as the real tool does, and names its tool's prerequisites. Generic reads
    report readOnlyInvocation:true. Web-variable and operating-mode previews retain their login/current-value reads and
    disclose contactedDevice:true. S7 Web API safety flags reflect the current HTTPS exchange; certificate validation is
    claimed only after a response with checks enabled and is null when disconnected. Executed results no longer carry
    targetVerified or preview scope text; scope returned by native execution is preserved.
  • Small response-shape changes matter to clients. PreviewToolBatch.data.previewToken aliases data.token, which remains
    until 5.0. On V19–V21, Unified HMI replies omit null DTO members while preserving false, zero and empty strings.
    On V19–V21, GetUnifiedGraphicSelection puts records and nextCursor under data.page and uses its public tool name in page scopes;
    CompareUnifiedGraphicSelections accepts both old and new labels. Migration pages and failure paths also name their
    public tools. HMI, hardware, library and optional-package scalar dates use ISO 8601 round-trip strings, preserving
    fractional seconds and timezone information.
  • Symbolic HMI types follow TIA. On V19–V21, EnsureUnifiedHmiTag.hmiDataType and
    BindUnifiedHmiTagDynamization.dataType default to empty. Symbolic tags use TIA's type; absolute tags still default to Bool.
    Dynamization type, PLC tag and address are optional expectations compared after binding, because those properties are
    read-only. Colour conversion and verification accept 0xAARRGGBB as well as the existing forms on V19–V21.

What is new compared with beta.4

  • More accurate write outcomes. A failed block move restored and verified in its original group reports failed unless
    target groups were created. Technology-object creation refused without changes reports failed. Verified imports retain
    a negative verdict, failed undo on an object subsequently deleted by rollback does not alone force unknown, and applied
    batch document imports report succeeded. Uncertain native document imports remain unknown.
  • Stable PLC import verification. Read-back and preview tokens ignore TIA-computed dates and memory sizes, so an unchanged
    block can keep its reviewed token after compilation. A completed mismatch reports failed and keeps backup and cleanup
    evidence. PatchPlcBlockDocument adds setMemberComment for DB, FB/FC interface and UDT members across all eight releases.
    UDT member comments are imported without verification.
  • PLC and offline refusals explain the next step. Failed live S7 watch connections keep the connection reason. Offline
    comparisons identify plc-online and suggest ConnectOnlinePlc; alarm export identifies missing PLC text lists. Real
    tag-table, block and type deletion needs dryRun=false, confirm=true and the exact bound expectedProjectFile.
    Offline library/template analyses distinguish completed findings from missing folders, and release validation identifies
    caller-supplied fixtures absent from the repository and package. ASCII source guidance explains re-saving without a BOM.
    Source replies expose encoding and importableByTool; other text keeps its UTF-8 BOM and...
Read more

v4.0.0-beta.4

v4.0.0-beta.4 Pre-release
Pre-release

Choose a tag to compare

@asckye asckye released this 05 Nov 14:34

v4.0.0-beta.4 — fourth 4.0 pre-release

This is the fourth 4.0 pre-release of Automation Engineering Workbench (formerly TIA Portal Openness MCP).
It is a pre-release on GitHub: it is never marked as the latest release, and is not offered by the
3.3 updater or the Workbench update check of a 3.3 installation. Download it by hand from the
releases page to test it.

Unless a release is named below, the changes apply to all eight supported TIA Portal releases, V14 SP1, V15.1 and V16–V21.
The beta.4 changes have not run on a real TIA Portal. A separate real-machine regression session follows publication.

Behavior changes you must know

  • 27 more write tools preview by default. A call without dryRun:false, the preview's expectedPlanHash and the exact
    bound expectedProjectFile only previews or refuses the write. Use the hash and project file from that tool's own preview.
    The full list is below. Actions that only read retain their direct behavior.
  • Plans include input file contents. Changing an input file after preview makes the old plan stale and refuses apply.
    Preview again after a host restart. Directory plans currently include every file recursively, including files the import
    itself will not use.
  • Canonical parameter names. Use exportFile for a file, exportDirectory for an output directory, sourceDirectory for
    an input directory and an array of exact segments for devicePath. Old names and the legacy device-path string work until
    5.0 and return DEPRECATED_PARAMETER warnings in meta.warnings. Do not send an old name and its replacement together.
    An omitted required export target uses a folder for the current session under the output root. Omitted report directories
    also move there. GetSessionState.data.outputRoot identifies the root.
  • Schemas use descriptions for alternatives. No tool input schema has a root oneOf, allOf or anyOf. Mutually
    exclusive arguments and form-specific fields are described and checked at run time. Nested property schemas may still
    use combinators. Clients must handle a refused call even when its arguments pass their schema validation.
  • One tool-list model, short list by default. V14 SP1–V19 clients now start with the lite list. V20/V21's short list
    expands. All eight use the plc-foundation profile name, shared instructions and catalog shape. FindTools discovers the
    rest, CallTool invokes them, and --profile full requests the full list. The Workbench operator sees the full list for
    the selected release even when the attached AI host uses lite. Known tools unavailable on that release report
    UNSUPPORTED_CAPABILITY, while unknown names report TOOL_NOT_FOUND.
  • File-write approval shows the actual target. MCP file writes outside the output root require a Workbench approval card,
    including UNC targets. Every full normalized target is shown and bound to the decision. Git stage and commit always
    require approval. Turning off write approval requires typing the displayed localized confirmation word.
  • Workbench form prefill. PrefillWorkbenchForm exposes a flat schema. mode="set" requires exactly the fields for its
    selected form, and mode="clear" requires an empty fields object. Prefills belong to the calling session and await human
    confirmation. A mismatched form and field set is refused at run time.
  • Session recovery. A timed-out worker read returns TIMEOUT and drains before reuse. During recovery, cached
    GetSessionState and host-only tools remain available, while tools needing the worker remain gated. Write timeouts can
    still leave an unknown outcome requiring reset. Disconnect reports requiresTiaRestart from outstanding calls and the
    process lease. Use that result to decide whether TIA must restart. Save As, archive retrieval and isolated startup keep
    the current binding in sync.
  • Export handles are per session. A session can no longer read, list or clear another session's exports. Restarting its
    worker drops its export handles. Run the producing tool again to obtain new ones.

Tools newly covered by default preview

  • AttachDeviceNodeToSubnet, ConnectDeviceNodesToProfinetSubnet, CreateGsdDevice, CreateVersionControlWorkspace,
    DownloadPlc, EnsureSubnet.
  • ImportAlarmClasses, ImportAlarmTextLists, ImportHmiConnection, ImportHmiScreen, ImportHmiScreensFromDirectory,
    ImportHmiTagTable, ImportHmiTagTablesFromDirectory, ImportMasterCopyFromGlobalLibrary, ImportOpcUaInterface,
    ImportTechnologyObject, ImportTechnologyObjectsFromDirectory.
  • InvokeObject, InvokeService, ManageOnlineDriveFunctions, SeedProjectFromReference, SetDeviceItemAttribute,
    SetOpcUaInterfaceEnabled, SetPlcCpuSettings, SetPlcWatchTableModifyValue, SetUnifiedHmiButtonEventScriptCode,
    SetUnifiedHmiRuntimeState.

What is new compared with beta.3

What testers will notice

  • Batch tools use one plan hash. RepairAndReimportPlcBlock, ImportPlcTagTablesFromDirectory,
    ExportPlcWatchTablesToDirectory and ExportTechnologyObjectsToDirectory preview the selected items together and use one
    approval. Apply requires confirm:true, dryRun:false, the batch hash and the project file. Items run in order and stop
    at the first failure, with completed and unstarted items reported. The batch itself does not roll back earlier items.
  • Safer block moves. MovePlcBlockToGroup exports and checks a recovery copy before deleting the source, then imports and
    verifies the destination's parent, name, number and language. If verification fails, it attempts to remove the destination
    and restore the original group. Failed cleanup or restoration keeps the recovery file and reports the remaining work.
    OB moves remain refused because that round trip has not been verified to preserve their event assignment.
  • Rollback for captured writes. Multi-step engineering writes with captured recovery actions undo them in reverse order
    after failure. restored requires successful read-back verification. An uncertain or unverified restoration reports
    unknown and requires reset. Unified HMI button actions are sent in one worker request.
  • Native failure reasons. Results retain the redacted native reason. Proven refusals and failures that read back unchanged
    no longer become OUTCOME_UNKNOWN. Uncertain dispatched writes still require reset.
  • Remote relay. Remote MCP clients use a local stdio relay. Private and loopback destinations bypass proxies, other
    destinations follow the configured proxy and NO_PROXY rules, and new client configurations use the current user's
    DPAPI-protected access key. The HTTP listener validates Host and Origin on each request. The Workbench offers a proxy
    check and migration of old direct configurations.
  • Redesigned Workbench pages. The shell, project, environment check, logs and diagnostics, MCP and clients, version control
    and AI calls pages share the new layout. Approvals use a waiting/processed list and detail view with the host's risk level,
    equal-weight write decisions, a default rejection for destructive operations and a countdown. With several running TIA
    processes, select the exact PID to attach.
  • VMFIX-5b tool fixes. PLC loadable, fingerprint and monitor services are resolved through the PLC software and its device
    hierarchy. Unified tags bind through a verified PLC connection without writing read-only PlcName. Screen design, layout
    and background themes apply to existing screens without accidental rename requests. Missing connections report the native
    reason. On V21, technology-object creation still admits only the verified type/version pairs because other pairs caused a
    native crash. That V21 restriction remains pending real-machine evidence.
  • Other fixes. Technology-object directory export creates its output directory before the native export and reports a
    creation failure as an ordinary refusal. Tag-table import name filters are case-insensitive. The Workbench reads block details page by page with ListPlcBlocks, and native invocation logs can be filtered by exact request and timestamp range.

For developers

The wide merge-check is reported at about 12 minutes, compared with about 21 before FAST-GATE, against a target of about
10 minutes. Scheduling overlaps GUI and transport checks and reuses builds. HANG-GUARD replaces approved short waits with
120-second hang guards, and TREND-ALERT reports slowdowns above twice the recent median. Security analyzers and the block on
unapproved loosened checks run in the development gate, and full prepare performs a fresh dependency vulnerability scan.
These changes preserve the functional checks and their count gates.

Known limitations

  • Real TIA verification is pending. None of the beta.4 changes has run on a real TIA Portal. Publication is followed by a
    separate regression session on project copies, with its raw results retained for review. The generated checklist below
    remains unverified.
  • Argument and native-error detail is unfinished. Argument errors do not yet consistently carry JSON pointers, and native
    failures do not yet carry innererror. DES-4 Parts 2 and 3 moved to beta.5.
  • Update signing is not done. The maintainer accepted this risk on 2026-11-04. The updater checks a hash from the same
    GitHub release as the ZIP. Someone controlling the GitHub account could publish a malicious update.
  • LAN transport is plain HTTP. The maintainer accepted this risk on 2026-11-04. Anyone on the same network can read the
    access key and PLC passwords. Use it only on a trusted network.
  • UNC access can precede approval. Tool input and preview checks can contact a UNC server before an approval card and
    expose Windows credentials. S8 is planned before 4.0 to refuse network paths from AI ...
Read more

v4.0.0-beta.3

v4.0.0-beta.3 Pre-release
Pre-release

Choose a tag to compare

@asckye asckye released this 04 Nov 16:21

v4.0.0-beta.3: third 4.0 pre-release

This is the third 4.0 pre-release of Automation Engineering Workbench (formerly TIA Portal Openness MCP). It is published on
GitHub as a pre-release: it is never marked as the latest release, and the 3.3 updater and the Workbench update check of a
3.3 installation do not offer it. Download it by hand from the releases page to test it.

The last real-TIA test round used V21 on a virtual machine. This release fixes some of its findings; other findings remain
open as listed under Known limitations. These fixes and the new features have not been retested on a real TIA Portal yet.

Behavior changes you must know

  • File-write restrictions (SEC-1). Tools cannot write the approval settings or .git metadata. WritePlcSclSourceFile
    writes .scl files only; directory and extensionless inputs resolve to an .scl filename. It rejects alternate data streams
    and trailing dots or spaces. Git calls ignore repository hooks, fsmonitor and signing, so commits made through
    ManagePlcGitRepository do not run repository hooks.
  • Device whitelist removed. CreateHardwareDevice, CreateDevice and CreateHardwareCatalogDevice create any exact row of the same
    catalog read instead of only two example CPUs of the S7-1200/S7-1500 families, and the exact OrderNumber, version, duplicate-name
    check, preview hash, confirmation, project file identity and read-back after creation still apply.
  • expectedProject is the project name. It is Project.Name, not a file path: a value that looks like a path is refused with
    INVALID_ARGUMENT before any TIA call, and tools that check the project file keep expectedProjectFile (an absolute path).
  • ListPlcBlocks pages by default. It returns 4 items per page (limit 1 to 100); pass the returned meta.paging.nextCursor as
    cursor until complete is true, and start again with an empty cursor when a changed block inventory refuses the old one.
  • FindTools matches more strictly. A query of several words returns only tools that match every capability word with a minimum
    relevance, ranked by relevance with exact tool names first, while a one-word query still matches descriptions, so a broad
    query can return fewer tools than in beta.2.
  • Software-unit parameters only where the API has them. unitName and includeUnits appear only in the tool definitions of
    V16 to V21, swImportOptions from V15.1 on block and type imports (never on tag-table imports), and the culture
    importOptions only on V19 to V21.
  • New Workbench palette. The Workbench has new colors, system fonts, high-contrast outlines and a keyboard focus ring, while its
    layout, navigation and approval drawer are unchanged in beta.3.
  • Host stop and restart ask first. The Workbench asks for confirmation before it stops or restarts an MCP host, first asks the
    host to exit on its own (up to 20 seconds), and ends it by force only after a second confirmation that warns TIA Portal may
    need a restart.
  • Old HMI write tools preview by default. The EnsureUnifiedHmi*, ApplyUnifiedHmi* and BindUnifiedHmi* tools default to
    dryRun=true and return a plan; pass dryRun=false to write, with approval as before.

What is new compared with beta.2

What testers will notice

  • New public name. The product is now called Automation Engineering Workbench (自动化工程工作台). Executables, the plugin ID,
    the MCP server name tia-portal, the delivery package name and the repository address are unchanged. The Siemens trademark
    notice and the project origin are stated in the README and NOTICE files.
  • For testers. A 3.3 to 4.0 migration guide, a per-release
    real-machine checklist and new issue forms for bugs, real-machine results and feature
    requests.
  • MCP hosts are visible. The MCP page of the Workbench lists every host of its data folder: PID, version, start time,
    transport and HTTP endpoint. Hosts from an older or unknown version are flagged. After a human confirms, the Workbench can stop a
    host or restart the HTTP host with the saved settings. A stdio host is restarted by its MCP client. AI tools cannot stop or
    restart hosts.
  • DecodePlcSimaticMl works on a clean installation. The package includes an isolated CPython 3.12.10 standard-library runtime,
    pinned by hash, with its original licence. No user Python, pip download or ecosystem environment is needed. A missing runtime
    prerequisite is reported without installation paths.

Fixes for the beta.2 VM findings

  • Worker timeouts. A read that times out now reports requiresSessionReset=true with the recovery steps, instead of "no reset
    needed". The time budgets are unchanged. A worker that still responds detaches from TIA on its own thread; a busy or lost worker
    is still ended, and TIA Portal may still need a restart.
  • Failed reads. Failed reads (DCC/Startdrive, library and project compare, SiVArc, Safety and others) report the same reset
    requirement as the session state. The next call no longer gets an unexpected SESSION_RESET_REQUIRED.
  • Old L2 PLC tools. CreatePlcBlockGroup, MovePlcBlockToGroup, RepairAndReimportPlcBlock, ImportPlcTagTablesFromDirectory and
    related tools no longer fail on a valid reply or a dry-run argument. CreateDevice and CreateHardwareCatalogDevice use the same
    exact hardware creation path as CreateHardwareDevice, including devices that TIA files in the ungrouped system group.
  • Native messages. A native failure keeps the redacted exception type and message in the result, not only in the server log.
  • One session state. Host tools, generation planning and the Workbench read one session state. PlanProjectGeneration no longer
    says "No TIA Portal is connected" for an attached project. GetWorkbenchState.data.session describes the calling MCP session;
    selectedSession is the Workbench's current selection.
  • EnsureUnifiedHmiTag. An unsupported binding is refused before the tag is created. If the tag was created and the binding then
    fails, the result reports a partial write and the reset requirement, not an unknown outcome.
  • Library type instances. Overwriting a library type instance by XML import can break its type link. The preview and the
    execution now warn about it. The preview reports recoveryStatus=not-attempted-preview; the execution reports the real backup
    result.
  • V20/V21 examples. V20 and V21 serve the maintained call examples instead of frozen engine values. Unified paths start at
    ScreenGroups/Screens, screen and tag-table paths are absolute, and the softwarePath/blockPath hints show grouped stations
    and group-qualified block paths.
  • Large results. A large direct or CallTool result includes a ready-to-run GetExportContent call to read the rest. Completed
    export content survives cache eviction, block pages keep their cursor through CallTool, and malformed worker pages are refused.
  • Extension-family replies (VMFIX-2). Alarm, OPC UA, SiVArc, Startdrive/DCC and Safety tools validate each worker reply against its
    own contract. A normal refusal or failure is a typed tool error with the native cause and no longer locks the session.
  • Unified reads and HMI probes (VMFIX-2). Paged Unified reads no longer fail with "Structured input was not decoded by the host".
    GetUnifiedObjectEvents returns the script code. The HMI connection probes find devices inside device groups by name or
    project-tree path and name the target when nothing is found. SetUnifiedHmiRuntimeState reports the native failure cause.

New tools and parameters

  • Registered tools per release: see the tool matrix; runtime tools/list is authoritative.
  • AnalyzePlcCrossReferences (new READ tool, all eight releases) exports the relevant PLC blocks once and analyses callers,
    callees and reference sites offline, without the native cross-reference service. "Not queried" is never reported as zero
    references.
  • Native cross references. GetPlcCrossReferences, GetUnifiedCrossReferences and the delete-time reference checks run by
    default on V14 SP1 to V20. V21 stays opt-in: a human-only Workbench switch for the current session (the environment variable
    still works) enables it with a risk notice. GetSessionState reports where the setting comes from and the read-only approval
    state.
  • HMI. Faceplate interface items can be addressed by PropertyName; their values are converted to the current value's type and
    read back. Faceplate instance tracing no longer asks the caller to guess the type path and version.
  • Software units (V16 to V21). PLC XML import, export and directory import take an exact unitName; without it the PLC root is
    used as before. New explicit swImportOptions (V15.1 to V21) and culture importOptions (V19 to V21) are off by default and
    shown in the preview. The software tree shows units, tag and constant reads take unitName or includeUnits, and
    AnalyzePlcCrossReferences can select a unit. Unit objects are published with the existing SetPlcUnitObjectAccess tool (preview,
    approval, read-back).
  • ListPlcBlocks takes limit and cursor, pages in a stable group-qualified path order and reads full attributes only for the
    current page. Every item has the exact path that GetPlcBlockInfo and ExportPlcBlock accept.

Safety and approval

  • The old HMI write tools refuse renames and same-name items of another type, and keep per-item write results a...
Read more

v4.0.0-beta.2

v4.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

@asckye asckye released this 30 Oct 19:00

v4.0.0-beta.2: second 4.0 pre-release

This is the second 4.0 pre-release. It is published on GitHub as a pre-release: it is never marked as the latest release,
and the 3.3 updater and the Workbench update check of a 3.3 installation do not offer it. Download it by hand from the release
page to test it. Native behavior remains unverified on a real TIA Portal.

What is new compared with beta.1

  • Tester reports. Unified tag tables and screens given as /Group/Sub/Name are created inside the existing groups instead of
    at the root under the path as a name; relative, backslash and malformed paths are refused with the corrected absolute form.
    Malformed object paths (objectPath, branch and similar) are refused before confirmation, approval or any TIA call, with the
    expected shape in the message. SetUnifiedHmiButtonEventScriptCode no longer reports an unknown outcome on V20/V21.
  • HMI review fixes. Unified object-path examples start at Screens/ScreenGroups; a faceplate container example was added.
    Faceplate, custom web control and custom widget containers require containedType (passed verbatim) and other item types refuse
    it; flags enums accept combinations such as "ShowCaption, CanMove"; Unified tag-table lists include nested groups with absolute
    paths; Classic tag lists without a table name list every table; failed lookups are no longer reported as "not found".
    EnsureUnifiedHmiTag now requires plcName and plcTag (no PLC_1 or same-name default).
  • Stability. The HTTP host listens before it builds a session catalog, and bridged tool calls are dispatched asynchronously.
  • Workbench text. The P8-80e text review improves labels and guidance across the Workbench.
  • Sensitive-value digests. The P8-83b fix keeps sensitive values redacted consistently in approval, plan and audit digests.
  • Release chain. Packaging and release-record fixes support the host and PLC-worker delivery without the retired engine.
  • PLC audit fixes (P8-81d). Imports refuse unsupported SimaticML versions instead of rewriting their headers and require
    explicit overwrite authorization. Type imports precede blocks, compile results retain native diagnostics, and V21-only
    FC/FB and related composers are withheld on V20 while release-aware UDT, tag-table and global DB builders remain available.
  • HMI audit fixes (P8-81e). Project graphics tools are registered on all eight releases; Unified screen-item inspection is
    limited to V19–V21, and the classic tag-table/package builders are withheld on V20. HMI imports default to overwrite=false,
    missing folders refuse instead of falling back to the root, omitted script options preserve existing settings, and unverified
    Unified connection creation refuses with guidance.
  • Library, VCI, Safety and reflection fixes (P8-81f). DCB library import is registered from V16. VCI uses the documented
    root-relative export directory and chooses supported formats consistently. Library and Safety writes validate prerequisites
    before changes; ambiguous reflection calls and guarded writes refuse with dedicated-tool guidance.
  • Security and optional-product fixes (P8-81g). PUT/GET changes default to preview (dryRun=true); unverified security
    attributes refuse before writes. Password-policy failures retain unchanged-state evidence, credential callbacks respect their
    lifetime, and drive/SiVArc operations use release-specific admission and native feasibility checks.

Install it next to 3.3

  1. Download TIA_MCP_Delivery_v4.0.0-beta.2_<date>.zip and its .sha256 from the GitHub pre-release and check the SHA-256.
  2. Unpack it into a new folder, for example C:\TIA_MCP_4.0.0-beta.2. Do not unpack it over the 3.3 installation and do not run the
    3.3 updater on it. Each installation keeps its own data and logs when its folder is writable.
  3. Start TiaOpenness.exe from the new folder and use the environment check. Point a separate MCP client entry at the new folder;
    keep the 3.3 entry for your normal work. See configuration.
  4. Use copies of your TIA projects. Do not connect the 3.3 and the 4.0 hosts to the same TIA Portal process at the same time.
  5. To remove the pre-release, close its processes and delete its folder; the 3.3 installation is not changed.

Report problems

Open an issue with the pre-release report form
and include:

  • the package name, the TIA Portal version with its update, and the release key (14sp1 to 21);
  • the item number from the "Not verified on a real TIA Portal" list below, if the report is about one of its items;
  • the tool call with its arguments (remove passwords and keys) and the complete result envelope;
  • what you expected and what TIA Portal shows, and whether the project was saved;
  • the Workbench audit or diagnostics export for the request ID (the diagnostics folder is data\diagnostics in the installation
    folder, or %LOCALAPPDATA%\TiaMcp\diagnostics when that folder is not writable). Do not attach customer projects, credentials or
    unredacted logs.

Every item in the list below has a number. When you check one, give its item number and say whether it passed; a passed item is as
useful as a failed one.

Not verified on a real TIA Portal

Generated by generate-prerelease-notes from the real-machine ledger and the API audit VM checklist. Builds, offline suites and CI passed for this pre-release; none of the items below has been run against a real TIA Portal. Please report what you check with the item number, the TIA version and the exact steps.

Real-machine ledger

未发布改动的验收边界

  1. 引擎监控/强制表与工艺对象共享原语(P4-I2,TiaSharedAdapterPaths 默认 false): NOT RUN;V20/V21 使用测试工程副本比较两种变体,核对借用同一个 ProjectBase、原有 MTA 线程、调用顺序与参数、诊断关联 ID。覆盖根组/嵌套组、重名与精确路径、空表、反射回退、读属性失败;监控表覆盖 XML 导出→修改→Override 导入→新代理读回、None 导入、注释行创建/删除、整表删除及计数读回,强制表保持原有查找/创建和属性拒绝语义。工艺对象覆盖递归枚举、导出、目录导入、受支持的技术版本、创建后 Find、参数读取/写入、删除后验证、部分失败与工程切换;Foundation 八版分别核对根组/递归读取范围与不覆盖导出。比较消息、字段、结果顺序及失败后的工程状态,不自动重放写入。在线监视与 S7 读取须另行授权;离线编译、调用图和响应快照不代替真机验收,未验收不得发布。
  2. 引擎硬件目录与设备创建共享原语(P4-I3,TiaSharedAdapterPaths 默认 false): NOT RUN;发布前在 V20、V21 测试工程副本分别比较默认与共享路径的 CreateDevice、CreateHardwareDevice、SearchHardwareCatalog、SearchInstalledGsdDevices、CreateHardwareCatalogDevice、CreateGsdDevice。核对同一 ProjectBase、原有 MTA 线程、目录反射及类型化字段读取的顺序与参数、同文件同关联 ID 日志;覆盖无工程、空关键字、无目录候选、重复候选、评分排序、GSDML 回退、精确 TypeIdentifier、Unified 面板版本拒绝、MLFB×版本×名称尝试顺序、失败后继续及部分写入后的工程状态。Foundation V19–V21 保持所属 STA、目录 Find 和字段顺序、计划哈希及确认保护、完整设备清点、恰好一次 CreateWithItem、结果未知后禁止重放;核对不同宿主各自的响应和错误语义,回读创建对象并显式保存。记录引擎/适配器哈希与 TIA 补丁;离线调用图和快照不替代真机验收,验收前不得发布或默认开启。
  3. 引擎 PLC 块与编译共享原语(P4-I4a,TiaSharedAdapterPaths 默认 false): NOT RUN;八版静态证据通过,宿主限于迁移方法,V20/V21 两种引擎调用图与非域 IL 通过。V20、V21 使用同版测试工程副本比较两种变体:导出覆盖及不一致块跳过、空组删除与删后回读、类型组创建、组重命名/删除、块保护、验证导入及可选编译、移动块的文档/XML 回退与恢复文件保留、OB 拒绝。覆盖软件/设备编译器查找、Safety 登录不登出、编译消息读取失败;在线快照/指纹另需明确授权,核对 TLS/密码回调及分页。逐项记录原生调用顺序、参数、引擎 MTA 与 Foundation/Studio STA、既有工程和对象归属、异常文本及部分失败。八版 Foundation/Studio 核对块/类型遍历和批次导入导出的原有覆盖策略;缺少或失效句柄后不重放写入。离线响应相同与织入校验不代替真机回放。
  4. 引擎 VCI 共享原语(P4-I1,TiaSharedAdapterPaths 默认 false): NOT RUN;V20、V21 各以测试工程副本对比默认与开启开关的同版引擎,完成五个 VCI 工具的往返验收后,方可考虑默认开启;未验收的试验构建不得发布。核对同一个 ProjectBase、原有 MTA 线程、原生调用顺序与参数、同文件同关联 ID 日志。覆盖无工程/无 VCI 服务、空及嵌套工作区、名称大小写与首个工作区选择、缺目录与重名拒绝、列表可选属性失败;状态覆盖 Equal/Unequal/文件缺失/未知或异常及 changedOnly。同步覆盖 dryRun、跳过 Equal、未知状态的两种 changedOnly、逐项失败后继续;WorkspaceToProject 仍在原生调用前拒绝。映射覆盖根与用户设备组、设备过滤、粗粒度对象拥有子树、既有映射、文件命名、maxObjects 截断、walkTrace、dryRun、导出失败与查询失败后重取工作区、部分完成后继续,确认不重试同一次写入。切换、关闭、重开工程后不得沿用旧 VCI 句柄;强制 GC 后中间代理仍可用。比较完整消息、字段、计数和结果顺序,回读工作区文件与映射并显式保存;记录引擎/适配器哈希、TIA 补丁和失败后的工程状态。离线调用图与响应快照不代替这些验收。
  5. PLC 文档与外部源共享原语(P4-I4b,TiaSharedAdapterPaths 默认 false): NOT RUN;V20、V21 分别用测试工程副本比较默认与共享引擎的十个工具,静态证据见 P4-I4b(八版静态证明通过,不能替代真机验收);L5 验收前不得默认开启或发布试验构建。核对借用同一个 ProjectBase、原有 MTA、调用参数与顺序及同关联 ID 诊断。文档覆盖单块/批量导入导出、成对文件检查、覆盖选项、Override 后编号恢复的写入顺序、空/失败结果、返回对象不符、部分成功与停止、目录和文件操作失败、导出不一致块及不支持/许可失败;回读完整消息、对象顺序、编号和实际文件。外部源覆盖名称宽松匹配与精确匹配的既有差异、重复导入、缺失源的幂等删除、无参生成与带选项及目标组生成、主副本创建、dryRun、非空组删除拒绝、V20 改名拒绝与 V21 改名回读、单元与系统组遍历;失败后确认实际工程状态,不自动重试写入。八版 Foundation 保留各自版本拒绝、精确寻址、预览/覆盖、生成/编译/回读顺序、未知结果和原 STA 线程;批量导入继续通过同一导入上下文。切换/关闭/重开工程后不得复用失效句柄;记录构建哈希、TIA 补丁、日志、读回与显式保存结果,离线测试不代替真机往返。
  6. Studio 共享适配器会话(P4-G2,TiaSharedAdapterPaths 默认 false): NOT RUN;L5 完成前不得把开关默认值改为 true,试验构建不得作为发布包。八个精确版本(14sp1、15.1、16、17、18、19、20、21)分别用测试工程副本比较旧、新路径:附加已有进程与启动进程、带界面/无界面、打开/复用/保存/关闭/断开,PLC 与 HMI 设备及块/类型/变量表遍历、SimaticML 与源导出、覆盖拒绝与确认后的 XML/源导入、软件/设备编译、检查报告。核对调用顺序、参数、所属 STA、同步进度及回调重入拒绝;比较错误文本、部分成功结果和出错后继续操作。VCI 覆盖 16/17 初版、18/19 旧版、20/21 新版的工作区、映射、状态、双向同步(含 dryRun),14sp1/15.1 及无服务工程保持能力不可用;切换工程后不沿用旧 VCI 句柄。记录 bridge/adapter 哈希、打包副本织入验证、hello 身份、诊断日志及退出清理结果;离线 DTO 比对、mock、八版编译和桥接冒烟不代替真机验收。

V20/V21 host + worker acceptance (P6-54)

  1. 20: NOT RUN — On the V20 VM, connect to the intended TIA process and explicitly bind a disposable project copy; verify project identity and read state. Import one fixture and export it back to a separate directory; read back both sides. Compile the selected PLC software and record full nested diagnostics. Induce the approved worker timeout/fault fixture, inspect actual project state, restart the idle ...
Read more

v4.0.0-beta.1

v4.0.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@asckye asckye released this 23 Oct 04:14

v4.0.0-beta.1: first 4.0 pre-release

This is the first 4.0 pre-release. It is published on GitHub as a pre-release: it is never marked as the latest release,
and the 3.3 updater and the Workbench update check of a 3.3 installation do not offer it. Download it by hand from the release
page to test it.

This pre-release was not tested on a real TIA Portal. Builds, the offline suites, the V4 contract and response snapshots and GitHub CI
passed; the items that only a real TIA Portal can confirm are listed at the end. Please test with copies of your projects only.

What is new compared with 3.3.0

The complete list is in the 4.0.0 release draft; the main points:

  • Breaking MCP changes. Tool names are normalized by operation and domain, inputs use typed V4 schemas, and every result uses one
    schema-version-4 envelope. There are no 3.x tool aliases; the tool migration tables list every old name
    with its destination. Update prompts, scripts and client rules that call 3.x tool names.
  • One host and one worker for all eight releases. V14 SP1 to V21 start TiaMcp.FoundationHost.exe --release-key <key> from
    their own runtime folder, and the host starts the release's PLC worker for each MCP session. V20 and V21 no longer use the engine
    executables, and the package no longer contains them. Tools common to all eight releases share one implementation.
  • Command line. TiaMcp.FoundationHost.exe keeps doctor, audit verify, schema, version, config, install-plc-tools
    and help on every release; the engine commands such as gen, compile, export and import are retired in favor of the MCP
    tools.
  • Sessions and safety. Every MCP session has its own worker and leases the selected TIA process; an unknown write outcome locks
    the session until it is inspected and disconnected. Writes are previewed before approval, and refusals are typed.
  • Sensitive values stay out of digests. Approval cards, argument digests, generation and candidate plan hashes and audit
    records replace passwords, keys, credentials and tokens with a fixed placeholder before hashing. The real value still reaches
    the operation, so an apply may use a different password than its preview.
  • More tools on V14 SP1 to V19, ported from V20/V21 where the release's API allows them, plus the Workbench control, standard
    package and staging tools on every release.
  • New Workbench design. The Workbench follows Ant Design v5: a grouped side menu (icons only in narrow windows), a header with
    the MCP status, the connection, approvals, diagnostics and the language, and one Project page that combines the overview and the
    program blocks with a bulk-action bar. Below a 1200 px window the right-hand cards move under the page content. Light, dark and
    high-contrast themes and Chinese and English are kept; text and buttons meet WCAG 2.2 AA contrast. All text uses the Maple Mono
    CN font (SIL OFL 1.1), loaded privately from the installation and never installed system-wide, and the style matches the
    EplanMCP Workbench: no ligatures, a semibold selected menu item, and Reject and Approve buttons with the same style and width.
  • Workbench features. Write approvals, a hash-chained audit log, a live call panel, an environment check, ladder rendering and
    the program book.
  • Updater. The C# updater (runtime/tools/TiaMcp.Updater.exe) replaces the PowerShell script. A pre-release installation is
    offered newer pre-releases and the final release; a plain installation is only offered plain releases.

Install it next to 3.3

  1. Download TIA_MCP_Delivery_v4.0.0-beta.1_<date>.zip and its .sha256 from the GitHub pre-release and check the SHA-256.
  2. Unpack it into a new folder, for example C:\TIA_MCP_4.0.0-beta.1. Do not unpack it over the 3.3 installation and do not run the
    3.3 updater on it. Each installation keeps its own data and logs when its folder is writable.
  3. Start TiaOpenness.exe from the new folder and use the environment check. Point a separate MCP client entry at the new folder;
    keep the 3.3 entry for your normal work. See configuration.
  4. Use copies of your TIA projects. Do not connect the 3.3 and the 4.0 hosts to the same TIA Portal process at the same time.
  5. To remove the pre-release, close its processes and delete its folder; the 3.3 installation is not changed.

Report problems

Open an issue with the pre-release report form
and include:

  • the package name, the TIA Portal version with its update, and the release key (14sp1 to 21);
  • the item number from the "Not verified on a real TIA Portal" list below, if the report is about one of its items;
  • the tool call with its arguments (remove passwords and keys) and the complete result envelope;
  • what you expected and what TIA Portal shows, and whether the project was saved;
  • the Workbench audit or diagnostics export for the request ID (the diagnostics folder is data\diagnostics in the installation
    folder, or %LOCALAPPDATA%\TiaMcp\diagnostics when that folder is not writable). Do not attach customer projects, credentials or
    unredacted logs.

Every item in the list below has a number. When you check one, give its item number and say whether it passed; a passed item is as
useful as a failed one.

Not verified on a real TIA Portal

Note (2026-10-22): items 1–6 compare the removed V20/V21 engine with the shared path; the engine was removed before this pre-release, so they cannot be checked and are withdrawn. Start with item 7.

Generated by generate-prerelease-notes from the real-machine ledger and the API audit VM checklist. Builds, offline suites and CI passed for this pre-release; none of the items below has been run against a real TIA Portal. Please report what you check with the item number, the TIA version and the exact steps.

Real-machine ledger

未发布改动的验收边界

  1. 引擎监控/强制表与工艺对象共享原语(P4-I2,TiaSharedAdapterPaths 默认 false): NOT RUN;V20/V21 使用测试工程副本比较两种变体,核对借用同一个 ProjectBase、原有 MTA 线程、调用顺序与参数、诊断关联 ID。覆盖根组/嵌套组、重名与精确路径、空表、反射回退、读属性失败;监控表覆盖 XML 导出→修改→Override 导入→新代理读回、None 导入、注释行创建/删除、整表删除及计数读回,强制表保持原有查找/创建和属性拒绝语义。工艺对象覆盖递归枚举、导出、目录导入、受支持的技术版本、创建后 Find、参数读取/写入、删除后验证、部分失败与工程切换;Foundation 八版分别核对根组/递归读取范围与不覆盖导出。比较消息、字段、结果顺序及失败后的工程状态,不自动重放写入。在线监视与 S7 读取须另行授权;离线编译、调用图和响应快照不代替真机验收,未验收不得发布。
  2. 引擎硬件目录与设备创建共享原语(P4-I3,TiaSharedAdapterPaths 默认 false): NOT RUN;发布前在 V20、V21 测试工程副本分别比较默认与共享路径的 CreateDevice、CreateHardwareDevice、SearchHardwareCatalog、SearchInstalledGsdDevices、CreateHardwareCatalogDevice、CreateGsdDevice。核对同一 ProjectBase、原有 MTA 线程、目录反射及类型化字段读取的顺序与参数、同文件同关联 ID 日志;覆盖无工程、空关键字、无目录候选、重复候选、评分排序、GSDML 回退、精确 TypeIdentifier、Unified 面板版本拒绝、MLFB×版本×名称尝试顺序、失败后继续及部分写入后的工程状态。Foundation V19–V21 保持所属 STA、目录 Find 和字段顺序、计划哈希及确认保护、完整设备清点、恰好一次 CreateWithItem、结果未知后禁止重放;核对不同宿主各自的响应和错误语义,回读创建对象并显式保存。记录引擎/适配器哈希与 TIA 补丁;离线调用图和快照不替代真机验收,验收前不得发布或默认开启。
  3. 引擎 PLC 块与编译共享原语(P4-I4a,TiaSharedAdapterPaths 默认 false): NOT RUN;八版静态证据通过,宿主限于迁移方法,V20/V21 两种引擎调用图与非域 IL 通过。V20、V21 使用同版测试工程副本比较两种变体:导出覆盖及不一致块跳过、空组删除与删后回读、类型组创建、组重命名/删除、块保护、验证导入及可选编译、移动块的文档/XML 回退与恢复文件保留、OB 拒绝。覆盖软件/设备编译器查找、Safety 登录不登出、编译消息读取失败;在线快照/指纹另需明确授权,核对 TLS/密码回调及分页。逐项记录原生调用顺序、参数、引擎 MTA 与 Foundation/Studio STA、既有工程和对象归属、异常文本及部分失败。八版 Foundation/Studio 核对块/类型遍历和批次导入导出的原有覆盖策略;缺少或失效句柄后不重放写入。离线响应相同与织入校验不代替真机回放。
  4. 引擎 VCI 共享原语(P4-I1,TiaSharedAdapterPaths 默认 false): NOT RUN;V20、V21 各以测试工程副本对比默认与开启开关的同版引擎,完成五个 VCI 工具的往返验收后,方可考虑默认开启;未验收的试验构建不得发布。核对同一个 ProjectBase、原有 MTA 线程、原生调用顺序与参数、同文件同关联 ID 日志。覆盖无工程/无 VCI 服务、空及嵌套工作区、名称大小写与首个工作区选择、缺目录与重名拒绝、列表可选属性失败;状态覆盖 Equal/Unequal/文件缺失/未知或异常及 changedOnly。同步覆盖 dryRun、跳过 Equal、未知状态的两种 changedOnly、逐项失败后继续;WorkspaceToProject 仍在原生调用前拒绝。映射覆盖根与用户设备组、设备过滤、粗粒度对象拥有子树、既有映射、文件命名、maxObjects 截断、walkTrace、dryRun、导出失败与查询失败后重取工作区、部分完成后继续,确认不重试同一次写入。切换、关闭、重开工程后不得沿用旧 VCI 句柄;强制 GC 后中间代理仍可用。比较完整消息、字段、计数和结果顺序,回读工作区文件与映射并显式保存;记录引擎/适配器哈希、TIA 补丁和失败后的工程状态。离线调用图与响应快照不代替这些验收。
  5. PLC 文档与外部源共享原语(P4-I4b,TiaSharedAdapterPaths 默认 false): NOT RUN;V20、V21 分别用测试工程副本比较默认与共享引擎的十个工具,静态证据见 P4-I4b(八版静态证明通过,不能替代真机验收);L5 验收前不得默认开启或发布试验构建。核对借用同一个 ProjectBase、原有 MTA、调用参数与顺序及同关联 ID 诊断。文档覆盖单块/批量导入导出、成对文件检查、覆盖选项、Override 后编号恢复的写入顺序、空/失败结果、返回对象不符、部分成功与停止、目录和文件操作失败、导出不一致块及不支持/许可失败;回读完整消息、对象顺序、编号和实际文件。外部源覆盖名称宽松匹配与精确匹配的既有差异、重复导入、缺失源的幂等删除、无参生成与带选项及目标组生成、主副本创建、dryRun、非空组删除拒绝、V20 改名拒绝与 V21 改名回读、单元与系统组遍历;失败后确认实际工程状态,不自动重试写入。八版 Foundation 保留各自版本拒绝、精确寻址、预览/覆盖、生成/编译/回读顺序、未知结果和原 STA 线程;批量导入继续通过同一导入上下文。切换/关闭/重开工程后不得复用失效句柄;记录构建哈希、TIA 补丁、日志、读回与显式保存结果,离线测试不代替真机往返。
  6. Studio 共享适配器会话(P4-G2,TiaSharedAdapterPaths 默认 false): NOT RUN;L5 完成前不得把开关默认值改为 true,试验构建不得作为发布包。八个精确版本(14sp1、15.1、16、17、18、19、20、21)分别用测试工程副本比较旧、新路径:附加已有进程与启动进程、带界面/无界面、打开/复用/保存/关闭/断开,PLC 与 HMI 设备及块/类型/变量表遍历、SimaticML 与源导出、覆盖拒绝与确认后的 XML/源导入、软件/设备编译、检查报告。核对调用顺序、参数、所属 STA、同步进度及回调重入拒绝;比较错误文本、部分成功结果和出错后继续操作。VCI 覆盖 16/17 初版、18/19 旧版、20/21 新版的工作区、映射、状态、双向同步(含 dryRun),14sp1/15.1 及无服务工程保持能力不可用;切换工程后不沿用旧 VCI 句柄。记录 bridge/adapter 哈希、打包副本织入验证、hello 身份、诊断日志及退出清理结果;离线 DTO 比对、mock、八版编译和桥接冒烟不代替真机验收。

V20/V21 host + worker acceptance (P6-54)

  1. 20: NOT RUN — On the V20 VM, connect to the intended TIA process and explicitly bind a ...
Read more

v3.3.0

Choose a tag to compare

@asckye asckye released this 05 Oct 00:31

v3.3.0 — Unified desktop and compatible runtime refactor

3.3.0 is the first release after the internal refactor across phases 0–5, including the default-build changes from phase 4. It includes MCP runtimes for V14 SP1, V15.1 and V16–V21 and one desktop workbench for configuration and engineering. Original V14/V15 are not supported.

MCP tool names, parameter names and types, response structures and error conventions remain compatible with 3.2.0, except for the stricter PLC name resolution described below (G9). The experimental Studio session and engine VCI routes behind TiaSharedAdapterPaths remain disabled (false) and are outside this release. Phase 6 changes belong to 4.0.

Version scope

TIA release Registered tools MCP implementation
V14 SP1 57 PLC foundation host with exact-version worker
V15.1 58 PLC foundation host with exact-version worker
V16 60 PLC foundation host with exact-version worker
V17 60 PLC foundation host with exact-version worker
V18 60 PLC foundation host with exact-version worker
V19 62 PLC foundation host with exact-version worker
V20 477 Full engine; 63-tool lite profile with discovery
V21 488 Full engine; 63-tool lite profile with discovery

Counts and contracts are unchanged from 3.2.0 and match the eight contract snapshots. These catalogs do not imply feature parity across TIA releases. Foundation and full engines can expose different schemas for the same tool name; use the selected engine's schema and GetToolUsage.

Changes

  • One desktop. The root TiaMcpConfigurator.exe opens the WPF/.NET 10 workbench. Engineering and MCP & clients share one window and retain their page state. Menus are grouped by owner: Project and PLC run the workbench's own bridge operations (Ctrl+O open or connect, Ctrl+S save, Ctrl+B compile), MCP runs the service and client actions of the configuration page with the same availability as its buttons, View switches pages (Ctrl+1 / Ctrl+2), and Tools holds language and theme. The title bar shows the MCP service state on both pages and keeps version selection. Client configuration merging, backups and secret protection are preserved; native bridges and MCP engines remain separate backend processes.
  • Desktop fixes. The options panel opens correctly, panels follow the light/dark theme, application dialogs use the workbench style, and the configuration menu entries that stayed Chinese in English mode are translated. The caption shows the current page, and Help exposes updates from either page. Summary, log and diff cards share one card style; Windows 10 shows the caption and list icons instead of empty boxes; closing the workbench with the HTTP service running no longer crashes.
  • Bundles work outside the repository. Engines and Studio locate bundled guides, templates, companion scripts, sibling engines and bridge components from the installation layout. A complete extracted bundle needs no Git checkout. The V21 ecosystem catalog is embedded in both full engines, so its queries no longer depend on a loose JSON file; editing the reference copy does not change those queries. Existing resource overrides and compatibility probes remain in place. See runtime layout.
  • Bundled .NET 10 runtime. The package ships Microsoft .NET 10.0.12 in runtime/dotnet (base runtime, ASP.NET Core and Windows Desktop), taken from Microsoft's official archives and checked against their published SHA-512. The V14 SP1–V19 foundation hosts move from .NET 8 to .NET 10, and every .NET executable in the package looks for this copy first, so the target computer needs no .NET 8, ASP.NET Core or .NET 10 Desktop Runtime installation.
  • Framework requirement for older workers. The V14 SP1, V15.1 and V16 foundation workers now target .NET Framework 4.8, matching the later workers. .NET Framework is a Windows component and cannot be bundled; install 4.8 on Windows versions that do not include it (before Windows 10 1903).
  • Worker and Studio bridge protocol. Both now use internal protocol 2, with an identity handshake and request/session correlation; their JSON payloads use System.Text.Json. This requires no MCP client protocol change. Failed requests are never automatically replayed. Handled Studio operation errors keep their original text and allow the session to continue; a broken channel requires explicit recovery after inspecting the actual TIA state.
  • One diagnostics journal per process. Engine and in-process adapter diagnostics share a journal and call correlation IDs, making an operation traceable across that boundary. Separate worker processes keep their own journals. The default location remains %LOCALAPPDATA%\TiaMcp\diagnostics, with the existing TIA_MCP_DIAGNOSTICS_DIRECTORY override.
  • V15.1 project files. The V15.1 foundation engine accepts the .ap15_1 files TIA V15.1 actually writes. Since 3.2.0 it accepted only .ap15, so binding, opening or creating a V15.1 project failed; a V15 .ap15 project is still not opened as V15.1.
  • Process and installation fixes. Child-process input is written as UTF-8 without a BOM regardless of the Windows console code page, avoiding corrupted non-ASCII requests. Foundation health reports use the application release version instead of a hard-coded value. The desktop updater recognizes a worktree's .git file as a source checkout and disables installation updates there.

Internally, the large engine classes were split into domain tools/services and a session kernel, with shared logic, runtime channels and adapter contracts separated into libraries. Compatibility evidence includes unchanged tool/schema contracts, raw response snapshots for direct and CallTool paths where available, per-domain byte comparisons (68 domains, 3,748 checks per full-engine version for the response conversions), and native call inventories checking the structural moves. The refactor plan records the evidence and its limits.

PLC name resolution — behavior change (G9)

In the V20/V21 full engines, reads and writes now resolve a non-empty softwarePath only by an exact software name or a unique structural alias: CPU, owning station/device, or a group-qualified device/software path. Matching ignores case and surrounding whitespace. An incorrect name no longer selects the only PLC in the project, and substrings are no longer guessed. This prevents a stale name from silently targeting a different PLC after another client changes the bound project.

For example, assume one PLC named PLC_Main, on CPU CPU_1 in station Station_1, under device group Line_A:

GetBlocks argument 3.3.0 result
{"softwarePath":" plc_main "} Resolves PLC_Main.
{"softwarePath":"CPU_1"} or {"softwarePath":"Line_A/Station_1/PLC_Main"} Resolves the uniquely matching PLC.
{"softwarePath":"PLC_Old"} or {"softwarePath":"Main"} Returns NotFound with available PLC paths; 3.2 could select the sole PLC.
{"softwarePath":""} Still selects the sole PLC; it cannot choose between multiple PLCs.

If two PLCs share the station alias Station_1, that alias returns an ambiguity error listing the candidates. Use a unique software name or the appropriate qualified path. A group name alone is not a PLC alias. The same rules apply to reads such as ExportPlcTagTable and writes such as ImportPlcTagTable. Verified resolutions are cached, and changing the bound project clears the cache.

Before upgrading, replace placeholder, stale or partial PLC names in saved prompts and automation with actual names or unique paths from the selected project. Empty-name shorthand remains available where the tool accepts it and the project contains exactly one PLC.

Validation and real-machine acceptance

Recorded offline evidence covers full-engine functional and protocol checks, eight exact-version SDK builds, Foundation/Studio channel fault tests, JSON golden samples, desktop/configuration tests and bundle relocation checks. The channel suite recorded 253 checks; Studio relocation compared 1,921 results; embedded ecosystem catalog checks passed 75 cases in each full engine. These are implementation-task results recorded in the refactor plan and layout evidence, not a completed 3.3.0 real-machine acceptance run. The release workflow rebuilds and validates the final candidate and package.

The 3.3.0 minimal per-VM acceptance list is the publication gate: Foundation MCP on V14 SP1–V19 (including the net48 change on the oldest three), Studio on V14 SP1/V16/V21, and G9 plus default-engine smoke checks on V20/V21. It uses the candidate bundle outside the repository and test-project copies. Every ite...

Read more

v3.2.0

Choose a tag to compare

@asckye asckye released this 03 Oct 11:42

v3.2.0 — Eight TIA releases, direct Openness Studio and unified tool examples

Released 2026-10-03. The complete delivery includes MCP runtimes for V14 SP1, V15.1 and V16–V21, the WPF configurator, and TIA Openness Studio with eight native adapters. Application release version: 3.2.0. Original V14/V15 are not supported.

Version scope

TIA release Registered tools MCP implementation
V14 SP1 57 PLC foundation host with exact-version worker
V15.1 58 PLC foundation host with exact-version worker
V16 60 PLC foundation host with exact-version worker
V17 60 PLC foundation host with exact-version worker
V18 60 PLC foundation host with exact-version worker
V19 62 PLC foundation host with exact-version worker
V20 477 Full engine; 63-tool lite profile with discovery
V21 488 Full engine; 63-tool lite profile with discovery

These are implemented tool catalogs, not feature parity between releases or complete coverage of every Siemens API. Equal tool names can have different parameters and responses between foundation and full engines. Use the selected engine's schema and GetToolUsage.

Changes

  • The configurator selects the exact installed release. Shared version identities, environment discovery and independent algorithms reduce duplication; typed adapters preserve real SDK differences. Original version branches were archived before deletion; master is the maintained branch.
  • TIA Openness Studio is included as a direct Openness desktop client. Its English/Chinese Glass Layers views preserve the application commands and use a native bridge without an MCP dependency. VCI uses legacy APIs on V16–V19 and modern APIs on V20/V21; V14 SP1/V15.1 have no VCI implementation.
  • Every registered tool has a parameterized call example through GetToolUsage, together with input origins, result interpretation and official references. The unified library includes 25 programming examples and 14 call sequences, 89 pinned official documents and 381 indexed code blocks/methods. The 1,322 release/tool combinations and 1,038 operation examples are checked against actual MCP schemas. Official API patterns and project-authored wrapper examples are identified separately.
  • Foundation external-source workflows now import an ASCII SCL/AWL/DB/UDT file, generate PLC blocks/types, compile and read back results. V14 SP1 exposes inventory observations because its generation method returns void; V15.1+ maps native generated objects to their actual paths. Ordinary native generation errors retain diagnostics and a usable session so corrected source can be tried again.
  • Foundation compilation no longer rejects every execution. It checks the selected PLC and observable project online states, and returns typed native counts and nested diagnostics. Devices without an exposed state provider are listed rather than asserted offline; Siemens' all-devices-offline prerequisite still applies.
  • Flat UDT and global DB XML builders accept outputReleaseKey for all eight releases, selecting Interface v2/v3/v4/v5 and version-dependent object attributes. The shared dependency planner reuses the integrated MIT Eido implementation.
  • All 30 MCP prompts register independently of optional unavailable assemblies. HMI screen import no longer automatically replays a failed write; directory batches retain the first failure. Startdrive parameter reads avoid the previous detailed parameter/bit traversal; the reported BICO crash remains unverified.
  • The formal release pipeline now rebuilds and packages all eight MCP runtimes and Studio, verifies their source/runtime hashes, and independently checks the downloaded release asset. Embedded JSON examples are part of the validated source inventory.

Validation and remaining work

The release process runs both full-engine test identities, eight typed worker/adapter builds, Studio client/WPF tests, foundation functional tests with the supplied eight SDKs, STDIO/HTTP checks, full/lite checks, diagnostics and local stability tests. It executes 74 in-memory call examples and validates 16 UDT/global DB interface fragments against their corresponding official XSDs. Final evidence is in the full-engine build record, multi-version build record and example coverage.

New native TIA/project acceptance remains NOT RUN. These checks do not establish successful import or compilation in a real project, or crash safety. This release does not deploy to a virtual machine or download to a PLC.

  • Foundation catalogs remain smaller than the full engines. The functional matrix tracks 29 reviewed families across eight releases; watch-table/technology-object imports, broader VCI exposure and additional families remain to be completed.
  • Foundation source import currently accepts ASCII. Chinese/non-ASCII source encoding requires version-specific native validation.
  • The other six shared PLC XML builders still emit V21 candidate XML. Interface-fragment XSD validation does not certify a complete document or CPU/type semantics.
  • Native PLC cross-reference and Unified script-library Name crash issues remain subject to their documented limits. The reported p2051[0] BICO read crash has no confirmed native regression pass. Worker isolation cannot guarantee TIA survives a native API failure.

Download and upgrade

New users can follow the beginner guide (Chinese), covering installation, local/VM connections, version selection, Studio, and the bundled SCL import/compile exercise. It includes copyable AI prompts and explains how to inspect actual results.

Download TIA_MCP_Delivery_v3.2.0_20261003.zip and its .sha256 asset. GitHub's automatically generated source archives do not include the runtime binaries. Stop the MCP/Studio processes before replacing an installation, preserve your configuration and secret, and restart clients after updating. No running service is updated automatically.

Select runtime/v<release-key>/TiaMcpServer.exe or use TiaMcpConfigurator.exe; Studio is runtime/studio/TiaOpenness.exe. Install matching Siemens TIA Portal, Openness, licenses and .NET runtimes separately: full engines require .NET Framework 4.8, foundation hosts also require .NET 8/ASP.NET Core 8, and Studio requires .NET 10 Desktop Runtime. Python companion tools retain their separate setup.

The archive contains the reviewed source, tests, documentation, templates, licenses and manifest-verified application files. Siemens PublicAPI assemblies, private engineering projects, user design handoffs, credentials and build logs are excluded.

Package: TIA_MCP_Delivery_v3.2.0_20261003.zip (2492 files, 43742716 bytes).

Source commit: 299f947d4b54a92873e9321a39f6b3dc39279e11.

ZIP SHA-256: 6ec0d0fc535db18bb496b77d49ee0cf55bd36ab78b6ed15871ef463fd6323a91.

v3.1.0

Choose a tag to compare

@asckye asckye released this 02 Oct 03:11

v3.1.0 — Openness diagnostics, PLC editing and V21 ecosystem tools

Released 2026-10-01. Complete V20/V21 delivery, with engine and configurator file version 3.1.0.0. The full inventory contains 486 tools, including 22 additions since v3.0.0; the default lite profile exposes 62, with the others accessible through FindTools and CallTool.

Changes

  • Optional --isolate-openness keeps MCP host diagnostics available after a worker failure. The supervisor uses bounded queues/deadlines, explicit recovery and no automatic write replay. It remains disabled by default. Exact project binding and cross-process TIA ownership checks reduce accidental session switching. See isolation and recovery.
  • The generated tool matrix is now replaced atomically, so an open memory-mapped viewer does not make publication fail while truncating the existing document. First creation and replacement with an active mapped view were checked locally.
  • Fine-grained diagnostics cover supported engine-owned Openness call boundaries. The build checks instrumentation coverage and wrapper compatibility; stage records distinguish attempted, returned and thrown calls. They do not instrument Siemens internals or prove crash safety.
  • PLC cross-reference protections also cover reflection routes. Native queries remain disabled by default because they have caused TIA exits. Download readiness uses actual consistency evidence, and document import checks use exact returned objects rather than ambiguous name matching.
  • PLC document workflows add offline call/symbol reference analysis, capability inspection, bounded XML text/start-value edits, and guarded overwrite import with retained export and readback comparison. Native import/compilation acceptance remains pending. See editing workflow and limits.
  • V21 ecosystem additions provide a dated official/third-party catalog, local Siemens XSD fragment validation, analysis-only SimaticML decoding and custom web control packaging. The catalog has 86 entries with explicit compatibility, licensing and integration status; it is not a list of 86 fully integrated products. See ecosystem adapters.
  • Precise HMI tag deletion, software-unit document operations, V20 option wrappers and compatibility diagnostics extend existing native tools. Siemens AI guidance is pinned to the latest reviewed source; all 32 guide bodies remain unchanged.

Added tools

Area Tools
Compatibility and diagnostics InspectSimaticSdCompatibility, ReadOpennessCompatibility, ReadNativeInvocationLog
Session and worker control ConnectToProject, ReadOpennessWorkerStatus, RestartOpennessWorker
HMI DeleteHmiTag, ManageUnifiedCwcPackage
PLC documents and references ManagePlcBlockDocuments, ReadPlcBlockScopes, ReadPlcBlockEditCapabilities, AnalyzePlcReferences, PatchPlcBlockDocument, ImportPlcBlockVerified
Offline ecosystem ReadV21EcosystemCatalog, ValidatePlcXmlSchemas, DecodePlcSimaticMl
Optional products ManageSinumerikSafetyMode, InitializeSimotionScripting, ExportScadaData, ImportSinumerikAlarmTexts, ManageSinumerikArchive

Tool registration is not a promise that an optional product or API exists on every installed version. The supplied PublicAPI, installed products, licenses, target object and native acceptance requirements still apply.

Validation

The release build records both Windows/net48 engines, 2,703 offline checks, 75 ecosystem protocol checks per version, and 17,936 local tool calls across direct/isolated hosts, STDIO/HTTP and full/lite profiles. API shape checks cover 2,840 cases for V20 and 3,126 for V21; the configurator has 111 checks. HTTP, resource discovery, process leases, fault injection, native journal readers and diagnostic wrapper checks are also in the build record.

The pinned decoder separately passed 107 selected upstream tests; two symbolic-link tests were skipped because the local Windows account could not create symlinks. Older extended stress and probe records are historical evidence for their recorded binaries, not additional tests of this release.

These checks do not attach to TIA, compile a user project or download to a PLC. This publication does not include new native acceptance or deployment to the user's virtual machine. The standalone native lifecycle/MCP/probe harnesses remain explicit opt-in tools.

Known limitations and upgrade

  • The V21 Unified script-library type Name crash remains unresolved. The known write route is guarded; this is not a usable rename fix. Standalone diagnostic preparation and evidence are included without claiming successful native rename tests.
  • Native PLC cross-reference crash safety, faceplate type creation and editing of type-internal controls/scripts are not certified by this release. Offline reference analysis cannot prove that an object is unreferenced or safe to delete.
  • Worker isolation protects availability of the MCP host; it cannot guarantee that TIA survives a failing API call. Writes interrupted by failures can have unknown outcomes and must not be replayed automatically.
  • SimaticML decoding is for reading only: its output is not recompilable/reimportable. XSD validation covers recognized fragments, not the whole export or instruction semantics. CWC packaging checks basic file/manifest conventions, not JavaScript behavior, the complete manifest schema or runtime compatibility; CWC is distinct from a faceplate/library type.
  • Official MAC, Project Check, external IDEs and remaining catalog candidates are not all embedded. Do not treat upstream claims or a V21 version selector as local acceptance.

Download the complete TIA_MCP_Delivery_v3.1.0_20261001.zip and its .sha256, rather than GitHub's source-only ZIP. Stop the MCP service before updating; the configurator's update workflow verifies and backs up the existing installation. Reconnect clients after restarting the engine. This publication does not automatically update a running service.

The archive contains V20/V21 runtimes and the WPF configurator, source, tests, documentation, templates and licenses. Siemens PublicAPI assemblies, private TIA projects, credentials and build logs are excluded. Python companion tools need their documented environment setup; isolation remains opt-in. V17–V21 upstream branches are retained independently and are not additional certified runtimes in this package.

Package: TIA_MCP_Delivery_v3.1.0_20261001.zip (1608 files, 22408358 bytes).

Source commit: 7316071a6b284034f200347eab81ce2fda98e1a9.

ZIP SHA-256:

f99f231a165075ed6f1cf6de35182f443eed02946583c02dd2b458f6f5a62454

v3.0.0

Choose a tag to compare

@asckye asckye released this 29 Sep 18:27

v3.0.0 — Official Openness workflow fixes and ecosystem tools

Released: 2026-09-29. Complete V20/V21 delivery: TIA_MCP_Delivery_v3.0.0_20260929.zip plus its SHA-256 sidecar.

This release adds 11 tools (464 total; lite remains 59), incorporates the pinned Siemens tia-portal-ai-extensions guidance, and fixes connection selection, ownership, late attachment cleanup, DLL identity checks, transaction outcomes and nested exclusive access.

Upgrade changes

  • RunToolsInTransaction now accepts only eight reviewed synchronous editing tools: CreatePlcTypeGroup, DeleteEmptyPlcBlockGroup, ManagePlcUserGroup, ManageDeviceUserGroup, ManageUnifiedHmiGroup, DeleteEmptyUnifiedHmiScreenGroup, UpdateUnifiedObjectProperties, and UpdateUnifiedMultilingualProperty. Unsupported calls fail preflight before starting a transaction; use their standalone tools where appropriate. Existing broader transaction clients need updating. This contract restriction is why the version advances to 3.0.0.
  • Native PLC GetCrossReferences and deletion cross-reference queries are disabled by default following reported TIA crashes. TIA_MCP_ENABLE_NATIVE_PLC_CROSS_REFERENCES=1 is an explicit diagnostic opt-in and still requires readable, consistent compilation state. Compilation success does not establish that the native query is safe.
  • All MCP transports share a process-local execution gate. Diagnostics record BEFORE/RETURNED/THREW without argument contents. Separate engine processes still have separate session state.

Added capabilities

ReadOpennessGuidance, RenderPlcVisualDiff, RunPlcCompanionTool, ReadToolBatch, PreviewToolBatch, ApplyToolBatch, ManagePlcGitRepository, GenerateOpcUaModelledInterface, AuditEngineeringExports, InstantiatePlcXmlTemplates, and ComposePlcAliasAlarmLad.

The usage guide documents previews, bounded inputs, installation and output formats. Batch apply is not an atomic transaction. OPC UA output generation does not import or compile a PLC. PLC Tools runs in a separate Python environment; install it with scripts/ecosystem/Install-PlcTools.ps1. The Python environment, Siemens PublicAPI assemblies and user projects are excluded from the distribution.

The 32 official Siemens guidance topics and nine fixes are documented in the official workflow audit. GetAuthoringGuide("openness-workflow") links the workflow in the engine. Symbol quoting and array readback corrections from upstream preserve this project's existing LAD render features. Vendored MIT sources retain attribution in third-party notices; GPL implementations were not copied.

Validation and limits

V20 and V21 builds, 2,551 offline assertions, API shape checks (V20: 2,805; V21: 3,097), 31 ecosystem checks per runtime and transport tests run locally. The pinned Python offline suite previously passed 2,091 tests with eight documented skips. The complete release build also runs resource discovery, remoting and configurator regression checks; exact results and input hashes are recorded in manifest/release-build.json and manifest/configurator-build.json.

No VM deployment or live TIA writes were performed for these new features. Native transaction/close behavior still needs acceptance testing. Pure Openness creation of a Unified faceplate type from scratch, editing its internal controls and type-local scripts remains unverified; library and instance operations do not establish those capabilities. See the audit for the remaining coverage gaps.

Upstream version-branch integration is intentionally deferred until after this release is published.

Package: TIA_MCP_Delivery_v3.0.0_20260929.zip (1465 files, 18203739 bytes).

Source commit: 32856cf2a35bc9f378bd31b43150ddc90802fc61.

ZIP SHA-256:

5a97c0b4649f4dc20d5a8d2d38d9316ac1509d5657df25bb1ef9613e5b88757a

v2.9.2

Choose a tag to compare

@asckye asckye released this 21 Sep 11:46

v2.9.2

小修(PATCH)。2.9.1 真机(项目1,Override 重生成后未编译):DeletePlcBlock {..., crossReferences:true} 被护栏挡住时只说“⚠️ 取不到这个块的交叉引用”,看不出是“PLC 有未编译块、先 CompileSoftware”。

改动

  • Portal.DeletePlcBlock / DeletePlcType:改用带 out reason 的 GetCrossReferences 重载;crossReferences=true 时结果多一个 crossReferenceUnavailableReason(与 DeletePlcTagTable 一致),警告写成“取不到这个块的交叉引用(refused: N block(s) ... not compiled ...)”。
  • 其余同 2.9.1(工具 453、lite 59、离线 2461)。

待真机

  • 项目1:Override 重生成后不编译,DeletePlcBlock {softwarePath:"MCP_STD", blockPath:"MCP_SimLogic", dryRun:true, crossReferences:true} 的 crossReferenceUnavailableReason 应以 refused: 开头并点名块;编译后再调应有交叉引用。

Package: TIA_MCP_Delivery_v2.9.2_20260921.zip (785 files, 16229054 bytes).

Source commit: e7256176d9121acea88fa7211c98c7fef3c57aee.

ZIP SHA-256:

0a0bc121d6eccc44e43c997bbfd72e99f7ab18ce30af0c8a837b313f35515fe9