From other pages
The System, Server, Connector and Process roots as the Logic column shows them, every fixed point with its meaning, the read-only point and branch panels, and the notice that names the page where each root is edited.
The second caption of the Logic column, From other pages, holds the four roots this page only shows: System, Server, Connector and Process, in that order. Their points are readable by every expression, script, dashboard binding and agent tool, but nothing under them is created, edited or deleted here. Selecting any of their rows puts a one-line notice where the verbs would have been, with a button that opens the page that owns it.
The edited-elsewhere notice
| Root | The line the bar carries | Button | Drawn when the role holds |
|---|---|---|---|
| Connector | Read only here: drivers, devices and tags are edited on the Connector page. | Open Connector, the Connector page | View connector |
| Process | Read only here: models, units and channels are edited on the Process page. | Open Process, the Process page | Look at models, Run procedures or View histories |
| Server | Read only here: the OPC UA server is configured in Settings. | Open Settings, landing on the server's Configuration section | Change settings |
| System | Read only: application diagnostics the app publishes about itself, not edited anywhere. | None |
The line shows for every node under the root, however deep; the button shows only when this window's role can open the destination, so a viewer reads the sentence and never a door that answers with a refusal. Signing in as a role that holds the permission brings the button with it.
System
| Address | Type | Reading |
|---|---|---|
System.Now |
Date and time | The current instant. Inside an expression or a script it is the evaluation instant, so every reference within one run reads the same time. |
System.StartTime |
Date and time | When the application process started. |
System.Uptime |
Decimal | Seconds since the application started. |
System.Version |
Text | The application version. |
The four points are always Good.
Server
| Address | Type | Reading |
|---|---|---|
Server.Running |
Boolean | Whether the embedded OPC UA server is up. Always Good. |
Server.StartTime |
Date and time | When the server started. A Bad gap until it has started. |
Server.Uptime |
Decimal | Seconds since the server started. A Bad gap until it has started. |
Server.SessionCount |
Integer | Connected OPC UA sessions. Bad while the server is down. |
The same figures are shown on the server's Status section.
Connector
The Connector root draws the live tree the Connector page configures: one folder per driver kind (Simulated, ModbusTcp, …), then the folders the devices are filed in, then the devices, then their tags. Only enabled devices whose tags are materialized in the embedded server appear; a disabled device, and a device without a materialized tag, are absent together with their addresses. A tag's address is its alias, Connector.<Driver>.<Folders…>.<Device>.<Tag>, each segment sanitized (device folders); a Modbus RTU line adds no level. A driver and a folder wear the folder mark, a device the device mark, a tag the mark of the value category it publishes (Boolean, number, text, date). Expanding a tag in the Browse… picker lists its read surface; the column stops at the tag, and selecting it opens the point panel.
Process
The Process root draws every model as a folder, its units as folders in their order, and under each unit five fixed folders:
| Folder | Points | Type |
|---|---|---|
| Channels | One point per channel of the model, read through the unit's binding; a channel bound to a tag offers the tag surface, one bound to a variable the variable surface, an unbound one nothing. | The channel's data type |
| Procedure | Status, Running, Busy, Verdict, Mode, ActiveProcedure, SegmentIndex, CycleIndex, CycleCount, Cycle, FailedCycles, SamplesEvaluated, SamplesOut, SamplesUnavailable, SamplesInvalid, Elapsed, StartedAt. |
Text, Boolean, Integer, Decimal or Date and time as each name suggests |
| Productivity | Today and Rolling, each with Summary (ProductivityPercent, YieldPercent, TypicalElapsedSeconds, Finalized, OK, NOK, Indeterminate, Unclassified, Aborted, Failed), Outputs (one folder per productive output, with Quantity and RatePerHour) and Procedures (one folder per procedure with productivity enabled, with Quantity, RatePerHour and the summary points). |
Decimal for rates, percentages and durations; Integer for counts |
| Commands | Start, Hold, Resume, Stop, Abort (each reads whether the command could execute right now) and Comment (no reading). |
Boolean; Comment is text |
| Next | Procedure (the staged procedure's name) and one point per metadata field of the staged procedure; the branch reshapes when another procedure is staged, and a sequential field previews its next value. |
Text |
What each reading means is on the unit address space. A productivity point is Good only when its own value exists: a quantity with no completions is a real zero, while a rate with no occupied time or a percentage with no reference is a Bad gap. Command points are read-only everywhere: a dashboard Button dispatches the command and reads the point to disable itself; a script that calls one is refused at validation. No Process point can be written from Logic: recipes, staging and comments belong to the run screens.
The point panel
Selecting a point under any of the four roots (a diagnostic, a tag, a channel, a run-state or productivity point) opens a read-only panel headed by the point's mark and name and the line "A reading the address space publishes: what it holds right now, and the address an expression or a script names it by."
| Field | What it shows |
|---|---|
| Address | The rooted address, in a read-only text box you can select and copy. |
| Value | The current reading, large; "?" when the address no longer resolves; a dash for a gap. |
| Quality | Good or Bad. |
| Updated | For a tag, its application timestamp (or the source timestamp when there is none); for a variable, when it was last written or evaluated; for a computed point, now. |
The readouts refresh twice a second. Under them: "Use this address in an expression or a script (autocomplete or Browse…)." The panel has no verb: nothing here writes a tag (write it on the tag's page, from a script or from a dashboard control), and nothing copies for you beyond selecting the text.
The branch panel
Selecting a driver, a folder, a device, a model, a unit or one of the fixed folders opens the branch panel: the branch's mark and name, its address as a pill, the line "A branch of the address space: what it holds, and what each point reads right now.", and a grid of its direct children with Name, Address and Value (a dash for a gap or a Bad reading, "?" when a row no longer resolves), refreshed twice a second.
Why these nodes have no verbs
A driver, a device or a tag is configured on the Connector page, where its fields, its enable switch and its delete live; a model, a unit or a channel on the Process page; the server in Settings; the application diagnostics nowhere. Filtering the column, expanding, collapsing and copying an address are the only gestures these rows take, and a right-click on them opens no menu.