Status
The faceplate of the embedded OPC UA server: its lamp and state, the endpoint, Start, Stop, Restart and Test connection, and the six live meters.
Status is the first row of the OPC UA SERVER group on the Settings page, and the only place the server is started and stopped by hand. It is drawn as a faceplate: a masthead with the lamp, the state text, the endpoint and the power controls, over a recessed well of six meters. The page re-renders every second, so the meters track the running server. Opening the page takes the Change settings permission.
The masthead
| Element | What it shows |
|---|---|
| Lamp and state text | Online (green) while the server is up and its address space is live; Starting… (amber) between the start and that moment; Stopped (grey) while the host is not running. The bar along the card's edge takes the same colour, from the same reading as the lamp, so the two cannot disagree. |
| Endpoint | The network address a client dials: opc.tcp://<computer name>:<port>/UA/GanterLab. The computer's stable name is advertised, never 0.0.0.0 or a DHCP address; the same-machine alternative is under Connection addresses on Client access. |
The state text is the same one the tray icon's tooltip and the status bar read; see The embedded OPC UA server.
The commands
| Command | What it does | Greyed when (situation) | Not drawn when (role) |
|---|---|---|---|
| Start | Materializes the current configuration and starts the communication host. The status bar reads "Starting the OPC UA server…" and then "OPC UA server started.", or, when the host came back stopped, "OPC UA server failed to start: <the last error the server logged>" (or "…It may be unable to bind port N. Check the logs." when it logged nothing). |
While another lifecycle command runs, while a unit is running ("Configuration is locked while a Unit is running."), while the runtime is stopped ("Runtime stopped"). | Drawn only while the server is stopped. |
| Stop | Stops the host gracefully: every client session ends, and the device communication the host carries stops with it, so the Connector reads nothing until Start. "Stopping the OPC UA server…" then "OPC UA server stopped." | The same three situations. | Drawn only while the server is running. |
| Restart | Stop then Start, re-reading the configuration. "Restarting the OPC UA server…" then "OPC UA server restarted." or the failure text above. | The same three situations. | Drawn only while the server is running. |
| Test connection | Reports what the station knows about its own server, without changing anything: "The OPC UA server is stopped. Start it to accept connections.", "The OPC UA server is starting, not ready yet.", or "OPC UA server reachable at <endpoint> with N active session(s)." It is a statement from the running process, not a probe over the network. |
Never. | Never. |
A start that returns without an error is still checked: the OPC UA stack can fail to bind its port and only log the fact, so the feed reports the failure rather than a success. A failed start leaves the lamp grey; the reason is in the server log on Events.
The meters
| Meter | What it counts |
|---|---|
| Uptime | Time since the server last started, as 2h 14m 5s, 14m 5s or 5s; a gap mark while it is stopped. The same instant feeds the Server.StartTime and Server.Uptime points of the Logic address space. |
| Sessions | The client sessions the server has accepted right now, the same list Connected now shows on Client access. |
| Devices | The devices configured in the Connector, across every driver, enabled or not. |
| Drivers | How many distinct drivers those devices use. |
| Errors | The error lines in the communication host's log feed (server and drivers). The feed keeps the most recent 500 lines; the count turns red when it is not zero. |
| Warnings | The warning lines in the same feed, amber when not zero. For a role holding View events the number is a button that opens the detached Events window on the station's own desktop ("Open the Events window"); in a browser on another device it is greyed with "Available on the station's local desktop only.", and for a role without the permission it is a plain number. |
What this section does not do
It does not disconnect one session (revoking a certificate on Client access does), it does not clear the log counts (the feed is bounded and rolls on its own), and it does not restart the application. It never starts the server on its own after a failure: a failed bind is reported and waits for your Start. The endpoint is changed on Configuration, and only while the server is stopped.