The drivers list and a driver's page
The Drivers row's registry table with its enable and disable pair, and a driver node's page: Refresh, Discover, Add device, Pair device, Add line, the device table and the state of a driver the package does not carry.
Two surfaces on the Connector page are about drivers rather than devices. The Drivers row at the top of the Communication column opens the registry: every driver this installation carries, with its enable/disable pair. A driver node in the tree opens that driver's own page: its devices (or, for Modbus RTU, its serial lines) and the verbs that grow the branch. Both are visible with View connector; the toggles and the create verbs need Configure connector.
The Drivers page
The header reads Drivers with the line "Enable the drivers you use. Only enabled drivers appear in the tree, and a driver that has devices stays enabled until its devices are deleted." and a pill summarizing the registry: "3 enabled · 9 devices", with "· 1 line" inserted once a Modbus RTU line exists.
The table
| Column | What it shows |
|---|---|
| Driver | The display name. |
| Description | The driver's one-line description, or "Driver not included in this package." for a driver the package does not carry. |
| Devices | How many devices are configured under it. |
| Health | A dot and the word: Unknown, Disabled, Offline, Partial or Online, rolled up from the driver's devices (its lines, for Modbus RTU). An enabled driver with no devices reads Unknown and a disabled one Disabled; neither pulls the Drivers row's own dot down. |
The list holds the drivers this package carries, in alphabetical order, plus any absent driver that persisted devices or lines still name. OPC DA never appears: the registry knows it, but no driver serves it in this product. Because the list is read from the embedded server's plugin registry, it settles a few seconds after launch, once the server is running.
Row actions
| Command | What it does | Greyed when (situation) | Not drawn when (role) |
|---|---|---|---|
| Open | Selects the driver's group in the tree and opens its page. | The driver is disabled (it has no group to open). | Never. |
| Enable | Adds the driver's group to the tree, empty, and persists the enabled set. The group comes back with the folders it was left with. | The driver is already enabled, or the package does not carry it (tooltip "Driver not included in this package."). | Without Configure connector. |
| Disable | Removes the group from the tree and persists the set. | The driver is off, or it still has devices ("Delete this driver's devices before disabling it.") or serial lines ("Delete this driver's serial lines before disabling it."); the tooltip says which. | Without Configure connector. |
Both toggles refuse while a run holds the station or the runtime is stopped, with the reason in the action feed. Enabling a driver the package does not carry is refused with "'IEC 61850' was not enabled: Driver not included in this package." Disabling the driver whose page is open clears the selection. Adding a device to a driver enables that driver on its own, so the set never contradicts the tree.
The command bar
| Command | What it does | Greyed when (situation) | Not drawn when (role) |
|---|---|---|---|
| Refresh all | Re-applies the whole configuration to the embedded server and reloads the tree from the database. The column comes back closed with nothing selected, and the feed reads "Devices refreshed." | A run holds the station or the runtime is stopped. | Never. |
A driver's page
The header carries the driver's name, its device count in parentheses ("Simulated (9)"; the line count for Modbus RTU) and a health dot. The line under it depends on the situation. For a role without Configure it reads "The devices this driver talks to. Open a row to inspect its settings and tags." For Matter: "Pair a new physical device over Bluetooth, or discover nodes already commissioned in the local Fabric." For any other driver: "Add a device, then use the row actions to open, enable/disable or delete it. The driver is fixed per device." For a driver the package does not carry: "The devices a configuration from elsewhere left here. Open a row to inspect its settings and tags." Modbus RTU says instead "Each line owns one physical serial bus. Configure the port tuple on the line, then add unit-addressed devices beneath it."
The command bar
| Command | What it does | Greyed when (situation) | Not drawn when (role) |
|---|---|---|---|
| Refresh | The same re-apply and reload as Refresh all. | A scan or a pairing is running, a run holds the station, the runtime is stopped. | Never. |
| Add line (Modbus RTU only) | Creates a disabled serial line and opens it; see Serial lines. | A scan is running, or the station refuses mutations. | Without Configure connector. |
| Discovery target field | For a driver whose scan takes a target (OPC UA: "OPC UA server address, e.g. opc.tcp://plc-host:4840"), the box stands immediately before Discover, because it is the parameter that command reads. | While a scan runs or the station refuses mutations. | Without Configure connector, or when the driver has no scan. |
| Discover | Starts the driver's scan; becomes Cancel ("Canceling…" once pressed) while it runs. Details on Discovery. | The scope is invalid, a pairing is running, or the station refuses mutations. | Without Configure connector, or when the driver has no scan. |
| Pair device (Matter only) | Opens the pairing form on the page. | A scan or a pairing is running, the form is already open, or the station refuses mutations. | Without Configure connector. |
| Add device (every other driver) | Creates "New device" (then "New device 2", and so on), enabled, at the driver's own level, and opens it; see Devices. | The package does not carry the driver (tooltip "Driver not included in this package."), a scan or a pairing is running, or the station refuses mutations. | Without Configure connector. |
Right-clicking the driver row offers the same first verb (Add line, Pair device or Add device) and Refresh.
The device table
Every driver except Modbus RTU lists its devices, the same rows the tree draws:
| Column | What it shows |
|---|---|
| Device | The name. |
| Endpoint | The Base URI the embedded server connects to, assembled from the device's Connection card. |
| Tags | How many tags the device has. |
| Health | Dot and word, as on the tree. |
| Last error | The most recent warning or error the journal associated with the device, or "Driver not included in this package." for a device the package cannot serve. |
Row actions: Open for every role, then for Configure connector Enable and Disable (each greyed when it does not apply) and Delete in danger ink, with a confirmation naming the device and its tags. All four grey while a scan or a pairing runs. The empty table reads "No devices yet."
Modbus RTU lists its lines instead: Line, Physical tuple (port · baud · format · timeout), Devices, State (a dot plus text such as "Online · 2/2 devices online") and the actions Open, Enable, Disable and Delete, the last three for Configure connector only. Enable is also greyed while the line's tuple is invalid.
Below the table
The Scan scope card (Modbus TCP) and the Discovered devices card appear around a scan, and the Pair Matter-over-Thread device form replaces the first row on the Matter driver. All three are on Discovery.
Driver not included in this package
A driver group exists for an absent driver only because persisted devices name it: a restored backup, a configuration brought from another machine. Its page then shows a caution banner, "Driver not included in this package": the devices came from a configuration that had the driver, keep their settings and can be deleted, but this installation cannot reach them, so they stay offline and no new device can be added here. On such a page Add device stays drawn and greyed with that reason, Discover is not offered, Copy device on its devices is greyed with the same tooltip, and the runtime's onboarding failure is not repeated as a Last error, because there is no fault to investigate. Which drivers this can happen with is on Drivers.
What these pages do not do
The registry cannot be extended from the page, and a driver cannot be renamed or reordered. A device cannot be moved to another driver. Deleting a driver's devices from the table deletes them one at a time, each with its own confirmation; there is no delete-all. Enabling or disabling a driver does not touch its devices' own Enabled switches, and disabling is never possible while devices or lines remain.