The first live value

The walk from an empty Connector to a tag that reads: the driver, the device, the tag, the first poll, and the Logic address the value gets.

1. Open Connector on the rail. The column on the left is called Communication; its first row, Drivers, lists every driver the package ships. Open it and make sure the driver you need is enabled; for a first try, the built-in Simulated driver needs no hardware. See Drivers.
2. Select the driver in the tree and press Add device on its page (a driver that can find equipment also offers Discover). The device's card takes a Name, a Poll interval (ms) and the connection fields the driver needs; every field saves as you leave it. See Devices.
3. On the device page, press Add tag on the Tags card. The new row takes a name, the address the driver expects on the device, a data type and an access; the tag joins the grid and the tree.
4. The embedded runtime connects in the background and starts polling. Until the device answers, the status bar's health reads "Connector: device not communicating" in red and the device counts under the Issues chip of the Connector column; an unreachable device costs nothing else, its tags read bad quality until the connection lands.
5. Select the tag. Its page shows the Live value card (the current value, the source timestamp and the application timestamp), and the Conversion card explains how the raw reading became the engineering value. See Tags and The value pipeline.

That value now has a Logic address, Connector.<Driver>.<Device>.<Tag> (with a folder segment for a device filed in a folder), and is ready to be shown on a dashboard, read from an expression in Logic, or bound to a channel of a Process model. Other OPC UA clients read it once you let them in: the embedded server starts with Client authentication set to Disabled, which refuses every outside session, so pick Anonymous or Username & password under Settings, OPC UA server, Configuration before pointing a client at it.