State: kit shipped. Built over the documented and stubbed Openness names and tested on Linux against an object tree with those names; nothing has run against TIA Portal.
Read the tag tables
Each TIA Portal project (.apNN) row of TwinCAT Projects has a PLC Tags group. Expanding it, or running Read TIA Portal PLC Tags, reads it through the engineering host in the project's resident session (the build's, started without a user interface). Then there is a row per PLC with its device, and under it the tag table groups and tables as TIA Portal's project tree shows them.
For each tag: name, data type, address, comment per language and external access flags. For each user constant: name, data type and value. A member Openness could not read is named in the problems of its tag or table, never filled in.
The tag table editor
Open a table row, or run Open TIA Portal Tag Table. The editor shows one row per tag with its name, data type, address and comment in one language, and the user constants below, read only. Comment Language (toolbar) chooses the language.
| Key | Edit |
|---|---|
| Arrow keys | Move between cells |
| F2 or Enter | Change the focused cell |
| Insert | Add a tag |
| Delete | Remove the tag |
The same changes are commands on a table row and in the Command Palette: Add TIA Portal PLC Tag..., Remove TIA Portal PLC Tag..., Rename TIA Portal PLC Tag..., Change Data Type of TIA Portal PLC Tag..., Change Address of TIA Portal PLC Tag..., Change Comment of TIA Portal PLC Tag....
A cell or command whose member the loaded Openness version does not let the engineering host set is read only and says why. Which changes are offered is read from TIA Portal's types at run time, not assumed.
How a change is made
- The confirmation names the project, the PLC, the table, the tag with what it is now and what it becomes, and whether the project is saved. Choose Change and Save or Check without Saving.
- The change is made under TIA Portal's exclusive access, inside a transaction, and read back.
- Then the transaction is committed and the project saved, or, with Check without Saving, rolled back, so TIA Portal's project is never left with a change nobody saved.
Refused: TIA Portal reports unsaved changes in the project (a save would write them too); the table changed since it was read; the PLC, table or tag is not there or no longer as you saw it; a new name that another tag or user constant of the PLC already has (compared without regard to case); the project file or the engine session changed since the change was shown. A change TIA Portal raises on is rolled back and reported in TIA Portal's words; a change the read-back does not show is rolled back too. A rollback, commit or save whose effect cannot be read back is reported as not verified, with what to check.
Go to a tag
Go to TIA Portal PLC Tag (on a Problems entry, or in the Watch view's context menu) opens the table of a tag whose name is exactly a name the entry holds in double quotes, or the watched name. Go to TIA Portal PLC Tag... in the Command Palette asks for the name.
Not verified
- Every Openness call against TIA Portal, in particular creating a tag with name, data type and address, setting a comment, whether a transaction disposed without commit restores the tag, the form in which TIA Portal writes back a data type or address, and what it raises for a duplicate name or an address it refuses.
- Windows.