tia-openness-control

Use TIA Portal Openness as the execution boundary: any AI proposes structured actions, generated .NET code performs them through Siemens.Engineering, and every destructive or plant-impacting operation is explicit, logged, and reviewable.

• Identify the project path and exact operation. Detect the installed TIA Portal version automatically when the user does not specify one. • Confirm prerequisites: Windows host, TIA Portal V15 through V21 installed, user in the Siemens TIA Openness Windows group, Openness enabled, project backed up, and matching PublicAPI path. For first-time setup, instruct the user to add the Windows account to that group with administrator rights, then sign out and back in. • Choose execution mode: WithUserInterface for exploratory/debug work, WithoutUserInterface for repeatable batch work. • Generate or modify a C# .NET controller. Use scripts/new-openness-controller.ps1 to scaffold a starter controller when useful. • Keep AI commands declarative, such as JSON/YAML action plans, and map them through a whitelist. Do not execute arbitrary prompt text as code. • Run read-only or dry-run behavior first; then write only the requested target objects. • Capture stdout, stderr, exit code, active project path, and log file path for every run. • Verify results by reading the project back through Openness. Do not claim success from exit code, file timestamp, or "no exception" alone. • Save or archive the project and report changed objects, warnings, and compile diagnostics.

Keep this skill usable by any AI agent or automation runner: • Describe actions as plain JSON/YAML command documents. • Generate ordinary PowerShell, C#, .csproj, and CLI commands. • Avoid product-specific hidden state, proprietary prompt features, or assumptions about a single AI runtime. • Make every generated controller runnable by a human from a terminal. • Return machine-readable results when possible so another AI can continue from logs. Example command document: `json { "tiaVersion": "auto", "projectPath": "D:/Projects/Line1.ap20", "mode": "WithUserInterface", "dryRun": true, "actions": [ { "type": "ListDevices" } ] } `

Support TIA Portal V15, V15.1, V16, V17, V18, V19, V20, and V21. When scaffolding a controller, prefer automatic detection: `powershell powershell -ExecutionPolicy Bypass -File .\scripts\new-openness-controller.ps1 -OutputPath . -ProjectName TiaOpennessController ` The script scans C:\Program Files\Siemens\Automation\Portal V\PublicAPI\V and selects the highest supported installed version. Use -TiaVersion V17 or -TiaVersion V15_1 only when the user explicitly wants a specific version.